When the planning tool does not match SAP, planners stop trusting the plan. The cause is usually the integration, not the planning engine. Start with a register like this one.
| Object | Direction | Leading system | Frequency | Business owner |
|---|---|---|---|---|
| Materials, locations, sources of supply | SAP → platform | S/4HANA | Daily | Master data team |
| BOMs, routings, capacities | SAP → platform | S/4HANA | Daily | Production engineering |
| Sales orders, stock, receipts | SAP → platform | S/4HANA | Hourly or near real time | Customer service, warehouse |
| Forecast | Platform → SAP | Platform | Weekly | Demand planning |
| Planned orders, purchase requisitions | Platform → SAP | Platform | Daily | Supply planning |
| History and actuals | SAP → platform | S/4HANA | Weekly | Planning lead |
Three rules behind the register
- One leading system per object. Never both.
- Timing that matches the decision. Nightly is fine for tactical planning; operational planning needs near real time.
- Errors the business can read. A failed interface should be visible to planners, not only to IT.
