G/L Account Master Records

Business transactions are posted to accounts and are managed via accounts. You must create a master record for each account you need. It contains information that controls the entry of business transactions in an account and the processing of data.

The G/L accounts record the business transactions in totals form. In the standard system, all business transactions that are posted to G/L accounts are updated in the general ledger. Additionally, you can define further ledgers which are also posted to. For this, you must use the Special Purpose Ledger system. Information on additional ledgers can be found in FI-SL Special Purpose Ledger.

The following sections contain basic information on G/L account master data as well as explanations of the settings that you make in Customizing. More detailed information on how to make these settings can be found in the General Ledger Accounting Implementation Guide. You can also find out how to create, display, change, delete, or lock general ledger master data.

FI General Ledger Accounting

The central task of G/L accounting is to provide a comprehensive picture for external accounting and accounts. Recording all business transactions (primary postings as well as settlements from internal accounting) in a software system that is fully integrated with all the other operational areas of a company ensures that the accounting data is always complete and accurate.

The SAP FI General Ledger has the following features:

• Free choice of level: corporate group or company
• Automatic and simultaneous posting of all sub-ledger items in the appropriate general ledger accounts (reconciliation accounts)
• Simultaneous updating of general ledger and cost accounting areas
• Real-time evaluation of and reporting on current accounting data, in the form of account displays, financial statements with different financial statement versions and additional analyses.

Essentially, the general ledger serves as a complete record of all business transactions. It is the centralized, up-to-date reference for the rendering of accounts. Actual individual transactions can be checked at any time in realtime processing by displaying the original documents, line items, and transaction figures at various levels such as:

• Account
• Journals
• Summary/balance transaction figures
• Balance sheet/profit and loss evaluations

Can EBS post to a cost center and income statement G/L Account?

I am trying to post directly to a cost center instead of using a clearing acct. The clearing acct is determined via user exit and acct modifier.

How would I post directly to a cost center?

Please see OSS note 494777 and 155596 for explanation of the function exit_rfebbu10_001 (enhancement FEB00001) for EBS processing... You might also want to reference OSS note 0124655 that describes supported functions of the EBS...

We use a custom "Z" table (this data is treated as transportable configuration) that contains our cost center values for posting to P&L accounts processed in EBS... this table supplies the values in the user-exit (above)...

GR/IR Clearance Account in SAP system

GI/IR clearing account is value based or quantity based?

Please find details for the GR/IR Clearance account in SAP system:

GR/IR Clearing Account Maintenance

Quantity differences between goods receipt and invoice receipt for a purchase order result in a balance on the GR/IR clearing account.

- If the quantity invoiced is larger than the quantity received, the system then expects further goods receipts for this purchase order to clear the balance.

- If the quantity received is larger than the quantity invoiced, the system then expects further invoices for this purchase order to clear the balance.

You can also clear differences for delivery costs. If no more goods or invoices are to be received, you must clear the balance manually. This can be done in different ways:

- You can return the extra goods to the vendor.

- You can cancel the invoice and post a corrected invoice or a credit memo for the surplus posted quantity.

- You can clear the GR/IR clearing account manually.

Maintaining the GR/IR Clearing Account

The GR/IR clearing account is usually cleared at the end of a period or fiscal year for that order items that no further goods receipts or invoices are expected for.

1. Choose Logistics -> Materials Management -> Logistics Invoice Verification -> GR/IR Account Maintenance -> Maintain GR/IR Clearing Account.

The GR/IR Account Maintenance screen appears.

2. Enter data as required on this screen in the Document header data frame.

3. In the Selection frame, you choose various selection criteria for the transactions for which you want to post the differences are available for the following selection fields. You maintain them in the user master.

4. Choose the processing type:
- Automatic clearance
- The Automatic clearance function is intended for processing in the background.
Choose Program -> Execute in background.
- Prepare list
- Choose Execute.
- The selection screen appears.

5. On the selection screen, the individual purchase order items that have quantity variances and match your selection are now listed. Select the order items that you want to clear.

6. Clear the GR/IR clearing account for the selected purchase orders by choosing List -> Post clearing.

Account Maintenance Document

Document that displays the quantities of the debit or credit of a material in GR/IR clearing account maintenance.

If you clear quantity differences between the goods receipt and invoice receipt for a purchase order using account maintenance, the system produces an account maintenance document.

You can branch from the account maintenance document to the following accounting documents, assuming that they exist:
- Accounting document
- Profit center document
- Special ledger document
- Material ledger document

Change Reconciliation Account of Customer Master in sap

There is no problem to change the account number in the vendor or customer master data, that is :

All Document Items that were created in the old account will be posted in the same old account when you have a payment posting, compensations, etc.

All document created after the change will be posted in the new account as well as the payment postings, compensations and others.

The system will separate the postings in accordance with the moment at the documents were created.

You can do a test in the development client before you do the change in the production.

For example :-

You can create a new reconciliation account because you want the G/L accounts to separate out sales. Just switched the setting in Customer Master and off you go. SAP will recognized the old account for the old postings and used the new account for any new postings.

Here is the official SAP help on the subject:-

You should run balance sheet adjustment program after any reconciliation account change.

The system performs any adjustments required due to the change of reconciliation accounts or G/L accounts. The items from the old reconciliation accounts are allocated to the new accounts.

Since you cannot post to the reconciliation accounts directly, the postings are made to temporary adjustment accounts.

These adjustment accounts should be displayed along with the relevant reconciliation account in the balance sheet. The postings are then reversed after the balance sheet has been created.

The program for sorting the payables and receivables makes the necessary adjustments automatically. This means that you have to define the adjustment account numbers and the posting keys for these postings in the system.

If you purchase and install the FI-LC Consolidation application and have bought up a previous customer or vendor (thus also taking on his/her payables and receivables), please refer to the note in the report documentation on changed reconciliation accounts. To define the account numbers, select the activity Define adjustment accounts for changed reconciliation accounts in the Accounts Receivable and Accounts Payable Implementation Guide.

You should only run this program if your new reconciliation account is classified differently from the original in your FS. e.g.. AR to Intercompany accounts. It will just reclassify the existing balance. The line items will not be transferred. If not then no need to run the program at all.

How to Configure FICO Reconciliation

In Co, we create Recon accts to keep Fi gl in balance with CO. Not all transactions affect FI gls, best example of it is internal order settlements, they use secondary cost elements and does not affect your G/l accts. To update FI side of it we maintain recon accts. These are primarily for cross company, cross functional and cross business area transactions.

The number of recon accts to be defined is dependant on various factors, like how your management wants to see the reports.. whether they want to classify the cost based on CO object class or by Co types etc..

However the basic config you got to follow is:

1. Activate Recon accts (if you have created CO area newly, it would be active).
use T.code: KALA

2. Assignment of Recon document type to the Controlling area.
T.code: OKKP

3. Creating clearing accts (that you want to us! e for reconciliation. During FI-Co recon.. inter company clearing accounts will be automatically credited or debited and now you need to create offset acct which will show up in P&l acct).
Acct determination set up thru T.code: OBYA

4. Maintain accts for Automatic Recon posting.
T.code OBYB

5. Assign Number ranges to Recon activity.
Tcode OK13 *-- Radha Krishna

Without creating of reconciliation account, can you create vendor? What is the use of reconciliation?

Customer and vendor accounts are sub ledger GL's. We will have to create two reconciliation GLs in viz. Reconciliation GL for Customer and Vendor in chart of accounts.

After, while creating customer and vendor master records, we have to mention respective reconciliation GL in their company code segment details. This recon a/c will show you the net balances in GL for customer and vendor a/cs.

Without creating Vendor you can still create individual GL for each customer and vendor , but then
1) Your list of GL's in chart of account will be very lengthy.
2) Duplication of work as SD/ MM people are also required to create their own list.
3) Cross company code consolidation will not be possible as the chart of accounts will be different.
4) Very difficult to keep track of individual customer/ vendor a/cs.
5) Not advisable even in real time accounting system i.e. manual book keeping.

Step-by-Step Procedure for Customizing an Electronic Bank Reconciliation Statement in sap

To set up Electronic Bank Statements (EBS)

Processing in SAP for most customers in North America.

1. Create House Bank and Account ID (FI12)

2. Setup EDI Partner Profile for FINSTA Message Type (WE20)

3. Configure Global Settings for EBS (IMG)
- Create Account Symbols
- Assign Accounts to Account Symbols
- Create Keys for Posting Rules
- Define Posting Rules
- Create Transaction Types
- Assign External Transaction Types to Posting Rules
- Assign Bank Accounts to Transaction Types

4. Define Search String for EBS(Optional)
- Search String Definition
- Search String Use

5. Define Program and Variant Selection

Additional information is also available in the SAP Library under:
Financial Accounting > Bank Accounting (FI-BL) > Electronic Bank Statement >
Electronic Account Statement Customizing.

SAP FI Tips by: Ramesh

Bank Reconcilliation Statement

The following are the steps for BRS:

Create Bank Master Data - This can be created through T.Code FI01 or you can also create the house bank through IMG/FA/Bank accounting/Bank account

2. Define House Bank

3. Set up Bank selection payment programe- IMG/FA/ARAP/BT/AUTOIP/PM/Bank selection for payment prg.

a. setup all co codes for payment transaction - Customer and vendors

b.setup paying co codes for payment transactions

c.setup payment method per country

d.setup payment method per co code for payment transaction

e.setup bank determination for payment transaction

Please go for Cheque mangement using T code FCHI (IMG/FA/ARAP/BT/OP/AutoOp/PaymentMedia/CheckManagement) and for void reasons FCHV. You can create Bank Reconcilliation statement by TC FF67 (SAP/AC/Treasury/CashManagement/Incomings/ManualBankStatement) . Don't forget to keep the opening Balance as zero. Use FBEA for post process.

All the steps together will lead to (FF67) Bank reconciliation statement.

Document flow confusion in SAP FI

I have a problem understanding basic things like how a document flows in the Sap system. When posting a customer invoice the subledger will be debited with that amount, now my confusion is will the same amount be posted to the G/L only or the very same amount will also be posted to the reconciliation general ledger - making 3 postings or The recon acc is the G/L . I don't see 3 postings happening because then 2 debits will be Posted against one debit -please clarify me on this.

Also the different between the G/L, Special ledgers and the recon acc is not clear to me.

Customer and Vendor accounts are maintained in a subledger. Posting to these accounts will also be posted to the A/R and A/P reconciliation accounts. All Reconciliation accouints are GL accounts.

All G/L accounts are not reconciliation accounts.

Why is this done?

In large businesses, there will be hundreds/thousands of customers/vendors. All these are personalaccounts (there are three types of accounts: nominal, personal and real). These personal accounts are grouped in to sub-ledgers and any posting to them is reconciled to the G/L
via the reconciliation accounts.

Prakash

For fulfilling completing the double entry system accounting the Reconciliation accounts i.e., Accounts Receivable and Accounts Payable are used. All the Vendors are grouped under Acounts Payable & Customers are grouped under Accounts Receivable. And also always any time the balance in reconciliation account shows as zero.

Ex: 1) Vendors transaction:
For Invoice posting:
Inventory A/c Dr
To Vendor A/c................Accounts Payable A/c (Reconciliation Ledger)
(In SAP since we are linking in the G/L Master Accounts Payable with the Reconciliation Accounts type setting as Vendors. Hence, with one entry 3 Accounts are automatically updated)

Accounts Payable is Liability & Inventory is Current Assets.
For Payment to Vendor:
Vendor A/c Dr.....Accounts Payable A/c
To Bank/ Cash A/c

Ex:2) Customer Transaction:
Sales Invoice Posting:
Customer A/c Dr...Accounts Receivable A/c (Reconciliation A/c)
To Sales A/c

Receipt Posting:
Bank A/c Dr
To Customer A/c...........Accounts Receivable A/c

In Normal Accounting the Reconciliation Accounts are called as Control Accounts and we pass 2 entries for each transaction i.e., Sale, as following:
1) Customer A/c Dr (Sales Ledger / Accounts Receivable A/c)
To Sales A/c (General Ledger)
2) Accounts Receivable A/c Dr (General Ledger)
To Customer A/c (Sales Ledger Adjustment A/c)

Hence, any time the Control A/c balance is zero.

I hope I am clear and now your confusion problem gets resolved.

These are basic accounting differentiation for different types of accoutns. This is a basic accounting concept and is not specifically mentioned anywhere in SAP terminology.

Personal accounts:

Accounts in the name of individuals, organizations etc.
For example, Company A A/c, XYZ limited co A/C, Suresh A/C, Indian Bank A/C etc

Real Accounts:

These are accounts related to assets, both real and tangible.
example, furniture a/c, machinery a/c, accounts receivables a/c etc

Nominal Accounts:

These are related to incomes/expenditures and profit/losses.
for example, sales A/c, salary a/c etc

I hope this clears your doubts

What is "Real Time" Integration? in sap

What is "real time integration" advantage of SAP?

What is the Config for Integration entry? How these entries get formulated in backend?

Real time integration is nothing but the data posting to all the affected areas instantly when an activity is performed. For E.g. When you do a FI-SD integration, when a PGI is posted, the following entry is affected :

1. Cost of Goods Sold Dr 100
To Inventory Account Cr 100

Here the Cost of Goods Sold is an FI entry and Inventory Account related to MM but both of them gets affected immediately when you post a PGI in SD.

The updation of these entries when PGI is done is called Real Time Integration. The affect is shown in all FI, MM and SD modules once you save the entry.

The configuration for the below entry is done in OBYC

1. Cost of Goods Sold Dr 100 (T-Key GBB)
To Inventory Account Cr 100 (T-Key BSX)

The automatic entries are posted to inventory accounts through T-keys to which GL accounts are assigned. These T-keys are assigned to movement types in MM. Please refer to T-code OMWN and OMWB for proper understanding.

Configuration for Special Purpose Ledger in sap

SAP FI Question:
Why do we use special purpose ledger?
What are the configurations we need to make?

We are using the Special Purpose Ledger for statutory reporting or mangement reporting purpose. It also help us in doing single entry, adjstment posting like income tax deperication.

Steps for cofig.
- Define Table Group
Financial Accounting -> Special Purpose Ledger -> Basic Settings -> Tables -> Definition -> Define Table Group

- Maintain Field Movement
GCF2
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Basic Settings -> Master Data -> Maintain Field Movements

- Maintain Ledger for statutory ledger
GCL2
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Basic Settings -> Master Data -> Maintain Ledgers -> Copy Ledger
Assign Co Code
Assign Activities

- Define Versions
GCW1
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Periodic Processing -> Currency Translation -> Define Versions

- Set Up Exchange Rate Type
OC47
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger ® Periodic Processing -> Currency Translation -> Set Up Exchange Rate Type

- Create Number ranges
GC04
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Actual Posting -> Number Ranges -> Maintain Local Number Ranges

- Create Currency Translation document type
GCBX
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Actual Posting -> Maintain Valid Document Type

- Create Posting period variant
GCP1
IMG Menu Path :
Financial Accounting -> Special Purpose Ledger -> Actual Posting -> Posting Period -> Maintain Local Posting Period

Using the Lock Box Files in SAP FI

I was trying to learn & experiment with using the lock box. However, I don't have any sample files that I can upload and see if it works. Does anyone have any sample bank files and any material that I can use. It would really help me undestand the procedure.

Lockbox is a process provided by a bank where the customer remits his payment to a PO Box at your bank, the bank deposits the check in your account and enters the remittance data from the customer. Then the bank sends the data to you electronically for you to import and apply in SAP-AR.

The structure that the bank uses is usually one of two formats. BAI will provide you the customer information and the check amount but no invoice remittance data. Usually cheaper and works well for a business where customers are paying only one invoice at a time.

BAI-2 offers remittance data but the bank charges more for the service because they have to enter more info.

Look at structures FLB** to see the transfer data.

When the bank sends the customer payment data you use Treasury function FLB2 to import and then process the payments. This process attempts to determine where to apply the payment and will post directly against an invoice, an account to a customer or if it can't even determine the customer it posts into a clearing account (configured) to be resolved.

What is Hold and Parking of Document? in sap

Hold Document: It is for short term and is used when tranaction Dr or Cr is uncertained and generally its is used for external purpose. eg: Advance from potential customer

Parking Document: Its is for longer period generally used for internal purpose. eg: Advance made for employes.

What is the main purpose of this document. Why we are using this one to in FI? How it is useful?

Parking documents is used when we need to get any clarification regarding some account.

We can temporarily park or store this document till we get it cleared or approved.

Then we can post it.

Remember.... parking does not update the accounts....... it just stores the document..... whereas posting will update the accounts....( for example.... the reducing/increasing of the account balances).

The TC for Parking Documents is F-02 -> enter the required details ->go to the menu (at top ) ->Document-> Park.

To post a parked document : FBV0-> go to the menu Document-> Post.

Other TCs used pertaining to Parking of Documents are :

FV50 : Post / Delete : Single Screen Transaction
FBV2 : Change
FBV3 : Display
FBV4 : Change Header
FBV5 : Display Changes
FBV6 : Refuse

Difference between Posting Key and Field Status Variant in sap

What is the use of Field Status Variant. Why it is required?

What is the difference between "Posting Key Variant and Field Status Variant". Why both the things are required to define as both control the fields. What specific fields are controlled this fields.

'Posting Key Variant ' Controls- fields of Posting Key and 'Field Status Variant' controls fields of G/L Account.Fields of G/L Account which are controlled by FSV can see in T.Code OBC4 and Fields of Posting Keys in SPRO-FAGS-Document- Line Item. Both can controls common fields, then SAP applies 'SDRO' rule.

SDRO rule. The fields can be Suppressed, Displayed, Required, Optional.

Posting is key controls
- which type of accounts can be posted to
- whether the line item is debit or credit
- and the field status of the document line item

Where as FSG (group into Field status Variant) controls only the the document line item for that account.

There are only three field status options during document entry:
- Suppressed
- Required
- Optional

If both Posting key and FSV has the same field as Required and optional, system uses the link rules, takes the one which has the highest priority(in this case required).

But in case of Master record Field status which is controlled by Account Group, there are 4 options of field status:
- Suppressed
- Display
- Required
- Optional

Account group defines:
a. length of gl account number
b. no. ranges of the gl account numbers
c. field status of the GL account master data in the company code segment.(which fields to appear when you create a gl account) (to control...double click on your GL account group in Screen transaction code OBD4)

Posting key defines:
a. whether the line item is a debit or credit
b. to which type of account the amount should be posted to(ex: when you use posting key 40, you will be able to post to gl accounts. When you use Posting key 01, you will be only able to post to customer account.
c. document screen layout during posting of a document. (which fields to appear in a document...double click on the posting key and select field status and make the entries as required /optional etc)

Field status group defines:
Document screen layout during posting of a document. (which fields to appear in a document...double click on the field status group and select fields and make the entries as required /optional etc)

LOGIC: you assign field status variant to the company code, FSV is a bundle of field status groups.

ex: in FSG G001 you have made the text as required entry...you assigned the field status group g001 to cash account..so when you use cash account and try to post a document it will definitely prompt you to enter the text (text made as required.)

Both FSG and PK control the same feilds in a document.There is no dominance between FSG and Posting keys..but we should know the allowed combinations....

If text is made required in PK and suppressed in FSG..the system will issue a error msg..Rules for PK...and FSG....is set incorrectly for SGTXT field.

Permissable combinations:

Pk R/S O/S R/o R S O

FSG S/R S/O o/r R S O

Result e SD RD NP NP NP

R = required
s = suppressed
e = error
SD = Suppressed dominates
Rd = required dominates
np = no problem.

Various Postings To The GL Account Postings in sap

During various postings, the GL account postings will be taken place as follows:

For Domestic Procurement of Raw Material
During GR
Material Stock Dr.
GR/IR clearing Cr.
During Excise Invoice Credit
Cenvat Account Dr.
Cenvat Clearing Cr.
During Invoice Verification
Cenvat Clearing Dr.
GR/IR Clearing Dr.
Vendor Payable Cr.

For Domestic proceurement of Capital Goods
During GR
Material Stock Dr.
GR/IR clearing Cr.
During Excise Invoice Credit
Cenvat Account Dr. (50%)
Cenvat On-hold Dr. (50%)
Cenvat Clearing Cr.
During Invoice Verification
Cenvat Clearing Dr.
GR/IR Clearing Dr.
Vendor Payable Cr

Subsequent of Capital Goods
Cenvat Account Dr. (50%)
Cenvat On-hold Cr. (50%)

For Import Procurement of Raw Material
During Customs Duty Clearing invoice
Custom Clearing Dr.
Custom Payable Cr.
During GR
Material Stock Dr.
GR/IR clearing Cr.
During Excise Invoice Credit
Cenvat Account Dr.
Custom Clearing Cr.
During Invoice Verification
GR/IR Clearing Dr.
Vendor Payable Cr.

For Excise Duty Credit of Raw Material without PO

Cenvat Account Dr.
Cenvat Clearing Cr.

For Excise Duty Reversal through Excise JV

Cenvat Clearing Dr.
Cenvat Account Cr.

During Excise Invoice Creation
Cenvat Suspense Account Dr.

Cenvat payable Cr.

For TR6C Challan
PLA Account Dr.
PLA on hold Account Cr.

During Fortnightly Utilization
Cenvat payable Dr.
Cenvat Account Cr.
PLA Account Cr.

Sample Account Assignment in G/L Account in sap

Where do we specify the sample account in FS00. I created a sample account for all expense accounts to use a particular field status group. Now I want to specify that sample account while creating g/l accounts. how do I do that?

We define Sample account at OB15 and the path is SAP Ref:
IMG\Financial Accounting\GLAccounting\GLAccounts\MasterRecords\Preparations\Additional Activities\Sample Accounts

Step1: Maintain List of Rules types

In this step you just create a code for your Sample Account

Create a New Entry
XXXX Sample account for Pleasecontact1 then save

Step 2: Define Data Tranfer Rules FSK2

In this step you define the data tranfer rule i.e., whether it can be editable or only display etc after a Master recored is created with Sample Account.

Selects the fields that you want to transfer (check boxes)and can be changed and can't be changed etc., then save.

Step 3: Assign Company Code to Rule Type

In this step you will assign your sample account to your company code.

Just select your company and select your Sample account and assing then save.

Step 4: Create Sample Account. FSM1

Now create Sample Account same as you create at FS00, then Save.

Now Sample account is created. Now you can find Sample account field in FS00 (if you assign it company code it won't be displayed) enter Sample account no, and press enter all the fiels that you have selected in Step 2 will be copied (transferred) accrding the the rule (checkboxes) you have selected there.

At Tcode FS00

At FS00 you can see/Edit/Create a GL Master Record which is maintained by the Company Code. Where as Sample Account is not GL Master Record but it is a set of settings/rules which are easily available to create a GL Master Record (understand this point clearly) This sample account does not hold your transaction data nor you can edit or view at FS00.

To use your Sample Account:
1. Go to FS00, give a GL account no (other than Sample account no ofcourse). Select create
2. Then check all fields, whether any field is filled like Currency, Open Item Management, etc *for your confirmation* (obviously every field is empty)
3. Now enter Sample Account no in Sample Account field and give Account Group. press Enter. U will get a message that "Data from changed Sample account was accepted", check data.
4. Now chek all fields again. Now u will find some fields filled with values which you have defined in Data Transfer Rules while creating Sample Account.

This is the purpose of Sample account.

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

Settting up the FI Validations in sap

You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.

For e.g. to allow postings from company code 0001 to business area AA only.

GGB0 - To maintain the validations

Validation - Enter a validation name e.g. VBUS

Applicaion Area - SAP module e.g. FI

Calling Point - Dependent upon the application area that is selected.

0001 - Document Header - validate enteries at document header, e.g BKPF table

0002 - Line Items - check line item entris within a document, e.g. BSEG table

0003 - Complete Document - check settings for the whole documents.

e.g. Validation step 001
Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.
If checks failed, the error message number 14 is displayed to stop the transaction.

Prerequisite
$BUKRS = '0001' AND
$GLVOR = 'FI00'

Check
$GSBER = 'AA'

Message
Type E No. 14 - Business Area not allowed for company 0001
Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS
3 - 4

OB28 - Define Validations for Posting

CC CallPnt Validation Description Activtn Level
0001 2 VBUS Business Area Validation 1

Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input

GGB4 - Manage the activation of all validations in the SAP system.

Configuring the Functional Areas in sap fico

It organize your business for cost of sales accounting. It allow you to segregate and classify different types of costs within one expense account. For e.g. a single labour account to determine what amount of labour is spent directly on production as compare to sales or hr.

OKBD - Maintain Functional Area

GGB1 - Maintain Functional Area Subsititions

Subsititions replace and fill in field values behind the scenes without the users knowledge. It is activated at the company code level.

For e.g. Subsitiution BAA Step 001

Prerequisite
FUNCTAREA
$KOSAR = 'M'

Field Constant value
Profit center P1234

If condition is met field Profit center will be replaced with P1234.

GS01 - Creating a set for FUNCTAREA

• Set ID - FUNCTAREA
• Table - ACCIT
• Field Name - HKONT

From Value To Value
10000 12000

OBBZ - Prepare Cost of Sales Accounting

CC CallPnt Validation Description Activtn Level
0001 5 BAA 1

What is sap fico Chart of Accounts

Q. What is chart of accounts?

Chart of accounts is a grouping of GL accounts that used to post transaction from cross modules and FI modules. These can be further used for reporting like Balance Sheet, P&L, and Trial Balance etc...Chart of accounts are usually very specific to an organization and you will not find the same chart of account across two different companies. SAP does give you standard set of accounts that can be used as template but it usually requires detail discussion with accounts so a list can be finalized.

Q. How many types of Chart of Account?

There can be only one primary chart of account per company code in SAP. You can have a different set of chart of account that can be used for Group Account and one for Alternative accounts.

Three types of Chart of Account .

1.Operative Chart of account
It is the COA you are opering for COA defines the Ledger account.

2.Country Chart of Account
You can use this COA for the legal requirement for the country specific.

3.Group of Chart of Account
Supposes for the same company , which uses different COA for their purposes, they can be grouped into Group of Chart of Accounts.

Q. What is alternative chart of accounts?

Alternative chart of accounts is secondary grouping of account that is generally used for statuary reporting. For example you might have a company chart of account but due to statutory nature (for countries like Russia and China to name a few), you have to report your account activity in an account range that has been provided by the company stature. In this case you have a primary chart of account as explained above and alternative chart of account. Postings should always be made in the primary chart of account and in the GL account setup these primary accounts should be associated to alternative chart of accounts. This way updates can be made to both primary and alternative chart simultaneously.

Q. What is group COA?

A group chart of account is way to group your primary accounts. For example from an operation perspective you can have several cash accounts but from a group reporting perspective you might want to group all cash activity under one account. These are usually used for Consolidation reporting. Tips by : Jayaraman

Q. Can we create our own COA from scratch (not copy from a std. version)?

Yes, the procedure is:
IMG side
1) Create Chart of acount (OB13)
2) Create account groups as per ur own list of GL's and give no range (OBD4)
3) Asign Chart of account to ur company code (OB62)
4) Define retained earning account (OB53)

After, for creation in Chart of account segment FSP0
- for Company code segment FSS0
- for central creation FS00

Transport Chart of accounts from Dev to QA in fico

Can anybody tell me the process of moving the chart of accounts from Dev to QA and then from QA to production?

Hamed

You must to create a transport request for chart of accounts. The steps are:

1) t-code OBY9 - create the request for customizing,
- type the name of chart of accounts and
- flag the all parameters. Save and note the request number.

2) t-code SE10 - select from your previous request
- create for chart of accounts the "Customizing task"
- and push "Display object list" icon (shift+F11).
From menu: Object list -> Change/display -> New Entry.
You must complete:
- R3TR TABU SKB1 then,
- double clik on skb1 -> new entry -> Key fields -> and complete:
- Client C 1 your client
- Company code C 2 your company code
- G/L account no. C 3 *
(attention: you must put "*" for G/L account no.)
Save.

3) release the requests - F9 - both requests

4) in the new client - t-code SCC1 complete:
- Source client
- Transport request
- flag on Incl.task request and
- Test run Start immediately.

If the all it is ok you can try without Test run.