CO Report Custom development ALV report

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

  • KA03 Display Cost Element. Shows one cost element; no bulk comparison with G/L accounts.
  • FS00 G/L Account Master Record Maintenance. Shows and changes one G/L account; does not check cost element consistency.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
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 levelCSKA-KTOPL = TKA01-KTOPL AND CSKA-KSTAR = CSKB-KSTARECC + S/4
TKA01Controlling AreasChart of accounts of the controlling areaTKA01-KOKRS = CSKB-KOKRSECC + S/4
TKA02Controlling Area AssignmentCompany codes assigned to the controlling areaTKA02-KOKRS = CSKB-KOKRSECC + S/4
SKA1G/L Account Master (Chart of Accounts)G/L account in the chart of accounts: balance sheet indicator, account groupSKA1-KTOPL = TKA01-KTOPL AND SKA1-SAKNR = CSKB-KSTARECC + S/4
SKB1G/L Account Master (Company Code)Company code record of the G/L accountSKB1-BUKRS = TKA02-BUKRS AND SKB1-SAKNR = CSKB-KSTARECC + S/4
SKATG/L Account DescriptionsG/L account descriptionSKAT-KTOPL = TKA01-KTOPL AND SKAT-SAKNR = CSKB-KSTAR AND SKAT-SPRAS = P_SPRASECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_KOKRSControlling areaSingle valueCSKB-KOKRSYes1000
S_KSTARCost elementRange / multipleCSKB-KSTARNo600000 – 799999
S_KATYPCost element categoryRange / multipleCSKB-KATYPNo1, 42, 43
P_SPRASDescription languageSingle valueSKAT-SPRASNoTR
P_REVERSAlso list P&L accounts without a cost elementCheckbox—NoX
P_ERRONLShow only errors and warningsCheckbox—NoX

Output columns

#ColumnSource
1Controlling areaCSKB-KOKRS
2Chart of accountsTKA01-KTOPL
3Cost element / accountCSKB-KSTAR
4DescriptionSKAT-TXT50
5Cost element categoryCSKB-KATYP
6Valid fromCSKB-DATAB
7Valid toCSKB-DATBI
8G/L account existsCalculated X when SKA1 has a record with the same number
9Balance sheet accountSKA1-XBILK
10Account groupSKA1-KTOKS
11Missing company codesCalculated Company codes in TKA02 without an SKB1 record
12Check resultCalculated Error, warning or OK, with the rule that fired
13Recommended fixCalculated Fixed text by rule (e.g. create G/L account, merge category into one period)

Sample output

Controlling areaChart of accountsCost element / accountDescriptionCost element categoryValid fromValid toG/L account existsBalance sheet accountAccount groupMissing company codesCheck resultRecommended fix
1000TRHP760100Marketing expenses101/01/201512/31/9999XGDROK
1000TRHP770450Consulting expenses101/01/201812/31/9999XGDR2000Error: company code record missingCreate the G/L account in company code 2000
1000TRHP943000Maintenance activity allocation4301/01/201212/31/2019Warning: category changes over timeMerge the category into one validity period
1000TRHP253000Machinery and equipment101/01/201612/31/9999XXBLNError: primary element on a balance sheet accountDelete the cost element or correct the account type
A view built with fictional sample data; not real system data.

How does the report work?

  1. For the selected controlling area, the chart of accounts is read from TKA01-KTOPL and the assigned company codes from TKA02.
  2. 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.
  3. 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.
  4. 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.
  5. 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

CA Package Custom

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 …

5 components · v1.0

Related reports

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.

Related report: Cost Element vs G/L Account Consistency Check (S/4HANA Conversion Readiness)