SAP FICO · COMPLETE TRAINING

SAP FICO — Complete Training Material

End-to-end training across FI, CO, Bank Accounting, In-House Banking, and Material Ledger — with meanings, worked examples, journal entries, configuration, common errors, and interview preparation.

0 The Whole Picture — How SAP FICO Fits Together

Before diving into any single topic, understand how every piece of FICO connects. This is the mental map that every SAP FICO consultant carries.

The Big Picture

One-sentence summary

SAP FICO records every financial event of a business — where money came from, where it went, what it cost, what it earned — and turns that into statutory reports (FI) and management insight (CO).

Module Map — How Everything Connects

FI · Financial Accounting
Statutory · Legal entity view

BL — Bank

IHB — In-House Bank

CO · Controlling
Management · Cost object view

CO-CC

CO-PC

CO-PP

CO-PA

PCA

ML — Material Ledger

Logistics Modules
Source of many FI/CO postings

WM / EWM

Outputs
What stakeholders see

Balance Sheet

P&L

Cash Flow

Cost Reports

Profitability

Segment

The Complete Transaction Journey

Follow a single business transaction — a customer order — through every module:

Stage	Module	What Happens	FI / CO Impact
1	SD	Customer places order	No posting yet
2	MM / PP	Materials procured / produced	GR/IR, ML postings, production order debits
3	SD	Goods issued to customer	Dr COGS / Cr Inventory (via ML)
4	SD	Billing document created	Dr Customer / Cr Revenue / Cr GST
5	CO-PA	Profitability segment updated	CE1xxxx line items
6	BL	Bank statement — payment received	Dr Bank / Cr Customer
7	IHB	Intercompany netting (if group)	Dr IHC / Cr Customer
8	CO-CC	Cost center assessment	Secondary allocation
9	ML	Actual costing run	Price differences to inventory / COGS
10	FI Close	Month-end adjustments	Accruals, FX, depreciation

The Two Lenses

FI Lens — Legal Entity

"Did we make a profit? How much tax do we owe? What's our balance sheet?" — used by auditors, tax authorities, shareholders, regulators.

CO Lens — Cost Object

"Which product is most profitable? Which department overspent? Should we make or buy?" — used by managers, controllers, CFO.

Reconciliation

FI and CO must always reconcile. In S/4HANA, this is automatic because everything is stored in ACDOCA.

Integration

Every logistics event (goods movement, billing) creates an FI posting. Every FI posting with a cost object creates a CO posting.

Recommended Learning Order

Enterprise Structure — where data lives
GL & Core FI — how postings work
AP, AR, AA — the three core subledgers
Bank Accounting — money in / money out
In-House Banking — group-level treasury (only relevant in large groups)
Controlling — cost & profitability management
Product Costing & CO-PC — cost of goods manufactured
Material Ledger — actual costing & price differences
Integration & S/4HANA — how it all hangs together
Close & Troubleshooting — the monthly cycle
Interview Prep — scenarios and case studies

1 SAP & Enterprise Structure

The organizational units that define how data, documents, and reports are structured.

Meaning

What is it?

Enterprise structure defines the legal, organizational, and management boundaries within which business transactions are recorded. Every document you post carries a piece of this structure — Company Code, Plant, Cost Center, Profit Center.

Key Organizational Units

Client (Mandant)

Top-level container. Self-contained commercial unit with its own master data.

Company Code (BUKRS)

Independent legal entity. Balance sheet and P&L produced here.

Controlling Area (KOKRS)

Management accounting boundary. Multiple company codes can share one.

Business Area (GSBER)

Cross-company-code segment for internal reporting.

Functional Area (FKBER)

Classifies expenses by function — production, sales, admin, R&D.

Plant (WERKS)

Operating facility within a company code. Central to MM, PP, ML.

Cost Center (KOSTL)

Where overhead costs are incurred. Departmental reporting.

Profit Center (PRCTR)

Internal profitability unit. Produces internal P&L and balance sheet.

Segment (SEGMENT)

Reporting segment for IFRS 8 / Ind AS 108.

House Bank (BANKL)

Bank relationship for a company code — used in Bank Accounting (BL).

IHC Company Code

Dedicated company code for In-House Cash Centre.

Valuation Area (BWKEY)

Organizational unit for material valuation — usually a plant. Central to ML.

Real-World Example

Scenario — ABC Group

Company: ABC Manufacturing Group, with operations in India, Singapore, Germany.

Client 100
Company Codes: IN01 (India), SG01 (Singapore), DE01 (Germany)
Controlling Area ABCG — shared across IN01, SG01, DE01
Plants: PL01 (Pune), PL02 (Chennai), PL03 (Singapore)
Cost Centers: CC-PROD, CC-QA, CC-MKT, CC-FIN, CC-IT
Profit Centers: PC-IND, PC-CON, PC-EXPORT
House Banks: HDFC, ICICI (India); DBS (Singapore)
IHC Company Code: IHC0 — group treasury centre

Configuration Highlights

Config	Transaction	Purpose
Create Company Code	OX02	Legal entity
Assign Company Code to Controlling Area	OX19	Link FI & CO
Create Cost Center	KS01	Overhead collector
Create Profit Center	KE51	Internal profitability
Maintain 3KEH	3KEH	Auto profit center substitution
Create Plant	OX10	Facility within company code
Maintain House Bank	FI12	Bank relationship for BL

Common Errors & Fixes

"Company code not defined"

Posting without a valid company code.

Check OX02 and user defaults.

"Controlling area not assigned"

FI posting with cost object fails.

Assign via OX19.

"Cost center does not exist on date"

Expired or future validity.

Extend with KS02.

"Profit center not in company code"

Wrong company code assignment.

Reassign via KE51.

Interview Prep

Q1: Can one controlling area be assigned to multiple company codes?

Yes — provided they share the same chart of accounts, fiscal year variant, and currency (or have currency translation configured). Common in companies with multiple legal entities managed centrally.

Q2: Business Area vs Profit Center?

Business Area (GSBER) is a legacy cross-company-code unit. Profit Center (PRCTR) is the modern equivalent — it produces a full internal P&L and balance sheet and is used for segment reporting.

2 General Ledger & Core FI

The heart of financial accounting — how every transaction is recorded, classified, and reported.

Meaning

What is it?

The General Ledger (GL) is the central repository of all financial transactions. Every posting in AP, AR, AA, BL, IHB, or CO flows through the GL. GL accounts are defined at two levels: Chart of Accounts (SKA1) and Company Code (SKB1).

Core Concepts

GL Account Master

SKA1 + SKB1. Determines P&L or balance sheet classification, currency, field status.

Document Type

Two-char code (SA, KR, DR) controlling number range, posting keys, reversal.

Posting Key

40=debit GL, 50=credit GL, 31=credit vendor, 21=debit vendor, 01=debit customer.

Number Range

Determines document number sequence per document type and company code.

Field Status Group

Controls required/optional/suppressed fields per GL account.

Posting Period

Open periods — normal (1–12) and special (13–16) for adjustments.

Parallel Ledgers

Leading ledger (0L) + non-leading (IFRS, tax, local GAAP).

Parked Documents

Saved but not posted. Do not affect balances. Used for approval workflows.

Substitutions & Validations

Rules that auto-fill or validate fields at posting time (OBBH / OB28).

Document Splitting

New GL feature — every document balanced by profit center / segment.

Example — Journal Entry

Scenario

ABC Ltd. pays office rent of ₹50,000 for April 2024 by bank transfer.

PK	Account	Description	Debit (₹)	Credit (₹)
40	400100	Rent Expense	50,000
50	100200	Bank — Current Account		50,000
Total			50,000	50,000

Transaction: F-02 (general posting).

Configuration Highlights

Config	Transaction	Purpose
Define Chart of Accounts	OB13	Framework for all GL accounts
Create GL Account	FS00	Central creation (SKA1 + SKB1)
Define Document Type	OBA7	Number range + posting keys
Define Number Ranges	FBN1	Assign to document types
Define Field Status Group	OBC4	Field-level control per GL account
Open/Close Periods	OB52	Control posting periods
Substitution Rules	OBBH	Auto-fill fields at posting
Validation Rules	OB28	Block postings that violate rules

Common Errors & Fixes

"Posting period closed"

Period not open in OB52.

Open period or use special period 13–16 for adjustments.

"Account not defined in company code"

GL master missing at company-code level.

Create SKB1 segment via FS00.

"Number range exhausted"

Internal number range full.

Extend in FBN1.

"Reconciliation account missing"

Vendor/customer without recon account.

Assign in LFB1 / KNB1.

Interview Prep

Q1: Posting key vs document type?

Document type classifies the entire transaction and controls number range and allowed account types. Posting key applies to a single line and determines debit/credit and account type.

Q2: How does SAP ensure debits equal credits?

SAP enforces the double-entry rule at save. If totals differ, the document is rejected with "Document is not balanced."

Q3: What is document splitting?

A New GL feature ensuring documents are balanced not only in total but also by dimensions like profit center or segment — enabling real-time segment reporting.

3 Accounts Payable, Receivable & Asset Accounting

The three subledgers that sit beside the GL — each with its own master data, transactions, and reconciliation.

Meaning

What is it?

AP, AR, and AA are subledgers — they maintain detailed records for specific account types and post summarised balances to the GL via reconciliation accounts. At month end, subledger balance must equal GL reconciliation account balance.

Accounts Payable (AP)

Master Data: LFA1 (general), LFB1 (company code), LFM1 (purchasing).

Example — Vendor Invoice with GR/IR

ABC Ltd. buys raw material worth ₹1,00,000 + 18% GST from Vendor V-2001. Goods received last week.

PK	Account	Description	Debit (₹)	Credit (₹)
86	191100	GR/IR Clearing	1,00,000
40	140100	GST Input Credit	18,000
31	200100	Vendor V-2001		1,18,000

Key T-codes: FB60F110FBL1NF.19

Accounts Receivable (AR)

Master Data: KNA1 (general), KNB1 (company code), KNVV (sales).

Example — Customer Invoice & Payment

ABC Ltd. sells goods for ₹2,00,000 + 18% GST on 30-day terms.

PK	Account	Description	Debit (₹)	Credit (₹)
01	120100	Customer C-5001	2,36,000
50	400000	Sales Revenue		2,00,000
50	210100	GST Output Payable		36,000

On payment: Dr Bank ₹2,36,000 / Cr Customer ₹2,36,000.

Key T-codes: FB70F-28F150FBL5N

Asset Accounting (AA)

Master Data: ANLA (asset master), ANLB (depreciation terms), ANLC (values), ANEP (line items).

Example — Asset Acquisition & Depreciation

Delivery van purchased for ₹8,00,000 + 18% GST. Useful life: 5 years. Straight line.

PK	Account	Description	Debit (₹)	Credit (₹)
70	150100	Motor Vehicles	8,00,000
40	140100	GST Input Credit	1,44,000
50	200100	Vendor		9,44,000

Monthly depreciation: Dr Depreciation Expense ₹13,333 / Cr Accumulated Depreciation ₹13,333.

Key T-codes: AS01ABZONABUMNAFABAW01N

Configuration Highlights

Config	Transaction	Purpose
Vendor Account Groups	OBD3	Field status and number range
Customer Account Groups	OBD2	Field status and number range
Payment Terms	OBB8	Discount and baseline date
Automatic Payment Program	FBZP	F110 setup
Asset Classes	OAOA	Grouping for AA
Depreciation Keys	AFAMA	Method, life, rate
Account Determination (AA)	AO90	Map asset transactions to GL

Common Errors & Fixes

"Vendor blocked for posting"

Blocked in LFB1.

Unblock or investigate.

"No payment method found"

F110 can't determine payment method.

Maintain in LFB1 and check FBZP.

"GR/IR account not defined"

Missing OBYC config.

Maintain WRX in OBYC.

"Depreciation already posted"

AFAB run twice.

Restart mode or reverse with AFABR.

Interview Prep

Q1: What is a reconciliation account?

The GL account linked to a subledger (AP, AR, AA). You cannot post directly to it — all postings go through the subledger. Guarantees subledger = GL at any point.

Q2: What is GR/IR clearing?

A suspense account. GR debits inventory, credits GR/IR. Invoice debits GR/IR, credits vendor. If matched, zero balance. Residual is reclassified with F.19 at month end.

Q3: How is depreciation calculated?

By asset class → depreciation key → method, life, rate → depreciation area. Posted via AFAB. Entry: Dr Expense / Cr Accumulated Depreciation.

4 Bank Accounting (BL)

Managing cash, bank statements, reconciliations, and cash flow — the link between the bank and the GL.

Meaning

What is it?

Bank Accounting (BL) manages the company's relationships with banks: recording payments, receiving bank statements, matching them to GL entries, and forecasting cash. It answers: "How much cash do we have? What's coming in? What's going out? Does the bank balance match our books?"

Bank Accounting consists of three connected sub-areas: Bank Master Data, Electronic Bank Statement (EBS), and Cash Management / Liquidity Forecast.

Core Concepts

House Bank

A bank the company has a relationship with (HDFC, ICICI, DBS). Defined in FI12 for each company code.

Bank Account ID

Specific account within a house bank (current account, OD account, etc.). The pair (house bank + account ID) = your bank account.

Bank Directory

Master list of banks, bank keys, and routing numbers. Maintained via BA01 / FI01.

Bank Statement

File received from bank (MT940 / MT942 / CAMT.053 / BAI2) listing all transactions in the account.

EBS — Electronic Bank Statement

Automated processing of bank statement files. Transactions are matched to open items automatically.

Lockbox

Bank-operated PO box for customer payments. Bank sends a lockbox file; SAP matches to customer invoices.

Manual Bank Statement

Entered manually via FF67 for banks that don't send electronic files.

Cash Position

Snapshot of cash at a point in time (end of day) — FF7A.

Liquidity Forecast

Forward projection of cash inflows/outflows — FF7B.

Bank Reconciliation

Monthly comparison of bank balance vs GL balance. Difference = unreconciled items.

Payment Medium Workbench

Generates payment files (NACH, ACH, SWIFT) in bank-specific formats — DMEE.

Bank Chain

Sequence of banks involved in an international payment (intermediary banks).

Real-World Example — EBS Processing

Scenario

ABC Ltd. receives a bank statement from HDFC for 30.04.2024. It contains 3 transactions:

Customer payment received from C-5001: ₹2,36,000
Vendor payment to V-2001: ₹1,18,000
Bank charges: ₹500

Step 1 — Bank statement file received (MT940): Uploaded via FF.5 or automatically via SFTP.

Step 2 — Processing the statement: FF67 or automatic post-processing via FEBAN.

Step 3 — Auto-matched postings:

PK	Account	Description	Debit (₹)	Credit (₹)
40	100200	Bank — HDFC Current	2,36,000
15	120100	Customer C-5001		2,36,000
—	200100	Vendor V-2001	1,18,000
—	100200	Bank — HDFC Current		1,18,000
40	500200	Bank Charges	500
50	100200	Bank — HDFC Current		500

Why EBS is powerful

Instead of manually entering hundreds of bank transactions, EBS uses interpretation algorithms to auto-match. Rule-based algorithms identify the transaction type from the bank code; search algorithms find the matching open item (e.g., by invoice number, amount, customer code).

EBS Configuration — The Key Steps

Config	Transaction	Purpose
Create House Bank	FI12	Bank relationship per company code
Create Account ID	FI12	Specific bank account within house bank
Bank Statement Format	OT83	Define MT940, CAMT.053, etc.
Create Account Symbols	OT01 / OTB1	Map bank transactions to GL accounts
Assign GL Accounts to Account Symbols	OT02 / OTB1	Link posting keys and GL accounts
Create Transaction Types	OT03 / OTB2	Define business transactions (e.g., incoming transfer)
Assign Transaction Types to Account Symbols	OT04 / OTB3	Map business transactions to GL accounts
Define Posting Rules	OT05 / OTB4	Sequence of algorithms to match and post
Assign Posting Rules to Bank Accounts	OT06 / OTB5	Link rules to specific bank account
Bank Statement Upload	FF.5	Upload MT940 / CAMT files
Post-Processing	FEBAN	Manual handling of unmatched items

Cash Management & Liquidity Forecast

Cash Management (FF7A): Shows actual cash and bank balances at end of day, by bank account and currency. Provides a snapshot of liquidity.

Liquidity Forecast (FF7B): Forward-looking projection combining:

Open customer invoices (expected inflows)
Open vendor invoices (expected outflows)
Planned payments and receipts
One-time and periodic postings

Both are configured via Cash Management groups (OT51) and planning levels.

Common Errors & Fixes

"Account symbol not assigned to bank account"

EBS cannot determine the GL account for a transaction type.

Review OTB1 / OT01 configuration.

"No posting rule found"

Bank account has no posting rule assigned.

Assign posting rule via OTB5 / OT06.

"Bank statement file format invalid"

MT940 variant mismatch.

Check OT83 format definition matches bank's actual file.

"Manual bank statement items pending"

Auto-matching failed for some items.

Process in FEBAN — assign manually or adjust algorithms.

"Bank balance ≠ GL balance"

Unreconciled items (outstanding cheques, deposits in transit).

Run bank reconciliation report; investigate stale items with the bank.

"Cash position does not match"

Bank sub-accounts not mapped to cash management groups.

Maintain mapping via OT51 / transaction FF7A config.

Interview Prep

Q1: What is the difference between House Bank and Account ID?

A House Bank is the banking partner (e.g., HDFC Bank). An Account ID identifies a specific account within that bank (current account, OD account, ESCROW). Together they form the unique bank identifier in SAP: BANKL + BNKACC. You can have multiple account IDs under one house bank.

Q2: How does EBS auto-match a customer payment?

EBS uses a three-layer approach: (1) Interpretation algorithms identify the transaction type from the bank code and text fields. (2) Posting rules define which algorithms run and in what order. (3) Search algorithms look up the matching open item — by invoice number, amount, or customer code. If a match is found, the item is auto-cleared. If not, it goes to FEBAN for manual processing.

Q3: What is the difference between Cash Position and Liquidity Forecast?

Cash Position (FF7A) is a snapshot of current bank balances — what you have now. Liquidity Forecast (FF7B) is a projection into the future — what you expect to receive and pay, based on open items and planned transactions. Cash Position looks backward and at today; Liquidity Forecast looks forward.

Q4: What is lockbox and how is it different from EBS?

A lockbox is a physical PO box operated by the bank for customer payments. The bank collects the payments, processes them, and sends SAP a lockbox file (BAI2 format). SAP matches the payments to customer invoices using invoice numbers or MICR data. EBS is a broader concept — it processes the entire bank statement (all transactions). Lockbox is a specific tool for automating customer receipt matching at high volume.

Q5: How do you reconcile the bank statement with the GL?

After EBS is fully processed, the GL bank account balance should equal the bank statement's closing balance. Any difference is due to: outstanding cheques, deposits in transit, bank errors, or unrecorded bank charges. Use the bank reconciliation report, review unreconciled items, and clear them once the underlying transaction is recorded.

5 In-House Banking / In-House Cash (IHB / IHC)

How large groups centralise cash, net intercompany payments, and manage internal liquidity — using an internal bank structure.

Meaning

What is it?

In-House Banking (also called In-House Cash / IHC) is a treasury tool that lets a group act as its own bank. Instead of every subsidiary maintaining multiple external bank accounts and making cross-border payments to each other, the group sets up an In-House Cash Centre that acts as an internal bank. All intercompany payments flow through the IHC. The IHC then consolidates and nets external payments, reducing bank fees, FX exposure, and cash trapped in subsidiaries.

IHC is a Treasury (TRM) submodule, but it posts directly to FI — so FICO consultants frequently work with it.

Why Companies Use IHC

Cash visibility: Treasury has real-time visibility of all subsidiary cash positions.
Netting: Intercompany payables and receivables offset each other — only net payments are made.
Reduced bank fees: Fewer external transactions = lower transaction fees.
FX consolidation: FX is managed centrally, not in each subsidiary.
Internal lending: Group can lend to subsidiaries at internal rates.
Better cash pooling: Physical or notional pooling of balances.

Core Concepts

In-House Cash Centre (IHCC)

A dedicated company code representing the internal bank. Acts as the counterparty for all intercompany transactions.

IHC Account

An internal account held by each subsidiary with the IHC. Equivalent to a bank account, but internal to the group.

Internal Customer

The subsidiary as a customer of the IHC. Created in IHC customer master.

Internal Vendor

The IHC as a vendor to the subsidiary. Created as an IHC vendor.

Payment Order

An instruction to the IHC to pay on behalf of a subsidiary. Central to IHC processing.

Netting

Offsetting payables and receivables between subsidiaries. Only the net is settled.

Physical Cash Pooling

Actual transfer of funds to a concentration account.

Notional Pooling

Balances aggregated for interest calculation only — no physical transfer.

Internal Loan

Loan from IHC to a subsidiary, with internal interest calculation.

IHC FX

Currency conversion handled by IHC on behalf of subsidiaries.

Real-World Example — Intercompany Netting

Scenario — ABC Group

Three subsidiaries trade with each other:

ABC India (IN01) owes ABC Singapore (SG01) ₹50,00,000
ABC Singapore (SG01) owes ABC Germany (DE01) €50,000 (₹45,00,000)
ABC Germany (DE01) owes ABC India (IN01) €55,000 (₹49,50,000)

Without IHC, ABC Group would make 3 external cross-border payments.

With IHC: All three subsidiaries post their intercompany invoices to the IHC as if the IHC were their bank. The IHC computes net positions and settles only the net amounts.

Subsidiary	Gross Payable	Gross Receivable	Net Position
IN01	50,00,000	49,50,000	-50,000 (pay)
SG01	45,00,000	50,00,000	+5,00,000 (receive)
DE01	49,50,000	45,00,000	-4,50,000 (pay)

Only 2 net payments are made instead of 3 gross payments — and all through the IHC rather than between subsidiaries.

Journal entries (simplified) — when ABC India pays its intercompany invoice:

PK	Account	Description	Debit (₹)	Credit (₹)
40	210200	Intercompany Payable (SG01)	50,00,000
50	210500	Due to IHC		50,00,000

IHC then settles the net payable with SG01 directly. SG01's books show the reverse.

IHC vs Bank Accounting — What's Different

Aspect	Bank Accounting (BL)	In-House Cash (IHC)
Counterparty	External bank	Internal bank (IHC Centre)
Purpose	Manage external payments and statements	Manage group internal payments and cash
Statement format	MT940 / CAMT.053 from bank	IHC generates internal statement
Payment flow	Company → Bank → Beneficiary	Subsidiary → IHC → Beneficiary (or netting)
FX	Handled by external bank	Handled by IHC at internal rates
Volume reduction	—	Netting reduces external transactions by 60–80%
Module	FI (Bank Accounting)	TRM (Treasury) + FI postings

Configuration Highlights

Config	Transaction	Purpose
Create IHC Company Code	OX02	Dedicated company code for IHC
Create IHC Customer / Vendor	FD01 / FK01	IHC master record
Define IHC Accounts	IHCC_CREATE_ACCOUNT	Internal accounts per subsidiary
Assign Subsidiaries to IHC	SAP IMG: Financial Supply Chain	Define which company codes participate
IHC Posting Rules	IHC Customizing	Rules for auto-posting to IHC
Netting Configuration	Netting IMG	Define netting rules and cut-off
Payment Order Types	IHC Payment Config	Types of payment orders accepted

Common Errors & Fixes

"IHC account not found for company code"

Subsidiary has no IHC account.

Create IHC account and assign to the subsidiary.

"Payment order rejected"

Missing or invalid payment order type.

Check IHC payment configuration and order type.

"Netting proposal empty"

No intercompany invoices found within the netting period.

Verify cut-off dates and invoice posting dates.

"FX rate not found for IHC conversion"

Missing exchange rate for IHC pair.

Maintain rate in OB08 or IHC rate table.

"IHC posting blocked — reconciliation account missing"

IHC recon account not maintained.

Assign IHC recon account to the IHC customer/vendor.

Interview Prep

Q1: What is the purpose of In-House Cash?

IHC centralises cash management across a group. It acts as an internal bank — subsidiaries hold internal accounts with the IHC instead of external bank accounts for intercompany flows. This enables netting, centralised FX, internal lending, and dramatic reduction in external bank transactions and fees.

Q2: How does netting work in IHC?

Subsidiaries post their intercompany payables and receivables to the IHC instead of directly to each other. At defined cut-off dates (daily, weekly, monthly), the IHC computes net positions per subsidiary. Only the net is settled externally. Example: if IN01 owes SG01 ₹50L and SG01 owes IN01 ₹49.5L, only ₹0.5L is settled instead of ₹99.5L.

Q3: How is IHC different from regular bank accounting?

Bank Accounting deals with external banks — statements come from the bank (MT940), payments go to external beneficiaries. IHC deals with internal group transactions — statements are generated internally, payments flow between subsidiaries and the IHC. IHC is a Treasury module, not pure FI, but it produces FI postings.

Q4: What are the prerequisites for implementing IHC?

(1) A dedicated company code for the IHC. (2) Customer and vendor master records for the IHC. (3) Internal accounts created for each participating subsidiary. (4) Clear intercompany reconciliation accounts. (5) Defined payment order types and posting rules. (6) Netting configuration if netting is used. (7) Agreement on internal FX rates and interest calculation.

6 Controlling (CO) — The Full Landscape

Complete CO coverage: Cost Center Accounting (CO-CC), Cost Element Accounting (CO-CEL), Internal Orders (CO-OPA), Activity-Based Costing (CO-ABC), Product Costing (CO-PC), Cost Object Controlling / Production (CO-PP), Profitability Analysis (CO-PA), and Profit Center Accounting (PCA).

Meaning

What is CO?

Controlling (CO) is the management accounting module. It captures costs and revenues by cost object — cost centers, internal orders, production orders, profit centers, profitability segments — and answers: Where did the money go? Which department overspent? Which product is most profitable? Where can we cut costs?

CO is where the deepest financial insight lives.

The CO Submodule Map

Submodule	Purpose	Key Objects	Key Tables
CO-CEL · Cost Element Accounting	Bridge between FI accounts and CO	Primary & Secondary CEs	CSKA, CSKB, COKA
CO-CCA · Cost Center Accounting	Overhead costs by department	Cost Centers, Activity Types, SKFs	CSKS, CSKT, CSLA, COEP
CO-OPA · Overhead Orders	Costs for short-term events/projects	Internal Orders	AUFK, AUFTR, COEP
CO-ABC · Activity-Based Costing	Activity-driven overhead allocation	Business Processes	CBPR, CBPT
CO-PC · Product Cost Controlling	Standard cost of products	Cost Estimates	KEKO, KEPH, CKHS, CKIS
CO-PP · Cost Object Controlling (Production)	Actual cost of production orders	Production Orders	AFKO, AFPO, AFVC, RESB, COEP
CO-PA · Profitability Analysis	Margin by market segment	Operating Concern, Characteristics	CE1xxxx, CE4xxxx
EC-PCA · Profit Center Accounting	Internal P&L by profit center	Profit Centers	CEPC, GLPCT, ACDOCA

CO-CEL — Cost Element Accounting

Purpose: Every primary cost element corresponds to an FI P&L account. Cost element accounting maintains this link and defines cost element categories.

Primary Cost Element (Category 01)

Has an FI GL counterpart. Represents costs flowing from FI into CO — salaries, rent, materials.

Secondary Cost Element (Category 21/41/42/43)

CO-only. Represents internal cost flows — assessments (42), distributions (43), activity allocations (41).

Revenue Element (Category 11)

Has an FI revenue account counterpart. Used in CO-PA.

T-codes: KA01KA02KA06

CO-CCA — Cost Center Accounting

Purpose: Collects overhead costs by department or function, and allocates them to receivers.

Cost Center Master

CSKS — category, responsible person, hierarchy, validity dates.

Activity Type

CSLA — unit of output (machine hour, labour hour). Used for internal activity allocation.

Statistical Key Figure

Non-monetary measure (headcount, sqm) used as allocation base.

Assessment

KSU1–KSU8. Allocates costs to receivers under a secondary cost element.

Distribution

KSV1–KSV5. Allocates costs preserving original cost elements.

Activity Allocation

KB11N / KB21N. Charges costs from sender to receiver based on activity quantity.

Example — IT Cost Center Assessment

CC-IT has ₹5,00,000 of costs. Allocated to CC-PROD (67%), CC-MKT (17%), CC-FIN (16%) via statistical key figure "headcount".

Cost Center	Cost Element	Amount (₹)
CC-IT (Sender)	Sec. CE 900001	−5,00,000
CC-PROD	Sec. CE 900001	+3,35,000
CC-MKT	Sec. CE 900001	+85,000
CC-FIN	Sec. CE 900001	+80,000

T-codes: KS01KL01KK01KSU5KSV5KB11N

CO-OPA — Internal Orders

Purpose: Collect costs for a specific purpose (marketing campaign, R&D project, event). Settled at period end.

Order Types

Define behaviour — budget profile, settlement profile, planning profile.

Order Status

CRTD → REL → TECO → CLSD. Controls whether postings are allowed.

Budget & Availability Control

Prevents overspending. Tolerance limits trigger warnings or blocks.

Commitment Management

Tracks future obligations (POs, requisitions) even before invoices arrive.

Settlement Rule

Defines where costs go at period end.

T-codes: KO01KO02KO88KO8G

CO-PC — Product Cost Controlling

Purpose: Calculate the standard cost of manufactured products. Detailed walkthrough in Tab 7.

BOM

Bill of Materials — components required to make one unit.

Routing

Sequence of operations (work centers) with standard times.

Costing Variant

Determines valuation strategy, overhead rates, and cost component split.

Cost Component Split

Breakdown of standard cost by material, labour, overhead.

CO-PP — Cost Object Controlling (Production)

Purpose: Collect actual manufacturing costs on production orders, calculate WIP and variance, settle to receivers.

Production Order

The cost object. Collects material, labour, and overhead costs.

Goods Issue

Materials consumed — debits production order, credits inventory.

Confirmation

Records labour and machine time — debits order, credits cost center.

Goods Receipt

Finished goods received into stock — credits order at standard cost.

WIP (KKAO)

Calculated for incomplete orders at period end.

Variance (KKS1)

Calculated for completed orders — difference between actual and standard.

Settlement (KO88)

Transfers variance to COGS or CO-PA.

CO-PA — Profitability Analysis

Purpose: Analyze margin by market segment — customer, product, region, channel.

Operating Concern

Top-level CO-PA organizational unit. Defines the characteristics and value fields.

Characteristics

Dimensions — customer, product, region, channel. CE4xxxx config.

Value Fields

Measures — revenue, discount, COGS, margin. CE4xxxx config.

Costing-Based vs Account-Based

Costing-based uses value fields; account-based uses GL accounts. S/4HANA uses both, stored in ACDOCA.

T-codes: KEA0KE21NKE24KE30KE31KEQ3

EC-PCA — Profit Center Accounting

Purpose: Internal P&L and balance sheet by profit center.

Profit Center Master

CEPC — company code assignment, responsible person, hierarchy.

3KEH Substitution

Auto-derives profit center from cost center or GL account.

Internal P&L

Profit centers get a full P&L view — revenue, cost, margin.

Internal Balance Sheet

Profit centers also receive balance sheet items (AR, AP, inventory).

Transfer Pricing

Internal prices when one profit center supplies another.

T-codes: KE51KE523KEHKE5Z

Common CO Errors & Fixes

"Cost element not created for GL account"

P&L account not linked to a cost element.

Create with KA01 (ECC) or auto-created in S/4HANA.

"Sender = receiver in cycle"

Assessment cycle has same sender and receiver.

Fix in KSU2.

"No SKF values maintained"

Assessment based on SKF but no values exist.

Maintain via KB31N.

"Settlement rule missing"

Order cannot be settled.

Maintain in KO02 / CO02 before KO88.

"WIP calculation not possible"

Order not fully confirmed.

Post all confirmations, re-run KKAO.

"Operating concern not assigned"

CO-PA posting fails.

Assign controlling area to operating concern.

Interview Prep

Q1: Primary vs secondary cost element?

Primary has an FI GL counterpart (salary expense, rent). Secondary exists only in CO and represents internal flows (assessment, distribution, activity allocation).

Q2: Distribution vs assessment?

Distribution preserves original cost elements (receiver sees the underlying cost). Assessment consolidates into one secondary cost element.

Q3: Cost center vs profit center?

Cost center collects costs by department. Profit center produces an internal P&L by product line, region, or business — it receives both costs and revenues.

Q4: What is the difference between CO-PA and PCA?

CO-PA analyzes margin by market segment (customer, product, region) — external-facing view. PCA analyzes profit by internal organizational unit (division, region) — internal view. Both reconcile to FI.

Q5: How does CO-PP tie to CO-PC?

CO-PC calculates the standard cost estimate before production. CO-PP collects actual costs during production and compares them to the standard to calculate variance. The standard cost from CO-PC is the benchmark used by CO-PP.

7 Product Costing (CO-PC) — Detailed Walkthrough

How SAP calculates the standard cost of a product and tracks actual costs on production orders.

Meaning

What is it?

Product Costing answers: "How much does it cost to make this product?" It uses the Bill of Materials (BOM) and Routing to estimate costs before production, then tracks actual costs during and after production to calculate variances. It is the bridge between FI, CO, MM, PP, and Material Ledger.

Core Concepts

BOM

List of raw materials and components required for one unit.

Routing

Operations (work centers) with standard times.

Cost Estimate

Calculated cost from BOM, routing, activity prices, overhead rates.

Costing Variant

Controls calculation logic — valuation, overhead, cost component split.

Cost Component Split

Breakdown by material, labour, overhead, etc.

Standard Cost

Expected cost, marked and released for the fiscal year. Used for inventory valuation.

Production Order

Cost object collecting actual manufacturing costs.

WIP

Value of partially completed production at period end.

Variance

Actual vs standard — analysed by input price, quantity, resource usage.

Settlement

Transfer variance to COGS, inventory, or CO-PA.

Real-World Example — Full Production Cycle

Scenario

ABC Ltd. produces FG-WIDGET. Standard cost estimate for 2024: ₹500/unit (Material ₹300, Labour ₹120, Overhead ₹80).

Production order for 1,000 units. Actual costs: Material ₹3,10,000, Labour ₹1,15,000, Overhead ₹85,000.

Step 1 — Cost estimate (CK11N) + Mark/Release (CK24):

Cost Component	Per Unit (₹)	For 1,000 Units (₹)
Material	300	3,00,000
Labour	120	1,20,000
Overhead	80	80,000
Standard Cost	500	5,00,000

Step 2 — Goods Issue of raw materials (MB1A):

Account	Dr (₹)	Cr (₹)
Production Order	3,10,000
Raw Material Inventory		3,10,000

Step 3 — Activity confirmation (CO11N):

Account	Dr (₹)	Cr (₹)
Production Order	2,00,000
Cost Center (activity credit)		2,00,000

Step 4 — Goods Receipt of FG (MB31):

Account	Dr (₹)	Cr (₹)
FG Inventory (1,000 × ₹500)	5,00,000
Production Order		5,00,000

Step 5 — Order balance after all postings:

Entry	Debit (₹)	Credit (₹)
Material consumed	3,10,000
Labour + Overhead	2,00,000
Goods receipt		5,00,000
Balance	5,10,000	5,00,000
Variance (Unfavourable)	₹10,000

Step 6 — WIP calculation (KKAO) and Variance (KKS1):

For fully delivered orders, variance of ₹10,000 is decomposed into:

Input price variance (material price difference)
Input quantity variance (more material used)
Resource usage variance (more machine/labour hours)
Remaining variance (overhead differences)

Step 7 — Settlement (KO88):

Account	Dr (₹)	Cr (₹)
Variance — COGS	10,000
Production Order		10,000

Outcome

Order balance is now zero. ₹10,000 unfavourable variance charged to P&L (or CO-PA). 1,000 finished units sit in inventory at ₹5,00,000.

Key Transactions

CK11N Create cost estimate CK24 Mark & release CK40N Mass costing run CO01 Create production order CO02 Change/release order MB1A Goods issue CO11N Confirmation MB31 Goods receipt KKAO Calculate WIP KKS1 Calculate variance KO88 Settle order

Common Errors & Fixes

"Cost estimate not found"

No estimate for material/plant/year.

Run CK11N, then mark/release via CK24.

"Standard cost not released"

GR values material at zero.

Release via CK24.

"WIP calculation not possible"

Order not fully confirmed.

Complete confirmations, re-run KKAO.

"Settlement rule missing"

KO88 fails.

Maintain in CO02.

Interview Prep

Q1: Standard cost vs actual cost?

Standard = pre-calculated expected cost (used for inventory valuation). Actual = real cost incurred. Difference = variance.

Q2: What is WIP and when is it calculated?

Work in Process = value of partially completed production at period end. Calculated via KKAO. Prevents P&L distortion by deferring costs related to unfinished work.

Q3: Walk me through the settlement process.

(1) All confirmations posted. (2) KKAO calculates WIP for incomplete orders. (3) KKS1 calculates variances for complete orders. (4) KO88/KO8G settles variance to receiver (COGS, CO-PA). Order balance → zero.

8 Material Ledger (ML)

Actual costing, price differences, and multi-currency valuation — the bridge between MM, PP, and FI/CO.

Meaning

What is it?

The Material Ledger (ML) records the actual cost of materials, in multiple currencies and multiple valuation approaches. It tracks every goods movement for a material, compares standard cost to actual cost, and calculates price differences that are posted to inventory or COGS at period end.

In S/4HANA, Material Ledger is mandatory and is the foundation of actual costing.

Why Material Ledger Matters

Actual costing: Not just standard — real cost of materials in real currency.
Multi-currency: Value materials in company code currency, group currency, and hard currency.
Price differences: Purchase price variance (PPV) is tracked and settled at period end.
Valuation alternatives: Legal valuation, group valuation, profit center valuation.
Foundation for CO-PA: Actual cost component split feeds profitability analysis.
Inventory accuracy: Ensures inventory is valued at true cost, not just standard.

Core Concepts

Valuation Area (BWKEY)

Usually the plant. Each material-plant combination has its own valuation record.

Standard Price (S)

Fixed price. Price differences are collected and settled at period end.

Moving Average Price (V)

Recalculated with every goods movement. Price differences absorbed immediately.

Price Difference Categories

PPV (purchase), PRD (production), PRV (other), KDM/KDV (exchange rate).

Cost Component Split

Breakdown of cost into material, labour, overhead — used for CO-PA.

Periodic Actual Costing

Month-end run (CKMLCP) that revalues inventory and COGS to actual cost.

Single-Level vs Multilevel

Single-level revalues each material independently. Multilevel propagates differences through the BOM.

Valuation Views

Legal view (statutory), Group view (consolidated), Profit Center view (management).

Material Ledger Document

Every movement creates an ML document — records quantity, value, price, currency.

Settlement

At period end, price differences are settled to inventory or COGS.

Real-World Example — Price Difference Settlement

Scenario

ABC Ltd. buys a raw material RM-100. Standard price: ₹100/kg. During April 2024:

Purchased 1,000 kg at ₹105/kg (₹5,000 more than standard)
Consumed 800 kg for production
200 kg remain in inventory at month end

Step 1 — Purchase at ₹105 (above standard):

Account	Dr (₹)	Cr (₹)
Inventory RM-100 @ standard ₹100	1,00,000
Price Difference (ML)	5,000
Vendor		1,05,000

The ₹5,000 price difference is held in a Material Ledger account (not yet in P&L).

Step 2 — Month-end actual costing run (CKMLCP):

Selection → Determine → Revalue → WIP → Settlement → Post-Close
The ₹5,000 price difference is distributed between:

Receiver	Quantity	Share of Difference	Amount (₹)
Inventory (200 kg)	20%	₹1,000	1,000
COGS (800 kg consumed)	80%	₹4,000	4,000

Step 3 — Settlement entry:

Account	Dr (₹)	Cr (₹)
Inventory RM-100 (revaluation)	1,000
COGS — Price Variance	4,000
Price Difference (ML)		5,000

Outcome

Inventory is now valued at actual cost (₹101/kg blended), and COGS reflects the ₹4,000 PPV. Material Ledger account is cleared. Standard price in the material master stays at ₹100 — but ML now knows the true cost.

Material Ledger Tables

Table	Purpose
CKMLHD	Material Ledger Header — one per material/valuation area
CKMLPP	Periodic Material Ledger — quantities per period
CKMLCR	Material Ledger — currency amounts per period
CKMLCT	Currency types per material ledger record
MLIT	Material Ledger Document — line items (S/4HANA)
MLCD	Material Ledger — Cost Component Split
MLHD	Material Ledger Document Header
MBEW	Material Valuation — standard price, MAP, valuation class

The Actual Costing Run (CKMLCP)

The monthly actual costing run is the heart of ML. Sequence:

Selection: Choose materials, period, valuation area.
Determination: Collect all goods movements, invoices, and production postings.
Multilevel Price Determination: Propagate price differences through the BOM.
Revaluation: Revalue inventory to actual cost.
WIP: Calculate WIP for production orders (interfaces with CO-PP).
Settlement: Post differences to inventory and COGS.
Post-Close: Lock the period, mark as closed.

T-codes: CKMLCP Actual Costing Run CKM3 Material Price Analysis CKMLCPAVR Alternative Valuation Run CKMLQS Quantity Structure

Material Ledger in S/4HANA

Key change

In S/4HANA, Material Ledger is mandatory. It is no longer an optional add-on. All materials, in all valuation areas, use ML. The ML data is integrated into ACDOCA — every ML posting also appears in the Universal Journal. This eliminates the historical reconciliation between ML and FI.

Common Errors & Fixes

"Material Ledger not active for valuation area"

ML not activated for the plant.

Activate ML via OMWD / OLMB for the valuation area.

"Actual costing run already executed"

Trying to rerun CKMLCP for the same period.

Reverse the prior run or use post-close step cautiously.

"Price difference not distributed"

Selection missing some materials.

Expand selection criteria or check material status.

"Multilevel price determination fails"

BOM hierarchy broken or missing cost estimates.

Verify BOM and cost estimate for finished products.

"Currency type not defined"

Trying to value in a currency not configured.

Maintain currency types via OMX1 / 8KEM.

"Inventory differs from ML value"

Reconciliation issue between MM-FI and ML.

Run CKM3 / CKMLCP to identify mismatched materials.

Interview Prep

Q1: What is the purpose of Material Ledger?

ML records actual cost of materials in multiple currencies and valuation views, calculates price differences, and enables monthly actual costing. It bridges the gap between standard cost (used for daily postings) and actual cost (true economic cost).

Q2: How does ML handle price differences?

When a material is purchased at a price different from standard, the difference is posted to a Material Ledger price-difference account (not P&L). At month end, the actual costing run (CKMLCP) distributes this difference proportionally between inventory (remaining) and COGS (consumed).

Q3: What is single-level vs multilevel price determination?

Single-level revalues a material based on its own price differences. Multilevel propagates differences through the BOM — e.g., if raw material is ₹5 more, then every finished good that uses it inherits part of that difference. Multilevel gives a truer cost for manufactured products.

Q4: What changes in S/4HANA for Material Ledger?

ML becomes mandatory. It is integrated into ACDOCA (Universal Journal), eliminating the traditional ML-FI reconciliation. The actual costing run (CKMLCP) is still used but now writes to ACDOCA. The Material Ledger document (MLIT) replaces the older CKMLPP/CKMLCR views for most reporting.

Q5: How does Material Ledger support CO-PA?

ML produces an actual cost component split — material, labour, overhead — for every material. CO-PA uses this to build a cost-of-sales view by product. Without ML, CO-PA would only have standard cost; with ML, CO-PA reflects the true cost of goods sold, including purchase price variances.

9 Integration & S/4HANA

How FI integrates with other modules and what changes in S/4HANA.

Meaning

What is it?

Modules share data through integration points. When a goods receipt posts in MM, it creates an FI document. When a billing document is created in SD, it posts revenue to FI and updates CO-PA. Most production issues surface at these boundaries.

FI-MM Integration (OBYC)

MM Event	FI Entry	Transaction Key
Goods Receipt (GR)	Dr Inventory / Cr GR/IR Clearing	WRX · BSX
Invoice Receipt (IR)	Dr GR/IR Clearing / Cr Vendor	WRX · KDM
Price Difference	Dr/Cr Price Difference	PRD
Goods Issue to Production	Dr Production Order / Cr Inventory	BSX · GBB-VBR
Physical Inventory Adjustment	Dr/Cr Inventory / Dr/Cr Adjustment	BSX · GBB

FI-SD Integration (VKOA)

SD Event	Account	Dr (₹)	Cr (₹)
Billing	Customer Receivable	1,18,000
Billing	Revenue		1,00,000
Billing	GST Output		18,000

FI-BL Integration

Bank statement (EBS) → FI document. Payment runs (F110) → FI document + payment file. Cash position (FF7A) draws from GL bank balances.

FI-IHB Integration

IHC produces FI postings on behalf of subsidiaries. Intercompany payables/receivables replace traditional bank movements. Netting replaces gross payments.

FI-ML Integration

Every material movement creates both an MM document and an ML document. ML feeds the actual cost component split into CO-PA and updates inventory value in FI.

S/4HANA — Universal Journal (ACDOCA)

What changed?

In ECC, FI and CO stored data in separate tables (BKPF/BSEG for FI, COBK/COEP/COSP/COSS for CO). In S/4HANA, all are replaced by ACDOCA — one table containing FI + CO + AA + ML + CO-PA line items. This eliminates reconciliation and enables real-time analytics.

ECC Table	S/4HANA Equivalent	Type
BKPF	BKPF (still physical)	Header
BSEG	ACDOCA (view: BSEG)	Line items
BSID / BSIK / BSIS	Views on ACDOCA	Open items
COEP / COSP / COSS	ACDOCA (views)	CO line items
CE1xxxx (CO-PA)	ACDOCA (PAOBJNR)	CO-PA
ANEP (AA)	ACDOCA (integrated)	AA postings
CKMLPP / CKMLCR (ML)	ACDOCA / MLIT	ML postings

Key fields in ACDOCA

RCLNT, RLDNR, RBUKRS, BELNR, GJAHR, DOCLN, RACCT, KOSTL, PRCTR, OBJNR, MATNR, PAOBJNR, KSTAR, HSL, DRCRK.

Migration Considerations

Custom reports — any report reading COSP/COSS/COEP/CE1xxxx must be reviewed. In S/4HANA these are compatibility views on ACDOCA — performance may suffer.
New GL required — classic GL is not supported. Parallel ledgers must be configured before migration.
Material Ledger mandatory — if ML is not currently active, full implementation is required (often the longest workstream).
Business Partner — customer/vendor master migration to Business Partner (BP) model.
Credit Management — FI-AR credit management replaced by FSCM.
Classic CO-PA — costing-based CO-PA continues but stored in ACDOCA. Account-based is the recommended path.

Interview Prep

Q1: What is the Universal Journal?

ACDOCA — single table for all financial line items (FI, CO, AA, ML, CO-PA). Eliminates FI-CO reconciliation. Enables real-time analytics.

Q2: How does OBYC work?

OBYC maps transaction keys (BSX, WRX, PRD, GBB) + chart of accounts + valuation class + valuation grouping code → GL account. Determines which accounts get debited/credited in MM-FI postings.

Q3: Biggest S/4HANA FI/CO challenge?

Volume of custom code referencing old tables (COSP, COSS, COEP, CE1xxxx). Migration requires rewriting reports against ACDOCA. Also ML activation and BP migration are significant workstreams.

10 Period-End Close & Troubleshooting

The structured close sequence — now including BL, IHB, and ML activities.

Typical Close Calendar (Day 1 – Day 6)

Day	Activity	Transaction	Owner
Day 1	Cut-off — block new postings for prior period	OB52	FI Team
Day 1	Process final EBS / bank statements	FF.5 / FEBAN	BL Team
Day 1	Post GR/IR reclassification	F.19	AP Team
Day 2	Run AP payment program	F110	AP Team
Day 2	Accruals and prepayments	FBS1 / F-02	GL Team
Day 2	Asset depreciation run	AFAB	AA Team
Day 3	Foreign currency valuation	FAGL_FC_VAL	GL Team
Day 3	Intercompany reconciliation & IHC netting	IHC Netting	IHB Team
Day 3	CO assessment and distribution cycles	KSU5 / KSV5	CO Team
Day 3	WIP calculation and variance	KKAO / KKS1	CO Team
Day 4	Settlement of orders	KO8G	CO Team
Day 4	Material Ledger actual costing run	CKMLCP	ML Team
Day 4	ML settlement — price differences to inventory / COGS	CKMLCP (settle)	ML Team
Day 5	Bank reconciliations	FF67 / manual	BL Team
Day 5	Subledger to GL reconciliation	FBL1N / FBL5N	AP/AR
Day 5	IHC reconciliation with subsidiaries	IHC Reports	IHB Team
Day 6	Close prior period	OB52	FI Team
Day 6	Publish management reports	—	Finance

Key Close Activities Explained

1. Accruals (FBS1): Expenses incurred but not invoiced. Dr Expense / Cr Accrual Liability. Reversed next period.

2. Prepayments (F-02): Payments made in advance. Dr Prepaid / Cr Bank, then monthly Dr Expense / Cr Prepaid.

3. GR/IR Reclassification (F.19): Reclassifies GR/IR balance to "Goods Received Not Invoiced" or "Invoice Received Not Delivered". Reversed next period.

4. FX Valuation (FAGL_FC_VAL): Revalues open FX items at closing rate. Dr/Cr FX Adjustment / Cr/Dr Unrealised Gain/Loss.

5. Depreciation Run (AFAB): Dr Depreciation Expense / Cr Accumulated Depreciation.

6. CO Assessment (KSU5) / Distribution (KSV5): Allocates overhead to receivers.

7. WIP (KKAO) / Variance (KKS1) / Settlement (KO8G): Closes production orders.

8. Material Ledger (CKMLCP): Runs actual costing, distributes price differences, revalues inventory and COGS.

9. IHC Netting: Consolidates intercompany payables/receivables, settles only net amounts.

Common Close-Time Errors

"Posting period closed"

Late invoice after OB52 close.

Reopen temporarily with approval, or post in current period.

"Subledger does not reconcile to GL"

AP balance ≠ GL recon.

Run RFAGL_SUBLEDGER_RECON; investigate manual postings to recon account.

"Depreciation already posted"

AFAB run twice.

Restart mode or reverse prior run with AFABR.

"FX valuation incorrect"

Rates not updated.

Maintain rates in OB08 before FAGL_FC_VAL.

"GR/IR balance large"

Old GRs never invoiced or vice versa.

Run MR11 to clear small; escalate large ones to purchasing.

"ML actual costing fails"

Some materials missing cost estimates or BOM broken.

Fix cost estimates and BOM; re-run CKMLCP.

"IHC netting proposal empty"

Wrong cut-off or missing invoices.

Verify cut-off dates and invoice posting dates.

"Bank reconciliation difference"

Outstanding cheques or deposits in transit.

Investigate and clear stale items.

Interview Prep

Q1: Walk me through a typical month-end close.

Day 1: Cut-off, EBS final processing, GR/IR reclassification. Day 2: Payment run, accruals, depreciation. Day 3: FX valuation, IHC netting, CO assessments, WIP/variance. Day 4: Settlement, ML actual costing. Day 5: Reconciliations. Day 6: Close and report.

Q2: How do you handle a late invoice after period close?

If immaterial, post in current period. If material, reopen prior period with approval, post, re-close. Document as a control breakdown.

Q3: Why is subledger-to-GL reconciliation critical?

Detects unauthorised manual postings to reconciliation accounts. Confirms AP subledger = GL vendor recon account. Any difference must be investigated before close.

Q4: How does FX valuation work?

FAGL_FC_VAL revalues open FX items at closing rate. Difference = unrealised FX gain/loss. Reversed at start of next period so settlement rate is used when item clears.

11 Interview & Scenario Practice

Scenario-based questions spanning FI, CO, BL, IHB, and ML.

Answer Framework

The 5-Point Framework

(1) Business context. (2) Configuration / process. (3) Journal entry. (4) Integration points. (5) Common errors and fixes.

Scenario-Based Questions

Scenario 1: A vendor invoice of ₹1,18,000 (18% GST) is posted and paid 30 days later with 2% cash discount. Show both entries.

Invoice (FB60):

Dr Expense / Inventory — ₹1,00,000
Dr GST Input — ₹18,000
Cr Vendor — ₹1,18,000

Payment with discount (F-53):

Dr Vendor — ₹1,18,000
Cr Bank — ₹1,15,640
Cr Cash Discount Received — ₹2,000
Cr GST Adjustment — ₹360 (reversal of input credit on discount)

Config: Payment terms (OBB8) with 2%/10 days. Discount calculated on base amount only.

Scenario 2: A production order for 1,000 units costs ₹5,10,000 actual; standard is ₹5,00,000. How is the variance calculated and settled?

Variance (KKS1) decomposed into:

Input price variance (material purchase price)
Input quantity variance (more material used)
Resource usage variance (more hours)
Remaining variance (overhead)

Settlement (KO88): Dr Variance ₹10,000 / Cr Production Order ₹10,000. Order balance → zero.

Scenario 3: Vendor reconciliation account doesn't match AP subledger. How do you investigate?

Steps:

Compare FBL1N (subledger) to FAGLL03 (GL recon account).
Filter GL for manual document types (SA, DR) — direct postings to recon accounts are usually the cause.
Check for parked/blocked documents, reversal errors.
Reverse or correct. Recommend field status group that blocks direct posting.

Scenario 4: Explain how EBS auto-matches a customer payment.

Three-layer matching:

Interpretation algorithms identify transaction type from bank code/text.
Posting rules define which algorithms to run and in what order.
Search algorithms find matching open item by invoice number, amount, customer code.

If matched → auto-cleared. If not → goes to FEBAN for manual processing.

Scenario 5: ABC Group has 3 subsidiaries with mutual payables/receivables. How does IHC netting reduce transactions?

Without IHC: 3 gross cross-border payments.

With IHC netting: Subsidiaries post to IHC instead of each other. IHC computes net positions:

IN01: −50,000 (net pay)
SG01: +5,00,000 (net receive)
DE01: −4,50,000 (net pay)

Only 2 net payments made — 60–80% reduction. FX exposure also centralised.

Scenario 6: A raw material is standard ₹100/kg but purchased at ₹105/kg. 1,000 kg bought, 800 kg consumed. How does ML handle the price difference?

Purchase entry:

Dr Inventory — ₹1,00,000 (at standard)
Dr Price Difference (ML) — ₹5,000
Cr Vendor — ₹1,05,000

Month-end CKMLCP settlement distributes ₹5,000:

Inventory (200 kg remaining) — 20% → ₹1,000
COGS (800 kg consumed) — 80% → ₹4,000

ML account cleared. Inventory revalued to actual cost.

Scenario 7: Client wants to migrate ECC → S/4HANA. Top 3 FI/CO considerations?

Custom reports referencing COSP/COSS/COEP/CE1xxxx — must be rewritten against ACDOCA. Budget significant time.
New GL + Parallel ledgers — mandatory in S/4HANA. If on classic GL, full migration required.
Material Ledger activation — mandatory in S/4HANA. If not currently used, full ML implementation + historical valuation migration needed. Often the longest workstream.

Additional: Business Partner migration (customer/vendor), FSCM Credit Management, classic CO-PA → account-based CO-PA.

Rapid-Fire Questions

FI vs CO?

FI = external/legal/statutory. CO = internal/management/cost objects.

Primary vs secondary cost element?

Primary = has FI GL counterpart. Secondary = CO-only (assessments, allocations).

Distribution vs assessment?

Distribution preserves original cost elements. Assessment consolidates under a secondary CE.

Cost center vs profit center?

Cost center = collects costs by department. Profit center = internal P&L and balance sheet.

House Bank vs Account ID?

House Bank = banking partner (HDFC). Account ID = specific account within that bank. Together they form BANKL + BNKACC.

EBS vs Lockbox?

EBS = processes the entire bank statement (all transactions). Lockbox = specific tool for automated customer receipt matching at high volume.

Cash Position vs Liquidity Forecast?

Cash Position = snapshot (today). Liquidity Forecast = projection (future).

What is IHC?

In-House Cash — group internal bank. Centralises cash, nets intercompany payments, reduces external transactions.

Material Ledger purpose?

Records actual cost of materials in multiple currencies and views. Enables actual costing and price difference settlement.

Standard price vs moving average price?

Standard (S) = fixed, differences tracked in ML. Moving Average (V) = recalculated with every movement, differences absorbed immediately.

Universal Journal?

ACDOCA — single table for FI + CO + AA + ML + CO-PA in S/4HANA. Eliminates FI-CO reconciliation.

What changed in ML for S/4HANA?

ML becomes mandatory. Integrated into ACDOCA. MLIT replaces older ML tables for most reporting.

← Back to SAP FICO Learning