Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD0 (Package) Master Data: Common Objects
IMG Activity
| ID | FMDM_USMD001 | Edit Data Model |
| Transaction Code | S_SE4_70000034 | (empty) |
| Created on | 20080603 | |
| Customizing Attributes | FMDM_USMD001 | Edit Data Model |
| Customizing Activity | FMDM_USMD001 | Edit Data Model |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FMDM_USMD001 |
Use
In this Customizing activity, you define and activate a data model to map master data in the system, along with its properties and relationships. The system uses this data model to generate database tables in which the master data can be stored.
Warning
You can use only one data model in an active version. Once a data model is active, you can no longer deactivate it; instead, it can only be deleted in its entirety - that is, including all related objects such as change requests, editions, and UI models.
By default, the system displays all data models that are available for processing. For each data model you can see whether an active version of the data model exists and whether that version differs from the version of the data model that is displayed in the processing view.
Requirements
You have created any customer-specific data elements you want to use for the entity types in the data model or for their attributes.
Standard settings
Activities
You define the different types of master data in the data model as entity types. In the Entity Types subdialog, you define at least one entity type for each data model. When doing this, you can define various properties for each entity type. You can also make settings for the entity type in the following subdialogs:
- Attributes:
Here you define the attributes of each entity type in the data model. Attributes are mapped as non-key fields in the generated database tables of the entity type. You also need to assign an existing data element to each attribute. The data element determines the technical properties of the attribute as well as the field labels and the input help texts on the user interface. Attributes can be defined as required entry fields or as optional fields. You use a currency-supplying or unit-supplying attribute to assign a currency or unit of measure to the attribute.
- Additional Entity Types in Hierarchies
If you want it to be possible to set up a hierarchy for the entity type, you must specify at least the root node (hierarchy name) for the hierarchy here. To do this, choose one of the available entity types and assign Hierarchy Name as the usage type. You also can specify all entity types that are to be allowed in the hierarchy of the entity type (No Special Use).
- Relationships
If you have defined multiple entity types, you can determine what type of relationship should link them (leading, referencing, qualifying, or foreign key relationship). For each relationship, you specify a relationship type and a cardinality.
NOTE:
If you want to create dependencies between entities over more than one level in this Customizing activity, then you need to check the capabilities of the UI configuration you want to use.
Example: A leading entity with a storage and use type 1 has a dependent entity with a storage and use type 4 on the second level that has another dependent entity with a storage and use type 4 on the third level.
For more information, see SAP Library for SAP Master Data Governance 6.1 on SAP Help Portal at http://help.sap.com/erp_mdg_addon61. In SAP Library, choose Configuration of Master Data Governance -> General Settings -> Web Dynpro Applications in Customizing -> Managing of UI Configurations.
To display the active version of a data model, in the menu choose Edit -> Analysis -> Display Activated Version.
Example
See also
For more information about defining master data in the data model, see SAP Library under SAP ERP Central Component -> Accounting -> Financial Master Data Management -> Configuration.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | FMDM_USMD001 | 0 | BTD0000051 | Application Framework |
| SIMG | FMDM_USMD001 | 1 | O SE40000001 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_USMD001 | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20091013 |
| SAP Release Created in | 604 |
