Skip to Content

Future proof your SAP Business Planning and Consolidation project for S/4HANA

Are you currently evaluating, implementing, or running SAP Business Planning and Consolidation (BPC) but also have S/4HANA Finance in your future roadmap?  Did you know that the building blocks for SAP BPC optimized for S/4HANA Finance are pre-delivered and completely different from your existing stand-alone SAP Business Warehouse (BW) and BPC environments?  To help SAP customers who want to implement BPC but are not yet ready for S/4HANA Finance, SAP has recently released an SAP note that will allow them to prepare their current environment for a more easy migration to S/4HANA Finance in the future.

To provide some additional context for those not familiar with S/4HANA Finance, it represents the next generation of SAP ERP financial and management accounting functionality by merging all pertinent transactional and analytical information into a single-source-of-truth table known as the Universal Journal.  Using S/4HANA Finance, customers can quickly evaluate the financial implications of business decisions with real-time analytics, forecasting, and simulation capabilities via a simplified user experience.

A key enabling technology within S/4HANA Finance is SAP Business Planning and Consolidation. SAP had already more tightly integrated BPC and BW via a modeling option known as “BPC Embedded” (distinct from the prior option known as “BPC Standard”).  Both BPC Embedded and BPC Standard are for standalone deployments. In contrast, BPC optimized for S/4HANA enhances BPC Embedded within S/4HANA itself via pre-packaged application content that read S/4HANA master data and transactional actuals in real-time.

Going a step further, with the recent release of SAP Note 2243472 in November 2015, it’s now possible to use the BPC optimized for S/4HANA building blocks (metadata known as “InfoObjects”) in your standalone BPC Embedded implementation.  By applying this SAP note, the risk of boxing in your solution from future migration to S/4HANA Finance is mitigated. In order to have the SAP note independently validated and tested, SAP collaborated with TruQua Enterprises, LLC an SAP-certified consultancy and an SAP-licensed software development partner.  TruQua not only validated the SAP note in its internal systems but also at one of its customers who will soon be going live with the solution. Validation activities included feedback on the migration methodology, areas needing clarification and the results of system tests for technical accuracy that all lead to the improvement of the SAP note.

For full details on how to optimize SAP Business Planning and Consolidation for S/4HANA Finance, you can access the complete note from SAP here: You’ll find attached a detailed step-by-step guide of how to import the new InfoObjects and how to structure your transports for a future migration.

As part of its independent testing and validation, TruQua performed the following activities within TruQloud (TruQua’s cloud-based “Try-And-Decide” offering):

  1. Followed the instructions in SAP note 2243472 importing S/4HANA InfoObjects into a standalone BPC Embedded 10.1 system.
  2. Built and tested a custom BPC Embedded 10.1 planning application using the imported S/4HANA InfoObjects.
  3. Transported the custom planning application into an S/4HANA Finance system (leaving behind the imported S/4HANA InfoObjects) to verify that migration of custom development was possible.
  4. Further modified and customized the S/4HANA InfoObjects by adding new hierarchies and master data attributes and incorporated the changes into the custom planning application.
  5. Ensured master data and hierarchy consistency across the landscape referenced within the custom planning application by maintaining master data and hierarchies within a separate SAP ERP system and loading them into the relevant S/4HANA InfoObject within the standalone BPC Embedded system.  For simulation and testing purposes, the assumption was made that the SAP ERP system used for master data maintenance would eventually become the S/4HANA system via migration.
  6. Manually made the corresponding changes to S/4HANA InfoObjects (including master data and hierarchies) within the S/4HANA system directly to ensure master data consistency with the standalone BPC Embedded system.
  7. Transported all the changes to the custom planning application in the standalone BPC Embedded system to the S/4HANA system.

Outside of TruQloud lab testing, TruQua has implemented, tested and validated the SAP note at one if its customers going live early this year on a stand-alone BPC Embedded system as part of a more extensive implementation and “real world” scenario.  Note that the S/4HANA migration activities will be part of a subsequent phase at that customer.

Any questions with regards to implementation and testing experience with the SAP note can be directed to

You must be Logged on to comment or reply to a post.
    • I don’t know if I got the question right: yes in the S/4 BPC embedded context real time consolidation is on the roadmap. For details please check the latest roadmap documents the SAP Service Marketplace: –> eg. SAP Road Map for Finance or SAP S/4HANA, on – premise edition Road Map

    • Note is 2235568 is currently available as a Pilot-Release only.

      Please get in direct contact with us and we can grant you access to the note.

      If available please include your customer nunber. You can also create a message in the SAP Support portal.

      • frankly, content of transport request included in 2235568 seems rudimentary.
        Original BI “content” contains not only InfoObjects, but also aggregation levels, queries and InfoAreas. That note contains ONLY InfoObjects. Furthermore those IOs are in English only, whereas content of “New Financial Planning” is in German as well. The concept still makes sense though.

        • it is true that note 2235568 contains only the InfoObjects, which serve as a basis for anything that is modeled, and thus having this as a basis will reduce future migration efforts.

          As we don’t have the same backend tables etc. in SAP BW as in S/4 the intention was not and could not be to create a similar or the same BI content which is shipped with S/4. E.g. there is no ACDOCA in SAP BW.

          Thanks for the feedback on the language topic.


      • Can I please get the infoobjects in note 2235568?

        Also, we have an internal S4 environment and can see the /ERP/SFIN_XX infocubes. But when i try to create a connection in BPC optimized web, i only see ERP/SFIN_M01 and M02. I don’t see the cost center planning, IO planning cubes. Is there any activation step i’m missing in order to see these?

        • Hi Neeti,

          to gain access to the note please create a message in the support portal and include your customer number.

          Concerning your other question: please check the documentation for SAP BPC for S/4HANA ā€“ especially the BI Content part:
          You also might want to check the note 1972819 ā€“ Setup SAP BPC optimized for S/4 HANA Finance and Embedded BW Reporting to verfify that you have set up everything that is necessary.

          The central MultiProvider is /ERP/SFIN_M01. Iā€™m not aware of a MultiProvider /ERP/SFIN_M02.

          In the documentation you will see the various Aggregation Levels and respective queries which are eg. used for cost center planning.




  • Thanks Guido. Very interesting article.

    May I ask: what is note 2235568? Is this note planning related or does it include consolidation related objects as well?

    We are creating a planning and consolidation case (stand alone deployment on BW) and we would like to use /erp/ objects from the beginning.
    For planning purposes, we activated note 2243472, which brought us a lot of /erp/-objects.
    I would like to do the same for consoliation. Is there a note which includes the consolidation-specific /erp/-objects (i.e. /erp/group, /erp/icomp, /erp/iprctr…)