SAP FICO – Configuration and end user guide
SAP FICO – Configuration and end user guide
Document Prepared By
Rajesh Sethi
Part 1
Sr. Content Tcodes
No
1 Enterprise Structure
1.1 Define Company OX15
1.2 Define Company Code OX02
1.3 Define Business Areas OX03
1.4 Maintain Consolidated Business Area OCC1
1.5 Define credit control area OB45
1.6 Assignment of Company code to Company OX16
1.7 Assign Business Area To Consolidated Business Area OBB6
1.8 Assign credit control area to company code OB38
7 Account Receivable
7.1 Define account group with screen layout (customer) OBD2
7.2 Create number ranges for customer account group XDN1
7.3 Assign number ranges to customer account group OBAR
7.4 Customer related documents OBA7
7.5 Tolerance group for customer OBA3
7.6 Creation of G/L Account FS00
7.7 Create customer master FD01
7.8 Post Customer invoice F-22
7.9 Check customer balance FBL5N
7.10 Incoming payment posting F-28
8 Advance payment from customer
8.1 Create G/L for advance from customer FS00
8.2 Define recon a/c for customer down payments OBXR
8.3 Down payment F-29
8.4 Raise invoice F-22
8.5 Down payment clearing F-39
8.6 Clear open item F-32
9 Dunning Procedure
9.1 Define dunning area OB61
9.2 Define dunning procedure FBMP
9.3 Assign dunning procedure to customer master FD02
9.4 Sale invoice posting F-22
9.5 Run dunning F150
10 House Bank
10.1 Create G.L Account FS00
10.2 Define house bank FI12
10.3 Creation of check lots FCHI
10.4 Purchase invoice posting FB60
10.5 Outgoing payment with clearing F-53
10.6 Creation of manual check FCH5
10.7 Display check resister FCHN
10.8 Check encashment date updating FCH6
10.9 Go and see check register FCHN
10.10 Unissued checks cancellation FCH3
12 Cash Journal
12.1 GL creation for cash journal FS00
12.2 Define document type
12.3 Define number range for cash journal document FBCJC1
12.4 setup cash journal FBCJC0
12.5 Create, change, delete business transaction FBCJC
12.6 Setup print parameter for cash journal FBCJC3
12.7 Posting to Cash journal FBCJ
13 Withholding Tax
13.1 Check withholding tax countries
13.2 Define official withholding tax keys
13.3 Define reasons for exemption
13.4 Define withholding tax type for invoice posting
13.5 Define withholding tax for payment
13.6 Check recipient types
13.7 Define withholding tax code
13.8 Assign withholding tax types to company
13.9 Activate extended withholding tax
13.10 Create G/L account
13.11 Define automatic posting
13.12 Maintain Company code settings
13.13 Assign withholding tax types to vendor
13.14 Post purchase invoice
15 Asset Accounting
15.1 Assign tax code for non-taxable transactions OBCL
15.2 Copy reference Chart of Depreciation /Depreciation Area EC08
15.3 Assign Chart of Depreciation to Company code OAOB
15.4 Specify account determination
15.5 Create screen layout rule
15.6 Define number range intervals
15.7 Define asset classes
15.8 Create G/L account FS00
15.9 Assignment of accounts for automatic postings AO90
15.10 Specify document type for posting of deprecation
15.11 Specify intervals and posting rules
15.12 Specify rounding for net book value and /or deprecation
15.13 Define screen layout for asset master data
15.14 Define screen layout for asset deprecation areas
15.15 Deprecation keys creation (Rate+ Methods)
15.16 Define multi-level methods AFAMS
15.17 Maintain period control methods
15.18 Maintain deprecation key
15.19 Determine depreciation areas at asset class
15.20 Create of main asset master AS01
15.21 Sub asset creation AS11
15.22 Main asset purchase posting/asset acquisition F-90
15.23 Report to view sub asset wise, year wise values AW01N
15.24 Asset transfer within company code ABUMN
15.25 Asset retirement with customer F-92
15.26 Asset Scraping ABAVN
15.27 Depreciation run AFAB
16 FI-MM Integration
16.1 Create plant OX10
16.2 Maintain storage location OX09
16.3 Maintain purchasing org OX08
16.4 Create purchasing group OME4
16.5 Assign plant to company code OX18
16.6 Assign purchasing org to plant OX17
16.7 Define valuation level OX14
16.8 Define valuation control OMWM
16.9 Group together valuation area OMWD
16.10 Define Valuation classes OMSK
16.11 Define material type OMS2
16.12 Maintain Company Code for Material Management OMSY
16.13 Maintain default values for tax codes OMR2
16.14 Maintain vendor specific tolerances OMRX
16.15 Create inventory a/c under asset FS00
16.16 Create GR/IR a/c under liability FS00
16.17 Automatic posting OBYC
16.18 Create material MM01
16.19 Create vendor XK01
16.20 Create Purchase Requisition ME51N
16.21 Create Purchase Order ME21N
16.22 Goods receipt MIGO
16.23 Invoice Verification MIRO
16.24 Vendor payment posting F-53
20 Internal Order
20.1 Activate Order management OKKP
20.2 Define Order type KOT2
20.3 Maintain number range for orders KONK
20.4 Make Internal order required OBC4
20.5 Create internal order group KOH1
20.6 Create internal order KO04
20.7 Transaction posting FB50
Organizational units in financial accounting
Sap define the enterprise structure as the organizational units that together represent your company’s
business units and divisions. Without enterprise structure, you couldn’t integrate and configure your
program. You could not run SAP FI at all. That why first we need to create enterprise structure in SAP
system.
So let’s see how can we configure enterprise structure.
1. Define Company
Tcode: OX15
Path:
Execute.
Click on new entries and enter below detail.
Save it.
You will get one pop up window.
Click on create
Request (F8)
Click here to
save.
Click here to
save in your
request
Note: Customizing request or Transport request are used to transfer configuration from one client to
another. For example development client to quality assurance client or quality assurance client to
production client.
2. Define company code
Company code: Smallest organizational unit of external accounting for which a complete, self-
contained set of accounts can be created. This includes the entry of all transactions that must be posted
and the creation of all items for legal individual financial statements, such as the balance sheet and the
profit and loss statement.
The company code is an organizational unit used in accounting. It is used to structure the business
organization from a financial accounting perspective. The company code is an organizational unit used
in accounting.
Tcode: OX02
Path:
Tcode: OX03
Path:
Save it.
4. Maintain consolidation business area
A consolidation business areais an accounting organizational unit that represents a central business
segment within a business organization and that has a balance sheet which can be included in business
area consolidation. In the SAP system, you execute the functions for consolidating business areas
based on consolidation business areas.
Tcode: OCC1
Path:
Execute
New entries.
Save it.
5. Define credit control area.
Define your credit control areas. The credit control areais an organizational unit that specifies and
checks a credit limit for customers.
A credit control area can include one or more company codes. It is not possible to assign a company
code to more than one control area. Within a credit control area, the credit limits must be specified in
the same currency.
Tcode: OB45
Path:
Save it.
One time back
Execute.
New entires.
Tcode: OX16
Path:
Save it.
2. Assign Company code to credit control area.
Tcode:
Path:
Execute.
Search company code and assign credit control area.
Save it.
Tcode: OB38
Path:
Save it.
1. Maintain fiscal year variant
An accounting period is also known as the fiscal year which usually runs for 12 months (each month
= one period) with your company publishing a financial statement for each fiscal year as well as taking
stock inventory. Each period within a fiscal year is known as a posting period. When you post
transactions in the SAP system each transaction is assigned to a particular posting period (made up of
month and year) and the transaction figures are updated for that period. SAP identifies documents
using document type, fiscal year and posting period. It uses Fiscal Year Variants (FYV) to manage
fiscal years and posting periods variants to open or close posting periods.
There is also a concept called special period to manage activities such as period-end closing (audit or
tax adjustments), a fiscal year can have fewer than 12 months known as a shortened fiscal year, there
are two definitions for a fiscal year.
Calendar Fiscal Year: There are 12 posting periods that correspond to the 12 calendar months,
with the first posting period starting on 1st January. Normally you use the calendar as the fiscal year
which means the start and end date of each posting period is the same as that of the corresponding
calendar month. Depending on posting date the system will assign the correct period to a transaction.
Non-Calendar Fiscal Year: a fiscal year that does not corresponding to a calendar year is known as
a non-calendar fiscal year, and thus such posting periods may or may not match to the calendar months.
Its possible that a fiscal year has fewer then 12 posting periods (shortened fiscal year) which means
you have to define the number of posting periods.
Tcode: OB29
Path:
Execute.
Click on new entries.
Save it.
Or you can copy V3 Fiscal year variant and change name.
2. Assign company code to fiscal year variant.
When we assign fiscal year variant to company code then our company’s financial year will be 1st
April to 31st March.
Tcode:OB37
Path:
Save it.
3. Define posting period variant
We have already defined fiscal year variant and assign it to our company code, it is time to define
Posting period variant. Posting period variant is used to control which accounting period is open for
posting. This is an important control tool for every organization which has monthly closing. Usually
every posting period is assigned to one company code, but you could assign one posting variant to
many company codes. In this way you will control all the entities in once which has pros and cons.
Despite the strict dates you agree with other departments in your organization there will always be a
cases where for some operation, period should be open. So you should very carefully consider whether
you are going to define one posting period for several company codes or you will have one for each.
Tcode: OBBO
Path:
New entries
Create number ranges for documents. For each number range you specify (among other things):
•A number interval from which document numbers are selected.
•The type of number assignment (internal or external) you assign one or more.
The number range becomes effective via the document type specified in document entry and posting.
You can use one number range for several document types. This means you can differentiate
documents by document type.
Tcode: OBA7
Path:
2. Maintain
Search Document type number range
here for same
no.
1. Check
number
3. Enter
company code
5. Click here
6. Maintain current
year and number
range interval
Follow same steps and maintain number ranges for given document types
7. Define posting keys
Posting key is a two-digit numeric key. It is defined to control the entry of document line items in a
financial accounting transaction. Posting key specifies the line item is either debit or credit entry,
account type and the screen layout of line items. Special posting keys are used for posting special
general ledger transactions.
The system uses the posting key, special G/L indicator to determine the alternative settlement
account. The posting key determines
1. Account type
2. Debit/Credit posting
3. Layout of entry
Tcode: OB41
Path:
Double click on posting keys
In this section I will cover both Field Status Groups (FSG) and Field Status Variants (FSV), FSG
control the additional account assignments and other fields that can be posted at the line-item level for
a G/L account, it is important to remember that field status of your account must mesh with the field
status group of the posting key and/or Material Management (MM) movement types. A common
posting error occurs when a field in the G/L field status group and the same field in the MM movement
type field is suppressed. It is a good idea to keep as many fields as possible optional and to make only
the most important fields as required or suppressed.
Tcode: OBC4
Path:
2. Click on
copy as
1. Select 0001 or
1000
+91 9623241316
2. Click on Field
Status.
Let’s suppose you want to make some field mandatory, display, hide, optional in general data. Then
follow following steps.
Tcode: OB13
Path:
Execute
Click on new entry and maintain following details.
Under status deselect blocked check box (do not select blocked
check box)
Select save button or Ctrl+s
Select your request and press enter to save in your request.
Tcode: OB53
Path:
Tolerance Group" for G/L (General Ledger) accounts is a mechanism used to control the
maximum permissible amounts for posting transactions to specific G/L accounts within the
framework of the organization's financial control policies. Tolerance groups help ensure that
financial transactions fall within predefined limits and prevent unauthorized or erroneous
postings that might have a significant impact on financial statements.
Tcode: OBA0
Path:
+91 9623241316
Tcode: OBA4
Path:
Select new entries button
Save it.
7. Enter global parameters
Tcode: OBY6
Path:
Save it.
8. Define calculation procedure
Calculation Procedure is a set of rules and formulas that determine how certain values are
calculated or derived for specific purposes, such as tax calculation or cost allocation.
Calculation procedures are used to automate complex calculations and ensure consistency
in various financial and controlling processes.
Double click on define procedure. Then select TAXAR and click on copy as.
Click on centrally
To create new account click on Create then take GL account number and company code.
GL Master data
Type/Description
Control Data
Create/Bank/Interest
+91 9623241316
2. Equity Share
Type/Description
Control data
Create/bank/interest
3. Cash account
Type/Description
Control data
Create/bank/interest
4. Salaries accounts
Type/Description
Control data
Create/bank/interest
5. Rent account
Type/Description
Control data
Create/bank/interest
6. Outstanding
Type/Description
Control data
Create/bank/interest
11. General ledger posting
Tcode: F-02
Path:
+91 9623241316
Step 2:
Press enter
Step 3:
Now select documents from menu bar then click on simulate
Save it.
12. Change documents
Tcode: FB02
Path:
If you want to make any changes in documents. Then you can follow above path or Tcode.
Take whatever the document you want to change and make changes
13. Display documents
Tcode: FB03
Path:
Take document number, company code and fiscal year. Then press enter.
14. Display accounts balance
Tcode: FS10N
Path:
Give G/L account, Company code, Fiscal year, then click on execute (F8).
And here you can see accounts balance.
15. Documents parking
Tcode: FB65
Path:
Select Documents – Park documents
Display park documents
Tcode: FBV3
Path:
3. Click on display
1. Select doc
number.
If you want to make any changes then double click on a/c number and save or post it.
17. Sample documents
Select insert interval and maintain number range for X2 then save it.
Step 2: Creation of sample documents
Tcode: F-01
Path:
+91 9623241316
Press enter.
Again enter and if you want to make any change double click on a/c number make whatever
the changes you want to make then save it.
18. Document Reversal
Individual reversal
Tcode: FB08
Path:
Mass reversal
Tcode: F.80
Path:
Take company code and fiscal year, then click on execute.
+91 9623241316
Chapter 4: Accounts Payable
1 Creation of vendor accounts groups(OBD3)
2 Create number range for vendors account (XKN1)
3 Assign number range to vendor account groups(OBAS)
4 Define tolerance group for vendor(OBA3)
5 Document types and no. ranges (OBA7)
6 Create GL Accounts for Material under asset(FS00)
7 Create GL Accounts for sundry creditors under liability
8 Creation of vendor master(FK01)
9 Purchase invoice posting(F-43)
10 View vendor account transactions(FBL1N)
11 Outgoing payment with clearing(F-53)
AP- Accouts payable
1. Define accounts group with screen layout(Vendor)
Tcode: OBD3
Path:
Click on intervals.
Click on interval
Type/Description
Control data
Create/Bank/Interest
Save it.
7. Create GL Accounts for Sundry creditors.
Tcode: FS00
Path: Same as above.
Save it.
8. Create Vendor master data
Tcode: FK01
Path:
Press enter.
Save it.
You will get following message: Vendor 0000023700 was created in company code IBM3.
9. Invoice posting
Tcode: F-43
Path:
Select document overview.
Save it.
Chapter 5: Advance payments to vendors (down payments to vendors)
1 Create GL Account for advance to vendor under Asset(FS00)
2 Link between sundry creditors and advance to vendors(OBYR)
3 Advance payment posting(F-48)
4 Go and see the vendor account transaction (FBL1N)
5 Purchase invoice posting (F-43)
6 Go and see the vendor account
7 Transfer of advance from special GL to normal by clearing special GL items (F-54)
8 Clearing of normal items(F-44).
Vendors down payments
In company when we purchase some material or services from vendor at that time vendor
send us bill of purchased material/service. After that we have to verify invoice and release
vendor payment.
In some scenario it may be necessary to do advance payment (prepayment).
In simple world advance payment means a payment which is made to vendor/supplier before
receiving goods/services.
In this document detail configuration and end user transaction are given.
Press Enter.
Select Control Data Tab
Select Create/Bank/Interest
Press Enter and Save it.
2. Link between sundry creditors and advance to vendors
Tcode: OBYR
Path:
+91 9623241316
Save it.
3. Advance payment posting
Tcode: F-48
Path:
Press Enter
Select Document Overview
Save it.
4. Go and see the vendor account transaction
Tcode: FBL1N
Path:
Execute (F8)
5. Vendor invoice posting
Tcode: F-43
Press Enter
Press Enter
Select Document Overview
Press Enter.
Double click on available balance.
Save it.
Tcode: FBL1N
8. Clearing of normal items.
Tcode: F-44
Path: Same as above.
Press Enter.
➢ Net 30, Net 45, Net 60: These terms mean that the payment is due 30,45 or 60 days
from the invoice date, respectively.
➢ 3/14, 2/30, Net 45: This indicate that the buyer can take a 3% discount if they pay the
invoice within 14 days, if they pay the invoice between 15-30 days discount will be 2%,
But the full payment is due in 45 days.
1. Crete GL account
Tcode:
Save it.
5. Purchase invoice posting.
Tcode: F-43
Give below details.
Press enter
Press enter
Press enter.
Save it.
6. CHECK VENDOR BALANCE
Tcode: FBL1N
7. Vendor payment posting
Tcode: F-53
Press enter
Save it.
8. Check GL balance
Tcode: FAGLL03
Give GL A/c number and company code.
Select execute.
Chapter 7: Account Receivable
1 Define account group with screen layout (customer) (OBD2)
2 Create number ranges for customer account group(XDN1)
3 Assign number ranges to customer account group(OBAR)
4 Customer related documents (OBA7)
5 Tolerance group for customer (OBA3)
6 Creation of G/L Account (FS00)
7 Create customer master (FD01)
8 Post Customer invoice (F-22)
9 Check customer balance (FBL5N)
10 Incoming payment posting ( F-28)
Accounts Payable
Press enter
Enter once again to Save in your request.
2. Create number ranges for customer account group
Tcode: XDN1
Path:
Press enter
Press enter
Select company code data button.
Press enter.
Press enter.
Press enter.
Select document overview.
Save it.
Select Execute(F8).
11. Incoming payment posting.
Tcode: F-28
Path:
Press Enter
Select document overview.
The down payment process is a fundamental financial transaction that allows businesses to
receive advance payments from their customers before the actual delivery of goods or
services. This process serves to secure a commitment from customer and is especially
common in industries with long sales cycle or high value transaction
The down payment process in SAP FICO typically begins with the creation of a down
payment request, where the customer expresses their intent to make an advance payment.
Once approved, a down payment invoice is generated, confirming the commitment and
recording the financial transaction. This down payment invoice is posted to the customer's
account and a dedicated clearing account in SAP.
When the goods or services are delivered as per the agreed terms, the advance payment is
cleared against the open invoice using the down payment clearing function in SAP. This
result in the actual revenue recognition and appropriate financial posting.
The down payment process in SAP FICO helps maintain accurate accounting records,
prevents revenue leakage, and ensures that both customers and businesses have clear
visibility of the financial commitment. It's a crucial aspect of financial management, enabling
businesses to streamline their operations and maintain transparency in their financial
dealings. The process can be customized to suit various business requirements and can
involve multiple documents and approval steps based on the complexity of the transaction
and specific industry needs.
Business Scenario:
Let’s consider a scenario in which a company, ABC pvt ltd has received a down payment from
customer, XYZ ltd for the purchase of some material or service. The total of the material or
service is 10,000, XYZ ltd is agree to pay 50% or 100% payment in advance.
Lest see how to customise SAP for Down Payment and enter transactions.
1. G/L for advance from customer.
Tcode: FS00
Path:
Double click on A.
Give chart of account
Press enter
Save it.
3. Down payment
Tcode: F-29
Path:
Press enter
Select document overview
Tcode: F-22
Path:
Tcode: F-39
Path:
Give details
Press enter
Double click on available Amount
Path:
Press enter
1. Introduction
2. Define dunning area (OB61)
3. Define Dunning Procedure (FBMP)
4. Sales invoice posting (F-22)
5. Assign dunning procedure to customer (FD02)
6. Run dunning (F150)
Introduction
Dunning procedure is a process used to remind customers about their outstanding invoices
and to encourage them to make payments. It involves a series of steps and actions to
manage overdue accounts. Here's a detailed explanation of the dunning procedure in SAP
FICO:
1. Dunning Levels:
- The dunning procedure begins by defining different dunning levels. Each level corresponds
to a specific degree of payment overdue. For example, Level 1 might be for invoices overdue
by 7 days, Level 2 for invoices overdue by 14 days, and so on.
2. Dunning Areas:
- Dunning areas are used to classify customers or vendors into different categories based on
specific criteria, such as geography or business unit. This allows for more customized
dunning processes.
3. Dunning Keys:
- Dunning keys are used to control the dunning process. They determine the intervals
between dunning runs, the dunning program to be executed, and other parameters.
Dunning keys are assigned to customer or vendor master records.
4. Dunning Programs:
- SAP provides standard dunning programs that you can execute to initiate the dunning
process. You can also create custom dunning programs if needed.
5. Dunning Notices:
- Dunning notices are the reminders sent to customers or vendors with overdue invoices.
These notices can be generated in various formats, including letters, emails, or faxes.
6. Dunning Run:
- The dunning run is the actual execution of the dunning program. It identifies overdue
items, selects the appropriate dunning level for each item, and creates dunning notices for
customers or vendors.
+91 9623241316
7. Dunning Proposal:
- Before executing a dunning run, SAP FICO allows you to generate a dunning proposal. This
is a simulation of the dunning run, which shows the items that will be dunned at each level.
8. Dunning History:
- SAP FICO maintains a dunning history that tracks all dunning activities for each customer or
vendor, helping you keep a record of communication and payment reminders.
1. Define dunning area.
Tcode: OB61
Press enter
Save it.
4. Sales invoice.
Tcode: F-22
Select Parameter
Select Additional Log
Save it.
Select Status
Select schedule
Click on schedule
Press enter-enter
Select sample printout.
Start immediate
Press enter-enter
Press enter
Select new entries
Save it.
Double click on bank account
Save it.
3. Creation of check lots.
Tcode: FCHI
Path:
Press enter
Press enter
Select document overview.
Save it.
5. Outgoing payment with clearing.
Tcode: F-53
Give below details.
Press enter
Save it
Document 4027 was posted in company code IBM3.
6. Creation of manual check
Tcode: FCH5
Path:
Press enter
Save it.
Press enter
Give encashment date.
Select execute
Some time while writing check we commit mistake before issuing to party – we cancel check
Select void.
Checks 1020 to 1020 have been voided.
11. How to create void reason code
Tcode: FCHV
Path :
Save it.