XCC_TR_HEADERS
This table stores the transaction header attributes calling the budgetary control engine. There are foreign keys back to the calling subledger or general ledger transaction. Funds check calls maybe purged from this table.
Details
-
Schema: FUSION
-
Object owner: XCC
-
Object type: TABLE
-
Tablespace: TRANSACTION_TABLES
Primary Key
Name | Columns |
---|---|
XCC_TR_HEADERS_PK |
HEADER_NUM |
Columns
Name | Datatype | Length | Precision | Not-null | Comments | Status |
---|---|---|---|---|---|---|
HEADER_NUM | VARCHAR2 | 100 | Yes | Unique identifier for this transaction. | ||
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. | ||
TRANSACTION_NUMBER | VARCHAR2 | 240 | This columns contains the transaction number. | |||
SOURCE_ACTION_CODE | VARCHAR2 | 30 | Yes | Subledger commitment control action. Valid values depend upon the subledger and transaction type involved. | ||
DATA_SET_ID | NUMBER | 18 | Yes | Identifies the budgetary control transaction or group of transactions processed in a run. | ||
RESULT_CODE | VARCHAR2 | 30 | Yes | Status of the budgetary control transaction. | ||
ARRIVAL_ORDER | NUMBER | 18 | If multiple transactions are being processed at once, order in which they should be considered. | |||
DRAFT_FLAG | VARCHAR2 | 1 | Yes | Indicates whether this funds activity was attempted in draft mode or final mode. Funds activities attempted in draft mode do not reserve funds. They just check to see whether the funds activity would have passed. | ||
BUDGET_FLAG | VARCHAR2 | 1 | Yes | Indicates whether or not this is a budget transaction. | ||
OVERRIDE_FLAG | VARCHAR2 | 1 | Indicates if this transaction was overridden. | |||
LEDGER_ID | NUMBER | 18 | Ledger associated with this transaction, it is NULL for GL and XLA, as the ledger is a line level attribute there. It is also NULL for budgets. | |||
BUSINESS_UNIT_ID | NUMBER | 18 | Business unit of this transaction, it is only populated here when the transaction type or action does not support distribution level BUs. | |||
DESTINATION_TYPE_CODE | VARCHAR2 | 30 | Destination type is either Expense or Inventory. | |||
TRANSACTION_SOURCE_CODE | VARCHAR2 | 30 | Transaction source code is populated for projects only. | |||
DOCUMENT_TYPE_CODE | VARCHAR2 | 30 | Document type code is populated for projects only. | |||
JE_SOURCE_CODE | VARCHAR2 | 25 | General ledger journal source is populated for GL and XLA data only. | |||
LIQUIDATION_DATE_CODE | VARCHAR2 | 30 | Method via which the liquidation date should be obtained, it is used for PPM. | |||
PARTIAL_RESERVATION_FLAG | VARCHAR2 | 1 | Indicates if partial reservations are allowed. | |||
DATA_PURGED_FLAG | VARCHAR2 | 1 | Indicates that one or more lines have been purged for this transaction. Valid values are Y and N. | |||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | Active | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | Active | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | Active | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | Active | ||
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | Active | ||
OVERRIDABLE_CODE | VARCHAR2 | 30 | Indicates what type of override is available when running in override or override check mode. | |||
HEADER_GROUP_CODE | VARCHAR2 | 30 | Used to control whether multiple transactions should be grouped together for purposes of budegtary control. If provided, any transactions with the same value for this column will pass or fail budgetary control as a unit. | |||
FAILURE_REASON_CODE | VARCHAR2 | 30 | Reason for failure when budgetary control failed for some reason other than a failed budgetary control activity. Some potential reasons are: failure of related transactions, or a burdening failure. | |||
SUCCESS_REASON_CODE | VARCHAR2 | 30 | Reason for success when no budgetary control activity was generated. Potential success reasons are: budgetary control not being applicable, or no control budgets being applicable for this transaction. A transaction may still fail budgetary control, if a related transaction fails. |
Indexes
Index | Uniqueness | Tablespace | Columns | Status |
---|---|---|---|---|
XCC_TR_HEADERS_N1 | Non Unique | FUSION_TS_TX_DATA | DATA_SET_ID | Active |
XCC_TR_HEADERS_N2 | Non Unique | FUSION_TS_TX_DATA | TRANSACTION_TYPE_CODE, SOURCE_HEADER_ID_1, SOURCE_HEADER_ID_2 | Active |
XCC_TR_HEADERS_N3 | Non Unique | Default | TRANSACTION_NUMBER | |
XCC_TR_HEADERS_U1 | Unique | FUSION_TS_TX_DATA | HEADER_NUM | Active |