XCC_SL_TR_HEADERS

This table stores the details of subledger transactions that have been involved in an override action. It contains the details of the last override action performed on a transaction and the outcome of the action.

Details

• Schema: FUSION

• Object owner: XCC

• Object type: TABLE

• Tablespace: TRANSACTION_TABLES

Primary Key

Name	Columns
XCC_SL_TR_HEADERS_PK	TRANSACTION_TYPE_CODE, SOURCE_HEADER_ID_1, SOURCE_HEADER_ID_2

Columns

Name	Datatype	Length	Precision	Not-null	Comments
TRANSACTION_TYPE_CODE	VARCHAR2	30		Yes	Type of the subledger or general ledger transaction.
SOURCE_HEADER_ID_1	VARCHAR2	30		Yes	Subledger or general ledger transaction primary key.
SOURCE_HEADER_ID_2	VARCHAR2	30		Yes	Subledger or general ledger transaction primary key.
OVERRIDE_ACTION	VARCHAR2	30		Yes	Last override action performed on the transaction.
ACTION_OUTCOME	VARCHAR2	30		Yes	Result of the last override action performed on the transaction.
CREATION_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the creation of the row.
CREATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who created the row.
LAST_UPDATED_BY	VARCHAR2	64		Yes	Who column: indicates 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.
LAST_UPDATE_LOGIN	VARCHAR2	32			Who column: indicates the session login associated to the user who last updated 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.

Indexes

Index	Uniqueness	Tablespace	Columns
XCC_SL_TR_HEADERS_U1	Unique	FUSION_TS_TX_IDX	TRANSACTION_TYPE_CODE, SOURCE_HEADER_ID_1, SOURCE_HEADER_ID_2