Reporting from line items

Because the Universal Journal stores line items and not pre-calculated totals, every report in SAP S/4HANA finance is, in effect, a live query over the same lines. That has three practical consequences for business users: drill-down always reaches the source, different reports agree with each other, and new attributes can be analyzed without a separate data store.

Drill-down to the source

Start with a balance in the Trial Balance app. Contoso's revenue account shows 1,240,000 USD for period 10 in company code 1710. Click the amount and you reach the line items behind it. Click a line and you reach the journal entry. From the journal entry's related documents, you reach the billing document, and from there the sales order. That path, from a number on a financial statement to the customer's order, was possible in ECC, but often depended on several reports agreeing. Now it is one continuous path over the same data.

Trial BalanceRevenue account, period 10, company code 1710
G/L line itemsAll lines summing to that balance
Journal entryHeader and lines for one billing
Billing documentSource document via reference
Sales orderThe original customer commitment

Drill-down from a balance to its business origin.

Reports that agree

In ECC it was common for the general ledger, the profit center report and the profitability report to show slightly different revenue for the same period, because they were fed by separate postings, sometimes at different times. With the Universal Journal, a G/L revenue report, a profit center report and a margin analysis report read the same lines. If they disagree, it is because they are filtered differently (ledger, period, attribute), not because the data differs.

Question	Typical app	Reads
What is the balance of each account?	Trial Balance	Universal Journal lines, totaled by account
Which postings make up this balance?	Display Line Items in General Ledger	Universal Journal lines
How did this cost center do against plan?	Cost center reports (for example Cost Centers - Plan/Actual)	Actual lines with cost center; plan data
What margin did we make on this customer or product?	Margin analysis reports	Revenue and cost of goods sold lines with market segment attributes

Different questions, same line items. App names vary by release and role; use the app finder.

Plan data and other journals

Actual postings live in the Universal Journal. Plan data uses a parallel structure designed to match it, so plan and actual can be compared on the same attributes. Consolidation data has its own store too. For a business user, the important point is that actuals have one home.

Why period totals are no longer stored

Stored totals had to be updated on every posting and could, in rare cases, fall out of step with the line items. Removing them removes that risk and simplifies posting. It also means period-end jobs that existed purely to roll up or reconcile totals are no longer needed. The trade-off is that very large reports do real work each time they run, which SAP HANA is designed to handle.

New questions without a new data store

Because all attributes sit on the same lines, answering a new management question often means adding a column or a filter rather than building a new extract. Contoso's controller can ask for revenue by customer group and plant, or cost of goods sold by product and segment, from the same lines finance uses for the balance sheet. Companies can also extend the journal with their own fields where the standard ones are not enough. The flip side is that a report is only as good as the attributes on the lines it reads, which is exactly why testers check those attributes at posting time instead of discovering gaps at month end.

What would you do?

The Contoso sales controller reports that margin analysis shows 15,000 USD less revenue for October than the trial balance. Someone suggests a reconciliation project. What is the best first step?

Key points