The SAP IBP Order Based Real-Time Integration (RTI) feature supports seamless integration between SAP and Non-SAP systems. RTI will be the primary integration method for order-based planning going forward.
The following Figure shows a schematic of the overall architecture.

Real-Time Integration 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.

Real-Time Integration Profile
When you create a real-time integration profile, in the Header, you provide the following:
- A new profile ID, your OBP planning area, configured on flexible master data, to and from which the integration profile should integrate data
- The SAP IBP logical system that is used in the integration model of the SAP ECC or SAP S/4HANA system and that routes the data that is integrated using CIF, and with the corresponding real-time integration profile to the planning area
Under Inbound, you define the source logical systems for inbound integration from your SAP ECC or SAP S/4HANA system to SAP IBP. The logical system is displayed in the list if the communication arrangement is set up correctly.
Under Outbound, you define how data is distributed to your external systems in outbound integration.
The RTI Mapping section contains the Master Data Type Mappings table and the Key Figure Mappings table. A real-time integration profile can have different states: active, inactive, or pending deletion.
An example of a Real-Time Integration Profile is shown in the following figures.



SAP IBP Real-Time Integration Architecture
Data is captured in real-time, for example, after the creation of Purchase Orders, that is a Business Transaction Event. This data is then transformed into SAP IBP specific data that would be transferred to SAP IBP. At this point, there is a possibility to manipulate the data using RTI specific BAdis (business add-ins). The data is then sent to the Outbound Queue, from where the Cloud Connector sends the data to SAP IBP Inbound Queue. After processing the queues, the data is persisted in the Application Tables of SAP IBP.
After the planning run in SAP IBP - for example, the supply elements, are then put in outbound queues, and from cloud connector, they are moved to 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 type of data transferred from the source system to SAP IBP (Inbound) and from SAP IBP to the source system (Outbound) is shown in the following figure, Data Transfer.

SAP IBP Real-time Setup
Technical Integration using Core Interface (CIF)
A prerequisite for the usage of real-time integration with SAP ERP or SAP S/4HANA on-premise is the implementation of all notes listed in SAP note 3106619. The figure, Real-Time Integration Setup, shows an overview of the steps required to set up RTI in SAP S/4HANA. For details, refer to the SAP Help Portal.

Setting up RTI in SAP IBP
The figure, SAP IBP Setup, shows an overview of the steps required to set up RTI in SAP IBP. For details, refer to the SAP Help Portal.

An overview of Real-Time Integration Technology is shown in the following figure.

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.

The SAP IBP real-time Integration feature allows you to monitor the data transfer both in SAP IBP and SAP ERP or SAP S/4HANA on-premise, as shown in the following figure.

Multiple External Systems and Multiple Planning Areas are also supported.
With the Message Monitoring app, you can display an overview of one of your interfaces and the messages processed through this interface.


