Multidomain MDM
- Multidomain MDM 10.3
- All Products
Physical Name
| MDM Hub Datatype (Size)
| Description
|
---|---|---|
ROWID_XREF
| NUMBER (38)
| Primary key that uniquely identifies this record in the cross-reference table.
|
PKEY_SRC_OBJECT
| VARCHAR2 (255)
| Primary key value from the source system. You must concatenate keys that contain multiple fields or multiple columns into a single key value. Use the MDM Hub internal cleanse process or an external cleanse process such as an ETL tool or some other data loading utility to concatenate the keys.
For admin system cross-reference records that are a result of an edit, the PKEY_SRC_OBJECT is SYS0:< ROWID_OBJECT >, where ROWID_OBJECT is the row ID of the edited record.
If the PKEY_SRC_OBJECT is SYS0:< ROWID_OBJECT > and the PUT_UPDATE_MERGE_IND is 1,
MDM Hub deletes the cross-reference record during unmerge.
|
ROWID_SYSTEM
| CHAR (14)
| Foreign key to C_REPOS_SYSTEM, which is the MDM Hub repository table that stores an MDM Hub identifier and description of each source system that can populate the ORS.
|
ROWID_OBJECT
| CHAR (14)
| Foreign key to the base object. The
MDM Hub assigns ROWID_OBJECT to the associated base object record.
|
ORIG_ROWID_OBJECT
| CHAR (14)
| The original ROWID_OBJECT of the cross-reference record.
|
GBID_Column_Name _GOV
| VARCHAR or INT
| The original global identifier value.
|
STG_ROWID_TABLE
| CHAR (14)
| Name of the staging table whose lookup configuration was used when the
MDM Hub loaded the cross-reference record.
|
S_ Foreign_Key_Column_Name | VARCHAR (255)
| A shadow column that contains the value used to look up the foreign key column.
|
SRC_ LUD
| TIMESTAMP
| Last source update date. The
MDM Hub updates SRC_ LUD when the source system sends an update to the cross-reference record.
|
CREATOR
| VARCHAR2 (50)
| User or process responsible for creating the cross-reference record.
|
CREATE_DATE
| TIMESTAMP
| Date on which the cross-reference record was created.
|
UPDATED_BY
| VARCHAR2 (50)
| User or process responsible for the most recent update to the cross-reference record.
|
LAST_UPDATE_DATE
| TIMESTAMP
| Date of the most recent update to any cell in the cross-reference record. The
MDM Hub updates LAST_UPDATE_DATE as applicable during the load process and consolidation process.
|
DELETED_IND
| NUMBER (38)
| Reserved for future use.
|
DELETED_BY
| VARCHAR2 (50)
| Reserved for future use.
|
DELETED_DATE
| TIMESTAMP
| Reserved for future use.
|
PERIOD_START_DATE
| TIMESTAMP
| Start date of an effective period of a record. A PERIOD_START_DATE value is required for cross-reference records of timeline-enabled base objects.
|
PERIOD_END_DATE
| TIMESTAMP
| End date of an effective period of a record. A PERIOD_END_DATE value is required for cross-reference records of timeline-enabled base objects.
|
PUT_UPDATE_MERGE_IND
| NUMBER (38)
| When the value is 1, indicates that a Put API call updated that particular record by specifying the ROWID_OBJECT value in the Put API request.
|
INTERACTION_ID
| NUMBER (38)
| For state-enabled base objects. Interaction identifier that is used to protect a pending cross-reference record from updates that are not part of the same process as the original cross-reference record.
|
HUB_STATE_IND
| NUMBER (38)
| For state-enabled base objects. Integer value indicating the state of the record. Valid values are:
The default value is 1.
|
PROMOTE_IND
| NUMBER (38)
| For state-enabled base objects. Integer value indicating the promotion status. The promote process uses PROMOTE_IND to determine whether to promote the record to an ACTIVE state. Valid values are:
The
MDM Hub does not change PROMOTE_IND to 0 if the promote process does not successfully promote the record.
|