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 imports 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 imported as user defined properties (UDPs) with names starting by 'MDM_'.
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
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 identical to and defined by the SAP MDM documentation.
LIMITATIONS
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 | XML file exported by SAP Master Data Management. | FILE | *.xml | Mandatory | ||||
| Default language | Specify the language you would like to use. It must be defined in the XML file. SAP Master Data Management can support multiple languages. Here are some examples: English [US] German [DE] French [FR] Japanese [JP] Russian [RU] Korean [KR] Portuguese [PT] Spanish [ES] Italian [IT] Chinese [CN] Czech [CZ] Dutch [NL] Polish [PL] Finnish [FI] Swedish [SE] Danish [DK] Hungarian [HU] |
STRING | English [US] | Mandatory | ||||
| Multiple Languages | Set to True if you would like to capture Table and Field names in multiple languages as user defined properties. Otherwise, set to False. It could be useful when going to a tool that does not support multiple encodings |
BOOLEAN | True | |||||
| PrimaryKeys schema | Select the schema according to which you'd like primaryKeys to be built. 'Schema Unique&Required' Attribute (column) is PK when the field is UNIQUE and REQUIRED flag is set. If a table does not declare UNIQUE field(s) the Internal_ID is used 'Schema Unique' Attribute (column) is PK when the field is UNIQUE only (REQUIRED=No). If a table does not declare UNIQUE field(s) the Internal_ID is used 'Schema InternalId' PK is always an artificial Internal_ID field (disregard field settings of UNIQUE and REQUIRED for all tables in the model) |
ENUMERATED |
|
Unique&Required | ||||
| Multi-Valued Tuple | Set to True if you would like additional intermediate entity to be used in case of Multi-Valued Tuple relationship. | BOOLEAN | True |
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 |