Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Staging Table Columns

Staging Table Columns

Staging tables contain system columns and user-defined columns.

System Staging Table Columns

The Schema Manager creates and maintains the system staging table columns.
The following table describes the system columns of staging tables: 
Physical Name
MDM Hub Data type (Size)
Description
PKEY_SRC_OBJECT
VARCHAR (255)
Primary key from the source system. The PKEY_SRC_OBJECT value must be unique. If the source record does not have a single unique column, concatenate the values from multiple columns to uniquely identify the record.
ROWID_OBJECT
CHAR (14)
Primary key from
MDM Hub
.
MDM Hub
assigns a unique ROWID_OBJECT value during the stage process.
DELETED_IND
INT
Reserved for future use.
DELETED_DATE
TIMESTAMP
Reserved for future use.
DELETED_BY
VARCHAR (50)
Reserved for future use.
LAST_UPDATE_DATE
TIMESTAMP
Date when the source system last updated the record. For base objects, LAST_UPDATE_DATE populates LAST_UPDATE_DATE and SRC_LUD in the cross-reference table, and based on trust settings might also populate LAST_UPDATE_DATE in the base object table.
UPDATED_BY
VARCHAR (50)
User or process responsible for the most recent update.
CREATE_DATE
TIMESTAMP
Date on which the record was created.
PERIOD_START_DATE
TIMESTAMP
Start date of an effective period of a record. PERIOD_START_DATE value is required for timeline-enabled base objects.
PERIOD_END_DATE
TIMESTAMP
End date of an effective period of a record. PERIOD_END_DATE value is required for timeline-enabled base objects.
CREATOR
VARCHAR (50)
User or process responsible for creating the record.
SRC_ROWID
VARCHAR (30)
Database internal Row ID column that traces records back to the landing table from the staging table.
HUB_STATE_IND
INT
For state-enabled base objects. Integer value indicating the state of this record. The following values are valid:
  • 0=Pending
  • 1=Active
  • -1=Deleted
The default value is 1.
VERSION_SEQ
INT
For timeline-enabled base objects, value shows the order that records with the same primary source key were loaded into the stage table. For base objects that are not timeline-enabled, this value must be 1.
The VERSION_SEQ column is mapped to from a user-defined landing table column. The landing table column contains the version sequence for records with the same primary key but different period start and period end dates.

User-defined Staging Table Columns

To avoid decreased performance caused by unnecessary trust calculations, ensure that the columns you add to staging tables come from specific source systems.
When you add columns from source systems, you can restrict the trust columns to columns that have data from multiple staging tables. When staging tables have columns from specific source systems, you do not treat every column as if it comes from every source system. You do not need to add trust for each column. Also, you do not need validation rules to downgrade the trust on null values for all of the sources that do not provide values for the columns.

0 COMMENTS

We’d like to hear from you!