Specifications
136 CHAPTER 7 Master Data Services
selected. When the batch processing is complete, you can review the status of the batch in
the staging batch log, which is available in Master Data Manager, as shown in Figure 7-11.
FIGURE 7-11 The staging batch log
If the log indicates any errors for the staging batch, you can select the batch in the log and
then view the Staging Batch Errors page to see a description of the error for each record that
did not successfully load into the MDS database. You can also check the Status_ID column of
the staging table to distinguish between successful and failed records, which have a column
value of 1 and 2, respectively. At this point, you should return to the source system and
update the pertinent records to correct the errors. The next steps would be to truncate the
staging table to remove all records and nally to load the updated records. At this point, you
can create a new staging batch and repeat the process until all records successfully load.
Exporting Master Data
Of course, MDS is not a destination system for your master data. It can be both a system
of entry and a system of record for applications important to the daily operations of your
organization, such as an enterprise resource planning (ERP) system, a customer relationship
management (CRM) system, or a data warehouse. After you commit a model version, your
master data is available to other applications through subscription views in the MDS database.
Any system that can consume data from SQL Server can use these views to access up-to-date
master data.
To create a subscription view in Master Data Manager, you start by assigning a name to
the view and selecting a model. You then associate the view with a specic version or a ver-
sion ag.
TIP You can simplify the administration of a subscription view by associating it with a
version ag rather than a specic version. As the version of a record changes over time,
you can simply reset the ag for the versions. If you don’t use version ags, a change in
version requires you to update every subscription view that you associate with the version,
which could be a considerable number.
Next, you select either an entity or a derived hierarchy as the basis for the view and the
format of the view. For example, if you select an entity, you can format the view to use leaf
members, consolidated members, or collection members and the associated attribute val-
ues. When you save the view, it is immediately available in the MDS database to anyone (or
any application) with Read access to the database. For example, after creating the Product