MDG Data Modeling basics.

Data modeling the first step with any mdg implementation. As with every other aspect of MDG, data modeling process is very flexible and generic. The flexibility ensures that MDG can address a variety of customer requirements and data model design specifications.

This blog highlights various rules and reasons behind the data modeling decisions. For an end to end solution implementation, check out the eLearning sessions posted here.

Once the data model is implemented in MDG and activated, the system automatically generates the underlying tables and structures. When the end users create or change data from the UI, the data is persisted in these generated tables.

Data Model for Z4 (a test data model):

The corresponding generated tables for Z4:

There are a variety of configuration options when creating an Entity. Each of the options affect the final MDG solution in a unique way. In this blog we consider the configuration options available with mdg data modeling and their significance. 

First step in mdg data modeling is to create a SU Type 1 (Storage and Usage Type One) entity. To draw an analogy with MDM, SUT1 in MDG corresponds to the Main Table in MDM.

For a simple Type1 entity, the Storage Type, Data Element and Description are the main fields. Leave the others as defaults. Data Element is a optional field here. When provided, the Data Element is a key field in the generated table.

For this Entity, I have added one attribute of type Z3COMMENTS. Pl. note that the Data Elements and Domains used in MDG Data Modelling already exist as part of a ERP solution or are created (using SE11 tcode) .

This is a simple data model with a single Entity. Suggested next steps:

1. The four Entity Types in MDG
2. Understanding relationship in MDG
3. Key Assignment and Deletion have a dependency on each other. These dependencies are enforced by the system. Try changing the default values to observe the specific dependencies.

Following three error messages show up when I try changing the Key Assignment to "Key Can Be Changed; Internal Key Assignment Possible".

4. Try creating the SUType1 entity with out the data element. Instead add an attribute of this type (of data element) to the Type1 entity. See the resulting change in the schema of the generated table.

Cheers!