How to Create a Custom Entity Type in SAP MDG: Step-by-Step Tutorial

The SAP Master Data Governance comes with a robust collection of entity classes that cover the material customers, vendor financial master data. However, in actual implementations there are many business requirements that surpass what's provided from the box. When you have to manage the customisation of a business object, such as cost center hierarchies or retail location data or an industry-specific master file knowing how to create an individual entity type within MDG is a crucial knowledge that each technical MDG consultant requires. This guide explains how to create the different types of entities in SAP MDG as well as how entities' names and types are categorized and stored to the underlying MDG tables, and provides a full step-by-step procedure to create an entity type that is custom in MDG SAP.

What Are Entity Types in SAP MDG?

In SAP MDG An entity type is a particular master object of data that is controlled by the system -consider it the concept of "what kind of data" is being created, altered or approved. The standard entity types are items such as material (MM) as well as business partners (BP) as well as finance cost object. Every entity type has their own model of data specifying its attributes, relations and hierarchies applicable to that object.

The entities types used in SAP MDG aren't only labels, they're the foundation that decides the way in which the UI is created and how SAP MDG workflows are activated as well as how validations operate and how data is replicated to the target system. Each governance process you create in MDG such as single object processing mass processing, mass processing, data consolidation, etc. -is set up to work with an entity type.

When your business demands require the regulation of something SAP does not provide from the beginning (a customized reference object for data, a master for an industry or an extension to one of the models already in place) You must expand your MDG database model to develop an entity type that is custom rather than attempting to fit the requirements into an existing standard entity type.

Entity Type and Entity Name in SAP MDG Table: Understanding the SAP MDG Data Model

Before you can create an entity type that is custom it is important to know the place where entities types reside in the system, and also how the entity type and name are stored in the SAP MDG tables.

The MDG information model has been created and stored in the Data Modeler (transaction USMD_MODEL) The resultant metadata is saved in a set of tables in the system, most particularly:

Table	Description
USMD100	It stores the definitions of entities themselves as well as the ID of the entity type as well as long and short descriptions (this is where the entities type and name are registered together)
USMD101	It holds attributes associated with each type of entity
USMD102	Is a way to define the relationships between entities of different types
USMD201/USMD202	To store metadata related to hierarchy when the type of entity supports hierarchies
USMD_STRUCTURE	Connects entity types to their database structures, as well as active area tables

The entity type is a four-character number (similar similar to the other SAP objects keys) and the entity name is the text description, both long and short, that is maintained in a variety of languages. This description is displayed on the UI when business users choose or submit governance requests to the object. If you create a customized entity type, you are filling these table (via using the Data Modeler interface instead of directly maintaining tables) by introducing a new key as well as its associated metadata attributes, structural mappings.

Understanding the structure of the table is important since troubleshooting custom entity type problems -- such as absence of UI fields, invalid validations or failures to replicateusually trace back to the inconsistencies between these tables as well as the structures they refer to.

Prerequisites Before Creating a Custom Entity Type in MDG SAP

Before you begin to configure ensure that these are in the correct order:

• Access to the the transaction USMD_MODEL (Data Modeler) with authorization
• A clear business need document that defines the elements, key structure and the necessary relationships to create the object
• A custom development namespace or package to store the generated structures and also includes
• Decide if the entity type requires singular processing, bulk processing, consolidating data or support for hierarchy This will determine the amount of configuration that is needed in the downstream
• Alignment with your Base/Development team regarding your transportation strategy, as the data model modifications are cross-client and must be able to flow through the normal transportation procedures

Skipping the requirements-gathering step is the most common reason custom entity type builds need rework later, since adding attributes after UI configuration and workflows are already built creates significant rework.

Step-by-Step: How to Create a Custom Entity Type in MDG SAP

Step 1: Create a New Governance Model (or Use an Existing One)

Open the transaction "USMD_MODEL. When you're adding an entity model to a custom governance scope, you can select this model. In other cases, create a brand new governance model that is under the namespace you have created. The model functions as a container that ties all entities with similar types.

Step 2: Define the Entity Type

In the Data Modeler you can navigate towards the type of entity node, and select the option to create a brand distinct entity type. You'll specify:

• A unique entity type key (4 characters, customer namespace)
• Descriptions for long and short descriptions (this is your entity's name, which is maintained for each the language)
• If the entity type is an entity type that is a root (standalone) or an entity that is dependent (subordinate to another type of entity)
• Time-dependency settings, in case the object has validity requirements.

This is the point at which the entity type as well as the entity name relationships in the structure of SAP MDG tables actually is established the system generates the appropriate entry in USMD100 when you enable the model.

Step 3: Define Attributes

Include the attributes that comprise your customized object. Each attribute should be defined as follows:

• Name of the attribute along with the Data element (reuse current data elements when it is possible to cut development time)
• Key attributes in contrast to. non-key attributes
• What is the condition of the attribute or optional.
• Check table references and value help for dropdowns as well as F4's behavior for search

These attributes make up USMD101, and are the basis of the database structure for your type of entity.

Step 4: Define Relationships (If Applicable)

If your custom entity type is connected to other types of entities such as an object for a location which connects to business partner records, create these relationships using the Data Modeler. Relationships define how data is linked to process and the way it appears in the UI's relationship viewer.

Step 5: Generate the Data Model

After entity types as well as attributes and relationships are established Utilize the function generate within USMD_MODEL. This will generate:

• The database tables for staging and active areas
• Structures that are referenced by BRFplus rules. UI or BRFplus rules
• Standard function modules and BAdI implementation stubs to the type of entity you are using

Errors in generation at this point are typical when attribute data elements are in conflict with the existing structure or key definitions aren't consistentread the log of generation carefully prior to beginning.

Step 6: Activate the Governance Model

After successful generation, you can activate the model. The activation completes the definition of an entity type and makes it accessible for additional configuration steps such as UI modeling workflow assignment, workflow modeling, or BRFplus configuration. This is also when your customized entity type is made accessible and selectable by downstream customizing transactions.

Step 7: Configure the UI (Floorplan Manager/Fiori)

With the entity type active, configure the create/change/display UI using Floorplan Manager (or the Fiori-based UI configuration for cloud/S/4HANA-based MDG). Convert the attributes of your entity into UI fields, then arrange them into tabs and logical groups as well as configure search and results view views for the type of entity.

Step 8: Set Up Process Configuration

Configure the governance procedure to the entity's new type by Customizing in the process model node of MDG. This includes:

• Defining single object processing steps (create, change, mark for deletion)
• Assignment of workflow template in the event that approval steps are needed
• Configuring the number ranges for entities for entities that use internal numbering

Step 9: Configure Validations and Derivations

Utilize BRFplus to create validation rules (ensuring that the data is of good quality before records are activated) and derivation rules (auto-populating fields according to the business rules). These rules are based on the attributes you set up in the previous step, so the accuracy of your attributes setup earlier is a big benefit in this case.

Step 10: Test End-to-End

Before making the transition to QA or production to production, make sure you test the entire process: make an entry, run it through the workflow you have set up to verify that the rules for validation and derivation trigger correctly, and verify that the data is properly inserted into the tables in active area. If replication is required verify the external interface separately after the core governance function is that it is stable.

Common Mistakes When Creating Custom Entity Types in SAP MDG

• Skipping proper data element reuse creating new data elements for each attribute, instead of using standard ones will increase the cost of maintenance and could cause problems with the existing BRFplus reports or expressions.
• Underestimating relationship modeling -- relationships are difficult to retrofit following activation, therefore, it is best to map them out completely in the requirement phase.
• Do not begin planning for mass processing in the early stages If mass upload/mass modification is required it should affect the design of key elements and attributes at the beginning, rather than being added later.
• Ignoring sequence of transport Changes to the data model, UI configuration, and BRFplus policies often require move in the right order. If they are not done, it can cause an inconsistent behavior across different environments.
• Insufficient testing of derivation/validation interplay -- rules that work fine independently can conflict when triggered together during actual processing, so combined testing matters more than isolated unit testing.

Why Custom Entity Types Matter for Your SAP MDG Career

The ability to build and configure an individual entity type within MDG SAP is one of the primary distinctions between a professional who can create standard scenarios and those who are able to provide highly complex, customized governance solutions. A majority of large-scale MDG implementations require at minimum the creation of a custom entity whether it's a specific master object of data or as an extension of the standard data models. This makes this an extremely valuable capability for technical MDG architects and consultants alike.

If you're working on your SAP MDG skills by implementing custom entity type creation from beginning to end from data modeling all the way to UI setting up and creating rules -- provides you with an experience that is practical and interview-ready. It is far beyond the textbook understanding of the standard entities.

Need hands-on assistance in creating custom entities and governance processes using SAP MDG? Best Online Career's SAP MDG training covers data modeling, user interface configuration, BRFplus rule-based processes, and real-world implementation scenarios to help you develop the necessary technical abilities for your job.