Configuring the SOA Manager for MDG (NW 7.
40 or higher)
cl_gui_frontend_services=>gui_upload
This document describes the configuration steps that are required to enable the
exchange of business partner data using point-to-point enterprise services
communication without a process integration (PI) system.
Prerequisites
Authorizations
The following authorizations are required in the MDG hub system and in the MDG
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 MDG hub and the MDG client system carry out the
steps described below in both systems.
Choose transaction SU01, choose Create and enter a user.
On the Roles tab assign the role SAP_BC_WEBSERVICE_ADMIN_TEC.
Business Functions
The following business functions are active in the MDG hub system and in the MDG
client system.
Note Note
To activate the business function run the Customizing activity under Start of the
navigation path SAP Customizing Implementation Guide Next navigation step Activate
Business Functions End of the navigation path
FND_SOA_REUSE_1: Improvements for SOA Reuse Functions
Note 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
CA_SUPPLIER_SOA: Business Foundation for Services for Supplier
CA_BP_SOA: Business Foundation: Services for Business Partner
The following business function needs to be activated on ERP client systems that
are configured for customer client maintenance:
MDG_CUST_ERPCLIENT_1: Master Data Governance for Customer on Client (ERP)
Support for Point-to-Point Communication
To activate the support for the point-to-point communication run this activity in
the MDG hub system and in the MDG client system in Customizing for Start of the
navigation path SAP Customizing Implementation Guide Next navigation step Cross-
Application Components Next navigation step Processes and Tools for Enterprise
Applications Next navigation step Enterprise Services Next navigation step Point-
to-Point Enablement for Asynchronous Enterprise Services Next navigation step
Activate Support for Point2Point Communication End of the navigation path.
Connection to System Landscape Directory
Either the MDG hub system and the MDG client 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 MDG hub 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 Start of the navigation path Master Data Governance Next
navigation step General Settings Next navigation step Data Replication Next
navigation step Define Custom Settings for Data Replication Next navigation step
Define Technical Settings Next navigation step BAdI: Determination of Local System
Name End of the navigation path.
Configuration of the Web Service Runtime
The technical configuration of the web service runtime is done according to SAP
note 1043195Information published on SAP site.
Error and Conflict Handler
SAP recommends to activate the error and conflict handler. To do so, run the
following Customizing activity in the MDG hub system and in the MDG client system:
Start of the navigation path SAP Customizing Implementation Guide Next navigation
step Cross-Application Components Next navigation step General Application
Functions Next navigation step Error and Conflict Handler Next navigation step
Activate Error and Conflict Handler End of the navigation path.
Procedure
The following steps are required to configure the SOA Manager for MDG (transaction
SOAMANAGER) in the MDG hub and the MDG client system.
Create a profile for point-to-point communication
To create a new profile in the MDG hub and the MDG client system carry out the
steps described below in both systems.
On the Technical Administration tab choose Profiles.
Choose Create Profile, enter MDG as name, enter a description, and choose Next.
Note Note
The profile names and versions should be identical in the SOA manager settings for
both MDG hub and MDG client systems.
Mark User ID/Password, verify that in section Identifiable Business Context the
filed IBC Determinationhas the value No IBC Determination and choose Next.
In the section Transport Security mark the check box Secure Communication Only.
If necessary enter proxy settings and choose Finish to save the settings and
activate the profile.
Configure the client setting
To configure the client setting in the MDG hub and the MDG client system carry out
the steps described below in both systems.
On the Technical Administration tab, choose SAP Client Settings and then choose
Edit.
Enter an Organization Name.
Choose Get from SLD to receive the Business System from the system landscape
directory (SLD).
Enter the own Business System ID.
Note Note
To retrieve the own Business System ID run transaction SLDCHECK and check the
section Calling function LCR_GET_OWN_BUSINESS_SYSTEM.
Choose Save to receive the Business Application ID.
Configure a provider system for the Business Scenario Configuration
To configure a provider system for the business scenario configuration in the MDG
hub and the MDG client system carry out the steps described below in both systems.
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 Profile Name defined in step 1 and choose Next.
Enter the SLD Identifier in for following form:
<client>.SystemName.<XYZ>.SystemNumber.<Installation Number>.SystemHome.<Host>, for
example 416.SystemName.QV6.SystemNumber.0020270862.SystemHome.uxdbqv6
Note Note
The SystemNumber can be found as described: Start of the navigation path System
Next navigation step Status Next navigation step SAP System Data Next navigation
step Installation Number End of the navigation path
Similarly, the SystemHome can be found under Start of the navigation path System
Next navigation step Status Next navigation step Database Data Next navigation step
Host End of the navigation path .
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 Note
To identify the host name and port for access URL call transaction SMICM and choose
Start of the navigation path Goto Next navigation step Services End of the
navigation path. Use the HTTPS host name and port displayed in the list. We
recommend to use the message server host.
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.
Maintain the Business Application ID.
Choose Create to maintain a business application ID in MDG hub System
Enter an application name and a description, for example:
sap.com/BusinessApplicationABAP
Enter the business application ID.
Note Note
Note that the business application ID can be found in the counterpart system in the
transaction SOAMANAGER under Start of the navigation path Technical Administration
Next navigation step SAP Client Settings End of the navigation path.
Press Finish to save and activate the system connection.
Note Note
As a result the Identifiable Business Context Reference (IBC reference) for the
counterpart system has been generated automatically. To verify this proceed as
follows:
On the Service Administration Tab follow the link Identifiable Business Context
Reference.
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.
Edit Logon Data for Business Scenario
To create a user account in the MDG hub and the MDG client system carry out the
steps described below in both systems.
Note Note
The back end user has to exist in both systems.
On the Service Administration tab choose Logon Data Management.
On the Maintenance tab choose Create, enter your Logon Data Name and Description
for example SERVICE_USER/Generic Service User and choose Next.
Select User/Password or X.509 as Authentication Method.
Enter the user name that you created earlier in the backend system and choose
Finish to activate the logon data.
Assign Logon Data to Provider IBC Reference
To assign logon data to the IBC Reference of counterpart system in the MDG hub and
the MDG client system carry out the steps described below in both systems.
On the Service Administration tab choose Logon Data Management.
On the Assignments tab choose Create.
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.
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.
Create Integration Scenario Configuration for Point-to-Point Communication using
Service Group
To create the integration scenario configuration for point-to-point communication
using a service group in the MDG hub and MDG client system, carry out the steps
described below in both systems.
Create the integration scenario configuration.
On the Service Administration tab choose Local Integration Scenario Configuration.
Choose Create, enter a name and a description for the business scenario and choose
Next.
Search for service definitions and assign a profile.
Choose Add to search for Service Definition.
In the dialog box search for the Service Definition BUSINESSPARTNERSUITEBULKREPLIC,
mark it in the result list and choose Add to Worklist.
Similarly search for the following service definitions and add them to the
worklist:
Service Definition (Internal Name)
External Name
BUSINESSPARTNERSUITEBULKREPLI1
BusinessPartnerSUITEBulkReplicateConfirmation_In
BUSINESSPARTNERRELATIONSHIPSUI
BusinessPartnerRelationshipSUITEBulkReplicateRequest_In
BUSINESSPARTNERRELATIONSHIPSU1
BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_In
Note Note
To configure 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 MDG hub and MDG client system,
execute step 3 with the values shown below:
Service Definition (Internal Name)
External Name
BUSINESSPARTNERBASICDATABYELEM
BusinessPartnerBasicDataByElementsQueryResponse_In
Assign profile to service definition.
Select all services definitions from the list and choose Assign Profiles.
Select the profile MDG, choose Assign Profile and choose Next.
Select service groups and provider IBC reference.
Choose Add to search for the Service Group.
Enter the service group MDG_BS_SUPPLIERREPLICATEREQ, mark it in the result list and
choose Add to Worklist.
If appropriate, repeat the procedure for the service group
MDG_BS_SUPPLIERREPLICATECONF.
Note Note
To configure 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 MDG hub and MDG client system,
execute step 3 with the values shown below:
Service Group (Internal Name)
Description
MDG_BS_BP_SEARCH
Service Group for BusinessPartnerBasicDataByElementsQueryResponse
Assign business application.
Select all service groups from the list and assign the IBC reference by choosing
Assign IBC Reference.
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.
Choose Finish.
Activate business scenario using the processing of pending tasks
Note Note
Do not activate the business scenario immediately because first the business
scenario in the counterpart system needs to be defined.
After creating the integration scenario configuration in counterpart system choose
Yes to activate the Business Scenario.
Follow the link in the section Pending Tasks.
Choose Process List to process all pending tasks.
Note Note
The activation of the logical ports will not succeed because first the pending
tasks needs to be processed in the counterpart system. For that reason process all
pending tasks in MDG hub system to activate the business scenario on the MDG hub.
Afterwards process all pending tasks in the MDG client where the activation failed.
OPTIONAL: Set Consumer Proxy to Default Port (Transaction SOAMANAGER)
Caution Caution
In case the replication is triggered for PI service instead of P2P communication in
the hub or the client, and the SOA message is displayed in SXMB_MONI instead of
SRT_MONI, you have to set the logical port for the consumer proxy to default in
SOAMANAGER.
In the client of the MDG hub, you have to set the logical port to default for the
consumer proxies:
On the Service Administration tab, choose Web Service Configuration.
Search for object name CO_MDG_BP_RPLCTRQ, and click on the internal name to display
the consumer proxy details.
On the Configurations tab, mark the entry with the desired target system, and
choose Set Log. Port Default.
Repeat the steps above for all entries mentioned in the table below.
Consumer Proxy
External Name
CO_MDG_BP_RPLCTRQ
BusinessPartnerSUITEBulkReplicateRequest_Out
CO_MDG_BP_RELATIONSHIP_OUT
BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out
In the client of the MDG client system, you have to set the logical port to default
for the consumer proxies:
On the Service Administration tab, choose Web Service Configuration.
Search for object name CO_USMD_COMPANYRPLCTNBCO, and click on the internal name to
display the consumer proxy details.
On the Configurations tab, mark the entry with the desired target system, and
choose Set Log. Port Default.
Repeat the steps above for all entries mentioned in the table below.
Consumer Proxy
External Name
CO_MDG_BP_RPLCTCO
BusinessPartnerSUITEBulkReplicateConfirmation_Out
CO_MDG_BP_RELATIONSHIP_CNF_OUT
BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out
