Page tree
Skip to end of metadata
Go to start of metadata

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 ( 

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:       PDF | Recording

Webinar Meet the Expert: IBP Real Time Integration | November 18, 2021

Slides and Recording:       PDF | Recording

OSS Note       3110007 - IBP Real-time Integration: Information/Restrictions - SAP ONE Support Launchpad


OSS Note       3106619 - SAP IBP Real-time integration - Notes for installation - SAP ONE Support Launchpad

RTI Setup Checklist   (part of OSS note 3110007 and subject of consultant webinar)

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.  

1.1. 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: 

  1. 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.  
  2. 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. 
  3. 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.  
  4. 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. 
  5. 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.  
  6. 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. 

1.2. 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 2111New 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. 

1.3. Q: I am an existing customer. What should I consider before moving to RTI? 

  1. 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.  
  2. 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. 

1.4. 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. 

1.5. Q: Will new APIs/features be released on SDI in the coming years? 

Upcoming new features will be delivered in RTI.  

1.6. Q: 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.  

  • 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. 
  • 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.
  • Customers currently on SDI and wondering when they should migrate to RTI, see question “How long will SDI be supported?”

1. 61. Q: Can we migrate from existing planning area to new RTI model planning? Is there any automatic migration option from CPI-DS/SDI to RTI?

There is no "easy button" migration between PA's in OBP – OSS notes, best practices and thorough online help is provided.

1.62. Q: Will the existing customers need to transition to RTI? If yes, will this involve re-implementation?

SDI will continue to be supported in foreseeable future, but eventually yes

1.7. Q: Would you advise RTI implementation for a fresh OBP implementation with time constraints on Project timelines? 

This depends on various factors such as when you want to go-live, are there business requirements that need extensibility or customizations, are there non-SAP source systems involved etc. Decision tree presented during the session should help with this.

1.8. 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.  

1.9. 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.  

1.10. 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.

1.11. Questions around extensibility, BAdls, IBP Add-On, staging tables

1.11.1. 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.

1.11.2. 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.  

1.11.3. 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.  

1.11.4. 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. 

1.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

1.11.6. Can we define the customer attributes for SDI integration to OBP side in RTI?

The custom attributes which are supported yet by SDI will not be available. But we will provide the possibility to extend with own attributes the structures during 2022

1.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.

1.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 that Spyros presented  timelines for extensibility, APIs etc. during the presentation.

1.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. 

1.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 no ""real time"". It could be that these tables can continue to be used on a customer specific basis even in an RTI integration. RTI will offer in one of the next releases 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."

1.12. Questions around RTI and CI-DS

1.12.1 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.

1.12.2. Q: 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.

1.12.3. Q: 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.

1.12.4. Q: do you see the new integration will also replace CPI-DS ? it is difficult to understand why it is so difficult to get the data right sometimes using CPI-DS hopefully it is not the case with the new technology

RTI will not replace CI-DS. You can continue to use CI-DS.

1.12.5. Q: RTI will replace SDI in future?

RTI might replace SDI in the future when SAP has achieved sufficient parity between both integration modes.

1.13. 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. 

1.14. 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. 

1.15. Q: Is there a visual representation of release timelines of different RTI related features?  


1.16. 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. 

1.17. Q: Can you provide a decision tree for various integration scenarios that customers might be encountering?  

1.18. Q: Extensibility: Can the transactional types be extended? 

Yes – this is being planned for 2H 2022 

1.19. Q: What monitoring capabilities with RTI have? 

SAP Fiori apps to Monitor the Queue-Processing and start / stop queue will be available. 

1.20. 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 ( In addition, we also recommend our customers and partners to get in touch with the product team for timely guidance. 

1.21. Question in the area of Multi-ECC, Multi-PA, and Multi-IBP

1.21.1. 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 

1.21.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 be possible. There are details to be considered.

1.21.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.

1.21.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. 

1.21.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

1.21.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.

1.22. Questions on short and mid-term roadmap for RTI

1.22.1. Q: Will the APIs provided also allow to read pegging information from IBP Response?

This is one of the requirements that we want to achieve - Like SDI Analytical Outbound.

1.22.2. RTI will also replace SDI for integration with non-SAP systems?

This is planned for back H2 of 2022, See slide deck

1.22.3. Will there be automatic reconciliation? Or CCR like activity will exist?

Yes, tools comparable to APO Comparison and Reconciliation is delivered with IBP2202. See slide deck, page 16.

1.22.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 plan is to enable via other systems using generic APIs, see slide deck.

1.22.5. Is any database cleanup required as in the CIF, every 3 or 6 months?

Reconciliation between S/4 / ECC and IBP is delivered with IBP2202.

1.22.6. Will SAP CI-DS be moved to RTI? or only SDI?

There is currently no plan to move CI-DS to RTI.

1.22.7. How IBP OBP with ePPDS  Integration works with RTI?

Planned support for upcoming releases for Synchronized Planning

1.22.8. Can you speak to the 'custom attribute' question asked above in the RTI scenario? It sounds like that wouldn’t be possible until 2022. Do you envision that being through RTI or with CPI-DS?

Planned for 2022 as part of RTI, as show in presentation. See slide deck

1.22.9. Hope you also have some source-target system reconciliation app in IBP designed similar to CCR in APO?

Yes, this is delivered with IBP2202.

1.23. Questions regarding the ECC and S/4 releases connected via RTI

1.23.1. What is the “oldest” version of ECC that would support RTI?

ECC EHP4. See OSS Note 3106619

1.23.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 will be supported. There are many other ECC and S/4 releases that allow to connect to IBP OBP using RTI. See OSS Note 3106619

1.24. 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.

1.24.1. Is there a future roadmap to combine both time series and order based integration? or will they always be separate?

There is a road map item called "One Model" to bring together Order Based Planning and Time Series. The "Flexible Planning Area" which is a prerequisite for Realtime Integration is a first step into this direction.

1.24.2. When SAP will provide a subcontracting solution in time series planning?

Subcontracting is on the roadmap for H1-2023 for OBP, not TS

1.24.3. What about Batch data / Batch information? Will it require RTI once it is supported \ released.

Integration of batches will be based on RTI. Part of Long-Term Roadmap, but quarter not defined.

1.24.4. Are Quality Inspections included in RTI?

QI Lots will require RTI when they are released. Part of Long-Term Roadmap but quarter not defined.

1.24.5. 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

1.24.6. 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.

1.25. Questions concerning APO

1.25.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.

1.25.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.

1.25.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.

1.26. Questions in the area of Core Interface (CIF)

1.26.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."

1.26.2. Is RTI is trigger based like SLT?

Yes, event driven like the CIF

1.26.3. Will RTI be trigger based?  What is the potential impact to performance on source?

Similar to the CIF, using business transaction events.

1.26.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.

1.26.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.

1.26.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.

1.26.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.

1.26.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.

1.27. Questions around queue management

1.27.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.

1.27.2. What is the type of queue is it the same as APO - qRFC?

bgRFC, not qRFC.

1.27.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.

1.27.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.

1.27.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.

1.27.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.

1.28. Questions related to middleware, Cloud Connector, installation and license requirements

1.28.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).

1.28.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.

1.28.3. Any documents on Cloud Connectors which will be required for RTI?     

No. Cloud connector is a pure middleware without logic.

1.28.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.

1.28.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.

1.28.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.

1.28.7. Is there a separate system for RTI like CPI-DS or it is configuration/plug in like SDI ?

There is no separate system.

1.28.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.

1.29. Questions related to S/4 HANA CLOUD

1.29.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

1.29.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  

1.30. Questions regarding Times Series

1.30.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.

1.30.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.

1.31. 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 work arounds.

1.32. Do we have CCR concept with RTI and will this be based on auto correction?   

CCR will be available in later releases. We are also evaluating potential automation.

1.33. 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.

1.34. What about S/4HANA Private Cloud? Can we consider it as On-premise scenario?   

From an architecture point of view yes.

1.35. 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 CPIDS, Fileupload or maintain manually in IBP. Same procedure as with SDI.


back to top

  • No labels