XCC_TR_HEADERS_HISTORY
This table contains budgetary control transactions that have been purged from the regular XCC_TR_HEADERS table. You must save the contents of this table for audit purposes. You can also archive them to some other storage location.
Details
-
Schema: FUSION
-
Object owner: XCC
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
XCC_TR_HEADERS_HISTORY_PK |
HEADER_NUM |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| 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 | Primary key for the subledger or general ledger transaction. | |
| SOURCE_HEADER_ID_2 | VARCHAR2 | 30 | Yes | Primary key for the subledger or general ledger transaction. | |
| TRANSACTION_NUMBER | VARCHAR2 | 240 | Transaction number for the subledger or general ledger. | ||
| SOURCE_ACTION_CODE | VARCHAR2 | 30 | Yes | Commitment control action for subledger or general ledger. Valid values depend on 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 whether the funds activity would have passed. Valid values are Y and N. | |
| BUDGET_FLAG | VARCHAR2 | 1 | Yes | Indicates if this is a budget transaction. Valid values are Y and N. | |
| OVERRIDE_FLAG | VARCHAR2 | 1 | Indicates if this transaction used an override. Valid values are Y and N. | ||
| LEDGER_ID | NUMBER | 18 | Ledger associated with this transaction. It is NULL for Oracle Fusion General Ledger and Oracle Fusion Subledger Accounting data, as the ledger is a line level attribute for those products. It is also NULL for budget adjustment data. | ||
| BUSINESS_UNIT_ID | NUMBER | 18 | Business unit of this transaction. It is NULL for Oracle Fusion General Ledger data, Oracle Fusion Subledger Accounting data, and budget adjustment data. It is also NULL when the transaction type or action supports line level business units. | ||
| DESTINATION_TYPE_CODE | VARCHAR2 | 30 | Destination type. Valid values are EXPENSE or INVENTORY. | ||
| TRANSACTION_SOURCE_CODE | VARCHAR2 | 30 | Transaction source. Populated for Oracle Fusion Project Portfolio Management data only. | ||
| DOCUMENT_TYPE_CODE | VARCHAR2 | 30 | Document type. Populated for Oracle Fusion Project Portfolio Management data only. | ||
| JE_SOURCE_CODE | VARCHAR2 | 25 | Journal source for general ledger. Populated for Oracle Fusion General Ledger and Oracle Fusion Subledger Accounting data only. | ||
| LIQUIDATION_DATE_CODE | VARCHAR2 | 30 | Method by which the liquidation date must be obtained. | ||
| PARTIAL_RESERVATION_FLAG | VARCHAR2 | 1 | Indicates if partial reservations are allowed. Valid values are Y and N. | ||
| OVERRIDABLE_CODE | VARCHAR2 | 30 | Indicates the type of override available when running in override or override check mode. | ||
| DATA_PURGED_FLAG | VARCHAR2 | 1 | Indicates whether one or more lines have been purged for this transaction. | ||
| HEADER_GROUP_CODE | VARCHAR2 | 30 | Code that groups multiple transactions for budgetary control. Transactions with this value will pass or fail budgetary control as a group. | ||
| FAILURE_REASON_CODE | VARCHAR2 | 30 | Reason code when budgetary control fails due to reason other than failed budgetary control activity. Possible reasons include failure of related transactions, failure of related lines, or burdening failure. | ||
| SUCCESS_REASON_CODE | VARCHAR2 | 30 | Reason code when budgetary control activity is not generated. Possible reasons include budgetary control is not applicable, or control budgets are not applicable to the transaction line. The transaction line may still fail budgetary control if a related transaction or a related transaction line fails. | ||
| 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_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. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| XCC_TR_HEADERS_HISTORY_U1 | Unique | Default | HEADER_NUM |