With the integration tools for the Harmonized Planning area, SAP is making a big step forward. When you want to integrate data into SAP IBP, there are two choices for the SAPIBP2 planning area. There is a flexible choice between ETL-like technologies and more dedicated objects, such as those for real-time integration.
Real-Time Integration
Real-Time Integration (RTI) uses bgRFC (background RFC) to enable transactionally consistent integration of master data and transactional data between IBP and the source systems. With RTI, any changes to planning relevant objects (Master data: Product, Location, and so on, AND Transaction data: Purchase Requisitions, Purchase Orders, Sales Orders, and so on) will be captured, transformed, stored in a queue, and ‘pushed’ to the SAP IBP system without the need for a scheduled batch job.
At the point of a transfer, it is possible to manipulate data using RTI-specific BAdis (business add-ins). The data is then sent to the outbound queue, from which the Cloud Connector sends it to the SAP IBP Inbound Queue. After processing the queues, the data is persisted in SAP IBP's application tables.
After the planning run in SAP IBP - for example, the supply elements- are then put in outbound queues, and from the cloud connector, they are moved to the SAP S/4HANA inbound queue, where again there is a possibility to manipulate the data using Badis. Finally, the supply elements are created in the SAP S/4HANA system.
The transfer of data using RTI takes place asynchronously. Data is transferred and buffered in the receiving system (inbound queue). Queues with errors lead to the data channels being blocked and prevent further transfer.
The SAP IBP RTI offers monitoring functions that enable the monitoring of the data transfer both in SAP IBP and SAP ECC/S/4 SAP HANA
The following figure shows a schematic of overall RTI architecture.
The setup of the integration model controls the transfer of master data and transactional data. It is generated in the SAP ECC or SAP S/4HANA system and contains all data that is to be transferred to the SAP IBP system, as shown in figure, Data Transfer.
Multiple enterprise systems can be connected via real-time integration. If data is modified in the source system, it will be updated and available in the SAP IBP planning system within a second, creating orders, transactional data, and any stock, etc. It will be integrated into the master data by definition, with a fast integration that no competitor can match.
Conversely, assuming RTI is established and confirmed production can change every second, it is not desirable to use that transferred data in the monthly S&OP process as a time series, as the S&OP inputs need to be locked. From a business perspective, that might be detrimental to the S&OP process, which is why it's necessary to split the key figures and establish a decoupling point.
Cloud Integration (SAP CI)
The solution for integrating the Harmonized Planning Area lies with the SAP CI solution, a purely cloud-based tool within the SAP Integration Suite.
The SAP Integration Suite combines the features and functions of various capabilities, including Cloud Integration, API Management, Trading Partner Management, Integration Advisor, Open Connectors, Integration Assessment, and Migration Assessment.
SAP Business Technology Platform (SAP BTP) is necessary to enable integration. The subaccount within SAP BTP will consume the Integration Suite application.
SAP Cloud Integration connects cloud and on-premise applications with other SAP and non-SAP applications, both cloud and on-premise. SAP CI supports end-to-end process integration through the exchange of messages processed in real-time, scenarios spanning different companies, organizations, or departments within a single organization. It supports separate subaccounts for development, quality, and production with a transport system.
The detailed process flow for data integration into SAP IBP using SAP CI is depicted in the following figure.
SAP Cloud Connector serves as a link between SAP BTP applications and on-premises systems.
Necessary setups for integration enablement in SAP IBP include:
- Defining the communication scenarios to determine the authorizations, the inbound and outbound services, and the required authentication methods.
- Registration in the Communication Systems app to enable communication between different systems. The communication system represents the communication partner within a communication. For inbound communication, this system calls the services provided by your system. For outbound communication, this system provides the services called by your system.
- Defining the communication arrangement for the inbound communication from SAP Integration Suite to SAP IBP in the Communication Systems app.
Harmonization of Integration Tools and Processes
Harmonized Planning Area, will allow using order-based objects in the time series context. It won't be needed to integrate product master data twice, once via CI-DS and once again via RTI. Per the SAPIBP2 planning area's logic, SAP's default for such integration is to do it only once.
If the customer is not feeding SAP IBP from SAP S/4 or SAP ECC, but from a BW or non-SAP system, they can still use the optional ETL integration, as illustrated in the following figure.
Integration processes have a great opportunity to offer flexibility to the customer, namely by decoupling RTI from exclusive usage in order-based planning so that it's also available for time series space planning for master data and order data, at least for input. Orders are read-only and will be exposed to key figures, allowing consumption by time series applications, namely, IO and time-series supply planning. It applies to demand planning only to some extent (sales orders will be interesting). The ETL usage will be the same as before; it will be available for master data in addition to RTI, and of course, ETL will be used for time series (for example, historical sales for S&OP or Demand). Currently, there are no plans to have RTI for time series.
Choosing the Integration Technology
The value to the customer is in the ability to choose the integration pattern. It's not predetermined by selecting the application for implementation. It is a unique integration pattern for every customer. So, this decoupling exercise will also give the customer the flexibility to choose.
SAP is positioning cloud integration and the integration suite for new customers who start with SAPIBP2. Also, the preference will be to start with RTI early to make adopting SAP IBP modules easier.
For the existing customers, Cloud Integration Data Services (CI-DS) will be supported. The downside is the requirement of an agent, as it is not a cloud-native architecture.