These are the frequently asked questions for SAP IBP Real-Time Integration and Transition from SDI. If you have additional questions that need to be added, please contact the SAP IBP Customer Engagement Team (email@example.com). Overview of Real Time Integration (RTI) technology: Almost 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 etc. AND Transaction data: Purchase Reqs., Purchase Orders, Sales Orders etc.) will be captured, transformed, stored in a queue, and ‘pushed’ to the IBP system without need for a scheduled batch job.
Overview of Real Time Integration (RTI) technology:
Almost 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 etc. AND Transaction data: Purchase Reqs., Purchase Orders, Sales Orders etc.) will be captured, transformed, stored in a queue, and ‘pushed’ to the IBP system without need for a scheduled batch job.
Q: Which integration technology should the customers choose to go with?
Choice of integration technology depends on the requirements and the timing of the project. There are 6 scenarios that we consider here:
- Order based planning (OBP) customers already productive on SDI: Stick to SDI. Wait for the release where desired functionalities are supported and move to RTI to realize optimal value from a manual migration project.
- OBP implementation projects with short term go-live needs: If the project must go live before 2022, then we suggest using SDI technology to realize value immediately. SDI will be supported for a while and customers can plan and migrate to RTI at a later point.
- OBP implementation projects planned post RTI release (2111): For projects planned to go-live later, our recommendation is to consider RTI as the default integration technology. If there are advanced extensibility needs, then RTI might not be the immediate choice. We also recommend that you discuss your integration requirements with the SAP IBP product team when you are at this point.
- New OBP projects for customers with productive Timeseries/other IBP modules: OBP implementations will still have to use SDI or RTI for integration. Refer above three sections for guidance based on timelines of the project.
- New IBP customers implementing SAP IBP Time series supply: Our long-term goal is to have a single configured master data/order model where TS and OBP will co-exist. One of the prerequisites for this combined model would be the ability to extend Order-based planning master data types (planned for 1H 2022). As of now, RTI will have no impact on customers implementing SAP IBP Timeseries planning.
- New IBP customers with non-SAP source systems: Customers with non-SAP source systems will need APIs to integrate with IBP. With IBP2111 customers can already integrate master data using CI-DS. But since the transactional data APIs are planned for end of the year 2022, we recommend customers to plan for a 2023 go-live.
Q: What are the pre-requisites for adopting RTI?
Implementing Configured data model is a prerequisite for using RTI. A new sample model (“SAP7F – F stands for Flexible) based on RTI will be provided as a reference in release 2111. New customers must base their order-based planning model based on this sample model. For existing order-based planning customers, it is recommended to plan for a transition to RTI from the current SDI based integration.
Q: I am an existing customer. What should I consider before moving to RTI?
- With RTI there is a requirement to use the new configured data model. This move to the configured data model will require the customer to use provided new sample planning area and manually create a new planning area. This will also mean that the customer cannot leverage the existing SAP7 based planning area automatically. An appropriate time to do this would be to align this project with the release of a major functionality such as sub-contracting, scheduling agreements etc.
- RTI release in 2111 will have basic integration capabilities (CIF like integration for IBP inbound, batch integration for IBP outbound integration). It is recommended to already outline integration scenarios and engage in discussions with the product team even if the need to change integration technology is not immediate.
Q: How long will SDI be supported? Or When will SDI be out of maintenance for IBP OBP?
We will support SDI till RTI has functional parity with the current SDI capabilities (including extension capabilities). We will also build in an extra timeline for customers to transition to RTI. Meanwhile, SAP will continue to evaluate availability of SDI every year.
Q: Will new APIs/features be released on SDI in the coming years?
Upcoming new features will be delivered in RTI.
Q: Will there be a migration path from SDI to RTI? What should I do to move from SDI to RTI?
A full migration path is not available. A new sample planning area will be provided based on which customers can configure their RTI based planning area.
- Custom Key figures, planning levels, copy operators, planning view templates, application jobs etc., must be configured in the new planning area. Manual adjustments can be copied from the old planning area to the new planning area.
- RTI can be used to transfer all master data and order data from ECC/S4HANA to the new planning area.
- Existing BADI implementation cannot be reused with RTI and will have to be reimplemented using the BADIs for RTI. Although there won’t be a complete reuse of the code and no copy & paste, we do expect that the design of the old BADIs can help to reduce the efforts of the re-implementation.
- Master data types can be extended with custom attributes and filled with BADIs in ECC/S4HANA (planned for 2205) or directly in IBP using existing features such as Data Integration, Manage Master Data, Excel workbook, etc.
Q: What changes can we expect when we move from SDI to RTI?
There are 3 important changes with RTI:
- Scheduling: With RTI integration will happen near real time without need for batch jobs (Note: In 2111, outbound integration will be via batch jobs but this will be replaced with real time interfaces as well later)
- Modeling extensions via Configured Data Model: Unlike with SDI which relied on a static data model, with configured data model customers can extend their model(relevant for MD from 2111). Content for the additional master data fields need to be integrated using CI-DS. Master Data Types attribute extensibility for RTI is planned for 1H 2022.
- Flexible data loads: With RTI both full initial load and push delta loads are possible.
Q: Will the IBP add on for ECC/S4 exist in the RTI world? Will there be support packs released for IBP ERP add on?
IBP add on for ECC/S4HANA will continue to exist and support packs will be released as needed (CI-DS features and bug fixes). However, RTI does not use/need add on capabilities.
Q: Does upgrading to 2111 release mandate use of Configured Data Model and RTI?
SDI based existing implementations can upgrade to 2111 without any impact. If you choose to, you can use both SDI and RTI in parallel with separate planning areas.
Q: Data of the EXT tables (e.g. transportation lanes) will be used for IBP Inventory Optimization. Can RTI be used in parallel with the IBP ERP add on?
IBP add on for ECC/S4 HANA can coexist with RTI. Note though that RTI and SDI cannot integrate into the same planning area. SDI integrates into a static planning area and RTI will integrate into a configured data model. Customers can continue to use these tables for SAP IBP IO.
Q: Extensibility: Can the developments of SDI IBP ERP or S4HANA add on be reused?
No – RTI will not use SDI ERP or S4HANA add on for functioning. While the design used for the developments in the IBP add-on can be reused, it will have to adapted to the BADIs in RTI.
Q: Extensibility: If there are new BADIs for RTI then, when will the BADIs for RTI be available?
List of available BADIs will be provided when the RTI feature is launched as part of 2111 release.
Q: Extensibility: In RTI implementations what is the equivalent of custom ABAP programs which directly filled the Ext-tables (e.g., STOCK_EXT) in SDI?
Alternatively, you can directly load master data using CI-DS. This option is not available for orders.
Q: Will CI-DS as an integration technology be available/needed after RTI is released?
Yes – CI-DS as a data integration technology will still be available. After moving to the Configured Data Model (Planned for 2111), CI-DS (or excel workbook, Manage Master Data app, Data Integration app) can be used to insert/update/delete master data into both baseline and planning versions. However, in 2111, order data can be integrated from source systems only using RTI.
Q: Is RTI a pre-requisite for Synchronized Planning?
Synchronized planning is currently supported with SDI. It will be enhanced for support with RTI as well. If you are planning to go live with RTI and will implement synchronized planning with PPDS, an alignment with the product team on exact timelines is recommended.
Q: How is the IBP Timeseries supply model going to use information brought in via RTI?
IBP Timeseries supply model will be a separate model. RTI will only populate the IBP OBP application tables. Key figures can be copied between Order based and Timeseries planning areas using copy operator like we can do it now.
The integration of master data through RTI into the IBP time series supply model will be supported with a later release.
Q: Is there a visual representation of release timelines of different RTI related features?
Q: Extensibility: Can the MD types be extended with additional attributes?
One of the prerequisites of the RTI is the Configured Data Model. With the Configured Data Model, customers can create additional attributes/fields they need. Customers can use CI-DS to bring in MD for IBP in general. These additional attributes are usable in IBP, e.g. as attributes of planning levels. Extensibility support in Order-based planning (additional attributes in ECC data objects/RFC extensions) will come in 1H 2022. Same for Planning Run Profile using extensible master data attributes.
Q: Can you provide a decision tree for various integration scenarios that customers might be encountering?
Q: Extensibility: Can the transactional types be extended?
Yes – this is being planned for 2H 2022
Q: What monitoring capabilities with RTI have?
SAP Fiori apps to Monitor the Queue-Processing and start / stop queue will be available (planned 2111).
Q: What are some of the key features planned for future release?
SAP IBP roadmap can be found in the ‘Discover’ section of our help page (https://help.sap.com/IBP). In addition, we also recommend our customers and partners to get in touch with the product team for timely guidance.
Q: Will RTI support the integration from multiple source systems?
RTI will support the integration from multiple SAP ERP and SAP S/4HANA on-premise systems into the baseline versions of one or more planning areas with release 2111
- Multiple source systems into one target planning area
- Multiple source systems into individual planning areas
- Multiple divisions of one source system into individual planning areas
- Multiple divisions of one source system into planning areas of different IBP systems