OBP Best Practice

Test Script
SAP IBP for Supply Chain 2402
IBP - order-based planning inbound integration with SAP

S/4HANA
ID: 2S4
PUBLIC
Table of Contents
1 Purpose
2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 Business Conditions
2.5 Preliminary Steps
2.5.1 Define MRP Type X0
2.5.2 Assign Node Type to Plants
2.5.3 Define MRP Area for Subcontractors
2.5.4 Maintain MRP Type and GR Processing Time in Material Master
2.5.5 Maintain Procurement Type in Material Master
2.5.6 Maintain Customer Classification in Customer Master
2.5.7 Create Subcontracting Info Records
2.5.8 Create Sales Orders, Outbound Deliveries, and Initial Stock
2.5.9 Create Planned Orders and Production Orders
2.5.10 Create Purchase Requisition and Purchase Order
2.5.11 Create Stock Transfer Requisition and Stock Transfer Order
3 Overview Table
4 Test Procedures
4.1 Configuration Data
4.1.1 Integrate Configuration Data to IBP
4.2 Master Data
4.2.1 Maintain Additional Data for Production Data Structure
4.2.2 Create Integration Model for Plants
4.2.3 Activate Integration Model for Plants
4.2.4 Create Integration Model for Master Data - General
4.2.5 Activate Integration Model for Master Data - General
4.2.6 Create Integration Model for Master Data – Subcontracting-Specific
4.2.7 Activate Integration Model for Master Data – Subcontracting-Specific
4.2.8 View Master Data
4.2.9 Update Master Data through Data Integration
4.2.10 Update Master Data through Manage Master Data App
4.2.11 Create Application Job for Master Data Synchronization
4.2.12 Check Master Data Consistency with Machine Learning (Optional)
4.3 Master Data Change Transfer
4.3.1 Create Variant for Background Integration Model Activation
4.3.2 Create Variant for Production Data Structures Change Transfer
4.3.3 Create Variant for Deactivated Integration Models Deletion
4.3.4 Create and Schedule Background Job for Master Data Changes
4.4 Transactional Data
4.4.1 Create Integration Model for Transactional Data
4.4.2 Activate Integration Model for Transactional Data
4.4.3 View Projected Stock
4.4.4 Check Integration Results in SAP Integrated Business Planning, Add-in for Microsoft Excel
4.5 Set Up Outbound Integration in Real-Time Integration Profile
4.6 Transactional Data Reconciliation
4.6.1 Run Reconciliation Job (Optional)
4.6.2 Solve Data Inconsistencies (Optional)
5 Appendix
5.1 Process Integration
5.1.1 Preceding Processes
5.1.2 Succeeding Processes
IBP - order-based planning inbound integration with SAP S/4HANA(2S4)

Purpose ERROR: REFERENCE SOURCE NOT FOUND 2
IBP - order-based planning inbound integration with SAP S/4HANA(2S4)
Purpose ERROR: REFERENCE SOURCE NOT FOUND 3
Document History
Revision Change Date Description
0 February 5, 2018 Document creation for IBP 1802
1 May 8, 2018 Updated version for IBP 1805
2 August 7, 2018 Updated version for IBP 1808
3 November 6, 2018 Updated version for IBP 1811
4 February 5, 2019 Updated version for IBP 1902
7 November 5, 2019 Updated version for IBP 1911
8 January 29, 2020 Updated version for IBP 2002
9 April 29, 2020 Updated version for IBP 2005
10 July 29, 2020 Updated version for IBP 2008
11 October 29, 2020 Updated version for IBP 2011

ERROR: REFERENCE SOURCE NOT FOUND
Error: Reference source not found Error: Reference source not found 4
Revision Change Date Description

1 Purpose
You can integrate master data and transactional data from your SAP S/4HANA system into order-based planning in SAP Integrated Business Planning for Supply Chain (SAP IBP) in near real time
without the need for batch jobs. For real-time integration (RTI), functions of the Core Interface (CIF) are used to capture changes to the data in real time and to asynchronously integrate master and
transactional data into SAP IBP.
This solution process covers the complete integration process from SAP S/4HANA to SAP IBP. It describes the different master data and transactional objects, provides references to SAP Best
Practices for SAP S/4HANA to explain how to maintain them in SAP S/4HANA, as well as the steps needed to execute the initial resp. delta load. On the receiving side in SAP IBP, the imported
data is checked with the help of SAP Fiori apps and Microsoft Excel planning views.
Note:
We have various showcases of the order-based planning process in SAP IBP. Therefore, we split the inbound integration solution processes as follows:
IBP – order-based planning inbound integration with SAP S/4HANA (2S4) is used for the solution processes of supply and allocations planning and response planning:
 IBP for response and supply – supply and allocations planning – heuristic (2I0)
 IBP for response and supply – supply planning – OBP optimizer (42C)
 IBP for response and supply – response planning (2P0)
IBP – order-based planning inbound integration for deployment planning (4VA) is used for the solution processes of deployment planning and transportation load building:
 IBP for response and supply – deployment planning – optimizer (4UT)
 IBP for response and supply – transportation load building (6NV)
IBP – order-based planning inbound integration for shelf life planning (6Z1) is used for the solution process of shelf life planning:
 IBP for response and supply – shelf life planning (6WZ)
Note: The solution process for deployment planning using the optimizer and the solution processes for supply and allocations planning and response planning are mutually exclusive because the
deployment optimizer run does not consider product allocations (see SAP Note 2640432).
This document provides a detailed procedure for testing this solution process after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in
its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must
be added.

2 Prerequisites
This section summarizes all prerequisites to conduct the test in terms of systems, users, master data, organizational data, and other test data and business conditions.
2.1 System Access
System Details
SAP S/4HANA Accessible via SAP GUI.
SAP Integrated Business Planning web user Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.
interface
Example:
System Details
SAP S/4HANA <SID>
SAP Integrated Business Planning web user in- https://myXXXXXX.scmibp.ondemand.com

terface
SAP Integrated Business Planning, add-in for Connection Name: myXXXXXX

Microsoft Excel Server URL: https://myXXXXXX.scmibp.ondemand.com
Planning Area: RM1SAP7F
2.2 Roles
Assign the following business roles to your individual test users.
Business Role Business Role Description Log On
Administrator (IBP) Administrator (IBP)
Supply Planner (IBP) Supply Planner (IBP)

2.3 Master Data, Organizational Data, and Other Data
The organizational structure and the master data of your company should have been created in your SAP S/4HANA system during its initial setup. The organizational structure reflects the structure
of your company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your company.
This test script requires that at least organizational structure data and master data such as plants, materials, suppliers, customers, and work centers exist in your SAP S/4HANA system.
You have two options to fulfill this requirement: you can reuse existing data (option 1), or you can create your own data (option 2).
Option 1: you use the organizational structure data and master data that is created in SAP S/4HANA when you install SAP Best Practices for SAP S/4HANA. Below you find the list of sample data
referenced in this test script.
Caution: The sample data referenced in this test script is available in the SAP Best Practices for SAP S/4HANA installations for the following versions: Germany, China, the Netherlands, and
Hong Kong, China.
Data Sample Value Details Comments
Material FG126 Serial Number Managed Finished Good MTS
Material SG25 Semifinished Good External Procurement
Material SG124 Semifinished Good Subassembly
Material RM20 Raw Material Ext. Procurement Contract
Material SG23 SEMI23, PD, Subcontracting
Material RM13 RAW13, PD, Subcontracting
Material RM14 RAW14, PD, Subcontracting
Plant 6210 Plant 1 HK
Plant 1310 Plant 1 CN
Plant 1010 Plant 1 DE
Plant 3710 Plant 1 NL
Supplier 13300001 Domestic Supplier 1 CN
Supplier 10300001 Domestic Supplier 1 DE

Data Sample Value Details Comments
Subcontractor 13300007 国内外包商
Subcontractor 10300007 Inland-Lohnbearbeiter A, DE
Customer 62100001 Domestic Customer 1 HK
Customer 62100003 Domestic Customer 3 HK
Customer 37100001 Domestic Customer 1 NL
Customer 37100002 Domestic Customer 2 NL
Work Center ASSEMBLY Assembly
Work Center TESTING Testing
Work Center PACK01 Packing Line 1
Work Center TECHNIC CNC machine
Option 2: you create your own organizational structure data and master data or add your own data to existing data. For more information on how to create master data objects, see the following
Master Data Scripts (MDS) delivered with SAP Best Practices for SAP S/4HANA:
MDS Description
Enterprise Structure [local] (J57) The Enterprise Structure [local] (J57) configuration guide describes how to create plants.
Create Customer Master (BND)
Create Supplier Master (BNE)
Create Product Master of Type "Trading Good" (BNF)
Create Product Master of Type "Raw Material" (BNR)
Create Product Master of Type "Semi-Finished Good" (BNS)
Create Product Master of Type "Finished Good" (BNT)
Create Purchasing Info Record (BHD)
Create Production Work Center (BNJ)

MDS Description
Create Production Bill of Material (BNK)
Create Routing (BNL)
Create Production Version (BLD)
Sample Master Data for MTS Production – Discrete Manufacturing This configuration guide describes how to create sample master data for SAP Best Practices.
[local] (BJL)
2.4 Business Conditions

Before this solution process can be tested, the following business conditions must be met.
Solution process ID Business Condition
BD9 - Sell from Stock The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
You can run through the Sell from Stock (BD9) SAP S/4HANA test procedures to create sales orders and deliveries. Then you can check the integration of the
sales documents into the SAP IBP system.
BJ5 - Make-to-Stock Production – Dis- The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must present in the SAP S/4HANA system.
crete Manufacturing You can run through the Make-to-Stock Production – Discrete Manufacturing (BJ5) SAP S/4HANA test procedures to convert planned orders to production or-
ders, confirm operations of the production orders and post goods receipts. You can then check the integration of the production orders and stock into the SAP IBP
system.
J45 - Procurement of Direct Materials The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
You can run through the Procurement of Direct Materials (J45) SAP S/4HANA test procedures to create purchase requisitions and orders, change purchase orders
and post goods receipts. You can then check the integration of the purchase orders and stock into the SAP IBP system.
Intercompany Stock Transfer The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
Stock Transfer with Delivery You can create stock transfer requisitions and orders, change stock transfer orders and post goods receipts. You can then check the integration of the stock transfer
orders and stock into the SAP IBP system.
Stock Transfer without Delivery
(no SAP Best Practice solution processs
available for SAP S/4HANA)
2.5 Preliminary Steps
Caution: Before you start to implement the following preliminary steps, make sure to have implemented the entire Setting Up the Integration for Order-Based Planning section in the
Configuration Guide – Getting Started with Implementing the SAP Best Practices for SAP Integrated Business Planning document.
2.5.1 Define MRP Type X0
Use
In this step, you create a new MRP type X0 to allow the planning of materials in an external system (SAP Integrated Business Planning).
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1. Log on to SAP S/4HANA in SAP GUI Log on to SAP S/4HANA in the SAP GUI.
2. Access Customizing with transaction Access Customizing by entering transaction code SPRO.
SPRO
3. Navigate to IMG activity Choose Production → Production Planning → Master Production Scheduling → Master Data
→ Check MRP Types from the menu.
4. Choose New Entries On the Change View “MRP Types”: Details screen, choose New Entries.
5. Enter Data for MRP Type X0 On the Change View “MRP Types”: Details screen, enter the following data:
MRP Type: X0
Description: Without MRP, with BOM Explosion
MRP Procedure: X – Without MRP, with BOM Explosion
Planning method: 1 – Planned by external system
6. Choose Save On the Change View “MRP Types”: Details screen, choose Save. The MRP type is created.

2.5.2 Assign Node Type to Plants
Use
In this step, you assign the relevant node type to existing plants. Node type DC stands for distribution center, PL stands for production plant. After the transfer to SAP IBP, the Plant Type field will
reflect this information.
Procedure
2. Open transaction SM30 Enter transaction code SM30 and press E n t e r .
3. Enter Table/View On the Edit Table Views: Initial Screen, make the following entry:
Table/View: V_T001W_DR.
4. Choose Maintain On the Edit Table Views: Initial Screen, choose Edit.
5. Assign Node Type On the Change View “Allocation of Node Type”: Overview screen, assign the node type to
the plants as follows:
Example:
1010 – PL
1310 – PL
3710 – DC
6210 – DC
Note: The DC node type is used for distribution centers, PL for production plants.
6. Choose Save Choose Save.

2.5.3 Define MRP Area for Subcontractors
Use
In this step, you create an MRP area for subcontractors.
Procedure
2. Access Customizing with transaction SPRO Access Customizing by entering transaction code SPRO.
3. Navigate to IMG activity Choose Production → Material Requirements Planning → Master Data →
MRP Areas → Define MRP Areas for Subcontractors from the menu.
4. Choose New Entries On the Change View “MRP areas - Subcontracting”: Overview screen,
choose New Entries.
5. Enter Data for MRP Area On the New Entries: Details of Added Entries screen, enter the following
data:
MRP Area: 1010-10307
Description: Subcontractor 10300007
Plant: 1010
and press Enter.
6. Assign Subcontractor Double click the Subcontractor (one entry per MRP area) from the Dialog
Structure. On the Change View “Subcontractor (one entry per MRP area)“:
Overview screen, choose New Entries.
7. Assign Subcontractor On the New Entries: Overview of Added Entries screen, enter the follow- The MRP area for the subcontractor is cre-
ing data: ated.
Subcontr.: 10300007
and press Enter and then choose Save.
8. Repeat to Create Another MRP Area Repeat step 4 – 7 to create another MRP area for a subcontractor with the
following data:
MRP Area: 1310-13307

Description: Subcontractor 13300007

Plant: 1310
Subcontractor: 13300007
2.5.4 Maintain MRP Type and GR Processing Time in Material Master
Use
In this step, you assign the newly created MRP type X0 to materials that will be planned in SAP IBP and maintain the goods receipt (GR) processing time in the material master.
Procedure
2. Open transaction MM02 Enter transaction code MM02. Alternatively, choose Logistics → Materials Management →
Material Master → Material → Change from the menu.
3. Select material On the Change Material (Initial Screen), enter the following material:
<Material number>: FG126
4. Press Enter On the Change Material (Initial Screen), press E n t e r .
5. Select MRP 1 and MRP 2 views In the Select View(s) dialog box, select MRP 1 and MRP 2.
6. Choose Continue In the Select View(s) dialog box, choose Continue or press E n t e r .
7. Enter plant In the Organizational Levels dialog box, enter the following data:
Plant: 6210
8. Change MRP type On the Change Material (Finished Product) screen, enter the following data:
MRP Type: X0

9. Change GR processing time Press E n t e r to switch to the MRP 2 tab.

On the Change Material (Finished Product) screen, enter the following data:
Goods Rec. Proc. Time: 1
10. Choose Save On the Change Material (Finished Product) screen, choose Save. The new MRP type X0 and the GR
processing time are assigned to the
material.
11. Repeat steps 2–10 for other Material- Repeat steps 2–10 for other material-plant combinations as needed.
Plant combinations
For SAP S/4HANA Best Practices demo data, change the MRP type and Goods receipt pro-
cessing time for the following material-plant combinations:
Material Location MRP Type Goods Rec. Proc. Time
FG126 1310 X0 0
FG126 1010 X0 0
FG126 3710 X0 1
SG124 1010 X0 0
SG124 1310 X0 0
SG25 1010 X0 0
SG25 1310 X0 0
RM20 1010 X0 0
RM20 1310 X0 0
SG23 1010 X0 0
SG23 1310 X0 0
RM13 1010 X0 0
RM13 1310 X0 0
RM14 1010 X0 0

Material Location MRP Type Goods Rec. Proc. Time
RM14 1310 X0 0
2.5.5 Maintain Procurement Type in Material Master
Use
Caution: This step is only needed if you have activated the SAP S/4HANA Best Practices content with master data. In this step, you change the procurement type to External Procurement on the
material plant level. As a result, the requirement for the respective material in the respective plant will be fulfilled by stock transfer from another plant. If your master data reflects the actual
supply network relationship, you can skip this step.
For finished products in distribution centers (DCs), the procurement type is changed to External Procurement to avoid that production-related data is transferred to SAP IBP.
Procedure
2. Open transaction MM02 Enter transaction code MM02. Alternatively, choose Logistics → Materials Management →
Material Master → Material → Change from the menu.
3. Select the Material On the Change Material (Initial Screen), enter the following material:
<Material number>: FG126
4. Choose Enter On the Change Material (Initial Screen), press E n t e r .
5. Select MRP 2 view In the Select View(s) dialog box, select MRP 2.
6. Choose Continue In the Select View(s) dialog box, choose Continue or press E n t e r .

7. Enter Plant In the Organizational Levels dialog box, enter the following data:
Plant: 6210
8. Change Procurement Type On the Change Material (Finished Product) screen, enter the following data:
Procurement Type: F – External Procurement
9. Choose Save On the Change Material (Finished Product) screen, choose Save. The new procurement type is as-
signed to the material.
10. Repeat steps 3 to 9 for other Material- Repeat steps 2–9 for other material-plant combinations as needed.
Locations
For SAP S/4HANA Best Practices demo data, change the procurement type for the following
material-plant combinations:
FG126/3710
2.5.6 Maintain Customer Classification in Customer Master
Use
In this step, you assign a customer classification to customer master data. The customer classification can later be used for demand priority ranking.
Procedure
2. Open transaction BP Enter transaction code BP.
3. Specify the customer On the Maintain Business Partner screen, enter the Business Partner, for example,
62100001. Choose Enter, then double-click the selected customer.
4. Choose Switch between Display and Choose Switch between Display and Change (F6).
Change

5. Maintain customer classification In the Change in BP role field, choose Customer (Maintained).
6. Choose Customer: General Data tab Choose the Customer: General Data tab.
7. Maintain Customer Classification Maintain the customer classification in the Customer Classific. field, for example, A.
8. Save your changes Choose Save. The customer classification is saved.
9. Choose Open BP Choose Open BP. The Open business partner dialog
box is displayed.
10. Repeat steps 3 to 9 for other customers Repeat steps 5 to 9 for other customers:
62100003, A
37100001, B
37100002, B
2.5.7 Create Subcontracting Info Records
Use
In this step, you create the subcontracting info records. Real-time integration (RTI) will then integrate the subcontracting info records into SAP IBP as a transportation lane and the production
version ID will be assigned to this transportation lane.
Procedure
2. Open transaction ME11 Enter transaction code ME11. Alternatively, choose Logistics → Materials Management →
Purchasing → Master Data → Info Record → Create from the menu.
3. Enter Header Data On the Create Info Record: Initial Screen screen, make the following entries and then press
Enter.

Supplier: 10300007
Material: SG23
Purchasing Org.: 1010
Plant: 1010
Info Record Category: Subcontracting
4. Enter General Data On the Create Info Record: General Data screen, make the following entries and then press General data is added.
Enter.
Available From: Today
Available To: 12/31/9999
5. Enter Purchasing Data On the Create Info Record: General Data screen, choose Purch. Org. Data 1 to go to the Cre-
ate Info Record: Purch. Org. Data 1 screen.
6. Enter Purchasing Data On the Create Info Record: Purch. Org. Data 1 screen, make the following entries: Purchasing data is added.
In the Control section:
Pl. Deliv. Time: 3
Standard Quantity: 1
Version: 0001
Note: This is the production version ID of the subcontracting product.
In the Condition section:

Net Price: 1 EUR
Note: Here we only list the minimum required data relevant for the SAP IBP integration
for the subcontracting process.
7. Save your data Choose Save. The purchasing info record is saved.
8. Create next Info Record Repeat steps 2 – 7 to create another subcontracting info record with the following data:
Supplier: 13300007
Material: SG23
Purchasing Org.: 1310
Plant: 1310
Info Record Category: Subcontracting
Pl. Deliv. Time: 3
Standard Quantity: 1

Version: 0001
Net Price: 1 CNY
2.5.8 Create Sales Orders, Outbound Deliveries, and Initial Stock
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Tester Name Testing Date Click here to enter a date.
Business Role(s) Administrator (IBP)
Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration <Enter a duration, e.g. 60 minutes>
Purpose
In SAP S/4HANA, you create sales orders, outbound deliveries, and initial stock. This data is later transferred to SAP IBP.
Caution: Check the data in your system first. This step is only needed if your SAP S/4HANA system has no sales orders, outbound deliveries, or initial stock belonging to the integration model
you’ve defined. If relevant transactional data is available already, you can skip this step.
Note: After creating sales documents or stocks and completing the Create Stock Transfer Requisition and Stock Transfer Order section, you can follow the View Projected Stock section to check
the integration of sales documents and stocks from SAP S/4HANA to SAP IBP.
Procedure
1. Create Stock Follow test script BD9 (Sell from Stock, delivered in SAP The stock is posted in SAP
Best Practices for SAP S/4HANA) to create stock in SAP S/ S/4HANA.

4HANA with the following information and save.

App: Post Goods Movement
Transaction code: MIGO
Example:
Movement Type: 561
Material: FG126
Plant: 3710
Storage Location: 371A
Quantity: 1300
Movement Type: 561

Material: FG126
Plant: 1010
Storage Location: 101A
Quantity: 1500
2. Create Sales Orders Follow test script BD9 (Sell from Stock, delivered in SAP Sales orders are created in
Best Practices for SAP S/4HANA) to create sales orders in SAP S/4HANA.
SAP S/4HANA with the following information and save.
Caution: Due to the availability check triggered during

sales order creation, each sales order in SAP S/4HANA
can be either unconfirmed, partially confirmed, or
confirmed.
This confirmation status of each sales order is transferred
to SAP IBP during the inbound integration process.
Therefore, a confirmation status is shown in SAP IBP
before the confirmation run for the sales order has taken
place.
The confirmation run in SAP IBP then reconfirms or
calculates new confirmations for the sales orders.
App: Manage Sales Orders

Transaction code: VA01
Example:
Sales Order 1:
Order Type: OR

Sales Organization: 3710

Distribution Channel: 10
Division: 00
Customer: 37100001
Delivery Date: <current date + 14 days>
Material: FG126
Plant: 3710
Quantity: 600
Sales Order 2:
Order Type: OR
Division: 00
Customer: 37100001
Delivery Date: <current date + 21 days>
Material: FG126
Plant: 3710
Quantity: 1000
Sales Order 3:
Order Type: OR
Division: 00
Customer: 37100001
Delivery Date: <current date + 10 weeks>
Material: FG126
Plant: 3710
Quantity: 1000
3. Create Outbound Deliv- Follow test script BD9 (Sell from Stock, delivered in SAP Outbound delivery is created
ery Best Practices for SAP S/4HANA) to create an outbound de- in SAP S/4HANA.
livery in SAP S/4HANA.
App: Create Outbound Deliveries
Transaction code: VL01N

Example:
Shipping Point: 3710
Selection Date: <delivery selection date,
for example, current date + 14 days>
Order: <your sales order number>
From Item: <your sales order item number,
for example, 10>
2.5.9 Create Planned Orders and Production Orders
Test Administration
Purpose
In SAP S/4HANA, you create planned orders and production orders that are later transferred to SAP IBP.
Caution: Check the data in your system first. This step is only needed if your SAP S/4HANA system has no planned orders or production orders belonging to the integration model that you’ve
defined. If relevant transactional data are available already, you can skip this step.
Procedure
1. Create Planned Order Follow test script BJ5 (Make-to-Stock Production – Planned order is created in SAP S/4HANA.
Discrete Manufacturing, delivered in SAP Best Prac-

tices for SAP S/4HANA) to create planned orders in

SAP S/4HANA with the following information and
save.
App: Manage PIRs/Schedule MRP Runs
Transaction code: MD61/MD02
Example:
Planned Order Information:
Planned Order Profile: LA
Material: FG126
Plant / MRP Area: 1310
Order Quantity: 20
Basic Dates End: <current date + 20
days>
2. Create Production Order Follow test script BJ5 (Make-to-Stock Production – Production order is created in SAP S/4HANA.
Discrete Manufacturing, delivered in SAP Best Prac-
tices for SAP S/4HANA) to convert the planned order
into a production order.
App: Monitor Material Coverage Net/Individual Seg-
ments
Transaction code: MD04
Example:
Production Order Information:
Material: FG126
Production Plant: 1310
Order Quantity: 20
Basic Dates End: <current date + 7
days>.
Note: If you’ve created more than one planned

order, you can choose one planned order to convert
it into a production order.

2.5.10 Create Purchase Requisition and Purchase Order
Test Administration
Purpose
In SAP S/4HANA, you create purchase requisitions and purchase orders that are later transferred to SAP IBP.
Caution: Check the data in your system first. This step is only needed if your SAP S/4HANA system has no purchase requisitions or purchase orders belonging to the integration model that
you’ve defined. If relevant transactional data are available already, you can skip this step.
Procedure
1. Create Purchase Requisition and Pur- Follow test script J45 (Procurement of Direct Materials, deliv- The purchase requisition and purchase order are created in SAP
chase Order ered in SAP Best Practices for SAP S/4HANA) to create the S/4HANA.
purchase requisition and purchase order in SAP S/4HANA with
the following information and save.
App: Create Purchase Requisition Advanced/ Manage Purchase
Orders
Transaction code: ME51N/ME21N
Example:
Material: RM20
Purch. Org: 1310
Purch. Group: 001
Plant: 1310
Supplier: 13300001

2.5.11 Create Stock Transfer Requisition and Stock Transfer Order
Test Administration
Purpose
In SAP S/4HANA, you create stock transfer requisitions and stock transfer orders that are later transferred to SAP IBP.
Caution: Check the data in your system first. This step is only needed if your SAP S/4HANA system has no stock transfer requisitions or stock transfer orders belonging to the integration model
that you’ve defined. If relevant transactional data are available already, you can skip this step.
Procedure
1. Create Stock Transfer Requisition and Create a stock transfer requisition and a stock transfer order in Stock transfer requisition and stock transfer order are created in
Stock Transfer Order SAP S/4HANA with the following information and save. SAP S/4HANA.
App: Create Purchase Requisition Advanced/ Manage Purchase
Orders
Transaction code: ME51N/ME21N
Example:
Material: FG126
Purch. Org: 6210
Purch. Group: 001
Procurement Plant: 6210
Supplying Plant: 1310

3 Overview Table
This scope item consists of several process steps provided in the table below.
Process Step Business Role App/Transaction Expected Results
Integrate Configuration Data to IBP Administrator (IBP) SAP IBP Configuration data (UoM, currencies, calendars) are integrated to SAP IBP.
Application Jobs app
Maintain Additional Data for Production Data Structure Administrator (IBP) SAP S/4HANA Additional data (variable bucket consumption) for the production data struc-
Maintain Additional Data for Production Data ture is maintained.
Structure
Create Integration Model for Plants Administrator (IBP) SAP S/4HANA Integration model is created.
Transaction CFM1
Activate Integration Model for Plants Administrator (IBP) SAP S/4HANA Activating the integration models triggers an initial data transfer. Plants are
Transaction CFM2 transferred to SAP IBP.
Create Integration Model for Master Data Administrator (IBP) SAP S/4HANA Integration model is created.
Transaction CFM1
Activate Integration Model for Master Data Administrator (IBP) SAP S/4HANA Activating the integration models triggers an initial data transfer. Master
Transaction CFM2 data is transferred to SAP IBP.
View Master Data Supply Planner (IBP) SAP IBP Master data is successfully integrated from SAP S/4HANA to SAP IBP.
Manage Master Data app
Update Master Data through Data Integration Supply Planner (IBP) SAP IBP Additional master data is successfully updated via file upload.
Data Integration Jobs app
Update Master Data through Manage Master Data Supply Planner (IBP) SAP IBP Additional master data is successfully updated via Manage Master Data app.
Manage Master Data app
Create Application Job for Master Data Synchronization Administrator (IBP) SAP IBP Master data is synchronized.
Check Master Data Consistency with Machine Learning Administrator (IBP) SAP IBP Master data consistency is checked.
(Optional) Application Jobs app
Create Variant for Background Integration Model Activa- Administrator (IBP) SAP S/4HANA Variant is created.

Process Step Business Role App/Transaction Expected Results
tion Transaction SE38
Create Variant for Production Data Structures Change Administrator (IBP) SAP S/4HANA Variant is created.
Transfer Transaction CURTO_CREATE_IBP
Create Variant for Deactivated Integration Models Deletion Administrator (IBP) SAP S/4HANA Variant is created.
Transaction SE38
Create and Schedule Background Job for Master Data Administrator (IBP) SAP S/4HANA Background job is created and scheduled.
Changes Transaction SM36
Create Integration Model for Transactional Data Administrator (IBP) SAP S/4HANA Integration model is created.
Transaction CFM1
Activate Integration Model for Transactional Data Administrator (IBP) SAP S/4HANA Activating the integration models triggers an initial data transfer. Transac-
Transaction CFM2 tional data is transferred to SAP IBP.
View Projected Stock Supply Planner (IBP) SAP IBP Orders have been transferred from SAP S/4HANA.
Projected Stock app
Check Integration Result in SAP Integrated Business Plan- Supply Planner (IBP) SAP IBP Data displayed correctly in Excel add-in.
ning, Add-In for Microsoft Excel Excel add-in
(RM 010 Forecast and Constraints planning
view)
Set Up Outbound Integration in Real-Time Integration Pro- Administrator (IBP) SAP IBP The real-time integration profile is maintained.
file Real-Time Integration Profiles app
Run Reconciliation Job (optional) Administrator (IBP) SAP IBP Data inconsistencies are identified.
Solve Data Inconsistencies (optional) Administrator (IBP) SAP IBP Data inconsistencies are corrected after reconciliation.
Data Comparison and Reconciliation for RTI
app

4 Test Procedures
This section describes test procedures for each process step that belongs to this solution process.
4.1 Configuration Data
4.1.1 Integrate Configuration Data to IBP
Test Administration
Purpose
You integrate configuration data, that is, factory calendar, unit of measure, and currency information to SAP IBP by running the Real-Time Integration (Calendar, UoM, Currency) application job.
Procedure
1. Log on to SAP Integrated Business Log on to the SAP Integrated Business Planning web user inter- The SAP Fiori launchpad as the access point to all web-based ap-
Planning face. plications for SAP Integrated Business Planning is displayed.
Apps are displayed as tiles.
2. Open Application Jobs App Open the Application Jobs app by clicking the corresponding
tile.

3. Create Job Choose Create. The New Job screen is displayed.
4. Enter Parameters The New Job screen is designed as a guided procedure that com-
prises several main sections. You can sequentially navigate
through the individual sections by filling in the required data
and then choosing Step x where x is the number of the next step.
Enter the following data:
Example:
Template Selection
Job Template: Real-Time Integration
(Calendar, UoM, Currency)
Job Name: Real-Time Integration
(Calendar, UoM, Currency)
Scheduling Options
Start Immediately: Select the checkbox
Parameters
Source Logical System: S4HCLNT001
Currency: X (selected)
Factory Calendar: X (selected)
Unit of Measure: X (selected)
5. Schedule Job Choose Schedule.
6. Check Job Status Choose Go to refresh the job status until the status is set to Fin-
ished.
4.2 Master Data
4.2.1 Maintain Additional Data for Production Data Structure
Test Administration

Purpose
A production data structure (PDS) is used in SAP IBP as a source of supply for in-house production. It contains the capacities and components required to manufacture the finished product. The PDS
of SAP IBP is generated from the SAP S/4HANA PDS which is created from the production version, routing, and bill of material (BOM).
In this step, you maintain additional data (like the variable bucket consumption of capacities) in SAP S/4HANA before you execute the initial load.
Procedure
1. Maintain Additional Data for Produc- In the SAP S/4HANA system, access the transaction using The Selection for Production Data Structures dialog box is dis-
tion Data Structure using SAP GUI transaction code /nPDS_MAINT or open the following menu played.
path:
Logistics → Central Functions → Supply Chain Planning Inter-
face → Integrated Business Planning → Maintain Master Data
→ Location Material → Maintain Additional Data for Produc-
tion Data Structure
2. Specify Data Selection In the Selection for Production Data Structures dialog box,
make the following entries (choose Multiple Selection):
Example:
Material No.: FG126, SG124
Plnt: 1310, 1010
PDS Usage in SCM: S
3. Choose Execute Choose Execute. The Maintain Additional Data for Production Data Structures
screen is displayed.
4. Select one entry On the Maintain Additional Data for Production Data Structures Detailed information is displayed in the lower part of the screen.
screen, select one entry by choosing the PDS Detail Information
icon in the Details column.
Example:

Material: FG126
Plant: 1310
Version: 0001
PDS Type in SCM: S
5. Navigate to Operat. Data tab In the lower part of the screen, navigate to the Operat. Data tab.
6. Maintain Additional Data On the Operat. Data tab, maintain the BucketCons (Variable
Bucket Consump.) values for the operations.
Example:
Activity: 0010
Acty Type: P
Work center: ASSEMBLY
BucketCons: 2
Activity: 0020
Acty Type: P
Work center: TESTING
BucketCons: 1
Activity: 0030
Acty Type: P
Work center: PACK01
BucketCons: 1
Caution: The BucketCons value is the variable bucket

consumption for one product. Only Activity Type P will be
considered in SAP IBP.
7. Select another entry On the Maintain Additional Data for Production Data Structures
Example:
Material: FG126
Plant: 1010
Version: 0001
PDS Type in SCM: S
8. Navigate to Operat. Data tab On the lower part of the screen, navigate to the Operat. Data tab.

Example:
Activity: 0010
Acty Type: P
Work center: ASSEMBLY
BucketCons: 2
Activity: 0020
Acty Type: P
Work center: TESTING
BucketCons: 1
Activity: 0030
Acty Type: P
Work center: PACK01
BucketCons: 1

Example:
Material: SG124
Plant: 1310
Version: 0001
PDS Type in SCM: S
Example:
Activity: 0010
Acty Type: P
Work center: TECHNIC
BucketCons: 1


Example:
Material: SG124
Plant: 1010
Version: 0001
PDS Type in SCM: S
Example:
Activity: 0010
Acty Type: P
Work center: TECHNIC
BucketCons: 1

15. Choose Back Choose Back.
4.2.2 Create Integration Model for Plants
Test Administration

Purpose
When you generate an integration model for plants, you specify which plants are to be selected from the total dataset in the SAP S/4HANA system. Only this specified dataset will be transferred to
SAP IBP.
A separate integration model for plants is useful because we assume that the layout of the supply chain network (in particular, regarding plants and distribution centers) does not change as often as
other master data. Therefore, this integration model will not be included in the background job for master data changes that is explained later in this test script (see Error: Reference source not found
Error: Reference source not found).
Note: CIF provides a standard integration model to prepare data to be transferred from SAP S/4HANA to SAP IBP. You can use business add-ins (BAdIs) to overrule the integration model,
enabling you to transfer attributes that aren’t included in a standard integration model. This doesn’t change the data in your external system. The use of BAdIs is optional. For more information,
see Business Add-Ins (BAdIs) for SAP IBP, Integration of Location. You can also refer to SAP Note 3110007.
Procedure
1. Create Integration Model In the SAP S/4HANA system, access the transaction using The Create Integration Model screen is displayed.
transaction code CFM1 or open the following menu path:
face → Real-Time Integration with SAP IBP → Integration
Model → Create
2. Enter Header Data of Integration Model Enter the following data:
Example:
Model Name: IBP_SUP_PL
Logical System: <Your IBP Logical System>
for example ZXYCLNT100
APO Application: RTI
3. Select Plants In the Material Dependent Objects section, enter the following The Plants indicator is selected.
data:
Plants: X (selected)

4. Enter General Selection Options for In the General Selection Options for Materials section, enter the The plant master data to be transferred to SAP IBP is specified.
Materials following data:
Caution: Selection options are important to avoid that non-
Example: relevant plants in SAP S/4HANA are transferred to SAP IBP
Plnt: Select the plants to be transferred as locations.
1010, 1310, 3710, 6210 Before activating the integration model, you can check the
objects to be transferred.
5. Create Variant On the Create Integration Model screen, choose Goto à Vari- The Variant Attributes screen is displayed.
ants à Save as Variant …. Since the system does not save the selection options you make
when creating an integration model, you can save the settings as a
variant on the selection screen. Variants allow you to reuse the
settings you have saved whenever you want. If you want to recre-
ate an integration model at a later time, you can call up the re-
quired variant by choosing the Select Variant icon in the toolbar
at the top of the selection screen.
6. Enter Variant Attributes On the Variant Attributes screen, enter the following data:
Example:
Variant Name: IBP_SUP_PL
Description: Variant IBP_SUP_PL Plant Model
7. Save Variant On the Variant Attributes screen, choose Save. The variant is saved.
8. Choose Execute On the Create Integration Model screen, choose Execute. The integration model is saved.
Note: Before generating and activating the integration model,

you can check the objects included that will be transferred. On
the Create Integration Model screen, choose No. Filter Objects
for the relevant Filter Object.
For example, by checking the No. Filter Objects for Plants,
you can check the plants included in the integration model
that will be transferred to SAP IBP as locations.
9. Choose Generate IM On the Create Integration Model screen, choose Generate IM. The Integration Model is generated.

4.2.3 Activate Integration Model for Plants
Test Administration
Purpose
Activating the integration model for plants triggers an initial data transfer of plant master data from SAP S/4HANA to SAP IBP.
Plants are transferred to SAP IBP as locations.
Procedure
1. Activate Integration Model In the SAP S/4HANA system, access the transaction using The Activate or Deactivate Integration Model screen is displayed.
Model → Activate
2. Enter Selection Criteria On the Activate or Deactivate Integration Model screen, enter Selection criteria is specified.
the following data:
Example:
Model: IBP_SUP_PL
Logical System: <Your IBP Logical System> for
example ZXYCLNT001
3. Choose Execute On the Activate or Deactivate Integration Model screen, choose SAP S/4HANA plant master data is transferred to SAP IBP.
Execute.

4. Expand All Nodes In the hierarchy view on the left side of the screen, select Inte-
gration Models and choose Expand All Nodes.
5. Select RTI Node of Integration Model Double-click the RTI node of your integration model. A table is displayed on the right side of the screen that shows the
integration model versions.
6. Select Line in the Table Select a line in the table.
7. Choose Active/Inactive Choose Active/Inactive. The New Status column is switched to Active.
8. Choose Start Choose Start. The Prev. Status column is switched to Active. Master data is
transferred to SAP IBP.
4.2.4 Create Integration Model for Master Data - General
Test Administration
Purpose
When you generate an integration model for master data, you specify which master data objects are to be selected from the total dataset in the SAP S/4HANA system. Only this specified dataset will
be transferred to SAP IBP.
Note: In the example described in the SAP Best Practices for SAP IBP, we create integration models for plants, master data, and transactional data. In an implementation project, you might
consider to further split the integration models for master data. For example, you could create separate integration models for materials, customers, work centers, purchasing info records, and
production data structures.
Note: CIF provides a standard integration model to prepare data to be transferred from SAP S/4HANA to SAP IBP. You can use business add-ins (BAdIs) to overrule the integration model,
enabling you to transfer attributes that aren’t included in a standard integration model. This doesn’t change the data in your external system. The use of BAdIs is optional. For more information,
see Business Add-Ins (BAdIs) for SAP IBP, Integration of Location, Integration of Products and Location Products, Integration of Resources, Integration of Production Data Structures,
Integration of Purchasing Info Records, Integration of Special Procurement Type of the Material Master Records. You can also refer to SAP Note 3110007.
Procedure
Model → Create
Example:
Model Name: IBP_SUP_MD
example ZXYCLNT100
3. Select Materials and Plants In the Material Dependent Objects section, enter the following The Materials indicator is selected.
data:
Materials: X (selected)
4. Enter General Selection Options for In the General Selection Options for Materials section, enter the The material master data to be transferred to SAP IBP is speci-
Materials following data: fied.
Example: Caution: Selection options are important to avoid that non-

Material: Select the material master to be transferred to SAP relevant material-plant combinations in SAP S/4HANA are
IBP FG126, SG124, SG25, RM20, SG23, transferred to SAP IBP as product-location combinations.
RM13, RM14 Before activating the integration model, you can check the
Plnt: Select the plants for which the material is to be

transferred 1010, 1310, 3710, 6210
MRP Type: Select the MRP Type for which the material is
to be transferred. This is the one you defined in chapter
Define MRP Type X0.
X0 - Without MRP, with BOM Explosion

5. Select Purchasing Info Record In the Material Dependent Objects section, enter the following Pur. Info Record indicator is selected.
data:
Pur.Info Record: X (selected)
6. Enter Selection of Source of Supply Choose Further Restrictions next to Pur.Info Record and enter The purchasing info records that are to be transferred to SAP In-
the following data in the Selection of Source of Supply section: tegrated Business Planning are specified.
Material-Dependent Source of Supply Selection: X (se-
Caution: Sources of supply are integrated as transportation
lected)
lanes to SAP IBP. Note that you will have to add further
Include Dependent Vendors and Issuing Plants: X (se- information to the transportation lanes after they were
lected) integrated to SAP IBP. For more information, see chapters
Standard Info Record: X (selected) Update Master Data through Data Integration and Update
Master Data via Excel Master Data Workbook.
Note: The Material and Plnt selection criteria specified
under General Selection Options for Materials will also be
applied to the Purchasing Info Record selection.
7. Select PDS (ERP) In the Material Dependent Objects section, enter the following The PDS (ERP) indicator is selected.
data:
PDS (ERP): X (selected)
8. Enter Production Data Structure Choose Further Restrictions next to PDS (ERP) and enter the The production data structures to be transferred to SAP IBP are
following data in the Production Data Structure section: specified.
Example:
PDS Type: SNP
Prod. Version: 0001
9. Select Material Independent Objects to In the Material Independent Objects section, enter the following The Customers, Work Centers, and Vendors indicators are se-
be Transferred data: lected.
Customers: X (selected)
Work Centers: X (selected)
Vendors: X (selected)
10. Select Customers Choose Special Restrictions next to Customers and enter the fol- The customers to be transferred to SAP IBP are specified.
lowing data in the Customers section:
Example:
Customer:
37100001
37100002
62100001
62100003

PLNTC_3710
PLNTC_6210
11. Select Work Centers Choose Special Restrictions next to Work Centers and enter the The work centers to be transferred to SAP IBP are specified.
following data in the Resources section:
Example:
Work Center:
ASSEMBLY
TESTING
PACK01
TECHNIC
Plant:
1010
1310
12. Select Vendors Choose Special Restrictions next to Vendors and enter the fol- The vendors to be transferred to SAP IBP are specified.
lowing data in the Vendors section:
Example:
Supplier:
10300001
13300001
10300007
13300007
Note: If you use purchasing info records for stock transfer

processes where a dummy vendor has a supply plant
assigned, you must integrate this vendor as well:
PLNTV_1010
PLNTV_1310

Example:
Variant Name: IBP_SUP_MD_GEN
Description: Variant IBP_SUP_MD Model Gen

For example, by checking the No. Filter Objects for Material
Master Data, you can check the material-plant combinations
included in the integration model that will be transferred to
SAP IBP as product-location combinations.
4.2.5 Activate Integration Model for Master Data - General
Test Administration
Purpose
Activating the master data integration model triggers an initial data transfer of master data from SAP S/4HANA to SAP IBP.

Procedure
Model → Activate
the following data:
Example:
Model: IBP_SUP_MD
example ZXYCLNT001
3. Choose Execute On the Activate or Deactivate Integration Model screen, choose SAP S/4HANA master data is transferred to SAP IBP.
Execute.
4.2.6 Create Integration Model for Master Data – Subcontracting-Specific
Test Administration

Purpose
For subcontracting, the integration of the PDS from SAP S/4HANA to SAP IBP is different than the integration of other PDS types. The PDS at subcontractor locations can be integrated to SAP IBP
by selecting the PDS type SNP Subcontracting in the integration model. This subcontracting PDS must be assigned to an info record with the category Subcontracting in SAP S/4HANA.
In this step, you create a new integration model to integrate subcontracting-related master data.
Procedure
Model → Create
Example:
Model Name: IBP_SUBCON
example ZXYCLNT100
3. Enter General Selection Options for In the General Selection Options for Materials section, enter the The material master data to be transferred to SAP IBP is speci-
Materials following data: fied.

Material: Select the material master to be transferred to SAP relevant material-plant combinations in SAP S/4HANA are
IBP SG23, RM13, RM14 transferred to SAP IBP as product-location combinations.
Before activating the integration model, you can check the

Define MRP Type X0.
X0 – Without MRP, with BOM Explosion
4. Select Purchasing Info Record In the Material Dependent Objects section, enter the following Pur. Info Record indicator is selected.
data:
Pur.Info Record: X (selected)
5. Enter Selection of Source of Supply Choose Further Restrictions next to Pur.Info Record and enter The purchasing info records that are to be transferred to SAP IBP
the following data in the Selection of Source of Supply section: are specified.
Material-Dependent Source of Supply Selection: X (se-
lected)
Include Dependent Vendors and Issuing Plants: X (se-
lected)
Subcontracting Info Record: X (selected)
Note: The Material and Plnt selection criteria specified

under General Selection Options for Materials will also be
applied to the Purchasing Info Record selection.
6. Select PDS (ERP) In the Material Dependent Objects section, enter the following The PDS (ERP) indicator is selected.
data:
PDS (ERP): X (selected)
7. Enter Production Data Structure Choose Further Restrictions next to PDS (ERP) and enter the The production data structures to be transferred to SAP IBP are
following data in the Production Data Structure section: specified.
Example:
PDS Type: SNP Subcontracting
Prod. Version: 0001
Example:

Variant Name: IBP_SUBCON

Description: Variant IBP_SUBCON Model Gen

12. Choose Generate IM On the Create Integration Model screen, choose Generate IM. The integration model is generated.
4.2.7 Activate Integration Model for Master Data – Subcontracting-Specific
Test Administration
Purpose
Activating the master data integration model triggers an initial data transfer of master data from SAP S/4HANA to SAP IBP.

Procedure
Model → Activate
the following data:
Example:
Model: IBP_SUBCON
example ZXYCLNT001
Execute.
4.2.8 View Master Data
Test Administration

Business Role(s) Supply Planner (IBP)
Purpose
Use the Manage Master Data app to check the master data integrated from SAP S/4HANA.
Note: If you can’t find the data outlined in the next steps in your SAP IBP system, you can use the SAP IBP Monitor bgRFC Queues app to monitor the integration queues.
Procedure
Planning web user interface face. plications (apps) for SAP Integrated Business Planning is dis-
played. Apps are displayed as tiles.
2. Open Manage Master Data app Open the Manage Master Data app by choosing the correspond- The Manage Master Data screen is displayed.
ing tile on the launchpad.
3. Choose Filter On the Manage Master Data screen, choose Filter.
4. Filter Data In the Filter dialog box, select your planning area and choose
OK.
Example:
5. Select Location Master Data Choose the Location master data type. The location master data records are displayed in a table that
opens on the right side of the screen.
Example:
RM1LOCATION
6. Check Location Master Data Vendors and Plants from SAP S/4HANA are integrated as Loca- All required plants and vendors were integrated from SAP S/
tions to SAP IBP. Vendors have Type-Location V, plants have 4HANA to SAP IBP.
Type-Location P assigned.

Check if all your locations were integrated.
Example:
Type-Location P (Plants):
Plant 1 DE (1010)
Plant 1 CN (1310)
Plant 1 NL (3710)
Plant 1 HK (6210)
Type-Location V (Vendors):
0010300001
0013300001
0010300007
0013300007
PLNTV_1010
PLNTV_1310
7. Select Customer Master Data In the Master Data Types table on the left side of the screen, The customer master data records are displayed in the table on the
choose the Customer master data type. right side of the screen.
Example:
RM1CUSTOMER
8. Check Customer Master Data Check if all your customers were integrated. All required customers were integrated from SAP S/4HANA to
SAP IBP.
Example:
Binnenlandse klant NL1 (0037100001)
Binnenlandse klant NL2 (0037100002)
Domestic HK Customer 1 (0062100001)
Domestic HK Customer 2 (0062100003)
PLNTC_3710
PLNTC_6210
9. Select Product Master Data In the Master Data Types table on the left side of the screen, The product master data records are displayed in the table on the
choose the Product master data type. right side of the screen.
Example:
RM1PRODUCT
10. Check Product Master Data Check if all your materials were integrated as products. All required products were integrated from SAP S/4HANA to
SAP IBP.
Example:
FG126

RM20
SG124
SG25
SG23
RM13
RM14
11. Select Location Product Master Data In the Master Data Types table on the left side of the screen, The location product master data records are displayed in the ta-
choose the Location Product master data type. ble on the right side of the screen.
Example:
RM1LOCATIONPRODUCT
12. Check Location Product Master Data Check if all your plant-material combinations were integrated as All required location products were integrated from SAP S/
location products. 4HANA to SAP IBP.
Example:
Location/Material
1010/FG126, 1010/RM20, 1010/SG124, 1010/SG25,
1010/SG23, 1010/RM13, 1010/RM14,
0010300007/SG23, 0010300007/RM13,
0010300007/RM14,
1310/FG126, 1310/RM20, 1310/SG124, 1310/SG25,
1310/SG23, 1310/RM13, 1310/RM14, 0013300007/SG23,
0013300007/RM13, 0013300007/RM14,
3710/FG126,
6210/FG126,
13. Select Transportation Lane Master Data In the Master Data Types table on the left side of the screen, The transportation lane master data records are displayed in the
choose the Transportation Lane master data type. table on the right side of the screen.
Example:
RM1TLANE
14. Check Transportation Lane Master Data Check if all your supplier info records were integrated as trans- All required transportation lanes were integrated from SAP S/
portation lanes. 4HANA to SAP IBP.
Example:
Mode of Transport / Product ID / Ship-From Location /
Ship-To Location
DEF / FG126 / 1010 / 3710
DEF / FG126 / 1310 / 3710
DEF / FG126 / 1310 / 6210

DEF / RM20 / 0010300001 / 1010

DEF / SG25 / 0010300001 / 1010
DEF / RM20 / 0013300001 / 1310
DEF / SG25 / 0013300001 / 1310
DEF / RM13 / 0010300001 / 1010
DEF / RM14 / 0010300001 / 1010
DEF / RM13 / 0013300001 / 1310
DEF / RM14 / 0013300001 / 1310
DEF / RM13 / 1010 / 0010300007
DEF / RM14 / 1010 / 0010300007
DEF / RM13 / 1310 / 0013300007
DEF / RM14 / 1310 / 0013300007
DEF / SG23/ 0010300007 / 1010
DEF / SG23/ 0013300007 / 1310
15. Select Resource Master Data In the Master Data Types table on the left side of the screen, The resource master data records are displayed in the table on the
choose the Resource master data type. right side of the screen.
Example:
RM1RESOURCE
16. Check Resource Master Data Check if all your work centers were integrated as resources. All required resources were integrated from SAP S/4HANA to
SAP IBP.
Example:
Assembly_001 (WASSEMBLY_1010_001)
Assembly_001 (WASSEMBLY_1310_001)
Packaging_001 (WPACK01_1010_001)
Packaging_001 (WPACK01_1310_001)
Tech_001 (WTECHNIC_1010_001)
Tech_001 (WTECHNIC_1310_001)
Testing_001 (WTESTING_1010_001)
Testing_001 (WTESTING_1310_001)
17. Select Production Data Structure (PDS) In the Master Data Types table on the left side of the screen, The PDS master data records are displayed in the table on the
Master Data choose the Production Data Structure (PDS) master data type. right side of the screen.
Example:
RM1PDS
18. Check Production Data Structure (PDS) Check if all your production data structures were integrated. All required production data structures were integrated from SAP
Master Data S/4HANA to SAP IBP.

Example:
Location ID / Product ID / Production Version ID For the subcontracting PDS, the related production version ID in
SAP IBP is a concatenated value of the plant ID and the original
1010 / FG126 / Version 0001 (0001)
production version ID in SAP S/4HANA. The location ID as-
1010 / SG124 / Version 0001 (0001) signed to the subcontracting PDS is that of the supplier, not of the
1010 / SG23 / Version 0001 (0001) plant.
1310 / FG126 / Version 0001 (0001)
1310 / SG124 / Version 0001 (0001)
1310 / SG23 / Version 0001 (0001)
0010300007 / SG23 / Version 0001 (00011010)
0013300007 / SG23 / Version 0001 (00011310)
19. Select PDS Activity Master Data In the Master Data Types table on the left side of the screen, The PDS activity master data records are displayed in the table on
choose the PDS Activity master data type. the right side of the screen.
Example:
RM1PDSACT
20. Check PDS Activity Master Data Check if all your PDS activities were integrated. All required PDS activities were integrated from SAP S/4HANA
to SAP IBP.
Example:
Activity ID / Location ID / Product ID / Production Version
ID
DEF / 1010 / FG126 / 0001
DEF / 1010 / SG124 / 0001
DEF / 1010 / SG23 / 0001
DEF / 0010300007/ SG23 / 00011010
DEF / 1310 / FG126 / 0001

DEF / 1310 / SG124 / 0001
DEF / 1310 / SG23 / 0001
DEF / 0013300007/ SG23 / 00011310
21. Select PDS Component Master Data In the Master Data Types table on the left side of the screen, The PDS component master data records are displayed in the ta-
choose the PDS Component master data type. ble on the right side of the screen.
Example:
RM1PDSCOMP
22. Check PDS Component Master Data Check if all your PDS components were integrated. All required PDS components were integrated from SAP S/
4HANA to SAP IBP.
Example:

Location ID / Product ID / Production Version / Activity

ID / Component Product ID
1010 / FG126 / 0001 / DEF / RM20
1010 / FG126 / 0001 / DEF / SG124
1010 / FG126 / 0001 / DEF / SG25
1010 / FG126 / 0001 / DEF / SG23
1010 / SG23 / 0001 / DEF / RM13
1010 / SG23 / 0001 / DEF / RM14
0010300007/ SG23 / 00011010 / DEF / RM13
0010300007/ SG23 / 00011010 / DEF / RM14
1310 / FG126 / 0001 / DEF / RM20
1310 / FG126 / 0001 / DEF / SG124
1310 / FG126 / 0001 / DEF / SG25
1310 / FG126 / 0001 / DEF / SG23
1310 / SG23 / 0001 / DEF / RM13
1310 / SG23 / 0001 / DEF / RM14
0013300007/ SG23 / 00011310 / DEF / RM13
0013300007/ SG23 / 00011310 / DEF / RM14
23. Select PDS Resource Master Data In the Master Data Types table on the left side of the screen, The PDS Resource master data records are displayed in the table
choose the PDS Resource master data type. on the right side of the screen.
Example:
RM1PDSRES
24. Check PDS Resource Master Data Check if all your PDS resources have been integrated. All required PDS resources were integrated from SAP S/4HANA
to SAP IBP.
Example:
Location ID / Product ID / Production Version / Resource
ID
1010 / FG126 / 0001 / WASSEMBLY_1010_001
1010 / FG126 / 0001 / WPACK01_1010_001
1010 / FG126 / 0001 / WTESTING_1010_001
1010 / SG124 / 0001 / WTECHNIC_1010_001
1310 / FG126 / 0001 / WASSEMBLY_1310_001

1310 / FG126 / 0001 / WPACK01_1310_001
1310 / FG126 / 0001 / WTESTING_1310_001
1310 / SG124 / 0001 / WTECHNIC_1310_001

4.2.9 Update Master Data through Data Integration
Test Administration
Purpose
Once the master data has been integrated from SAP S/4HANA, you need to enhance it with further settings that are not covered by the integration process. For Demand Type, Location, Location
Product, and Resource master data, you can use the Data Integration Jobs app and upload CSV files.
Procedure
Planning web user interface face. plications for SAP Integrated Business Planning is displayed.
2. Open Data Integration Jobs app Open the Data Integration Jobs app by choosing the correspond- The Data Integration Jobs screen is displayed.
ing tile on the launchpad.
3. New Data Integration Job Choose Add on the lower left side of the screen. The New Import Job screen is displayed.
4. Upload Demand Type Master Data On the New Import Job screen, make the following entries:
Data Type: Master Data
Master Data Name: RM1DEMANDTYPE
File: OBP_DemandType.csv
Separator: Semicolon (;)
Operation Type: Insert/Update
Job Name: Leave the default value

5. Choose Save and New On the lower part of the New Import Job screen, choose Save On the New Import Job screen, your new job is listed with the
and New. Processing status.
6. Upload Location Master Data Repeat steps 3 to 5 with the following data: Note:
Data Type: Master Data In addition to the data already integrated from SAP
Master Data Name: RM1LOCATION S/4HANA, this step loads data into the following attributes:
File: OBP_Location.csv Geo Latitude
Separator: Semicolon (;) Geo Longitude

7. Upload Location Product Master Data Repeat steps 3 to 5 with the following data: Note: In addition to the data already integrated from SAP
Data Type: Master Data S/4HANA, this step loads data into the following attributes:
Master Data Name: RM1LOCATIONPRODUCT Forecast Consumption Profile
File: OBP_LocationProduct.csv Product Allocation Profile
Separator: Semicolon (;) Shipping Calendar ID

Inbound Calendar ID
8. Upload Resource Master Data Repeat steps 3 to 5 with the following data: Note: To model supplier constraints, you must upload
Data Type: Master Data resources of Resource Type 3.
Master Data Name: RM1RESOURCE
File: OBP_Resource_Supplier.csv
Separator: Semicolon (;)
4.2.10 Update Master Data through Manage Master Data App
Test Administration

Business Roles Supply Planner (IBP)
Purpose
Once the master data has been integrated from SAP S/4HANA, you need to enhance it with further settings that are not covered by the integration process.
You use the Manage Master Data app to update transportation lanes and transportation lane resources.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail / Comment
#
1. Log on to SAP Integrated Log on to the SAP Integrated Business Planning web user interface. The SAP Fiori launch-
Business Planning web pad as the access point
user interface to all web-based appli-
cations for SAP Inte-
grated Business Plan-
ning is displayed. Apps
are displayed as tiles.
2. Open Manage Master Open the Manage Master Data app by clicking the corresponding tile on the launchpad. The Manage Master
Data app Data screen is dis-
played.
3. Search Transportation In the Search field, enter the transportation lane master data type associated with your planning area (see Setup instructions for
Lane Master Data Type implementing order-based planning, section Copying Sample Planning Area), and choose the Search icon.
Example:
Transportation Lane (SF7TLANE)
4. Select Transportation Select the Master Data Type: Transportation Lane (SF7TLANE).
Lane Master Data Type
5. Search Products In the Product field on the right side of the Manage Master Data screen, enter the following products. Then choose Go. The master data is dis-
played.
Example:
FG126

#
6. Go to Settings and select Choose Settings and select attributes Transportation Lane Priority and Transportation Calendar ID.
additional attributes
7. Choose Mass Edit and Choose Mass Edit and maintain the Transportation Lane Priority and Transportation Calendar ID with the following data:
maintain the data
Example:
Ship-To Mode of Transportation Transportation

Ship-From Loc. ID Product ID
Location ID Transport ID Lane Priority Calendar ID
1010 3710 DEF FG126 200 W8
1310 3710 DEF FG126 100 W8
1310 6210 DEF FG126 100 W8
played.
Example:
RM13, RM14
10. Choose Mass Edit and Choose Mass Edit and maintain the Lead Time with the following data:
maintain the data
Example:
Ship-From Loc. ID Ship-To Location ID Mode of Transport ID Product ID Lead Time
1010 0010300007 DEF RM13 1
1010 0010300007 DEF RM14 1
1310 0013300007 DEF RM13 1
1310 0013300007 DEF RM14 1
played.
Example:

#
RM20, SG25
13. Note down Additional Note down the Additional Lane ID for purchased products (see example below). Note: The
Lane ID Additional Lane ID
Example: is used to maintain
Additional Lane ID: 0_1010_3_5300000072_000000 the transportation
The Additional Lane ID is defined in SAP ERP or SAP S/4HANA as a concatenation of the following lane resource.
attributes: Stock Transfer Type, Purchasing Organization, Reference Document Category, and Reference
Document Number
Ship-From Loc. Ship-To Mode of Additional Lane ID

Product ID
ID Location ID Transport ID (note down your ID here)
0010300001 1010 DEF RM20 <ID 1>
0010300001 1010 DEF SG25 <ID 2>
0013300001 1310 DEF RM20 <ID 3>
0013300001 1310 DEF SG25 <ID 4>
14. Search Transportation In the Search field, enter the transportation lane resource master data type associated with your planning area (see Setup instruc-
Lane Resource Master tions for implementing order-based planning, section Copying Sample Planning Area), and choose the Search icon.
Data Type
Example:
Transportation Lane Resource (SF7TLANERESOURCE)
15. Select Transportation Select the Master Data Type: Transportation Lane Resource (SF7TLANERESOURCE).
Lane Resource Master
Data Type
16. Search Products In the Product field on the right side of the Manage Master Data screen, enter the following products. Then choose Go. Empty record in the ta-
ble.
Example:
SG25
RM20

#
17. Choose Mass Edit and Choose Mass Edit and enter the following data for the transportation lane resource: Note: The
maintain Transportation Additional Lane ID
Lane Resource Note: Instead of manually entering the records, you can also copy the records from the table below and paste them into the is an attribute of the
mass maintenance table. To copy and paste, you need to ensure that the attributes are in the same sequence in both tables.
transportation lane
The resource ID must be consistent with the uploaded file OBP_Resource_Supplier.CSV. master data type.
The Additional Lane
IDs that you must
Additional Resource ID use here are the ones
Mode of Ship-To
Lane ID Product Ship-From Loc. you noted down in
Transport Location
ID ID the previous step.
ID ID
10300001_1010_RM20
<ID 1> DEF RM20 0010300001 1010
10300001_1010_SG25
<ID 2> DEF SG25 0010300001 1010
13300001_1310_RM20
<ID 3> DEF RM20 0013300001 1310
13300001_1310_SG25
<ID 4> DEF SG25 0013300001 1310
Add the following data to all above transportation lane resource records:
Attributes Value
Capacity Consumption Rate Source 0
Capacity Base Quantity 1
Capacity Consumption Rate 1
4.2.11 Create Application Job for Master Data Synchronization
Test Administration

Purpose
In the following two cases, you need to run the Order-Based Planning: Master Data Synchronization job template to synchronize the master data of the planning area with the OBP Master Data
Store:
 Additional fields such as the allocation profile have been loaded using the Data Integration app or SAP CI-DS. (This case is covered in this document and was described in the previous two
chapters.)
 Attribute values have been set with any kind of operator, such as ABC/XYZ segmentation.
Procedure
tile.
Example:
Template Selection
Job Template: Order-Based Planning:
Master Data Synchronization
Job Name: Order-Based Planning: Master
Data Synchronization
Scheduling Options


Parameters
Planning Area Version: RM1SAP7F/Base
Version
ished.
4.2.12 Check Master Data Consistency with Machine Learning (Optional)
Test Administration
Purpose
After the master data has been loaded to SAP Integrated Business Planning, you can check master data consistency using application job template ML Master Data Consistency. By means of the ML
Master Data Consistency job, machine learning can learn semantic rules to identify problems in master data and recommend values for correction. In this chapter, you run the ML Master data
Consistency job on attributes PRODGROUP and PRODTYPE of the data type PRODUCT, for instance.
Note: There are other ways to analyze patterns. You can use the Manage Master Data app and review the results from that app in the Discover Patterns in Master Data app. For more details on
analyzing patterns using Manage Master Data app, see Discover Patterns in Master Data | SAP Help Portal.

Procedure
2. Open Application Jobs App Open the Application Jobs app by choosing the corresponding
tile.
Example:
Template Selection
Job Template: ML Master data Consistency
Job Name: Enter a name for your job or leave the
default one.
Scheduling Options
Parameters
Master Data Type: Choose the master data type for
your planning area, for example, SI1PRODUCT.
Categorical Attributes: PRODGROUP, PRODTYPE
Numeric Attributes: Blank
Grouping-Numeric Attributes: Blank
Planning Filter: Blank
Min Support: 0.05
Min Confidence: 0.90
Min Lift: 0.00
Max Items in Antecedent: 4
Current Period Calculation: Execution Time

ished.
7. Choose Log Choose Log in the Finished job.
8. Check master data consistency results You can view the master data consistency results for the:
 number of records analyzed
 number of rules
 number of recommendations
You can open the.csv file in the Categorical Attributes Learn
Rules attachment. The.csv file attachment shows the rules
learned including a ranked list of learned association rules, for
example, the products with PRODGROUP L004 and PROD-
TYPE FERT.
Note: The rules may include the root attribute PRDID if the
number of products is very small considering the min
support or other settings in the job parameters. For example,
in the parameter setting in step 4, the min support is 0.05, If
the number of products is less than or equal to 20, you may
see PRDID included in the rules learned.
You can open the.csv file in the Categorical Attributes

Outliers/Suggested Values attachment The .csv file shows out-
liers and recommendations including a ranked list of outliers
and suggested values if any.
Note: If the number of recommendations is 0, this means

that there are no outliers for the categorical attributes with
the rules learned. The attachment shows a blank record.
For more details on the parameter settings of the ML Master
Data Consistency job or its results, see Using an Application
Job to Discover Patterns- SAP Help Portal

4.3 Master Data Change Transfer
4.3.1 Create Variant for Background Integration Model Activation
Test Administration
Purpose
You must create a variant to periodically reactivate your newest integration model version.
Procedure
1. Start to Define Variant In the SAP S/4HANA system, access the transaction using The Define Background Job screen is displayed.
transaction code SE38 or open the following menu path:
Tools ® ABAP Workbench ® Development ® ABAP Editor
2. Enter Program Name On the ABAP Editor: Initial Screen screen, enter the Program
Name and choose Execute.
Program Name: RIMODAC2
3. Enter Selection Criteria On the Activate or Deactivate Integration Model (Possible In

Background) screen, enter the following data:
Example:
Model: IBP_SUP_MD


Activate Newest Version: Selected
Example:
Variant Name: IBP_SUP_MD_ACT
Description: Variant IBP_SUP_MD Model Act
6. Save Variant On the Variant Attributes screen, choose Save. The variant is saved and can be used in the background job which
is described in the next chapter.
7. Create Variant Repeat steps 2 – 6 to create another variant for activating the
subcontracting master data integration model periodically with
the following data:
Example:
Model: IBP_SUBCON
Activate Newest Version: Selected
Variant Name: IBP_SUBCON_ACT

Description: Variant IBP_SUBCON Model Act

4.3.2 Create Variant for Production Data Structures Change Transfer
Test Administration
Purpose
You create a variant to periodically transfer Production Data Structures changes.
Procedure
1. Start to Define Variant In the SAP S/4HANA system, access the transaction using The Transfer of Production Data Structures to SAP APO screen is
transaction code CURTO_CREATE_IBP or open the following displayed.
menu path:
Model → Change Transfer → Production Data Structure (PDS)
→ Transfer Production Data Structure (PDS)
2. Specify Selection In the Transfer of Production Data Structures to SAP APO

screen, make the following entries:
Example:
Logical System: Your IBP Logical System, for example,
ZXYCLNT001
Plant: for example, 1010,1310
Production Version: 0001
MRP Type: X0
PDS Usage: S

Including Subcontracting: Selected

Change Transfer: Not Selected
3. Choose Save to Switch to Create Vari- In the Transfer of Production Data Structures to SAP APO
ant Screen screen, choose Save.
4. Create Variant On the Variant Attributes screen, enter the following data: The variant for PDS transfer job is created.
Example:
Variant Name: IBP_PDS_Change
Description: Variant IBP_PDS_Change
4.3.3 Create Variant for Deactivated Integration Models Deletion
Test Administration
Purpose
The system doesn’t deactivate integration models automatically. We recommend that you delete them regularly for performance reasons.
In this chapter, you create a variant to periodically delete deactivated integration models for master data. You can take a similar approach for integration models for transactional data.

Procedure
1. Start to Define Variant In the SAP S/4HANA system, access the transaction using The Define Background Job screen is displayed.
transaction code SE38 or open the following menu path:
Tools ® ABAP Workbench ® Development ® ABAP Editor
2. Enter Program Name On the ABAP Editor: Initial Screen screen, enter the Program
Name and choose Execute.
Program Name: RIMODDEL
3. Enter Selection Criteria On the Delete Integration Models screen, enter the following
data:
Example:
Model: IBP_SUP_MD
Select Inactive IMs Only: Selected
Caution: This setting ensures that you only delete inactive

integration models.
Example:
Variant Name: IBP_SUP_MD_DEL
Description: Variant IBP_SUP_MD Model Del
6. Save Variant On the Variant Attributes screen, choose Save. The variant is saved and can be used in the background job which
is described in the next chapter.

7. Create Variant Repeat steps 1 – 6 to create another variant for deactivating the
subcontracting master data integration model with the following
data:
On the Delete Integration Models screen, enter the following
data:
Example:
Model: IBP_SUBCON
Logical System: ZXYCLNT001
Select Inactive IMs Only: Selected
Variant Name: IBP_SUBCON_DEL

Description: Variant IBP_SUBCON Model Del
4.3.4 Create and Schedule Background Job for Master Data Changes
Test Administration
Purpose
In this procedure, you create and activate a new version of the integration model for the master data that has been created in SAP S/4HANA. Although you can do this manually, for performance
reasons, we recommend that you set up a periodic background job which runs during off-peak hours, for example, at night. In the background job, the reports referred to below should run in
sequence. This procedure offers the following advantages:
 Master data that has been created recently and meets the selection criteria of integration models that already exist is included in these integration models and transferred to the target system.
 Master data that has been changed to such an extent that it no longer meets the selection criteria of the corresponding integration model is excluded from the transfer.
 Master data (material, customer, vendor, and source of supply) that has been changed since the last transfer is retransferred and will now be up to date.
Additional steps in the background job are:
 PDS change transfer
 Deletion of deactivated integration models
Note: The integration model for plants is not included in this periodic job because we assume that the layout (in particular, the plants and distribution centers) of the supply chain network does
not change as often as other master data.
If a new plant is added to the supply chain network in S/4HANA, you must adapt and manually reactivate the integration model for plants.
If master data of an existing plant has been changed in S/4HANA, you must manually reactivate the integration model for plants.
Procedure
1. Start to Define Background Job In the SAP S/4HANA system, access the transaction using The Define Background Job screen is displayed.
transaction code SM36 or open the following menu path:
Tools ® CCMS ® Background Processing ® Define Job
2. Enter Job Name On the Define Background Job screen, enter the Job Name.
Example:
Job Name: IBP_SUP_MD
Job class: for example, B (Middle priority)
3. Define Steps On the Define Background Job screen, choose Define steps.
4. Define Step 1 In the Create Step 1 dialog box, in the ABAP program section, Step 1 is defined.
enter the following data:
Name: RIMODGEN
Variant: IBP_SUP_MD_GEN
Choose Save.
5. Add Step 2 You are now on the Step List Overview screen. Choose Create
to add an additional step.
Name: RIMODAC2
Variant: IBP_SUP_MD_ACT

Choose Save.
Name: RIMODGEN
Variant: IBP_SUBCON_GEN
Choose Save.
Name: CUSLNTRTO_CIF_REPORT
Variant: IBP_PDS_Change
Choose Save.
Name: RIMODAC2
Variant: IBP_SUBCON_ACT
Choose Save.
Name: RIMODDEL
Variant: IBP_SUP_MD_DEL
Choose Save.

Name: RIMODDEL
Variant: IBP_SUBCON_DEL
Choose Save and Back.
17. Schedule Job On the Define Background Job screen, choose Start condition.
18. Schedule Job In the Start Time dialog box, choose Date/Time. In the Date/
Time section, maintain Scheduled Start Date and Scheduled
Start Time according to your business requirements.
Example:
Scheduled Start Date: for example, tomorrow
Scheduled Start Time: for example, 1:00AM Periodic Job:
<selected>
19. Schedule Job In the Start Time dialog box, choose Period Values.
In the Period Values dialog box, choose Daily.
Choose Save.
20. Schedule Job In the Start Time dialog box, choose Save.
21. Save Job On the Define Background Job screen, choose Save. The job is saved with status Released.
In the above example the job is scheduled to run every day at
1:00AM, starting tomorrow.
4.4 Transactional Data
4.4.1 Create Integration Model for Transactional Data
Test Administration

Purpose
When you generate an integration model for transactional data, you specify which transactional data objects are to be selected from the total dataset in the SAP S/4HANA system. Only this dataset
will be transferred to SAP IBP.
Procedure
Logistics → Central Functions → Supply Chain Planning In-
terface → Real-Time Integration with SAP IBP → Integration
Model → Create
2. Enter Header Data of Integration Enter the following data:

Model
Example:
Model Name:IBP_SUP_TD
3. Enter General Selection Options for In the General Selection Options for Materials section, enter Material and plant master data to be transferred to SAP IBP is
Materials the following data: specified.

Material: Select the material master to be transferred to relevant material-plant combinations in SAP S/4HANA are
SAP IBP transferred to SAP IBP as product-location combinations.
FG126, SG124, SG25, RM20, SG23, RM13, Before activating the integration model, you can check the
RM14 objects to be transferred.
Plnt: Select the plants for which the material is to be

transferred

1010, 1310, 3710, 6210,
Define MRP Type X0.
X0 – Without MRP, with BOM Explosion
4. Select Storage Loc.Stk In the Material Dependent Objects section, select the Storage
Loc.Stk indicator.
5. Select Transit Stock In the Material Dependent Objects section, select the Transit
Stock indicator.
6. Select Vend. Spec. Stk In the Material Dependent Objects section, select the Vend.
Spec. Stk indicator.
7. Select Sales Orders In the Material Dependent Objects section, select the Sales Or-
ders indicator.
8. Select Planned Orders In the Material Dependent Objects section, select the Planned
Orders indicator.
9. Select PO and Preqs In the Material Dependent Objects section, select the POs and
PReqs indicator.
10. Select Req. Reduction In the Material Dependent Objects section, select the Req. Re-
duction indicator.
11. Select Prod. Order In the Material Dependent Objects section, select the Prod. Or-
der indicator.
12. Select Manual Reserv. In the Material Dependent Objects section, select the Manual
Reserv. Indicator.
variant on the selection screen. Variants allow you to reuse the set-
tings you have saved whenever you want. If you want to recreate
an integration model at a later time, you can call up the required
variant by choosing the Select Variant icon in the toolbar at the top
of the selection screen.

Example:
Variant Name: IBP_SUP_TD_JOB
Description: Variant for IBP_SUP_TD

4.4.2 Activate Integration Model for Transactional Data
Test Administration
Purpose
Activating the transactional data integration model triggers an initial data transfer of transactional data from SAP S/4HANA to SAP IBP.

Procedure
1. Create Integration Model In the SAP S/4HANA system, access the transaction using The Activate or Deactivate Integration Model screen is displayed.
Model → Activate
2. Enter Selection Criteria On the Activate or Deactivate Integration Model screen, enter
the following data:
Example:
Model: IBP_SUP_TD
example ZXYCLNT100
Execute.
5. Select RTI Node of Integration Model Double-click the RTI node of your integration model. A table is displayed on the right side of the screen showing the in-
tegration model versions.
6. Select Line in the Table Select the latest record in the table.

4.4.3 View Projected Stock
Test Administration
Purpose
You can use the Projected Stock app in SAP IBP to see the receipt and requirement elements for a particular product or location integrated from SAP S/4HANA.
Note: You can also use the View Confirmations app if you’re mainly interested in the integration of sales orders and outbound deliveries.
Note: If you can’t find the data outlined in the next steps in your SAP IBP system, you can use the Monitor bgRFC Queues app to monitor the integration queues.
Procedure
Planning web user interface face. plications (apps) for SAP Integrated Business Planning is dis-
2. Open Projected Stock app Open the Projected Stock app by choosing the corresponding The Projected Stock screen is displayed.
tile on the launchpad.
3. Specify Selection Criteria and Display On the Projected Stock screen, in the upper filter section, enter On the lower part of screen, you can see a list of results.
Projected Stock Results the following data:
Example:
Versions/Scenario: RM1SAP7F / Base Version
Product: FG126

Date Horizon for Status: Two Months

Type of First Deviation: All
Choose Go.
4. Check Detail for one Location Product Choose a single row.
Example:
Product: FG126
Location Number: 6210
Based on the data that you’ve created in SAP S/4HANA, the

lower part of the screen displays, for example, the sales order,
the outbound delivery, and the stock.
5. Check Detail for another Location Choose a single row.

Product
Example:
Product: FG126
Based on the data that you’ve created in SAP S/4HANA, the

lower part of the screen displays, for example, the planned order
and the production order.
6. Choose Home On the Projected Stock screen, choose Home. The SAP Fiori launchpad is displayed.
4.4.4 Check Integration Results in SAP Integrated Business Planning, Add-in for Microsoft Excel
Test Administration

Purpose
You can use the SAP Integrated Business Planning, add-in for Microsoft Excel to check, for instance, the data in the Production Capacity sheet.
Using the RM010 Forecast and Constraints planning view template, you can quickly check the integration results in the Excel add-in. You can also manually add other key figures to the planning
view, for example Sales Order (Request).
Procedure
1. Log on to SAP Integrated Business Log on to the SAP Integrated Business Planning, add-in for The SAP IBP tab appears in Microsoft Excel with the active rib-
Planning, add-in for Microsoft Excel Microsoft Excel. Use the Response and Supply planning area, bon.
for example, RM1SAP7F.
2. On the SAP IBP tab, choose Favorites On the SAP IBP tab, choose the Favorites dropdown list. The RM010 Forecast and Constraints planning view appears in
the dropdown list.
3. Select RM010 Forecast and Constraints From the Favorites dropdown list, select RM010 Forecast and The favorite RM010 Forecast and Constraints planning view is
Constraints. loaded.
4. Navigate to Capacity sheet Navigate to the Production Capacity sheet. The Production Capacity sheet is displayed.
5. Check Capacity Available Check if the value of key figure Capacity Available is
displayed correctly.
Example:
Resource: WASSEMBLY_1010_001

4.5 Set Up Outbound Integration in Real-Time Integration Profile
Test Administration
Purpose
After the initial inbound integration to SAP IBP, you must set up the Outbound Integration in the Real-Time Integration Profile before you run the outbound integration or reconciliation application
job.
Note: This is a one-time activity. Once you have mapped the Location Numbers to Order Types, you only have to repeat this activity if new locations are added to your integration.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail / Comment
Step #
1. Log on to SAP Integrated Log on to the SAP Integrated Business Planning web user interface. The SAP Fiori launchpad as the access
Business Planning point to all web-based applications for
SAP Integrated Business Planning is dis-
2. Open Real-Time Integration Open the Real-Time Integration Profiles app by clicking the corresponding tile on the
Profiles App launchpad.
3. Select Real-Time Integration On the Real-Time Integration Profiles screen, select the real-time integration profile you
Profile created when implementing the Setup instructions for implementing order-based
planning.
Example:
BP_RTI_INT_PROFILE

Step #
4. Choose Create Inactive In- On the Real-Time Integration Profiles screen, choose Create Inactive Instance. An inactive instance of your profile is
stance created.
5. Open the Inactive Real-Time On the Real-Time Integration Profiles screen, choose the inactive profile. The Integration Profile screen is dis-
Integration Profile played.
6. Choose Edit On the Integration Profile screen, choose Edit.
7. Choose Outbound In the Outbound Transfer Modes section, enter the following data:
Purchase Requisition: Periodic
Stock Transfer Requisition: Periodic
Planned Order: Periodic
Sales Order Confirmation: Periodic
Queue Prefix: CG0
8. Choose Outbound – Outbound On the Integration Profile screen, choose Outbound – Outbound Systems.
Systems
9. Choose Target Logical System In the Outbound Systems table, choose your Target Logical System. The Outbound System screen is dis-
played.
Example:
S4HCLNT001
10. Choose Create Select your Target Logical System. A new entry is added to the Distribution
In the Outbound System screen, choose Create. Definitions table.
11. Map Location Number to Or- In the Distribution Definition table, enter the following data:
der Type
Example:
Order Type: Planned Order (PLA)
Note: You can only maintain definitions for locations that have already been
integrated.
12. Choose Apply In the Outbound Systems screen, choose Apply. The Integration Profile screen is dis-
played.

Step #
13. Create Further Mappings Repeat steps 10 to 12 with the following data:
Example:
1310 – Planned Order (PLA)
1010 – Purchase Requisition (PUR)
1010 – Stock Transfer Requisition (STR)
14. Choose Save On the Integration Profile screen, choose Save.
15. Choose Back On the Integration Profile screen, choose Back. The Real-Time Integration Profiles
screen is displayed.
16. Select Inactive Real-Time In- On the Real-Time Integration Profiles screen, select the inactive real-time integration
tegration Profile profile.
17. Choose Activate On the Real-Time Integration Profiles screen, choose Activate The Real-Time Integration Profile is up-
dated with the Distribution Definition.
4.6 Transactional Data Reconciliation
4.6.1 Run Reconciliation Job (Optional)
Test Administration

Purpose
You can run the Real-Time Integration (Reconciliation) application job to identify any data inconsistencies between your S/4HANA system and your SAP IBP system. Data inconsistencies can
occur during data transfer using the Core Interface (CIF), for example, if you manually deleted entries in the queue or if there are queue entries with errors. The Real-Time Integration
(Reconciliation) application job finds objects that are not available in one of the systems as well as objects that are not the same in the two systems.
Note: Before you run the application job, make sure to check the Monitor bgRFC Queues app in SAP IBP and the bgRFC Monitor in your S/4HANA system for queue entries with errors and
correct these errors.
Also make sure to process all change points. In the properties of the Real-Time Integration (Reconciliation) application job, you can also specify to search only for inconsistencies without change
points.
Note: Check SAP Notes 3115087 and 3094837 first and implement them if needed.
Procedure
tile on the launchpad.
4. Enter Parameters The New Job screen is designed as a guided procedure that
comprises several main sections. You can sequentially navigate
Example:

Template Selection
Job Template: Real-Time Integration:
Reconciliation
Job Name: Real-Time Integration:
Reconciliation
Scheduling Options
Parameters
Logical System: Select the S/4HANA system that you
want to compare, for example, S4HCLNT001
Comparison Result Name: For example,
REC_RESULT
Integration Model: Select the integration model that
you want to compare.
Object Selection: By Location Product
Attributes
Product ID: Select the product that you want to
compare.
Location Number: Select the location number that you
want to compare.
Note: If you restrict the selection to specific products,

locations, or integration models, you can improve the
performance of the comparison. Otherwise, the system
compares all objects.
You can also use the By Planning Filter object selection for
further attribute selection.
Planned Orders: X (selected)

Production / Process Orders: X (selected)
Purchase Requisitions: X (selected)
Purchase Orders: X (selected)
Purchase Orders Confirmations: X (selected)
Sales Orders: X (selected)
Storage Location Stock: X (selected)
Transit Stock: X (selected)
Vendor Special Stock: X (selected)

5. Schedule Job Choose Schedule. The job is started.
6. Check Job Status Choose Go to refresh the job status until the status is set to Fin- The job is finished without errors.
ished.
4.6.2 Solve Data Inconsistencies (Optional)
Test Administration
Purpose
After you have run the Real-Time Integration (Reconciliation) application job, you can display the comparison result and correct the data inconsistencies using the Data Comparison and
Reconciliation for RTI app.
Procedure
2. Open Data Comparison and Reconcilia- Open the Data Comparison and Reconciliation for RTI app by
tion for RTI App clicking the corresponding tile on the launchpad.
3. Check Result in General On the Data Comparison and Reconciliation for RTI screen, The comparison result is shown.

find your comparison result in the list and check the Status col-
umn.
If Inconsistent Data Found is shown in the Status column, click
on your comparison result and check the details.
4. Check Result in Detail On the Comparison Result screen, you can see the summary of The order comparison details screen is shown.
data inconsistencies for each order type and stock type.
By choosing a specific object type showing inconsistencies, for
example, the purchase order, you can display the details.
5. Correct Inconsistencies Depending on the object type and error category, resolve the in- Reconciliation is executed.
consistencies by using the reconciliation buttons, for example,
Send to SAP IBP, or Send to External System, and so on.
Note: For more information about which object types can

be compared and the type of inconsistencies that are
identified for the individual object types, see Comparison of
Individual Object Types
6. Check Reconciliation Result After reconciliation, go back to the Comparison Result screen, The data inconsistencies are corrected after reconciliation.
choose Iteration to check whether the correction was successful
or not. This way, you can determine whether an error still exists
after the reconciliation or not.
After reconciliation is executed for all errors, the Data Compari-
son and Reconciliation for RTI screen shows Consistent Data
After Iteration is in the Status column.

5 Appendix
5.1 Process Integration

The process to be tested in this test script is part of a chain of integrated processes.
5.1.1 Preceding Processes

You may first have completed the following processes and conditions before you start with the test steps:
Sell from Stock (BD9) The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
You can run through the Sell from Stock (BD9) SAP S/4HANA test procedures to create sales orders and deliveries. Then you can check the integration of the sales
documents into the SAP IBP system.
Make-to-Stock Production – Discrete Manufacturing The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
(BJ5) You can run through the Make-to-Stock Production – Discrete Manufacturing (BJ5) SAP S/4HANA test procedures to convert planned orders to production orders,
confirm operations of the production orders and post goods receipts. You can then check the integration of the production orders and stock into the SAP IBP system.
Procurement of Direct Materials (J45) The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
You can run through the Procurement of Direct Materials (J45) SAP S/4HANA test procedures to create purchase requisitions and orders, change purchase orders
and post goods receipts. You can then check the integration of the purchase orders and stock into the SAP IBP system.
Intercompany Stock Transfer The Preliminary Steps chapter of this test script describes how to create the orders and stock elements that must be present in the SAP S/4HANA system.
Stock Transfer with Delivery You can create stock transfer requisitions and orders, change stock transfer orders and post goods receipts. You can then check the integration of the stock transfer
orders and stock into the SAP IBP system.
Stock Transfer without Delivery
(no SAP Best Practices solution processs available
for SAP S/4HANA)
5.1.2 Succeeding Processes

After completing the activities in this test script, you can continue testing the following business processes:
IBP for response and supply – supply and allocations Planning-relevant master data and transactional data integrated from SAP S/4HANA is used as input to the IBP for response and supply – supply and allocations

planning – heuristic (2I0) planning – heuristic (2I0) process.
IBP for response and supply – supply planning – Planning-relevant master data and transactional data integrated from SAP S/4HANA is used as input to the IBP for response and supply – supply planning – OBP op-
OBP optimizer (42C) timizer (42C) process.
IBP for response and supply – response planning Planning-relevant master data and transactional data integrated from SAP S/4HANA is used as input to the IBP for response and supply – response planning (2P0)
(2P0) process.

Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths,
and menu options.
www.sap.com/contactsap
Textual cross-references to other documents.
© 2024 SAP SE or an SAP affiliate company. All rights reserved.
Example Emphasized words or expressions. 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
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a notice.
programming language when they’re surrounded by body text, for example, SELECT and INCLUDE. Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, These materials are provided by SAP SE or an SAP affiliate company for
and names of installation, upgrade and database tools. 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
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. 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.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the SAP and other SAP products and services mentioned herein as well as their
system. 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
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . companies.
See www.sap.com/copyright for additional trademark information and

notices.


OBP Best Practice

Uploaded by

Copyright:

Available Formats

You might also like

OBP Best Practice

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OBP Best Practice

Uploaded by

Copyright:

Available Formats

Test Script

SAP IBP for Supply Chain 2402

IBP - order-based planning inbound integration with SAP

IBP - order-based planning inbound integration with SAP S/4HANA(2S4)

Revision Change Date Description

0 February 5, 2018 Document creation for IBP 1802

1 May 8, 2018 Updated version for IBP 1805

2 August 7, 2018 Updated version for IBP 1808

3 November 6, 2018 Updated version for IBP 1811

4 February 5, 2019 Updated version for IBP 1902

5 May 6, 2019 Updated version for IBP 1905

6 August 5, 2019 Updated version for IBP 1908

7 November 5, 2019 Updated version for IBP 1911

8 January 29, 2020 Updated version for IBP 2002

9 April 29, 2020 Updated version for IBP 2005

10 July 29, 2020 Updated version for IBP 2008

11 October 29, 2020 Updated version for IBP 2011

12 February 3, 2021 Updated version for IBP 2102

13 May 5, 2021 Updated version for IBP 2105

14 August 4, 2021 Updated version for IBP 2108

15 October 27, 2021 Updated version for IBP 2111

16 February 2, 2022 Updated version for IBP 2202

17 May 4, 2022 Updated version for IBP 2205

18 August 3, 2022 Updated version for IBP 2208

19 October 26, 2022 Updated version for IBP 2211

20 February 3, 2023 Updated version for IBP 2302

21 May 5, 2023 Updated version for IBP 2305

22 August 4, 2023 Updated version for IBP 2308

23 October 27, 2023 Updated version for IBP 2311

24 February 2, 2024 Updated version for IBP 2402

ERROR: REFERENCE SOURCE NOT FOUND

ERROR: REFERENCE SOURCE NOT FOUND

2.1 System Access

SAP S/4HANA Accessible via SAP GUI.

SAP S/4HANA <SID>

SAP Integrated Business Planning web user in- https://myXXXXXX.scmibp.ondemand.com

SAP Integrated Business Planning, add-in for Connection Name: myXXXXXX

Business Role Business Role Description Log On

Administrator (IBP) Administrator (IBP)

Supply Planner (IBP) Supply Planner (IBP)

ERROR: REFERENCE SOURCE NOT FOUND

Data Sample Value Details Comments

Material FG126 Serial Number Managed Finished Good MTS

Material SG25 Semifinished Good External Procurement

Material SG124 Semifinished Good Subassembly

Material RM20 Raw Material Ext. Procurement Contract

Material SG23 SEMI23, PD, Subcontracting

Material RM13 RAW13, PD, Subcontracting

Material RM14 RAW14, PD, Subcontracting

Plant 6210 Plant 1 HK

Plant 1310 Plant 1 CN

Plant 1010 Plant 1 DE

Plant 3710 Plant 1 NL

Supplier 13300001 Domestic Supplier 1 CN

Supplier 10300001 Domestic Supplier 1 DE

ERROR: REFERENCE SOURCE NOT FOUND

Subcontractor 13300007 国内外包商

Subcontractor 10300007 Inland-Lohnbearbeiter A, DE