SAP S4HANA Configuration and End User Guide
SAP S4HANA Configuration and End User Guide
Content Tcodes
No
1 Enterprise Structure
Definition
1.1 Define Company OX15
1.2 Define Company Code OX02
1.3 Define credit control area OB45
1.4 Define Business Areas OX03
1.5 Maintain Consolidated Business Area OCC1
1.6 Maintain financial management area OF01
1.7 Define segment
Assignment
1.8 Assignment of Company code to Company OX16
1.9 Assign credit control area to company code OB38
1.10 Assign Business Area To Consolidated Business Area OBB6
1.11 Assign company code to financial management area OF18
6 Business partner
6.1 Activation switch for Function
6.2 Define Account Groups with Screen Layout (Customers) OBD2
6.3 Create Number Ranges for Customer Accounts XDN1
6.4 Assign Number Ranges to Customer Account Groups OBAR
6.5 Define Account Groups with Screen Layout (Vendors) OBD3
6.6 Create Number Ranges for Vendor Accounts XKN1
6.7 Assign Number Ranges to Vendor Account Groups OBAS
6.8 Define Tolerance (Vendors/Customer) OBA3
6.9 Define Number Ranges (in Business Partner) BUCF
6.10 Define Groupings and Assign Number Ranges
6.11 Define BP Roles
6.12 Define BP Role for Direction Customer to BP
6.13 Define Number Assignment for Direction BP to Customer
6.14 Define BP Role for Direction Vendor to BP
6.15 Define Number Assignment for Direction BP to Vendor
7 Accounts Payable
7.1 Create GL Accounts FS00
7.2 Create Business Partner BP
7.3 Purchase invoice posting F-43/FB60
7.4 View vendor account transactions FBL1N
7.5 Outgoing payment with clearing F-53
8 Vendor down payments
8.1 Create GL Account for advance to vendor under Asset FS00
8.2 Define alternative Reconciliation Account for down payment OBYR
8.3 Advance payment posting F-48
8.4 Check vendor down payment FBL1N
8.5 Purchase invoice posting FB60
8.6 Check vendor down payment FBL1N
8.7 Down payment clearing F-54
8.8 Clearing of normal items F-44
14 House Bank
14.1 Create G.L Account FS00
14.2 Define house bank FI12
14.3 Creation of check lots FCHI
14.4 Purchase invoice posting FB60
14.5 Outgoing payment with clearing F-53
14.6 Creation of manual check FCH5
14.7 Display check register FCHN
14.8 Check encashment date updating FCH6
14.9 See check register FCHN
14.10 Unissued checks cancellation FCH3
16 Cash journal
16.1 GL creation for cash journal FS00
16.2 Define document type OBA7
16.3 Define number range for cash journal document FBCJC1
16.4 Setup cash journal FBCJC0
16.5 Create, change, delete business transaction FBCJC
16.6 Setup print parameters for cash journal FBCJC3
16.7 Posting to Cash journal FBCJ
18 Withholding Tax
18.1 Check withholding tax countries
18.2 Define official withholding tax keys
18.3 Define reasons for exemption
18.4 Define withholding tax type for invoice posting
18.5 Define withholding tax for payment
18.6 Check recipient types
18.7 Define withholding tax code
18.8 Assign withholding tax types to company
18.9 Activate extended withholding tax
18.10 Create G/L account
18.11 Define automatic posting
18.12 Maintain Company code settings
18.13 Assign withholding tax types to vendor
18.14 Post purchase invoice
Enterprise Structure
The Enterprise Structure in SAP FICO refers to the organizational hierarchy that represents a
company's financial and business operations within the SAP system. It consists of different
organizational units that help in structuring and managing financial transactions, reporting, and
business processes efficiently.
Select favourites
then right
1. Define Company
Tcode: OX15
Execute.
Click on new entries and enter below detail.
Save it.
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:
on new entries
Save it.
4. Maintain consolidation business area
Tcode: OCC1
Path:
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:
Execute.
Save it.
One time back
Execute.
New
entires.
A Segment in SAP FICO is an organizational unit introduced to meet the International Financial
Reporting Standards (IFRS) and Generally Accepted Accounting Principles (GAAP) requirements
for Segment Reporting. It allows businesses to provide financial reports based on different
segments of operations, such as geographical areas, product lines, or business divisions.
Segment reporting helps stakeholders analyze the financial performance of different parts of
the organization separately, improving transparency and decision-making.
Tcode:
Path: Same as above.
New Entries
Tcode: OX16
Path:
Save it.
2. Assign Company code to credit control area.
Tcode:
Path:
Tcode: OB38
Path:
Save it.
Financial accounting global settings
1. Maintain fiscal year variant
A Fiscal Year Variant (FYV) in SAP FICO defines the financial year structure, including periods and
special periods, used for financial reporting and posting transactions. It determines how SAP divides
the fiscal year into posting periods.
• A fiscal year can have 12 normal periods (monthly) or fewer (e.g., quarterly).
• SAP also allows 4 special periods for year-end adjustments.
• Calendar Year Variant: The fiscal year follows the calendar year (January–December). Example: K4
(Standard SAP Variant).
• Non-Calendar Year Variant: The fiscal year differs from the calendar year, e.g., April–March (used in
India), July–June, etc. Example: V3 (April–March).
• Shortened Fiscal Year: Used when a company changes its fiscal year, leading to a temporary fiscal year
with fewer periods.
Tcode: OB29
Path:
Execute.
Click on new entries.
Select and double click on Periods.
Select new entries.
Save it.
3. Define posting period variant
A Posting Period Variant (PPV) in SAP controls which posting periods are open for financial
transactions. It ensures that postings happen only in the allowed periods, preventing accidental
postings in closed periods.
SAP allows controlling posting periods separately for different account types:
• A – Assets
• D – Customers (Debtors)
• K – Vendors (Creditors)
• M – Materials
• S – General Ledger (G/L)
Tcode: OBBO
Path:
New entries
Execute
Give company code
Press enter
Click on new entries
Create number ranges for documents. For each number range you specify (among other things):
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 SA and double click. number range
here for same
no.
1. Check
number
3. Enter
company code
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:
Execute.
2.Click on
copy as
1.Select 0001
3. Change FStV and
Name
Let’s suppose you want to make some field mandatory, display, hide, optional in general data. Then
follow following steps.
Double click on field status group
Execute.
Search Company Code and assign Field Status Variant.
Purpose:
• Standardizes accounting processes across the organization.
• Helps in financial reporting and compliance.
• Ensures consistency in transaction postings.
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.
2. Assign company code to chart of accounts
Tcode: OB62
Path: Same as above.
For example:
Liabilities: 100000 - 199999
Assets: 200000 - 299999
Income: 300000 - 399999
Expenses: 400000 – 499999
Tcode: OBD4
Tcode: OB53
Path:
Execute