Relationships Staging Table (Master Data Services)
Use the parent child relationship staging table (mdm.tblStgRelationship) in the Master Data Services database to:
Move members in explicit hierarchies.
Add members to collections.
This topic contains the following sections:
Displays an automatically assigned identifier. If the batch has not been processed, this field is blank.
Displays an automatically assigned identifier that groups records for staging. All members in the batch are assigned this identifier, which is displayed in the Master Data Manager user interface in the ID column. This value is also in mdm.tblStgBatch, in the ID field.
If the batch has not been processed, this field is blank.
Optional value. Specify a user name to filter the records in the Master Data Manager user interface. The logged in user can view:
The user name should match the name in the Master Data Manager Users list, for example DOMAIN\user_name or server\user_name.
Required value. Specify the case-sensitive name of the model.
Required value. Specify the name of the entity.
Required value only if you are designating a relationship for the member in an explicit hierarchy. Specify the explicit hierarchy name.
Leave blank if you are adding a member to a collection.
Specify whether the member is being added to an explicit hierarchy or a collection. Possible values are:
Required value. Specify the member code.
For explicit hierarchies:
You can use MDMUNUSED for TargetCode to add leaf members to the Unused node of a non-mandatory explicit hierarchy.
You can use ROOT for TargetCode to add members to the root of an explicit hierarchy.
For collections, specify the code of the collection that you want to add the member to.
For explicit hierarchies:
For collections, specify 1.
Optional value. For explicit hierarchies, specify an integer that indicates the order of the member in relation to the other members under the parent. Each member should have a unique number.
Displays the status of the import process. Possible values are:
Displays an error code. For all records with a Status_ID of 2, view the Staging Batch Errors page in Master Data Manager for a more detailed description.
You can save the following example to a flat file and import it into your Master Data Services database if you have completed the following tasks:
Deployed the sample Product model that is in the Master Data Services\Samples\Packages directory where you installed Master Data Services. For more information about deploying the sample Product model, see Deploying Models (Master Data Services).
Imported the example in Members Staging Table (Master Data Services).
For more information about importing data into a database by using SQL Server Integration Services, see How to: Run the SQL Server Import and Export Wizard.
The following example shows how to stage attribute relationships.
The first line in this example contains the column names.
The second line designates the MW consolidated member as a parent of the BK-M101 leaf member in the Product Management explicit hierarchy.
The third line designates the BK-M101 leaf member as a sibling of (at the same level as) the BK-M18B-40 leaf member in the Product Management explicit hierarchy.
The fourth line adds the JR collection to the USBIKE2WRK collection.
The fifth line adds the BK-M101 leaf member to the USBIKE2WRK collection.
The sixth line adds the MW consolidated member to the USBIKE2WRK collection.
ModelName,EntityName,HierarchyName,MemberType_ID,MemberCode,TargetCode,TargetType_ID Product,Product,Product Management,4,BK-M101,MW,1 Product,Product,Product Management,4,BK-M18B-40,BK-M101,2 Product,Product,,5,JR,USBIKE2WRK,1 Product,Product,,5,BK-M101,USBIKE2WRK,1 Product,Product,,5,MW,USBIKE2WRK,1