SAP FI Tables Replaced on S/4HANA (and Where Cost Elements Went)
In S/4HANA the universal journal table ACDOCA holds finance, controlling, asset and Material Ledger line items in one place. Many classic tables such as GLT0, COEP and the asset value tables stopped storing data, so custom reports that select from them can return wrong or empty results.
| ECC table | Area | What it held in ECC | In S/4HANA |
|---|---|---|---|
GLT0 | FI-GL | G/L account totals (classic GL) | Compatibility view reading from ACDOCA; no longer stores data |
FAGLFLEXA | FI-GL | New GL actual line items | Replaced by ACDOCA (universal journal) |
FAGLFLEXT | FI-GL | New GL totals | Compatibility view over ACDOCA |
BSIS | FI-GL | G/L open item index | Compatibility view; open items are ACDOCA lines with no clearing document |
BSAS | FI-GL | G/L cleared item index | Compatibility view; cleared items are ACDOCA lines with a clearing document |
BSEG | FI | Accounting document line items | Still exists for document data, but G/L line item reporting should read ACDOCA |
COEP | CO | CO object line items | Compatibility view over ACDOCA; CO postings are in the universal journal |
COSP | CO | CO totals, external postings (primary costs) | Compatibility view over ACDOCA |
COSS | CO | CO totals, internal postings (secondary costs) | Compatibility view over ACDOCA |
COBK | CO | CO document header | Retained as CO document header; line items now come from ACDOCA |
ANEP | FI-AA | Asset line items | Compatibility view; asset postings are in ACDOCA |
ANEA | FI-AA | Asset line item value fields | Compatibility view over ACDOCA |
ANLC | FI-AA | Asset value fields per year and depreciation area | Compatibility view over ACDOCA |
ANLP | FI-AA | Asset period values | Compatibility view over ACDOCA |
KNC1 | FI-AR | Customer master transaction figures | Compatibility view over ACDOCA |
KNC3 | FI-AR | Customer special G/L transaction figures | Compatibility view over ACDOCA |
LFC1 | FI-AP | Vendor master transaction figures | Compatibility view over ACDOCA |
LFC3 | FI-AP | Vendor special G/L transaction figures | Compatibility view over ACDOCA |
MLIT | Material Ledger | Material Ledger line items | Material Ledger is mandatory; valuation postings carried in ACDOCA |
CE1xxxx | CO-PA | Costing-based CO-PA line items | Account-based CO-PA reads ACDOCA; costing-based remains optional with its own tables |
CSKA | CO | Cost element master (chart of accounts level) | Cost elements are G/L accounts (SKA1/SKB1); CSKA and CSKB are kept for cost element category data |
CSKB | CO | Cost element master (controlling area level) | Maintained through the G/L account (FS00); no separate cost element master |
CSKU | CO | Cost element texts | G/L account texts in SKAT are used |
Exact object type (table, compatibility view or retained) varies by S/4HANA release and by SAP Note, so confirm in SE11 on your system before changing a custom report or extract. Treat this list as a starting map for your simplification item review, not as a substitute for the release documentation.
Want a review of your custom finance reports?
Send a list of Z-reports and we will flag which ones select from replaced tables. Optional, the reference above works on its own.
Optional. The tool and every export work without this. No spam.
How to use this reference
Search for the ECC table your report reads, then check the S/4HANA column to see whether it is a compatibility view, a retained table or replaced outright. Compatibility views let old code keep running but are not fast or complete for every field, so plan to rewrite hot paths against ACDOCA directly. Export the filtered list into your custom code remediation worksheet.
- Search by table name, area (FI-GL, CO, FI-AA) or keyword.
- Flag every custom Z-report that selects from a table in this list.
- Test amounts in ACDOCA against the compatibility view for one period.
Cost elements as G/L accounts
In ECC a cost element was a separate master record created in KA01 with its own category. From S/4HANA 1503 onward a cost element is a G/L account with an account type: primary costs or revenue, or secondary costs. Secondary cost elements used for allocations and settlements are G/L accounts too, created through FS00 and still carrying a cost element category that drives their use. Because every posting needs a G/L account, FI and CO can no longer drift apart.
- Primary cost elements: G/L accounts of type primary costs or revenue.
- Secondary cost elements: G/L accounts of type secondary costs.
- Old KA01 and KA02 transactions are replaced by G/L account maintenance.
Reading ACDOCA instead of the old tables
ACDOCA is keyed by ledger, company code, fiscal year, document number and line item. A cost center posting that used to be a COEP row is now an ACDOCA row with the cost center and controlling area filled in. Open item queries use clearing fields rather than separate open and cleared index tables. Ledger is part of the key, so filter the leading ledger when you reproduce an ECC report.
Common mistakes
The most frequent errors are summing across all ledgers, so amounts double, reading BSEG for G/L balances, and assuming a cost element master record still exists after migration. Another trap is custom append structures on BSEG or COEP that do not carry over to ACDOCA. Run the SAP Custom Code Migration app early, then compare period totals between old reports and rewritten ones.
Frequently Asked Questions
Which tables does ACDOCA replace in S/4HANA?
ACDOCA is the universal journal and takes over line item storage from GL, CO, asset accounting and Material Ledger tables. Totals tables such as GLT0 and COSP became compatibility views. Exact behavior depends on your release, so check each table in SE11 and in the simplification list.
What happened to cost elements in S/4HANA?
Cost elements are now G/L accounts. You create primary and secondary cost elements with FS00 by choosing the account type, not with KA01. CO postings need a G/L account anyway, which removes the old reconciliation between FI and CO.
Can I still use BSEG in S/4HANA?
BSEG still exists for accounting document line data, but SAP recommends reading ACDOCA for G/L reporting. Custom reports that join BKPF and BSEG often still run, though they may miss CO-only or Material Ledger postings that exist only in the universal journal.
Do old CO reports using COEP still work?
Usually yes through the compatibility view, which reads ACDOCA. Performance and field coverage can differ, and custom fields on COEP need to be extended onto ACDOCA. Test one period against the original numbers before relying on the view.
If your finance team keeps asking which table holds a number after a migration, we can put a private assistant over your own documentation and read-only ERP views so it answers with the query shown.
Related Tools
SAP FICO Database Tables Reference
A lookup of the standard finance and controlling tables used in reports, extracts and SE16N queries, with module and what each stores.
Developer ToolsSAP ACDOCA SQL Query Generator
Build SQL over ACDOCA for account balances and line items by ledger, company code, fiscal year and period range.
SAPSAP S/4HANA Key Simplifications Reference
A searchable reference of the biggest ECC to S/4HANA data model and functional changes, with the action each one usually forces.
SAPSAP Cost Element Categories Reference
A searchable list of SAP CO cost element categories, S/4HANA account types and the master data objects around them.
SAPS/4HANA Simplification Item Worksheet
An editable worksheet for logging simplification items from the Readiness Check, with decision, owner effort and cost totals.
More SAP tools
See allKeep exploring
Free tools
- SAP Controlling (CO) Database Tables ReferenceA searchable reference of the SAP tables behind cost centers, internal orders, product costing and material valuation.
- SAP FICO Database Tables ReferenceA lookup of the standard finance and controlling tables used in reports, extracts and SE16N queries, with module and what each stores.
- SAP Cost Element Categories ReferenceA searchable list of SAP CO cost element categories, S/4HANA account types and the master data objects around them.
ERP fixes and how-tos
- SAP KI 235: G/L Account Requires an Assignment to a CO ObjectSAP KI 235 fires when a P&L G/L account has no cost element or the posting carries no valid CO account assignment. Fix it with KA01/KA02 or a default assignment.
- QM order cost recording and settlement in SAPHow SAP QM orders collect inspection costs, how to set a settlement rule and how those costs settle to a cost center, with the key CO transactions.