Process documentationConfiguring Master Data Governance for Supplier

 

SAP Master Data Governance for Supplier (MDG-S) enables you to govern supplier master data on a hub system and to replicate the supplier master data to a variety of different client systems.

To use SAP Master Data Governance for Supplier, you need to carry out the steps described below.

Prerequisites

Business Function

Before you activate the business functions, ensure that you have the administration authorization for MDG. The required authorization objects are delivered with the authorization role SAP_MDG_ADMIN. In transaction PFCG, we recommend creating a copy of this role and assigning the relevant authorization values. For the authorization object USMD_DM Data Model you need to assign the values for the authorization field USMD_MODEL Data Model and the values for the authorization activity ACTVT Activity (for example 01:Create or generate, or 02: Change).

In the Customizing activity Activate Business Functions (transaction SFW5), you have activated the following business functions:

Note Note

If you intend to distribute data using SOA services, you have to activate the following business functions:

End of the note.

Note Note

If you want to use graphical elements in the MDG-S work center or the Business Context Viewer (BCV), we recommend to activate the following business functions:

For information about the Business Context Viewer, see Business Context Viewer (BCV).

End of the note.

Customizing

Note Note

You can access all MDG specific Customizing using transaction MDGIMG.

End of the note.

Authorization Objects

You have assigned the relevant authorization objects and roles. For more information about authorization objects and roles, see Supplier Master Data Governance (CA-MDG-APP-SUP).

Set Up Workflow

You have defined general settings for SAP Business Workflow in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step Business Management Next navigation step SAP Business Workflow End of the navigation path.

Web Dynpro Applications

You have activated the services for Web Dynpro Applications. For a detailed list of the relevant services, see Services to be Activated for Web Dynpro Applications.

Constraints

  • Master Data Governance for Supplier neither supports time dependency for central data and address usages nor time validity for addresses and bank details. Therefore it cannot run on clients using the SAP Business Partner with time dependency and time validity for other purposes.

  • An activation of Master Data Governance for Supplier on an SRM One Client system as a hub is not supported.

    Note Note

    Make sure that under Start of the navigation path System Next navigation step Status Next navigation step Component information End of the navigation path there is no SRM_SERVER entry.

    End of the note.
  • To distribute business partner data including purchasing organization data from an ERP system into an SRM client system as of SRM 7.01 and higher services are required. Communication via IDOCs is not possible.

Process

You run the settings for this process in Customizing under Start of the navigation path Cross-Application Components Next navigation step Processes and Tools for Enterprise Applications Next navigation step Master Data Governance End of the navigation path.

  1. Activation of the Business Partner (BP) Data Model

    Note Note

    When you activate the MDG_ERP_SUPPLIER_4 business function the system activates the BP data model. Before continuing with system configuration, open transaction SFW5 and check if the activation has been completed by choosing Start of the navigation path Goto Next navigation step Switch Framework Logs End of the navigation path and selecting the corresponding entry with a double click.

    End of the note.
    1. Check whether you can use the data model delivered by SAP for managing your supplier master data with MDG-S.

      If you want to enhance the delivered data model, edit it in the Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Data Modeling Next navigation step Edit Data Model End of the navigation path and activate it again.

      Note Note

      You can select the governance scope at any point after you activate the BP data model. The governance scope determines which fields can be edited and which fields are read-only on the MDG-S UI. To define the governance scope run this Customizing activity: Start of the navigation path Master Data Governance Next navigation step General Settings Next navigation step Process Modeling Next navigation step Define Governance Scope End of the navigation path

      To restore the BP data model to its state in enhancement package 6 for SAP ERP 6.0 run this Customizing activity: Start of the navigation path Master Data Governance Next navigation step Master Data Governance for Business Partner Next navigation step Activate BC Set to Reset Governance Scope End of the navigation path.

      For further information, see Defining a Governance Scope.

      End of the note.
    2. Assign an internal key

      To support internal key assignment, run the activity in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Data Modeling Next navigation step Define Prefixes for Internal Key Assignment End of the navigation path.

      Example: If you create new entries with the following values, all temporary IDs are prefixed with $ and an internal sequence number.

      Data Model = BP, Entity Type = ADDRNO => Prefix $ (where ADDRNO is the address number)

      Data Model = BP, Entity Type = BP_HEADER => Prefix $ (where BP_HEADER is the supplier number)

  2. Activate Business Configuration Set

    Note Note

    MDG-S offers two different groups of change request types that support either the supplier UI or the ERP vendor UI. Only one of these groups should be used. If you intend to use the ERP vendor UI as alternative to the supplier UI proceed as follows:

    1. Run the corresponding activity in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Supplier Next navigation step ERP Vendor UI (Alternative to the Supplier UI) Next navigation step Import Predefined Change Request Types for ERP Vendor UI End of the navigation path.

      Note Note

      To access the BC-Set open the assigned documentation and choose the link.

      End of the note.
    2. Proceed with the ERP vendor UI specific settings described in the corresponding note below.

    End of the note.

    If you intend to use the supplier UI run this activity in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Supplier Next navigation step Import Predefined Change Request Types End of the navigation path.

    Note Note

    To access the BC-Set open the assigned documentation and choose the link.

    End of the note.

    Note Note

    If you want to use the MDG-S work center or side panel or the Business Context Viewer (BCV), you must activate the BC set MDGAF_BCV under Start of the navigation path SAP Menu Next navigation step Tools Next navigation step Customizing Next navigation step Business Configuration Sets Next navigation step Activation of BC Sets End of the navigation path.

    End of the note.
  3. Create Number Range Interval for Cleansing Application

    If you intend to use the business partner cleansing application carry out the following steps in your MDG hub system.

    1. Run transaction COM_CLEAR_NUM, choose Display Intervals (Display Intervals) and make sure that the number range interval 01 is available.

    2. If the number range interval 01 is not available, run transaction COM_CLEAR_NUM, choose Change Intervals (Change Intervals) and create interval 01. For example:

      No

      From No.

      To No.

      01

      0000000001

      1000000000

      Note Note

      For further information, see Cleansing Cases.

      End of the note.
  4. Define Number Ranges for Supplier Account Groups per Target System

    If you intend to override the standard settings, so that you can distribute supplier master data into the target systems, with the numbers of the suppliers in the target system being different from the corresponding numbers in the hub system, run this activity in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Supplier Next navigation step Define Number Ranges for Supplier Account Groups per Target System End of the navigation path.

  5. Configure Change Request Settings

    Depending on your company’s requirements, you might want to adjust and enhance the change request default values.

    The following information describes the minimal settings required for a standard governance process. For more information about each Customizing activity, see the relevant documentation for that Customizing activity.

    1. Review and/or define which statuses the change requests can have, and which processing options are enabled for those statuses. Optionally, you can add new statuses to be used in the change request types defined in the next step.

      For more information, see Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Edit Statuses of Change Requests End of the navigation path.

      The following statuses are required for the SAP standard process:

      Status Value

      Description

      Permitted Processing

      00

      To Be Evaluated

      Change of Object List

      01

      To Be Considered and Approved

      Change of Object List

      02

      Changes to Be Executed

      Execution of Changes

      03

      To Be Revised

      Change of Object List

      04

      Final Check to Be Performed

      No Processing

      05

      Final Check Approved

      No Processing

      06

      Final Check Rejected

      No Processing

      07

      Activation Failed

      No Processing

      08

      Approved, to Be Replicated

      No Processing

      09

      Dependent Data to Be Processed/Approved

      Execution of Changes

      10

      To Revise: Perform Changes

      Execution of Changes

      11

      Process Errors After Activation

      Execution of Changes

      12

      Approved, Contact Person to be Processed

      No Processing

      99

      No Status Set

      No Processing

    2. Check in the Customizing that the following business activities are in your system under Start of the navigation path Master Data Governance Next navigation step General Settings Next navigation step Process Modeling Next navigation step Business Activities Next navigation step Create Business Activity End of the navigation path and make sure that they are assigned to the default data model BP.

      • SUP1 (Create Supplier)

      • SUP2 (Process Supplier)

      • SUP3 (Display Supplier)

      • SUP5 (Block/Unblock Supplier)

      • SUP6 (Mark Supplier for Deletion)

      • BPPC (Business Partner Data Cleansing)

      • BPPH (Process Business Partner Hierarchies)

      • BPPL (Business Partner Initial Load)

      • BPPM (Business Partner Mass Maintenance)

    3. Create new change request types for data model BP, or validate after import using business configuration set (BC Set).

      For more information, see Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Create Change Request Type End of the navigation path.

      • The following table shows the change request types for data model BP of the supplier UI. Only the relevant columns are included.

        Change Request Type

        Data Model

        Description

        Single Object

        Main Entity Type

        Workflow

        SUPPL1P1

        BP

        Create Supplier

        Yes

        BP_HEADER

        WS54300005

        SUPPL2P1

        BP

        Process Supplier

        Yes

        BP_HEADER

        WS54300007

        SUPPL5P1

        BP

        Block/Unblock Supplier

        Yes

        BP_HEADER

        WS60800059

        SUPPL6P1

        BP

        Mark Supplier for Deletion

        Yes

        BP_HEADER

        WS60800068

        BPHP1

        BP

        Process Business Partner Hierarchies

        No

        BP_HEADER

        WS60800095

        BPLP1

        BP

        Business Partner Initial Load

        No

        BP_HEADER

        WS72100006

        BPMP1

        BP

        Business Partner Mass Maintenance

        No

        BP_HEADER

        WS60800095

        BPCC2

        BP

        Process Business Partner Cleansing Case

        Yes

        BP_HEADER

        WS60800086

        The following settings should exist in the substructures of the change request types:

        Substructure of Change Request Types:

        • SUPPL1P1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

          • Business Activity: SUP1

        • SUPPL2P1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

          • Business Activity: SUP2

        • SUPPL5P1:

          • Entity type: BP_HEADER: Msg. Output = Standard

          • Business Activity: SUP5

        • SUPPL6P1:

          • Entity type: BP_HEADER: Msg. Output = Standard

          • Business Activity: SUP6

        • BPHP1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_HRCHY: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

            • BP_SUBHRY: Msg. Output = Standard

          • Business Activity: BPPH

        • BPLP1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_HRCHY: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

            • BP_SUBHRY: Msg. Output = Standard

          • Business Activity: BPPL

        • BPMP1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_HRCHY: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

            • BP_SUBHRY: Msg. Output = Standard

          • Business Activity: BPPM

        • BPCC2

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

          • Business Activity: BPPC

      Note Note

      In an optional step you can specify Service Level Agreement for all the mentioned change request types.

      End of the note.

      Note Note

      ERP Vendor UI Specific Settings

      • If you use the ERP vendor UI, check that the following business activities are in your system:

        • VLP1 (Create Supplier)

        • VLP2 (Process Supplier)

        • VLP3 (Display Supplier)

        • VLP5 (Block/Unblock Supplier)

        • VLP6 (Mark Supplier for Deletion)

        • BPPH (Process Business Partner Hierarchies)

        • BPPL (Business Partner Initial Load)

        • BPPM (Business Partner Mass Maintenance)

      • The following table shows the change request types for data model BP of the ERP vendor UI. Only the relevant columns are included.

        Change Request Type

        Data Model

        Description

        Single Object

        Main Entity Type

        Workflow

        VENDR01

        BP

        Create Supplier

        Yes

        BP_HEADER

        WS54300005

        VENDR02

        BP

        Process Supplier

        Yes

        BP_HEADER

        WS54300007

        VENDR05

        BP

        Block/Unblock Supplier

        Yes

        BP_HEADER

        WS60800059

        VENDR06

        BP

        Mark Supplier for Deletion

        Yes

        BP_HEADER

        WS60800068

        VENDL1

        BP

        Lean Vendor Creation

        Yes

        BP_HEADER

        WS54300013

        BPHP1

        BP

        Process Business Partner Hierarchies

        No

        BP_HEADER

        WS60800095

        BPLP1

        BP

        Business Partner Initial Load

        No

        BP_HEADER

        WS72100006

        BPMP1

        BP

        Business Partner Mass Maintenance

        No

        BP_HEADER

        WS60800095

        The following settings should exist in the substructures of the change request types:

        Substructure of Change Request Types:

        • VENDR01:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

          • Business Activity: VLP1

        • VENDR02:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

          • Business Activity: VLP2

        • VENDR05:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

          • Business Activity: VLP5

        • VENDR06:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

          • Business Activity: VLP6

        • VENDL1

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

          • Business Activity: VLP1

          Note Note

          Quite often many users are supposed to request the creation of new supplier master data. As these users might not be familiar with MDG, they need a UI that is easy to use, even without training. To fulfill this requirement MDG-S provides the lean request UI as a model.

          The lean request UI is based on the change request type VENDL1. It provides a basic subset of input fields and therefore offers a simplified way to create supplier master data. In a subsequent step, another user can change the data, can enter further data using the complete set of input fields and finally can approve the change request.

          To use the lean request UI the menu role SAP_MDGS_LVC_MENU_03, Master Data Governance for Supplier: Lean Requester Menu is required.

          End of the note.
        • BPHP1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_HRCHY: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

            • BP_SUBHRY: Msg. Output = Standard

          • Business Activity: BPPH

        • BPLP1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_HRCHY: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

            • BP_SUBHRY: Msg. Output = Standard

          • Business Activity: BPPL

        • BPMP1:

          • Entity types:

            • ADDRNO: Msg. Output = Standard

            • BP_HEADER: Msg. Output = Standard

            • BP_HRCHY: Msg. Output = Standard

            • BP_REL: Msg. Output = Standard

            • BP_SUBHRY: Msg. Output = Standard

          • Business Activity: BPPM

        For more information about the ERP Vendor UI, see Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Supplier Next navigation step ERP Vendor UI (Alternative to the Supplier UI) End of the navigation path.

      End of the note.
    4. Import Predefined Field Modification Criteria for Transaction BP Using MDG-S

      To Run this activity in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Business Partner Next navigation step Import Predefined Field Modification Criteria for Transaction BP Using MDG-S End of the navigation path.

    5. Optionally, you can define priorities, reasons, or rejection reasons for change requests. You can enter codes and a short description to tag or classify your change requests. These codes can be used later for change request analytics (process quality analysis). They also can be used to influence the workflow-driven processes. For example, depending on the priority of a change request, you can mark it for special processing.

      For more information, see Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Define Priorities for Change Requests / Define Reasons for Change Requests / Define Rejection Reasons for Change Requests End of the navigation path.

    Note Note

    You can apply system settings that allow you to monitor in detail how effectively your organization processes change requests. For details, see Enabling Detailed Analysis of Change Requests.

    End of the note.
  6. Set Up the Workflow

    This section describes how to make the Customizing settings required to run the workflow for the approval process in MDG-S.

    You define the workflow settings in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow. End of the navigation path.

    1. Activate type linkage

      To activate the type linkage, run the following activity in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow Next navigation step Activate Type Linkage End of the navigation path.

      Ensure, that one object type BUS2250 has the following settings:

      • Event: CREATED

      • Receiver Type: (blank)

      • Type linkage active: yes

      • Enable event queue: deactivated

      The type linkage indicator must not be active for all other receiver types of object type BUS2250 and event CREATED. This receiver type is defined via the receiver type function module USMD_WF_RECEIVER_TYPE. Make sure that receiver function module SWW_WI_CREATE_VIA_EVENT_IBF is entered.

      To enter the receiver type function module or if you need to change the settings, mark the according line in the table and chooseStart of the navigation path Goto Next navigation step Details End of the navigation path.

    2. Configure workflow tasks.

      To configure workflow tasks, run the following activity in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow Next navigation step Configure Workflow Tasks End of the navigation path.

      1. Go to application component CA-MDG-AF and choose Assign Agents.

      2. All activities (denoted by TS*) that are not set as Background Task need to be set to General Task. To do so, select the activity, choose Attributes, and change to General Task.

      3. Repeat the procedure for all non-background activities within the CA-MDG-APP-BP and CA-MDG-APP-SUP application components.

    3. Check number of workflow steps

      1. To define the workflow steps for the workflows assigned to your change request types (which shall be assigned to a processor), run the following activity in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow Next navigation step Other MDG Workflows Next navigation step Define Change Request Step Numbers End of the navigation path.

      2. If you use the change request types delivered with MDG-S, the following workflow steps are delivered:

        • WS54300005: Step 0, 1, 4, 5, 6, 7

        • WS54300007: Step 0, 1, 4, 5

        • WS60800059: Step 0, 1, 2, 3

        • WS60800068: Step 0, 1, 2, 3

        • WS60800095: Step 0, 1, 2, 3, 4, 5

        • WS72100006: Step 0, 1, 2, 3, 4, 5

    4. Create organizational unit or change staff assignments for organizational unit

      Create an organizational unit with transaction PPOCW or change staff assignments for an organizational unit with transaction PPOME. Users who will process the workflow steps have to be assigned to this organizational unit.

    5. Check or set up the business rule framework plus (BRFplus)

      1. To check the business rule framework plus (BRFplus) run the following activity in Customizing for Master Data Governance Start of the navigation path Master Data Governance for Supplier Next navigation step Workflow Next navigation step Assign Processor to Workflow Step Number in BRFplus for Supplier End of the navigation path.

        Note Note

        If the system does not contain the Customizing application MDG_BS_ECC_SUPPLIER_WF_CUSTM export it from client 000 using transaction SCC1.

        End of the note.

        Note Note

        To copy the content of the decision table GET_AGENT, do the following:

        Prerequisite: In transaction BRF+ under Personalize the User Mode Expert is selected.

        1. Run transaction BRF+ in the source client and search for Name MDG_BS_ECC_SUPPLIER_WF_CUSTM.

        2. In the search result list expand Start of the navigation path MDG_BS_ECC_SUPPLIER_WF_CUSTM Next navigation step Expression Next navigation step Decision Table Next navigation step GET_AGENT End of the navigation path and open GET_AGENT with a double click.

        3. Choose Start of the navigation path Additional Actions Next navigation step Export to Excel End of the navigation path to download the data.

        4. In your target client repeat the steps 1 and 2 to open the decision table GET_AGENT.

        5. Choose Start of the navigation path Additional Actions Next navigation step Import from Excel End of the navigation path to upload the data.

        End of the note.
      2. To assign processors to workflow step numbers run the following activity in Customizing for Master Data Governance Start of the navigation path Master Data Governance for Supplier Next navigation step Workflow Next navigation step Assign Processor to Workflow Step Number in BRFplus for Supplier End of the navigation path

        Assign processors, for example users or organizational units , for all change request types and their created workflow steps.

        The following table shows an example of the change request types and their workflow steps.

        Change Request Type

        Workflow Step Number

        Object Type

        Object ID

        SUPPL1P1

        01 Approval

        O

        OrgUnit-ID

        SUPPL1P1

        04 Revision after Rejection

        O

        OrgUnit-ID

        SUPPL1P1

        05 Subworkflow: Data Maintenance

        O

        OrgUnit-ID

        SUPPL1P1

        06 Subworkflow: Approval

        O

        OrgUnit-ID

        SUPPL1P1

        07 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        SUPPL2P1

        01 Approval

        O

        OrgUnit-ID

        SUPPL2P1

        04 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        SUPPL2P1

        05 Revision after Rejection

        O

        OrgUnit-ID

        SUPPL5P1

        01 Approval

        O

        OrgUnit-ID

        SUPPL5P1

        02 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        SUPPL5P1

        03 Revision after Rejection

        O

        OrgUnit-ID

        SUPPL6P1

        01 Approval

        O

        OrgUnit-ID

        SUPPL6P1

        02 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        SUPPL6P1

        03 Revision after Rejection

        O

        OrgUnit-ID

        BPLP1

        01 Processing

        O

        OrgUnit-ID

        BPLP1

        02 Approval

        O

        OrgUnit-ID

        BPLP1

        03 Revision after Rejection

        O

        OrgUnit-ID

        BPLP1

        04 Revision after Rejection

        O

        OrgUnit-ID

        BPLP1

        05 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        BPMP1

        01 Processing

        O

        OrgUnit-ID

        BPMP1

        02 Approval

        O

        OrgUnit-ID

        BPMP1

        03 Revision after Rejection

        O

        OrgUnit-ID

        BPMP1

        04 Revision after Rejection

        O

        OrgUnit-ID

        BPMP1

        05 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        BPHP1

        01 Processing

        O

        OrgUnit-ID

        BPHP1

        02 Approval

        O

        OrgUnit-ID

        BPHP1

        03 Revision after Rejection

        O

        OrgUnit-ID

        BPHP1

        04 Revision after Rejection

        O

        OrgUnit-ID

        BPHP1

        05 Decision: Activation Despite Discrepancy

        O

        OrgUnit-ID

        Note Note

        If you intend to use MDG-S and MDG-C in parallel and you already have assigned the processors to the change request types for MDG-C, then nevertheless the assignment of processors to the change request types BPLP1, BPMP1, and BPHP1 has to be done in the Customizing activity Assign Processor to Workflow Step Number in BRFplus for Supplier as described in this document.

        End of the note.
  7. Set Up the Rule-Based Workflow

    Note Note

    This document describes an example for a preconfigured Rule-Based Workflow for the Process Business Partner Cleansing Case.

    End of the note.

    MDG-S uses advanced workflow capabilities by combining the SAP Business Workflow with the SAP Business Rule Framework plus (BRFplus) tool. This section describes how to activate and load the necessary settings for BRFplus.

    To use the predefined change request type BPCC2 run the following Customizing activity Start of the navigation path Master Data Governance Next navigation step Master Data Governance for Supplier Next navigation step Import Predefined Change Request Types End of the navigation path and activate the BC set CA-MDG-APP-SUP_VC_USMD110_C04.

    Check that the steps for Rule-Based Workflow are imported by the BC-Set by running the following activity in Customizing: Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow Next navigation step Rule-based Workflow Next navigation step Define Change Request Steps for Rule-Based Workflow End of the navigation path.

    The following are the default steps required for the predefined change request type BPCC2.

    Type of Chg. Request

    CR Step

    Keys

    Validation

    Description

    BPCC2

    0

    Processing

    BPCC2

    90

    X

    Final Check

    BPCC2

    91

    Activation

    BPCC2

    92

    Revision

    BPCC2

    95

    Revision Processing

    BPCC2

    96

    Processing After Activation Error

    BPCC2

    99

    Complete

    To check that the predefined change request type exists see the Customizing activity Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Change Requests Next navigation step Create Change Request Type End of the navigation path.

    To check that the link between the predefined change request type and the generated BRF+ application ID exists, run transaction SE16, enter the table name USMD213C_SSW and look for the following entries:

    USMD_CREQ_TYPE

    USMD_BRFP_APP_ID

    BPCC2

    005056AC02D81ED2AC971CAB3C1DC848

    Check that the BRF+ catalogs (inclusive application, functions, decision tables with content) for the predefined change request type are in the client.

    Due to technical restrictions further settings currently cannot be included in the BC set processing therefore the following steps need to be executed manually:

    1. Run transaction BRF+.

    2. On the Catalog tab choose Select Catalog.

    3. Enter the search criteria: Select the Object Type Catalog and as Name enter USMD_SSW_CATA_BPCC2.

    Note Note

    If the catalog does not exist in your client, export the catalog from the client 000 using transaction SCC1.

    The import will also include the values in the three pre-delivered decision tables. For testing the standard workflow configuration you have to start the workflow now.

    End of the note.

    Maintain your content in the decision tables, reflecting your governance process. You can use the pre-delivered SAP content as a starting point.

    To maintain your content either run transaction USMD_SSW_RULE and select the correponding change request type or run the Customizing activity Start of the navigation path General Settings Next navigation step Process Modeling Next navigation step Workflow Next navigation step Rule-Based Workflow Next navigation step Configure Rule-Based Workflow End of the navigation path.

    Note Note

    If you extend the BRFplus decision tables make sure that the status of the final step is set to 05 Final Check Approved or 06 Final Check Rejected.

    End of the note.

    The following are the minimal settings for the relevant change request types.

    • DT_SINGLE_VAL_BPCC2 (Single value decision table)

    • DT_NON_USER_AGT_GRP_BPCC2 (Non-user agend decision table)

    • DT_USER_AGT_GRP_BPCC2 (User agent decision table)

    DT_NON_USER_AGT_GRP_BPCC2 and DT_SINGLE_VAL_BPCC2 contain the automated steps and follow-up logic used by the BRFplus. The follow-up logic can either result in an automated step or in a user task that will be made visible as a workflow.

    The users involved in the Master Data Governance process need to be included in table DT_USER_AGT_GRP_BPCC2 so that they can receive and execute the workflow tasks. Maintain agents (for example the users or organizations in the Portal Content and Portal Role Assignment sections of this document) for all change request types and their associated workflow steps. Each condition alias that appears in the DT_SINGLE_VAL_BPCC2 table needs at least one processor, either automatic or user (group). Therefore, for all non-automated steps at least one entry needs to exist in DT_USER_AGT_GRP_BPCC2.

    For further details on the workflow concepts, see Rule Based Workflow for Business Partner. You can adopt the settings described in that document for BP1P1 to BPCC2.

    The following step types are pre-delivered by SAP:

    Step Type

    Short Description

    Actions

    1

    Check Change Request

    01 Agree; 02 Disagree

    2

    Approve Change Request

    03 Approve; 04 Reject

    3

    Process Change Request

    05 Finalize Processing; 06 Send for Revision

    4

    Revise Change Request

    07 Resubmit; 08 Withdraw

    5

    Activate Change Request

    09 Activate; 10 Send for Revision

    6

    Approve Change Request (Without Rejection)

    03 Approve; 06 Send for Revision

    7

    Revise Change Request (Without Rejection)

    05 Finalize Processing

    8

    Activate Change Request

    09 Activate; 04 Reject

    The following agent types exist:

    User Agent Type

    Short Description

    US

    User

    O

    Organizational Unit

    C

    Job

    S

    Position

    AG

    Role

    SU

    Special User (Initiator/Last-Step User)

    The following is the standard content pre-delivered by SAP:

    DT_SINGLE_VAL_BPCC2

    Previous Change Request Step

    (PREVIOUS_STEP)

    Previous Action

    (PREVIOUS_ACTION)

    Condition Alias

    (COND_ALIAS)

    New Change Request Step

    (NEW_STEP)

    New Change Request Status

    (NEW_CR_STATUS)

    00 (Processing)

    No value

    1

    90 (Final Check)

    01 (To Be Considered and Approved)

    90 (Final Check)

    03 (Approve)

    2

    91 ( Activation)

    90 (Final Check)

    04 (Reject)

    3

    95 (Revision Processing)

    10 (To Revise: Perform Changes)

    91 (Activation)

    31 (Activation Successful)

    4

    99 (Complete)

    05 (Final Check Approved)

    91 (Activation)

    <>31 (Activation Successful)

    5

    96 (Processing After Activation Error)

    11 (Process Errors After Activation)

    92 (Revision)

    No value

    6

    99 (Complete)

    06 (Final Check Rejected)

    95 (Revision Processing)

    07 (Resubmit)

    1

    90 (Final Check)

    01 (To Be Considered and Approved)

    95 (Revision Processing)

    08 (Withdraw)

    8

    92 (Revision)

    96 (Processing After Activation Error

    09 (Activate)

    9

    91 (Activation)

    96 (Processing After Activation Error

    10 (Send for Revision)

    3

    95 (Revision Processing)

    10 (To Revise: Perform Changes)

    DT_USER_AGT_GRP_BPCC2

    Condition Alias

    (COND_ALIAS)

    User Agt Grp No.

    (AGENT_GROUP)

    Step Type

    (STEP_TYPE)

    User Agent Type

    (USER_TYPE)

    User Agent Value

    (USER_VALUE)

    1

    001

    2 (Approve Change Request)

    SU (Special User (Initiator/Last-Step User))

    INIT

    3

    001

    4 (Revise Change Request)

    SU (Special User (Initiator/Last-Step User))

    INIT

    5

    001

    5 (Activate Change Request)

    SU (Special User (Initiator/Last-Step User))

    INIT

    DT_NON_USER_AGT_GRP_BPCC2

    Condition Alias

    COND_ALIAS

    Agent Group

    AGENT_GROUP

    Process Pattern

    PROCESS_PATTERN

    2

    001

    05 (Activation (Do Not Bypass Snapshot))

    4;6

    001

    99 (Complete (Sub-)Workflow)

    8

    001

    08 (Roll back change request)

    9

    001

    06 (Activation (Bypass Snapshot))

    Notes

    • It is necessary to activate your new entries for each of the three decision tables.

    • In the preconfigured delivery for all step types the value for user agent type is SU (Special User) and the user agent value is INIT (Initiator). Therefore testing is immediately possible.

    • The quickest way to allow additional users to participate for example in the approve step for testing purposes is to copy the default entry for step type 2 into the DT_USER_AGT_GRP_BPCC2 table and change the entries as follows:

      • User Type: AG (Role)

      • User Value: SAP_MDGS_MENU_04 (The MDG-S role of PFCG/SU01)

    • If the system cannot find a processor for your change requests check the background steps of the change requests workflow log to see if a work item with the description Set Status x for Change Request y is in process or in error. If this is the case regenerate the authorization profile of SAP_ALL or include USMD* authorization objects into the authorization for the user WF-Batch.

    • Choosing the process pattern 06 Activation (Bypass Snapshot) means that the business partner will be activated, even if the business partner record was changed in the backend system since the change request was created. Any backend changes are lost upon activation. You can adjust this behavior with SAP Note 1797009Information published on SAP site. Implementing this note means that the system only overwrites changes to entities present in the change request rather than all entities.

  8. Show Master Data Governance for Supplier 6.1 Specific UIBBs

    By default the user interface building blocks (UIBB) for the entities delivered with the business function Master Data Governance for Supplier 6.1 are not shown after activation of the business function.

    To show these user interface building blocks proceed as follows:

    Note Note

    Depending on whether you use the supplier UI or the ERP vendor UI carry out the corresponding procedure.

    End of the note.

    Prerequisites:

    • In transaction SU01 on the Parameters tab the Set/Get parameter FPM_CONFIG_EXPERT is set to the value A.

    • The authorization objects S_DEVELOP and S_WDR_P13N are assigned to your user.

    Show specific UIBBs for the supplier UI

    1. Run transaction NWBC, enter the role SAP_MDGS_MENU_04 and choose Start NetWeaver Business Client for HTML.

    2. Choose Search Supplier.

    3. Choose Customize Page (Customize Page).

      Note Note

      If an error message is displayed concerning missing object component Customizing proceed as follows:

      1. Choose New.

      2. In the Create Customizing dialog box enter a description and choose OK.

      3. In the Select Transport Request dialog box choose OK.

      End of the note.
    4. Mark Main Page BS_BP_OVP.

    5. On the Overview Page Schema tab, choose Expand Node (Expand Node) in front of Section: BP_SECTION to open the UIBB structure.

    6. Mark UIBB: Relationship BS_BP_RELATIONS.

    7. In the Hidden Element field in the Attributes of UIBB section select Visible and choose Save.

    8. Repeat the procedure as of step 4 using the following values:

      • Edit Page BS_SP_GENERAL_DATA

        • UIBB: ERP Vendor: Sub-Ranges BS_SP_SUBRANGES

      • Edit Page BS_SP_COMPANY_CODE

        • UIBB: ERP Vendor Company Code: Extended Withholding Tax Types BS_SP_WITHHOLDING_TAXES

        • UIBB: ERP Vendor Company Code: Dunning Areas BS_SP_DUNNING_AREAS

      • Edit Page BS_SP_PURCH_ORG

        • UIBB: ERP Vendor Purchasing Organization: Different Purchasing Data BS_SP_PURCH2_ORGS

        • UIBB: ERP Vendor Purchasing Organization: Partner Functions BS_SP_FUNCTIONS

    9. As a final step on the Search Supplier screen choose Personalize (Personalize) and on the Personalize dialog box choose Reset to Default.

    Note Note

    To show the corresponding UIBBs within Block and Mark for Deletion change requests, mark an existing supplier in the search result list, choose Block or Mark for Deletion and proceed as described above as of step number 3.

    End of the note.

    Show specific UIBBs for the ERP vendor UI

    1. Run transaction NWBC, enter the role SAP_MDGS_MENU_04 and choose Start NetWeaver Business Client for HTML.

    2. Choose Search Vendor.

    3. Choose Customize Page (Customize Page).

      Note Note

      If an error message is displayed concerning missing object component Customizing proceed as follows:

      1. Choose New.

      2. In the Create Customizing dialog box enter a description and choose OK.

      3. In the Select Transport Request dialog box choose OK.

      End of the note.
    4. Mark Main Page BS_BP_OVP.

    5. On the Overview Page Schema tab, choose Expand Node (Expand Node) in front of Section: BP_SECTION to open the UIBB structure.

    6. Mark UIBB: ERP Vendor: Sub-Ranges BS_SP_SUBRANGES.

    7. In the Hidden Element field in the Attributes of UIBB section select Visible and choose Save.

    8. Repeat the procedure as of step 4 using the following values:

      • Edit Page BS_SP_COMPANY_CODE

        • UIBB: ERP Vendor Company Code: Withholding Tax BS_SP_COMPANY_CODE_WITHHOLDING

        • UIBB: ERP Vendor Company Code: Dunning Areas BS_SP_DUNNING_AREAS

      • Edit Page BS_SP_PURCH_ORG

        • UIBB: ERP Vendor Purchasing Organization: Different Purchasing Data BS_SP_PURCH2_ORGS

        • UIBB: ERP Vendor Purchasing Organization: Partner Functions BS_SP_FUNCTIONS

    9. As a final step on the Search Vendor screen choose Personalize (Personalize) and on the Personalize dialog box choose Reset to Default.

    Note Note

    To show the corresponding UIBBs within Block and Mark for Deletion change requests, mark an existing vendor in the search result list, choose Block or Mark for Deletion and proceed as described above as of step number 3.

    End of the note.

    Show specific UIBBs for the UI configuration BS_OVP_BP_ALL

    1. Run transaction SE80, select the package MDG_BS_BP_BOLUI.

    2. Depending on your SAP NetWeaver release choose:

      • SAP NetWeaver 7.31: Start of the navigation path Web Dynpro Next navigation step Web Dynpro Applicat. Next navigation step BS_OVP_BP Next navigation step Applic. Configurations Next navigation step BS_OVP_BP_ALL End of the navigation path

      • SAP NetWeaver 7.40: Start of the navigation path Web Dynpro Next navigation step FPM Applications. Next navigation step BS_OVP_BP Next navigation step FPM Application Configurations Next navigation step BS_OVP_BP_ALL End of the navigation path

    3. Double-click BS_OVP_BP_ALL and choose Test/Execute.

    4. On the Search Business Partner screen, choose Customize Page (Customize Page).

      Note Note

      If an error message is displayed concerning missing object component Customizing proceed as follows:

      1. Choose New.

      2. In the Create Customizing dialog box enter a description and choose OK.

      3. In the Select Transport Request dialog box choose OK.

      End of the note.
    5. Mark Main Page BS_BP_OVP.

    6. On the Overview Page Schema tab, choose Expand Node (Expand Node) in front of Section: BP_BP_OVP to open the UIBB structure.

    7. Mark UIBB: Relationship BS_BP_RELATIONS.

    8. In the Hidden Element field in the Attributes of UIBB section select Visible and choose Save.

    9. Repeat the procedure as of step 5 using the following values:

      • Edit Page BS_SP_MLT_ASSIGNMENT

        • UIBB: ERP Vendor: Sub-Ranges BS_SP_SUBRANGES

      • Edit Page BS_SP_COMPANY_CODE S

        • UIBB: ERP Vendor Company Code: Extended Witholding Tax Types BS_SP_WITHHOLDING_TAXE

        • UIBB: ERP Vendor Company Code: Dunning Areas BS_SP_DUNNING_AREAS

      • Edit Page BS_SP_PURCH_ORG

        • UIBB: ERP Vendor Purchasing Organization: Different Purchasing Data BS_SP_PURCH2_ORGS

        • UIBB: ERP Vendor Purchasing Organization: Partner Functions BS_SP_FUNCTIONS

    10. As a final step on the Search Business Partner screen choose Personalize (Personalize) and on the Personalize dialog box choose Reset to Default.

  9. Set Up Business Partner

    You set up the business partner Customizing and check number ranges and groupings that are mandatory for MDG-S.

    In addition if you need to set up or define settings for SAP Business Partner, run the following activity in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Business Partner Next navigation step Set up Business Partner End of the navigation path.

    Note Note

    Make sure your Customizing for the object Business Partner is harmonized throughout your hub and your client systems.

    End of the note.
  10. Set Up Vendor

    You set up or check the Customizing for the vendor master in the MDG hub system and for the relevant client systems.

    If you need to set up the vendor master, perform the following activity in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Supplier Next navigation step Integration with Vendor Master in ERP Next navigation step Set up Vendor Master for Master Data Governance for Supplier End of the navigation path.

    Note Note

    Make sure your Customizing for the object Vendor is harmonized throughout your hub and your client systems.

    End of the note.
  11. Set Up Customer-Vendor Integration

    You define the settings for customer-vendor integration in Customizing for Master Data Governance under Start of the navigation path Master Data Governance for Supplier Next navigation step Integration with Vendor Master in ERP Next navigation step Set up Customer Vendor Integration for MDG for Supplier End of the navigation path.

  12. Replicate Data

    Replication of master data from the MDG hub to the connected systems and clients can be done using the following methods:

    Note Note

    For information on how to replicate data to an SRM system, see Configuration for Data Replication to SRM Systems.

    End of the note.
  13. Define Value Mapping

    If required, you can define value mapping for elements such as, BP relationship role code and others in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Value Mapping End of the navigation path.

    The fields of the supplier record for which a value mapping can be defined, are stored in the table MDGV_ELEMENT.

  14. Define Key Mapping

    If you are working with multiple connected systems and did not consolidate the supplier keys during the initial load phase, key mapping may be required. You can define the system-specific mappings for the key value of the supplier in Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Key Mapping End of the navigation path.

  15. Search and Duplicate Check

    To configure the search and the duplicate check run the Customizing-activities under Start of the navigation path Master Data Governance Next navigation step General Settings Next navigation step Data Quality and Search Next navigation step Search and Duplicate Check End of the navigation path.

  16. Data Quality Services

    You have the option to integrate SAP Master Data Governance with data quality management solutions, such as SAP Analytics Data Quality Management, including address validation, duplicate check, and data enrichment.

    While creating new master data records, for example business partners, you can use the Web Dynpro application MDG_ADDR_CHECK_TEST (application configuration MDG_ADDR_CHECK_TEST_AC) to check that the entered address is valid and complete. This function supports you in detecting inconsistencies. It also helps you to improve the quality and completeness of your master data records with standardized address information on country and region codes, postal codes, as well as street names and house numbers.

    Alternatively, you can also integrate third-party solutions that offer, for example, updating of databases, change of address service, address enrichment, or data cleansing.

    For more information, see Validation and Enrichment.

    For more information about data quality, see SAP Help Portal at http://help.sap.comInformation published on SAP site Start of the navigation path Analytics Next navigation step All Products End of the navigation path.

  17. Set Up Embedded Search

    Prerequisites:

    • TREX is setup and configured for the Embedded Search in the system before enabling the master data object for Embedded Search.

      For further information how to setup TREX, see Creating a Connection Between Embedded Search and TREX/BWA.

    • You are authorized to access the Connector Administration Cockpit (Transaction ESH_COCKPIT).

    Procedure:

    Once TREX is configured, follow the steps mentioned below to enable the master data object for Embedded Search:

    Note Note

    The search object connector template for business partner/supplier (MDG_BUSINESS_PARTNER) contains information about entities and attributes and about the relationship among entities as defined in the data model.

    End of the note.

    Configure the search connector using transaction ESH_COCKPIT. For further information, see Using the Connector Administration Cockpit.

    Create a search connector for the corresponding embedded search template (MDG_BUSINESS_PARTNER).

    • After creating the search connector, an initial extraction of data for the connector is possible, choosing Start of the navigation path Actions Next navigation step Schedule Indexing End of the navigation path. This will select all data in database tables corresponding to a master data object.

    • Due to data changes after the initial extraction the embedded search index needs to be updated. To set this option choose Start of the navigation path Actions Next navigation step Schedule Indexing End of the navigation path and select Real-time Indexing.

  18. Set up SAP HANA-Based Search

    If you want to use the SAP HANA-based search, follow the instructions given in the document Configuring SAP HANA-Based Search for MDG.

  19. Choose the UI environment you want to use to run SAP Master Data Governance

    You can run SAP Master Data Governance in the environments of the SAP NetWeaver Business Client or in the environment of the SAP NetWeaver Portal.

    SAP NetWeaver Business Client

    If you are running SAP Master Data Governance on the SAP NetWeaver Business Client (and not on the SAP NetWeaver Portal), you need to configure the role for the Business Client in the SAP ERP system. To do so, perform the following steps in the SAP ERP system:

    1. On the SAP Easy Access screen, choose Start of the navigation path Tools Next navigation step Administration Next navigation step User Maintenance Next navigation step Role Administration Next navigation step Roles End of the navigation path and choose menu role SAP_MDGS_MENU_04. Alternatively, use transaction PFCG (Role Maintenance).

      Assign the menu role SAP_MDGS_MENU_04 to your users.

      SAP_MDGS_MENU_04, Master Data Governance for Supplier: Menu

      Note Note

      If you use the ERP vendor UI assign the role SAP_MDGS_VL_MENU_04, Master Data Governance for Supplier (ERP Vendor UI): Menu.

      End of the note.
    2. On the SAP Easy Access screen, choose Start of the navigation path Tools Next navigation step Administration Next navigation step User Maintenance Next navigation step Users End of the navigation path. Alternatively use transaction SU01 (User Maintenance) and assign the authorization role or the name of the copied role for the application to the master data governance user.

    The following authorization roles are delivered:

    Run transaction PFCG to verify the setting of the authorization objects within the roles and adapt the authorizations to your organizational structures.

    SAP NetWeaver Portal

    The SAP NetWeaver Portal content for MDG-S is derived directly from the system PFCG roles. To create SAP NetWeaver Portal roles for your users, you must log on to your portal and upload the content information from your back-end system PFCG roles.

    To upload your portal content to the portal, do the following:

    1. Set up your SAP NetWeaver Portal for MDG.

    2. In the Content Administration work center choose Start of the navigation path Portal Content Managment Next navigation step Portal Content End of the navigation path and select a portal content folder to upload the portal content.

    3. Right-click on the folder and choose Start of the navigation path New Next navigation step Role Next navigation step Role from Back End End of the navigation path.

    4. Select the system and client (or the connected system alias) you want to upload the role information from. This should be your hub system.

    5. From the list displayed select the PFCG role SAP_MDGS_MENU_04 and begin the upload.

    Once the MDG portal roles have been uploaded, you must assign them as follows:

    1. Log on to the portal.

    2. Choose Delegated User Administration.

    3. Enter your User ID and choose Go.

    4. Mark the line of your user and choose Modify.

    5. Select the Assigned Roles tab.

    6. Enter MDG as the search criteria.

    7. Select the portal role you have uploaded before.

    8. Choose Add and save.

    After assigning the user role you need to log off and log on again to the portal. For more information on uploading role information see SAP Note 1685257Information published on SAP site.

    Note Note

    To enable the navigation from FPM (Floorplan Manager) search results to the corresponding object maintenance, see SAP Note 1879171Information published on SAP site.

    End of the note.
  20. Data Transfer of Supplier Master Data

    Data transfer allows you to move master data between systems. These systems can be client or your main Master Data Governance systems.

    If MDG-S is used on a productive ERP system in the same client no further initial import is required.

    If MDG-S is used on a standalone ERP system supplier data that is not available on the ERP hub needs to be imported from one of the following sources:

    • Another ERP system

    • An SRM system

    • A CRM system

    • A non-SAP system

    Data Export from Source System

    To be able to export supplier master data, you can use the Export Master Data service (SAP ERP 6.0, EHP6) or the File Export (EHP5) which will create XML files in the SOA format. For exporting supplier master data from systems with ERP releases lower than SAP Business Suite Enhancement Package 5, use the existing functions in that release. For more information, see Extraction of Supplier and Customer Master Data (Earlier ERP Releases). In this case you need to configure the logical system for IDoc-XML. The steps are as follows:

    1. Create an XML-file port

      Use transaction WE21 to create an XML-file port for IDoc processing. Ensure that you have network access from your local client to the directory configured in the XML-file port. Enter the port name, description, and the physical directory. Enter the function module EDI_PATH_CREATE_CLIENT_DOCNUM. On the Outbound Trigger tab enter the RFC destination LOCAL_EXEC.

    2. Create Logical System

      Open transaction SALE and then go to Start of the navigation path Basic Settings Next navigation step Logical Systems Next navigation step Define Logical System End of the navigation path to create a new logical system.

    3. Maintain Distribution Model

      Open transaction SALE and then go to Start of the navigation path Modeling and Implementing Business Processes Next navigation step Maintain Distribution Model and Distribute Views End of the navigation path. You can also use transaction BD64 for this.

      1. Switch to change mode and choose Create Model View to create a new entry. Enter a short text and a technical identifier.

      2. Choose Add Message Type for the newly created model. Enter a logical source system name and a destination system name and choose the message type CREMDM.

    4. Create Partner Profile

      Run transaction SALE and then go to Start of the navigation path Modelling and Implementing Business Processes Next navigation step Partner Profiles Next navigation step Generate Partner Profiles End of the navigation path. Alternatively you can use transaction BD82.

      1. Select the newly created model using the input help for the technical name and then select the logical destination system.

      2. Enter the authorized user and the following values:

        • Version: 3

        • Pack.Size: 100

        • Output Mode: Immediate Transfer

        • Inbound. Processing: Immediately

      3. Choose Execute. You can ignore the port error that appears.

    5. Call transaction WE20 and make the following settings:

      1. Open the Partner Type LS folder and select the partner profile you created above.

      2. Update the message type CREMDM in the Outbound Parameters section. The Receiver Port is the XML-file port from the first step above. In the Basic Type field enter CREMDM04 for CREMDM.

    6. Test creation of IDOC XML

      1. Generate the IDoc-XML for supplier using transaction BD14.

      2. Check the newly generated IDocs using transaction WE02 or BD87. You can use the receiver port as the filter criteria in the Partner Port field.

      3. Use transaction AL11 to find the XML files on the directory of your XML-file port.

      4. To download the file for analysis purposes to local directory use transaction CG3Y.

    Data Cleansing in NetWeaver MDM

    In an optional step data cleansing, that means matching, merging, validation, and enrichment of data can be done with SAP NetWeaver MDM. The files from the data extraction process have to be converted in a first step and then can be imported into SAP NetWeaver MDM.

    After data cleansing steps the supplier data can be extracted again in order to import them into the MDG Hub. Additionally key and value mapping information might be created and uploaded with the supplier data.

    To convert the data for consumption in NetWeaver MDM you can use the WebDynpro Application MDG_TRANSFORMER_FPM_CMP which can be called from the work center for MDG-S under (Start of the navigation path Data Exchange Next navigation step Data Transfer Next navigation step Convert Master Data End of the navigation path

    Use transaction FILE to create the logical directory MDG_TRANS_SOURCE to be able to use the File Converter.

    Data Import into Target System (MDG Hub)

    Note Note

    To perform an initial load of master data, we recommend to use the functions described in the following documents:

    End of the note.

    If you want to use parallel processing for data import it is recommended that you register your queue name prefixes in the QIN Scheduler so that they are executed automatically and do not have to be manually activated each time. To register the queue name follow these instructions:

    1. Run transaction SMQ2.

    2. Choose Execute. This shows the list of current queues.

    3. ChooseStart of the navigation path Goto Next navigation step QIN Scheduler End of the navigation path.

    4. Choose the Registration.

    5. In the Queue Name field, enter a prefix for your queues. Add an asterisk after the name to allow you to add additional text to the prefix when scheduling the export or import. Enter additional details as required.

    6. Press OK.

    Your new queue has been registered and will execute automatically. You should inform those working with the Data Import service what the queue name is so they can use it.

    The IDoc-XML files contain the following fields in the header section:

    Field Name

    Field Description

    Value

    SNDPRT

    Partnertyp

    LS

    SNDPRN

    Sender Partner Number

    Defined in step 3 below.

    SNDPOR

    Sender Port

    Defined in step 1 below.

    RCVPRT

    Partnertyp

    LS

    RCVPRN

    Receiver Partner Number

    Defined in step 3 below.

    RCVPOR

    Receiver Port

    Defined in step 1 below.

    To be able to import IDoc-XML files the following set up activities need to be carried out:

    1. Use transaction IDX1 to create two ports in the IDoc adapter, one for sending and the other for receiving. Enter the port, client, description, and RFC destination for each port. Both ports should have the RFC destination of the MDG hub. Check that the port names match the names in your IDoc-XML file for the SNDPOR and RCVPOR, see table above for details.

    2. In transaction WE21 enter the receiver XML port using the same name as in step 1 above. Enter the port name under the folder XML File, and enter a description and a physical directory. In the function module field enter EDI_PATH_CREATE_CLIENT_DOCNUM. On the Outbound:Trigger tab, in the RFC destination field, enter LOCAL_EXEC.

    3. In transaction BD54 enter the sender and receiver partner numbers as logical system names.

    4. In transaction FILE create the logical file name. Enter a Logical File and a Name. In the Physical File field enter <PARAM_1>. In the data format field enter BIN. In the Application Area field enter CA. In the Logical Path field enter the logical file path

    5. In transaction AL11 make sure that the IDoc-XML files are stored under the logical path and that there are no other files stored in that directory. Double-click on the path to view the existing iDoc-XML file. You can use transaction CG3Z to copy a local IDoc-XML file to the path.

    6. To test the data import, open Start of the navigation path Data Exchange Next navigation step Data Transfer Next navigation step Import Master Data End of the navigation path in the SAP NetWeaver Portal or in the SAP NetWeaver Business Client. For more information, see Importing Master Data.

    You can use the Monitor Data Transfer application to get an overview of your data transfer processes.

  21. Event Control

    Check the table CRMC_BUT_CALL_FU and make sure that for the following entries the Call Function Module indicator is not set:

    • COM_BUPA_MWX*

    • BUPA_OUTBOUND_ALE_MAIN

    • BUPA_OUTBOUND_MAIN

    Check the table CRMC_BUT_CALL_FU and make sure that for the following entries the Call Function Module indicator is set:

    • ABA_FSBP_INBOUND_MAIN

    • ABA_FSBP_OUTBOUND_BPS_FILL

  22. Validations and Enrichments

    For an example of how to derivate the value of a field if you enter a specific value into another field, see Derivation of the Reconciliation Account After Selecting a Specific Company Code.

Result

The system is configured for Master Data Governance for Supplier.

More Information

Master Data Governance Security Guide

For information about the data model of Master Data Governance for Supplier and options to extend the data model, see the files offered on the SCN (SAP Community Network): http://scn.sap.com/docs/DOC-7858Information published on SAP site