Specifications

Integration CHAPTER 7 135
Integration
Master Data Manager also provides support for data integration between MDS and other ap-
plications. Master Data Manager includes an Integration Management area for importing and
exporting data. However, the import and export processes here are nothing like those of the
SQL Server Import And Export wizard. Instead, you use the Import page in Master Data Man-
ager to manage batch processing of staging tables that you use to load the MDS database,
and you use the Export page to congure subscription views that allow users and applications
to read data from the MDS database.
Importing Master Data
Rather than manually entering the data by using Master Data Manager, you can import your
master data from existing data sources by staging the data in the MDS database. You can
stage the data by using either the SQL Server Import And Export wizard or SQL Server Inte-
gration Services. After staging the data, you use Master Data Manager to process the staged
data as a batch. MDS moves valid data from the staging tables into the master data tables in
the MDS database and ags any invalid records for you to correct at the source and restage.
You can use any method to load data into the staging tables. The most important part of
this task is to ensure that the data is correct in the source and that you set the proper values
for the columns that provide information to MDS about the master data. For example, each
record must identify the model into which you will load the master data. When staging data,
you use the following tables in the MDS database as appropriate to your situation:
■
tblSTGMember Use this table to stage leaf members, consolidated members, or
collections. You provide only the member name and code in this table.
■
tblSTGMemberAttribute Use this table to stage the attribute values for each
member using one row per attribute, and include the member code to map the at-
tribute to the applicable member.
■
tblSTGRelationship Use this table to stage parent-child or sibling relationships
between members in a hierarchy or a collection.
NOTE For detailed information about the table columns and valid values for required
columns, refer to the “Master Data Services Database Reference” topic in SQL Server 2008
R2 Books Online at http://msdn.microsoft.com/en-us/library/ee633808(SQL.105).aspx.
The next step is to use Master Data Manager to create a batch. To do this, you identify
the model and the version that stores the master data for the batch. The version must have
a status of either Open or Locked to import data from a staging table. On your command to
process the batch, MDS attempts to locate records in the staging tables that match the speci-
ed model and load them into the tables corresponding to the model and version that you