Search Results fv_be_trx_sub_types_u1

Overview

The FV.FV_BE_TRX_SUB_TYPES table is a transaction configuration table within the Oracle E-Business Suite Federal Financials (FV) schema. It stores the valid sub-types associated with a given budget execution transaction type. The table functions as the base table behind the detail block of the Define Budget Transaction Types form, and the ETRM metadata identifies it as a new table introduced for the budget execution (BE) transaction type framework. Each row defines one permitted sub-type for a parent transaction type, scoped by ledger.

From a Data Vault modeling perspective, the heuristic classification of this table is standalone, indicating it does not assume a hub/link/satellite role in the mined relationship structure. It does, however, carry a foreign key to FV_BE_TRANSACTION_TYPES, so it may alternatively be modeled as a satellite of the transaction type parent if a dimensional or Data Vault design is being considered.

Key Information Stored

The table comprises 12 documented columns. The most significant include:

• BE_TT_ID (NUMBER 15, mandatory): Transaction Type identifier and foreign key to FV_BE_TRANSACTION_TYPES, linking each sub-type to its parent transaction type.
• SUB_TYPE (VARCHAR2 30): The transaction sub-type code; the primary business identifier.
• LEDGER_ID (NUMBER 15): Ledger identifier, enabling ledger-specific sub-type definitions.
• DESCRIPTION (VARCHAR2 180): Descriptive text for the transaction sub-type.
• DEFAULT_FLAG (VARCHAR2): Indicates whether the sub-type is the default for the parent transaction type.
• ENABLED_FLAG (VARCHAR2): Controls whether the sub-type is active and selectable.
• AUTHORITY_TYPE: Documented in the physical schema, providing an additional classification attribute.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN: Standard WHO audit columns capturing row creation and modification metadata, with foreign key references to FND_USER and FND_LOGINS.

No standalone surrogate primary key column is documented; the unique index FV_BE_TRX_SUB_TYPES_U1 on (SUB_TYPE, BE_TT_ID) serves as the business-key candidate, enforcing uniqueness of sub-type within a transaction type. The index resides in the APPS_TS_TX_IDX tablespace, while table data is stored in APPS_TS_TX_DATA with PCT Free 10.

Common Use Cases and Queries

Typical use cases include populating sub-type list-of-values (LOVs) on budget execution entry forms, validating user-entered sub-types against enabled definitions, and reporting on transaction sub-type configuration by ledger. A representative query retrieves all enabled sub-types for a transaction type:

• SELECT SUB_TYPE, DESCRIPTION, DEFAULT_FLAG FROM FV.FV_BE_TRX_SUB_TYPES WHERE BE_TT_ID = :tt_id AND ENABLED_FLAG = 'Y';
• Joining to the parent to list configuration: SELECT t.TRANSACTION_TYPE, s.SUB_TYPE, s.DESCRIPTION FROM FV.FV_BE_TRX_SUB_TYPES s, FV.FV_BE_TRANSACTION_TYPES t WHERE s.BE_TT_ID = t.BE_TT_ID;
• Identifying the default sub-type per transaction type uses DEFAULT_FLAG = 'Y' as a filter.

Related Objects

The principal related object is FV_BE_TRANSACTION_TYPES, to which BE_TT_ID refers as a foreign key. Because the ETRM dependency section lists no further inbound or outbound references, the table is largely self-contained. Related supporting objects commonly joined in practice include FND_USER (via CREATED_BY/LAST_UPDATED_BY), FND_LOGINS (via LAST_UPDATE_LOGIN), and the ledger table referenced through LEDGER_ID. The APPS.FV_BE_TRX_SUB_TYPES synonym provides the application-layer access point documented as referencing this object.