Configuring the SOA Manager for Master Data Governance
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.
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
To activate the business function run the Customizing activity under
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
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:
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 .
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 .
Configuration of the Web Service Runtime
The technical configuration of the web service runtime is done according to SAP note 1043195
.
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: .
The following steps are required to configure the SOA Manager for MDG (transaction SOAMANAGER) in the MDG hub and the MDG client system.
Configure the system for point-to-point communication via enterprise services
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
The profile names should be identical in the SOA manager settings for both MDG hub and MDG client systems.
Mark User ID/Password
and choose Next
.
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
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 in MDG hub and MDG client systems
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
, and choose Create
.
As Name
enter the business system ID of the target system, select the Profile Name
defined in step 1 using the input help and choose Next
.
Enter the SLD Identifier
in for following form: <client>.SystemName.<ABC>.SystemNumber.<Installation Number>.SystemHome.<Host>, for example 416.SystemName.QV6.SystemNumber.0020270862.SystemHome.uxdbqv6
Note
The SystemNumber can be found as described:
Similarly, the SystemHome can be found under .
Note
To identify the host name and port for access URL call transaction SMICM
and choose . Use the HTTPS host name and port displayed in the list. We recommend to use the message server host.
Enter the Access URL for WSIL
and Logon Information under WSIL Services
.
Enter User for WSDL
and a password for WSDL documents.
Enter the Service User
that you have created in the backend system.
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 that the business application ID can be found in the counterpart system in the transaction SOAMANAGER under .
Press Finish
to save and activate the system connection.
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
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 data 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
.
Assign Logon Data to Business Application
To assign logon data to the business application 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 System/Business Application
and choose Next
.
Select the user name you have entered in step 4 as Logon Data
from the drop down list and choose Finish
.
Configure System for Point-to-Point Communication via Service Group
To configure the system for point-to-point communication via service group in the MDG hub system carry out the steps described below.
Service definitions and service groups that need to be configured additionally to run MDG-C with client maintenance scenario are shown in brackets.
Create a business scenario in the MDG hub system.
On the Service Administration
tab choose Business Scenario Configuration
.
Choose Create
, enter your data and choose Next
.
Select service definitions and assign a profile.
Choose Add
to search for Service Definition.
In the dialog box search for the Service Definition
BUSINESSPARTNERRELATIONSHIPSU1, select it in the result list and choose Add to Worklist
.
Similarly search for the following service definitions and add them to the worklist:
BUSINESSPARTNERSUITEBULKREPLI1
[BUSINESSPARTNERRELATIONSHIPSUI (BusinessPartnerRelationshipSUITEBulkReplicateRequest_In)]
[BUSINESSPARTNERSUITEBULKREPLIC (BusinessPartnerSUITEBulkReplicateRequest)]
Assign Profile to service definition.
Select all services definitions from the list and choose Assign Profile
.
Select the profile MDG, choose Assign Profile
and choose Next
.
Select Service Groups and Assign Business Applications in the Provider System (i.e. MDG hub) Service Group:
Choose Add
to search for the Service Group, enter the service group MDG_BS_SUPPLIERREPLICATEREQ and choose Go
.
Repeat the procedure for the service group [MDG_BS_SUPPLIERREPLICATECONF].
Select MDG_BS_SUPPLIERREPLICATEREQ and [MDG_BS_SUPPLIERREPLICATECONF] from the search result list and choose Add to Work List
.
Assign Business Application.
Select the service group from the list and assign it to the business application by choosing Assign Business Application
.
Select the provider system and the assigned business application name from the list and choose Assign to Service Group
.
Choose Finish
.
Create a business scenario in the MDG client system.
On the Service Administration
tab choose Business Scenario Configuration
.
Choose Create
, enter your data and choose Next
.
Select service definitions and a assign profile.
Choose Add
to search for Service Definition
In the dialog box search for the Service Definition
BUSINESSPARTNERRELATIONSHIPSUI, select BusinessPartnerRelationshipSUITEBulkReplicateRequest_In in the result list and choose Add to Worklist
.
Similarly search for the following service definitions and add them to the worklist:
BUSINESSPARTNERSUITEBULKREPLIC
[BUSINESSPARTNERRELATIONSHIPSU1]
[BUSINESSPARTNERSUITEBULKREPLI1]
To assign a profile to the service definitions in the MDG client system carry out the steps described above in the corresponding chapter.
Select Service Groups and Assign Business Applications in the Provider System Service Group:
Choose Add
to search for the Service Group, enter the service group MDG_BS_SUPPLIERREPLICATECONF and choose Go
.
Repeat the procedure for the service group [MDG_BS_SUPPLIERREPLICATEREQ].
Select MDG_BS_SUPPLIERREPLICATECONF and [MDG_BS_SUPPLIERREPLICATEREQ] from the search result list and choose Add to Work List
.
To assign a business application in the MDG client system carry out the steps described above in the corresponding chapter.
Note
To activate the business scenario and changes in the SOA manager business scenario configuration choose Process List
in the Pending Tasks
Page under Service Administration
. Make sure, that all tasks are executed successfully.