Select language:

Process documentationConfiguring Master Data Governance for Material

 

To use SAP Master Data Governance (MDG) for material, you need to carry out the steps described below.

Prerequisites

Business Function

You have activated the following business functions:

  • Master Data Governance, Generic Functions (MDG_FOUNDATION)

  • Master Data Governance, Generic Functions 2 (MDG_FOUNDATION_2)

  • Master Data Governance for Material (MDG_Material)

  • Master Data Governance for Material 2 (MDG_Material_2)

Note Note

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 (for example MM, BP, or 0G) and the values for the authorization activity ACTVT Activity (for example 01: Create or generate, or 02: Change).

End of the note.

If you want to use the MDG for Material homepage or the Business Context Viewer you should activate the business functions /BCV/MAIN and /BCV/MAIN_1. For more information on the Business Context Viewer see, Business Context Viewer in Single Processing.

When you activate the MDG_Material business function the system activates the Material (MM) data model. Before continuing with system configuration, open transaction SFW5 and check if the activation has been completed by choosing Switch Framework Logs from the Goto menu and selecting the corresponding entry.

Set Up Workflow

To use the rule-based workflow processes of MDG for material, you have defined general settings for SAP Business Workflows in Customizing for SAP NetWeaver under   Application Server  Business Management  SAP Business Workflow  . Remember to regenerate the authorization profile of SAP_ALL or include USMD* authorization objects into the authorization for the user WF-Batch.

To activate the workflow features, use the semi-automated configuration in transaction SWU3. You can also access these settings in Customizing under   SAP NetWeaver  Application Server  Business Management  SAP Business Workflow  Maintain Standard Settings  

For further information see the documentation for the Configuration activity. Note the following when maintaining the settings:

  • When configuring the RFC destination you need superuser authorization to create the default WF-BATCH user.

  • Regenerate the authorization profile for SAP_ALL or include the USMD* authorization objects into the authorizations of the user WF-Batch.

  • For the Check Entries from HR Control Tables section you may need to execute report RHSOBJCH in transaction SE38 and keep the default settings.

  • Maintain the prefix numbers for the standard objects.

  • You do not need to maintain the Web Server and Guided Procedures Gateway.

Set Up Search

You must have installed and connected Enterprise Search either in embedded form or as central search engine service in order to use master data governance for material.

Adjust Profile Parameters

Ensure that the profile parameter size for the Shared Objects Memory is the correct. To check this setting run transaction RZ11 and verify that the value for parameter abap/shared_objects_size_MB is between 200 and 300 megabytes.

If you want to use the SAP NetWeaver Business Client with single sign on, ensure that the parameters login/create_sso2_ticket and login/accept_sso2_ticket are set correctly.

Use transaction RZ11 to check that the host name is fully qualified for parameter icm/host_name_full.

User Roles

In order to successfully conduct the next steps in the configuration process, you must have the following user roles assigned in thePFCG transaction:

  • SAP_BC_TREX_ADMIN

  • SAP_J2EE_ADMIN — Portal Role

  • SAP_QAP_ESH or SAP_ESH_LOCAL_ADMIN if it is not available.

  • SAP_MDGA_MENU — Master Data Governance: Analytics

  • SAP_MDG_ADMIN — Master Data Governance: Administrator

    This role contains authorizations for basic tasks relevant to the configuration and administration of SAP Master Data Governance (MDG) for all domains. Some authorizations allow critical activities. If you have multiple users involved in the configuration and administration of MDG content, we recommend you split this role into several new roles and give each new role a subset of the authorizations for this role. Such an approach ensures users only complete tasks they are responsible for and reduces the risk of critical errors. Authorizations for the MDG transactions are not included in this role.

  • SAP_MDGM_MENU — Master Data Governance Material: Menu

  • SAP_MDGM_DISP — Master Data Governance Material: Display

  • SAP_MDGM_REQ — Master Data Governance Material: Requester

  • SAP_MDGM_SPEC — Master Data Governance Material: Specialist

  • SAP_MDGM_STEW — Master Data Governance Material: Data Steward

In addition, the authorization object PLM_SPUSR is needed if the Search Object Connector for enterprise search is created for the Enterprise Search Software Component PLMWUI or any Enterprise Search Software Component that includes PLMWUI.

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.

Process

This process describes the minimal set of customizing steps and recommended check activities required to do the following:

  • Create materials

  • Change materials

  • Mark materials for deletion

  • Process multiple materials

You run the settings for this process in Customizing under   Cross-Application Components  Processes and Tools for Enterprise Applications  Master Data Governance  .

  1. Activate the Data Model MM

    Check (or enhance) and activate the MM data model including temporary IDs for internal number handling.

    1. Check whether you can use the data model delivered by SAP for managing your material master data with MDG for material.

      Activate the delivered data model MM in Customizing for Master Data Governance under   General Settings  Data Modeling  Edit Data Model  .

    2. Assign an internal key.

      To support internal key assignment, run the activity in Customizing for Master Data Governance under   General Settings  Data Modeling  Define Prefixes for Internal Key Assignment  .

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

      • Data Model: MM

      • Entity Type: MATERIAL

      • Prefix: $

      Note Note

      For MDG for material, authorizations cannot be defined here. Instead, the existing back-end authorizations are reused.

      For more information, see Customizing under   Logistics – General  Material Master  Tools  Maintain Authorizations and Authorization Profiles  .

      Other customizing activities in data modeling are only relevant for the material domain if your data model needs to be enhanced. For more information, see Enhancement of Master Data Governance Content and Extending the Data Model for Master Data Governance for Material.

      End of the note.
  2. Activate Business Configuration Set

    Run this activity in Customizing for Master Data Governance under   Master Data Governance for Material  Import Predefined Change Request Types  .

    To start, choose Activate and keep the default settings.

    If you want to use the MDG for Material homepage or the Business Context Viewer (BCV) then activate the BC set MDGMAT_BCV and MDGMAT_BCV_FOUNDATION under   SAP Menu  Tools  Customizing  Business Configuration Sets  Activation of BC Sets  .

  3. Verify UI Modeling (Optional)

    UI configuration activities are only relevant if you want to change the UI or if the MM data model has been enhanced.

    With Enhancement Package 6, the Business Add-In previously available to adjust the user interface for single processing of material is no longer available. Instead, a new UI provides greater flexibility while retaining and refining the features provided with Enhancement Package 5. For more information on upgrading the UI BAdI, see SAP Note 1606341.

    In Enhancement Package 6 the Web Dynpro application in the user role and settings made in Customizing determines the UI Configuration. In the pre-delivered PFCG Role SAP_MDGM_MENU the Web Dynpro application is linked to the application configuration.

    Example using the Create Material Web Dynpro:

    Web Dynpro Application MDG_BS_MAT is linked to application configuration BS_MAT_INIT. In the customizing activity Link Actions with UI Application and Business Activity: Standard Definition the current application configuration BS_MAT_INIT and the action Create are linked to target UI application MDG_BS_MAT_OVP and target UI configuration BS_MAT_OVP.

    The application configuration BS_MAT_OVP contains the component configurations BS_MAT_OVP_CBAand BS_MAT_OVP_LAYOUT.

    There are context based adaptations (CBA) in the pre-delivered component configuration BS_MAT_OVP_LAYOUT that influence the UI dynamically. The predefined adaptations are: Action, Change Request Type, Material Type, Workflow Step and Industry Sector.

    An adaptation is delivered for the action Delete. Some UIBBs are hidden and the Mark for Deletion flag is shown. These dimensions are defined in schema BS_MAT. The delivered schemas can be found in the View Cluster FPM_VC_ADAPT_SCHEMA accessed through transaction SE54.

    CBA schema can be reused and enhanced with custom-defined dimensions. Own schemas and UI configurations can be created without modification. See the extensibility guides for more information.

    Note Note

    You can view the Web Dynpro applications using transaction SE80. The package name is MDG_BS_MAT_UI.

    End of the note.
  4. Set Up Search

    There are two types of search options available:

    • Embedded Search (included in SAP NetWeaver on a local system)

    • SAP NetWeaver Enterprise Search (run centrally)

    Embedded Search is limited to indexing and searching within a single SAP system (single SAPSID). If you want to extend the reach of searches across two or more systems, use SAP NetWeaver Enterprise Search. In production scenarios with heavy data load it is mandatory to install a separate TREX instance that is used exclusively by Embedded Search for performance and sizing reasons. For installation information for TREX 7.1 see SAP note 1249465.

    Embedded Search

    If you want to use Embedded Search, run the following activity in Customizing for SAP NetWeaver under   Search  Embedded Search  .

    SAP delivers the following two standard templates for MDG for material. You need to activate these templates and prepare them for indexing.

    • Material (MATERIAL) – for the active data residing on the standard tables MA* and related objects

    • Material Template for MDG (MDG_MATERIAL) – for the inactive material data linked to the MDG change requests

    If you are not familiar with TREX or TREX is not yet activated, proceed as follows to make the basic settings:

    1. Create TREX_RFC user.

      If the TREX_RFC user is not available, create it with the required roles as mentioned in the SAP note 766516 for the target system.

    2. Connect to the TREX installation.

      During TREX installation, you created an RFC-destination for the TREX. Run transaction SM59 in the TCP/IP connections section to verify that it exists and can be linked. Link the ABAP system to this TREX destination.

      For more information, see Customizing for SAP NetWeaver under   Search and Operational Analytics  SAP NetWeaver Enterprise Search  TREX  Set TREX Destination  .

      Alternatively, you can run report ESH_ADM_SET_TREX_DESTINATION.

    3. Create and index the connectors.

      Open the Connector Administration Cockpit in Customizing for SAP NetWeaver under   Search and Operational Analytics  SAP NetWeaver Enterprise Search  Modeling, Administration, and Monitoring  Open Administration Cockpit  . Alternatively, you can run the transaction ESH_COCKPIT. Make the following settings:

      1. To open the Modeler, select the Modeler link.

      2. In the Software Component menu choose Maintain Software Components and chooseCreate. Enter the name for the new software component and assign a package. The SW Comp. Type is Normal Software Component. Choose Create. Enter a description for the new software component and choose Save. Select a workbench request.

        Note Note

        The new software component is necessary to get all extensions of the template MATERIAL, which are made in the included software component. When creating the search connector for MATERIAL and you have installed both, the MDG_APPL software component and the PLMWUI software component, you have to decide in which Software Component the MATERIAL connector is created. This is because both, MDG_APPL and PLMWUI are parent software components of SAP_APPL. Both the MDG_MATERIAL template and the MATERIAL template are used in the MDG applications (which are related to the software component MDG_APPL). This requires that the related connectors are created in the software component MDG_APPL. However, applications related to the software component PLMWUI require, that the MATERIAL connector is created in the software component PLMWUI. However, as described above, each connector can only be created in one software component.

        To overcome this situation, we have to create a super component of MDG_APPL and PLMWUI. If you now create the MATERIAL or the MDG_MATERIAL connector, they are assigned to this new top level component. Related search templates can be used in all underlying software components.

        End of the note.
      3. Mark your new software component and choose in the Software Component menu Include Software Components. Include the component MDG_APPL. Choose Save and select Workbench Transport. Repeat this process for the highest software component for the connector MATERIAL. For example, if the software layer hierarchy is PLMWUI > EA-APPL > SAP-APPL use the software component PLMWUI but if the software layer hierarchy is EA-APPL > SAP-APPL then use the software component EA-APPL.

      4. Go back to the Administration Cockpit and select Create. Select the new software component and search for the template MATERIAL. Once you have located the template, create the connector for the Enterprise Search. Create the connector using the MATERIAL template first and wait for the job to complete before creating the connector using the MDG_MATERIAL template.

      5. The two connectors Material and Material Template for MDG are now visible with the status preparing and or prepared. Select the Material connector and from the Actions menu select Schedule Indexing. On the new screen choose Show Input Form. Next, choose the option for immediate indexing and the recurrence period. You can also activate real-time indexing if the sizing, parameters, and performance of the system allow for this. Select all object types and choose Copy Settings. This copies the default settings from the input form to all object types. The status of the connector is changed to Indexing.

      6. Ensure authorization indexing. Enterprise Search requires its own authorizations. Authorizations for all MDG users must be indexed on the Enterprise Search system. The system writes every new or changed user as an entry into the table ESH_AU_USR_UPD that contains the user IDs that have been changed since the last indexing of the technical object type USER_AUTHORITY.

        The object type USER_AUTHORITY needs to be regularly scheduled for indexing on the Enterprise Search system. The object type USER_AUTHORITY can be found in the connector Material or the connector MDG_MATERIAL. You cannot enable real-time indexing for USER_AUTHORITY.

      Once indexing is complete the two connectors should have the status Active.

    4. Use the report ESH_TEST_SEARCH to verify the search function. In the Search Scope section, enter a Connector ID. Next, enter Default in the Request field and execute the report.

      • The connector MATERIAL returns the active material master data.

      • The connector MDG_MATERIAL returns the inactive material master data. At least one active change request of type MAT* needs to exist with materials assigned to it, otherwise you will get a message that the search provider MDG_MATERIAL does not exist during the search and in the duplicate check of any change request where this is relevant.

    For more information about TREX, see Configuration of the TREX Security Settings.

    Search Engine Service

    If you are running a central SAP NetWeaver Enterprise Search system and you connect other SAP NetWeaver systems with Embedded Search to the central system, follow the steps as described in Customizing for SAP NetWeaver under   Search  Search Engine Service  .

  5. Verify Data Quality and Search Settings

    In the delivered standard, the SAP NetWeaver Enterprise Search is used for MDG for material.

    In this step, you can verify the following:

    • Existence of entry ES and that Freeform, Complex Selection, and Fuzzy settings are activated

      This entry cannot be removed or deactivated (E-class entry delivered by SAP). You can verify these settings in Customizing for Master Data Governance under   General Settings  Data Quality and Search  Define Search Applications  .

    • The pre-delivered Match Profile for the MM data model is MATCH_MM_MATERIAL. You can find this Match Profile in Customizing for Master Data Governance under   General Settings  Data Quality and Search  Define Search Applications  

      If you wish you can now define your own matching fields for calculating the potential duplicates and matching values.

    • Configuration of the duplicate check

      If you want to run a duplicate check you have to assign the predelivered match profile MATCH_MM_MATERIAL or your own match profile to the MM data model and the MATERIAL entity type. Enter the search mode ES and select the field MPbased UI. Thresholds are not considered.

      You can configure this check in Customizing for Master Data Governance under   Data Quality and Search  Define Search Applications  Configure Duplicate Check for Entity Types  .

    • Assignment of the delivered search object connector templates

      Ensure for business object type 194 Material, that the delivered search object container MDG_MATERIAL and the MDG_APPL software component is assigned.

      You can check this in Customizing for Master Data Governance under   General Settings  Data Quality and Search  Assign Search Object Connector Templates to Object Types  .

  6. Configure Change Request Settings

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

    The following information describes the minimal settings for a basic 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.

      For more information, see Customizing for Master Data Governance under   General Settings  Process Modeling  Change Requests  Edit Statuses of Change Requests  .

      The following statuses are required for the SAP standard process. If you only activate Master Data Governance for Material, you should maintain the missing ones manually:

      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

      30

      To Be Revised with Changes

      Execution of Changes

      99

      No Status Set

      No Processing

    2. Check that the following business activities are in your system and that they are assigned to the default data model MM.

      • MAT1 Create Material

      • MAT2 Process Material

      • MAT3 Display Material

      • MAT6 Mark Material for Deletion

      • MATA Process Multiple Materials

      • MATB Import Material

      For more information, see Customizing for Master Data Governance under   General Settings  Process Modeling  Business Activities  Create Business Activity  .

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

      For more information, see Customizing for Master Data Governance under   General Settings  Process Modeling  Change Requests  Create Change Request Type  .

      The following table shows the change request types for data model MM. Only the relevant columns are included.

      Change Request Type

      Data Model

      Description

      Single Object

      Main Entity Type

      Workflow

      MAT01

      MM

      Create Material

      Yes

      MATERIAL

      WS60800086

      MAT02

      MM

      Change Material

      Yes

      MATERIAL

      WS60800086

      MAT06

      MM

      Mark Material for Deletion

      Yes

      MATERIAL

      WS60800086

      MAT0A

      MM

      Process Multiple Materials

      No

      MATERIAL

      WS60800086

      MAT0B

      MM

      Import Material

      No

      MATERIAL

      WS60800086

      The standard workflow template used by Master Data Governance for material is WS60800086. This template is a rule-based workflow which uses BRF+ decision tables.

      There is also a workflow template without BRF+, which covers the same processes. If you want to use this template, replace template WS60800086 with template WS46000057 in the relevant change request type.

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

      • MAT01

        • Entity type: MATERIAL

        • UI Config: MDG_MM_APP_BS_MAT_GEN (Only relevant for Enhancement Package 5)

        • Msg. Output: W Issue Error Messages as Warnings

        • Business Activity: Create Material (MAT1)

        • Service Level Agreement for Change Request Types: <leave empty>

      • MAT02

        • Same as for MAT01

        • Business Activity: Process Material (MAT2)

      • MAT06

        • Same as for MAT01

        • UI Config: MDG_MM_APP_BS_DEL_GEN (Only relevant for Enhancement Package 5)

        • Business Activity: Mark Material for Deletion (MAT6)

      • MAT0A

        • Same as for MAT01

        • UI Config: <leave empty>

        • Business Activity: MATA Process Multiple Materials

      • MAT0B

        • Same as for MAT01

        • UI Config: <leave empty>

        • Business Activity: MATB Import Material

    4. Optionally, you can configure the properties of the change request step. For more information see Customizing for Master Data Governance under   General Settings  Process Modeling  Change Requests  Configure Properties of Change Request Step  .

    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.

      Perform the following activity in Customizing for Master Data Governance under   General Settings  Process Modeling  Change Requests  Define Priorities / Reasons / Rejection Reasons for Change Requests  .

    6. Optionally, you can define print forms for change requests. By default, the form USMD_EDITION_CREQUEST is used. This is relevant only if your own or multiple print forms are required.

      For more information, see Customizing for Master Data Governance under   General Settings  Process Modeling  Change Requests  Define Print Form for Change Requests  .

  7. Configure Workflow Tasks

    As a prerequisite you have made the necessary general settings for workflows and defined the organizational plan in Customizing for SAP NetWeaver under   Application Server  Business Management  SAP Business Workflow  . Then you need to ensure that the active type linkages for Material (BUS2250) are set correctly. Follow the instructions in Customizing for MDG under   General Settings  Process Modeling  Workflow  Activate Type Linkage  . For entry BUS2250 with no workflow template select the flag Linkage Activated and deselect the flag Enable Event Queue. Do not set these flags for other BUS2250 entries that have workflow templates assigned.

    The standard workflow template used by Master Data Governance for material is WS60800086.

    In order to ensure the general assignment of processors using the rule-based workflow, run the following activity in Customizing for Master Data Governance under   General Settings  Process Modeling  Workflow  Configure Workflow Tasks  .

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

    2. All tasks (denoted by TS*) that are not set as Background Task need to be set to General Task. To do so, select the task, choose Attributes and change to General Task. In particular, ensure you do this for the Dialog Processing (TS 60807954) task.

    Alternative procedure using the generic workflow maintenance transaction:

    1. Run transaction SWDD

    2. In the Workflow field, enter the workflow template WS60800086, the highest version is automatically chosen.

    3. In the Navigation area go to step 000073 Dialog Processing and select it.

    4. In the Task Properties area, choose Agent Assignment for Task. Choose the Agent Assignment for Task button.

    5. On the next screen select Dialog Processing and choose the Attributes button.

    6. In the Task popup select General Task and choose Transfer.

    7. Return to the Task Properties list and verify that the status icon beside Agent Assignment is green or yellow.

  8. Set Up the Rule-Based Workflow

    MDG for material 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.

    Check that the steps for Rule-Based Workflow are imported by the BC-Set by running the following activity in Customizing:   General Settings  Process Modeling  Workflow  Rule-based Workflow  Define Steps for Rule-Based Workflow  .

    The following are the default steps required for all change request types:

    Type of Change Request

    Change Request Step

    Keys

    Successful Validation Required

    Definition

    MAT01

    0

    Empty

    Empty

    Processing

    MAT01

    90

    Empty

    Checked

    Final Check

    MAT01

    91

    Empty

    Empty

    Activation

    MAT01

    92

    Empty

    Empty

    Revision/Cancel BG

    MAT01

    93

    Empty

    Empty

    Validation

    MAT01

    95

    Empty

    Empty

    Revision Processing

    MAT01

    99

    Empty

    Empty

    Complete

    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. Check for existing decisions tables and generate the decision tables and rules for each change request type either in Customizing or by running the system transaction USMD_SSW_RULE. If this step is not possible, go to step 2, otherwise go to step 3.

    2. Export the content from client 000 and import it into your hub client.

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

    More detail on these steps is available below.

    To activate and load the necessary settings for BRFplus proceed as follows:

    1. Check for existing decisions tables and generate the decision tables and rules for each change request type in Customizing under  General Settings  Process Modelling  Workflow  Rule-Based Workflow  Configure Rule-Based Workflow  

      Enter the change request types one after the other and choose the Continue button. After reviewing the decision tables you can leave this step without any further activities. If you get an error that the object is not available, proceed to the next step, otherwise skip to step 3. You can also makes these settings using the transaction USMD_SSW_RULE.

    2. Export the content from client 000 and import it into your hub client.

      1. Call transaction BRFplus in the 000 client.

      2. To switch to Expert mode from the Workbench menu choose User Mode.

      3. Search for the object USMD_SSW_CATA_MAT01 using the Workbench menu by choosing Open Object. Use the following values to search:

        • Object Type CA: Catalog

        • Name: USMD_SSW_CATA_MAT*

      4. From the search result select USMD_SSW_CATA_MAT01

      5. To export the content from client 000, right-click on the application in the repository (not the catalog entry) to open the context menu and choose   Tools  XML Export  

        Choose Include Referenced Objects (do not check Include Surrounding Application). Generate the XML file and download it. You can ignore the warnings on missing values not in the value list. The file size of each XML file should be approximately 101kb. The system may require you to assign the import to a transport.

      6. To Import the content into your MDG main client run the BRFplus transaction, from the Tools menu choose XML Import, select your XML file, and choose Upload File.

      7. Repeat these steps for all relevant change request types including:

        • MAT01 Create Material

        • MAT02 Process Material

        • MAT06 Mark Material for Deletion

        • MAT0A Process Multiple Materials

        • MAT0B Import Material

      The structure import will also include the values in the three pre-delivered decision tables. For testing the standard workflow configuration you need to copy and activate the two entries in the DT_USR_AGT_GRP_MATXX from user ANZEIGER to one or two existing user IDs in your system.

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

      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_MAT01

      • DT_NON_USER_AGT_GRP_MAT01

      • DT_USER_AGT_GRP_MAT01

      DT_NON_USER_AGT_GRP_MAT01 and DT_SINGLE_VAL_MAT01 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_MAT01 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_MAT01 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_MAT01.

      Conduct this maintenance for all relevant change request types. Further details on the workflow concepts can be found here. The following change request types appear in the standard delivery: MAT01, MAT02, MAT06, MAT0A, MAT0B.

      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_MAT01/2/6/A/B

      Previous Step

      Previous Action

      Condition Alias

      New Step

      New Change Request Status

      00 (Create Change Request)

      No value

      1

      90 (Final Check)

      02 (Changes to be executed)

      90 (Final Check)

      09 (Activate)

      2

      91 (Final Approval)

      02 (Changes to be executed)

      90 (Final Check)

      4 (Reject)

      3

      95 (Revision Processing)

      10 (To Revise: Perform Changes)

      91 (Final Approval)

      31 (Activation Successful)

      4

      99 (Complete)

      05 (Final Check Approved)

      91 (Final Approval)

      <>31 (Activation Successful)

      5

      90 (Final Check)

      11 (Process Errors After Activation)

      92 (Revision/Cancel BG)

      No value

      6

      99 (Complete)

      06 (Final Check Rejected)

      95 (Revision Processing)

      07 (Request Again)

      7

      90 (Final Check)

      02 (Changes to be executed)

      95 (Revision Processing)

      08 (Withdraw)

      8

      92 (Revision/Cancel BG)

      02 (Changes to be executed)

      DT_USER_AGT_GRP_MAT01/2/6/A/B

      COND_ALIAS

      AGENT_GROUP

      STEP_TYPE

      USER_TYPE

      USER_VALUE

      1;5;7

      001

      8 (Activate Change Request)

      US

      ANZEIGER

      3

      001

      4 (Revise)

      US

      ANZEIGER

      DT_NON_USER_AGT_GRP_MAT01/2/6/A/B

      COND_ALIAS

      AGENT_GROUP

      PROCESS_PATTERN

      2

      001

      06 (Activation (Bypass Snapshot))

      4;6

      001

      99 (Complete (Sub-)Workflow)

      8

      001

      08 (Roll back change request)

      Notes

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

      • The quickest way to allow users to participate in any workflow step for testing purposes is to copy the two default entries in the DT_USER_AGT_GRP_MAT01/2/6/A tables and change the entries as follows:

        • User Type: AG (Role)

        • User Value: SAP_MDGM_MENU (The MDGM 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.

  9. Set Up Data Transfer

    Data Transfer allows you to move master data between systems. These systems can be clients or your main Master Data Governance (MDG) system. The first step of a data transfer is the export of the master data to an IDoc-XML file, which you can save locally or on your application server. In the second step, you import the data into your central MDG system. During the import step you can decide if you want the new master data to appear directly in the active area, or if you want to work with change requests and import the data to the staging area.

    Data Export from Source System

    To be able to export material master data, you need to configure the logical system for IDoc-XML export to the application server file system. 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   Basic Settings  Logical Systems   to create a new logical system.

    3. Maintain Distribution Model

      Open transaction SALE and then go to   Modeling and Implementing Business Processes  Maintain Distribution Model and Distribute Views  . 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 types MATMAS and CLFMAS.

    4. Create Partner Profile

      Run transaction SALE and then go to   Partner Profiles  Generate Partner Profiles  . 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 types MATMAS and CLFMAS in the Outbound Parameters section. The Receiver Port is the XML-file port from the first step above. In the Basic Type field enter MATMAS05 for MATMAS and CLFMAS02 for CLFMAS.

    6. Test creation of IDOC XML

      1. Generate the IDoc-XML for material using the transaction BD10.

      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 Import into Target System (MDG Hub)

    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 the Execute button. This shows the list of current queues.

    3. From the Goto menu, select QIN Scheduler.

    4. Choose the Registration button.

    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. Choose OK.

    Your new queue has been registered and will execute automatically. You should inform those working with the Import Master Data service of the new queue name so that they can use it when creating new imports.

    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 path 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. Open the Configuration activity   General Settings  Data Transfer  Define File Source and Archive Directories for Data Transfer   and assign your new logical file path name as a directory for data transfer.

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

    7. To test the data import, open the Data Importservice from the Material Governance work center in the SAP NetWeaver Portal or SAP NetWeaver Business Client. For more information, see Data Import.

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

  10. Set Up Data Replication

    For Master Data Governance for Material you have two options for replicating data from the MDG hub to the connected systems and clients:

    • Data replication using Application Link Enabling (ALE)

    • Data replication using Application Link Enabling (ALE) with the Data Replication Framework

    For more information, see in Customizing under   Application Server  IDoc Interface / Application Link Enabling (ALE)  SAP Business Workflow  .

    Set Up Data Replication Using ALE

    The following process describes briefly the minimal settings required for the two main message types MATMAS and CLFMAS.

    1. Verify logical systems

      Run transaction SALE and choose   Basic Settings  Logical Systems  . Both clients (source and target) need to be defined as logical systems and need to be assigned to the relevant clients.

    2. Check communication

      Run transaction SALE and choose   Communication  Created RFC Connections  . The target partner system has to be defined here as an ABAP connection with a connection type of 3 and with same name as the target logical system. Perform a connection test.

    3. Maintain distribution model

      1. Run transaction SALE (Display ALE Customizing) and choose   Modeling and Implementing Business Processes  Maintain Distribution Model and Distribute Views  . Alternatively, run transaction BD64 (Maintenance of Distribution Model).

      2. In change mode, create a new model.

        Choose the Create Model View pushbutton. Enter a short text and a technical name.

      3. Choose the Add Message Type pushbutton for the newly created model.

      4. Enter names for the logical source and destination systems and choose message type MATMAS.

    4. Create partner profile. (In the receiving client)

      1. Run transaction SALE and choose   Partner Profiles  Generate Partner Profiles  . Alternatively, run transaction BD82 (Generate Partner Profiles).

      2. Select the newly created model and in the Partner System field, enter the logical destination system.

      3. Enter the ALE-User (the default value is ALEREMOTE) and the following values, and execute.

        Field

        Value

        Version

        3

        PackSize

        100

        Output Mode

        Transfer IDoc immediately

        Inb. Parameters: Processing

        Trigger Immediately

      4. To verify your settings, run transaction WE20 and from the Partner Profiles menu, choose Partner Type LS. Verify that Partner type LS is the logical destination system.

      5. In the detail screen, the chosen message type MATMAS must appear.

    5. Distribute model view to receiving system.

      1. Run transaction SALE and choose   Modeling and Implementing Business Processes  Maintain Distribution Model and Distribute Views  . Alternatively, run transaction BD64.

      2. Select the new model and choose   Edit  Model view  Distribute  .

      3. Verify that the correct receiving system is marked and choose Enter.

      4. Verify within the receiving system that the model view was created.

    6. Create partner profile (receiving client).

      1. Run transaction SALE and choose   Modeling and Implementing Business Processes  Partner Profiles  Generate Partner Profiles  . Alternatively, run transaction BD82.

      2. Select the distributed model.

      3. Enter the ALE-User, and the following values, and execute.

        Field

        Value

        Version

        3

        PackSize

        100

        Output Mode

        Transfer IDoc immediately

        Inb. Parameters: Processing

        Trigger Immediately

        Note Note

        If the protocol contains the error Port could not be created this can be ignored.

        End of the note.
      4. Check that the correct process code is being used. To do this go to the details for the inbound parameter message types and in Inbound Options check that the parameter Process Code is MATM.

      Follow the above steps add the message type CLFMAS to the model. The process code in WE20 Inbound Details has to be CLFM. You can test the distribution using transaction BD10. Verify the results in the receiving client using transaction BD87.

    7. Repeat this procedure for message type CLFMAS.

      Note Note

      In the Configuration activity Define Technical Settings for Business Systems SAP recommends that you select the checkbox Status System Filter for the Material business object. This ensures that if an object instance was previously sent to a target system, it continues to be sent in the future, independent of filter settings.

      End of the note.

    Set Up Data Replication Using ALE with DRF

    In Master Data Governance for Material the replication of material master data from MDG Hub to connected client systems can be scheduled, triggered, and monitored using the Data Replication Framework (DRF) in concert with the ALE.

    Note Note

    If you are using ALE and DRF together to replicate materials you can improve performance by deselecting the change pointers for the MATMAS message type. You can do this in the Activate Change Pointers for Message Types configuration activity. You should only do this if all your MDG systems are integrated using ALE and DRF together. If you use ALE without DRF in one or more connected systems do not disable the change pointers.

    End of the note.

    The following customizing is relevant for data replication:

    • ALE (See Set Up Data Replication Using ALE above)

    • Enterprise Search (See Set Up Search above)

    • Key Mapping (See Key Mapping below)

    • ALE Audit (See Customizing for ALE Audit below)

    • Data Replication Framework (DRF)

    The following process outlines the steps required to perform the customizing for the last three points above.

    Customizing for Data Replication Framework (DRF)

    1. Run transaction DRFIMG and navigate to   Enhance Default Settings for Outbound Implementation  Define Parameters   to check if the outbound parameter PACK_SIZE_BULK is available.

      The following information should be available for this parameter:

      Outbound Parameter

      Description

      Data Type

      Value Length

      PACK_SIZE_BULK

      Package Size for Bulk Messages

      Integer

      10

    2. Run transaction DRFIMG and check if the filter objects below have been defined. Select   Enhance Default Settings for Outbound Implementation  Define Filter Objects   to view the filter object definitions. The main filter object is MDG_BS_MAT.

      Filter Objects

      Type

      Technical Name

      Description

      Segment Filter Object

      F_MAT1

      Plant segment of material

      Segment Filter Object

      F_MAT2

      Sales segment of material

      Segment Filter Object

      F_MAT3

      Storage segment of Material

      Segment Filter Object

      F_MAT4

      Tax class segment of material

      Segment Filter Object

      F_MAT5

      Valuation segment of material

      Segment Filter Object

      F_MAT6

      Class segment of material

    3. Use transaction DRFIMG to check if the outbound implementation I_MAT has been defined. Select   Enhance Default Settings for Outbound Implementation  Define Outbound Implementations  .

    4. Define the technical settings for the business system.

      1. Enter transaction DRFIMG and navigate to   Define Custom Settings for Data Replication  Define Technical Settings for Business Systems  .

      2. In the Business System field specify the receiver system. In the Logical System field enter the Logical System used for IDoc communication. In the RFC Destination field enter the RFC destination to be used for RFC communication with the receiver system.

      3. Select the entry and double-click on Define Bus. Systems, BOs.

      4. In the BO Type field enter the business object type 194. In the Description field, enter a descriptive text.

      5. Select the entry and double-click on Define Bus. Systems, BOs, Communication Channel. In the Communication Channel field enter the means you want to use to transmit data to the applications. In the Key Harm. field specify if you want your keys harmonized between the hub and the client systems.

    5. Create the replication model and assign it to the outbound implementation as follows:

      1. Enter transaction DRFIMG.

      2. Navigate to   Data Replication  Define Custom Settings for Data Replication  Define Replication Models  .

      3. Select Define Replication Model and then select New Entries.

      4. Enter a replication model and a description. In the Log Days field, you may enter the number of days after which you want an Application Log to expire. In the Data Model field, enter MM.

      5. Select the newly defined replication model and choose Assign Outbound Implementation.

      6. Choose New Entries.

      7. Assign the outbound implementation I_MAT.

      8. Assign a target system for the outbound implementation I_MAT.

      9. Assign the outbound parameter PACK_SIZE_BULK to the outbound implementation I_MAT with the Outbound Parameter Value 5.

    6. Save and activate the replication model.

  11. Define Value Mapping

    The elements for possible value mapping are predelivered.

    If required, you can define value mapping for elements such as, UoM, industry sector, material type, and others in Customizing for Master Data Governance under   General Settings  Value Mapping  .

  12. Define Key Mapping

    If you are working with multiple connected systems and did not consolidate the material 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   General Settings  Key Mapping  .

    The mapping definitions of the key mappings are conducted by any authorized user using the business transaction from the portal or the corresponding back-end transaction.

    Customizing for Key Mapping

    If you are working with multiple connected systems you may want to define or configure the key mapping between the MDG Hub and the client systems. Use the following steps to determine if the client system and hub system need to be key mapped or harmonized:

    1. Enter transaction DRFIMG and navigate to   Define Technical Settings  Define Technical Settings for Business Systems  .

    2. Select a business system and choose Define Bus. Systems. BOs.

    3. Select BO Type 194.

    4. Choose Define Bus. Systems. BOs, Communication Channel.

    5. In the Key Harm column, check if the channel uses harmonized IDs or key mapping. If nothing is selected you may choose to set up key mapping if required.

    Note Note

    Key and value mapping must be performed once for each connected system where data is being replicated from MDG Hub system.

    End of the note.
  13. Customizing for ALE Audit (Optional)

    You can configure your client and hub systems so that your client systems send confirmation of replicated materials back to the MDG hub. Use the following steps to set up this confirmation process.

    In the client system make the following settings:

    1. Select Distribution Model

      1. Run transaction BD64 and choose Change/Display.

      2. Select the distribution model you created above and choose Add Message Type.

      3. In the Add Message Type screen enter the following:

        • In the Sender field, enter the logical system from which the acknowledgement is sent (The client system).

        • In the Receiver field, enter the logical system to which the acknowledgement is sent (The hub system).

        • In the Message Type field, enter ALEAUD.

      4. Choose Ok.

    2. Select Partner Profile

      1. Run transaction SALE and choose   Partner Profiles  Generate Partner Profiles  . Alternatively, run transaction BD82 (Generate Partner Profiles).

      2. Select the distribution model and in the Partner System field, enter the hub logical system name.

      3. Enter the ALE-User (the default value is ALEREMOTE) and the following values.

        Field

        Value

        Version

        3

        PackSize

        100

        Output Mode

        Transfer IDoc Immediately

        Inb. Parameters: Processing

        Trigger Immediately

      4. Click on the Execute button. The log for partner profile generation appears showing the new sender and receiver systems

      5. To verify your settings, run transaction WE20 and from the Partner Profiles menu, choose Partner Type LS. Verify that Partner type LS is the logical destination system.

      6. In the detail screen, the message type, ALEAUD must appear.

      7. In the Inbound Options tab, in the Process Code field enter AUD2.

      8. Select the Cancel Processing After Syntax Error checkbox.

      9. In the Processing by Function Module section, select the Trigger Immediately radio button.

      10. Choose Save.

      11. Run transaction BD64. Select the model view and select   Edit  Model View  Distribute  . Select the Hub system and click OK.

    In the hub system make the following settings:

    1. Distribution Model

      1. Run transaction BD64 and check that the same Distribution Model View with partner profile was created.

    2. Partner Profile

      1. Run transaction WE20 and check that the partner profile with logical name of the receiver system (Hub system) exists below the Partner Type LS folder.

      2. Select Receiver Logical System (Hub system) and choose Change.

      3. Choose Create Outbound Parameter.

      4. In the Message Type field enter ALEAUD.

      5. In the Outbound Options tab, in Receiver Port field, enter the logical system name for the client from which the status information is to be received.

      6. In the Output Mode list, select Transfer IDoc Immediately.

      7. In the Basic Type field enter ALEAUD01.

      8. Select the Cancel Processing After Syntax Error checkbox.

      9. Choose Save.

    3. Configure DRF Customizing

      1. Run transaction DRFIMG.

      2. Navigate to   Data Replication  Define Custom Settings for Data Replication  Define Technical Settings for Business Systems  .

      3. Select the receiver system (Hub system) and double-click on Define Bus. Systems, BOs, Communication Channel.

      4. Enter the business object type 194 and choose OK.

      5. Select the checkbox Upd.KM.

      6. Choose Save.

  14. Choose where you want to run SAP Master Data Governance

    You can run SAP Master Data Governance in either of the following environments:

    • SAP NetWeaver Portal

    • SAP NetWeaver Business Client

    SAP NetWeaver Portal

    The SAP NetWeaver Portal content for MDG for material is part of the standard delivery for the SAP Business Suite and is delivered with SAP enhancement package 6 for SAP ERP 6.0 and software component BP ERP MDGM.

    You must implement the following business packages using Java Support Package Manager (JSPM) in your SAP NetWeaver Portal.

    • Business Package for Material Master Data Manager 1.61 (BPERPMDGM 1.61)

    • Business Package for Common Parts (mySAP ERP) 1.61 (BPERP5COM 1.61)

    • Business Package for Financial MDM 1.61 (BPERPFINMDM 1.61)

    The system alias for BPERPMDGM, BPERPMDGS and MPERPFINMDM is SAP_FMDM, so it means it will point to the same backend system. This backend system has to be created in the portal as system object and the system alias SAP_FMDM has to be assigned to it. You need to add the S_RFC authorization object with activity 16 to users that you want to be able to see the work items in UWL iViews.

    Once activated, you must assign and personalize the role Material Master Data Manager in the portal as follows:

    1. Logon to the portal.

    2. Choose Delegated User Administration.

    3. Enter your User ID and choose the Go pushbutton.

    4. Mark the line of your user and Modify.

    5. Select the Assigned Roles tab.

    6. Enter Material as the search criteria.

    7. Select role Material Master Data Manager.

    8. Click Add and save.

    After assigning the user role you need to log off and log on again to the 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 create, define, or configure the roles for the Business Client in the SAP ERP system. There are four roles that contain authorization and navigation data and one that contains only navigation data. The Master Data Governance for Material: Menu (SAP_MDGM_MENU) role contains all navigation information without authorizations.

    To assign and personalize the role Master Data Governance for Material: Menu (SAP_MDGM_MENU) proceed as follows:

    1. On the SAP Easy Access screen, choose   Tools  Administration  User Maintenance  Role Administration  Roles   or alternatively, run transaction PFCG (Role Maintenance). Choose role SAP_MDGM_MENU.

      This role ensures that the necessary steps can be started without using the SAP NetWeaver Portal. This can be used for testing or if the portal is inactive.

      Assign and personalize the role SAP_MDGM_MENU to your users. In the role SAP_MDGM_MENU on the Personalization tab, edit the Personalization Key SAP Master Data Governance (R_FMDM_MODEL): Define the standard model MM and the related UI configuration.

    2. Verify the setting of the authorization objects within the roles and restrict them if required.

    3. On the SAP Easy Access screen, choose   Tools  Administration  User Maintenance  Users  . Run transaction SU01 (User Maintenance) and assign the Master Data Governance for Material: Menu role (SAP_MDGM_MENU) for application to the MDG user.

  15. Final Steps

    SAP recommends to regenerate the data model again at the end of these setup steps to ensure clear code generation.

    Note Note

    Before you can run Master Data Governance services like Display Material, you need to assign the data model MM to your user. Alternatively, the user administrator can maintain the following Personalization Parameter for your user profile: SAP Master Data Governance R_FMDM_MODEL.

    End of the note.

Result

The system is configured for MDG for material. In addition, if data load has been done, mass changes and distribution to other systems can also be executed.

More Information

Impact of Material Master Customizing

Some Material Master customizing activities are relevant for Master Data Governance for Material:

  • Under the Configuring the Material Master node, the activity Define How Maintenance Statuses Are Determined in Data Transfer impacts Master Data Governance for Material.

  • Under the Field Selection node, all activities that change the field properties affect the field properties in Master Data Governance for Material. The field properties hidden, displayed, mandatory, and optional impact the Master Data Governance for Material fields.

  • Under the Basic Settings node, all activities impact Master Data Governance for Material. Example settings include the output format of the material number and the material types.

  • Under the Settings for Key Fields node, all activities impact Master Data Governance for Material. Example settings include the definition of material groups, and the settings for EANs.

  • Under the Data Transfer: Material Master node, the activity Define Required-Field Check for ALE/Direct Input impacts Master Data Governance for Material. There you define how the material master for industry is updated if required fields not belonging to the core maintenance status lack entries.

Was this page helpful to you?