ZCH_DEDUP_HEADERS

Details

Schema: FUSION
Object owner: FUSION
Object type: TABLE
Tablespace: FUSION_TS_TX_DATA

Primary Key

Name	Columns
ZCH_DEDUP_HEADERS_A_PK	DEDUP_HEADER_ID

Columns

Name	Datatype	Length	Precision	Not-null	Comments
DEDUP_HEADER_ID	NUMBER		18	Yes	Primary key
MASTER_ID	NUMBER		18	Yes	The survivor Id for the deduplication request.
DEDUP_REQ_NUMBER	VARCHAR2	64			Request Number
DEDUP_REQ_STATUS	VARCHAR2	30		Yes	Status of the request.
OBJ_NAME	VARCHAR2	30		Yes	The merge object name, like party, account etc.
OBJ_DEF	VARCHAR2	100			The merge object definition, whole package name
DEDUP_TYPE_CODE	VARCHAR2	30			Same party merge or party site merge.
DEDUP_REASON_CODE	VARCHAR2	30			Merge reason
ASSIGNED_USER_ID	VARCHAR2	64			Assigned to User
REQUEST_ID	NUMBER		18		Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row.
JOB_DEFINITION_NAME	VARCHAR2	100			Enterprise Service Scheduler: indicates the name of the job that created or last updated the row.
JOB_DEFINITION_PACKAGE	VARCHAR2	900			Enterprise Service Scheduler: indicates the package name of the job that created or last updated the row.
CREATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who created the row.
CREATION_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the creation of the row.
LAST_UPDATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who last updated the row.
LAST_UPDATE_LOGIN	VARCHAR2	32			Who column: indicates the session login associated to the user who last updated the row.
LAST_UPDATE_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the last update of the row.
OBJECT_VERSION_NUMBER	NUMBER		9	Yes	Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
USER_LAST_UPDATE_DATE	TIMESTAMP				Disconnected Mobile: indicates the date and time of the last update of the row. This value is different from LAST_UPDATE_DATE if the update originally happened in a different database (i.e. a different mobile database or the server).
CONFLICT_ID	NUMBER		18	Yes	Disconnected Mobile: this value is used to guarantee the uniqueness of the row when duplicates are created in different databases (i.e. mobile databases or the server).
DEDUP_REQ_SOURCE	VARCHAR2	30			The creation source of the merge request, such as user created, bulk import
REVIEWED_FLAG	VARCHAR2	1			To indicate that the record is reviewed by data steward
REVIEW_REQUIRED_FLAG	VARCHAR2	1			To indicate that the record needs to be reviewed by data steward
RULE_BASED_MASTER_FLAG	VARCHAR2	1			To indicate the master is set by rules
PROCESSED_USER_ID	NUMBER		18		The person who processed the request
PROCESSED_DATE	TIMESTAMP				The date the request is submitted
CREATION_SRC_BATCH_ID	NUMBER		18		Store the creation source batch Id, for example, the import batch Id or identification batch Id.
DEDUP_REQ_NAME	VARCHAR2	500		Yes	Deduplication request name
REQUESTED_USER_ID	NUMBER		18		This column stores the actual user who created the record.
DESCRIPTION	VARCHAR2	100			Description
COMMENTS	VARCHAR2	2000			Comments

Indexes

Index	Uniqueness	Tablespace	Columns
ZCH_DEDUP_HEADERS_A_U1	Unique	Default	DEDUP_HEADER_ID