Search Results fv_be_transaction_types_u2

Overview

The table FV.FV_BE_TRANSACTION_TYPES is a reference and configuration table within the Oracle E-Business Suite Budget Execution (BE) module of ETRM (Enterprise Territory and Revenue Management), residing in the FV schema. It defines the appropriation transaction types available to a set of books and budget level, forming part of the budgetary control and funds-checking framework introduced in EBS 12.1.1 and extended in 12.2.2. Each row represents a named appropriation transaction type (for example, commitment, obligation, or expenditure) together with descriptive and behavioral flags that govern how Federal or public-sector appropriations are processed, rolled up, and validated.

Under a heuristic Data Vault classification, this object is best modeled as a hub, since its primary key BE_TT_ID is a surrogate identifier that anchors multiple downstream transactional and reference tables. It functions as a standalone master entity rather than a link or satellite, reflecting its role as an authoritative catalogue of transaction types rather than a relationship or descriptive history store.

Key Information Stored

The table contains 37 documented columns, of which the most significant are:

• BE_TT_ID — the system-generated surrogate primary key, enforced by the unique index FV_BE_TRANSACTION_TYPES_U2. This is the column referenced by foreign keys in child tables.
• SET_OF_BOOKS_ID — identifies the ledger or set of books to which the transaction type belongs.
• BUDGET_LEVEL_ID — identifies the budget level associated with the transaction type.
• APPRN_TRANSACTION_TYPE — the business name of the appropriation transaction type.
• DESCRIPTION — a user-facing description of the transaction type.
• ROLLUP_TYPE — deprecated column relating to appropriation rollup; documented as obsolete following the BE redesign.
• ROLLUP_AMOUNT — flag indicating whether the amount should roll up to the ROLLUP_TYPE.
• LEGISLATIVE_INDICATOR, ADVANCE_FLAG, TRANSFER_FLAG, UPDATE_FLAG — behavioral flags controlling how the type participates in legislative, advance, transfer, and update processing.
• PUBLIC_LAW_CODE_FLAG, SUB_TYPE_FLAG, ENABLED_FLAG, AUTHORITY_TYPE — flags governing authority validation, sub-type usage, and whether the type is active.
• DEFAULT_TRANSACTION_CODE — default code applied when this transaction type is used.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments supporting extensibility.

The business key is enforced by the composite unique index FV_BE_TRANSACTION_TYPES_U1 across SET_OF_BOOKS_ID, BUDGET_LEVEL_ID, and APPRN_TRANSACTION_TYPE, meaning the pairing of ledger, budget level, and transaction type name must be unique. Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide audit and concurrency tracking.

Common Use Cases and Queries

Typical usage involves validating or reporting on the transaction types configured for a given ledger and budget level, and joining to child tables that reference BE_TT_ID. A representative query listing enabled transaction types would be:

• SELECT be_tt_id, apprn_transaction_type, description FROM fv.fv_be_transaction_types WHERE set_of_books_id = :sob AND enabled_flag = 'Y';
• Joining to FV_BE_ACCOUNT_PAIRS, FV_BE_TRX_CODES, and FV_BE_TRX_SUB_TYPES on BE_TT_ID to resolve transaction codes and sub-types per transaction type.
• Reporting on rollup behavior via ROLLUP_AMOUNT and the authority-driven flags (LEGISLATIVE_INDICATOR, AUTHORITY_TYPE) to support appropriation reporting and funds checking.

Related Objects

The following children reference FV_BE_TRANSACTION_TYPES.BE_TT_ID:

• FV_BE_ACCOUNT_PAIRS.BE_TT_ID — account pair mapping for each transaction type.
• FV_BE_TRX_CODES.BE_TT_ID — transaction codes associated with a transaction type.
• FV_BE_TRX_SUB_TYPES.BE_TT_ID — sub-type definitions associated with a transaction type.

These downstream tables together consume the surrogate key as a foreign key, reinforcing the hub modeling recommendation.

Note: As documented, this object is Oracle Internal Use Only; access should be limited to standard Oracle Applications programs.