Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Rules for Loading Data

Rules for Loading Data

The load batch process loads records in any state. The state is specified as an input column on the staging table. The input state can be specified in the mapping as a landing table column or it can be derived. If an input state is not specified in the mapping, then the state is assumed to be ACTIVE (for Load inserts). When a record is updated through a Load batch job and the incoming state is null, the existing state of the record to update will remain unchanged.
The following table lists the state of the incoming cross-reference record in the first column, the state of the existing cross-reference record in the top row, and the resulting action in the cells: 
XREF States
Existing: ACTIVE
Existing: PENDING
Existing: DELETED
Existing: No XREF
(Load by rowid)
Existing: No Base Object Record
Incoming: ACTIVE
Update + Promote
Update + Restore
Incoming: PENDING
Pending Update
Pending Update
Pending Update + Restore
Pending Insert
Pending Insert
Incoming: DELETED
Soft Delete
Hard Delete
Soft Delete
Not recommended
Not recommended
Incoming: Undefined
Treat as ACTIVE
Treat as PENDING
Treat as DELETED
Treat as ACTIVE
Treat as ACTIVE
If history is enabled after a hard delete, then records with HUB_STATE_IND of -9 are written to the cross-reference history table (HXRF) when cross-references are deleted. Similarly, if base object records are physically deleted, then records with HUB_STATE_IND of -9 are added to the history table (HIST) for the deleted base objects.


We’d like to hear from you!