Show TOC

Procedure documentationConfiguring 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.

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.

    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 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

    End of the note.

    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 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, Central 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.

  1. 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.

    1. On the Technical Administration tab choose Profiles.

    2. Choose Create Profile, enter MDG as name, enter a description, and choose Next.

      Note Note

      The profile names should be identical in the SOA manager settings for both MDG hub and MDG client systems.

      End of the note.
    3. Mark User ID/Password and choose Next.

    4. If necessary enter proxy settings and choose Finish to save the settings and activate the profile.

  2. 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.

    1. On the Technical Administration tab, choose SAP Client Settings and then choose Edit.

    2. Enter an Organization Name.

    3. Choose Get from SLD to receive the Business System from the system landscape directory (SLD).

    4. 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.

      End of the note.
    5. Choose Save to receive the Business Application ID.

  3. 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.

    1. On the Technical Administration tab, choose Provider Systems, and choose Create.

    2. 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.

    3. 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 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 .

      End of the note.

      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.

      End of the note.
    4. Enter the Access URL for WSIL and Logon Information under WSIL Services.

    5. Enter User for WSDL and a password for WSDL documents.

    6. Enter the Service User that you have created in the backend system.

    7. Maintain the Business Application ID.

      1. Choose Create to maintain a business application ID in MDG hub System

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

      3. 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.

        End of the note.
      4. Press Finish to save and activate the system connection.

  4. 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.

    End of the note.
    1. On the Service Administration tab choose Logon Data Management.

    2. On the Maintenance tab choose Create, enter your data and choose Next.

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

    4. Enter the user name that you created earlier in the backend system and choose Finish.

  5. 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.

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

    2. On the Assignments tab choose Create.

    3. Use the input help to select a Provider System/Business Application and choose Next.

    4. Select the user name you have entered in step 4 as Logon Data from the drop down list and choose Finish.

  6. 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.

    1. Create a business scenario in the MDG hub system.

      1. On the Service Administration tab choose Business Scenario Configuration.

      2. Choose Create, enter your data and choose Next.

    2. Select service definitions and assign a profile.

      1. Choose Add to search for Service Definition.

      2. In the dialog box search for the Service Definition BUSINESSPARTNERRELATIONSHIPSU1, select it in the result list and choose Add to Worklist.

      3. Similarly search for the following service definitions and add them to the worklist:

        • BUSINESSPARTNERSUITEBULKREPLI1

        • [BUSINESSPARTNERRELATIONSHIPSUI (BusinessPartnerRelationshipSUITEBulkReplicateRequest_In)]

        • [BUSINESSPARTNERSUITEBULKREPLIC (BusinessPartnerSUITEBulkReplicateRequest)]

    3. Assign Profile to service definition.

      1. Select all services definitions from the list and choose Assign Profile.

      2. Select the profile MDG, choose Assign Profile and choose Next.

    4. Select Service Groups and Assign Business Applications in the Provider System (i.e. MDG hub) Service Group:

      1. Choose Add to search for the Service Group, enter the service group MDG_BS_SUPPLIERREPLICATEREQ and choose Go.

      2. Repeat the procedure for the service group [MDG_BS_SUPPLIERREPLICATECONF].

      3. Select MDG_BS_SUPPLIERREPLICATEREQ and [MDG_BS_SUPPLIERREPLICATECONF] from the search result list and choose Add to Work List.

    5. Assign Business Application.

      1. Select the service group from the list and assign it to the business application by choosing Assign Business Application.

      2. Select the provider system and the assigned business application name from the list and choose Assign to Service Group.

      3. Choose Finish.

    6. Create a business scenario in the MDG client system.

      1. On the Service Administration tab choose Business Scenario Configuration.

      2. Choose Create, enter your data and choose Next.

    7. Select service definitions and a assign profile.

      1. Choose Add to search for Service Definition

      2. In the dialog box search for the Service Definition BUSINESSPARTNERRELATIONSHIPSUI, select BusinessPartnerRelationshipSUITEBulkReplicateRequest_In in the result list and choose Add to Worklist.

      3. Similarly search for the following service definitions and add them to the worklist:

        • BUSINESSPARTNERSUITEBULKREPLIC

        • [BUSINESSPARTNERRELATIONSHIPSU1]

        • [BUSINESSPARTNERSUITEBULKREPLI1]

    8. To assign a profile to the service definitions in the MDG client system carry out the steps described above in the corresponding chapter.

    9. Select Service Groups and Assign Business Applications in the Provider System Service Group:

      1. Choose Add to search for the Service Group, enter the service group MDG_BS_SUPPLIERREPLICATECONF and choose Go.

      2. Repeat the procedure for the service group [MDG_BS_SUPPLIERREPLICATEREQ].

      3. Select MDG_BS_SUPPLIERREPLICATECONF and [MDG_BS_SUPPLIERREPLICATEREQ] from the search result list and choose Add to Work List.

    10. To assign a business application in the MDG client system carry out the steps described above in the corresponding chapter.

    Note 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.

    End of the note.