Bridge Specifications
| Vendor | SAP |
| Tool Name | NetWeaver Master Data Management (MDM) |
| Tool Version | 5.5 to 7.1 |
| Tool Web Site | http://www.sap.com/usa/platform/netweaver/components/mdm/index.epx |
| Supported Methodology | [Data Modeling] Data Store (Physical Data Model, Logical Data Model) via XML File |
SPECIFICATIONS
Tool: SAP / NetWeaver Master Data Management (MDM) version 5.5 to 7.1 via XML File
See http://www.sap.com/usa/platform/netweaver/components/mdm/index.epx
Metadata: [Data Modeling] Data Store (Physical Data Model, Logical Data Model)
Component: SapMdm version 11.2.0
OVERVIEW
This bridge generates an SAP NetWeaver Master Data Management (MDM) XML file. Additional metadata elements, generally not available in most metadata design tools, are used by SAP MDM. These additional metadata elements are exported from user defined properties (UDPs) which are expected to be defined in the source model. These UDP's all must have names starting by 'MDM_'.
A sample blank XML file for SAP MDM is available ${MODEL_BRIDGE_HOME}\conf\MIRModelBridgeTemplate\MIRSapMdm\SapMdm-Blank.xml
The meaning and valid values of each MDM_xxx UDP is is identical to and defined by the SAP MDM documentation.
REQUIREMENTS
In order to obtain these UDP names and place them in a modeling tool, the user may create a new project in SAP MDM Development Studio producing an XML file. Then use the SAP MDM import bridge to import the file and then export the result to the chosen modeling tool. The resulting model in this modeling tool will contain a number of UDPs with names starting by MDM_xxx. The user may then use this model as a basis to create the data model which contains the correct MDM UDPs.
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
When importing from a multi model source technology (e.g. a database server with multiple databases or schemas), only one model (e.g. schema) is exported. Therefore, limit the import scope to a single model (e.g. subset one schema of a database).
Refer to the current general known limitations at https://www.metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope |
| File | SAP MDM XML file to generate. | FILE | *.xml | Mandatory | |
| XML Indentation (pretty printing) | Controls the pretty printing of XML, for the purpose of opening the generated file in a text editor. E.g. 'space characters' Several space characters as indentation. 'tab key' Tab character as indentation. 'empty' No indentation which leads to a more compact file. |
STRING |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"SAP NetWeaver Master Data Management (MDM) - Unsupported Beta Bridge" Metamodel SapMdm |
Mapping Comments |
| Attribute | Field | |
| Name | ML Lang | |
| PhysicalName | Code | |
| Class | Table | |
| Description | Description | |
| Name | ML Lang | |
| PhysicalName | Code |