Analytics Catalog/SAP S/4HANA/Controlling/Profit center report
Explore the catalogACDOCACost Center reportGeneral LedgerCDS viewsExtraction
SAP S/4HANA · Controlling (CO)

Profit Center Report

The P&L by profit center — revenue, cost, and operating result per segment, built on ACDOCA, where Margin Analysis is integrated. The loss-making segments surface first.

Sample build of the Profit Center Report — the P&L by profit center: revenue, cost, and operating result per segment, with the loss-making segments surfaced first, rendered tool-neutral so it runs in Power BI, SAC, or Tableau.

Profit Center Report sample
Q2 2026 · actual P&L
Filters
Controlling area
A000
Profit center group
All segments
Period
Apr–Jun 2026
Ledger
0L · leading
10.0M
Revenue
1.84M
Operating result
18.4%
Blended margin
1 / 4
Loss-making
Profit centerRevenueCostResultMargin
4000 · Legacy900,0001,008,000−108,000−12.0%
3000 · Services1,800,0001,620,000180,00010.0%
1000 · Consumer4,200,0003,360,000840,00020.0%
2000 · Enterprise3,100,0002,170,000930,00030.0%
AI Analyst · active
reading

Operating result 1.84M on 10.0M revenue — an 18.4% blended margin. But it is uneven: Enterprise runs 30% while Legacy is loss-making at −12%.

flag

Profit center 4000 · Legacy is below water — −108K on 900K revenue. It is the only loss-making segment, and it pulls the blended margin down about a point.

root cause & next step

Cost (1,008K) exceeds revenue (900K) on a declining line. Route to the profit-center owner with the margin trend — the question is price, cost-to-serve, or sunset. Margin Analysis lives in ACDOCA, so revenue and cost sit on the same journal line — no separate CO-PA to reconcile.

Illustrative data · reconciled to ACDOCA · runs on your warehouse. See it live →
ACDOCA · P&L lines+I_ProfitCenter · master────▶Profit Center Report

The report's query logic — generic SQL on ACDOCA. It sums revenue and cost by profit center for the period, classifying each line by the financial-statement hierarchy, to give the operating result and margin. The same SQL becomes a dbt model in your warehouse.

How it interconnects: in ACDOCA, PRCTR is the profit center and RACCT the G/L account; the account's place in the financial-statement version (FSV) decides whether a line is revenue or cost. Revenue posts as a credit (negative HSL), so it is sign-flipped for display. Margin Analysis is integrated in ACDOCA — revenue and cost sit on the same journal line, so there is no separate CO-PA table to reconcile.
SQL data set · genericized · parameterized · P&L by profit center, reads ACDOCA
Show / hide SQL
SELECT  a.prctr                                   AS profit_center,
        SUM(CASE WHEN f.stmt_section = 'REVENUE'
                 THEN -a.hsl ELSE 0 END)           AS revenue,
        SUM(CASE WHEN f.stmt_section = 'COST'
                 THEN  a.hsl ELSE 0 END)           AS cost,
        SUM(-a.hsl)                                AS operating_result
FROM    acdoca a
JOIN    fsv_node f ON f.racct = a.racct            -- financial-statement hierarchy
WHERE   a.rbukrs = :P_COMPANY_CODE
  AND   a.gjahr  = :P_FISCAL_YEAR
  AND   a.poper BETWEEN :P_FROM_PERIOD AND :P_TO_PERIOD
  AND   f.stmt_section IN ('REVENUE','COST')
GROUP   BY a.prctr
ORDER   BY operating_result ASC;
:P_COMPANY_CODE :P_FISCAL_YEAR :P_FROM_PERIOD :P_TO_PERIOD
Never any customer schema. Ordered worst-margin-first so loss-making segments surface at the top. Profit Center Accounting is integrated in ACDOCA via the PRCTR field — you do not read the classic profit-center ledger; read ACDOCA (or the released CDS view) directly, never via ODP-RFC.

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per P&L posting (profit center · account · period).

dim_profit_centerprofit center · group dim_accountrevenue / cost · FSV dim_segmentsegment reporting dim_dateyear · posting period fct_pc_pnlfact · one row per P&L linerevenue · cost · result
●— fact → dimension join
ElementTypeDefinition
dim_profit_centerdimensionProfit center & group — the segment that earns the margin (PRCTR)
dim_accountdimensionG/L account & FSV node — classifies the line revenue vs cost (RACCT)
dim_segmentdimensionSegment for external segmental reporting (SEGMENT)
dim_datedimensionConformed calendar — fiscal year & posting period
revenuemeasureCredit postings on revenue accounts, sign-flipped to positive
costmeasureDebit postings on cost-of-sales and expense accounts
operating_resultmeasureRevenue − cost — the margin for the profit center
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, or Azure. Reconciled to ACDOCA — 0 variance by design. You own the code, the model, and the data.
How the data gets here: a SAP-compliant extract of ACDOCA (or the released journal CDS view) — via SLT or Table/Table-CDC — never ODP-RFC (prohibited under SAP Note 3255746, blocked June 2026). See the extraction pattern & data flow →
See the complete model
How this report's P&L fact and dimensions fit the full owned model, via conformed keys.
Controlling data model → Enterprise model →

Every source object behind this report. Each linked object has its own page — with its fields and its real S/4HANA status, so you build on the right thing.

ObjectRoleKey fieldsS/4HANA status
ACDOCAUniversal Journal — the P&L lines (PRCTR · RACCT · HSL)6 PK · amountsTransparent table
I_ProfitCenterReleased profit-center master view — segment, hierarchy, validityreleasedReleased CDS view
I_GLAccountLineItemReleased journal-entry line view — the revenue & cost linesreleasedReleased CDS view
I_FinancialStatementVersionNodeReleased FSV hierarchy — classifies accounts revenue vs costreleasedReleased CDS view
CEPCProfit center master — controlling area, segment, validityKOKRS · PRCTR · DATBITransparent table
SKA1G/L account (chart of accounts) — account type for P&L classificationKTOPL · SAKNRTransparent table
Key fields = the primary key plus the columns this report selects; S/4HANA status = whether the object is a live transparent table, a released CDS view, or a compatibility view over ACDOCA. Extract the released CDS view or the transparent table directly — never a compatibility view, never via ODP-RFC.
Want this built & owned?
A reconciled, customer-owned profit-center P&L layer on ACDOCA, on your cloud — margin by segment, your team owns the code. Ten-day proof of concept.
See the Controlling module → Talk to us →