XCC_BC_SOURCE_DEFINITIONS
This table stores the configuration of how transaction types, actions affect budgetary control balances
Details
-
Schema: FUSION
-
Object owner: XCC
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
Name | Columns |
---|---|
XCC_BC_SOURCE_DEFINITIONS_PK |
TRANSACTION_TYPE_CODE, SOURCE_ACTION_CODE |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
TRANSACTION_TYPE_CODE | VARCHAR2 | 30 | Yes | Transaction type defined for budgetary control | |
SOURCE_ACTION_CODE | VARCHAR2 | 30 | Yes | Represents an action performed on a Transaction (e.g. Approve). | |
RESERVATION_CATEGORY_CODE | VARCHAR2 | 30 | The reservation category used for that specific action and transaction type. It is the same as the column name in the balances table. It refers to a lookup that would provide a label for reporting. | ||
BUSINESS_FLOW_CODE | VARCHAR2 | 30 | Yes | Represents the Business Flow such as Ledger, Procure To Pay, Project Portfolio Management. | |
BUSINESS_FUNCTION_CODE | VARCHAR2 | 100 | Yes | Represents a Business Function. | |
BC_ACTION_CODE | VARCHAR2 | 30 | Yes | Budgetary control action such as reserve or check. | |
BUCKET_CODE | VARCHAR2 | 30 | Bucket code to which the resulting budgetary action will post the amount to. It has the same name as the column name in the balances table and it refers to a lookup which can then be used as a reporting label. | ||
FORCE_PASS_FLAG | VARCHAR2 | 1 | Yes | Yes/No Flag to indicate whether or not to run that budgetary control action in force pass mode (i.e. won't block even if there isn't enough Funds available). | |
EXTRACT_VIEW_NAME | VARCHAR2 | 30 | Yes | Name of the database view that is used to extract the transaction information needed to budgetary control a transaction. | |
BURDENING_EXTRACT_VIEW_NAME | VARCHAR2 | 30 | Name of the database view that is used to extract the burdening information needed to budgetary control a project transaction. | ||
REVERSE_SIGN_FLAG | VARCHAR2 | 1 | Yes | Indicates whether or not we need to flip the amount sign.It is a Yes/No flag. | |
BACKING_TRANSACTION_TYPE_CODE | VARCHAR2 | 30 | Code of the backing transaction type. | ||
LIQUIDATION_TYPE_CODE | VARCHAR2 | 30 | Code indicating the type of liquidation (e.g. None, Full or Safe liquidation). | ||
RELEASE_UNLIQUIDATED_AMT_FLAG | VARCHAR2 | 1 | Yes | Yes/No flag for non liquidated amount processing. | |
MULTI_BU_FLAG | VARCHAR2 | 1 | Yes | Multi Business Unit indicator. It is a Yes/No flag. | |
USE_BUDGET_DATE_FOR_UNDO_FLAG | VARCHAR2 | 1 | Yes | Code to indicate whether or not to use the budget date for undo processing. It is a Yes/No flag. | |
PRE_BC_HOOK_API_NAME | VARCHAR2 | 61 | Name of the API to be called by the Budgetary Control Engine prior to perform any action. | ||
POST_BC_HOOK_API_NAME | VARCHAR2 | 61 | Name of the API to be called by the Budgetary Control Engine after performing the requested action. | ||
FAILURE_BC_HOOK_API_NAME | VARCHAR2 | 61 | Name of the API to be called by the Budgetary Control Engine in case of failure. | ||
REPROCESS_POST_HOOK_API_NAME | VARCHAR2 | 61 | Name of API to be called by the budgetary control engine after reprocessing. | ||
FAIL_UPON_CLOSE_PENDING_FLAG | VARCHAR2 | 1 | Yes | Indicates whether the budgetary control should fail when the control budget's period status is Close Pending. | |
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. | |
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. | ||
SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
ORA_SEED_SET1 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET1. Context values are Y or N. | |
ORA_SEED_SET2 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET2. Context values are Y or N. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
XCC_BC_SOURCE_DEFINITIONS | xcc_bc_business_functions | BUSINESS_FUNCTION_CODE |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
XCC_BC_SOURCE_DEFINITIONS_PK | Unique | Default | TRANSACTION_TYPE_CODE, SOURCE_ACTION_CODE, ORA_SEED_SET1 |
XCC_BC_SOURCE_DEFINITIONS_PK1 | Unique | Default | TRANSACTION_TYPE_CODE, SOURCE_ACTION_CODE, ORA_SEED_SET2 |