Charts of Account

In SAP FICO system, after creating Company Code, the next thing we have to do is creating Chart of Accounts (COA).In SAP R/3 term, Chart of Accounts is a unique four alphanumeric code that represents the structure of group of General Ledger (G/L) accounts. The COA contains the definition of all G/L accounts such as their account number, account name, and the type of G/L account (whether the account is a Profit &Loss; /P&L; type account or a balance sheet type account).
Each company code must have one chart of accounts (COA) for its general ledger. The COA must be assigned to the company code. A COA can be assigned to several company codes which mean that these company code’s general ledgers have the same structure.

We can define Chart of Accounts with “OB13” T-code or through “SPRO” T-code menu: Financial Accounting – General Ledger Accounting – G/L Accounts – Master Records – Preparations – Edit Chart of Account Lists.
The definition of COA determines some characteristics of the COA, which are:
§  Chart of Accounts code and its description.
§  The language of COA.
§  Length of G/L Account number of the COA (up to 10 digits, can be numerical or alphanumeric).
§  Type of integration between G/L accounts and cost elements. It controls of how a cost element can be maintained when maintaining a G/L account. A cost element classifies the company’s valuated consumption of production factors within a controlling area. A cost element corresponds to a cost-relevant item in the chart of accounts such as expense account (a P&L; account).
 The following options are available for each G/L account:
§  No maintenance of cost elements.
§  Cost elements maintained manually.
§  Cost elements maintained automatically. When we save a new G/L account, the related cost element is automatically created. A prerequisite is that a default value for the cost element category has been set up for this cost element. If no default value is found, the system will not create a cost element.
§  Group Chart of Accounts for consolidation process (if the general ledger of the company code will be consolidated to the parent company’s general ledger).
§  The status of COA: blocked or not. SAP suggests blocking COA if charts of accounts are created centrally and accounts are created locally. If this is the case, then the block prevents accounts from being created in the company codes for a chart of accounts that is not yet completed.

Comments

Post a Comment

Popular posts from this blog

Batch input session SM35

Image
Batch in put session is the same for all the modules and processes. Its independent and it can be use for all the processes. In SM35, we can select the session for recurring entry or for any other scheduled process. We can manage sessions, lock it, unlock it, see logs etc. For running batch input session it gives us 3 options. Foreground, background and errors only. Foreground means system will roll all the transaction on the screen and we can see it. Background means system will process all the transaction in background. Errors only means the system will process in background but will show errors. For ease we select extended log and expert mode while starting a batch input session. Now once we run batch input session we need to know results of it right? Here it is how we get results of batch input session in SAP FICO.  Batch job overview
Read more

Manual Clearing Vendor open line items F-44

Image
In SAP FICO, F-53 kept the line items open even if it got paid. How to clear them? Through F-44. Here give the vendor account number whom we want to clear line items. Process open items will redirect to the new screen. Select which line items to be cleared, simulate and save. It will clear the line items and gives a document number. Upon displaying document it shows a document with no line items but just header data. It is an important certification question that only clearing document display have just header data and no line items. All the financial accounting entries saved in tables BKPF and BSEG for header data and line item data respectively. So for most of the documents there is a link between these two tables, but for clearing document there is an entry in BKPF only.
Read more

iDoc types and applicable message types

Outbound processing: BENREP     BENEFIT1 CARNOT    DELVRY01 CREADV     PEXR2001, PEXR2002 DEBADV     PEXR2001, PEXR2002 DELFOR     DELFOR01 DELINS     DELFOR01 (FDS and JIT) DELJIT     DELFOR01 DESADV     DELVRY01, DELVRY02, DELVRY03 (previously: DESADV01) EXPINV     EXPINV01, EXPINV02, EXPINV03 GSVERF     GSVERF01 IFTMIN     SHPMNT03 IMPINV     IMPINV01 INVOIC     INVOIC01 ORDCHG     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 ORDERS     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 ORDRSP     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 PAYEXT     PEXR2001, PEXR2002 PRICAT     PRICAT01 PROACT     PROACT01 QUOTES     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 REMADV     PEXR2001, PEXR2002 REQOTE     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 SHPADV     SHPMNT03 SHPMNT     SHPMNT01, SHPMNT02, SHPMNT03, SHPMNT04 SHPORD     DELVRY01 WHSORD    DELVRY01 Inbound processing: CREADV  
Read more