XCC_SL_TR_OVERRIDERS
This table stores users that can override a subledger or general ledger transaction. This table only gets populated when running the budgetary control engine in override or override check mode and the current user cannot override the failed transactions.
Details
-
Schema: FUSION
-
Object owner: XCC
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
XCC_SL_TR_OVERRIDERS_PK |
TRANSACTION_TYPE_CODE, SOURCE_HEADER_ID_1, SOURCE_HEADER_ID_2, USER_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
TRANSACTION_TYPE_CODE | VARCHAR2 | 30 | Yes | Identifies the type of 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. | |
USER_ID | NUMBER | 18 | Yes | User who can override the Subledger or General Ledger transaction. | |
DATA_SET_ID | NUMBER | 18 | Yes | Identifies the budgetary control engine run that created this 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. | |
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_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update 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. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
XCC_SL_TR_OVERRIDERS_U1 | Unique | Default | TRANSACTION_TYPE_CODE, SOURCE_HEADER_ID_1, SOURCE_HEADER_ID_2, USER_ID |