Lesson 1 of 6
APO in 2027: options and timing
10 min
Listen to this lesson
SAP Advanced Planning and Optimization (APO) is part of SAP SCM 7.0, which belongs to the SAP Business Suite 7 family. Its mainstream maintenance ends on December 31, 2027, together with SAP ECC. SAP offers optional extended maintenance from 2028 to the end of 2030 at an extra fee (third-party sources cite a two-percentage-point uplift on the maintenance base), after which only customer-specific maintenance remains. APO does not stop working on January 1, 2028; it stops getting new legal and functional fixes under standard terms. Check your own contract and the SAP maintenance strategy pages for the exact terms that apply to you.
SAP's direction for APO has been stable for years: there is no APO successor release. Demand Planning (DP) and Supply Network Planning (SNP) are succeeded by SAP Integrated Business Planning (IBP). Production Planning and Detailed Scheduling (PP/DS) is succeeded by PP/DS in SAP S/4HANA, and global ATP (gATP) by advanced ATP (aATP) in S/4HANA. SAP Community posts that cite SAP's APO transition note (2456834) add an important point: there is no automated migration from APO to IBP or aATP. Configuration is rebuilt, not converted.
The four options
| Option | What it means | Risk |
|---|---|---|
| Stay on APO with extended maintenance | Keep SP1 running to 2030 on CIF to S/4HANA, pay the uplift | Shrinking skills, no new S/4HANA integration, a deadline that only moves the problem |
| IBP plus embedded PP/DS | DP and SNP to IBP; PP/DS into S/4HANA; aATP for order promising | Two products to implement and test; process redesign |
| IBP plus S/4HANA MRP only | Drop detailed scheduling; MRP and capacity planning in S/4HANA | Loses finite scheduling where it is needed |
| Staged move | Move demand first, then supply, then scheduling, each with a parallel run | Longer program; temporary integration between APO, IBP and S/4HANA |
Options for APO customers; the right one depends on which APO functions are really used.
Contoso's decision
Contoso's APO system SP1 (SCM 7.0 EHP 4) runs DP for demand, SNP heuristics for Detroit, Chicago and Toledo, and PP/DS sequencing on ASSY-10 in Detroit. During the S/4HANA conversion, the program kept SP1 connected to the converted system through CIF so planning would not change in the same weekend. Grace's steering group then chose a staged move with two parallel cycles: IBP for demand and time-series supply planning, embedded PP/DS in S/4HANA for Detroit scheduling, and an APO freeze in mid-2027. Sunita (demand planning lead) and Jonas (supply planner) own the planning processes; Priya leads testing; Theo's team owns the integration.
- Is DP or SNP used for decisions planners actually take each month?Yes → plan the IBP replacement · No → retire, do not migrate
- Is APO PP/DS used for finite scheduling on a bottleneck?Yes → embedded PP/DS in S/4HANA · No → S/4HANA MRP and capacity planning
- Is gATP used beyond simple product availability?Yes → fit-gap against aATP · No → standard availability check
- Can the business absorb all changes in one go-live?Yes → one cutover · No → staged move with parallel runs per stage
Step by step: building the APO inventory
- Export the list of planning areas, planning books, data views and macros from SP1, with last-used dates where the system records them.
- List all background jobs in
SM37over a full quarter, including process chains and the nightly SNP and PP/DS heuristic runs. - List the active CIF integration models and what they transfer in each direction (master data in, planned orders and requisitions out).
- List custom code: user exits, BAdI implementations, Z reports, Z tables and macros with custom functions; Kenji's team ranks each by use.
- Interview each planner about the decisions they take weekly and monthly, and which screens and reports they use for them.
- Join the lists: every object either supports a named decision or is a candidate for retirement.
The interview step is where the inventory gets honest. Contoso's system lists showed 23 planning books; planners used seven. Two Excel workbooks fed by APO downloads turned out to be the real S&OP pack, which no system list would have found. Those workbooks became the design input for IBP's S&OP views.
| APO area at Contoso | Objects found | Used for a monthly or weekly decision |
|---|---|---|
| DP planning books | 23 | 7 |
| DP macros | 140 | 53 (retain or redesign) |
| SNP heuristics and jobs | 18 jobs | 6, including the hidden deployment job |
| PP/DS heuristics on ASSY-10 | 9 | 4 |
| CIF integration models | 11 | All active; each analyzed |
| Custom reports and Excel downloads | 31 | 12 |
Illustrative course data: what the inventory found and how much of it mattered.
What would you do?
A business sponsor proposes paying for extended maintenance to 2030 and starting the IBP project in 2029, "when the S/4HANA program has settled". What is Priya's best advice to Grace?
- SCM 7.0 (APO) mainstream maintenance ends December 31, 2027; optional extended maintenance runs to 2030.
- DP and SNP go to IBP; PP/DS and gATP go to S/4HANA (embedded PP/DS, aATP).
- There is no automated migration: configuration is rebuilt.
- Inventory what APO really does, including background jobs, before choosing an option.
Check your understanding · not graded
Lesson check
1. When does mainstream maintenance for SAP SCM 7.0 (APO) end?
2. Which product succeeds APO PP/DS?
3. What does SAP say about migrating APO configuration to IBP?
4. Why did Contoso's APO inventory need to include background jobs?