Cost Element vs G/L Account Consistency Check (S/4HANA Conversion Readiness)
Short answer: A custom ALV report that compares the cost elements in an ECC system with the G/L accounts in the chart of accounts and lists inconsistencies that would block the merge of cost elements into G/L accounts on S/4HANA. Missing G/L accounts, number clashes and cost element categories that change over time are visible before the conversion.
- Estimated effort
- S · 2–4 working days
- System
- ECC and S/4HANA
- Tables
- 7
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
KA03 shows one cost element and FS00 one G/L account; there is no standard list that compares both in bulk. On S/4HANA, cost elements are kept as G/L accounts, and SAP's conversion pre-checks report inconsistencies late in the project with technical messages. Projects want to do this clean-up early, with a list the business can read.
Who uses it? FI/CO consultants on S/4HANA conversion projects, controllers and master data teams.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| CSKBCost Elements (Controlling Area Data) | Cost elements at controlling area level, category and validity (driving table) | — | ECC + S/4 |
| CSKACost Elements (Chart of Accounts Data) | Cost elements at chart of accounts level | CSKA-KTOPL = TKA01-KTOPL AND CSKA-KSTAR = CSKB-KSTAR | ECC + S/4 |
| TKA01Controlling Areas | Chart of accounts of the controlling area | TKA01-KOKRS = CSKB-KOKRS | ECC + S/4 |
| TKA02Controlling Area Assignment | Company codes assigned to the controlling area | TKA02-KOKRS = CSKB-KOKRS | ECC + S/4 |
| SKA1G/L Account Master (Chart of Accounts) | G/L account in the chart of accounts: balance sheet indicator, account group | SKA1-KTOPL = TKA01-KTOPL AND SKA1-SAKNR = CSKB-KSTAR | ECC + S/4 |
| SKB1G/L Account Master (Company Code) | Company code record of the G/L account | SKB1-BUKRS = TKA02-BUKRS AND SKB1-SAKNR = CSKB-KSTAR | ECC + S/4 |
| SKATG/L Account Descriptions | G/L account description | SKAT-KTOPL = TKA01-KTOPL AND SKAT-SAKNR = CSKB-KSTAR AND SKAT-SPRAS = P_SPRAS | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_KOKRS | Controlling area | Single value | CSKB-KOKRS | Yes | 1000 |
| S_KSTAR | Cost element | Range / multiple | CSKB-KSTAR | No | 600000 – 799999 |
| S_KATYP | Cost element category | Range / multiple | CSKB-KATYP | No | 1, 42, 43 |
| P_SPRAS | Description language | Single value | SKAT-SPRAS | No | TR |
| P_REVERS | Also list P&L accounts without a cost element | Checkbox | — | No | X |
| P_ERRONL | Show only errors and warnings | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Controlling area | CSKB-KOKRS |
| 2 | Chart of accounts | TKA01-KTOPL |
| 3 | Cost element / account | CSKB-KSTAR |
| 4 | Description | SKAT-TXT50 |
| 5 | Cost element category | CSKB-KATYP |
| 6 | Valid from | CSKB-DATAB |
| 7 | Valid to | CSKB-DATBI |
| 8 | G/L account exists | Calculated X when SKA1 has a record with the same number |
| 9 | Balance sheet account | SKA1-XBILK |
| 10 | Account group | SKA1-KTOKS |
| 11 | Missing company codes | Calculated Company codes in TKA02 without an SKB1 record |
| 12 | Check result | Calculated Error, warning or OK, with the rule that fired |
| 13 | Recommended fix | Calculated Fixed text by rule (e.g. create G/L account, merge category into one period) |
Sample output
| Controlling area | Chart of accounts | Cost element / account | Description | Cost element category | Valid from | Valid to | G/L account exists | Balance sheet account | Account group | Missing company codes | Check result | Recommended fix |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000 | TRHP | 760100 | Marketing expenses | 1 | 01/01/2015 | 12/31/9999 | X | GDR | OK | |||
| 1000 | TRHP | 770450 | Consulting expenses | 1 | 01/01/2018 | 12/31/9999 | X | GDR | 2000 | Error: company code record missing | Create the G/L account in company code 2000 | |
| 1000 | TRHP | 943000 | Maintenance activity allocation | 43 | 01/01/2012 | 12/31/2019 | Warning: category changes over time | Merge the category into one validity period | ||||
| 1000 | TRHP | 253000 | Machinery and equipment | 1 | 01/01/2016 | 12/31/9999 | X | X | BLN | Error: primary element on a balance sheet account | Delete the cost element or correct the account type |
How does the report work?
- For the selected controlling area, the chart of accounts is read from TKA01-KTOPL and the assigned company codes from TKA02.
- Cost elements are read from CSKA (chart of accounts level) and CSKB (controlling area level, with validity periods); an element that carries a different category (KATYP) in different validity periods is flagged.
- For each element the G/L account is looked up in SKA1: a primary element with no G/L account, or with a balance sheet account (SKA1-XBILK), is an error; a secondary element whose number clashes with an existing G/L account is a warning.
- In the other direction, P&L G/L accounts without a cost element are listed, so it can be checked whether they were left out on purpose.
- Each company code assigned to the controlling area is checked for an SKB1 record; the description is added from SKAT in the selected language and every row gets a recommended fix.
Performance notes
Only master data tables are read, so the report runs in seconds even for charts of accounts with several thousand accounts.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the cost element opens KA03; double-clicking the G/L account opens FS00.
- Export to Excel
Authorization objects
- K_CSKBCost element display authorization by controlling area
- F_SKA1_KTPG/L account authorization by chart of accounts
Frequently asked questions
Does this check replace SAP's conversion pre-check?
No. SAP's pre-checks are mandatory for the conversion. This report shows the same topics at the start of the project in a form the business can read, so fewer errors come up at the pre-check stage.
What happens to secondary cost elements on S/4HANA?
On S/4HANA, secondary cost elements are also created as G/L accounts, of the secondary cost type. Elements whose number clashes with an existing G/L account are therefore listed as warnings.
Does the report make the fixes itself?
No, it only lists them and writes the recommended fix. Fixes are made with FS00 and KA02, or with a separate mass maintenance program, and confirmed by running the report again.
Packages that include this solution
S/4HANA Conversion Readiness Pack
A five-component pack that finds the master data and finance inconsistencies to clean up before a system conversion from ECC to S/4HANA: business …
Related reports
Cost Centers with Missing or Invalid Profit Center Assignment Report
A custom ALV report that checks cost centers, and optionally internal orders, for their profit center assignment and lists records where the …
Subledger vs Reconciliation Account Balance Check Report (S/4HANA Migration Check)
A custom ALV report that totals customer and vendor subledger balances by reconciliation account and compares them with the G/L account balance for …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.