Rds Ibp Ibp2208 28 Quick Guide en XX
Rds Ibp Ibp2208 28 Quick Guide en XX
Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons
labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
1.0 2022 05 04
1 Solution Overview 6
2 System Setup 7
2.1 Software Product Versions 7
2.2 SAP Notes 8
2.3 Software Landscape Diagram 9
2.4 Install SAP Integrated Business Planning, Add-in for Microsoft Excel 11
2.5 Install Microsoft Excel VBA Add-In for Planning View Templates 12
2.6 Download Sample Data and Sample Planning Views 13
2.7 Set Up Integration with SAP Work Zone 13
2.7.1 Prerequisites 13
2.7.2 Create Communication System 14
2.7.3 Create Communication Arrangement 15
2.8 Set Up Real-Time Integration for Order-Based Planning 16
2.8.1 Prerequisites 17
2.8.1.1 Check SAP Notes 17
2.8.1.2 SAP Business Technology Platform and Cloud Connector 17
2.8.2 Set Up Connection Between SAP BTP and Cloud Connector 18
2.8.2.1 Create Service Instance in SAP BTP Cockpit 18
2.8.2.2 Connect SAP IBP with SAP BTP 20
2.8.2.3 Connect SAP BTP with Cloud Connector 21
2.8.3 Configure Cloud Connector 22
2.8.3.1 Configure Cloud To On-Premise Communication Channel 22
2.8.3.2 Configure Accessible Resources for Cloud To On-Premise Communication Channel 27
2.8.3.3 Configure On-Premise To Cloud Communication Channel 30
2.8.4 Configuration in SAP IBP 31
2.8.4.1 Inbound Integration – Create Communication User 32
2.8.4.2 Inbound Integration – Create Communication System 32
2.8.4.3 Inbound Integration – Create Communication Arrangements 33
2.8.4.4 Outbound Integration – Create Communication Users 35
2.8.4.5 Outbound Integration – Create Communication Systems 36
2.8.4.6 Outbound Integration – Create Communication Arrangements 42
2.8.5 Configuration in SAP S/4HANA 44
2.8.5.1 Define Logical Systems 44
2.8.5.2 Assign Logical System to Client 45
2.8.5.3 Specify System Release 46
2.8.5.4 Configure RFC Connections 47
2.8.5.5 Assign Number Range 49
2.8.5.6 Set Target System and Queue Type 49
2.8.5.7 Activate bgRFC Connection 50
2.8.5.8 Create bgRFC Supervisor Destination 51
2.8.5.9 Configure bgRFC (Inbound to SAP S/4HANA) 52
2.8.5.10 Configure Queue Name Prefix for SAP IBP (Inbound to SAP IBP) 53
2.8.5.11 Activate Business Transaction Events 54
2.8.5.12 Activate Change Pointers Generally 55
2.8.5.13 Activate ALE Change Transfer 55
2.8.5.14 Configure Change Transfer for Master Data 56
2.9 Set Up Integration for Time-Series Based Planning 57
4 Security Aspects 73
4.1 General Security Guidelines 73
4.2 User Administration and Authentication 73
Leverage SAP Best Practices for SAP Integrated Business Planning for Supply Chain (SAP IBP) to get an entry scope of the
following planning processes:
Sales and operations planning
Response and supply planning
Demand planning
Demand sensing
Inventory optimization
Demand-driven replenishment
SAP Best Practices for SAP Integrated Business Planning for Supply Chain V28.2208:
Are based on SAP Integrated Business Planning for Supply Chain 2208, SAP Work Zone, and SAP S/4HANA.
Support faster deployment of the required configuration settings
For an overview of this SAP Best Practices package, refer to the information provided in the SAP Best Practices Explorer:
https://rapid.sap.com/bp/RDS_IBP.
The package contains different deployment assets that are shipped either together with the SAP Integrated Business Planning for
Supply Chain product or through the SAP Best Practices Explorer.
These are the most important assets we deliver through the SAP Best Practices Explorer:
Sample planning views
Sample master data
Sample time profile
Sample key figure data
Configuration guides
Test scripts
Process diagrams
To use SAP Best Practices for SAP Integrated Business Planning, you need the respective application licenses. For details on
application licenses and the corresponding features, refer to the application help: Applications and Features of SAP Integrated
Business Planning for Supply Chain
The SAP Integrated Business Planning for Supply Chain system is provisioned by the SAP Cloud Service Center. The customer
receives an email containing the URL and an administration user for their system.
SAP Work Zone n.a. Cloud delivery Optional, required only if process 2BQ, 3RT, 2BS,
management functionality is to be 18N, 2BU, 2BW
used.
SAP Integrated Business 2208 n.a. Download from Software Download All scope items
Planning, add-in for Center. See chapter Installing the SAP
Microsoft Excel Integrated Business Planning, Add-in
for Microsoft Excel.
SAP S/4HANA, supply 1.0 Latest support Only required for the IBP for time- 3OF, 4NO
chain integration add-on package series based inbound and outbound
for SAP Integrated integration with SAP S/4HANA scope
Business Planning items.
SAP Cloud Integration for 1.0 Latest support Only required for the IBP for time- 3OF, 4NO
data services package series based inbound and outbound
integration with SAP S/4HANA scope
items.
SAP Enterprise Product n.a. Cloud delivery Only required for the IBP for sales 5LG
Development and operations – receipts analysis
scope items.
SAP Business Technology Latest n.a Only required for the scope items 2I0, 42C, 2P0,
Platform including SAP release related to order-based planning. 4UT, 2P2, 2S4,
Connectivity service and 2S6, 4VA, 5JD
Cloud Connector
Web Browser See SAP Note 1935915 on browser All scope items
recommendations.
Microsoft Excel See SAP Note 2135948 for an All scope items
overview of supported configurations.
To be announced SAP IBP OD 2208 – SCM-IBP-DM This note also links to the
Central Note product restrictions of SAP IBP.
To be announced SAP IBP OD 2208 – SCM-IBP-BF-PPF This note also links to the
Release Information Note Product Availability Matrix.
To be announced SAP IBP 2208 – Release SCM-IBP-DM Product restrictions for using
Restriction Note SAP IBP.
1790530 S&OP / IBP Planning View SCM-IBP-XLS-UI All restrictions mentioned in this
Templates for the Excel note also apply to the planning
Add-In view templates delivered with
this solution. Make sure to
install the Excel add-in for VBA
templates mentioned in this note.
2806360 SAP IBP, add-in for SCM-IBP-XLS-UI Follow the steps to ensure that
Microsoft Excel: your VBA add-in is properly
“SAP_IBP_Chart.xlam installed.
missing or not activated”
error message
2515578 IBP: DISAGG or COPY SCM-IBP-BF-DIS This note describes what you
operator not working need to do if target key figures
don’t show any values.
2776077 Order-based planning using SCM-IBP-RM This note describes the setup and
the time-series-based configuration steps needed to
forecast consumption support an SAP IBP order-based
operator planning run (confirmation run)
using an open forecast calculated
by TS-based forecast
consumption.
3106619 SAP IBP Real-time SCM-IBP-INT-RTI To use the SAP IBP real-time
integration - Notes for integration, you either need to
Use
The planning processes in SAP IBP are executed in Microsoft Excel spreadsheets. All users need to install the SAP Integrated
Business Planning, add-in for Microsoft Excel locally on their computer. You can download the installer from the Software
Download Center.
Procedure
Caution
Make sure to install the Excel add-in with English language settings only. Otherwise, the sample planning views might
not be displayed correctly.
Note
For more information on how to create a connection to the SAP IBP system and troubleshoot issues with the Excel add-
in, refer to the application help: Planning with Microsoft Excel.
2.5 Install Microsoft Excel VBA Add-In for Planning View Templates
Use
The planning view templates delivered with SAP Note 1790530 include a VBA-embedded template and a VBA add-in template
that help users to easily create planning views from scratch. In SAP Best Practices for SAP IBP, the planning view templates are
based on the templates with the VBA add-in. To use these planning view templates, users need to install the VBA add-in locally
on their computer.
You can find the installer in the link provided in SAP Note 1790530. There, you’ll also find detailed information on how to
install the VBA add-in.
Caution
The planning view templates provide examples based on the configuration and data of SAP Best Practices for SAP IBP
and are designed to help you get started. They cannot be used directly in productive mode. Please check and adapt the
templates to meet your requirements. They might also be subject to changes without any maintenance obligation.
All restrictions listed in SAP Note 1790530 also apply to the sample planning view templates delivered with SAP Best
Practices for SAP IBP.
Procedure
1. Extract SAP_IBP_Chart.xlam from the download link referenced in SAP Note 1790530.
2. Place this xlam file in folder %appdata%\Microsoft\Addins.
3. Open Microsoft Excel and go to File → Options → Add-Ins.
4. Choose Manage: Excel Add-ins → Go.
5. Select the checkbox for Sap_Ibp_Chart.
6. Choose OK.
Note
Please also check SAP Note 2806360 for further information on the VBA add-in installation.
Use
Sample planning views and sample data for SAP Best Practices for SAP IBP are delivered through the SAP Best Practices
Explorer. Before you start deploying your solution, download the corresponding ZIP files to your computer.
Caution
Make sure to download the ZIP files related to SAP IBP version 2208 that you’re deploying the solution for. The
sample planning view templates delivered with this solution only work with the SAP IBP, add-in for Microsoft Excel
(Excel add-in) 2208.
Procedure
7. Navigate to https://rapid.sap.com/bp/rds_ibp.
8. Choose the Accelerators tab.
9. In the Implementation section, choose Technical Assets for SAP7F (sample data, master data, planning view templates) to
download the assets required to set up the Best Practices scope items for the order-based planning scenarios.
10. In the Implementation section, choose Technical Assets for SAP8 (sample data, master data, planning view templates) to
download the assets required to set up the Best Practices scope items for the demand-driven replenishment scenarios.
11. In the Implementation section, choose Technical Assets for SAPIBP1 (sample data, master data, planning view templates) to
download the assets required to set up the Best Practices scope items for the time-series-based planning scenarios.
2.7.1 Prerequisites
Separate licenses of SAP Work Zone are required to enable the collaboration capabilities in SAP IBP. If you do not own SAP
Work Zone licenses or do not intend to use the collaboration capabilities in SAP IBP, you can skip this section.
Use
To enable the integration with SAP Work Zone, you need to define a new communication system and a new communication
arrangement based on communication scenario SAP_COM_0026. For more information on the integration with SAP Work Zone,
refer to the application help: SAP Work Zone Integration Guide.
Procedure
Example
Z_IBP_WORKZONE
Example
Z_IBP_WORKZONE
5. Choose Create.
6. On the Communication System screen, enter the following data:
Example
xxx.coreint1.workzone.ondemand.com
7. On the Communication System screen, in the User for Outbound Communication section, choose the plus sign (+).
8. In the New Outbound User dialog, enter the following data:
Example
https://myXXXXXX.accounts.ondemand.com
Procedure
Example
ZSAP_COM_0026_WORKZONE
Example
ZSAP_COM_0026_WORKZONE
Example
https://myXXXXXX.accounts.ondemand.com
Path /
Port 443
7. Choose Save.
Note
This chapter is only required for the following order-based planning scope items:
IBP for response and supply – supply and allocations planning – heuristic (2I0)
IBP for response and supply – supply and allocations planning - optimizer (42C)
IBP for response and supply – response planning (2P0)
IBP for response and supply – deployment planning – optimizer (4UT)
IBP – order-based planning inbound integration with SAP S/4HANA (2S4)
IBP – order-based planning outbound integration with SAP S/4HANA (2S6)
IBP – order-based planning inbound integration for deployment planning (4VA)
IBP – order-based planning outbound integration for deployment planning (5JD)
2.8.1 Prerequisites
Please note down the following information. You will need it throughout the next chapters:
Example
https://scc-ibp.xxx.yyy.corp:8443/
In the following chapters, we will focus on the configuration steps specific to SAP IBP. For the generic topics of SAP BTP
Connectivity and Cloud Connector, refer to the help documents mentioned above or to the main help pages: SAP BTP
Connectivity, Cloud Connector.
Use
To use the SAP BTP Connectivity service, you need an instance of the service. Follow the steps below to create a service
instance. For more information, see Creating Service Instances in Cloud Foundry and Creating Service Keys in Cloud Foundry.
Procedure
Example
https://cockpit.eu10.hana.ondemand.com/
2. In the navigation pane on the left, choose Account Explorer.
3. Choose the Subaccounts tab.
4. Select the subaccount. Refer to chapter Prerequisites to find out which one this is.
Example
Connectivity-BestPractices-IBP
Provider: Amazon Web Services (AWS)
Region: US-East (VA)
Environment: Multi-Environment
5. In the navigation pane on the left, choose Services à Instances and Subscriptions.
6. Choose Create to create a new service instance. A wizard for configuring your new instance is displayed.
7. In the New Instance or Subscription dialog box, enter the following data:
Plan connectivity_proxy
Example
BestPractices-ZXY
Example
IBP-ZXY
Note
This JSON text containing the service key will be used in the next chapter to automatically generate a communication
scenario.
Caution
JSON content shall be shared via plain text format only to avoid removal of any control characters.
Use
To connect your SAP IBP system with SAP BTP, you need to create two communication arrangements. They are based on the
following communication scenarios:
SAP BTP Connectivity Service – On Premise Integration (SAP_COM_0574)
SAP BTP Connectivity Service – Service Channel Integration (SAP_COM_0805)
For more information, see Integrating On-Premise Systems.
Procedure
Arrangement Name
Example
RTI_SAP_COM_0574
Service Key Paste the JSON text containing the service key that you generated in the previous
chapter Create Service Instance in SAP BTP Cockpit.
Arrangement Name
Example
RTI_SAP_COM_0805
Service Key Paste the JSON text containing the service key that you generated in the previous
chapter Create Service Instance in SAP BTP Cockpit.
Note
You can use the same service key for inbound and outbound.
Use
Now you add and connect your SAP BTP subaccount to the Cloud Connector. For more information, see Managing Subaccounts.
Procedure
Note
https://<hostname>:<port>
<hostname> refers to the machine on which the Cloud Connector is installed.
<port> is the Cloud Connector port specified during installation (the default port is 8443).
Example
https://scc-ibp.xxx.yyy.corp:8443/
2. Choose Add Subaccount.
3. In the Add Subaccount dialog box, enter the following data:
Example
US East (VA) – AWS
Subaccount Enter your SAP BTP subaccount ID (Cloud Foundry enabled). You can find this
information in your SAP BTP Cockpit under your Subaccount, tab General, field
Subaccount ID.
Example
f4010598-2199-4080-8b86-6d8c2689f67c
Display Name Enter a meaningful name that allows you to easily recognize your subaccount on the
UI as compared to the technical subaccount name.
Example
IBP-BestPractices
Location ID Define a location ID that identifies the location of this Cloud Connector for a specific
subaccount.
Example
IBPBP
Example
IBP-BestPractices
6. In the Subaccount Dashboard table, a new line is added. Check the status of your subaccount connection managed by this
Cloud Connector.
7. On the top of the screen, you see the Operational since … status message.
8. In the Tunnel Information section, Status is set to Connected.
9. Log in to your BTP account. Select your subaccount. Choose Cloud Connectors from the menu and make sure that your
newly linked Cloud Connector status is Connected.
Use
The Cloud Connector only allows access to trusted backend systems. For more information, see Configure Access Control
(RFC).
Procedure
Note
https://<hostname>:<port>
<hostname> refers to the machine on which the Cloud Connector is installed.
<port> is the Cloud Connector port specified during installation (the default port is 8443).
Example
https://scc-ibp.xxx.yyy.corp:8443/
2. On the Cloud Connector Administration screen, from the Subaccount field at the top of the screen, choose your subaccount.
Example
IBP-BestPractices
3. On the navigation pane on the left side of the screen, choose Cloud To On-Premise for your subaccount.
4. Choose the Access Control tab.
Note
The following configuration steps will differ depending on whether you want to use a direct connection to an
application server or load balancing using the message server. Implement either case 1 (without load balancing) or case
2 (with load balancing) based on your requirements.
Application Server Enter the host name of your SAP S/4HANA application server. The Cloud Connector
will try to establish a connection to this system, so the address has to be real.
Example
Instance Number Enter the instance number of your SAP S/4HANA application server. You can find this
value in your SAP Logon à Properties.Choose the Connection tab and check the field
Instance Number. Then choose Next.
Example
00
Virtual Host You can virtualize the system information if you want to hide your internal host name
from the cloud. You can enter any virtual information of your choice even if it doesn’t
exist.
Enter a virtual host name of your SAP S/4HANA application server. The field is pre-
filled with the values of the internal host.
Example
s4h
Virtual Port Enter a virtual instance number of your SAP S/4HANA application server. The field is
pre-filled with the values of the internal instance number. Then choose Next.
Example
00
The virtual port will then be composed as sapgw00.
Example
s4h
Note
Using the Check Internal Host checkbox, you can trigger a ping from the
Cloud Connector to the internal host to make sure the Cloud Connector can
indeed access the internal system.
If the ping to the internal host is successful, the state Reachable is shown. If it
fails, a warning is displayed in column Check Result. You can view the issue
details by choosing the Details button or check them in the log files.
Message Server Enter the host name of your SAP S/4HANA message server. You can find the message
server in your SAP Logon à Properties. Choose the Connection tab and check the
field Message Server.
Example
ldcss4h.xxx.yyy.corp
System ID Enter the system ID. The system ID is a three-character identifier that is also found in
the SAP Logon configuration. Choose Next.
Example
S4H
Virtual Host You can virtualize the system information if you want to hide your internal host name
from the cloud. You can enter any virtual information of your choice even if it doesn’t
exist.
Enter a virtual host name of your SAP S/4HANA message server. The field is pre-
filled with the values of the internal host.
Example
s4h
Virtual Port Enter the virtual system ID. It should be a three-character identifier. Choose Next.
Example
S4H
The virtual port will then be composed as sapmsS4H.
Example
s4h
Note
Using the Check Internal Host checkbox, you can trigger a ping from the
Cloud Connector to the internal host to make sure the Cloud Connector can
indeed access the internal system.
If the ping to the internal host is successful, the state Reachable is shown. If it
fails, a warning is displayed in column Check Result. You can view the issue
details by choosing the Details button or check them in the log files.
10. Now you need to set up the mapping for all application servers. In the Mapping Virtual To Internal System section, choose
Add to define a new system.
11. In the Add System Mapping dialog box, enter the following data:
Application Server Enter the host name of your SAP S/4HANA application server. You can find the host
name in your SAP Logon à transaction code: SMMS à field Host Name.
Example
ldai1s4h.xxx.yyy.corp
Instance Number Enter the instance number of your SAP S/4HANA application server. You can find this
value in your SAP Logon à Properties. Choose the tab Connection and check the field
Instance Number. Then choose Next.
Example
00
Virtual Host Enter a virtual host name of your SAP S/4HANA application server. The field is pre-
filled with the values of the internal host.
Example
ldai1s4h
Virtual Port Enter a virtual instance number of your SAP S/4HANA application server. The field is
pre-filled with the values of the internal instance number. Then choose Next.
Example
00
Example
ldai1s4h
Note
Using the Check Internal Host checkbox, you can trigger a ping from the
Cloud Connector to the internal host to make sure the Cloud Connector can
indeed access the internal system.
If the ping to the internal host is successful, the state Reachable is shown. If it
fails, a warning is displayed in column Check Result. You can view the issue
details by choosing the Details button or check them in the log files.
12. Repeat steps 10-11 to add the other application servers if needed.
Use
In addition to allowing access to a particular host and port, you must also specify which function modules (resources) may be
called from SAP IBP in your SAP S/4HANA system. The Cloud Connector only allows access to resources for which you grant
access explicitly. In an RFC scenario, these resources are specified by function module name. The Cloud Connector checks if the
function module name of an incoming request exactly matches the name specified in the configuration. If this is not the case, the
request is denied. For more information, see Configure Accessible Resources.
Procedure
Note
https://<hostname>:<port>
<hostname> refers to the machine on which the Cloud Connector is installed.
<port> is the Cloud Connector port specified during installation (the default port is 8443).
Example
https://scc-ibp.xxx.yyy.corp:8443/
2. On the navigation pane on the left side of the screen, choose Cloud To On-Premise for your subaccount.
Note
The following configuration steps will differ depending on whether you want to use a direct connection to an
application server or load balancing using the message server. Implement either case 1 (without load balancing) or case
2 (with load balancing) based on your requirements.
Active X (selected)
Note
You have two options to enter the data based on the Naming Policy:
9. If you want to use the Exact Name option, repeat steps 5 to 7 with the following data:
Active X (selected)
Note
You have two options to enter the data based on the Naming Policy:
Prefix: you only need to enter the prefix of the function name.
Exact Name: you need to enter specific functions.
If you choose the Prefix option, the Cloud Connector allows all incoming requests for which the function module name
begins with the specified string. If you choose the Exact Name option, the Cloud Connector checks if the function
module name of an incoming request exactly matches the name specified in the configuration. If this is not the case, the
request is denied.
16. If you want to use the Prefix option, repeat steps 5 to 7 with the following data:
17. If you want to use the Exact Name option, repeat steps 5 to 7 with the following data:
Note
You can download the configured resources as a ZIP file and reused them in other mapping definitions. This can save
you time especially if load balancing is used in the system landscape on the on-premise side.
18. Repeat the above steps for all relevant application servers. If you have downloaded the configured resource as a ZIP file, you
can directly upload this file instead of entering the data manually.
Use
For scenarios where a call must be made from on-premise systems to an SAP BTP ABAP environment using RFC, you can
establish a connection to an ABAP Cloud tenant host.
For more information, see Configure a Service Channel for RFC.
Procedure
Note
https://<hostname>:<port>
<hostname> refers to the machine on which the Cloud Connector is installed.
<port> is the Cloud Connector port specified during installation (the default port is 8443).
Example
https://scc-ibp.xxx.yyy.corp:8443/
2. On the Cloud Connector Administration screen, from the Subaccount field at the top of the screen, choose your subaccount.
Example
IBP-BestPractices
3. On the navigation pane on the left side of the screen, choose On-Premise To Cloud for your subaccount.
4. In the Service Channels section, choose Add.
5. In the Add Service Channel dialog box, enter the following data:
ABAP Cloud Tenant Host Enter your SAP IBP tenant name.
Example
myXXXXXX-api.scmibp.ondemand.com
Local Instance Number Define the local instance number by which the ABAP Cloud system can be reached by
the client systems.
Note
You can enter any instance number for which the port is not yet used on the
Cloud Connector host. Check the Service Channels Overview section to see
which port numbers are already used.
The port numbers follow this pattern: 33<LocalInstanceNumber>
Please note down this instance number. You will need it in chapter
Configuring RFC Connections.
Connections 1
Note
Enabled means that the channel is established immediately after you choose
Finish. Deselect this checkbox if you don’t want to establish the channel
immediately.
6. In the Service Channels section, the Status is displayed as Service channel is enabled.
For outbound integration, the following settings are created (replace S4H001 with your SAP S/4HANA system SID and client):
For more information, see Integrating On-Premise Systems via Real-Time Integration
Use
Create a communication user for inbound integration from SAP S/4HANA to SAP IBP.
Example
RTI_INTEG
Example
User inbound integration from S4 to IBP
Note
Remember the password for later use in chapter Configuring RFC
Connections.
5. Choose Create.
Use
Create a communication system for inbound integration from SAP S/4HANA to SAP IBP.
Procedure
System Name
Example
RTI_INBOUND
Communication User Add the inbound communication user you created in the previous chapter.
<User Name>
Example
RTI_INTEG
Note
One inbound communication system can be used for multiple logical SAP S/4HANA systems.
Use
Note
One inbound communication arrangement can be used for multiple logical SAP S/4HANA systems.
Procedure
Arrangement Name
Example
RTI_SAP_COM_0770
Example
RTI_INBOUND
Inbound Communication
User Name This field is filled automatically after you select the Communication System. You can
also select one user if multiple communication users are assigned to the
communication system.
Example
RTI_INTEG
Logical System Enter the logical system of your SAP S/4HANA system.
Example
S4HCLNT001
Note
Use transaction SE16 and open table T000 in your SAP S/4HANA system
to find out your logical system.
If you want to connect your SAP IBP system to multiple source SAP
S/4HANA systems, you need to add all of them here.
Note
Use the same communication system and communication user as for SAP_COM_0770:
Arrangement Name
Example
RTI_SAP_COM_0769
Use
Create two service users ZRTI_CONFIG_1 and ZRTI_MAIN_2 for later use in communication scenarios SAP_COM_0684 and
SAP_COM_0685. They are required for outbound integration and reconciliation.
Procedure
Example
ZSAP_SCM_IBP_RTI_CONFIG_1
Last Name
Example
ZRTI_MAIN_2
User Type B System
Role
Example
ZSAP_SCM_IBP_RTI_MAIN_2
Use
Note
If you need to run the outbound integration to multiple SAP S/4HANA systems, you must create a communication
system for each of these SAP S/4HANA systems.
Procedure
Example
RTI_S4H001_CFG_OUTBOUND
System Name
Example
RTI_S4H001_CFG_OUTBOUND
Host Name Enter the virtual host. See chapter Configure Cloud To On-Premise Communication
Channel.
Example
s4h
Note
See chapter Configure Cloud To On-Premise Communication Channel.
Port
Example
443
Cloud Connector On the right side of the screen, set the toggle to ON.
SCC Location ID Enter the <Location ID> you maintained when configuring the connection
between the SAP BTP subaccount and the Cloud Connector. See chapter Connect SAP
BTP with Cloud Connector.
Example
IBPBP
Note
You can use the location ID feature of the Cloud Connector to connect
multiple Cloud Connectors to a single SAP BTP subaccount.
Note
The SCC Location ID is case sensitive.
Target Host Enter the virtual host of your SAP S/4HANA application server.
Example
s4h
Note
Use the virtual host you maintained in chapter Configure Cloud To On-
Premise Communication Channel.
Note
All host names, instance numbers, and ports that you use in communication
systems based on the Cloud Connector are virtual names. This means that you
don’t have to use the real names and numbers from your on-premise network,
if you don’t want to make such internal information public in the cloud. You
can also choose names and numbers identical to your internal ones. All names
must be configured in the Cloud Connector. You can see all existing virtual
backend system names in the SAP BTP Cockpit under Cloud Connectors à
Connectivity.
Instance Number Enter the last two digits of the virtual port of your SAP S/4HANA system instance.
Example
00
Note
Use the virtual port you maintained in chapter Configure Cloud To On-
Premise Communication Channel.
Client Enter your SAP S/4HANA system client that is to send transaction data.
Example
001
Message Server Enter the virtual host of your SAP S/4HANA message server.
Example
s4h
Note
Use the virtual host you maintained in chapter Configure Cloud To On-
Premise Communication Channel.
Note
All host names, instance numbers, and ports that you use in communication
systems based on the Cloud Connector are virtual names. This means that you
don’t have to use the real names and numbers from your on-premise network,
if you don’t want to make such internal information public in the cloud. You
can also choose names and numbers identical to your internal ones. All names
must be configured in the Cloud Connector. You can see all existing virtual
backend system names in the SAP BTP Cockpit under Cloud Connectors à
Connectivity.
Client Enter your SAP S/4HANA system client that is to send transaction data.
Example
001
Group Enter your SAP Logon group (you can choose from the available ones. Run transaction
SMLG in your on-premise system.)
Example
PUBLIC
Target System Enter the virtual system ID you maintained for your SAP S/4HANA message server.
Example
S4H
Communication User Add the outbound communication user you created in chapter Outbound Integration –
Create Communication Users.
Example
ZRTI_CONFIG_1
Example
RTI_S4H001_TRANS_OUTBOUND
System Name
Example
RTI_S4H001_TRANS_OUTBOUND
Host Name Enter the Virtual Host. See chapter Configure Cloud To On-Premise Communication
Channel.
Example
s4h
Note
If you use load balancing, enter the virtual host name of your message server.
Port
Example
443
Cloud Connector On the right side of the screen, set the toggle to ON.
SCC Location ID Enter the <Location ID> you maintained when configuring the connection
between the SAP BTP subaccount and the Cloud Connector. See chapter Connect SAP
Example
IBPBP
Note
You can use the location ID feature of the Cloud Connector to connect
multiple Cloud Connectors to a single SAP BTP subaccount.
Note
The SCC Location ID is case sensitive.
Target Host Enter the virtual host of your SAP S/4HANA system.
Example
s4h
Note
Use the virtual host you maintained in chapter Configure Cloud To On-
Premise Communication Channel.
Note
If you use load balancing, enter the virtual host name of your message server.
Note
All host names, instance numbers, and ports that you use in communication
systems based on the Cloud Connector are virtual names. This means that you
don’t have to use the real names and numbers from your on-premise network,
if you don’t want to make such internal information public in the cloud. You
can also choose names and numbers identical to your internal ones. All names
must be configured in the Cloud Connector. You can see all existing virtual
backend system names in the SAP BTP Cockpit under Cloud Connectors à
Connectivity.
Instance Number Enter the last two digits of the Virtual Port of your SAP S/4HANA system instance
Example
00
Client Enter your SAP S/4HANA system client that is to send transaction data.
Example
Message Server Enter the virtual host of your SAP S/4HANA message server.
Example
s4h
Note
Use the virtual host you maintained in chapter Configure Cloud To On-
Premise Communication Channel.
Note
All host names, instance numbers, and ports that you use in communication
systems based on the Cloud Connector are virtual names. This means that you
don’t have to use the real names and numbers from your on-premise network,
if you don’t want to make such internal information public in the cloud. You
can also choose names and numbers identical to your internal ones. All names
must be configured in the Cloud Connector. You can see all existing virtual
backend system names in the SAP BTP Cockpit under Cloud Connectors à
Connectivity.
Client Enter your SAP S/4HANA system client that is to send transaction data.
Example
001
Group Enter your SAP Logon group (you can choose from the available ones. Run transaction
SMLG in your on-premise system.)
Example
PUBLIC
Target System Enter the virtual system ID of your SAP S/4HANA message server.
Example
S4H
Communication User Add the outbound communication user you created in chapter Outbound Integration –
Create Communication Users.
Example
ZRTI_MAIN_2
Use
Procedure
Arrangement Name
Example
RTI_SAP_COM_0684_S4H001
Example
RTI_S4H001_TRANS_OUTBOUND
Outbound Communication
User Name This field is filled automatically after you select the Communication System. You can
also select one user if multiple communication users are assigned to the
communication system.
Example
ZRTI_MAIN_2
Logical System Enter the logical system of your SAP S/4HANA system. If you don’t know this value,
you can look it up in transaction BD54 in your SAP S/4HANA system.
Example
S4HCLNT001
Arrangement Name
Example
RTI_SAP_COM_0685_S4H001
Communication System
Example
RTI_S4H001_CFG_OUTBOUND
User Name
Example
ZRTI_CONFIG_1
Logical System
Example
S4HCLNT001
Use
Create the logical systems for your SAP S/4HANA and SAP IBP systems.
Procedure
Note
The logical system is usually named as follows: <your SAP S/4HANA system name>CLNT<client>.
Example
S4HCLNT001
5. On the Change View “Logical Systems”: Overview screen, choose New Entries.
6. On the New Entries: Overview of Added Entries screen, enter the following data:
Example
S4HCLNT001
Name
Example
S4HCLNT001
7. Repeat steps 5 and 6 with the following data for the SAP IBP system:
Note
The CIF target logical system (which is the SAP IBP system) is logically linked to the target planning area in SAP IBP.
If more than one planning area is required in SAP IBP, then additional logical systems must be created.
Example
ZXYCLNT100
Name
Example
ZXYCLNT100
8. Choose Save.
9. Choose a workbench request if required.
Use
Procedure
Example
001
Example
S4HCLNT001
8. Choose Save.
9. Choose a workbench request if required.
Use
Procedure
Example
ZXYCLNT100
Release 713
6. Choose Save.
7. Choose a workbench request if required.
Use
Create an RFC destination connecting the Cloud Connector. For more information about the cloud connector, see Cloud
Connector.
Note
The CIF and the SM59 configuration will be related 1:1 in the SAP IBP planning area. If you need multiple planning
areas in SAP IBP, you must create dedicated CIF target logical systems and SM59 destinations. Consider this aspect in
your naming concept.
Procedure
Example
ZXYCLNT100
7. Choose the Technical Settings tab and enter the following data:
Example
scc-ibp.xxx.yyy.corp
Instance No. Enter the Instance Number you specified when configuring the service channel in the
Cloud Connector. The number consists of the last two digits of the Port value.
Example
27
Note
See chapter Configure On-Premise to Cloud Communication Channel.
8. Choose the Logon & Security tab and enter the following data:
User Make sure to use the same user as in chapter Inbound Integration – Create
Communication User.
Example
RTI_INTEG
9. Choose the Special Options tab and enter the following data:
Note
The UI might differ depending on your SAP S/4HANA version. If the “Use SAP HANA Cloud Connector” checkbox is
displayed, you can simply ignore it because it isn’t used by RTI.
Note
If the connection test is successful, a table displaying Logon and Transfer of x KB actions and results will be displayed.
12. On the RFC Destination ZXYCLNT100 screen, choose Utilities à Test à Authorization Test from the menu.
Note
If the authorization test is successful, a table displaying Logon and Transfer of x KB actions and results will be
displayed.
Use
Define the number range for the parallel initial data transfer (number range object CIF_LOAD).
Procedure
To Number 9999
5. Choose Save.
Use
The CIF framework must know which RFC destinations are defined as SAP IBP target systems. Therefore, you set the target
SAP IBP system as the logical system name (and consequently the corresponding RFC connection) in SAP S/4HANA.
Procedure
Example
ZXYCLNT100
Note
This is a read-only field. After the initial integration run, the operation mode
will be set automatically.
Q_Type I
Note
For real-time integration with SAP IBP, you can only use inbound queues.
The Inbound Queues setting means that queue processing is controlled by the
target system. If there are not enough work processes, the data is first saved
temporarily in inbound processing in the target system and then processed
gradually as resources become available.
5. Choose Save.
Use
Activate the bgRFC connection for your SAP IBP target logical system.
Note
You must have created an RFC connection with the same name as your logical system. Otherwise, the activation will
fail. See chapter Configuring RFC Connections.
Procedure
Example
ZXYCLNT100
Use
You configure a supervisor destination for the bgRFC to receive the configuration settings for the bgRFC scheduler. In addition,
the supervisor starts or stops the schedulers as required.
Prerequisites
You have created a system user of type B called BGRFCSUPER. Use transaction SU01 to create the system user. This user
is used for the bgRFC communication using the destination you will create, for example, BGRFC_SUPERVISOR.
You have assigned role SAP_BC_BGRFC_SUPERVISOR to user BGRFCSUPER. Use transaction SU01 to assign this role
to the user BGRFCSUPER.
For SAP NetWeaver 7.0, you have created a bgRFC destination as an ABAP connection using the RFC destination name
BGRFC_SUPERVISOR, without load balancing, target host, SAP Gateway host and service. Specify the user, language and
password. This ensures that the scheduler is activated on the same application server as the specified user. Later, you
configure the supervisor destination for the bgRFC to receive the configuration settings for the bgRFC scheduler.
Procedure
Use
Transaction SBGRFCCONF in SAP S/4HANA is used to assign the prefix to a queue. During runtime, you can monitor this
queue in transaction SBGRFCMON.
Example
Integration Profile with outbound queue prefix CG1 is defined for Planning Area PA_Y. Data is integrated to
S/4HANA system A. You can monitor the queue in system A by filtering for queue CG1 in transaction
SBGRFCMON.
Procedure
Example
ZXYCLNT100
2.8.5.10 Configure Queue Name Prefix for SAP IBP (Inbound to SAP
IBP)
Use
In transaction CFI1, you define the prefix used by the sender system. This prefix indicates the source SAP S/4HANA system,
enabling you to distinguish multiple SAP S/4HANA systems connected to your SAP IBP system. If one queue is blocked on the
SAP IBP side, all other parallel queues can still be processed. During runtime, you can monitor the queues in the SAP IBP
Monitor bgRFC Queues app.
Procedure
Example
ZXYCLNT100
5. On the Change View “Queue Name Prefix for SAP IBP”: Overview screen, choose Save.
Use
For transactional data, there is a smooth transition between the initial transfer (supply) of data and the transfer of data changes.
As soon as the integration model is activated, the SAP S/4HANA system switches from the initial supply of data to the transfer of
data changes. If you create, change, or delete a document relevant to SAP IBP, the system immediately transfers this change to
SAP IBP (online transfer).
In some cases, you can also perform an online transfer of changes to specific master data, such as material, customer, and vendor
data that is already contained in an active integration model, to the target system.
To enable the online transfer of changes from SAP S/4HANA to SAP IBP, you must activate Business Transaction Events
(BTEs) generally in SAP S/4HANA for the integration with SAP IBP.
Procedure
A X (selected)
A X (selected)
6. Choose Save.
7. Choose a workbench request if required.
Use
Procedure
Use
Procedure
CIFCUS X (selected)
CIFVEN X (selected)
CIFSRC X (selected)
4. Choose Save.
Use
Procedure
Days in Past 30
Type Multiresource 1
Application-Dependent Settings
4. Choose Save.
2.9.1 Prerequisites
Note
This configuration step is only required for the following time-series-based planning scope items:
IBP – time-series-based inbound integration with SAP S/4HANA (3OF)
IBP – Integration of planned independent requirements to SAP S/4HANA (4NO)
The system administrator first needs to install and configure the SAP Data Services Agent. This is not described in this
document. For more information, refer to the application help: SAP Data Services Agent.
Key figures:
CAPASUPPLY (Capacity Supply)
INITIALINVENTORY (Stock on Hand)
MINRECEIPT (Minimum External Receipts)
MINPRODUCTION (Minimum Production Receipts)
ACTUALSQTY (Actuals Qty)
EXCHANGERATE (Exchange Rate)
OPENORDERSREV (Open Orders Rev)
Note
EXCHANGERATE is modeled as an attribute as key figure in sample planning area SAPIBP1. SAP provides two
options for integrating the exchange rate in time-series-based inbound integration with SAP S/4HANA:
The first is to integrate the exchange rate as a master data type. In this case, you get a static exchange rate in SAP IBP
after integration from S/4HANA.
The second is to integrate the exchange rate as a key figure. In this case, the time-dependent exchange rates maintained
in S/4HANA are integrated to SAP IBP.
Choose the option that best suits your requirements.
Use
Procedure
Note
If you skipped the previous step, the SCM-IBP-INT-ECC-TS-IO node and its extractors are nevertheless there. You can
find them under the NODENOTCONNECTED node.
Example
/IBP/LOCATION_ATTR
Note
If required, you can specify additional selection conditions using the Selections parameter. You can also use the
Projections field to define which fields to request. These criteria correspond to fields that are mapped in the CI-DS data
flow or are used to evaluate filters that cannot be sent to the extractor.
The /IBP/ETS_REPL_TEST report comes with a set of system variants. Half of these variants contain the requested
fields and filter settings of the templates delivered in CI-DS. The other half of the variants have the same filter settings
but request more fields. They can be used to analyze the details of the selected data. This is especially useful with the
/IBP/ORDER_KF extractor because the detailed variant shows all individual object IDs and attributes related to the
aggregated time series.
For most of these extractors, in order to check whether they provide data correctly, you have to run the corresponding
initial load steps described in the IBP for time-series-based inbound integration with SAP S/4HANA (3OF) test script.
Use
This section describes how to activate the BAdI delivered by SAP to fill in the data for master data type attributes that will be
used in the SAP IBP business processes.
Procedure
Use
This section describes how to define the logical SAP S/4HANA system from which you’re going to replicate data to SAP IBP.
This logical system is used to uniquely address the system in your system landscape.
Procedure
Note
The logical system is usually named as <your SAP S/4HANA system name>CLNT<client>, for example,
S4HCLNT001.
5. On the Change View “Logical Systems”: Overview screen, choose New Entries.
6. On the New Entries: Overview of Added Entries screen, enter the following data:
Example
S4HCLNT001
Example
S4HCLNT001
7. Choose Save.
8. Choose a workbench request if required.
Use
Example
001
Example
S4HCLNT001
8. Choose Save.
9. Choose a workbench request if required.
Use
A Business Transaction Event (BTE) allows you to immediately and automatically transfer all changes made to SAP S/4HANA
transactional data and the following master data to SAP IBP:
Vendor
Customer
Material
Procedure
5. Choose Save.
6. Choose a Workbench Request if required.
Use
You need to maintain the SAP S/4HANA logical system that you’re using to replicate data to SAP IBP.
Procedure
Example
S4HCLNT001
Release 70
6. Choose Save.
7. Choose a workbench request if required.
Use
Use
This section describes how to activate the change transfer of info records.
Procedure
active X (selected)
5. Choose Save.
6. Choose a customizing request if required.
Use
This chapter describes how to create the communication user for the WebSocket RFC integration.
Note
The authentication method can be either certificate-based using an X.509 certificate or basic authentication. This
document only describes the basic authentication. For certificate-based authentication, see Defining the Communication
Arrangement.
Procedure
Example
BP_USER_0593
Example
BP_USER_0593
5. Choose Create.
Procedure
Example
Example
BP_IBP_0593
4. Choose Create.
5. On the Communication System screen, in the Technical Data section, select Inbound Only.
6. On the Communication System screen, in the User for Inbound Communication section, choose the plus sign (+).
7. In the New Inbound User dialog box, enter the following data:
Example
BP_IBP_0593
8. Choose OK.
9. On the Communication System screen, choose Save.
Procedure
Example
ZSAP_COM_0593_WEBSOCKET
Example
7. Choose Save.
Note
This configuration step is only required for the following time-series-based planning scope item:
IBP – Integration of planned independent requirements to SAP S/4HANA (4NO)
To be able to schedule jobs in SAP Cloud Integration for data services from SAP IBP, you must perform the configuration tasks
described in the next sections.
For more information, refer to the application help: Configuring the Outbound Communication with SAP Cloud Integration for
Data Services. You can also refer to SAP Note 2593057.
Procedure
Example
BP_CIDS_0035
Example
BP_CIDS_0035
5. Choose Create.
6. On the Communication System screen, enter the following data:
Example
7. On the Communication System screen, in the Users for Outbound Communication section, choose the plus sign (+).
8. In the New Outbound User dialog box, add the user for the outbound communication using the authentication method User
Name and Password and the format WebServicesUser|<your organization>.
9. On the Communication System screen, choose Save.
Procedure
Example
BP_SAP_COM_0035_CIDS
Example
BP_CIDS_0035
7. Choose Save.
Note
This section is only required if you want to view 3D models of locations in the IBP for sales and operations – footprint
analysis (5LG) scope item, or if you want to view 3D models of products in the IBP for response and supply – response
planning (2P0) scope item.
2.10.1 Prerequisites
Communication scenario SAP_COM_0658 is used to display 3D models of your products or locations in SAP IBP apps. To set
up this communication scenario in your SAP IBP system, you must:
Own a license of SAP Enterprise Product Development.
Have added the SAP IBP tenant domain to the list of allowed origins in the Security Administration app in the Visualization
area of SAP Enterprise Product Development.
Have administrator rights to download the default client certificate from the Maintain Client Certificates app.
Have access to the SAP Enterprise Product Development APIs and a generated service key for communication.
For more information, refer to the application help: Integrating with SAP Enterprise Product Development.
Procedure
Example
ZSAP_COM_0658_EPD
Service Key Copy and paste the service key file content
Use
You associate a 3D model of a location for the IBP for sales and operations – footprint analysis (5LG) scope item, or you
associate a 3D model of a product for the IBP for response and supply – response planning (2P0) scope item.
Once the SAP_COM_0658 communication scenario has been implemented, several SAP IBP apps such as Intelligent Visibility
can display a View 3D Model icon next to attribute identifiers that have 3D models associated with them in the SAP Enterprise
Product Development service.
To associate a 3D model, you must:
Have access to the Browse Visualizations app in the Enterprise Product Development launchpad.
Have 3D visualization models that are available in the Enterprise Product Development storage.
Procedure
Note
This step is executed in SAP Enterprise Product Development.
1. Log on to the SAP Fiori launchpad in the SAP Enterprise Product Development system.
2. Open Browse Visualizations.
3. Navigate to the folder where the 3D visualization model is stored.
4. Go to the Details of the 3D model for your location.
5. Select the Metadata tab and choose Edit.
6. To associate an SAP IBP attribute identifier with a 3D model for your location, enter the two-part keys on the Metadata
screen as follows:
Example
ZXY_100
Note
Enter value ALL for all systems.
Category <PLANNING_AREA_NAME>
Example
ZSAPIBP1
Note
Enter value ALL for all planning areas.
Name ATTR
Value LOCID
Example
ZXY_100
Note
Enter value ALL for all systems.
Category <PLANNING_AREA_NAME>
Example
ZSAPIBP1
Note
Enter value ALL for all planning areas.
Name ATTR_VALUE
Example
1010
7. Choose Save.
8. To associate an SAP IBP attribute identifier with a 3D model for your product, repeat the above steps and enter the two-part
keys on the Metadata screen as follows:
Example
ZXY_100
Note
Enter value ALL for all systems.
Category <PLANNING_AREA_NAME>
Example
ZSAPIBP1
Note
Enter value ALL for all planning areas.
Name ATTR
Value PRDID
Example
ZXY_100
Note
Enter value ALL for all systems.
Category <PLANNING_AREA_NAME>
Example
ZSAPIBP1
Note
Enter value ALL for all planning areas.
Name ATTR_VALUE
Example
FG126
This section provides an overview of where business consultants can get information on the available SAP Best Practices
scenarios that we call scope items.
For SAP Best Practices for SAP Integrated Business Planning, you can check the available scope items in the SAP Best Practices
Explorer.
You can download the SAP Best Practices package using the Download button. The downloaded ZIP file contains the
configuration guides that describe crucial parts of the system configuration of the respective process.
In the Solution Scope section, you find information on which business processes are covered by the scope items:
You can access an individual business process description by choosing its name, for example, IBP for sales and operations –
demand review (2BQ).
By choosing the Process flow link, you can navigate to the process diagram. This diagram provides the business process
representation.
By choosing the Test script link, you can navigate to the business process documentation. Use this document to evaluate the
business process in the system.
This section provides an overview of the security-relevant information that applies to the deliverables of this solution package.
You implement SAP Best Practices for SAP Integrated Business Planning manually by following the configuration guides as
outlined in the Prerequisites Matrix.
The following matrix shows which configuration guide must be deployed for which scope item:
In some cases, no manual implementation of time-series based planning scope items is required (see the caution notes below).
You can find all configuration guides in the content library in the SAP Best Practices Explorer:
https://rapid.sap.com/bp/RDS_IBP → Accelerators → Implementation → SAP Best Practices content library
Is the SAP Best Practices for SAP IBP content updated in my system with each SAP IBP upgrade?
The SAP Best Practices for SAP IBP content pre-installed in or added to your SAP IBP system is not automatically updated with
each SAP IBP release. The SAP Best Practices for SAP IBP content will remain in the same state as when the tenant was first
provisioned or when the content was added. If you want the SAP Best Practices for SAP IBP content to be updated to the latest
version, you need to manually configure the latest content as outlined in the Prerequisites Matrix.
For further details, refer to the FAQ document.
SAP Best Practices provides preconfigured content and settings to be deployed with existing SAP applications. For information
about SAP Integrated Business Planning installation and usage, refer to the SAP Help Portal.
For information on SAP S/4HANA, supply chain integration add-on for SAP Integrated Business Planning, see the SAP Help
Portal:
For information on real-time integration for order-based planning, see the SAP Help Portal:
For information on SAP Work Zone, see the SAP Help Portal: