SAP Training India USA Pakistan online training From now FICO Consultant.I teach SAP FICO Module I have my own sap Server If you are interested to lean Sap Fico I cover all topics in SAP FICO I have lot of training materials in FICO including job interview questions and Answers regarding FICO. Feel free to contact me by if you want to learn sap fico new posting by email

Jun 4, 2008

Business Blueprint Sap project

Business Blueprint


This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP systems.

The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out.

Integration
You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.

When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration.

You can also display and edit the project documentation from the Business Blueprint phase, during configuration.

You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions.

Prerequisites
You have created a project of type implementation, template, or upgrade, in the project administration.

Features
Scope of the Business Blueprint Transaction Function
Tab

Create a project structure
Structure

Display the following documentation:

Documentation delivered by SAP, e.g. scenario descriptions

Documents from templates, e.g. from template projects

To be able to edit general documentation, copy it to the Project Documentation tab.
General Documentation

Assign documents to structure elements

Create, Change, Upload user documents
General Documentation in template projects

Project Documentation in all project types

Input administration data, e.g. project status, team members assigned, planned and actual resources
Administration

Assign transactions and programs to structure elements
Transactions

Create, Display and Edit issues und messages
Issues/Messages

Display and Create a process graphic
Graphics

Where-used list:

Use in user project

Use in other projects

Go to use by double-click
General Documentation

Project Documentation

Transactions


General Functions Function
Navigation

Change the sequence, hide or show tabs
Settings User-Specific

Translate project structure

For further information about translating document names for URLs, in your project, see Translating a Template
Goto Translation

Create/print a Business Blueprint document
Business Blueprint Create Blueprint Document

Assign document authorization
Assign authorizations in the Role (PFCG) and User Maintenance.


Activities
Create a Blueprint structure in the Structure tab, using predefined substructures.

Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.

Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.

Create project documentation to save in the Business Blueprint, in the Project Documentation tab.

Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise.

Print the Business Blueprint document.

When the Business Blueprint is complete, you can start to set up the development system landscape.

Result
You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.

May 31, 2008

Test Scripts FICO

Guide for Testing SAP Financial
TESTING

Unit Testing
When you test every single document is called unit testing.

String Testing
One transaction full activity is called string testing . For example Vendor invoice, goods received and vendor payment.

Integration Testing
It is purely with other modules and we have to check whether the FI testing is working with other related modules or not.

Regression Testing
Testing for whole database. Bring all the data into another server and do the testing is called regression.

UAT
When we test any particular document with the user and if it is ok immediately we have to take the signature on the document, which is signed off and can be forwarded to the immediate boss. There are some steps to be followed when we go for user acceptance testing.

Transaction – Script Writing – Expected Results – Compare with Actual Results

TPR (Transaction Problem Reporting)
While doing the user acceptance testing if we get any problems then there are some methodologies to be followed according to the company’s policy and normally as a tester we always need to write on Test Script itself.

Key Features
Understanding the business scenarios
Organization Structure to incorporate the tune of the script.
Preparation of test scripts
Execute and record results to see if it is fine before going to approval.
Make changes to your test script if required.

What is Test Script (Scenario Testing)
Header Data
Step in Process
Transaction Code / Program (FB60)
Menu Path
Description
Field Data and actions to complete
Expected Results
Actual Results
TPR
Closing Period
F.19 Clearing GR/IR Account
F.13 Adjustments GR/IR Account

Using of these above two accounts will help us in clearing the balances and adjustments to those respective clearing accounts so that the GR/IR account will be zero balance and the balances will appear in respective reconciliation accounts accordingly the balances will be carried forwarded to next fiscal year.

GR/IR Clears the following Documents
GL Document
Customer Documents
Vendor Documents
Assignment Field is important in any document (ZUONR), Amount (DMBTR)

Foreign Currency Valuation
Lowest Value Method, If we are in loss then only we will account for it.

GL Accounts which are important in Testing
Enjoy Transaction - FB50
Normal Transaction - FB01
Document Parking - FV50
Post with Clearing - F-04
Incoming Payment - F-06
Outgoing Payment - F-07

Document Related
Reset Cleared Items - FBRA
Parking Document Posting - FBVO
Reversal Documents - F-14
Company Code Clearing A/C
(Trial Balance purposes) reversal - (FBUB)

Clearing Account
Partial clearing Invoice - 100 - Open Item
Paid - 70 - Open Item
Balance - 30

In Partial Clearing you can see 100 and 70 are cleared line items and 30 as balance and if it is in Residual you can only 30 as balance as it creates new line item and you can’t see the other cleared line items.

As no company will use residual clearing as it affects on ageing reports.

Open Items in Foreign Currency in all Modules GL/AP/AR - F.05
Master Data

Company Code
Currency
Only Balances in local currencies
Reconciliation Account Type

Year End Scripts
Re Grouping Receivables / Payables - (F101)

Bad Debts Provisions – Scripts
We assume that the customer has not paid at the end of the year you doubt whether this receivable will ever be paid. So you make a transfer posting for the receivables to an account for individual value adjustments using special GL Indicator E and Transaction Code F-21

Carry forward Balances
Sub Ledgers and General Ledger balances to be forwarded to next Fiscal Year

Accounts Payables
Vendor Down Payments
Invoice
Parking
Reversal
Outgoing Payments
Automatic Clearing
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations

Accounts Receivables
Customer Down Payments
Invoice
Parking
Reversal
Incoming Payments
Manual Clearing
Advance (Down Payment)
Post with Clearing
Post without Clearing
Reset Clearing
Carry forward
Regrouping
Foreign Currency Valuations

May 29, 2008

GL ACCOUNT TYPE

G/L NO.---------LONG TEXT-----------ACCOUNT GROUP------ACCOUNT TYPE-----RECON ACCOUNT
100001----------EQUITY CAPITAL------SHARE CAPTIAL------BALANCE SHEET----- NO
100401---------A/P DOMESTIC---------CURRENT LIABILITY----BS SHEET-----VENDOR
100402----------ACCUMULATED DEPRECIATION CURRENT LIABILITY---BS-----------ASSETS
200000-----------PLANT AND MACHINERY------

Account Group

ACCOUNT GROUP------DESCRIPTION----------FROM----------------TO
SCPL-----------SHARE CAPITAL-----------100000------------100100
RSPL----------RESERVES & SURPLUS------100100-------------100200
SCLN----------SECURED LOANS-----------100200-------------100300
UNSC----------UNSECURED LOANS---------100301-------------100400
CLPS----------CURRENT LIABILITIES-----100401-------------100500
FXAT----------FIXED ASSET-------------200000-------------200100
CAST----------CURRENT ASSETS----------200101-------------200200
LNAN----------LOANS AND ADV-----------200201-------------200300
SALE----------SALE REVENUE------------300000-------------300100
OTIN----------OTHER REVENUE-----------300101-------------300200
RMCN----------RAW MAT CONSUMPTION-----400000-------------400100
PERN----------PERSONAL COST-----------400100-------------400200
ADMN----------ADMIN COST--------------400201-------------400300
SEDN----------SELLING DISTRU----------400301-------------400400
DEPN----------DEPRECIATION------------400401-------------400500

May 22, 2008

Validation GGB0

Validation are used to check setting and return a message if the prerequisite check condition is met you can used validation to supplement existing sap logic to fit you business needs a validation is a valuable tool that can be used in many of the financial and controlling modules.
Fi validation to fulfill our requirement of allowing posting from company code 1200 to be posted to only business area EES to maintain the validation.

May 20, 2008

Variant

A variant is a particular setting when we post any transcations some data input screen allow us to save and execute variant we can create variant is a good way to save time because we already put some data for this and next time we just execute this variant so no need to enter all data.

May 15, 2008

Depreciation

When you do a midyear takeover of assets, as opposed to a yearend
takeover, you'll need to handle

current year transactions in a special way in order to have
correct info on acquisition reports for both

book and tax purposes. Assets acquired in the current fiscal
year will require an acquisition transaction
to load them correctly.

*

Assets acquired before the current fiscal year

The AS91 transaction looks for three amount fields:

KANSW

Asset cost as of the end of the last fiscal
year
KNAFA

Accumulated depreciation balance as of the
end of the last FY
NAFAG

Depreciation expense posted this FY

*

Assets with a capitalization date in the current fiscal year

The AS91 transaction grays out the cost and accumulated depreciation
fields (KANSW) and (KNAFA) and requires
the following:

NAFAG

Depreciation expense posted this FY
BZDAT

Acquisition date
BWASL

Transaction type - default 100
ANBTR

Asset cost

*

Current year acquisitions to prior year assets

Create old asset the normal way and add the current year transaction.

KANSW

Asset cost as of the end of the last fiscal year
KNAFA

Accumulated depreciation balance as of the end
of the last FY
NAFAG

Depreciation expense posted this FY
BZDAT

Acquisition date of current year posting
BWASL

Transaction type - default 152
ANBTR

Cost of additional asset posting

*

Current year retirements of prior year assets

DEAKT

Asset deactivation date, which is the retirement
transaction date
KANSW

Asset cost as of the end of the last fiscal year
KNAFA

Accumulated depreciation balance as of the end
of the last FY
NAFAG

Depreciation expense posted this FY
BZDAT

Transaction date of current year retirement
BWASL

Transaction type - default 200
ANBTR

Retirement amount. Should be current month NBV
for area 01 and prior year NBV for the tax areas.

Important Enteris FI

Inventory Accounting Entries
For Example: during Goods Receipt

Stock Account - Dr
G/R I/R Account - Cr
Freight Clearing account - Cr
Other expenses payable - Cr

During Invoice Verification

G/R I/R Account - Dr
Vendor - Cr

When the Goods are issued to the Production Order the following transactions takes place:

Consumption of Raw Materials - Dr
Stock A/c - Cr

When the Goods are received from the Production Order the following transactions takes place:

Inventory A/c - Dr
Cost of Goods Produced - Cr
Price difference - Dr/Cr
(depending on the difference between standard cost and actual cost)

When the Goods are dispatched to customer through delivery the following transactions takes place:

Cost of Goods Sold - Dr
Inventory A/c - Cr

When the Goods are issued to a Cost Center or charged off against expenses the following transactions takes place:

Repairs and Maintenance - Dr
Inventory A/c - Cr

When the Goods are stock transferred from one plant to another, the following transactions takes place:

Stock A/c - Dr (Receiving location)
Stock A/c - Cr (Sending location)
Price difference - Dr/Cr
(due to any difference between the standard costs between the two locations)

When the stocks are revalued, the following transactions takes place:

Stock A/c - Dr/Cr
Inventory Revaluation A/c - Cr / Dr

When the Work in Progress is calculated the following transaction takes place:

Work in Progress A/c - Dr
Change WIP A/c - Cr

Physical verification /shortages and excesses : Shortages/excesses on authorizations shall be adjusted using the physical inventory count transaction.

SAP CO TABLE NAME

Table Name Description Important Fields
AUSP Characteristic Values MANDT / OBJEK / ATINN / ATZHL
CO-KBAS Overhead Cost Controlling
A132 Price per Cost Center MANDT / KAPPL / KSCHL / KOKRS
A136 Price per Controlling Area MANDT / KAPPL / KSCHL / KOKRS
A137 Price per Country / Region MANDT / KAPPL / KSCHL / KOKRS
COSC CO Objects: Assignment of Origina MANDT / OBJNR / SCTYP / VERSN
CSSK Cost Center / Cost Element MANDT / VERSN / KOKRS / GJAHR
CSSL Cost Center / Activity Type MANDT / KOKRS / KOSTL / LSTAR
KAPS CO Period Locks MANDT / KOKRS / GJAHR / VERSN

CO-KBASCORE Overhead Cost Controlling: General Services
CSKA Cost Elements (Data Dependent on MANDT / KTOPL / KSTAR
CSKB Cost Elements (Data Dependent on MANDT / KOKRS / KSTAR / DATBI
CSKS Cost Center Master Data MANDT / KOKRS / KOSTL / DATBI
CSLA Activity Master MANDT / KOKRS / LSTAR / DATBI
CO-OM (KACC) Overhead Cost Controlling
COBK CO Object: Document Header MANDT / KOKRS / BELNR
COEJ CO Object: Line Items (by Fiscal MANDT / KOKRS / BELNR / BUZEI
COEJL CO Object: Line Items for Activit MANDT / KOKRS / BELNR / BUZEI
COEJR CO Object: Line Items for SKF (by MANDT / KOKRS / BELNR / BUZEI
COEJT CO Object: Line Items for Prices MANDT / KOKRS / BELNR / BUZEI
COEP CO Object: Line Items (by Period) MANDT / KOKRS / BELNR / BUZEI
COEPL CO Object: Line Items for Activit MANDT / KOKRS / BELNR / BUZEI
COEPR CO Object: Line Items for SKF (by MANDT / KOKRS / BELNR / BUZEI
COEPT CO Object: Line Items for Prices MANDT / KOKRS / BELNR / BUZEI
COKA CO Object: Control Data for Cost MANDT / OBJNR / GJAHR / KSTAR
COKL CO Object: Control Data for Activ MANDT / LEDNR / OBJNR / GJAHR
COKP CO Object: Control Data for Prima MANDT / LEDNR / OBJNR / GJAHR
COKR CO Object: Control Data for Stati MANDT / LEDNR / OBJNR / GJAHR
COKS CO Object: Control Data for Secon MANDT / LEDNR / OBJNR / GJAHR
CO-OM-CEL (KKAL) Cost Element Accounting (Reconciliation Ledger)
COFI01 Object Table for Reconciliation L MANDT / OBJNR
COFI02 Transaction Dependent Fields for MANDT / OBJNR
COFIP Single Plan Items for Reconciliat RCLNT / GL_SIRID
COFIS Actual Line Items for Reconciliat RCLNT / GL_SIRID

CO-OM-CCA Cost Center Accounting (Cost Accounting Planning RK-S)
– What is RK-S
A138 Price per Company Code MANDT / KAPPL / KSCHL / KOKRS
A139 Price per Profit Center MANDT / KAPPL / KSCHL / KOKRS
CO-OM-OPA (KABR) Overhead Orders: Application Development R/3
Cost Accounting Settlement
AUAA Settlement Document: Receiver Seg MANDT / BELNR / LFDNR
AUAB Settlement Document: Distribution MANDT / BELNR / BUREG / LFDNR
AUAI Settlement Rules per Depreciation MANDT / BELNR / LFDNR / AFABE
AUAK Document Header for Settlement MANDT / BELNR
AUAO Document Segment: CO Objects to b MANDT / BELNR / LFDNR
AUAV Document Segment: Transactions MANDT / BELNR / LFDNR
COBRA Settlement Rule for Order Settlem MANDT / OBJNR
COBRB Distribution Rules Settlement Rul MANDT / OBJNR / BUREG / LFDNR
CO-OM-OPA (KAUF) Overhead Orders: Cost Accounting Orders
AUFK Order Master Data MANDT / AUFNR
AUFLAY0 Enttity Table: Order Layouts MANDT / LAYOUT
EC-PCA (KE1) Profit Center Accounting
CEPC Profit Center Master Data Table MANDT / PRCTR / DATBI / KOKRS
CEPCT Texts for Profit Center Master Da MANDT / SPRAS / PRCTR / DATBI
CEPC_BUKRS Assignment of Profit Center to a MANDT / KOKRS / PRCTR / BUKRS
GLPCA EC-PCA: Actual Line Items RCLNT / GL_SIRID
GLPCC EC-PCA: Transaction Attributes MANDT / OBJNR
GLPCO EC-PCA: Object Table for Account MANDT / OBJNR
GLPCP EC-PCA: Plan Line Items RCLNT / GL_SIRID

EC-PCA BS (KE1C) PCA Basic Settings: Customizing for
Profit Center Accounting
A141 Dependent on Material and Receive MANDT / KAPPL / KSCHL / KOKRS
A142 Dependent on Material MANDT / KAPPL / KSCHL / WERKS
A143 Dependent on Material Group MANDT / KAPPL / KSCHL / WERKS

SAP FICO TABLE NAME

Table Name Description Important Fields
Financial Accounting
FBAS Financial Accounting “Basis”
BKPF Accounting Document Header BUKRS / BELNR / GJAHR
BSEG Accounting Document Segment BUKRS / BELNR / GJAHR / BUZEI
BSIP Index for Vendor Validation BUKRS / LIFNR / WAERS / BLDAT /
of Double Documents XBLNR / WRBTR / BELNR / GJAHR
/ BUZEI
BVOR Inter Company Posting BVORG / BUKRS / GJAHR / BELNR
Procedure
EBKPF Accounting Document Header GLSBK / BELNR / GJHAR / GLEBK
(docs from External Systems)
FRUN Run Date of a Program PRGID
KLPA Customer / Vendor Linking NKULI / NBUKR / NKOAR / PNTYP
/ VKULI / VBUKR / VKOAR

KNB4 Customer Payment History KUNNR / BUKRS
KNB5 Customer Master Dunning Data KUNNR / BUKRS / MABER
KNBK Customer Master Bank Details KUNNR / BANKS / BANKL / BANKN
KNC1 Customer Master Transaction KUNNR / BUKRS / GJHAR
Figures
KNC3 Customer Master Special KUNNR / BUKRS / GJAHR / SHBKZ
GL Transactions Figures
LFB5 Vendor Master Dunning Data LIFNR / BUKRS / MABER
LFBK Vendor Master Bank Details LIFNR / BANKS / BANKL / BANKN
LFC1 Vendor Master Transaction LIFNR / BUKRS / GJHAR
Figures
LFC3 Vendor Master Special LIFNR / BUKRS / GJHAR / SHBKZ
GL Transactions Figures
VBKPF Document Header for AUSBK / BUKRS / BELNR / GJHAR
Document Parking
FBASCORE Financial Accounting General Services “Basis”
KNB1 Customer Master (Company Code) KUNNR / BUKRS
LFA1 Vendor Master (General Section) LIFNR
LFB1 Vendor Master (company Code Section) LIFNR / BUKRS
SKA1 G/L Account Master (Chart of Accounts) KTOPL / SAKNR
SKAT G/L Account Master (Chart of Accounts – SPRAS / KTOPL / SAKNR
Description)
MAHNS Accounts Blocked by Dunning KOART / BUKRS / KONKO / MABER
Selection
MHNK Dunning Data LAUFD / LAUFI / KOART / BUKRS /
(Account Entries) KUNNR / LIFNR / CPDKY / SKNRZE /
SMABER / SMAHSK / BUSAB

FI-GL-GL (FBS) General Ledger Basic Functions-
G/L Accounts
SKAS G/L Account Master – SPRAS / KTOPL / SAKNR / SCHLW
(Chart of Accounts Key Word list)
SKB1 G/L Account Master (Company Code) BUKRS / SAKNR
FI-GL-GL (FBSC) General Ledger Accounting: Basic
Functions - R/3 Customizing for G/L Accounts
FIGLREP Settings for G/L Posting Reports MANDT
TSAKR Create G/L account with reference BUKRS / SAKNR
FI-GL-GL FFE) General Ledger Accounting: Basic
Functions - Fast Data Entry
KOMU Account Assignment Templates for G/L KMNAM / KMZEI
Account items
FI-AR-AR (FBD) Accounts Receivable: Basic Functions - Customers

KNKA Customer Master Credit Management : KUNNR
Central Data
KNKK Customer Master Credit Management : KUNNR / KKBER
Control Area Data
KNKKF1 Credit Management : LOGSYS / KUNNR / KKBER / REGUL
FI Status data
RFRR Accounting Data – A/R and A/P RELID / SRTFD / SRTF2
Information System
FI-BL-PT Bank Accounting: Payment (BFIBL_CHECK_D)
Transactions – General Sections
PAYR Payment Medium File ZBUKR / HBKID / HKTID / RZAWE /
CHECT
PCEC Pre-numbered Check ZBUKR / HBKID / HKTID / STAPL
FI-BL-PT-AP(FMZA)Bank Accounting: Payment
Transactions – Automatic Payments

F111G Global Settings for Payment Program for MANDT
Payment Requests
FDZA Cash Management Line Items in Payment KEYNO
Requests
PAYRQ Payment Requests KEYNO

What is the table name for G/L Master data, when we create
centrally (T.Code - FS00)?
As far as general ledger master data is concerned, the following tables are involved :

Table name : SKB1 : G/L Account Master ( Company Code)
Fields:
BUKRS : Company Code
SAKNR : G/L Account

Table name : SKA1 : G/L Account Master ( Chart of Accounts )
Fields:
KTOPL : Char of Accounts
SAKNR : G/L Account

Table name : SKAT : G/L Account Master Record ( Chart of Accounts : Description )
Fields:
SPRAS : Language
KTOPL : Char of Accounts
SAKNR : G/L Account