Show TOC

Procedure documentationAdding New Attributes to Standard Entity Types Locate this document in the navigation structure

 

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

Note Note

You can create attributes in the customer namespace, for example, under ZZ* and YY*.

End of the note.

Procedure

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

  1. Create the attribute.

    You can make this assignment in one of the following activities in Customizing for Master Data Governance:

    •   General Settings   Data Modeling   Edit Data Model  .

      1. Select your data model and switch to the Entity Types subdialog.

      2. Select the entity type for which you want to add an attribute and switch to the Attributes subdialog.

      3. Create a new attribute and assign a data element. The system then derives the properties, field labels, field help, and input help values for the attribute. Avoid assigning data elements more than once.

    •   General Settings   Data Modeling   Configuration Workbench   (Web application).

      1. Select your data model.

      2. In the Entity Typespanel, select the entity type for which you want to add an attribute, and open the Attributes tab.

      3. Create a new attribute and assign a data element. The system derives the values for the properties, field labels, field help, and input help for the attribute. Assign data elements only once, respectively.

    Note Note

    If you create attributes that, unlike entity A, use the MDG active area as the active area, you need to create a new entity type B with storage and use type 4 in which you embed the new attributes. You also need to define a relationship of type leading with the cardinality 1:0 from entity type A to entity type B. For more information, see Adding New Entity Types to Data Models.

    End of the note.

  2. Adjust the UI configuration.

    Configure the Web Dynpro user interface, for example, using administrator mode in the Floorplan Manager (FPM) and using Business Add-Ins.

    • Choose   UI Modeling   Edit UI Configuration   (Web Dynpro application USMD_UI_CONFIGURATION), and add generic user-interface building blocks (UIBBs) to the Web Dynpro configuration for the Floorplan Manager. To access administrator mode, you need to insert the parameter SAP-CONFIG-MODE=X into the URL at the runtime of single processing and execute the link Adjust Configuration.

    • (Optional) Under   UI Modeling   Business Add-Ins   BAdI: Adjust User Interface for Single Processing   (BAdI USMD_UI_EVENT2), create your own implementation.

      1. In your implementation, allow the methods that you want to adjust to be inherited from the implementing class of a delivered standard implementation. If the implementing class does not allow inheritance because it is marked as FINAL, you need to create a copy of the class.

        Note Note

        Note that the copy does not automatically contain corrections from Support Packages or SAP Notes. Therefore ensure you check the relevant SAP Notes for the implementing class and manually implement any corrections.

        End of the note.

      2. Deactivate the existing BAdI implementation and activate your new BAdI implementation.

  3. (Optional) Adjust the settings for Interactive Forms.

    1. Copy the relevant scenario and adjust it under   Process Modeling   Change Requests   Form-Based Change Requests   Edit Scenario for Form-Based Change Requests   (view cluster VC_APB_ISR_CUST).

    2. Assign the copied scenario to a change request type at entity type level under   Process Modeling   Change Requests   Create Change Request Type   (view cluster VC_USMD110).

    3. You can customize the display data under   Process Modeling   Change Requests   Form-Based Change Requests   BAdI: Customize Form Display for Change Request   (BAdI USMD_ISR_FORM).

  4. (Optional) Customize the BRFplus-based validation and derivation rules under   Data Quality and Search   Define Validation and Derivation Rules   (Web Dynpro application USMD_RULE).

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

    • If BRFplus is not sufficient for your purposes, a Business Add-In is also available under   Data Quality and Search   BAdI: Define Validations/Derivations   (BAdI USMD_RULE_SERVICE).

  5. Configure the print forms for single processing.

    You assign the generated structures under   Data Modeling   Generate Data Model-Specific Structures   (view cluster VC_USMD004). You can enhance the standard using a Business Add-In under   UI Modeling   BAdI: Change Data to Be Printed   (BAdI USMD_PRINT_FORM).

  6. Configure the settings for data replication.

    The source structures of the Service Mapping Tool (SMT) contain CI includes that you can enhance under   Data Modeling   Generate Data Model-Specific Structures   (view cluster VC_USMD004).

    Take into account the following settings and adjust these if required:

    1. Target structure enhancements depend on the outbound implementation:

      • If you are already using additional attributes, for example, in your RFC interfaces or service definitions, the target structures may already be enhanced.

      • If you are adding new attributes to your infrastructure, you need to enhance the structures, for example, for services, by regenerating proxies with specific APPEND structures.

    2. You can enhance the SMT mapping using the standard enhancement concept of the Service Mapping Tool.

    3. You can enhance service interfaces using the standard enhancement concept of SAP NetWeaver Process Integration (PI).

      After data enhancements are defined in PI, proxy regeneration generates certain APPEND structures for the delivered proxy structures. Since the proxy structure was simply enhanced and not replaced, you can use it as the target structure in the SMT mapping and outbound service interface without making modifications.

    4. You can create additional fields either by means of an SMT enhancement or by implementing a BAdI. You implement this BAdI in the application-specific Customizing settings for Master Data Governance, for example, under   Master Data Governance for Supplier   BAdIs for Data Replication  .

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