Budgetary Control Validation Transactions
The budgetary control validation transactions view object contains transaction header details for each budgetary control validation request.
Data Store Key : FscmTopModelAM.FinExtractAM.XccBiccExtractAM.TransactionHeaderExtractPVO
Primary Keys : HeaderNum
Initial Extract Date : CreationDate
Incremental Extract Date : LastUpdateDate
Attributes
This table provides the list of exposed attributes and their descriptions.
| Name | Description |
|---|---|
| ArrivalOrder | An incremental number to identify the order at which transactions are submitted for budgetary control validations. |
| BudgetFlag | Budget Transaction |
| BusinessUnitId | The identifier of the business unit of the transaction submitted for budgetary control validations if it's provided by the transaction distribution. |
| CreatedBy | The user who created the budgetary control validation transaction. |
| CreationDate | The date and time when the budgetary control validation transaction was created. |
| DataPurgedFlag | Indicates whether one or more lines have been purged for this transaction. |
| DataSetId | The unique identifier of the budgetary control validation attempt. |
| DestinationTypeCode | The receiving destination type of the source transaction that's originated from Procurement. Valid values are EXPENSE or INVENTORY. |
| DocumentTypeCode | The code representing the document type of the Project Management transaction. |
| DraftFlag | Indicates whether the budgetary control validation transaction was attempted in draft or final mode. The draft mode only validates the transaction. The final mode reserves funds if the transaction passes the validation. |
| FailureReasonCode | The code that indicates the reason the transaction failed budgetary control validation when it isn't due to a control budget failure. A list of accepted values is defined in the lookup type ORA_XCC_BC_SC_FAIL_REASONS. |
| HeaderGroupCode | The code that indicates the group to which the transaction may belong within a budgetary control validation process. If a transaction belongs to a group, the entire group must pass or fail budgetary control as a unit. |
| HeaderNum | Number assigned to a source transaction within a budgetary control validation attempt. |
| JeSourceCode | The journal source for general ledger and subledger accounting transactions. |
| LastUpdateDate | The date and time when the budgetary control validation transaction was last updated. |
| LastUpdateLogin | The session login associated with the user who last updated the budgetary control validation transaction. |
| LastUpdatedBy | The user who last updated the budgetary control validation transaction. |
| LedgerId | The unique identifier of the ledger. |
| LiquidationDateCode | The code of the method of determining the liquidation date for Project Management transactions. |
| OverridableCode | The code for the type of override that's available when the budgetary control validation is processed in override or override check mode. Valid values are NONE, OTHER, and UNOVERRIDABLE. |
| OverrideFlag | Indicates whether the budgetary control validation transaction is overridden. |
| PartialReservationFlag | Indicates whether partial reservation is allowed. |
| ResultCode | Header Result Code |
| SourceActionCode | The code of the action performed on the source transaction. A list of accepted values are defined in the lookup type XCC_TRANSACTION_TYPE_ACTION. |
| SourceHeaderId1 | The source transaction identifier 1. |
| SourceHeaderId2 | The source transaction identifier 2. |
| SuccessReasonCode | The code that indicates the acceptable reason the transaction didn't impact any control budget. The transaction could fail budgetary control validation if the transaction belongs to a group and a related transaction within the group fails. A list of accepted values is defined in the lookup type ORA_XCC_BC_SC_FAIL_REASONS. |
| TransactionNumber | The source transaction number for the budgetary control validation attempt. |
| TransactionSourceCode | The code for the source of the budgetary control validation transaction. Valid values are PROJECTS and NULL. PROJECTS indicates the source of the budgetary control validation transaction is Project Management. |
| TransactionTypeCode | The source transaction type code. A list of accepted values are defined in the lookup type XCC_TRANSACTION_TYPES. |