6/20/2019

SAP Business Partner

Generated on: 2019-06-20

SAP S/4HANA | 1809.002

PUBLIC

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the SAP Help Portal.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 6/20/2019

Con guring SOA Manager for Business

Partner
Use
This document describes the con guration steps that are required to enable the exchange of business partner data between
SAP S/4HANA systems using point-to-point enterprise services communication without a Process Integration (PI) system.

Note
The technical names of a few objects may contain the text MDG. This has no relation to the product SAP MDG.

Prerequisites
Authorizations

The following authorizations are required in the provider system and in the receiver (client) system:

As administrative role for the SOA Manager SAP_BC_WEBSERVICE_ADMIN_TEC is assigned.

Authorizations are assigned for the transactions listed below:

SU01

SUIM

PFCG

Service Users in ABAP Stack

To create a service user in the provider and the receiver system carry out the steps described below in both systems.

1. Choose transaction SU01, choose Create and enter a user.

2. On the Roles tab assign the role SAP_BC_WEBSERVICE_ADMIN_TEC.

Business Functions

The following business functions are active in the provider system and in the receiver system.

Note
To activate the business function, run the Customizing activity under SAP Customizing Implementation Guide
Activate Business Functions

FND_SOA_REUSE_1: Improvements for SOA Reuse Functions

Note
By activating the business function, you can use the following cross-application tool improvements that
facilitate the use of services:

SOA Mapping Tool

Error Handling

Point-to-Point Enablement for Asynchronous Enterprise Services

This is custom documentation. For more information, please visit the SAP Help Portal 2
 6/20/2019

Business Foundation: Services for Business Partner

Support for Point-to-Point Communication

To activate the support for the point-to-point communication run this activity in the provider system and in the receiver
system in Customizing for SAP Customizing Implementation Guide Cross-Application Components Processes and
Tools for Enterprise Applications Enterprise Services Point-to-Point Enablement for Asynchronous Enterprise
Services Activate Support for Point2Point Communication .

Connection to System Landscape Directory

Either the provider system and the receiver systems are connected to the System Landscape Directory (SLD) or the
BAdI MDG_IDM_GET_LCL_SYSTEM is implemented to determine the local system ID. To verify the correctness of the
SLD content run transaction SLDCHECK in the provider and client systems. Ignore the browser dialog box. In the systems
check that message reads: “Summary: Connection to SLD works correctly.”

If you decide to implement the BAdI and not to use SLD, see the documentation of the IMG activity Master Data
Governance General Settings Data Replication De ne Custom Settings for Data Replication De ne Technical
Settings BAdI: Determination of Local System Name .

Con guration of the Web Service Runtime

The technical con guration of the web service runtime is done according to SAP note 1043195 .

Error and Con ict Handler

SAP recommends to activate the error and con ict handler. To do so, run the following Customizing activity in the
provider system and in the receiver system: SAP Customizing Implementation Guide Cross-Application
Components General Application Functions Error and Con ict Handler Activate Error and Con ict Handler .

Procedure
The following steps are required to con gure the SOA Manager for MDG (transaction SOAMANAGER) in the provider and the
receiver system.

1. Create a pro le for point-to-point communication

To create a new pro le in the provider and the receiver system carry out the steps described below in both systems.

a. On the Technical Administration tab choose Pro les.

b. Choose Create Pro le, enter MDG as name, enter a description, and choose Next.

Note
The pro le names and versions should be identical in the SOA manager settings for both provider and receiver
systems.

c. Mark User ID/Password, verify that in section Identi able Business Context the led IBC Determinationhas the
value No IBC Determination and choose Next.

d. In the section Transport Security mark the check box Secure Communication Only.

e. If necessary enter proxy settings and choose Finish to save the settings and activate the pro le.

2. Con gure the client setting

To con gure the client setting in the provider and the receiver system carry out the steps described below in both
systems.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 6/20/2019
a. On the Technical Administration tab, choose SAP Client Settings and then choose Edit.

b. Enter an Organization Name.

c. Based on your system connection, choose one of the following steps:

If your Business System is connected to the SLD: Choose Get from SLD to receive the Business

System from the system landscape directory (SLD).

If you have used the BAdI, provide local system ID as de ned in the BAdI

MDG_IDM_GET_LCL_SYSTEM

d. Enter the own Business System ID.

Note
To retrieve the own Business System ID run transaction SLDCHECK and check the section Calling function
LCR_GET_OWN_BUSINESS_SYSTEM.

e. Choose Save to receive the Business Application ID.

3. Con gure a provider system for the Business Scenario Con guration

To con gure a provider system for the business scenario con guration in the provider and the receiver system carry out
the steps described below in both systems.

a. On the Technical Administration tab, choose Provider Systems, then choose Create. Enter as Name the business
system ID of the counterpart system, enter a Description, select the Pro le Name de ned in step 1 and choose
Next.

b. Enter the SLD Identi er in for following form: <client>.SystemName.<XYZ>.SystemNumber.<Installation

Number>.SystemHome.<Host>, for example
416.SystemName.QV6.SystemNumber.0020270862.SystemHome.uxdbqv6

Note
The SystemNumber can be found as described: System Status SAP System Data Installation Number

Similarly, the SystemHome can be found under System Status Database Data Host .

c. Enter the Access URL for WSIL and Logon Information under WSIL Services.

Format of WSIL URL: https://<hostname>:<port>/sap/bc/srt/wsil?sap-client=<client>

Note
To identify the host name and port for access URL call transaction SMICM and choose Goto Services . Use the
HTTPS host name and port displayed in the list. We recommend to use the message server host.

d. Enter a User for WSDL and a Password for WSDL, enter a User for WSIL and a Password for WSIL. In both cases
you can enter the service user that you have crated in the backend system. Choose Next.

e. Maintain the Business Application ID.

i. Choose Create to maintain a business application ID in provider System

ii. Enter an application name and a description, for example: sap.com/BusinessApplicationABAP

iii. Enter the business application ID.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 6/20/2019

Note
Note that the business application ID can be found in the counterpart system in the transaction
SOAMANAGER under Technical Administration SAP Client Settings .

iv. Press Finish to save and activate the system connection.

Note
When you con gure the provider system , maintain details of the counterpart (other system) that you want to
connect to.

As a result the Identi able Business Context Reference (IBC reference) for the counterpart system has been
generated automatically. To verify this proceed as follows:

a. On the Service Administration Tab follow the link Identi able Business Context Reference.

b. Choose Search. The IBC reference for the counterpart system should be displayed in the list in form
XYZ_001 where XYZ_001 is system ID and client of the counterpart system.

4. Edit Logon Data for Business Scenario

To create a user account in the provider and the receiver system carry out the steps described below in both systems.

Note
The back end user has to exist in both systems.

a. On the Service Administration tab choose Logon Data Management.

b. On the Maintenance tab choose Create, enter your Logon Data Name and Description for example
SERVICE_USER/Generic Service User and choose Next.

c. Select User/Password or X.509 as Authentication Method.

d. Enter the user name that you created earlier in the backend system and choose Finish to activate the logon data.

5. Assign Logon Data to Provider IBC Reference

To assign logon data to the IBC Reference of counterpart system in the provider and the receiver system carry out the
steps described below in both systems.

a. On the Service Administration tab choose Logon Data Management.

b. On the Assignments tab choose Create.

c. Use the input help to select a Provider IBC Reference. Select the IBC reference of the counterpart system from
the search result list and choose Next.

d. Select the user name you have entered in step 2 of the previous chapter as Logon Data from the drop down list
and choose Finish.

6. Create Integration Scenario Con guration for Point-to-Point Communication using Service Group

To create the integration scenario con guration for point-to-point communication using a service group in the provider
and receiver system, carry out the steps described below in both systems.

a. Create the integration scenario con guration.

i. On the Service Administration tab choose Local Integration Scenario Con guration.

This is custom documentation. For more information, please visit the SAP Help Portal 5
 6/20/2019
ii. Choose Create, enter a name and a description for the business scenario and choose Next.

b. Search for service de nitions and assign a pro le.

i. Choose Add to search for Service De nition.

ii. In the dialog box search for the Service De nition BUSINESSPARTNERSUITEBULKREPLIC, mark it in the
result list and choose Add to Worklist.

iii. Similarly search for the following service de nitions and add them to the worklist:

Service De nition (Internal Name) External Name

BUSINESSPARTNERSUITEBULKREPLI1 BusinessPartnerSUITEBulkReplicateCon rmation_In

BUSINESSPARTNERRELATIONSHIPSUI BusinessPartnerRelationshipSUITEBulkReplicateRequest_In

BUSINESSPARTNERRELATIONSHIPSU1 BusinessPartnerRelationshipSUITEBulkReplicateCon rmation_In

Note
To con gure the business partner SOA based search and local copy for the customer client
maintenance scenario as provided by the business function in the provider and receiver system,
execute step 3 with the values shown below:

Service De nition (Internal Name) External Name

BUSINESSPARTNERBASICDATABYELEM BusinessPartnerBasicDataByElementsQueryResponse_In

c. Assign pro le to service de nition.

i. Select all services de nitions from the list and choose Assign Pro les.

ii. Select the pro le MDG, choose Assign Pro le and choose Next.

d. Select service groups and provider IBC reference.

i. Choose Add to search for the Service Group.

ii. Enter the service group MDG_BS_SUPPLIERREPLICATEREQ, mark it in the result list and choose Add to
Worklist.

iii. Repeat the procedure for the service group MDG_BS_SUPPLIERREPLICATECONF.

Note
To con gure the business partner SOA based search and local copy for the customer client
maintenance scenario as provided by the business function Master Data Governance for Customer on
Client (ERP) in the provider and receiver system, execute step 3 with the values shown below:

Service Group (Internal Name) Description

MDG_BS_BP_SEARCH Service Group for

BusinessPartnerBasicDataByElementsQueryResponse

e. Assign business application.

This is custom documentation. For more information, please visit the SAP Help Portal 6
 6/20/2019
i. Select all service groups from the list and assign the IBC reference by choosing Assign IBC Reference.

ii. In the dialog box, search for the IBC reference of the counterpart system, mark the entry in the search
result list and choose Assign to Service Group.

iii. Choose Finish.

f. Activate business scenario using the processing of pending tasks

Note
Do not activate the business scenario immediately because rst the business scenario in the counterpart
system needs to be de ned.

i. After creating the integration scenario con guration in counterpart system choose Yes to activate the
Business Scenario.

ii. Follow the link in the section Pending Tasks.

iii. Choose Process List to process all pending tasks.

Note
The activation of the logical ports will not succeed because rst the pending tasks needs to be processed in
the counterpart system. For that reason process all pending tasks in provider system to activate the business
scenario on the provider. Afterwards process all pending tasks in the receiver where the activation failed.

7. Set logical port as default.

To set the default logical port, carry out the following steps:

a. In the Service Administration tab, choose Web Service Con guration.

Note
Similarly, set the default logical port for

BusinessPartnerSUITEBulkReplicateCon rmation_Out in both provider and receiver systems.

b. Choose Object Type: All and Object Name:BusinessPartnerSUITEBulkReplicateRequest_Out

c. Open BusinessPartnerSUITEBulkReplicateRequest_Out. A logical port is created.

d. Select the logical port and click Set Log.Port Default

FND_SOA_REUSE_1: Improvements for SOA

Reuse Functions
Use

Technical Data

Technical Name of Business Function FND_SOA_REUSE_1

Type of Business Function Enterprise Business Function

Available As Of SAP S/4HANA 1511

Technical Usage Any stack including BS_FND

This is custom documentation. For more information, please visit the SAP Help Portal 7
 6/20/2019
Application Component Enterprise SOA (CA-SOA)

Directly Dependent Business Function Requiring Activation in Not relevant

Addition

You can use this business function to take advantage of cross-application tool improvements that facilitate the deployment of
enterprise services. These include enhancements to existing tools (Service Mapping Tool, Error and Con ict Handler), as well as
new functions for categorizing error messages and asynchronous point-to-point communication.

Prerequisites
You have installed the following components as of the version mentioned:

Type of Component Component

Software Component S4CORE

Features
Service Mapping Tool

The Service Mapping Tool (SMT) enables you to ll target structures by using sets of source structures. For example, you can
use it to convert enterprise service data into an SAP-internal format, and vice versa. This business function adds the following
features to the con guration component:

On the con guration user interface, you can toggle between the internal ABAP structure view (generated proxy
structure) and the external representation originating from a service interface (element names).

You can sort the tree display of a source or target structure alphabetically by eld name.

You can assign the source eld to the corresponding target eld by dragging and dropping within the con guration user
interface.

You can generate a where-used list of the relevant con guration entities (such as condition, transformation, conversion,
and eld check class) for a given package group.

A where-used list is available for mapping steps that are used by enterprise services. You can see all the service
interfaces and operations that use a speci c mapping step.

You make the Customizing settings for this function under Cross-Application Components Processes and Tools for Enterprise
Applications Enterprise Services Develop Enterprise Services Create and Edit Mappings.

For more information, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp SAP ERP Enhancement
Packages ERP Central Component Enhancement Package 5 Processes and Tools for Enterprise Applications Mappings for
Enterprise Services.

Error and Con ict Handler (Forward Error Handling)

You can use the Error and Con ict Handler (ECH) to process errors that are detected during the execution of asynchronous
enterprise services. It enables you to resolve errors and con icts on the provider side, either automatically, or with the
involvement of a business user. This business function adds the following features to the Error and Con ict Handler:

You can use your own settings to overwrite the settings for the standard business processes for forward error handling.

You can de ne your own business processes for forward error handling in the Postprocessing Office.

You can register for enterprise services that support forward error handling.
This is custom documentation. For more information, please visit the SAP Help Portal 8
 6/20/2019
Usability and user interface improvements are available for the Payload Editor.

You make the Customizing settings for these features under Cross-Application Components Processes and Tools for
Enterprise Applications Enterprise Services Error and Con ict Handler.

For more information, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp SAP ERP Enhancement
Packages ERP Central Component Enhancement Package 5 Processes and Tools for Enterprise Applications Error and
Con ict Handler (CA-FS-ECH).

Error Categorizer

You can use the Error Categorizer to classify error messages that are displayed when service operations are processed. This
enables you to override the xed assignment of error categories to error messages.

You make the Customizing settings for this component under Cross-Application Components Processes and Tools for
Enterprise Applications Enterprise Services Error Categorizer.

In the enhancement spot ES_BS_SOA_ERR_CAT, the Business Add-In (BAdI) BSSOA_ERR_CAT_BADI is available. You can use this
to change the results determined by the Error Categorizer.

Asynchronous Point-to-Point Communication

This business function includes additional features that enable you to trigger asynchronous enterprise services through the Web
service protocol, without using a mediator (such as SAP NetWeaver Process Integration):

The Response Receiver Correlation Manager enables you to register an incoming request or query. This registration can
be picked up in the corresponding con rmation or response message to control how the response message is routed.

In-application sequencing ensures that incoming messages are processed in the correct order at application level. If a
new message arrives, but a preceding message is missing, it places the new message in a queue until the missing
message arrives.

You can assign the point-to-point enabled services to service groups, and use this group de nition to con gure the
services in the SOA Manager component. A new wrapper class for outgoing service calls bundles the logical ports
generated through this group con guration.

You make the Customizing settings for these features under Cross-Application Components Processes and Tools for
Enterprise Applications Enterprise Services Point-to-Point Enablement for Asynchronous Enterprise Services .

Business Foundation: Services for Business

Partner
Use
Technical Data

Technical Name of Business Function CA_BP_SOA

Type of Business Function Enterprise Business Function

Available From SAP S/4HANA 1511

Technical Usage Any Stack including BS_FND

Application Component LO-MD-BP

This is custom documentation. For more information, please visit the SAP Help Portal 9
 6/20/2019
Required Business Function Not relevant

You can use this business function to activate the BADIs mentioned below to override the standard mapping with customer
speci c mapping of the supplier and customer replication services.

Integration
The BAdIs can be used by Master Data Governace for Supplier as well as by Master Data Governance for Customer.

Prerequisites
You have installed the following components as of the version mentioned:

Type of Component Component Required for the Following Features

Only

Software Component S4CORE NA

Features
BAdI: Business Partner Replication Request Inbound - MDG_SE_BP_BULK_REPLRQ_IN

BAdI: Business Partner Replication Request Outbound - MDG_SE_BP_BULK_REPLRQ_OUT

BAdI: Business Partner Replication Con rmation Inbound - MDG_SE_BP_BULK_REPLCNF_IN

BAdI: BP Relationships Replication Request Inbound - MDG_SE_BP_RELSHIP_IN

BAdI: BP Relationships Replication Request Outbound - MDG_SE_BP_RELSHIP_OUT

BAdI: BP Relationships Replication Con rmation Inbound - MDG_SE_BP_RELSHIP_CONF_IN

This is custom documentation. For more information, please visit the SAP Help Portal 10