Lesson 1 of 6
Deal scenarios and SAP target states
9 min
Listen to this lesson
Every merger, acquisition or divestiture ends up as a set of SAP decisions: which system the business will run on, which company codes and plants it will have, how its books reach the group, and when each of those things changes. The deal team decides the commercial shape; the SAP program has to turn it into a target state and a route to get there. Get the target state wrong and the program spends a year building the wrong thing. Get it right and most later decisions follow from it.
This course follows Contoso Motor Co. Right after converting its SAP ECC 6.0 system to SAP S/4HANA in August 2026, Contoso acquired Alternadores del Norte S.A. de C.V. in Monterrey, Mexico. Alternadores runs a non-SAP legacy ERP and already sold rotors and alternators to Contoso before the deal. Where a lesson needs a scenario that Contoso is not living through, such as a carve-out, it says so and labels it a what-if.
Six deal scenarios
| Scenario | Who acts | Typical SAP target state |
|---|---|---|
| Acquisition: absorb | Buyer | Target moves into the buyer's SAP as new company code(s) |
| Acquisition: standalone | Buyer | Target keeps its own ERP; the group sees only consolidated financials |
| Acquisition: coexist, then converge | Buyer | Finance integrated early (Group Reporting or Central Finance); operations move later |
| Merger of equals | Both | Pick a surviving system, merge both into a new SAP S/4HANA, or run two tiers |
| Divestiture or carve-out | Seller | Logical separation under a TSA, then physical separation of the sold unit's data |
| Spin-off | Seller to NewCo | NewCo gets a standalone landscape: a clone, a greenfield build or a two-tier setup |
Consulting firms use their own archetype names, such as absorption, tuck-in, standalone and transformational, and academic work adds best of breed and new build. The labels matter less than the question behind them: how much of the target's way of working will survive, and how fast must its numbers and processes become the buyer's?
What drives the target state
Start from the deal thesis. A cost-synergy deal (shared services, joint purchasing, one plant network) points toward absorbing the target into one SAP, because the synergies sit in shared processes and shared master data. A growth deal that buys a capability or a brand often keeps the target autonomous, so a standalone ERP with consolidation only is a legitimate answer. Then add the constraints: the target's ERP and release, any SAP ECC maintenance deadline, the need for consolidated financials at close, regulatory timelines, and whether a seller will provide transition services.
| Decision factor | Points toward | Contoso and Alternadores |
|---|---|---|
| Cost synergy in procurement and plants | Absorb into one SAP | Yes: shared rotor supply from Lakeside Components and existing intercompany trade |
| Target must stay autonomous | Standalone plus consolidation | No: Monterrey becomes part of Contoso's plant network |
| Consolidated financials needed from close | Group Reporting or Central Finance first | Yes: Alternadores reports through Group Reporting by flexible upload until it is loaded |
| Target on a non-SAP ERP | Load as new company code with the Migration Cockpit | Yes: no SAP source to select from |
| Mid-size business with standard processes and a short clock | Greenfield public edition or two-tier | Considered, then rejected to keep one system for intercompany flows |
| Repeat acquirer | A reusable onboarding template | Possibly: a later deal could reuse the Wave 2 load template and tests |
Decision factors and how they applied to Contoso's acquisition of Alternadores del Norte.
Contoso's decision
Before the deal closed, Grace, the PMO lead who now runs the SAP workstream of the integration program, was asked whether Alternadores should get its own SAP Cloud ERP (public edition) in a two-tier setup or be folded into Contoso's private edition. The architects mapped both. Two-tier would have been quicker to stand up and would have isolated Mexican localization. But Alternadores already trades with Contoso, the deal case counted on shared purchasing, and every intercompany flow across two systems needs interfaces, reconciliation and its own regression. Contoso chose to absorb: Alternadores becomes company code 1910 (MXN) with plant 1910 Monterrey and sales area 1910 / 10 / 00, loaded in Wave 2 into the live system, with the go-live weekend planned for 5 to 7 February 2027.
Absorption did not mean everything moved at once. Contoso uses a coexist, then converge path for the first months: on Day 1 Alternadores kept its legacy ERP for operations and Mexican e-invoicing, and its trial balance reached Group Reporting by flexible upload. Operations converge when Wave 2 goes live.
Write the target state down
A target state that lives only in a slide is renegotiated in every workshop. Record it as a decision with the systems, the organizational units, the consolidation path, the interim state and the date each part changes. List the options that were rejected and why: when someone asks in month five why Monterrey is not on its own public edition tenant, the answer should take one minute to find.
- End state: systems, clients and organizational units (company code, controlling area, plants, sales and purchasing organizations).
- Interim states: what runs where on Day 1, Day 100 and until the end state, including any TSA.
- Consolidation path: how the target's numbers reach group reporting in each state.
- Route: the SAP tooling and transition approach (lesson 2).
- Rejected options: each with the reason and who decided.
- Testing implication: which regression, reconciliation and interface tests each hop needs.
What would you do?
In the integration steering meeting, the CFO proposes running Alternadores on its own SAP Cloud ERP public edition tenant "because it is faster", reopening the decision Grace recorded. Rotor supply and alternator sales between Monterrey and Detroit are the core of the deal case. What should Grace bring back to the next meeting?
- Deal scenarios range from absorb to standalone, coexist-then-converge, merger of equals, carve-out and spin-off.
- The deal thesis and the constraints (ERP, deadlines, consolidation need, TSA) set the target state.
- Contoso absorbs Alternadores as company code 1910 in its live SAP S/4HANA, after a coexist phase with Group Reporting upload.
- Record end state, interim states, route, rejected options and the testing implication of each hop.
Check your understanding · not graded
Lesson check
1. A buyer wants procurement synergies and shared master data with the target. Which target-state family fits best?
2. On Day 1, how did Alternadores' numbers reach Contoso's group reporting?
3. Why did Contoso reject a separate two-tier public edition system for Alternadores?
4. Which item belongs in a target-state record besides the end state?