Lesson 2 of 5
CO-PA approaches
10 min
Listen to this lesson
Profitability analysis (CO-PA) answers "where do we make money?" by customer, product, region, channel and any other characteristic the business needs. ECC offered two flavors. Costing-based CO-PA was the one most companies used: it stores its own records with value fields such as revenue, discounts, material cost and freight, filled by mapping rules. Account-based CO-PA stored by cost element and was rarely used in ECC. In S/4HANA the account-based approach became margin analysis, built into the Universal Journal and much richer than its ECC ancestor.
| Costing-based CO-PA | Margin analysis | |
|---|---|---|
| Structure | Value fields defined in the operating concern | G/L accounts, with market segment characteristics on each journal line |
| Storage | Separate CO-PA tables | The Universal Journal |
| Reconciliation with the P&L | A known challenge; needs bridging | Reconciled by design |
| COGS detail | Cost components via value fields at billing | COGS split into component accounts at goods issue; variance categories on separate accounts |
| Future development | Supported on-premise and in Private Edition; SAP's new functions go to margin analysis | SAP's strategic direction; receives new features |
| Availability | Not in Public Edition; not with universal parallel accounting | All editions |
What margin analysis adds
Because margin analysis lives in the journal, every posting with a profitability-relevant account is enriched with the market segment when it posts. Revenue at billing, COGS at goods issue, production variances at settlement and allocations from cost centers all carry the same characteristics, and reports read them immediately. COGS can be split into cost components on separate accounts using the material's cost estimate, and production variances can be posted by category to separate accounts, which closes much of the gap that once made costing-based CO-PA attractive. Universal allocation can allocate cost center costs to market segments as well.
What costing-based CO-PA still does differently
Costing-based CO-PA remains a different tool. It records values that never reach the G/L, such as statistical condition values from pricing, and it can record incoming sales orders as profitability data before billing. It can value records with its own costing logic at the time of posting. Some of these needs can be met in margin analysis by other means, some need a design change, and some may need a business decision to stop doing them. SAP's comparison lists these value flows explicitly; check the current version for your release, because SAP has been adding margin analysis features over several releases.
| Need in ECC (costing-based) | Question for S/4HANA | Typical answer |
|---|---|---|
| Margin by customer and product | Can margin analysis show it from journal lines? | Yes, with characteristics derived at posting |
| COGS by cost component | Is the COGS split configured on component accounts? | Yes, if accounts and splitting profile are set up |
| Freight and rebate estimates on billing | Are they posted to the G/L or only statistical? | Design decision: post them, or report them elsewhere |
| Incoming sales order profitability | Is it still needed for management? | Often answered by sales analytics instead |
Translating costing-based CO-PA needs into S/4HANA questions.
Running both at once
Costing-based CO-PA and margin analysis can be active together in one operating concern. Margin analysis data is stored in the Universal Journal, so running it alongside costing-based CO-PA does not add a separate data store, and many converting companies do exactly that for a period. The catch is human, not technical: two profitability views produce two margin numbers, and people will ask which one is right. If you run both, decide up front which one is the management view, publish the bridge between them, and set an end date. For Contoso, margin analysis is the management view from the first period in production, and costing-based CO-PA is the comparison view until it is retired.
What would you do?
Grace hears that costing-based CO-PA "still works in S/4HANA" and proposes keeping it forever to avoid change. What is the most accurate response?
- Costing-based CO-PA uses value fields in separate tables; margin analysis uses G/L accounts in the Universal Journal.
- Margin analysis reconciles with the P&L by design and gains COGS split and variance accounts.
- Costing-based CO-PA is supported in Private Edition while new functions go to margin analysis, and it is unavailable in Public Edition and with universal parallel accounting.
- Statistical values and incoming sales order profitability need a design answer in margin analysis.
Check your understanding · not graded
Lesson check
1. Which approach is SAP's strategic direction in S/4HANA?
2. Where does margin analysis store its data?
3. Which edition offers margin analysis only?
4. Which ECC need often requires a design decision in margin analysis?