Quick Answer — SAP FICO T-Codes
- SAP FICO has 100+ transaction codes spanning FI (Financial Accounting) and CO (Controlling) — from daily posting (FB50, FB60) to configuration (OB52, SPRO) to reporting (FBL3N, FS10N).
- Most daily posting tcodes are unchanged in S/4HANA — FB50, FB60, FB70, F-28, F-53, F110 all work exactly as in ECC.
- Master data tcodes changed significantly — FS01/02/03 → FS00; XD01/XK01 → BP; FD32 → UKM_BP; KA01/02/03 deprecated entirely.
- Reporting has a new preferred layer — FAGLL03H replaces FBL3N as the primary GL line item report in S/4HANA, reading the Universal Journal (ACDOCA) directly.
- ECC end-of-support is December 2027 — understanding these tcode changes now is essential for any FICO consultant or student entering the job market.
25+
FI-GL Tcodes
18+
AP Tcodes
14+
AR Tcodes
12+
Asset Accounting
18+
CO Tcodes
20+
S/4 Changes
Key Takeaways
1
FB50, FB60, FB70, and F110 are unchanged in S/4HANA — the most-used daily posting and payment transactions in SAP FICO work identically in ECC and S/4HANA.
2
FS01/FS02/FS03 → FS00 and KA01/KA02/KA03 are fully deprecated — GL account and cost element master data are unified in FS00 in S/4HANA; every P&L GL account is automatically a cost element.
3
FAGLL03H replaces FBL3N as the primary GL reporting transaction — it reads the Universal Journal (ACDOCA) directly in real time and shows ledger views that FBL3N cannot display.
4
XD01, XK01, FK01, VD01 are all replaced by BP — the Business Partner transaction is the single master data transaction for all vendors and customers in S/4HANA.
5
AJRW is deprecated in S/4HANA — Asset Accounting fiscal year change is automatic in New Asset Accounting; AJAB and AFAB run without the prior AJRW step.
Before You Start
How to Read This Guide — Status Badges, ECC vs S/4HANA
SAP FICO spans two major components — FI (Financial Accounting) and CO (Controlling) — each with its own sub-modules, configuration areas, and reporting landscape. This guide covers every meaningful tcode across all of them, in both SAP ECC 6.0 and SAP S/4HANA, and tells you exactly what changed, what was replaced, and what to use in a modern S/4HANA system.
Active Works in both ECC and S/4HANA — no change
Deprecated Obsolete in S/4HANA — use the replacement shown
Modified Available but behaviour or scope changed in S/4HANA
S/4 New New tcode introduced in S/4HANA, not present in ECC
SAP ECC — The Legacy Stack
- Separate FI and CO document tables (BKPF/BSEG, COEP)
- Separate GL account master (FS01/02/03) and cost element (KA01/02/03)
- Separate customer (XD01) and vendor (XK01) master transactions
- Credit management via FD32 / FD31 / FD33
- Reporting reads from aggregated totals tables (GLT0, KNC1, LFC1)
- Asset fiscal year change requires manual AJRW run
- FBL3N reads BSEG — shows entry view only
SAP S/4HANA — The New Architecture
- Universal Journal (ACDOCA) — single table for all FI and CO postings
- GL account = cost element — managed centrally via FS00
- Business Partner (BP) replaces all customer and vendor master tcodes
- Credit management via SAP Credit Management UKM (UKM_BP, UKM_CASE)
- Reporting reads ACDOCA directly — real-time, no aggregation lag
- Asset fiscal year change is automatic in New Asset Accounting
- FAGLL03H reads ACDOCA — shows full ledger view including extension ledgers
ECC end-of-support: December 31, 2027. Every FICO consultant and student working today will encounter S/4HANA within the next 12–24 months — either through new implementations or through employer migrations. The tcode changes documented on this page are the most practical knowledge gap to close right now. VoiSAP's FICO training covers both ECC and S/4HANA environments so you are ready for either.
Financial Accounting — General Ledger
FI-GL Transaction Codes — Master Data, Posting, Reporting
FI-GL is the core of Financial Accounting — every financial posting ultimately hits the General Ledger. This is also where the biggest S/4HANA architecture change lands: the Universal Journal (ACDOCA) replaces multiple separate GL tables, which reshapes the reporting tcode landscape while leaving daily posting tcodes untouched.
GL Account Master Data
GL Master Data Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FS00 | GL Account Master — Create, Change, Display (Central) | Active | The primary GL account transaction in S/4HANA. In S/4HANA it also manages the CO-relevant fields (former cost element data) in one place. Replaces FS01/02/03 entirely. |
| FS01 / FS02 / FS03 | Create / Change / Display GL Account (chart of accounts level) | Deprecated | Replaced by FS00 in S/4HANA. The three separate transactions are merged into a single central maintenance screen. Do not use in S/4HANA. |
| FSP0 | GL Account at Chart of Accounts Level (Display/Change) | Active | Available in S/4HANA. Used to view/change chart-of-accounts-level GL data. Less commonly used than FS00. |
| FSS0 | GL Account at Company Code Level (Display/Change) | Active | Available in S/4HANA. Company-code-level GL account maintenance. |
| OB13 | Define Chart of Accounts | Active | Configuration. Unchanged in S/4HANA. Defines chart of accounts properties (INT, CANA, etc.). |
| OBD4 | Define GL Account Groups | Active | Defines account groups (Assets, Liabilities, Revenue etc.) and number ranges. Unchanged. |
| OB40 | Define Accounts for Tax Postings | Active | Tax GL account assignment. Unchanged in S/4HANA. |
| OBY6 | Copy Company Code (GL accounts) | Active | Copies GL account data from one company code to another. Available in S/4HANA. |
GL Document Posting
GL Posting Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FB50 | Enter GL Account Document (Enjoy — single screen) | Active | The primary GL journal entry tcode. Unchanged in S/4HANA. The Fiori equivalent is 'Post General Journal Entries' (F1306) but FB50 via SAP GUI remains fully supported. |
| F-02 | Enter GL Account Posting (Complex / header-first) | Active | Classic complex posting transaction. More flexible than FB50 for entries requiring specific posting keys or intercompany scenarios. Unchanged in S/4HANA. |
| FB08 | Reverse Document | Active | Reverses a posted FI document. Unchanged. In S/4HANA, reversal also reverses the ACDOCA line items. |
| FBB1 | Post Foreign Currency Valuation (Manual) | Active | Manual FX valuation posting. Available in S/4HANA though FAGL_FC_VAL handles periodic automated FX valuation. |
| F-03 | Clear GL Account | Active | Manual clearing of open GL items (e.g., GR/IR clearing account). Unchanged in S/4HANA. |
| F.13 | Automatic Clearing (GL, AP, AR) | Active | Mass automatic clearing of open items across GL, vendor, and customer accounts. Unchanged in S/4HANA. Critical for period-end close. |
| FB50L | Enter GL Account Document — Ledger-Specific | S/4 New | New in S/4HANA. Posts a document to a specific ledger (leading or non-leading) for parallel accounting scenarios. Not available in ECC. |
| GJR2 | Reverse Journal Entry (Universal Journal) | S/4 New | New S/4HANA reversal transaction specifically for Universal Journal entries. Supports ledger-specific reversals. |
GL Reporting & Display
GL Reporting Transactions9 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FS10N | GL Account Balance Display | Active | Standard GL balance view — period totals, cumulative balance, year-to-date. Active in S/4HANA. Reads from FAGLFLEXT (New GL totals table). |
| FBL3N | GL Account Line Item Display | Modified | Still available in S/4HANA but only shows entry view — does not show the full ledger view or extension ledger data. FAGLL03H is the preferred replacement in S/4HANA deployments. |
| FAGLL03H | GL Account Line Items — Universal Journal View | S/4 New | The primary S/4HANA GL line item report. Reads directly from ACDOCA. Shows full ledger view, profit centre, segment, functional area — all dimensions in one report. Replaces FBL3N for new S/4HANA work. |
| FAGLB03 | GL Account Balance (New GL / Ledger-Specific) | Active | Balance display with ledger selection — essential for parallel accounting. Available in both New GL (ECC) and S/4HANA. |
| S_ALR_87012284 | Financial Statements (Balance Sheet and P&L) | Active | The most-used financial statement ABAP report. Unchanged in S/4HANA. SAP Fiori provides a modern interactive equivalent reading from ACDOCA. |
| GR55 | Execute Report Group (Report Painter / Writer) | Active | Financial reporting via Report Painter. Unchanged in S/4HANA. Used for custom income statement and balance sheet layouts. |
| F.05 | Foreign Currency Valuation (GL) | Modified | Available in S/4HANA but FAGL_FC_VAL is the preferred foreign currency valuation transaction for New GL and S/4HANA parallel accounting scenarios. |
| FAGL_FC_VAL | Foreign Currency Valuation — New GL | Active | Preferred FX valuation transaction in both New GL (ECC) and S/4HANA. Supports ledger-specific and parallel accounting valuation runs. |
| F.16 | Balance Carryforward (GL) | Active | Year-end GL balance carryforward. Unchanged in S/4HANA. |
GL Configuration (Key Customizing)
GL Configuration Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| SPRO | SAP Implementation Guide (IMG Customizing Entry Point) | Active | The starting point for all configuration in SAP. Unchanged in S/4HANA though the IMG structure contains new and modified entries for S/4HANA-specific configuration. |
| OX02 | Define Company Code | Active | Define company code properties (name, country, currency, fiscal year variant). Unchanged in S/4HANA. |
| OB52 | Maintain Posting Period Variant | Active | The most-used FICO config tcode. Controls which periods are open by account type. Unchanged in S/4HANA. See our posting period error guide → |
| OB29 | Define Fiscal Year Variant | Active | Defines fiscal year calendar (calendar year, non-calendar, 4-4-5 etc.). Unchanged in S/4HANA. |
| OBA7 | Define Document Types | Active | Configure document types (SA, KR, DR, AB etc.) and their properties. Unchanged in S/4HANA. |
| OB41 | Define Posting Keys | Active | Posting key properties (01=customer debit, 31=vendor credit, 40=GL debit, 50=GL credit etc.). Unchanged in S/4HANA. |
| OBD1 | Define Field Status Groups | Active | Controls which fields are required/optional/suppressed on posting screens. Unchanged in S/4HANA. |
| OBC4 | Assign Field Status Variant to Company Code | Active | Unchanged in S/4HANA. |
Trainer insight — the biggest S/4HANA GL shift: In ECC, month-end GL reporting meant waiting for aggregation jobs to run and update GLT0 totals tables before FBL3N results were reliable. In S/4HANA, FAGLL03H reads ACDOCA in real time — every posting is immediately visible at full drill-down detail, no aggregation lag, no reconciliation between FI and CO. This is the operational benefit that makes S/4HANA reporting genuinely faster, not just a rebrand.
Financial Accounting — Accounts Payable
FI-AP Transaction Codes — Vendor Invoice, Payment, Clearing
Accounts Payable is where the most significant S/4HANA master data disruption happens — all vendor master transactions (FK01, MK01, XK01) disappear in favour of the unified Business Partner (BP). Day-to-day AP posting transactions (FB60, F110) are completely unchanged. If you're used to ECC AP, you'll feel at home in S/4HANA for daily work — but onboarding a new vendor now happens in a fundamentally different transaction. For the procurement side of AP — PO-based vendor invoices via MIRO, goods receipts via MIGO, and blocked invoice release via MRBR — see the SAP MM T-Codes — Invoice Verification section.
Vendor Master Data
Vendor Master Transactions5 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FK01 / FK02 / FK03 | Create / Change / Display Vendor (FI accounting view) | Deprecated | Replaced by BP in S/4HANA. FI vendor data is now part of the Business Partner record. Cannot be used for new vendor creation in S/4HANA. |
| MK01 / MK02 / MK03 | Create / Change / Display Vendor (MM Purchasing view) | Deprecated | Replaced by BP in S/4HANA. MM purchasing vendor data is also managed via Business Partner — all vendor views (FI and MM) are unified under one BP record. |
| XK01 / XK02 / XK03 | Create / Change / Display Vendor (Central — all views) | Deprecated | The central vendor creation tcode in ECC. Replaced entirely by BP in S/4HANA. |
| BP | Business Partner — Create, Change, Display (S/4HANA) | S/4 New | The single vendor/customer master transaction in S/4HANA. Replaces XD01, XK01, FK01, MK01, VD01. One BP record holds FI vendor data, MM purchasing data, SD customer data, and credit management data across all views. |
| FK10N | Vendor Account Balance Display | Active | Vendor balance overview — open items, cleared items, balance carryforward. Active in S/4HANA. |
Vendor Invoice & Payment Posting
AP Posting & Payment Transactions10 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FB60 | Enter Incoming Invoice (Vendor — without Purchase Order) | Active | Core AP invoice entry for non-PO invoices (rent, utilities, professional fees). Unchanged in S/4HANA. Fiori equivalent: 'Create Supplier Invoice' (F0859). |
| FB65 | Enter Incoming Credit Memo (Vendor) | Active | Vendor credit memo entry. Unchanged in S/4HANA. |
| F-43 | Enter Vendor Invoice (Complex / Classic) | Active | Header-first invoice posting with full posting key control. Used for complex AP entries not easily handled in FB60. Unchanged in S/4HANA. |
| F-41 | Enter Vendor Credit Memo (Complex) | Active | Classic vendor credit memo. Unchanged in S/4HANA. |
| F-53 | Post Outgoing Payment (Manual) | Active | Manual vendor payment with open item clearing. Unchanged in S/4HANA. Used when a specific invoice must be cleared manually rather than via F110. |
| F-58 | Payment with Printout | Active | Post payment and generate cheque/remittance simultaneously. Unchanged in S/4HANA. |
| F110 | Automatic Payment Program (Payment Run) | Active | The mass payment run transaction — processes all due vendor invoices per configured payment methods. Unchanged in S/4HANA. FBZP remains the configuration transaction. Fiori: 'Manage Automatic Payments' (F2762). |
| FBZP | Configure Automatic Payment Program | Active | Configuration of payment methods, house banks, company code payment settings, and ranking order. Unchanged in S/4HANA. |
| FBL1N | Vendor Line Item Display | Modified | Active in S/4HANA but shows only entry view. FBL1H is the Universal Journal vendor line item display preferred for S/4HANA reporting. Both are available. |
| FBL1H | Vendor Line Items — Universal Journal View | S/4 New | New S/4HANA vendor line item display reading from ACDOCA. Shows full ledger, profit centre, and segment data alongside vendor line items. Preferred over FBL1N in S/4HANA. |
AP Configuration
AP Configuration Transactions5 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| OBD3 | Define Vendor Account Groups | Active | Vendor account group configuration (domestic, foreign, one-time). In S/4HANA, account groups are assigned within the Business Partner grouping concept. |
| OBAS | Define Payment Terms | Active | Configure payment terms (Z001=14 days 2% discount/30 days net etc.). Unchanged in S/4HANA. |
| FBN1 | Define Document Number Ranges (FI) | Active | FI document number range maintenance. Unchanged in S/4HANA. |
| OB10 | Define Tolerance Groups for Employees (GL) | Active | Tolerance limits for posting amounts and payment differences. Unchanged in S/4HANA. |
| OBB8 | Define Payment Terms (Detailed) | Active | Detailed payment terms configuration. Unchanged in S/4HANA. |
The Business Partner change explained simply: In ECC, creating a vendor required up to three separate tcodes — FK01 for FI view, MK01 for MM purchasing view, and XK01 if you needed both at once. In S/4HANA, you do it all in one transaction: BP. You create a BP record, assign it the role "Vendor" (FI) and "Supplier" (MM), and maintain all views in one unified screen. Less navigation, one record, no synchronisation issues between FI and MM vendor data. This is the CVI (Customer Vendor Integration) change.
Financial Accounting — Accounts Receivable
FI-AR Transaction Codes — Customer Invoice, Collection, Credit Management
Accounts Receivable mirrors the AP disruption for customer master data — XD01, VD01 are replaced by BP. Additionally, the entire credit management architecture shifts from the classic FD32 / VKM1 approach to the SAP Credit Management UKM component. Day-to-day AR posting (FB70, F-28) is unchanged.
Customer Master Data & Credit Management
Customer Master & Credit Management8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| XD01 / XD02 / XD03 | Create / Change / Display Customer (Central) | Deprecated | Replaced by BP in S/4HANA. Customer master — FI, SD sales area, and credit management views — are all now managed in the Business Partner. |
| VD01 / VD02 / VD03 | Create / Change / Display Customer (Sales & Distribution view) | Deprecated | Replaced by BP in S/4HANA. SD sales area customer data is now maintained as a BP role assignment. |
| FD01 / FD02 / FD03 | Create / Change / Display Customer (FI view only) | Deprecated | FI-only customer master. Replaced by BP in S/4HANA. |
| FD32 | Change Customer Credit Management Data | Deprecated | Replaced by UKM_BP in S/4HANA. The entire credit management engine moved to the SAP Credit Management (UKM) component with S/4HANA. |
| FD31 / FD33 | Display Customer Credit Overview / Credit Management | Deprecated | Replaced by UKM_COMMITMENTS (credit exposure) and UKM_BP in S/4HANA. |
| UKM_BP | Business Partner Credit Management (S/4HANA) | S/4 New | Central credit management transaction in S/4HANA. Set credit limits, credit segments, and risk categories per business partner. Replaces FD31/FD32/FD33. |
| UKM_CASE | Credit Case Processing (S/4HANA) | S/4 New | Processes credit-blocked sales orders in S/4HANA. Replaces VKM1/VKM3 for credit release workflow. |
| UKM_COMMITMENTS | Display Credit Exposure by Business Partner | S/4 New | Real-time credit exposure display in S/4HANA — shows open orders, deliveries, and invoices in one view. Replaces F.31 and FD33. |
AR Invoice, Payment & Reporting
AR Posting & Reporting Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FB70 | Enter Outgoing Invoice (Customer — without Sales Order) | Active | Core AR customer invoice entry for non-SD billing. Unchanged in S/4HANA. Fiori: 'Create Customer Invoice' (F2222). |
| FB75 | Enter Customer Credit Memo | Active | Customer credit memo entry. Unchanged in S/4HANA. |
| F-28 | Post Incoming Payment (Manual) | Active | Primary manual customer payment transaction. Post cash received and clear open customer invoices simultaneously. Unchanged in S/4HANA. |
| F-32 | Clear Customer Account (Manual) | Active | Manual clearing of open customer items without a new payment posting. Unchanged in S/4HANA. |
| FBL5N | Customer Line Item Display | Modified | Active in S/4HANA (entry view only). FBL5H is the Universal Journal customer line item display preferred in S/4HANA deployments. |
| FBL5H | Customer Line Items — Universal Journal View | S/4 New | New S/4HANA customer line item report reading from ACDOCA. Shows full ledger, profit centre, and segment data. Preferred over FBL5N in S/4HANA. |
| FD10N | Customer Account Balance Display | Active | Customer balance overview. Active in S/4HANA. |
| F.31 | Credit Overview (Customer) | Deprecated | Replaced by UKM_COMMITMENTS in S/4HANA for credit exposure reporting. |
Financial Accounting — Asset Accounting
FI-AA Transaction Codes — Asset Master, Depreciation, Year-End
Asset Accounting (FI-AA) in S/4HANA uses "New Asset Accounting" — a complete redesign that integrates asset postings directly into the Universal Journal. The biggest practical change for FICO professionals is the elimination of the AJRW fiscal year change step, and the introduction of OAAQ for specifying the last closed year. All day-to-day asset master and transaction tcodes are unchanged.
Asset Master Data
Asset Master Transactions6 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| AS01 / AS02 / AS03 | Create / Change / Display Asset Master | Active | Standard asset master creation/change/display. Unchanged in S/4HANA. Asset master structure is the same but now linked to ACDOCA postings. |
| AS05 | Block Asset Master | Active | Block an asset to prevent further postings. Unchanged in S/4HANA. |
| AS06 | Mark Asset for Deletion | Active | Mark an asset as a deletion candidate (fully depreciated, retired). Unchanged. |
| AR01 | Asset Explorer | Active | Displays asset values, depreciation areas, and posting history in a tree view. Unchanged in S/4HANA — one of the most useful asset reporting tcodes. |
| AW01N | Asset Viewer | Active | Enhanced asset value display. Active in S/4HANA. |
| AS91 | Create Legacy Asset (Data Transfer) | Active | Used during data migration to upload legacy asset values. Still relevant for S/4HANA migration projects. |
Asset Transactions, Depreciation & Year-End
Asset Posting, Depreciation & Closing10 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| F-90 | Acquisition with Vendor (Asset Purchase with PO) | Active | External asset acquisition posting against vendor invoice. Unchanged in S/4HANA. |
| F-91 | Asset Acquisition without Vendor | Active | Internal asset acquisition (construction in progress, transfer from another asset). Unchanged. |
| ABUMN | Transfer Asset Within Company Code | Active | Intracompany asset transfer (change cost centre, plant, or asset class). Unchanged in S/4HANA. |
| ABAON | Asset Sale Without Customer | Active | Post asset retirement proceeds without customer invoice. Unchanged. |
| AFAB | Post Depreciation (Periodic Depreciation Run) | Active | The primary depreciation posting transaction. Unchanged in S/4HANA. In New Asset Accounting, AFAB posts directly to ACDOCA — no separate reconciliation with FI needed. |
| AFBP | Depreciation Posting Run Log | Active | Display results of the last AFAB depreciation posting run. Unchanged. |
| AJRW | Asset Accounting Fiscal Year Change | Deprecated | Key deprecation. In ECC, AJRW had to be run before AFAB could post in a new fiscal year. In S/4HANA New Asset Accounting, this step is automatic — AJRW is not required or used. Use OAAQ instead to specify the last closed fiscal year. |
| OAAQ | Specify Last Closed Fiscal Year (New AA) | S/4 New | S/4HANA replacement for AJRW in New Asset Accounting. Specifies which fiscal year is closed for asset accounting, enabling depreciation to post in the next period. |
| AJAB | Asset Year-End Closing | Active | Formal year-end closing for asset accounting — locks prior year asset values. Still required in S/4HANA New Asset Accounting. |
| S_ALR_87011990 | Asset History Sheet | Active | Standard asset history report — shows acquisitions, retirements, depreciation, and book value. Unchanged in S/4HANA. |
AJRW is one of the most common S/4HANA migration surprises. FICO consultants who ran AJRW religiously every December in ECC will often try to run it in S/4HANA and find it either doesn't exist or gives an error. The correct S/4HANA year-end asset process is: run AFAB for the last period of the year → run AJAB for year-end closing → set OAAQ to the closed year. No AJRW required.
New General Ledger & Parallel Accounting
New GL & Parallel Accounting T-Codes — Ledgers, Document Splitting, Segments
New GL (introduced in ECC 6.0) brought document splitting, parallel ledgers, and segment reporting. In S/4HANA, New GL is the default and only GL architecture — there is no "classic GL" option. The transactions from New GL in ECC carry over to S/4HANA with minimal change, though the Universal Journal makes many ledger-specific reporting transactions more powerful.
New GL & Ledger Transactions10 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| FAGLB03 | GL Account Balances (New GL — by Ledger) | Active | Balance display with ledger selection — essential for parallel accounting (IFRS vs local GAAP). Active in S/4HANA. |
| FAGLGVTR | Balance Carryforward (New GL) | Active | Year-end balance carryforward in New GL. Used in both ECC New GL and S/4HANA. |
| FAGL_FC_VAL | Foreign Currency Valuation (New GL) | Active | Preferred FX valuation transaction for New GL and S/4HANA. Supports parallel accounting valuation by ledger. |
| FAGLL03H | GL Account Line Items — Universal Journal | S/4 New | Reads ACDOCA directly. The standard S/4HANA GL line item report with full ledger, segment, profit centre dimensions. Most powerful GL reporting tcode in S/4HANA. |
| FAGLFLEXT | New GL Totals Table (via SE16N) | Modified | FAGLFLEXT is the New GL totals table in ECC. In S/4HANA, ACDOCA is the source of truth — FAGLFLEXT exists for compatibility but real-time balances come from ACDOCA. |
| GJ11 | Period Close — Universal Journal (S/4HANA) | S/4 New | New S/4HANA period-end close cockpit for the Universal Journal. Provides a structured checklist for FI period-end activities. Not available in ECC. |
| GCAC | Account Assignment for Document Splitting | Active | Configuration for document splitting — which dimensions (profit centre, segment, cost centre) are derived on each line item. Active in both New GL (ECC) and S/4HANA. |
| FB50L | Post GL Document — Ledger-Specific | S/4 New | Post a journal entry to a specific non-leading ledger (e.g. IFRS ledger) without affecting the leading ledger. New in S/4HANA for parallel accounting scenarios. |
| FINS_RCLASSIFICATION | Reclassification (Short/Long-Term Liabilities) | S/4 New | New in S/4HANA. Automatic reclassification of balance sheet items between current and non-current for IFRS compliance. Replaces manual period-end reclassification steps. |
| FBRA | Reset Cleared Items | Active | Reset a clearing document to restore open items — useful for error correction. Unchanged in S/4HANA. |
Controlling — Cost Centre Accounting
CO-CCA & Internal Orders — Cost Centre Master, Planning, Allocation
Controlling (CO) is the area where S/4HANA's Universal Journal makes the biggest architectural change: CO and FI are now truly one — every CO posting writes to ACDOCA in real time, eliminating the period-end FI/CO reconciliation that was a major month-end task in ECC. The most significant tcode change: cost element transactions (KA01/KA02/KA03) are gone because cost elements no longer exist as a separate object — every P&L GL account is automatically a primary cost element.
Cost Element — ECC vs S/4HANA (Critical Difference)
Cost Element Transactions — Biggest CO Change in S/4HANA4 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| KA01 / KA02 / KA03 | Create / Change / Display Cost Element | Deprecated | Completely deprecated in S/4HANA. Cost elements no longer exist as a separate master data object. Every P&L GL account IS a cost element in S/4HANA — managed via FS00. This eliminates the "GL account exists but cost element not created" error that was common in ECC. In S/4HANA, if FS00 shows a P&L account, it is automatically available for CO postings. |
| KA06 | Create Secondary Cost Element (ECC) | Deprecated | Secondary cost elements (for internal allocations — assessment, distribution, activity type settlement) are also replaced in S/4HANA. In S/4HANA, secondary cost elements are created directly as GL accounts of type "Secondary Cost" in FS00. |
| KA23 | Display Cost Elements — List | Deprecated | Cost element list display. In S/4HANA, use standard GL account list display or FS00 to find cost-element-relevant GL accounts. |
| FS00 | GL Account Master (includes CO fields in S/4HANA) | Modified | In S/4HANA, FS00 is expanded — the "Cost Element" tab from KA02 is now included within FS00. Assign cost element category, default cost assignment, and CO relevance all from FS00. One tcode rules all. |
Cost Centre Master & Planning
Cost Centre Transactions10 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| KS01 / KS02 / KS03 | Create / Change / Display Cost Centre | Active | Core CO master data. Unchanged in S/4HANA. Cost centre hierarchy, manager assignment, activity type assignment all maintained here. |
| KS12 | Change Cost Centres — Collective Processing | Active | Mass change to multiple cost centres. Unchanged in S/4HANA. |
| KS13 | Cost Centre Master Data List | Active | List report of all cost centres with their attributes. Unchanged in S/4HANA. |
| KSH1 / KSH2 | Create / Change Cost Centre Group (Hierarchy) | Active | Cost centre hierarchy maintenance. Unchanged in S/4HANA. |
| KSB1 | Cost Centre Actual Line Items | Active | Most-used CO reporting tcode. Drill down to individual cost postings per cost centre. In S/4HANA reads from ACDOCA — real-time, no lag. Unchanged tcode, improved data freshness. |
| KSB2 | Cost Centre Commitment Line Items | Active | Commitment line items per cost centre (purchase orders not yet goods-receipted). Unchanged. |
| KS12N | Plan Cost Centre Activity (Budgeting) | Active | Cost centre planning. Unchanged in S/4HANA. S/4HANA also offers SAP Analytics Cloud (SAC) for integrated planning as a modern alternative. |
| KSU5 | Execute Cost Centre Distribution | Active | Periodic cost centre distribution cycle execution. Unchanged in S/4HANA. |
| KSV5 | Execute Cost Centre Assessment | Active | Periodic cost centre assessment cycle. Unchanged in S/4HANA. |
| KB11N | Enter Manual Cost Allocation | Active | Manual reposting of costs between cost centres/orders. Unchanged in S/4HANA. |
Internal Orders
Internal Order Transactions6 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| KO01 / KO02 / KO03 | Create / Change / Display Internal Order | Active | Internal order master data — unchanged in S/4HANA. Internal orders used for temporary cost collection (events, projects, capex tracking). |
| KO88 | Settle Internal Order (Actual) | Active | Period-end internal order settlement to cost centres, GL accounts, or assets. Unchanged in S/4HANA. |
| KOB1 | Internal Order Actual Line Items | Active | Line item report for internal order costs. In S/4HANA reads from ACDOCA — real-time. Unchanged tcode. |
| CO43 | Actual Overhead Calculation (Order/Cost Object) | Active | Apply overhead rates to production orders and cost objects. Unchanged in S/4HANA. |
| KO8G | Settle Internal Orders — Collective Processing | Active | Mass settlement of multiple internal orders. Unchanged in S/4HANA. |
| KOH1 / KOH2 | Create / Change Internal Order Group | Active | Internal order hierarchy. Unchanged in S/4HANA. |
The cost element elimination — why it matters: In ECC, every FICO consultant has encountered the error "No cost element exists for GL account XXXXXX" — because a GL account was created in FI (FS01) but nobody created the corresponding cost element in CO (KA01). This two-step process caused countless project delays and support tickets. In S/4HANA, this error is impossible — because the concept no longer exists. FS00 creates the GL account and the CO relevance in one step. This is one of the most practical simplifications for FICO consultants on S/4HANA projects.
Controlling — Profitability Analysis
CO-PA T-Codes — Account-Based vs Costing-Based, Reporting, S/4HANA Change
CO-PA (Profitability Analysis) undergoes a significant architectural shift in S/4HANA. In ECC, most companies used Costing-Based CO-PA (which maintained its own separate database). In S/4HANA, Account-Based CO-PA is mandatory and is fully integrated with the Universal Journal — every revenue and cost posting automatically creates a CO-PA line item in ACDOCA in real time, with no period-end data transfer step needed. Costing-Based CO-PA can still be activated alongside it, but the strategic direction is account-based.
CO-PA Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| KE30 | Execute Profitability Report | Active | Primary CO-PA reporting tcode. In S/4HANA with account-based CO-PA, KE30 reports read from ACDOCA — real-time profitability by customer, product, region, sales org. Unchanged tcode, significantly improved data foundation. |
| KE24 | CO-PA Line Item Display (Actual) | Active | Drill down to individual CO-PA postings. In S/4HANA account-based CO-PA, these are ACDOCA line items with profitability characteristics (customer, product, division). Unchanged tcode. |
| KE4S | PA Transfer Structure (SD-to-CO-PA Value Flow) | Active | Configuration of which SD condition types transfer to which CO-PA value fields. Active in S/4HANA for costing-based CO-PA. In account-based CO-PA, SD revenue flows automatically via the Universal Journal. |
| KEA0 | Define Operating Concern | Active | Operating concern configuration — the top level of CO-PA structure defining characteristics and value fields. Active in S/4HANA, though account-based CO-PA uses the Universal Journal structure rather than custom value fields. |
| KES1 | Define CO-PA Characteristics | Active | Define profitability characteristics (customer group, product hierarchy, country etc.) for costing-based CO-PA. Active in S/4HANA. |
| KEDR | CO-PA Top-Down Distribution | Active | Distribute planned/actual costs from high-level to detail CO-PA segments. Active in S/4HANA. |
| KEND | CO-PA Realignment Run | Active | Realign CO-PA characteristics after master data changes. Active in S/4HANA. |
| KE1S | Transfer Sales Orders to CO-PA (Costing-Based) | Modified | In S/4HANA with account-based CO-PA, sales orders flow automatically to CO-PA via the Universal Journal — this periodic transfer step is not required for account-based CO-PA. Relevant only if costing-based CO-PA is also active. |
Account-Based CO-PA vs Costing-Based — the one-line summary: Costing-based CO-PA has custom value fields and a separate database — powerful but requires period-end data transfer and reconciliation. Account-based CO-PA uses GL accounts and ACDOCA — real-time, always reconciled with FI, no separate database, no transfer step. S/4HANA mandates account-based CO-PA. If you learned CO-PA in ECC with costing-based, be aware the reporting structure looks different in S/4HANA — the profitability is real-time in the GL rather than in a separate CO-PA database.
Controlling — Product Costing
CO-PC T-Codes — Standard Cost Estimate, Actual Costing, Material Ledger
Product Costing (CO-PC) transaction codes are among the most stable in the FICO landscape — CK11N, CK40N, CKMLCP are unchanged in S/4HANA. The major change is that in S/4HANA, the Material Ledger is mandatory — it was optional in ECC but S/4HANA requires it for all material valuation. This makes actual costing and inventory valuation more integrated and eliminates the material price differences that used to require separate reconciliation.
Product Costing & Material Ledger Transactions12 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| CK11N | Create Standard Cost Estimate (Single Material) | Active | The primary product costing transaction. Creates standard cost estimate for a single material. Unchanged in S/4HANA. |
| CK13N | Display Standard Cost Estimate | Active | Display an existing cost estimate. Unchanged in S/4HANA. |
| CK40N | Edit Costing Run (Mass Standard Cost Estimate) | Active | Mass costing run — create, mark, and release standard costs for hundreds of materials. Unchanged in S/4HANA. |
| CKR1 | Reorganise Standard Cost Estimates | Active | Archive or delete old cost estimates. Unchanged in S/4HANA. |
| CKMLCP | Material Ledger Closing Cockpit (Actual Costing) | Active | Critical for actual costing month-end. Runs the actual costing sequence: single-level price determination → multi-level price determination → revaluation of consumption. In S/4HANA, Material Ledger is mandatory — every company will use this transaction. |
| CKM3N | Material Price Analysis (Material Ledger) | Active | Analyse actual costs vs standard costs at material level. Unchanged in S/4HANA. |
| CKMVFM | Manage Material Ledger Documents | Active | Material Ledger document management. Unchanged in S/4HANA. |
| CO88 | Settle Production Orders — Actual | Active | Settle production order variances to CO-PA and material ledger. Unchanged in S/4HANA. |
| CKMVFM | Material Ledger Document Display | Active | Display material ledger documents. Unchanged in S/4HANA. |
| MR21 | Price Change (Change Material Price Manually) | Active | Manual material price change. In S/4HANA with mandatory Material Ledger, MR21 works in conjunction with the Material Ledger price determination. Unchanged tcode. |
| OKC2 | Maintain Allocation Structure (Settlement Rules) | Active | Configuration of cost object settlement rules — how costs settle from production orders to finished goods inventory. Unchanged in S/4HANA. |
| OKGS | Define Overhead Key (Costing Sheet) | Active | Configuration of overhead costing sheets for overhead rate application. Unchanged in S/4HANA. |
The Migration Reference
Complete SAP FICO ECC → S/4HANA T-Code Change Summary
This is the single-page reference every FICO consultant or student migrating from ECC to S/4HANA needs. Every deprecated, modified, or new tcode from this entire guide in one consolidated table.
All FICO ECC → S/4HANA Changes20+ changes
| ECC T-Code | ECC Function | S/4HANA Status | S/4HANA Replacement |
|---|---|---|---|
| FS01/FS02/FS03 | Create/Change/Display GL Account | Deprecated | FS00 — central GL account maintenance (also covers CO cost element fields) |
| FK01/FK02/FK03 | Create/Change/Display Vendor (FI) | Deprecated | BP — Business Partner (all vendor views) |
| MK01/MK02/MK03 | Create/Change/Display Vendor (MM) | Deprecated | BP — Business Partner (all vendor views) |
| XK01/XK02/XK03 | Create/Change/Display Vendor (Central) | Deprecated | BP — Business Partner |
| XD01/XD02/XD03 | Create/Change/Display Customer (Central) | Deprecated | BP — Business Partner |
| VD01/VD02/VD03 | Create/Change/Display Customer (SD) | Deprecated | BP — Business Partner |
| FD01/FD02/FD03 | Create/Change/Display Customer (FI) | Deprecated | BP — Business Partner |
| FD31/FD32/FD33 | Display/Change/Display Credit Management | Deprecated | UKM_BP (credit limits), UKM_CASE (credit cases), UKM_COMMITMENTS (exposure) |
| F.31 | Credit Overview | Deprecated | UKM_COMMITMENTS — real-time credit exposure in S/4HANA |
| KA01/KA02/KA03 | Create/Change/Display Cost Element | Deprecated | FS00 — P&L GL accounts ARE cost elements in S/4HANA; no separate object |
| KA06 | Create Secondary Cost Element | Deprecated | FS00 — create GL account with type "Secondary Cost" in S/4HANA |
| AJRW | Asset Accounting Fiscal Year Change | Deprecated | OAAQ — specify last closed fiscal year (automatic in New AA) |
| FBL3N | GL Account Line Item Display | Modified | FAGLL03H preferred — reads ACDOCA, shows full ledger view. FBL3N still works but entry view only. |
| FBL1N | Vendor Line Item Display | Modified | FBL1H preferred in S/4HANA — Universal Journal vendor view |
| FBL5N | Customer Line Item Display | Modified | FBL5H preferred in S/4HANA — Universal Journal customer view |
| F.05 | Foreign Currency Valuation | Modified | FAGL_FC_VAL preferred for New GL and S/4HANA parallel accounting FX valuation |
| KE1S | Transfer Sales Orders to CO-PA | Modified | Not required for account-based CO-PA in S/4HANA — revenue flows automatically via ACDOCA |
| — | — (New in S/4HANA) | S/4 New | New tcodes: BP, UKM_BP, UKM_CASE, UKM_COMMITMENTS, FAGLL03H, FBL1H, FBL5H, OAAQ, GJ11, FB50L, GJR2, FINS_RCLASSIFICATION, SCDD |
How to find deprecated tcodes in your own S/4HANA system: Run program PROFGEN_CORR_REPORT_2 via SE38 — it lists all transactions deleted in S/4HANA vs ECC with their automatic replacements. Also query table PRGN_CORR2 via SE16N for the old-to-new tcode mapping. SAP Note 2270335 covers FICO-specific tcode changes in S/4HANA Finance in detail.
Related FICO Guides on VoiSAP
Quick Answers
SAP FICO T-Code FAQ — 20 Questions Answered
For SAP FICO beginners, the essential transaction codes to master are:
FS00 (GL account master), FB50 (GL journal entry), FB60 (vendor invoice), FB70 (customer invoice), F-28 (incoming customer payment), F-53 (outgoing vendor payment), F110 (automatic payment run), F.13 (automatic clearing), OB52 (posting period control), FS10N (GL account balance), FBL1N (vendor line items), FBL3N (GL line items), FBL5N (customer line items), and SPRO (customizing). In S/4HANA, add BP and FAGLL03H.The major SAP FICO tcode changes in S/4HANA: (1)
FS01/02/03 → FS00; (2) FK01/MK01/XK01 → BP; (3) XD01/VD01/FD01 → BP; (4) FD32/FD31/FD33 → UKM_BP/UKM_CASE/UKM_COMMITMENTS; (5) KA01/KA02/KA03 deprecated — cost elements merged into GL accounts via FS00; (6) AJRW deprecated — asset fiscal year change is automatic in New Asset Accounting; (7) FBL3N still works but FAGLL03H is preferred for Universal Journal reporting.Yes,
FB50 (Enter GL Account Document) is fully active and unchanged in SAP S/4HANA. It remains the primary GL journal entry transaction. All core FICO daily posting transactions — FB50, FB60, FB70, F-02, F-43, F-28, F-53, F110 — are unchanged in S/4HANA. Deprecations affect master data transactions and some reporting, not daily postings.In SAP S/4HANA,
FS01 (Create GL Account), FS02 (Change), and FS03 (Display) are replaced by the single central transaction FS00. FS00 handles all GL account management in one screen — at both chart of accounts level and company code level. In S/4HANA, FS00 is further enhanced to include the controlling fields that used to be maintained separately in cost element transactions (KA02) — so FS00 now manages both the FI GL account and the CO cost element data in one place.OB52 is the SAP FICO transaction for maintaining posting period variants. It controls which fiscal periods are open for posting, by account type: A (assets), D (customers), K (vendors), S (GL accounts), M (materials). When users get "Posting period XXXX/YYYY is not open for account type K," an authorized user opens the relevant period in OB52. It is one of the most used FICO configuration transactions and is unchanged in S/4HANA. See our full posting period error guide.FBL3N is the classic ECC GL line item display — it reads from BSEG/GLT0 and shows only the "entry view" of documents. In S/4HANA, FBL3N still works but is limited. FAGLL03H is the new Universal Journal GL line item display that reads directly from ACDOCA — it shows the full ledger view including extension ledger data, parallel accounting values, profit centre, segment, functional area, and CO assignments. FAGLL03H is the preferred GL reporting transaction for all new S/4HANA work and gives far richer analytical detail than FBL3N.In SAP S/4HANA,
FD32 (Change Customer Credit Management) is replaced by UKM_BP. The full replacement mapping is: FD31 → UKM_COMMITMENTS (credit exposure display); FD32 → UKM_BP (credit limit and risk category maintenance); FD33 → UKM_BP; VKM1/VKM3 (blocked sales documents) → UKM_CASE; F.31 (credit overview) → UKM_COMMITMENTS. SAP Credit Management (UKM) is a separate module from FI in S/4HANA — it integrates with BP and allows rule-based, automated credit decisions.In SAP S/4HANA,
KA01, KA02, and KA03 are deprecated because cost elements no longer exist as a separate master data object. S/4HANA eliminated the concept: every P&L GL account is automatically a primary cost element, and secondary cost elements are created as GL accounts of type "Secondary Cost" in FS00. This eliminates the classic ECC problem of "GL account exists but cost element missing" — in S/4HANA, if the GL account exists and is a P&L type, it is automatically available for CO postings without any additional setup.Yes,
F110 (Automatic Payment Program) is completely unchanged in SAP S/4HANA and remains the primary transaction for mass vendor and customer payment runs. Configuration via FBZP is also unchanged. The only difference is downstream — payment documents post to the Universal Journal (ACDOCA) rather than separate BKPF/BSEG tables, but from the user perspective F110 operates identically to ECC.In ECC,
AJRW (Asset Accounting Fiscal Year Change) had to be run at year-end before AFAB could post depreciation in the new fiscal year. It was a mandatory step in ECC asset accounting. In S/4HANA with New Asset Accounting, AJRW is deprecated because the Universal Journal handles fiscal year transitions automatically — there is no separate "year change" step needed. Instead, use OAAQ to specify which fiscal year is last closed for asset accounting, then run AFAB normally. Many FICO consultants migrating from ECC try to run AJRW and receive an error — this is expected.The Universal Journal (table ACDOCA) is the single accounting document table in SAP S/4HANA that replaces the multiple separate tables of ECC — BKPF/BSEG (FI header/line items), BSAS/BSIK/BSID (open item clearing tables), COEP/COSP/COSS (CO line items), GLT0 (GL totals), and FAGLFLEXT (New GL totals). Every financial posting in S/4HANA writes to ACDOCA in real time — FI, CO, AA, ML, and CO-PA data in one document. For FICO tcodes, this means: (1) reporting transactions that relied on separate tables (FBL3N, FBL1N, FBL5N) have preferred S/4HANA alternatives (FAGLL03H, FBL1H, FBL5H); (2) period-end FI/CO reconciliation steps are eliminated; (3) all real-time reporting is faster and more dimensionally complete.
FB60 is a pure FI transaction for posting vendor invoices with no purchase order — rent, utilities, professional fees, subscription costs. It creates a financial accounting document only. MIRO (in MM) is for vendor invoices that reference a purchase order and performs a three-way match: PO line quantity/price vs goods receipt quantity vs invoice amount. MIRO creates both an MM invoice document and a linked FI accounting document simultaneously. If there is a PO, use MIRO. If there is no PO, use FB60. Both are unchanged in S/4HANA.SAP FICO period-end closing transaction codes include:
OB52 (open new period), F.13 (automatic clearing), FAGL_FC_VAL (foreign currency valuation), F.05 (FX valuation — classic), F-03 (manual clearing), F110 (final payment run), KSU5 (cost centre distribution), KSV5 (cost centre assessment), CO43 (overhead calculation), KO88 (internal order settlement), CKMLCP (material ledger closing — if actual costing), AFAB (depreciation posting), F.16 (balance carryforward), AJAB (asset year-end closing), S_ALR_87012284 (financial statements), and in S/4HANA GJ11 (Universal Journal period close cockpit).SPRO is the entry point to the SAP Implementation Guide (IMG) — the structured customizing menu where all configuration in SAP is performed. For FICO consultants, SPRO is the starting point for every configuration task: defining company codes (OX02), chart of accounts (OB13), fiscal year variants (OB29), document types (OBA7), posting keys (OB41), posting period variants (OB52), payment terms, and all sub-module configuration. SPRO itself is unchanged in S/4HANA, though the IMG structure contains new configuration nodes for S/4HANA-specific settings (UKM, New AA, Universal Journal).The most commonly used SAP FICO financial statement transaction is
S_ALR_87012284 (ABAP financial statement report — balance sheet and P&L). For custom layouts via Report Painter, use GR55. For New GL ledger-specific balances, use FAGLB03. In S/4HANA, SAP Fiori provides an interactive "Display Financial Statement" app reading from ACDOCA with drill-down to line items. The traditional ABAP reports (S_ALR_87012284, GR55) remain available in S/4HANA alongside Fiori.FB50 is the "Enjoy" single-screen journal entry — you enter header and all line items on one screen simultaneously. It is fast, user-friendly, and suitable for most standard journal entries. F-02 is the classic "complex posting" transaction — it works header-first, then one line item at a time, with full control over posting keys and special GL indicators. F-02 is preferred for complex entries: intercompany postings, entries requiring non-standard posting keys, or scenarios where you need fine-grained line-item control. Both are unchanged in S/4HANA.Key Fiori equivalents for FICO tcodes:
FB50 → 'Post General Journal Entries' (F1306); FB60 → 'Create Supplier Invoice' (F0859); FB70 → 'Create Customer Invoice' (F2222); FBL3N → 'Display Line Items in General Ledger'; F110 → 'Manage Automatic Payments' (F2762); FS00 → 'Manage G/L Account Master Data' (F1366); BP → 'Manage Business Partner Master Data'; UKM_BP → 'Manage Credit Accounts'. SAP GUI tcodes remain fully available alongside Fiori in S/4HANA — most companies phase in Fiori for business user roles while keeping GUI access for consultants and power users.To post to a cost centre in SAP FICO, use
FB50 (GL journal) or FB60 (vendor invoice) and enter the cost centre in the "Cost Ctr" field on the relevant line item — typically the expense line (debit). The cost centre field appears when the GL account is a P&L (income statement) account that is relevant for CO. In S/4HANA, the cost centre assignment is mandatory for all P&L postings where the account requires cost assignment — this is configured in the GL account master (FS00) field status. The KI235 "Account requires assignment to a CO object" error appears when a cost centre or other CO object is missing. See our KI235 error guide.Account-based CO-PA is the profitability analysis approach where revenue and cost data is analysed using standard GL accounts (rather than custom "value fields" in costing-based CO-PA) and stored in the Universal Journal (ACDOCA). In S/4HANA, account-based CO-PA is mandatory and posts in real time — every sales billing document, every cost posting, automatically generates CO-PA line items in ACDOCA. This means the
KE30 report and KE24 line items are now real-time in S/4HANA, no period-end data transfer required. The CO-PA data transfer transactions (KE1S) are not required for account-based CO-PA.Yes — the Material Ledger is mandatory in SAP S/4HANA for all company codes that use Materials Management. In ECC, the Material Ledger was optional (required only for actual costing or multi-currency valuation). In S/4HANA, it is always active because ACDOCA requires it for inventory valuation. This means the month-end Material Ledger closing transaction
CKMLCP is now a standard part of every FICO/MM period-end close in S/4HANA — even for companies that only use standard costing (not actual costing), the ML must be closed each period.Know every FICO tcode. Now use them on a real system.
A reference page builds awareness.
Live SAP access builds careers.
VoiSAP's live online SAP FICO training gives you hands-on access to a real SAP system — every transaction code on this page becomes second nature, not just memorized text. Trained by an 18-year SAP practitioner. 275+ Google reviews at 4.8 stars.
*Live SAP system access included. Canada & USA. 275+ Google reviews at 4.8 stars.