These are the frequently asked questions for SAP IBP Real-Time Integration and Transition from SDI and static planning area SAP7 to RTI and flexible planning area SAP7F. If you have additional questions that need to be added, please contact the SAP IBP Customer Engagement Team (firstname.lastname@example.org).
Update from November 2021:
based on latest information from the IBP 2111 developments and enriched with customer questions from the Sneak Preview Webinar of September 16th. Please click here for more information.
Update from January 2022:
SAP development continues to broaden the functionalities around Real Time Integration and the new flexible Planning Area SAP7F. First customers start their RTI / SAP7F implementation project, and we have performed further webinars and updated our OSS notes and online documentation. Here is current list of the most important links:
Webinar for consultants: SAP IBP for Consultants: How to set up Real-Time Integration | December 09, 2021
Slides and Recording: Recording
Webinar Meet the Expert: IBP Real Time Integration | November 18, 2021
RTI Setup Checklist (part of OSS note 3110007 and subject of consultant webinar)
Update from November 2022:
The entire Q&A has been updated. In particular, we adapted the statements regarding MOVE TO SAP7F by communicating the development of tools to reduce efforts while moving from SAP7/SDI to SAP7F/RTI.
Overview of Real Time Integration (RTI) technology:
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.
1. What are the pre-requisites for adopting RTI?
A new sample model (“SAP7F – F stands for Flexible) based on RTI is available since release 2111. New OBP 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.
There are other important pre-requisites for the use of RTI and SAP7F. Pls see OSS notes 3106619 and 3110007.
See section regarding migration (“Will there be a migration path from SDI to RTI? What should I do to move from SDI to RTI? ”)
2. I am an existing customer. What should I consider before moving to RTI?
With RTI there is a requirement to use the flexible planning area. This move to this configured (flexible) data model will require the customer to use the provided new sample planning area SAP7F and 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, shelf life, scheduling agreements, etc.
See also question “Can we migrate from existing planning area to new RTI model planning? Is there any automatic migration option from CI-DS/SDI to RTI?” with more details regarding tool support from SAP to move from Planning Area SAP7 to flexible Planning Area SAP7F.
3. 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.
See section regarding migration (“Will there be a migration path from SDI to RTI? What should I do to move from SDI to RTI? ”)
4. Will new APIs/features be released on SDI in the coming years?
Upcoming new features will be delivered a priori on the basis of RTI and SAP7F.
5. Will there be a migration path from SDI to RTI? What should I do to move from SDI to RTI?
A full, automatic migration path is not available. A new sample planning area SAP7F (“F like flexible or configurable) will be provided based on which customers can configure their RTI based planning area. For migration support for the Planning Areas, see question 6.61. “Can we migrate from existing planning area to new RTI model planning? “
- 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 (delivered with 2205) or directly in IBP using existing features such as Data Integration, Manage Master Data, Excel workbook, etc.
- To support your migration, comprehensive RTI online help is provided including a checklist for the setup of RTI both in S/4 and IBP. See OSS Note 3110007. In particular, this note delivers 2 very helpful guides:
- A step-by-step guide for the setup activities can be downloaded from SAP DAM
- A step-by-step guide for the RTI communication setup activities can be downloaded from SAP DAM
- Customers currently on SDI and wondering when they should migrate to RTI, see question “How long will SDI be supported?”
6. Can we migrate from existing planning area to new RTI model planning? Is there any automatic migration option from CI-DS/SDI to RTI?
- SAP has started a project to develop tools to support OBP customers to move from SAP7 to SAP7F
- Focus of the tools is on „most time consuming objects“ for customers ( e.g. Mapping tool for PA conversion)
- Delivered tools will be “expert tools” to be used by key/power users and experienced OBP consultants. Tools will not be designed for a large number of “ordinary users”.
- Tools will not be self-explanatory, but SAP intends to provide incremental support and there will be dedicated documentation (e.g., like OSS Note 3110007).
- The integration process still needs to be adopted by the customer.
- The tools will be rolled out as available throughout 2023 and will mostly be usable for other migration projects of planning areas.
- A webinar is planned in March 2023 for all affected customers and partners to educate them on the migration tools and share additional information. Invitations to the webinar will be send out in Q1/2023.
Not in scope for the migration tools from SAP7 to SAP7F:
- Object types with low effort on customer side
- Object types with too thigh complexity (e.g., BAdI code in S/4, SDI workarounds BAdI based on EXT tables)
- CI-DS flows
- Scheduled jobs
- Business roles
- and some more
Scope definition is subject to change!
More details regarding the move from SAP7 to SAP7F can be found in the following presentation: SAP DAM
There is no timeline yet for the deprecation of SDI integration. This will be announced with significant lead time. But we urge customers to look into the transformation and start planning for it. Especially new projects should start on SAP7F with RTI directly.
6.1. Will the existing customers need to transition to RTI? If yes, will this involve re-implementation?
SDI and SAP7 will continue to be supported in foreseeable future, but they will be deprecated one day.
6.2. I would like to use SAP7F Planning Area with SDI Integration, is it possible?
Unfortunately, no. SDI cannot be used with SAP7F.
7. Would you advise RTI implementation for a fresh OBP implementation with time constraints on Project timelines?
Yes, since IBP2211, net new OBP customers can only start their implementation based on RTI and SAP7F. The “old” sample planning area SAP7 is only available for existing OBP live customers.
8. What changes can we expect when we move from SDI to RTI?
Here are 3 of the 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 (Flexible Planning Area SAP7F): Unlike with SDI which relied on a static data model, with the configured data model (SAP7F), 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 available since IBP2208.
- Flexible data loads: With RTI both full initial load and push delta loads are possible.
- More details regarding the move from SAP7 to SAP7F can be found in the following presentation: SAP DAM
9. 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.
Please note that the addon will remain for the many customers because many customers use the CI-DS framework which was built on top of the EXT tables, for use in the time series modules of IBP. There are no plans to deprecate the IBP Add-On.
10. Does upgrading to 2211 and upcoming OBP releases mandate use of Flexible Planning Area and RTI?
SDI/SAP7 based existing implementations can upgrade to higher without any impact. If you choose to, you can use both SDI and RTI in parallel with separate planning areas.
11. Questions around extensibility, BAdls, IBP Add-On, staging tables
11.1. 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 (planning area SAP7F). Customers can continue to use these tables for SAP IBP IO.
11.2. 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.
11.3. Extensibility: If there are new BADIs for RTI then, when will the BADIs for RTI be available?
The available BAdIs for RTI are:
You can list them via se16 by F4ing “CIF*IBP” in S/4. In ECC, you need to have the necessary OSS notes installed.
11.4. 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.
11.5. Can we connect BADI with Z tables to integrate with SAP IBP?
Within a BAdI you can always read/write data to Z-tables - e.g. when integrating a sales order you can read in your Z-table a value and change the delivery priority
11.6. Can we define the customer attributes for SDI integration to OBP side in RTI?
The possibility to extend with own attributes the structures is provided with IBP2211. The custom attributes Cust_Attr1-10 which are supported yet by SDI are made available for RTI with IBP2302 for sales orders This includes their visibility in apps such as Projected Stock and their use as planning levels.
11.7. Will we still be using /IBP/* tables to capture the data first before it is integrated to IBP (SDI way of working)? Or will there be a new table structure approach to push the data from S4 to IBP system?
There will be no interim table like in SDI.
11.8. If there are no interim tables, then is it safe to say that RTI is pulling the data directly from S4/ECC standard tables and updates respective attributes in respective MDTs in IBP OBP Planning Area?
Yes, that’s correct. Of course there will be BADIs for data manipulation. Also note the timelines for extensibility, APIs etc. on the roadmap.
11.9. Will the /IBP/EXT* staging tables still need to be populated?
RTI will not be using the /IBP/EXT/ tables. RTI will have inbound and outbound queues which will be filled near real-time when there is relevant data to be integrated with.
11.10. With the staging tables, there was the option to create transaction data without impacting original ECC data. How will RTI enable that?
Please note that the current /IBP/*_EXT tables are an SDI feature - they are not relevant for RTI per se in the sense that the standard functionality does not use these ""staging"" tables anymore - simply because we are now ""real time"". It could be that these tables can continue to be used on a customer specific basis even in an RTI integration. RTI offers similar BAdIs than the ones that you had in the IBP Add-On to manipulate master and transactional data in ERP or S/4 before sending them over to IBP inbound integration via CIF." See question “Extensibility: If there are new BADIs for RTI then, when will the BADIs for RTI be available?”.
12. Questions around RTI and CI-DS
12.1. 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.
12.2. RTI and CI-DS to one and the same PA (if SAP plans to merge TS and OBP PAs)?
RTI and CI-DS to one and the same (flexible) PA is possible.
12.3. Can both RTI and CPI-DS be used in the same (OBP) planning area? RTI for the order-based data and CPI_DS for the time series part (e.g. forecast)?
Yes, that's possible.
12.4. Do you see the new integration will also replace CI-DS ? it is difficult to understand why it is so difficult to get the data right sometimes using CI-DS hopefully it is not the case with the new technology
RTI will not replace CI-DS. You can continue to use CI-DS.
12.5. RTI will replace SDI in future?
RTI will replace SDI in the future when SAP has achieved sufficient parity between both integration modes.
Regarding the Planning Areas, SAP7F will be the future solution SAP relies on. And on the long run SAP7 will be deprecated. See also question “Can we migrate from existing planning area to new RTI model planning? Is there any automatic migration option from CI-DS/SDI to RTI?” with more details regarding tool support from SAP to move from Planning Area SAP7 to flexible Planning Area SAP7F.
13. Is RTI a pre-requisite for Synchronized Planning?
Synchronized planning is currently supported for both SDI and RTI, that is for planning areas based on both templates SAP7 and SAP7F.
The currently implemented end-to-end order integration scenarios, technically referred to as Production Planning Integration Mode (PPIM). PPIMs can be modelled at the granularity level of location product.
The currently implemented production integration modes are as follows:
- PPIM 1: Detailed Scheduling delegated
- PPIM 3: Short-term-planning and detailed scheduling delegated
- PPIM 9: Displayed in detailed planning and scheduling
PPIM 1 is supported in SDI since IBP release 2008.
PPIM 3, 9 are supported in SDI since IBP release 2108.
PPIM 1, 3, 9 are supported in RTI since IBP release 2205.
However, more PPIMs are planned for delivery. Future PPIMs other than PPIM 1, 3, or 9 will not be delivered for use in SDI/SAP7.
14. 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 is supported with 2211, to “copy” master data from OBP to TS via rule based master data maintenance.
15. Extensibility: Can the MD types be extended with additional attributes?
One of the prerequisites of the RTI is the Configured Data Model (planning area SAP7F). With the Configured (or Flexible) 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.
16. What do I need to know to decide when to move from SAP7/SDI to SAP7F to RTI?
More information regarding integration scenarios can be found in the following presentation: SAP DAM
17. Extensibility: Can the transactional data be extended?
Yes – this is being planned for 2H 2023
18. What monitoring capabilities with RTI have?
SAP Fiori apps to Monitor the Queue-Processing and start / stop queue are be available.
19. 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.
E.g. the functionality of subcontracting is planned for H1/2023
20. Question in the area of Multi-ECC, Multi-PA, and Multi-IBP
20.1. 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
20.2. Can we connect multiple S4/ECC systems to a single planning area in IBP?
Yes, with SDI already since 2019, For RTI this is also possible. There are details to be considered.
20.3. Will RTI work with multiple ECC and S/4 systems in 2111?
Yes, you can integrate more than 1 ECC / S/4. Master data must be managed and consistent.
20.4. Does the Realtime integration support multiple IBP systems from same ECC?
Yes, this will be possible. This would require different, parallel "connection channels" to each IBP system. When same data from an ECC system are integrated into multiple IBPs, then the back integration from IBP to ECC should be done only from one IBP.
20.5. Can we use two separate planning areas for Response OBP using RTI?
From the same ECC system it might be possible. Attention needed for back integration from IBP to ECC: only disjunct data to different backend systems can be back integrated to S/4 / ECC – this can be maintained in the RTI Integration profile -> “outbound distribution”.
20.6. If we have 2-tier IBP (DEV+TEST) landscape and 3-tier S/4 landscape: can we integrate different ERP instances to two different planning areas in the same IBP instance (one for test and one for dev)?
Yes, this will be possible. This would require different "connection channels" to each PA - but they would reach the same IBP system and the data would arrive in the different SAP7F planning areas.
21. Questions on short and mid-term roadmap for RTI
21.1. Will the APIs provided also allow to read pegging information from IBP Response?
This is one of the requirements that we want to achieve end of 2023 - Like SDI Analytical Outbound.
21.2. RTI will also replace SDI for integration with non-SAP systems?
This is planned for back H2 of 2022.
21.3. Will there be automatic reconciliation? Or CCR like activity will exist?
Yes, tools comparable to APO Comparison and Reconciliation is available with IBP2202.
21.4. Will RTI have other targets such as SAP HANA or BW for analytics?
Initially to SAP ERP's only, it's part of those systems. Next year (2023), the plan is to enable integration via other systems using generic APIs..
21.5. Is any database cleanup required as in the CIF, every 3 or 6 months?
Reconciliation between S/4 / ECC and IBP was delivered with IBP2202.
21.6. Will SAP CI-DS be moved to RTI? or only SDI?
There is currently no plan to move CI-DS to RTI. But CI-DS can be used in addition to RTI.
21.7. How IBP OBP with ePPDS Integration works with RTI?
Synchronized Planning works with RTI. Like for all other future developments, future SYPP developments will focus on RTI and SAP7F.
21.8. Hope you also have some source-target system reconciliation app in IBP designed similar to CCR in APO?
Yes, this is delivered with IBP2202.
22. Questions regarding the ECC and S/4 releases connected via RTI
22.1. What is the “oldest” version of ECC that would support RTI?
ECC EHP4. See OSS Note 3106619
22.2. What is the dependency of the S4 versions? Does it support 2020 or is a newer version of S4 needed?
With S4 2020, RTI is supported. There are many other ECC and S/4 releases that allow to connect to IBP OBP using RTI. See OSS Note 3106619
23. Questions concerning the overall IBP R&S / OBP roadmap.
The following questions are not RTI specific. All new functions will be built so that they work with RTI. SDI will only be enhanced if necessary and as long as there is not sufficient parity between SDI and RTI / flexible planning area.
23.1. When SAP will provide a subcontracting solution in time series planning?
Subcontracting is on the roadmap for H1-2023 for OBP – only based on RTI/SAP7F, not TS, not SDI/SAP7.
23.2. What about Batch data / Batch information? Will it require RTI once it is supported \ released.
Integration of batches will be based on RTI. Batches as own entities including classification are roadmap.
With the introduction of Shelf Life, there is limited batch functionality in OBP. Stock Visibility by Batch with display on-hand stock by batch, showing expiration date; Planning Relevancy with expired batches being excluded from planning. Shelf Life in RTI/SAP7F only (not possible on SDI).
23.3. Are Quality Inspections included in RTI?
QI Lots will require RTI when they are released. Part of Long-Term Roadmap but quarter not defined.
23.4. Will RTI also work for sales scheduling agreements & sales contracts?
RTI will be required for Sched Agree. when they are released. They're part of Long-Term Roadmap but quarter not defined
23.5. Will RTI also support the Integration of Vendors etc. e.g. for Subcontracting purposes in R&S (although not supported yet)
Yes, and subcontracting is planned for year 2023.
24. Questions concerning APO
24.1. Will there be similar plug in for data being pulled from APO?
This connection is only for integrating S/4 or ERP systems to IBP, no direct integration from / to IBP to \ from APO. But you can operate APO applications in parallel to your RTI connected IBP implementation – from a technical perspective and under certain restrictions.
24.2. Will this RTI work in a hybrid environment where SAP ECC is already integrated with APO using CIF?
That is the idea, keep eye out for any restrictions. See above.
24.3. Can this run in parallel with APO?
Yes, allowing RTI integration (which is CIF based) to IBP and also classical CIF to APO, keep eye out for any restrictions though.
25. Questions in the area of Core Interface (CIF)
25.1. Is there a preferred model activation sequence like in the CIF?
The best practices for CIF model activation are the same ones like in classical CIF. E.g. it can be good to activate and execute CIF models that contain the org structures first, before doing this for the CIF models for material locations. Guidance in form of an OSS consulting note will be provided later. There is also RTI online help available. In general, CIF model activation sequence is your individual choice. In general, this is up to the individual implementation project and not different from APO-CIF best practices of the past. It also depends on individual volume requirements and the structure of master data and organizational structures such as plants, supplier, customers, distribution centers, etc."
Pls study in detail the RTI Setup Checklist mentioned in OSS note 3110007.
25.2. Is RTI is trigger based like SLT?
Yes, event driven like the CIF
25.3. Will RTI be trigger based? What is the potential impact to performance on source?
Similar to the CIF, using business transaction events.
25.4. Will there be flexibility on which "objects" are integrated real time vs batch? Some objects may not be required to integrate real time.
It would be good to understand the use case that is driving this question. From an RTI perspective, inbound for transactional data is real time. For the most of the master data is batch oriented. The outbound will be batch job based (Outbound will also be near real time in the subsequent releases). RTI based planning area will be a configured data model and there is a possibility to use CI-DS or Data Integration etc to input master data. Once we understand your specific use cases, we can provide more specific answers.
25.5. Please comment on potential impact to performance on "source" system for this event based triggers.
This is hard to estimate, but in general we can say that SAP does not expect significant changes in the ERP or S/4 system when RTI integration is activated. If you already have an APO installation, you can assume that the future performance impact is similar to the performance impact you have with CIF today.
25.6. How RTI transferring the PDS data? (without manually changing the consumption values)?
You can set up a job to transfer PDS changes on a regular basis.
25.7. Will we still need a separate Intgr Model S/4 --> PPDS; and S/4 OBP? Or will this become one CIF for both?
Currently, you would have CIF Integration Models: 1 to integrate to IBP-OBP via RTI and 1 within S/4 to integrate from genuine S/4 to S/4 ePPDS.
25.8. Asynchronous is like Change Pointers logic, correct?
You can use change pointers for certain data integration, so changes will not be transferred immediately. Asynchronous also means that if changes triggered from ECC fail in IBP,, the erroneous data transfer must be reprocessed on IBP side, not in ECC.
26. Questions around queue management
26.1. Is it similar to CIF in APO? Does IBP support Queue manager? Is there any provision to rectify the queues?
Yes to all 3 questions. Queue management is provided by using the bgRFC Monitoring capabilities.
26.2. What is the type of queue is it the same as APO - qRFC?
bgRFC, not qRFC.
26.3. Do we have post processing of queues concept?
Depends on what exactly mean. 1. There is post processing e.g. in IBP once master or transactional data changes arrive from S/4 in IBP - like in SDI / same. 2. There are inbound queues similar to what you know from APO-CIF and they can be managed in an own app, the bgRFC Monitor app where all queues can be displayed and expedited.
26.4. Since RTI is asynchronous, how is the scenario of system downtime and retry mechanisms supported?
If there is a planned downtime, you can block your queues and reprocess changes triggered in the meantime after connection or the system up and running again.
26.5. Why is it called 'near real-time'?
Most of our customers do not differentiate between RT and near RT. To be very precise, we say “Near RT” because the calls are asynchronous and not synchronous RFC calls. No difference in terms of speed.
26.6. If integration failures occur when sending data into IBP, will we be able to debug via the RFC user or will we need to contact SAP?
Monitoring tools will be available with the 2111 release and we'll continue to invest more around that topic. However, debugging queues will be only possible with S4 or ECC onPremise part.
27. Questions related to middleware, Cloud Connector, installation and license requirements
27.1. Is the SAP Cloud Connector the same tool which exists also for the SAP Cloud Platform when creating destinations in SAP SCP to extract data from the backend? Or are we looking in this case to a new SAP Cloud Connector?
Yes, this should be the same. It's part of the SAP Business Technology Platform (SAP BTP).
27.2. Cloud connector to Agent connection - does it refer any agent here like DP Agent? or any other new?
No. Agents are not needed - this is just ONE box.
27.3. Any documents on Cloud Connectors which will be required for RTI?
No. Cloud connector is a pure middleware without logic.
27.4. From the diagram, the RTI connectivity agent is located in the cloud. Will documentation on best practices be released for this?
No. This part is intrinsic to IBP - no documentation needed.
27.5. Are extra licenses required for RTI ?
The S/4 developments for RTI are integrated into genuine S/4 CIF objects, no extra add-on installation, no extra licenses.
For the connection of the source systems to SAP IBP, the SAP Connectivity service and cloud connector are needed. The connectivity service and cloud connector are part of the SAP Business Technology Platform which requires a separate subscription.
Already has BTP license
New to BTP
No additional subscription needed for RTI
Customer who wants to use RTI but does not have any BTP subscription, they must “purchase” some kind of subscription. Since there are so many options for purchasing BTP, I would recommend that the customer contacts their SAP account executive or go to SAP Store (store.sap.com) or contact sales/account representative.
No additional subscription needed for RTI
Partner who wants to use RTI but does not have any BTP subscription, they must purchase a subscription for a BTP test, demonstration, and development license via the SAP Partner Portal (partneredge.sap.com).
27.6. No Cloud Connector for RTI with S/4HANA on-prem/Private Cloud ?
SAP Cloud connector is needed for every ECC and for every S4HANA release.
27.7. Is there a separate system for RTI like CI-DS or it is configuration/plug in like SDI ?
There is no separate system.
27.8. Is the SAP Cloud Connector the same tool like the one used between SAP Cloud Platform and SAP ECC system? Or is it a new tool?
Yes. This is the same tool.
28. Questions related to S/4 HANA CLOUD
28.1. Will RTI be available for S/4HANA Public Cloud?
Not with IBP2111 - It's in our plans to provide this at a later time
28.2. How will time series demand planning be integrated to S/4HANA Public cloud? Will this be RTI? CP-DS agent will not be valid.
This is only possible via a CP-DS workaround at the moment. See here for more details here https://d.dam.sap.com/a/7fUtVqF
29. Questions regarding Times Series
29.1. Is there a roadmap to have RTI for time series based data ?
It's not on the roadmap yet. RTI with order based planning is the frontrunner. We aim to open this innovation also for TS based data.
29.2. What is planned for the Time Series Integration? Will CI-DS as well be replaced in the near future, before 2025 or after?
No plans to remove it, but RTI may cover TS in future as well. Initial focus is for Order Based only.
30. Is Demand-Driven OBP impacted the same way?
All processes are supposed to work with RTI the way they worked before with SDI integration, including Demand Driven replenishment in OBP. Exception: Supplier Constraint process requires additional modelling via resources.
31. Do we have CCR concept with RTI and will this be based on auto correction?
A dedicated FIORI app for reconciliation is available since IBP 2202.
32. RTI is not only push from source as you can also create / change e.g. a Plan. Order in R&S?
Just as now, you can create / change some data elements in R&S. This remains the same. E.g. Interactive Planning.
33. What about S/4HANA Private Cloud? Can we consider it as On-premise scenario?
From an architecture point of view yes.
34. Other Master Data like Product Substitution would not be supported by RTI
Product Substitution is not covered by RTI so you need to either load via CPI-DS, File upload or maintain manually in IBP. Same procedure as with SDI.