Show TOC

Procedure documentationAdding New Entity Types to Data Models Locate this document in the navigation structure

 

You can use this procedure to enhance Master Data Governance content by adding new entity types to data models.

Prerequisites

You have created the new entity types in the customer namespace Y* or Z*. The attributes for the new entity types are either in the customer namespace or the SAP namespace.

Any relationships that you define between a new entity type and an SAP entity type (as a To-entity type) must be in the customer namespace.

Example Example

A typical example is the dependent entity type with the cardinality N (table). In this case, you use an entity type of storage and use type 4 (Changeable via Other Entity Type; Generated Database Tables) and a different entity type of storage and use type 3 (Not Changeable via MDG; No Generated Tables) as an additional key.

Another example illustrates the dependent entity type with the cardinality 1:0, the active data of which the system stores in the MDG active area. In this case, you select the value MDG as the setting for the reuse active area for the entity type.

End of the example.

Procedure

The paths specified below are for Customizing for Master Data Governance and, unless otherwise specified, are relative paths under General Settings.

  1. Configure data modeling as follows:

    1. Assign new entity types to a standard data model. You can make this assignment in one of the following activities in Customizing for Master Data Governance:

      •   Data Modeling   Edit Data Model  (view cluster VC_USMD001).

      •   Configuration Workbench   (Web application).

    2. Create relationships for the dependent entity types. When doing this, take into account the example mentioned above as well as the following requirements:

      • For the additional key, you have to create a qualifying relationship for the entity type that can be changed by other entities. If the additional key is part of the SAP namespace, the qualifying relationship must be in the customer namespace.

      • For the higher-level entity type (delivered by SAP), you have to create a leading relationship for the entity type (SU type 4) in the customer namespace.

  2. Choose   UI Modeling   Edit UI Configuration   (Web Dynpro application USMD_UI_CONFIGURATION), and configure the Web Dynpro user interface in the Floorplan Manager (FPM).

    Recommendation Recommendation

    We recommend that you create and edit a (deep) copy of an existing UI configuration where possible.

    For more information, see Managing of UI Configurations.

    You can also carry out small changes in administrator mode in the FPM:

    1. Enhance the FPM configuration by adding the generic user-interface building blocks (UIBBs) for the relevant entity type.

    2. You can insert the parameter SAP-CONFIG-MODE=X into the URL at runtime and execute the link Adjust Configuration.

    End of the recommendation.

    Note Note

    • In component configuration, always edit the leading, higher-level entity type with storage and use type 1 first.

    • Assign the new UI configuration to one of the following:

      • The relevant role or user parameters

      • The change request type under   Process Modeling   Change Requests   Create Change Request Type  

    • If you want to use the Business Add-In (BAdI) Adjust User Interface for Single Processing (USMD_UI_EVENT2), note that:

      • If you copied a UI configuration, copy the implementation under   UI Modeling   BAdI: Adjust User Interface for Single Processing   and set the filter value to the UI configuration that you copied (and adjusted).

      • If you customized the UI configuration in administrator mode, you simply need to create a new implementation of the BAdI if you want to change the programming.

    End of the note.

  3. (Optional) Customize the validation and derivation rules under   Data Quality and Search   Define Validation and Derivation Rules  .

    • Assign a function of type Check Entity for validations and a function of type Derivation for derivations.

    • Alternatively, you can implement the Business Add-In under   Data Quality and Search   BAdI: Define Validations/Derivations   (BAdI USMD_RULE_SERVICE).

  4. Configure the print output as follows:

    1. Specify the structure names for the PDF output under   Data Modeling   Generate Data Model-Specific Structures   (view cluster VC_USMD004).

    2. You can then create the ABAP Dictionary structures using the Generate Structures function.

  5. Configure the settings for data replication.

    1. Specify the source structures for the SMT under   Data Modeling   Generate Data Model-Specific Structures   (view cluster VC_USMD004).

    2. You can then create the structures using the Generate Structures function. You can use the SMT structures to define a new SMT mapping. This can be used to:

      • Provide data for advanced SAP services

      • Provide data for customer-specific services

      • Provide data for other communication channels (ALE, RFC)

      Note Note

      If you cannot use existing service interfaces, the options listed here require significant implementation effort since you would be required to create your own outbound implementations.

      For more information about how to integrate the outbound interface framework with the data replication framework, see   Data Replication   Enhance Default Settings for Outbound Implementations   Define Outbound Interface Models  .

      End of the note.

  6. Configure the Enterprise Search settings.

    1. Configure the search object connector relevant for your Enterprise Search template. For more information about integrating Enterprise Search into Master Data Governance, see Enterprise Search.

    2. You need to generate the Enterprise Search-specific structures for the relevant entities under   Data Modeling   Generate Data Model-Specific Structures   (view cluster VC_USMD004).

More Information

Enhancement of Master Data Governance Content