Skip to Content

Future of APO and its migration

There were many questions and blogs on the future of APO. It was highlighted in one of my previous blogs on the expected merger of SCM application in S/4HANA as in URL

SAP has now released an OSS note 2456834 – Transition Guide for SAP APO stating that “SAP APO is partially succeeded by two products: SAP S/4 HANA and SAP Integrated Business Planning

APO has mainly 4 sub-modules – DP. SNP. GATP and PPDS. Below figure shows the high-level functionalities of each sub-module and SAP’s roadmap for these functionalities to the successor products. DP and SNP will be succeeded by IBP, GATP & PPDS will be succeeded by similar functionalities in S/4HANA.

IBP is a cloud application and AATP is a new name for functionalities of GATP in S/4HANA. Architecture, configurations, user interface for IBP and AATP are very different w.r.t APO .Hence, transition to successor products should be through new configurations i.e existing APO configurations can not be reused for IBP and AATP in S/4HANA. SAP has also clearly stated in the note that “An automated migration from SAP APO to the successor products is not possible“.

It is also now apparent that the future SAP landscape for customers using APO DP and SNP will need to be Hybrid i.e a mix of On-premise (Core ERP or S/4HANA) and Cloud (IBP).

IBP has been launched few years and many customers have started using it or migrated to it. PPDS has been merged in 1610 release of S/4HANA.Some parts of APO GATP have been made available in 1610 release of S/4HANA and SAP has also provided a road map for AATP as depicted in below figure.

Rule-based ATP (RBA) with substitution functionality of GATP is used by several customers, however, that is not yet available in AATP of S/4HANA. The first version of RBA is expected in 1808 release of S/4HANA.

As of now, APO functionalities are partially available in its successor products S/4HANA and IBP. We need to wait and watch when APO can be fully migrated to S/4HANA and IBP. However, it is very clear now that SAP is recommending to plan for transition from APO to its successor products IBP and S/4HANA.


You must be Logged on to comment or reply to a post.
  • Content is very clear and well documented. Very informative information.

    Thank you Mrinal for sharing useful info about future journey of SAP APO functionality.

  • It's a very useful introduction about the SAP APO roadmap to S/4 HANA and it's aslo celar that SAP is trying to put functionalities spread out focused on S/4 HANA platform. Thanks to Mrinal for your opinion sharing.

  • " is also now apparent that the future SAP landscape for customers using APO DP and SNP will need to be Hybrid i.e a mix of On-premise (Core ERP or S/4HANA) and Cloud (IBP)."

    But why Hybrid? Cant customers run S4/HANA cloud and IBP cloud?

  • Hello Mrinal,

    I also went thru the OS note you have talked about.and was hoping to see an update to that note from SAP. Unfortunately there are no new details.

    Since you seem to be in the know of this, what happens to functionalities BLOCK planning, Capable To Promise going forward. I didn't see much in the note about those topics. Can you throw some light?



    • Hi Subhash,

      Functionality for Block planning is available in embedded PP/DS of S/4HANA . As far as I know , SAP has plans to provide 'Feature parity' for APO - GATP functionalities in advanced ATP (AATP) of S/4HANA and hence similar functionality of Capable to promise (CTP) is expected in upcoming release of S/4HANA.

      Hope it helps.