Lesson 1 of 6
Where IBP fits: from APO to cloud planning
11 min
Listen to this lesson
SAP Integrated Business Planning for Supply Chain (SAP IBP) is SAP's cloud planning product. It runs as software as a service on SAP HANA, ships new releases several times a year (named by year and month, such as 2602 and 2608), and covers the planning horizon above day-to-day execution: sales and operations planning (S&OP), demand planning, inventory planning, supply planning and supply chain visibility. Execution stays in SAP S/4HANA: sales orders, MRP, production orders, purchase orders and deliveries.
Most practitioners meet IBP on one of two kinds of project. In an APO replacement, a company that planned in SAP Advanced Planning and Optimization (APO, part of SAP SCM 7.0) moves its demand and supply planning to IBP before APO's mainstream maintenance ends. In a greenfield planning project, a company that planned in spreadsheets introduces IBP for the first time. Contoso Motor Co. is the first kind.
Contoso's starting point
Contoso's ECC landscape included an APO system, SP1 (SCM 7.0 EHP 4), connected to the ERP through the Core Interface (CIF). Sunita, Contoso's demand planning lead, ran monthly statistical forecasts in APO Demand Planning (DP). Jonas, the supply planner for Detroit and Chicago, ran Supply Network Planning (SNP) heuristics to balance the two plants and the Toledo distribution center, and Detroit used APO PP/DS to sequence orders on ASSY-10. The S/4HANA conversion deliberately left planning alone: after go-live, SP1 kept running against the converted production system CMP. The planning program that follows (illustrative course data) replaces DP and SNP with IBP and moves Detroit's detailed scheduling into PP/DS embedded in S/4HANA. Course sap-scm-301 covers that transition; this course teaches IBP itself.
The IBP applications
SAP sells IBP as a set of applications on one shared data model, one database and two user interfaces (the Excel add-in and the web apps). Customers can add applications later in the same tenant. Names and license bundles have changed over the years, so check the exact names in your contract; SAP's learning material groups them as follows.
| Application | What it plans | Contoso use |
|---|---|---|
| IBP for sales and operations (S&OP) | Monthly balancing of demand, supply and finance at aggregate level | Monthly S&OP cycle chaired by the COO |
| IBP for demand | Statistical forecasting, demand sensing, consensus demand | Replaces APO DP |
| IBP for inventory | Multistage safety stock and inventory targets | Later phase |
| IBP for response and supply | Time-series supply planning with heuristics or optimizer; order-based planning and allocations | Replaces APO SNP (time-series) |
| Supply chain control tower | Visibility, alerts and KPIs across the network | Later phase |
| Demand-driven replenishment | DDMRP buffer positioning and sizing | Not in scope |
IBP applications as SAP groups them; check license names for your contract.
Time-series and order-based planning
IBP plans in two styles. Time-series planning stores numbers in buckets (weeks, months) for combinations of attributes such as product, location and customer. It is fast to aggregate and simulate, and it is what S&OP, demand planning and tactical supply planning use. Order-based planning works with individual orders, as MRP does, and is used for short-term response and supply. SAP delivers sample planning areas for both: SAPIBP1 for time-series processes and SAP7F for order-based planning, with a harmonized sample (SAPIBP2) introduced in 2025 releases to combine them. Verify which samples your release offers before you copy one.
Why APO projects go wrong
APO was installed on premise and heavily customized: macros, custom key figures, user exits on CIF. A common failure in replacement projects is to rebuild every APO macro in IBP. IBP is a different product with a different data model, and SAP's sample planning areas already contain most standard calculations. The better question is which planning decisions the business must make each month, and which IBP standard supports them.
What IBP does not do
It helps to be clear about the boundary, because test scope follows it. IBP does not create sales orders, production orders or purchase orders in S/4HANA, does not post goods movements, and does not replace MRP for component planning at Contoso in phase one. It produces numbers in buckets that the business agrees on, and it releases selected numbers to S/4HANA as requirements. Anything that happens after that release, such as MRP creating planned orders for CMC-RTR-200 rotors from Lakeside Components, is tested with the S/4HANA planning courses (sap-pp-202, sap-pp-203), using the released plan as input.
| Question a tester asks | Where the answer lives |
|---|---|
| Is next quarter's forecast for CMC-ALT-100 plausible? | IBP demand planning (forecast, error measures) |
| Can Detroit build what S&OP approved? | IBP supply planning (capacity key figures, scenarios) |
| Did the approved plan reach S/4HANA correctly? | Integration: CI-DS task log, PIRs in S/4HANA |
| Are rotors ordered in time for the plan? | S/4HANA MRP from the released PIRs |
| Is ASSY-10 sequenced correctly this week? | PP/DS embedded in S/4HANA |
Where each planning question is answered after the program.
What would you do?
In the first workshop, the APO team proposes rebuilding all 140 APO DP macros in IBP so that planners "see the same numbers". Grace asks Priya how to respond. What is the best approach?
- IBP plans the months ahead in the cloud; S/4HANA (MRP, PP/DS) plans and executes the days ahead.
- Applications share one data model: S&OP, demand, inventory, response and supply, control tower.
- Time-series planning uses buckets; order-based planning uses individual orders.
- Replace APO by planning decisions, not macro by macro.
Check your understanding · not graded
Lesson check
1. Which planning style does IBP use for monthly S&OP and demand planning?
2. What does PP/DS embedded in S/4HANA take over at Contoso?
3. Which SAP sample planning area is meant for time-series processes?
4. Why is rebuilding every APO macro in IBP a poor approach?