Prepare one downloadable document for the reply

you have given and make some improvements and

include missing steps of the sheet.
Of course. Here is an improved and more detailed cheat sheet for SAP FICO configuration,
incorporating missing steps from the provided document. This version is designed to be a
comprehensive, downloadable reference.

SAP S/4HANA FICO Configuration Cheat Sheet

This guide provides a structured overview of the essential configuration steps for SAP S/4HANA
Finance. It includes mnemonic techniques, the purpose of each step, key T-codes and tables,
and highlights the primary differences from SAP ECC.

Core Configuration Mnemonic

To remember the sequence of foundational settings, use this mnemonic: "Elephants From China
Play Drums To Frighten Green Alligators."
This translates to the core setup areas:
Enterprise Structure
Fiscal Year Variant
Chart of Accounts
Posting Period Variant
Document Types & Number Ranges
Tolerance Groups
Field Status Variant
Global Parameters & General Ledger (New) Settings
All Sub-ledgers (AP, AR, AA) & Controlling (CO)

1. Enterprise Structure
Purpose: To build the legal and organizational framework of the business for financial
reporting.
ECC vs. S/4HANA: The basic structure is similar, but S/4HANA introduces new
organizational units and centralizes customer/vendor data into the Business Partner (BP)
model.
 Key
Configuration Step Purpose Key T-Code(s)
Table(s)

Create the highest organizational unit,

Define Company OX15 T880
representing the entire enterprise.

Create the legal entity for which financial

Define Company Code OX02 T001
statements are generated.

Assign Company Code to

Link the legal entity to the parent enterprise. OX16 T001
Company

Define an organizational unit for managing

Define Credit Control Area OB45 T014
customer credit limits and risk.

Assign Company Code to Link the company code to the credit

OB38 T001
Credit Control Area management unit.

Create segments of the company for which

Define Business Area OX03 TGSB
internal P&L statements can be created.

Classify expenditures by function (e.g.,

Define Functional Area Administration, Sales) for cost-of-sales FM_FUNCTION TFMF
accounting.

2. Fiscal Year & Posting Periods

Purpose: To define the financial year and control which periods are open for posting
transactions.
ECC vs. S/4HANA: Functionality is largely the same. S/4HANA's ledger concept allows for
assigning different fiscal year variants to different accounting principles (e.g., leading vs.
non-leading ledgers) more easily[1].
Key T- Key
Configuration Step Purpose
Code(s) Table(s)

Define posting periods (e.g., 12 normal, 4

Maintain Fiscal Year Variant OB29 T009
special) and year-end dates.

Assign Company Code to Fiscal Link your company code to the defined
OB37 T001
Year Variant financial year structure.

Create a variant to manage the opening and

Define Posting Period Variant OBBO T010O
closing of periods.

Assign Posting Period Variant to

Link the variant to your company code. OBBP T001
Company Code

Control which periods are open for posting

Open and Close Posting Periods OB52 T001B
for different account types.
3. Chart of Accounts (COA) & G/L
Purpose: To structure all General Ledger (G/L) accounts used for reporting and posting.
ECC vs. S/4HANA: This is a major area of change. In S/4HANA, FI and CO are merged.
Secondary Cost Elements are created as G/L accounts with a specific "Secondary Costs"
G/L account type[1]. The G/L master record (FS00) is the single source for both[1].
Key T- Key
Configuration Step Purpose
Code(s) Table(s)

Create the master list that contains all G/L account

Define Chart of Accounts OB13 T004
definitions.

Assign Company Code

Link your company code to the COA. OB62 T001
to COA

Group G/L accounts by function (e.g., Assets,

Define Account Groups OBD4 T077S
Liabilities) and control field status.

Define Retained Earnings Specify the P&L account used for carrying forward
OB53 T030
Account net income/loss at year-end.

Create individual master records for each G/L SKA1,

Create G/L Accounts FS00
account. SKB1

4. Document Control
Purpose: To classify business transactions and ensure unique numbering for audit trails.
ECC vs. S/4HANA: The concept is the same, but all financial line items are now stored in the
Universal Journal table (ACDOCA)[1]. S/4HANA also allows for ledger-specific document
types.
Key T- Key
Configuration Step Purpose
Code(s) Table(s)

Classify transactions (e.g., SA for G/L, KR for

Define Document Types OBA7 T003
Vendor Invoice) and assign number ranges.

Define Document Number

Create number intervals for each document type. FBN1 NRIV
Ranges

Set payment difference limits and maximum

OBA0, T043G,
Define Tolerance Groups posting amounts for G/L accounts and
OBA4 T043T
employees.

Create a variant to control which fields are

Define Field Status Variant OBC4 T004V
suppress, optional, or required during data entry.

Assign Company Code to

Link the variant to your company code. OBC5 T001
Field Status Variant
5. Global Parameters & New G/L Settings
Purpose: To maintain central company code settings and activate key S/4HANA
functionalities.
ECC vs. S/4HANA: Activating Document Splitting is a critical step in S/4HANA to enable
real-time, balanced financial statements by characteristics like profit center or segment[1].
Configuration Step Purpose Key T-Code(s) Key Table(s)

Centrally review and maintain key

Enter Global Parameters assignments like COA, Fiscal Year OBY6 T001
Variant, etc.

Set up leading (e.g., 0L for IFRS) and

Define Ledgers for G/L
non-leading ledgers for parallel FINSC_LEDGER FAGL_T_LEDGER
Accounting
accounting.

Assign categories to G/L accounts

Classify G/L Accounts
to tell the system how to split SPRO Path FAGL_T8G32
for Document Splitting
documents.

Turn on the document splitting

Activate Document
functionality for your company SPRO Path V_FAGL_SPLIT_ACT
Splitting
code.

6. Accounts Payable (AP) & Accounts Receivable (AR)

Purpose: To manage all transactions with vendors and customers.
ECC vs. S/4HANA: The mandatory use of the Business Partner (BP) model is the most
significant change. XK01/XD01 are obsolete; the BP transaction is now the single point of entry
for creating and maintaining vendor and customer master data[1].
Key T-
Configuration Step Purpose Key Table(s)
Code(s)

Define Account Groups Group vendors/customers and control OBD3 /

T077K / T077D
(Vendor/Customer) their master data screen layout. OBD2

Create Number Ranges Define number intervals for XKN1 /

-
(Vendor/Customer) vendor/customer accounts. XDN1

Assign Number Ranges to Link the number ranges to the OBAS /

-
Account Groups corresponding account groups. OBAR

Set up number ranges and groupings

Define BP Number Ranges SPRO
for Business Partners, the central NRIV (for BP)
& Groupings Path
master record.

Configure Number Link BP Groupings to

SPRO
Assignment (BP to Vendor/Customer Account Groups to CVI_VEND_ACCGRP
Path
Vendor/Customer) enable synchronization (CVI).

Define Tolerances Set limits for payment differences and

OBA3 T043A
(Vendor/Customer) clearing.
 Key T-
Configuration Step Purpose Key Table(s)
Code(s)

Define Alternative Recon.

Link the normal reconciliation account OBYR /
Account for Down T074
to a special G/L account for advances. OBXR
Payments

Create the master record using the BP

transaction, assigning roles like FI BUT000 (General),
Create BP Master Data BP
Vendor (FLVN00) or FI Customer LFA1/KNA1 (Views)
(FLCU00)[1].

7. House Banks & Automatic Payment Program (APP)

Purpose: To manage bank accounts and automate the payment process for vendors.
ECC vs. S/4HANA: Bank account management is no longer a pure configuration activity. In
S/4HANA, it is handled via the Manage Bank Accounts Fiori app (or NWBC), treating bank
accounts as master data[1]. The classic FI12 is still available but not the recommended
approach.
Key
Configuration Step Purpose Key T-Code(s)
Table(s)

Define house banks and create accounts. In FI12_HBANK

Create House Bank & T012,
S/4HANA, use the Manage Bank Accounts (ECC), Fiori App
Bank Accounts T012K
Fiori App[1]. (S/4)

Define number ranges for checks issued

Create Check Lots FCHI T003N
from a bank account.

Configure global settings for the payment

Set Up All Company
program, including sending/paying FBZP T042
Codes for APP
company codes.

Set Up Paying
Define minimum payment amounts and
Company Codes for FBZP T042E
configure payment advice forms.
APP

Set Up Payment Define payment methods (e.g., Check, Wire)

FBZP T042Z
Methods per Country and their properties.

Set Up Payment
Assign payment methods to your company
Methods per Company FBZP T042D
code and set amount limits.
Code

Set Up Bank Rank house banks by payment method and T042B,

FBZP
Determination for APP currency to determine the payment source. T042I

Execute Automatic Create proposals, execute payments, and

F110 -
Payment Run print checks/remittances.
8. Controlling (CO)
Purpose: To set up the structures for internal management accounting, cost tracking, and
profitability analysis.
ECC vs. S/4HANA: The barrier between FI and CO is removed. All CO postings generate a
single journal entry in ACDOCA, ensuring real-time reconciliation. A Controlling Area can now
be assigned to multiple company codes with different fiscal year variants if needed[1].
Key T- Key
Configuration Step Purpose
Code(s) Table(s)

Define the primary organizational unit for

Maintain Controlling Area Controlling, linked to the COA and Fiscal Year OKKP TKA01
Variant.

Assign Company Code(s) Link one or more company codes to the

OKKP TKA02
to Controlling Area controlling area.

Activate the specific CO components you will use

Activate Components OKKP TKA01
(e.g., Cost Centers, Profit Center Accounting).

Maintain Number Ranges Define number ranges for different CO transaction

KANK NRIV
for CO Documents types.

Define versions for planning, actuals, and analysis

Maintain Versions OKEQ TKA09
(e.g., Version 0 for plan/actual).