SAP S/4HANA End-to-End Lab

Part 1 summarized what IFRS 18 changes: the income statement is split into operating, investing and financing categories, and an operating profit subtotal becomes mandatory. Part 2 looks at SAP FI. In SAP the shape of the income statement is defined by the Financial Statement Version (FSV). This post reads the FSV of an S/4HANA sandbox as it is today and lists what has to change to present it the IFRS 18 way. Example system: S/4HANA sandbox, company code CC10, chart of accounts COA1, financial statement version FSV1. It is a training system, not a real company. 1. What IFRS 18 requires in the income statement (summary) Item Topic Detail Three categories Operating, investing, financing Every income and expense item goes into one of the three categories. Income taxes and discontinued operations are shown separately. Subtotal Operating profit or loss Income minus expenses in the operating category. Mandatory. Subtotal Profit before financ...

IFRS 18 is the new international accounting standard that defines how financial statements, and the income statement in particular, are presented. This is Part 1 of a short series: it summarizes what IFRS 18 changes. Part 2 will look at the impact from an SAP FI point of view, and Part 3 from an SAP CO point of view. Note: the example figures below are illustrative only. Requirements are summarized from the IFRS Foundation materials linked at the end. 1. The standard at a glance Item Value Detail Standard IFRS 18 Presentation and Disclosure in Financial Statements Issued April 2024 Issued by the International Accounting Standards Board (IASB) Replaces IAS 1 Replaces the existing standard on presentation of financial statements Effective date 1 January 2027 Annual reporting periods beginning on or after this date; earlier application is permitted What changes Presentation and disclosure Recognition and measurement ...

Three Oracle SQL queries for ECC: G/L accounts, cost elements, and the two combined. Each section goes query → result → notes. Unlike S/4HANA, ECC keeps G/L accounts (SKA1) and cost elements (CSKA/CSKB) as separate masters. SKA1 has no GLACCOUNT_TYPE field; whether an account is a cost element is decided by whether a CSKB row exists. Verified on IDES ECC 6.0 EhP7 / client 800 / company code 1000 (IDES AG, chart of accounts INT, EUR) / controlling area 1000 (CO Europe). The result values were read in SE16N. Replace the schema prefix SAPSR3 with the one on your system. 1. G/L accounts — query Case G/L accounts used by a company code (T001 + SKA1 + SKB1 + SKAT) What it does The chart-of-accounts master (SKA1) joined to the company code segment (SKB1) and the texts (SKAT). The INNER JOIN on SKB1 keeps only accounts that were actually extended to the company code. Result 1,400 rows for SKB1 BUKRS = 1000 (SE16N Number of Entries) SELECT t.BUKRS, t.KTOPL, LTRIM(a.SAKNR, ...

This post opens a four-part overview of SAP CO (Controlling, management accounting). Part 1 starts from the question "why does SAP need CO at all?", then covers the difference between FI and CO, the CO sub-modules, the organizational structure, and how data created in other modules ends up in CO. Note: this series is reorganized from SAP CO overview training material. Screens, menus, T-codes and processing steps vary by SAP version and company-specific configuration. 1. Every business activity ends up as cost or revenue Take a manufacturing company as an example. Each logistics module owns one part of the process, FI records the accounting result, and CO reuses that data for analysis. Module What it manages SD To whom, and under which conditions, products are sold MM Purchasing and inventory of raw materials PP What is produced and how, based on BOM and Routing FI Receivables, payables, expenses, assets and revenue arising from...

Every G/L account a company code actually uses, plus which of them are cost elements — one query, one result set. Runs in DB02 → Diagnostics → SQL Editor as plain HANA SQL. Read-only, no ABAP object needed. Verified on an S/4HANA sandbox: client 100, company code CC10. 0. Before you start — chart of accounts and controlling area are different namespaces Case Company code → chart of accounts (KTOPL) / controlling area (KOKRS) — T001 / TKA02 What it does The G/L account master (SKA1/SKB1/SKAT) is keyed by chart of accounts. The cost element master (CSKB) is keyed by controlling area. Check the mapping before you join anything. Watch out On this system CC10 resolves to KTOPL='COA1' but KOKRS='CA10' — two different strings. JNC2 resolves to 'JNC'/'JNC2', which look similar enough to conflate. Result 2 rows SELECT t.BUKRS, t.KTOPL, k.KOKRS FROM T001 t LEFT JOIN TKA02 k ON k.MANDT = t.MANDT AND k.BUKRS = t.BUKRS WHERE t.MANDT = ...