In physical MDM, you need to ensure that configuration
settings are consistent with any customizations you have made to the
hybrid MDM configuration projects, such as survivorship rules defined
in composite view, and the mapping of attributes between virtual MDM
and physical MDM.
About this task
Preparing the physical MDM requires that you:
- Ensure business keys are defined in the V_ELEMENTATTRIBUTE table
for business objects included in the hybrid MDM mapping files. Business
keys are the one or more data elements that define the uniqueness
of a record. They are used by the composite view to determine which
attributes are included in the view. They also play a key role in
determining whether an existing attribute needs to be updated or a
new record needs to be created in physical MDM.
- Choose your
business keys with care. As long as the business key
values on a business object are unchanged, supplemental attributes
added to the business object remain associated with the business object.
When changes in the virtual MDM entity result in records being created,
the supplemental attributes from existing objects are not carried
over to the new objects. Also, if an existing record is no longer
in the virtual MDM entity, the business object is deleted from physical
MDM along with its supplemental attributes. The only exceptions are
party addresses, which are inactivated instead of deleted from physical
MDM, when they are no longer in the virtual MDM entity.
- Ensure
that reference data values in physical MDM code tables
are up-to-date. The values for reference data (such as state or province,
country, marital status, organization type) must align with the corresponding
values in the member records in virtual MDM. The default transformations
in the hybrid MDM are built upon the following reference data mapping.
Be certain to clean and standardize all of these fields with your
source systems before you add them to virtual MDM. Doing so allows
the entities to be persisted in a hybrid MDM solution.
Table 1. | Virtual MDM attribute type and field name |
Physical MDM code table |
|---|
| For member type: PERSON |
|
| MemHead.srcCode |
CDADMINSYSTP |
| PERMARITAL.maritalstatus |
CDMARITALSTTP |
| PERNAME.prefix |
CDPREFIXNAMETP |
| PERNAME.generation |
CDGENERATIONTP |
| PERADDR.provstate |
CDPROVSTATETP |
| PERADDR.country |
CDCOUNTRYTP |
| |
|
| For
member type: ORG |
|
| MemHead.srcCode |
CDADMINSYSTP |
| ORGTYPE.orgtype |
CDORGTP |
| ORGADDR.provstate |
CDPROVSTATETP |
| ORGADDR.country |
CDCOUNTRYTP |
IBM InfoSphere Master Data Management, Version 11.3