Home / Insights / Planning

Planning · 4 min read

Leaving APO: Choose the Planning Tool by the Planning Problem

APO goes out of mainstream maintenance with the rest of SAP Business Suite 7 at the end of 2027. So most APO users now have to pick a new planning platform. I have seen that choice made well and made badly, and the difference is almost always where the discussion started.

Start with the Problem, Not the Shortlist

The usual candidates are SAP IBP, PP/DS embedded in S/4HANA, OMP and Kinaxis. All four are serious tools. All four will give you a good demo. That is exactly why the demo tells you very little.

Before you look at any software, write down what makes planning hard in your business. Be specific. Not “we need better visibility”, but “we cannot see that the Tuesday filling line is overloaded until Thursday”. When I do this with a planning team it usually takes two workshops, and the answers shape the rest of the decision.

Five Questions That Sort the Options

How volatile is demand? If your main pain is forecasting, with promotions, seasonality and many customers, the strength you need sits in demand planning and consensus. IBP is built around that process.

Is capacity finite and does sequence matter? If the real constraint is a line, a changeover or a cleaning cycle, you need detailed scheduling close to execution. That points towards PP/DS in S/4HANA or a specialist like OMP, which handles sequencing well in process industries.

Does shelf life drive decisions? In food and dairy, a plan that ignores remaining shelf life is wrong even when the quantities add up. Check how each tool models batches, ageing and minimum remaining shelf life at the customer. Ask to see it, not to hear about it.

How big and how connected is the network? Many plants, many distribution centres and frequent what-if questions favour tools that recalculate the whole network quickly. Kinaxis is known for this kind of concurrent planning. A single plant with a few warehouses rarely needs it.

What can your planners handle? This one gets skipped. A tool that needs an optimisation expert to explain every plan will not be trusted by a planner who used to fix things in a spreadsheet. Be honest about the skills you have and the skills you can hire.

Screenshot to add
SAP IBP Excel add-in: supply planning view for one product family, showing constrained supply against a capacity alert on a production resource

Often the Answer Is Two Tools

On the programmes I have worked on, the outcome was rarely one tool for everything. A common pattern is IBP for demand and mid-term supply, with PP/DS or a specialist scheduler for the short-term plan in the factory. That is fine, as long as you are clear about which tool owns which horizon and how the plan passes between them. Unclear ownership between two planning layers causes more trouble than either tool.

Run a Proof on Your Own Data

Once you have two candidates, ask each vendor or partner for a short proof of concept. Two to four weeks is enough. Give them a real slice of your business: one product family, one or two plants, a few months of history, your actual capacity and shelf-life rules. Then let your own planners use it.

Watch three things. Does the plan make sense to the people who will own it? How much data cleaning was needed to get there? And how did the tool behave when you changed something, a breakdown or an extra order? The answers tell you more about the next five years than any slide.

Your master data will not be perfect for the proof. That is useful. It shows you early what has to be fixed before go-live, whichever tool you choose.

Zakaria Rziki is a partner at NES and an SAP supply chain solution architect. Ask him a question →

Not Sure Which Planning Problem You Are Really Solving?