Version Changed on Change Log

2.5 09/04/2024 - Chapter 6.6: avoid conflict with queue prefix configuration
between bgrfc and smqr
2.4 22/01/2024 - Chapter 5.6: Saving BADI implementation step corrected. It
does not need to be local object.
2.3 20/12/2023 - Chapter 4.1: BTP subaccount ID does not need to be Cloud
Foundry enabled. Wording refined
- Chapter 2.4: Cloud Foundry removed from prerequisites
section
- Chapter 2.5: Cloud Foundry remove from prerequisites

2.2 06/11/2023 - Chapter 4.1: BTP subaccount ID does not need to be Cloud
Foundry enabled. Content from brackets removed
- Chapter 5.3: RFC destination setup in case of High Availability
mode for CC.
2.1 25/09/2023 - Chapter 6.6: queue prefix assignment is not optional
2.0 07/17/2023 - Chapter 5.3: serializer protocol documentation update
- Chapter 6.6: queue prefix assignment
1.9 01/26/2023 - Chapter 4.2: virtual host/port guide update
- Chapter 6: maximum one 0684 and 0685 CA per target On-
Premise logsys
- Chapter 6.3: Value of Host name must equal with Target Host
attribute
1.8 08/12/2022 - Chapter 2: link added to BTP licensing for RTI
- Chapter 2.6: share via file instead of copy-paste
- Chapter 3.1 and 3.2: only one BTP connectivity supported
- Chapter 4.6: CC sizing guide added
- Chapter 6.5: bgrfc Supervisor destination configuration added
- Chapter 8: UCON troubleshooting
1.7 09/27/2022 - Chapter 8: new Troubleshooting chapter
- Chapter 6.2: screenshot and text updates. Using latest sampe
sample role version.
- Chapter 2.2: Cloud Foundry enablement not mandatory
anymore
- Chapter 2.4: Connectivity_proxy Runtime environment
selection
1.6 08/02/2022 - Chapter 5.3: RFC Client must be always 100
- Chapter 4.4: FUNCTION_IMPORT_INTERFACE
1.5 06/21/2022 - Chapter 2.1: chapter renamed, and paragraph added.
- Chapter 2.2: explanation for the region selection.
- Chapter 4.2: Cloud Connector setup step for 1 application
server only
1.4 05/23/2022 - Chapter 4.2: Instructions added when to use the setup
- Chapter 4.3: Instructions added when to use the setup with
Load balancer
- Chapter 4.4: Cloud Connector resource definitions (for short
names Prefix type added)
- Chapter 5.4: SAP Note added if system type is not available in
NDV2
- Chapter 6.2: SAP notes for PFCG sample roles for
Reconciliation added
- Chapter 6.5: added sbgrfcconf inbound destination
-
1.3 05/11/2022 - Chapter 5.3: RFC Setup
o No need to enable “Use HANA Cloud Connector”
 checkbox.
o Interface Check for Fast Serialization settings
highlighted
- Chapter 7: bgRFC Log
1.2 4/14/2022 - Chapter 2.1: BTP Global account requirement
- Chapter 5.4 update: CFC1 OpMode explanation added.
- Chapter 6.3: load balancing setup added
- Chapter 5.5 added for bgRFC
1.1 3/29/2022 - New Chapter: 4.3 Setup "Cloud To On-Premise"
Communication Channel (Load Balancer)
- Chapter 6.4 IBP - Create SAP_COM_0684 – Transactional Data
for Real-Time Outbound Integration updated: Communication
System definition in case of Load Balancer
- Chapter 4.4 Configure Accessible Resources update: download
Resource Definitions as zip file
- Adding Queue Prefix configuration to Chapter 5.3 On-Premise
– Configured CIF
1.0 3/22/2022 - Chapter 3.1 and 3.2: JSON content should be shared via plain
text format only
- Chapter 4.1 Connect Cloud Connector to your BTP subaccount:
Process and screenshots added

Pro tip: Please follow this guide in the order of the chapters step by step and check the
descriptions as well!
Contents
1. Concept ................................................................................................................................. 4
2. BTP Subaccount Setup ........................................................................................................... 5
2.1 Access your BTP Global account ..................................................................................... 5
2.2 Create Subaccount (Optional)......................................................................................... 6
2.3 Setup Connectivity Service Entitlement for subaccount ................................................ 10
2.4 Create Service Instance ................................................................................................ 12
2.5 Change existing service plan to connectivity_proxy (troubleshooting step)................... 14
2.6 Create Service Key........................................................................................................ 15
3. Setup BTP Connectivity in IBP .............................................................................................. 18
3.1 Create SAP_COM_0805 – SAP IBP Inbound BTP Connectivity........................................ 18
3.2 Create SAP_COM_0574 - SAP IBP Outbound BTP Connectivity...................................... 22
4. Cloud Connector Setup ........................................................................................................ 26
4.1 Connect Cloud Connector to your BTP subaccount ....................................................... 26
4.2 Setup "Cloud To On-Premise" Mapping ........................................................................ 29
4.3 Setup "Cloud To On-Premise" Mapping (Load Balancer scenario) ................................. 32
4.4 Configure Accessible Resources .................................................................................... 38
4.5 Setup "On-Premise to Cloud" Communication Channel ................................................ 40
4.6 Sizing guide .................................................................................................................. 42
5. Setup IBP inbound ............................................................................................................... 43
5.1 IBP - Create SAP_COM_0769 - Transactional Data for Real-Time Inbound Integration .. 44
5.2 IBP - Create SAP_COM_0770 - Master Data for Real-Time Inbound Integration ............ 49
5.3 On-Premise RFC Setup.................................................................................................. 52
5.4 On-Premise - Configure CIF........................................................................................... 58
5.5 On-Premise - Configure bgRFC ...................................................................................... 62
5.6 On-Premise – Implement BADi (optional) ..................................................................... 63
6. Setup IBP Outbound............................................................................................................. 68
6.1 On-Premise – Create service user for SAP_COM_0685 ................................................. 69
6.2 On-Premise – Create service user for SAP_COM_0684 ................................................. 74
6.3 IBP - Create SAP_COM_0685 – Configuration Data for Real-Time Outbound Integration
79
6.4 IBP - Create SAP_COM_0684 – Transactional Data for Real-Time Outbound Integration86
6.5 On-Premise – Configure bgRFC Supervisor Destination ................................................. 93
6.6 On-Premise – Configure bgRFC destination for inbound queues ................................... 94
7. Other ................................................................................................................................... 96
7.1 Logs for bgRFC.............................................................................................................. 96
8. Troubleshooting................................................................................................................... 97
1. Concept

In this example guide the following system ID will be used:

IBP system: XZY, Client: 100
S/4HANA On Premise System: S4H, Client: 001
2. BTP Subaccount Setup
In case your company has already a Global Account it can be reused. RTI does not required by
default a separate global account.

On this FAQ page you can find answer regarding licensing for RTI:

2.1 Access your BTP Global account

If you don’t know your BTP Account details please contact your SAP Sales representative. BTP is only
required for connectivity services for Real-Time integration.
 2.2 Create Subaccount (Optional)

Application help: Link

Update [2022-09]: During the recent months BTP became a multi environment (Cloud Foundry, Kyma,
Kubernetes, etc.) A subaccount can have multiple active environments (or none). Cloud Foundry was
the first of the environments, therefore Cloud Foundry enabled subaccount was required earlier. This
is not the case anymore. By creating a new subaccount, no Environment is Active by default but
connectivity_proxy plan don’t need an active environment (can instead create in “others”).

During this step the following entities will be created:

- Subaccount

Prerequisite:

- You have the Global Administrator role in the global account

- You have the Org Manager role in the organization you want to create a space

Procedure

1. Log on to SAP Business Technology Platform (SAP BTP) cockpit and go to the right
region, followed by the global account.
2. Choose New Subaccount, specify a display name and subdomain, and save your
changes.

Provide

- Display Name
- Subdomain,
- Region: select your infrastructure provider (AWS, GCP, Azure, etc.) of choice and (any)
region
- Global Account you want to assign this subaccount to. Please note: the subdomain will
become part of the URL for accessing applications that you subscribe to from this
subaccount. (Proper naming convention for multiple subaccounts)
3. Optional (this step not required anymore): Select the newly created subaccount,
choose Enable Cloud Foundry, provide a Cloud Foundry organization name, and then
choose Create.
4. Choose Spaces in the navigation bar and then choose New Space.

5. Enter a space name, assign space roles, as required, and save your changes.

6.
 2.3 Setup Connectivity Service Entitlement for subaccount

During this step the following entities will be created:

- connectivity_proxy will be added to the subaccount’s entitlements

Prerequisite:

- You have the Global Administrator role

- You have the Org Manager role in the organization you want to create a space
- Subaccount Created

Procedure

The screenshots below are useful to determine if the connectivity_proxy plan is added to the
subaccount. Ensure the connectivity_proxy plan is added.
 2.4 Create Service Instance

Application help: https://help.sap.com/viewer/09cc82baadc542a688176dce601398de/Cloud/en-

US/6d6846def3c443aa9f83d127353147ce.html

During this step the following entities will be created:

- Service Instance using connectivity_proxy

Prerequisite:

- Subaccount is created and ensure that connectivity_proxy added to the subaccount’s

entitlements

Procedure

- Login to SAP BTP Cockpit and follow the screenguide

Select Runtime Environment:

- Select “Other” or Cloud Foundry environment (if you enabled previously)

The instance takes a moment to create. Once it is completed you will see a status of Completed.
 2.5 Change existing service plan to connectivity_proxy (troubleshooting step)

Prerequisite:

- You already have a service instance with wrong Service Plan (e.g. “lite”)
- Subaccount is created and ensure that connectivity_proxy added to the subaccount’s
entitlements

Procedure

- Login to SAP BTP Cockpit and follow the screenguide

 2.6 Create Service Key

Application help: https://help.sap.com/viewer/09cc82baadc542a688176dce601398de/Cloud/en-

US/6fcac08409db4b0f9ad55a6acd4d31c5.html

During this step the following entities will be created:

- Service Key for BTP Subaccount Connectivity Instance

Prerequisite:

- Connectivity Instance creation with connectivity_proxy service plan

Procedure

- Login to IBP Cloud system and follow the screenshots

Navigate to the subaccount being used for RTI.

1. select Instances and Subscriptions. You should see the service created off Connectivity
Service with a plan as connectivity_proxy.
2. Click on the instance for the Connectivity Service.

3. The screen will split to show the instance. Select the three dots and then choose Create
Service Key.
4. Enter a Service Key name and press Create. This will Create a Service Key for you.
5. The Service Key will then be displayed under the Service Instance.

6. The service key will be required later during SAP_COM_0805 and 0574 Communication
Arrangement creation. In case different roles are responsible for these setup activities it is
highly recommended to download the Service Key and share as a file instead of text copy-
paste via email or chat programs.
3. Setup BTP Connectivity in IBP

https://help.sap.com/viewer/feae3cea3cc549aaa9d9de7d363a83e6/2202/en-
US/0ba15be350994915b9786684b8163968.html

3.1 Create SAP_COM_0805 – SAP IBP Inbound BTP Connectivity

IBP will allow service channels from SCCs that are connected to the subaccount that IBP is aware
of. For this validation SAP_COM_0805 is required.

Important: Currently a given IBP intsance can be connected to only one BTP subaccount. IF you
have created multiple ones, the configuration of the most recently created will be used by the
system. We highly recommend to have only one instance of SAP_COM_0805.

During this step the following entities will be created:

- SAP_COM_0805 Communication Arrangement

- ZSAP_COM_0805 Communication System – automatically created. This communication
system should not be assigned later for any other communication arrangements!

Prerequisite:

- Service key is created in BTP Subaccount. The below steps will show how the Service Key can
be retrieved from BTP.

Procedure

- Login to IBP Cloud system and follow the screenshots

Service key can be retrieved from the SAP BTP Subaccount:
After you have put the JSON text to clipboard switch over to the SAP_COM_0805 Dialog and CTRL +
V the Service Key into the Text Area. (sending of the JSON content by outlook might remove
automatically the quotation marks. Please in such case use plain text file).

Press the Create button.

SAP_COM_0805 has been created:

 3.2 Create SAP_COM_0574 - SAP IBP Outbound BTP Connectivity

Important: Currently a given IBP instance can be connected to only one BTP subaccount. IF you
have created multiple ones, the configuration of the most recently created will be used by the
system. We highly recommend to have only one instance of SAP_COM_0574.

During this step the following entities will be created:

- SAP_COM_0574 Communication Arrangement

- ZSAP_COM_0574 Communication System – automatically created. This communication
system should not be assigned later for any other communication arrangements!

Prerequisite:

- Service key is created in BTP Subaccount. The below steps will show how the Service Key can
be retrieved from BTP.

Procedure

- Login to IBP Cloud system and follow the screenshots

Service key can be retrieved from the SAP BTP Subaccount:
After you have put the JSON text to clipboard switch over to the SAP_COM_0805 Dialog and CTRL +
V the Service Key into the Text Area. (sending of the JSON content by outlook might remove
automatically the quotation marks. Please in such case use plain text file).
Press the Create button.

SAP_COM_0574 has been created:

4. Cloud Connector Setup
4.1 Connect Cloud Connector to your BTP subaccount

Application help: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-

US/f16df12fab9f4fe1b8a4122f0fd54b6e.html

During this step the following entities will be created:

- Link between BTP Subaccount and Cloud Connector

Prerequisite:

- Subaccount with created in BTP and Subaccount ID is known

- API endpoint of the BTP subaccount is known / or geographical region of the IBP system

Procedure

- Login to Cloud Connector. By default the Connector Overview screen is selected. IF not,
navigate there
- Click on “Add Subaccount” button

- Add Subbacount Dialog appears

- Enter the mandatory attributes

o Region: either choose from the drop down or enter the host suffix of the API
endpoint from the BTP Subaccount (url without the “https://api.” prefix)
o Subaccount: Your BTP Subaccount
 o Login email: your BTP login email
o Password: your login password
o Location ID: give any unique name for your location Id. Later in SAP_COM_0684 and
SAP_COM_0685 setup you will need it

- Save. New line will be added in the Subaccount Dashboard

- Click on the details and make sure that Cloud Connector is connected
- Login to your BTP Account, Select your Subaccount, Choose Cloud Connectors in the menu
and make sure that your newly linked Cloud Connector status is Connected.
 4.2 Setup "Cloud To On-Premise" Mapping

If you have multiple application servers on the on-premise side, using Load Balancer might be a
requirement. Please use the next chapter instead.

This chapter is only for a landscape setup when only one application server is connected to IBP.

Application help: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-

US/ca5868997e48468395cf0ca4882f5783.html

- Enter the Application Server

- Enter the Instance Number: Use the instance number or your application server (SAP Logon
-> Select your System -> right click -> “Properties…” -> Connection Tab -> Instance Number)
 - Enter the Virtual Application Server: free text that will be mapped to your actual
Application server. You will refer to this virtual name in IBP when setting up IBP outbound
integration.
- Enter the Virtual Instance Number: use a 2 digit number according to your choice. Can differ
from the Instance number of your application server. (you will refer to this number in IBP
configuration later)

Define Resource Definitions: either upload or create manually (follow steps Configure Accessible
Resources)

Upload previously saved resource definitions:

 4.3 Setup "Cloud To On-Premise" Mapping (Load Balancer scenario)

If you have only one application server, please use the previous chapter instead. This chapter is
relevant only if you have multiple application servers with load balancer on the on-premise side.

During this step the following entities will be created:

- Mapping for Message Server

- Mapping for all application servers maintained in the logon group including the application
host names as well

Prerequisite:

- Link between BTP Subaccount and Cloud Connector created

- Access to the On-premise application servers

Procedure

- Login to your Cloud Connector

Message Server Mapping

For the next step, you need to determine the host name of your message server (preferably the fully
qualified domain name).

Login via SAP Login -> start SMMS transaction -> check the highlighted entry and use this as a basis
for the Cloud Connector mapping setup.
- Enter the Message Server host
- Enter System ID

- Please create Resource Definitions by following steps in chapter Configure Accessible

Resources.
- Highly recommended to save Resource configuration to zip file and reuse in the following
steps
Setup Mapping for all application servers
- Login to SAP via SAP Logon
- Start transaction SMMS to determine the application servers

- For each of the hosts (example: s4h_aaa, s4h_bbb) create separate Cloud to On-Premise
Mapping with the same Resource Definitions:
 - Enter the Application Server
- Enter the Instance Number: Use the instance number or your application server (SAP Logon
-> Select your System -> right click -> “Properties…” -> Connection Tab -> Instance Number)

- Enter the Virtual Application Server: use the name of the application server
- Enter the Virtual Instance Number: Use the instance number or your application server (SAP
Logon -> Select your System -> right click -> “Properties…” -> Connection Tab -> Instance
Number)

Define Resource Definitions: either upload or create manually (follow steps Configure Accessible
Resources)

Upload previously saved resource definitions:

 4.4 Configure Accessible Resources

Application help: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-

US/3b12086100b344d39a2ff0c9410e66c6.html

Enable the following resources (IBP 2202 compatible scope – for latest up-to-date list check the
application help)

Resource Which Service uses

SBIC (as prefix) SAP_COM_0685

or
SBIC_MESSURE_TRANSFER
SBIC_CURRENCIES_TRANSFER

SBFC (as prefix) SAP_COM_0685

or
SBFC_FACTORY_CALENDAR_TRANSFER

CIF (as prefix) SAP_COM_0684

or
CIF_ORDER_INBOUND_IBP
CIF_SL_DOC_INBOUND_IBP
CIF_PO_INBOUND_IBP
CIF_CCR_JOB_STATUS_GET_IBP
CIF_CCR_ORDER_JOB_START_IBP
CIF_CCR_READ_ORDER_IBP
CIF_CCR_READ_STOCK_IBP
CIF_CCR_STOCK_JOB_START_IBP
CIF_DELTA3_GET_MATWERK
CIF_GET_MATWERK
CIF_GET_ALL_ACTIVE_MODELS
CIF_REFRESH_RECEIVE

BGRFC (as prefix) SAP_COM_0684

or
BGRFC_DEST_SHIP

RFC (as prefix) SAP_COM_0684

SAP_COM_0685

FUNCTION_IMPORT_INTERFACE (as exact match) SAP_COM_0684

Configured resources can be downloaded as zip file to local file system and reused for later in a
different mapping definition. This can save time especially if load balancer is used in the landscape
(on the on-premise side)
 4.5 Setup "On-Premise to Cloud" Communication Channel

During this step the following entities will be created:

- Communication Channel between Cloud Connector and your IBP System.

Prerequisite:

- SAP_COM_0805 Communication Arrangement has been created in SAP IBP

Procedure

- Login to your Cloud Connector

Use the api url of your IBP system. You can find it by following this steps:

1. login to your IBP system and start Communication Arrangement

2. Search for the 0805 Communication Arrangement that was created previously and open
it

3. You can find the API-URL of your IBP System:

You need to use the host name without the “https://” Protocol prefix

<host>-api.scmibp.ondemand.com

Application help: https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-

US/18602c25ae33423f847e9f2c539d7fa0.html
 4.6 Sizing guide

https://help.sap.com/docs/CP_CONNECTIVITY/cca91383641e40ffbe03bdc78f00f681/89e51224cc89
4d67a899be4d10cc54e1.html?q=garbage%20collection
5. Setup IBP inbound

Set up communication arrangements in SAP IBP to enable integration between order-based planning
and SAP ECC or SAP S/4HANA using real-time integration. You need to create the following
communication arrangements:

- SAP_COM_0769 - Planning - Transactional Data for Real-Time Inbound Integration

- SAP_COM_0770 - Planning - Master Data for Real-Time Inbound Integration

The following concept diagram shows what entities should be created and how they must relate to
each other. At the end of this chapter the this setup will be achieved.

The object names in this guide are just samples. Please adjust it in your environment according to
your policies.
 5.1 IBP - Create SAP_COM_0769 - Transactional Data for Real-Time Inbound Integration

During this step the following entities will be created:

- SAP_COM_0769 Communication Arrangement

- RTI_INBOUND Communication System

Prerequisite:

- No special prerequisites required (however it is suggested that SAP_COM_0805

Communication Arrangement has been successfully created)

Procedure

- Login to IBP Cloud system and follow the screenshots

Enter LOGSYS of you source on-premise system. The field is multivalued field. If your IBP will be
connected to multiple source on-premise systems, you have to list those as well.
Save
 5.2 IBP - Create SAP_COM_0770 - Master Data for Real-Time Inbound Integration

During this step the following entities will be created:

- SAP_COM_0770 Communication Arrangement

Prerequisite:

- SAP_COM_0769 created – the same Communication system will be reused

Procedure

- Login to IBP Cloud system and follow the screenshots

-
-

-
Enter LOGSYS of you source on-premise system. The field is multivalued field.
If your IBP will be connected to multiple source on-premise systems, you have to list those as well.
SAVE
 5.3 On-Premise RFC Setup

Before two or more systems can communicate with each other, you have to set up the technical
coupling between them.
The name of the corresponding RFC destination must be identical to the name of the logical
target system that will be used later to configure CIF framework.
(Be aware that CIF and SM59 configuration will be related 1:1 into IBP Planning Area. If you will
need multiple Planning Areas in IBP you have to create dedicated CIF target logsyses and SM59
destinations. Consider this aspect in your naming concept.)

During this step the following entities will be created:

- RFC Destination

Prerequisite:

- Communication user created in IBP system during SAP_COM_0769 or SAP_COM_0770

- Cloud Connector setup
o Cloud Connector installed
o Connected to BTP Subaccount
o “On-Premise to Cloud” Service Channel created towards to IBP system

Procedure

- Login to On-Premise backend system via SAP logon

- Start SM59 transaction

Technical Settings
- Enter the host name of the Cloud Connector (url your CC) – make sure it is accessible
within your network. (When using an RFC service channel in a high availability setup for
Cloud Connector, please read the abstract description at the bottom of
https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/configure-service-channel-for-
rfc)
- Enter the Instance number: last two digits of the Service Channel created in Cloud Conector
Logon & Security

- Client: 100 – ALWAYS!!!

Special Options

Please Ensure that you make the following setup:

- Protocol section: Fast Serializer

- Interface Check for Fast Serialization: Destination for New Scenario is selected
o Older Kernel versions might not offer „Fast Serializer” option. In this case please
select „classic with bgRFC” or similar one that is bgRFC specific.

 Newer Netweaver versions might contain a Flag „Use SAP HANA Cloud Connector”. Please
ignore this settings, no need use it.
SAVE

Test connection
Authorization Test
 5.4 On-Premise - Configure CIF

The steps required for the technical integration using Core Interface (CIF) are described here.

During this steps the following entities will be created:

- CIF Framework configuration

Prerequisite:

- RFC Destination has been created in SM59

Procedure

- Login to On-Premise backend system via SAP logon

Start BD54
Start NDV2

If you cannot select SAP_IBP as Syst. Type: SAP note 3054109 is not implemented.
Start CFC1

OpMode is a readonly field used by CIF framework and will be automatically modified by the
framework later. No need to set it/configure it.
Start CFC91
Start CFI1 (Optional)

https://help.sap.com/viewer/68fa1e86fe6f41d98421d1ce13a08a9f/2202/en-
US/f946552aa8964ba386c1ed7c8484ebfa.html

You can assign a specific queue prefix to a target IBP Logsys. With that you can separate and monitor
the incoming queues in IBP (use Monitor bgRFC Queue Fiori application)

5.5 On-Premise - Configure bgRFC

Please follow below help to setup a supervisor destination if not exits.

https://help.sap.com/docs/SAP_NETWEAVER_750/68bf513362174d54b58cddec28794093/8d58225
18bc72214e10000000a44176d.html
 5.6 On-Premise – Implement BADi (optional)

During this step the following entities will be created:

- Custom BADi implementation for CIF_MATERIAL_MAP_IBP

- Custom BADi implementation for CIF_LOCATION_MAP_IBP

Prerequisite:

Procedure

- Login to On-Premise system via SAP Logon

start /nSE18
Create Enhancement Implementation (this is just an example):

Material Location

Enhancement ZCIF_MATERIAL_MAP_IBP_SAMPLE ZCIF_LOCATION_MAP_IBP_SAMPLE

Implementation

Short Test Sample Implementation for Material Sample Implementation for Location
Integration Integration

Save the Enhancement implementation either as a local object or transportable one depending
on your needs.
Create BAdi implementation:
Material Location

BAdi ZCIF_MATERIAL_MAP_IBP_SAMPLE ZCIF_LOCATION_MAP_IBP_SAMPLE

Implementation

Description Sample Implementation for Material Sample Implementation for Location

Integration Integration

Implementing CL_CIF_MATERIAL_MAP_IBP_SAMPLE CL_CIF_LOCATION_MAP_IBP_SAMPLE

Class
6. Setup IBP Outbound

Set up the following communication arrangements in SAP IBP to enable integration from IBP to SAP
ECC or SAP S/4HANA using real-time integration. You need to create the following communication
arrangements:

- SAP_COM_0685 - Configuration Data for Real-Time Outbound Integration

- SAP_COM_0684 - Transactional Data for Real-Time Outbound Integration

The following concept diagram shows what entities should be created and how they must relate to
each other. At the end of this chapter this setup will be achieved.

The object names in this guide are just samples. Please adjust it in your environment according to
your policies.

IMPORTANT

There should be maximum one SAP_COM_0684 and 0685 related Communication arrangements per
target on-premise system (LOGSYS).
 6.1 On-Premise – Create service user for SAP_COM_0685

During this step the following entities will be created:

- IBPRTI_CSYS service user (User name can be any. This is just an example)
- ZSAP_SCM_IBP_RTI_CONFIG_1 PFCG role for configuration outbound from

Prerequisite:

- SAP Note 3115273 implemented

- Communication arrangement from SAP_COM_0574 has been created

Procedure

- Login to On-Premise system via SAP Logon

Start SU01

Start PFCG
 6.2 On-Premise – Create service user for SAP_COM_0684

During this step the following entities will be created:

- IBPRTI_TSYS service user (User name can be any. This is just an example)
- ZSAP_SCM_IBP_RTI_MAIN PFCG role for configuration outbound from

Prerequisite:

- SAP Note 3115273 implemented

- SAP Notes 3131724 and 3131295 implemented (required for reconciliation)
- As RTI delivers continuously not all role related notes might be listed here in this document.
Please check Central note 3106619 for any update. The note description contains text “Role”

Procedure

- Login to on-Premise system and follow the screenshots

Start SU01
Start PFCG

On the screenshots the sap sample role highlighted with blue.

SAP might release new version of sample role. Please make sure that you copy the latest version of
SAP sample role (version numbers represented a suffix in the role name. This higher the number, the
newer the version. Check SAP Note 3106619 for latest ones – CTRL+F “Role” on the page).
 6.3 IBP - Create SAP_COM_0685 – Configuration Data for Real-Time Outbound
Integration

During this step the following entities will be created:

- SAP_COM_0685 Communication Arrangement

- RTI_S4HCLNT001_0685 communication system

Prerequisite:

- On-Premise service user created for configuration outbound

- Cloud Connector mapping to internal on-Premise system setup completed

Procedure

- Login to IBP Cloud system and follow the screenshots

The next step can vary depending on you use load balancer in the On-Premise environment or not.
Fields to maintain (No Load Balancer)
- Value of Host name must equal with Target Host attribute
- Cloud Connector switch: switch on
- SCC Location ID: location ID of your SAP BTP subaccount
- Instance number: last 2 digits of the virtual Port
- Fast Serialization: DISABLE!
- Client: the client of the on-premise system
- Outbound user: configuration outbound service user created in On-Premise system
Fields to maintain (Load Balancer in your On-Premise environment):

- Host name: Virtual name of the message server configured in Cloud Connector. Value of
Host name must equal with Target Host attribute
- Cloud Connector switch: switch on
- SCC Location ID: location ID of your SAP BTP subaccount
- Target System: Virtual name of the message server configured in Cloud Connector
- Fast Serialization: DISABLE!
- Load Balancer: Enable!
- Client: the client of the on-premise system you want to send transaction data
- Group: SAP Logon group (you can choose from the available ones. Run SMLG transaction in
your on-premise system)
- Outbound user: configuration outbound service user created in On-Premise system
Scroll down to setup outbound user

Enter LOGSYS of you source on-premise system.

SAVE
 6.4 IBP - Create SAP_COM_0684 – Transactional Data for Real-Time Outbound Integration

During this step the following entities will be created:

- SAP_COM_0684 Communication Arrangement

- RTI_S4HCLNT001_0684 communication system

Prerequisite:

- On-Premise service user created for transactional data outbound integration

- Cloud Connector mapping to internal on-Premise system setup completed.
- In case Load Balancer is used on the On-Premise side, please perform CC setup according to
Chapter “Setup "Cloud To On-Premise" Communication Channel (Load Balancer)”)

Procedure

- Login to IBP Cloud system and follow the screenshots

-

-
-

-
The next step can vary depending on you use load balancer in the On-Premise environment or not.

Fields to maintain (No Load Balancer)

- Value of Host name must equal with Target Host attribute
- Cloud Connector switch: switch on
- SCC Location ID: location ID of your SAP BTP subaccount
- Instance number: last 2 digits of the virtual Port
- Fast Serialization: enable!
- Client: the client of the on-premise system
- Outbound user: configuration outbound service user created in On-Premise system
Fields to maintain (Load Balancer in your On-Premise environment):

- Host name: Virtual name of the message server configured in Cloud Connector
- Cloud Connector switch: switch on
- SCC Location ID: location ID of your SAP BTP subaccount
- Target System: Virtual name of the message server configured in Cloud Connector
- Fast Serialization: enable!
- Load Balancer: Enable!
- Client: the client of the on-premise system you want to send transaction data
- Group: SAP Logon group (you can choose from the available ones. Run SMLG transaction in
your on-premise system)
- Outbound user: configuration outbound service user created in On-Premise system
Scroll down to setup outbound user

Enter LOGSYS of you source on-premise system.

SAVE
 6.5 On-Premise – Configure bgRFC Supervisor Destination

https://help.sap.com/docs/SAP_NETWEAVER_750/68bf513362174d54b58cddec28794093/8d58225
18bc72214e10000000a44176d.html?locale=en-US
 6.6 On-Premise – Configure bgRFC destination for inbound queues

During this step the following entities will be created:

- New bgRFC Destination for queue prefixes to able to monitor incoming requests

Prerequisite:

- On-Premise service user created for transactional data outbound integration

- Cloud Connector mapping to internal on-Premise system setup completed.

Procedure

- Login to On-Premise system

- Start /nsbgrfcconf transaction

You can configure in IBP CG0…CG9 prefixes per Real-Time integration profile. If you want to have
only one inbound destination just add “CG”. IF you want to separate the IBP RTI queues (generated
from IBP) create dedicated inbound destinations for each prefix.
Important: Please make sure that you queue prefix settings does not run into conflict with existing
SMQR setup.

For example if you have CG* in SMQR and you want to configure CG0 in bgrfc this will lead to a
conflict and error.
7. Other

In this chapters we collect useful settings however they are not essential parts of the RTI
communication setup. Before you set them please check the available online documentation. This
chapter just collects them, this is not the official source of documentation

7.1 Logs for bgRFC

To enable logging for bgRFC

- Start /nsbgrfcconf transaction

- Select the 3rd tab (Scheduler:Destination)
- Check the History Active checkbox
8. Troubleshooting

Before you open an incident for SAP regarding connectivity issues please check the following typical
errors and their resolutions.

Application job errors for RTI templates

 Symption: "Error when opening an RFC connection (There is no SAP Cloud Connector (SCC)
connected to your subacc"
 Solution:
1. Delete SAP_COM_0805 and SAP_COM_0574 (with the related communication
scenario entities)
2. Re-create SAP_COM_0805 and SAP_COM_0574 by following Chapter 3

CFM2 integration - Outbound t/qRFC Ucon RFC Rejected

This error happens usually when RFC destination is unproperly created. Please ensure you have
enabled fast serialization for the RFC destination in your on-premise system (RFC Setup). After you
fixed the configuration please reactivate the CIF logsys in CFC91