IBP Time Series Back Integration into SAP ERP

(ECC & S/4HANA)

#building the bridge
Venu Kelkar, Michael Mack, SAP Product Management
July 2021

PUBLIC
PUBLIC
Overview of IBP Webcasts 2021
SAP IBP Integration Series

SAP IBP Integration using SAP Cloud Integration for data services (1/3): SAP BW/4HANA
Integration – June 16, 2021

SAP IBP Integration Series (2/3): Analytical Tools Integration( SAP Analytics Cloud/
Microsoft Power BI) – July 7, 2021

SAP IBP Integration using SAP Cloud Integration for data services (3/3): Time Series back
Integration into SAP ERP(ECC & S/4HANA) – July 29, 2021

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

Agenda

Welcome & Introduction :: 5 min (Michael)

Why back integration? :: 5 min (Michael)
What are the options? How to set up the options? What are the pros/cons? :: 50 min (Venu,
Michael)
Troubleshooting, Questions & Answers :: 5 min (Venu, Michael)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Why back integration?
"Planning is nothing without execution"

Use cases:

A FMCG company may need to procure

package materials based on an IBP Supply
Plan.

Any Discrete Manufacturer may want to

pass the final demand plan into a MRP
planning process

A High-Tech company may want to share a

production plan with a Subcontractor.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

What are the options?

Key questions:
Sales &
Operations

🎯 What IBP application modules do you like Planning

Demand
Driven
to implement? Inventory
Replenishment

🎯 What is your timeline?

Response
Demand
& Supply

SAP S/4HANA
✓ Production Planning
✓ Available to Promise
✓ MRP

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

What do you like to integrate?
Decoupling Point

Key Questions:

❑ At what Supply Chain Stage do you want to

integrate data?

❑ What order elements are integrated?

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
 What are the options?

➢ CI-DS based integration:

Back integration through RFC and
BAPIs

➢ SDI based integration:

Publishing through IBP Order-based
planning

Disclaimer:
The following slides provide the different options of integrating the data from IBP to ERP systems. These are not necessarily the only options and
are not part of the best practice content supported by SAP.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Cloud Integration for Data Services:
Back integration through RFC, Webservices and BAPIs

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

10
Integration Process Description
Inbound (IBP->S/4)

S/4 HANA
Target Tables

Convert documents ABAP to read file BAPI

based on standard and call BAPI
reports

Transfer data Export data from Export Data from IBP Export Data from
through standard IBP to a File via a Web Service IBP to S/4HANA BW as target
SDI through RFC
function call

SAP Smart Data SAP Cloud Integration for Data

Integration Services
Use Order-Based planning area CI-DS Task
Reads from the IBP Calculation Scenario and writes to S/4 Tables. Can perform limited transformations

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

 SAP Cloud Integration for data services– Connectivity
Wide range of supported sources and targets
SAP Business Suite Databases Cloud HANA Applications Other cloud Files Cloud
Applications Databases in the cloud applications Storage
(ERP, SCM/APO, …)

Business Content SAP HANA MSSQL Server SAP IBP (Integrated SuccessFactors Delimited files: Azure Storage:
Extractors on Azure VM Business Planning) applications
Standard and custom SAP (Sybase) ASE and PaaS Local files Azure Blob
extractors, including delta SAP Lumira oData (v2 & v4) Storage
queues – through ODP SAP (Sybase) IQ Remote
SAP HANA database-as- Web Services (SOAP files Azure Data
RFC Enabled Function IBM DB2 a-service on HANA and REST) through Lake
modules Cloud Platform SFTP Storage
MSSQL Server
ABAP tables XML Files
MySQL
Cluster, transparent, pool,
Z-tables Based on
Oracle XSD
Custom ABAP programs Teradata
Generated on the fly – no Template
ABAP coding needed. file

SAP BW
Direct access to ODS
tables
Write access through
staging BAPI
Load into
ADSO(BW/4HANA)
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12
Integration Process Description: IBP to S/4HANA

S/4HANA or ECC

Web Service
Call 1
CI-DS
IBP SAP CI-DS
Agent

RFC Call Source Tables

2

BW extractor
as a target
3

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

 Steps to write data to S/4HANA through the Webservice call
• Create a webservice(If req.) in S/4HANA.
• Create a datastore of type webservice in SAP Cloud Integration for
Data Services.
• Import the webservice into the datastore and provide the WSDL
path.
• Create a task and dataflow with web service call and XML mapping.
• Finish the mapping of the Webservice call .

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

 Steps to write data to S/4HANA through the RFC function
• Create a datastore of SAP application suite type and specify the
application server.
• Import the RFC function into the datastore. Ex:
BAPI_PR_CREATE.
• Create a task and dataflow with RFC call and XML mapping.
• Replace the existing RFC function transforms with the Imported
data store.
• Finish the mapping of the RFC functions.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

Demo

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

16
 Has or will have a critical impact

Has or potentially have an impact

Integration Process Description Will not have an impact
Inbound (IBP->S/4)
Option 1: Webservice Option 2: Direct RFC Option 3: BW Extractor as
and BAPI call call to S/4HANA target.

Performance
Usage of standard
integration

DDIC object
requirements
Number of RICEF
objects
Use case realization
Note: For Integration of the PIRs, CI-DS has a standard template "IBP_to_ERP_PIR_via_RFC". Recommendation is to use this template. View the webinar: PDF | Recording | FAQ

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

SDI based integration:
Publishing through IBP Order-based planning

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

18
High Level Process & Object Flow

SAP IBP S/4HANA or ECC

Conversion:
SOP-Supply Planning Minimum • Production Order
• Production
• Transport
• External Receipts
1 • Stock Transfer Order
• Purchase Order

Production Receipt
Transport Receipt
Receipts
3 5
Manual
adjustments 2
Production &
4 Production Order 9
Distribution Receipts Stock Transfer Order
interactive Plg Purchase Order

Planned Order
6 External planned:
• Planned Order
Stock Transfer Request
Purchase Request
7 8 • Stock Transfer Request
• Purchase Request

OBP Supply Planning

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

Assumptions & prerequists

Prerequisites:

- Consistency - MD / TD TS/OBP/S4 are current

- TS Supply using ProductionSourceHeader with key attribute SourceID <-> Production Version
- Multi Mode of Transport (MoT)– if only one used simple
- When multi sourcing – model TS Supply with MoT
(Help Link https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2102/en-
US/6896c69dfef04b4f9d322f99dc7621a1.html )

OBP does not have UoM configuration like in TS.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

 1
8 2

1. Order Inbound OBP

7 3

6 4
5

Inbound integration – full load, batch based via

SAP HANA SDI Middleware

Output:

✔ Order are in sync between S4/ERP and

IBP order based planning.

✔ Orders have matching numbers, dates and

quantities

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

 1
8 2

2. Copy order-based data to time series key figure

7 3

6 4
5

Copy operator that copies selected Order key

figure data to stored Time series (TS) key
figure.

Output:

✔ Time series (TS) in sync with IBP order

based planning.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22

Planning

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23

 1
8 2

3. Calculated KF for new planned Receipts/ Transport

7 3

6 4
5

Use a separate, calculated Key Figure to

calculate delta/ net supply planning quantity that
was created by Time series (TS) Planning.

Formula:

Handover KF = Resulting SOP Plan – fixed

Orders

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

 1
8 2

4. Disaggregation weekly to daily level

7 3

6 4
5

Possible approaches

- Copy operators

- Week weights via attributes

- KF calculations via Split factor

⚠Filter blocks

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25

 1
8 2

5. Copy time series key figure to order-based data

7 3

6 4
5

Copy operator that copies Time

series (TS) planning output to
interactive order-based planning
key figure.

Key Question:
▪ Do you copy over planning results
for all materials or only on selected
decoupling points in your Supply
Chain?

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26

 1
8 2

6.1 Create Receipts from Interactive KFs Job

7 3

6 4
5

JOB Chain

- Order clean-up

- create Receipts from Interactive KFs Job

Output:

✔ all existing planned order elements in

order- based planning are deleted.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 27

 1
8 2

6.2 Create Receipts from Interactive KFs Job

7 3

6 4
5

JOB Chain

- Order clean-up

- create Receipts from Interactive KFs Job

Output:

✔ Order elements are created in IBP based

on TS planning results.

‼ Pegging & Gating Factors are not updated.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28

 1
8 2

7. Planning run (confirmation run) - OPTIONAL

7 3

6 4
5

Depending on supply chain model used in TS

and OBP and Step #5 you may want to plan
the entire operational supply plan. I.e. full
planning scope upstream & downstream

Output:

✔ Order elements are created for the full

planning scope upstream & downstream.

✔ Pegging & Gating Factors are created.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 29

 1
8 2

8. Integration cycle
7 3

6 4
5

Out & Inbound integration –

with key completion in IBP

Output:

✔ Order are in sync between

S4/ERP and IBP order based
planning.

✔ Orders have matching numbers,

dates and quantities

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

 1
8 2

9. Order conversion/ Execution in ERP

7 3

6 4
5

Handover to Logistic execution.

Output:

✔ Planned elements are converted into ‘real’

Orders, Goods Receipt and Goods Issue
posted, etc.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 31

What we do NOT suggest is to use OBP as a mere middleware

1. Do not overload TS with execution level complexity to get a realistic SC plan

2. No top-down copy of all TS product plans including all SC levels

• from purchasing
• across all levels of production
• to distribution
• expecting a multi-level bucket plan would be executable, i.e. consistently pegged
→ OBP planned items need to exist for SC execution to “breathe”.

Use this approach for a hierarchical planning approach, with more granular data in order based planning or
MRP

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 32

Comparison

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 33

33
10. Comparison and Wrap-up

CI-DS based integration: SDI based integration:

Back integration through RFC Publishing through IBP Order-
and BAPIs based planning
• Reduced complexity • static, out-of-the box integration interface that is tailored to
Opportunities • Less manual efforts and fewer expertise needed for discreet industry scenarios in SAP S/4HANA and ERP
maintenance on the middleware
• More flexible with Cloud Integration and potential for
realizing complex scenarios

• Deletion of the existing receipt elements • 2 Interfaces

Challenges • Maintenance of RICEF objects on S/4HANA side. • Additional Master and Transactional Data
• Product Lifecycle needs to be considered • additional effort to setup, maintain and operate the order-
based planning configuration.
• Complex scenarios such as VMI, MRP areas, Make-to-
order etc.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 34

Troubleshooting

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 35

35
 Troubleshooting and tips/tricks
• BAPI_PR_CREATE creates the procurement orders incorrectly. Ex.:
The procurement orders are not fixed.
• Set the PRITEMX parameter as required.

• For SOAP API calls, the system configuration setup switch does not
make to the web service calls to the correct system.
• View the note: 2776028. The service name, address etc should match
the across the WSDL for a given SOAP version.

• BAPI_PLANNEDORDER_CREATE cannot create Account

assignment order type planned orders.

• BAPI_REQUIREMENTS_CHANGE does not provide a response

when executing the task in Cloud Integration for data services.
• Re-import the webservice function.
• Ensure that the SOAPADDRESS points to the right system and location
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 36
Troubleshooting and tips/tricks
• Copying the existing standard template for RFC and web service calls gives a syntax error:
IMP-100 Import ATL
Syntax error at line <187>: <SELECT __RFC_FUNCTION ERP.."/IBP/EDD_PL_FILL"[](PrepareRFC.IT_PL)[IT_PL]
FROM PrepareRFC
SET("distinct_run_as_separate_process"='no',>: near <]> found <']'> expecting <identifier, a quoted identifier>.

• Remap the RFC call, delete the old RFC function and redo the XML map and the RFC call transforms.
• Further workarounds are in the note: 2934476

• To integrate Planned Independent requirements from IBP To ERP view the note: 2989287

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37

Questions & Answers
Watch IBP- SAP Cloud Integration for data
services Webinar Series
Mini-Series: SAP IBP Integration using CPI-DS (1/4)- SAP ERP
Integration PDF | Recording
Mini-Series: SAP IBP Integration using CPI-DS (2/4)- SAP BW Integration PDF | Recording
Mini-Series: SAP IBP Integration using CPI-DS (3/4)- Back integration from SAP IBP to
SAP ERP using RFC Enabled Function Modules PDF | Recording
Meet the Expert: SAP IBP External Integration - Capabilities and
Roadmap PDF | Recording
Mini-Series: SAP IBP Integration using CPI-DS (4/4)- Microsoft Azure Data Lake &
Microsoft Azure Cloud Storage Integration PDF | Recording | FAQ
Meet the Expert: SAP IBP APO Integration PDF | Recording | FAQ
SAP IBP External Integration Capabilities and Roadmap PDF | Recording
What’s New in IBP Time Series Integration using CPI-DS PDF | Recording
SAP IBP Integration Series: Connect IBP with Analytical Toos e.g., SAC
or PowerBI PDF | Recording
SAP IBP Integration Series: BW/4HANA as a target PDF | Recording

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 39

Thank you.
Contact information:
Venkat Madireddi, SAP Cloud Integration for data services Product Management
[email protected]

Bruno Ranchy, SAP IBP Customer Office

[email protected]
Venu Kelkar, SAP IA&C(Intelligent Adoption and Consumption Hub)
[email protected]

Michael Mack, SAP IBP Customer Office

[email protected]
Follow us

www.sap.com/contactsap

© 2020 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 w ithout the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed w ithout 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, w ithout representation or
w arranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions w ith respect to the materials.
The only w arranties 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
w arranty.
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
w ithout notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forw ard-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 forw ard-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as w ell 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.