Lesson 3 of 5
The decision
10 min
Listen to this lesson
Choosing the profitability approach is a business decision with technical consequences, not the other way round. It changes what management reports show, how sales and finance talk about margin, and how much reconciliation work finance does each month. It belongs to the finance process owner, with sales and the CFO's office in the room. The project team prepares the options, the evidence and the impact; the business decides.
The options in a conversion
| Option | What it means | Pros | Cons |
|---|---|---|---|
| A: Margin analysis only | Activate margin analysis; retire costing-based CO-PA at conversion | Simplest target; reconciled; future-proof | Big change for report users on day one; history stays in old structure |
| B: Both in parallel, then retire | Activate margin analysis; keep costing-based for a defined period | Comparison and continuity; time to redesign reports | Double work and a bridge each month; needs a firm end date |
| C: Keep costing-based | Do not use margin analysis for management reporting | Least change now | New SAP functions go elsewhere; blocks universal parallel accounting; reconciliation burden stays |
Options for a company that used costing-based CO-PA in ECC.
Practitioner guidance from SAP experts points in one direction: activate margin analysis when moving to S/4HANA, and if you keep costing-based CO-PA, keep it alongside rather than instead. One reason is history. There is no standard tool that converts years of costing-based CO-PA records into margin analysis, so a company that wants trend reporting across the conversion date either keeps the old data available for comparison or builds a mapped history in its analytics layer. Keeping costing-based CO-PA active until at least the end of the fiscal year is a common way to support year-over-year analysis and reconciliation.
- ExploreInventory of CO-PA useEvery report, interface and user of costing-based CO-PA in EP1 listed with owner and frequency
- ExploreOption paperOptions A to C with impacts on reports, processes, effort and risk
- Decision workshopBusiness decisionDan decides with sales and the CFO office; recorded in SAP Cloud ALM
- RealizeBuild and testMargin analysis characteristics, derivation, COGS split; report redesign
- After go-liveParallel periodMonthly bridge; retirement criteria checked
- Year endRetirement decisionCosting-based reports switched off when criteria are met
Preparing the option paper
The option paper is where most of the work happens. It should list every current use of costing-based CO-PA, found from usage statistics, interfaces and interviews; the value fields and characteristics involved; and for each use, how it would be met in margin analysis or why it would be retired. Add the impact on processes (for example, whether freight accruals must now post to the G/L), the build effort for margin analysis characteristics, derivation and COGS split, and the test effort for report continuity. Finish with a recommendation and the risks of each option. Keep it short enough to read in one sitting; detail goes in appendices.
- Current use: reports, interfaces, planning and the decisions each supports.
- Gap list: needs margin analysis does not meet out of the box, with a proposed answer for each.
- Process impact: postings that must change, such as statistical values that would now post.
- Effort and risk: configuration, report rebuild, testing, and the parallel-period workload.
- Recommendation and retirement criteria if a parallel period is chosen.
What Contoso decided
Record the decision properly. In SAP Cloud ALM, the decision becomes a requirement with its rationale, linked to the user stories for margin analysis configuration and report redesign, and to the test cases that will prove report continuity. When an auditor or a new CFO asks "why do the margins look different from 2025?", the answer should be a link, not a memory.
- Do management decisions rely on values that never post to the G/L?Yes → list them and decide how each is replaced or retired · No → next question
- Is universal parallel accounting or Public Edition on the roadmap?Yes → margin analysis is required · No → next question
- Do users need year-over-year margins across the conversion date?Yes → keep costing-based in parallel for at least the fiscal year · No → next question
- Can the team run a monthly bridge during a parallel period?Yes → option B with an end date · No → option A with report redesign done before go-live
What would you do?
In the decision workshop, the head of sales insists on keeping the "freight estimate per customer" from costing-based CO-PA, which is only a statistical value. What should Dan ask for before deciding?
- The CO-PA approach is a business decision owned by finance, with sales and the CFO office involved.
- Options: margin analysis only, both in parallel with an end date, or keep costing-based.
- There is no standard migration of costing-based history; plan year-over-year reporting deliberately.
- Record the decision, rationale and retirement criteria in SAP Cloud ALM and track the end date.
Check your understanding · not graded
Lesson check
1. Who owns the decision on the profitability approach?
2. Why do many companies keep costing-based CO-PA for the rest of the fiscal year?
3. Which is a sound retirement criterion for costing-based reports?
4. What does the option paper for the CO-PA decision need for every current use of costing-based CO-PA?