SAP IBP Response & Supply

SAP IBP Real-Time Integration

Spyros Negas, Jothish Karunakaran – SAP IBP Product Management
November 18th 2021

PUBLIC
Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Agenda

Real-Time Integration (RTI) – Current state and Outlook

System Demo

Transitioning to Real-Time Integration (RTI)

Q&A

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Real-Time Integration (RTI)
- Current State and Outlook
 Available
SAP IBP Order Based Integration Architecture
SAP HANA Smart Data Integration (SDI)
Full Data Load

Periodic Data Integration (pull from IBP)

Integration technology: SDI HTTPS

(SAP HANA Smart Data Integration)
SDI Data
SAP IBP
• File-Based integration
(SAP IBP Open-API) Provisioning
• Tables integration Agent
SAP S/4HANA or ERP

IBP Integration
Integration flow: Add-On Data Integration Application
Tables
• Periodic data integration SDI Data
• Pull-logic for master and Other Systems Provisioning
transactional data from source Adapter Open
SDI Inbound/
system (SAP ECC, API Outbound
Data Staging Tables
SAP S/4HANA On Premise)
via scheduled job Tables
Files
• Full data load

SAP Technical Connection

Customer Data Flow
Cloud Firewalls
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
On Premise
Real-time integration for SAP IBP

Definition: Almost real time integration from source to target system via asynchronous functions

Goals: Integration with SAP ECC, SAP S/4HANA On-Premise and SAP S4/HANA Cloud
• By using the same integration technology (bgRFC*) for all source systems
• Supporting transactionally consistent and real time integration
(for master- and transaction data)
Transactionally consistent data integration is required on business transaction level of the source system.
Example: When a purchase requisition is converted into a purchase order in one business transaction in SAP S/4HANA, then both
orders need to be send, integrated and received in SAP IBP as one atomic action to avoid missing or doubled quantities for
subsequent planning.

of captured data which are relevant for SAP IBP planning processes
• Supporting Initial Load & Delta load of data

*bgRFC = Background Remote Function Call

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC This is the current state of planning and may be changed by SAP at any time. 6
 SAP IBP Order Based Integration Architecture: Real Time Integration
SAP ECC/S4HANA and SAP IBP Full and Delta Data Load

Near Real Time Data Integration (Push from Source)

SAP ECC or S/4HANA

RTI BAdIs SAP IBP

Inbound Queue
Data transformation and create, change, In 2111,

(CIF-Like)
delete transactional data bgRFC ** outbound will be Model Configuration
via batch job
(CIF-Like)
(Master Data)

Outbound Queue
(CIF-Like)
SAP Cloud Connector

Connectivity Agent *
Data Capturing (CIF-Like)
for each Planning Relevant Object generate
- create, update, delete

(Transactional Data: PO, Purchase Req, …

Outbound Queue
Master Data: Product, Location, …)

(CIF-Like)

Inbound Queue
Business Transaction
Events

(CIF-Like)
RTI BAdIs
bgRFC ** Application
Data transformation and simplification for Tables
each planning relevant object
(CIF-Like)

SAP
Customer
* Background Remote Function Call Firewalls
Cloud
On Premise
SAP IBP Integration Architecture: RTI (IBP Inbound) SAP
Customer
Firewalls
Cloud
On Premise

SAP IBP SAP S/4HANA Cloud

Data Capturing (CIF-Like)
for each Planning Relevant Object
- create, update, delete -
(Transactional Data: PO, Purchase Req, …
Master Data: Product, Location, …)
RTI

Outbound
bgRFC via WebSocket RFC

(CIF-Like)
Inbound
Planning Queue

Queue
Business Transaction Events
Data WebSocket
Connectivity RFC Data transformation and simplification
Model
bgRFC “tunneled” Agent for each planning relevant object
(CIF-Like)

SAP ECC SAP S/4HANA On-Premise

Data Capturing (CIF-Like) Data Capturing (CIF-Like)
for each Planning Relevant Object
for each Planning Relevant Object
- create, update, delete -
- create, update, delete -
(Transactional Data: PO, Purchase Req,
(Transactional Data: PO, Purchase Req,
…Master Data: Product, Location, …)
RTI …Master Data: Product, Location, …)

Outbound
Outbound

(CIF-Like)
(CIF-Like)

Business Transaction Events Business Transaction Events

Queue
Queue

bgRFC
SAP Cloud RTI Data transformation and simplification
Data transformation and simplification Connector bgRFC
for each planning relevant object
for each planning relevant object
(CIF-Like)
© 2021 SAP SE or an SAP (CIF-Like)
affiliate company. All rights reserved. ǀ PUBLIC 8
SAP IBP Integration Architecture: RTI (IBP Outbound) SAP
Customer
Firewalls
Cloud
On Premise

SAP IBP SAP S/4HANA Cloud

Outbound
Planning

Queue
bgRFC via
Data Model

(CIF-Like)
WebSocket

Inbound
WebSocket RFC RTI Creating, updating and

Queue
RFC
(planned Connectivity deleting orders
orders, etc.) (CIF-Like)
bgRFC “tunneled”
Agent

SAP ECC SAP S/4HANA On-Premise

RTI

RTI

(CIF-Like)
(CIF-Like)

Inbound
Inbound

Creating, updating and Creating, updating and

Queue
Queue

bgRFC bgRFC
SAP Cloud
deleting orders deleting orders
Connector
(CIF-Like) (CIF-Like)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

This is the current state of planning and may be changed by SAP at any time.
Real-time integration for SAP IBP

Real-Time Integration of master and transactional data IBP 2111

• Initial and delta load
• Push from source system to target system by direct data capturing in ECC and SAP S/4HANA
• Master data:
• Location
• Product
• Resource
• PDS
• Transportation Lane
• Transactional data:
• Stock
• Planned Order / Production Order
• Purchase Requisition / PO / STR / STO / Inbound Delivery
• Sales Order / Outbound Delivery
• Outbound integration (only transactional data):
• Planned Orders, STRs, Purchase Requisitions, and Sales order confirmations

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

ETL Integration using Cloud Integration for Data Services (CI-DS)
2108 - Default communication scenario SAP_COM_0593
SAP
Customer
Cloud
On Premise

Applications
IBP Application Firewalls
SC Control Tower
Data Integration SOAP
Collaboration S&OP
Fiori App
Job Scheduler
Demand Driven Demand Response
Replenishment Inventory & Supply

Write APIs
for CI-DS based Integration Websocket RFC
IBP Integration
Read APIs
for CI-DS based Integration Websocket RFC
Add-On
S/4 HANA
Extractors for
CPI-DS based
Integration
or ECC
HANA CI-DS CI-DS
Data Integration (incl. Templates) Agent
Master Data Key Figures
Processing logic
Calculation &
Other
Processing (BW, …)
Logic

Central APIs IBP2111: OBP supports flexible master data model

This enables customers
− to read / write master data using Cloud Integration for Data
Data Model
Services (CI-DS)
− to use Data Integration Fiori app for additional master data upload
Real-time integration for SAP IBP

Multiple systems can be connected with SAP IBP

Monitoring:
IBP 2111
• SAP Fiori apps to Monitor the Queue-Processing and start / stop queue

Integration Model:
• With filter capabilities, customers can define in SAP ECC and SAP S/4HANA IBP 2111
which data to be integrated

Extensibility – Data Manipulation:

• BAdIs in SAP ECC and SAP S/4HANA to change the data to be integrated IBP 2111

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

 Planned

Real-time integration for SAP IBP

Reconciliation: SAP IBP Fiori app to compare data in source and target system IBP 2202*

Real-time outbound integration: Integrating planning results into the source system IBP 2208*

Interfaces:
• Provide APIs
• to read / write master data IBP 2111

• to read / write transactional data 2H 2022*

besides real-time integration to enable customers to integrate with other systems 2H 2022*
(BW, Non-SAP, etc.)

Extensibility – Structural Extensions:

• Ability to enhance master data objects (e.g. add additional field to a master data 1H 2022*
object)
2H 2022*
• Ability to enhance transactional data
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC *This is the current state of planning and may be changed by SAP at any time. 13
Real-Time Integration (RTI)
- System Demo
Transitioning to Real-Time Integration (RTI)
SAP IBP Order Based Integration Architecture
Decision tree to arrive at the appropriate integration technology

Any
enhancements
Using SDI Y N Evaluate additional
Existing OBP on add on?
functional needs – plan to
ABAP (e.g.,
customers adapter ? subcontracting)
transition from SDI to RTI

Use SDI File adapter and/or

N non-SAP source systems
Y
Plan to transition to RTI
after 2h 2022 as APIs for Validate availability of
transactional data planned workaround or future
to be delivered by 2h2022 functionality (IBP roadmap)

Y - Consider RTI by default

Customers N Go-live in - Select SDI, if RTI is not
Go-live
planning OBP before 2022? 2022? supporting required functionality
IBP roadmap). Contact product
implementation team for details.
Y N Go-lives in 2023 or later

Use SDI Use RTI

Customer planning SAP

IBP Timeseries or other Continue using SAP CI-DS (No
non-OBP impact due to RTI)
SAP CI-DS - SAP Cloud Integration for Data Services
implementation OBP – Order Based Planning
RTI – Real Time Integration
FAQs - Highlights
• How long will SDI be supported for existing IBP Response & Supply implementations ?
We intend to support SDI till RTI reaches functional parity plus additional time for customers to transition to RTI. We will revisit
SDI support every year thereafter. Our intent is to support all customers to plan and transition to RTI without any business
impact for them
• Will there be a migration path from SDI to RTI?
Not a full migration. We will provide a new sample planning area SAP7F with which you can configure a RTI based planning
area. Any BADI implementations will have to be redone for RTI BADIs although, SDI BADI implementations will help reduce
design efforts. RTI can be used to transfer all master and transactional data. Custom key figures, planning levels, copy operators,
planning view templates, planning levels, application jobs etc. have to be configured in the new planning area
• What changes can we expect when we move from SDI to RTI?
With RTI, master and transactional data can be transferred near real-time without need for batch jobs. Also, along with initial
full loads, push delta loads will be possible. Since it is based on a configured data model, model extensions are possible.
• 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.
• Can master data and transactional data be extended in RTI?
Yes. Master data extensions can be done in 2111. Transactional data extensibility is planned for 2H 2022.
• Does RTI affect existing Time Series implementations?
No. RTI only affects the order based implementations. You can continue to use CI-DS and existing integration methodologies for
Time series.

Click Here for RTI-related FAQs

Q&A
Thank you.
Contact information:
spyridon.negas@sap.com
jothish.karunakaran@sap.com
Appendix
Useful links for Real-Time Integration

Application help for Real-Time Integration: Link

Application help for OBP Flexible Planning Area: Link

Frequently Asked Questions: Link

OSS note with Information/Restrictions: Link

 Information and main restrictions
 Installation pre-requisites for SAP ERP and SAP S4/HANA
 Step by step guide/checklist for installation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

Follow us

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.