Search Results fv_be_trx_sub_types




Overview
Explore in AI Chat

Overview

The FV_BE_TRX_SUB_TYPES table is a Federal Financials (FV) product table in Oracle E-Business Suite that stores the sub types associated with a budget transaction type. It functions as the base table for the detail block of the Define Budget Transaction Types form, providing the granular classification layer beneath the transaction type definition maintained in FV_BE_TRANSACTION_TYPES. In the standard budgeting workflow for federal agencies, transaction types categorize budget actions (for example, appropriations, apportionments, or allotments), while sub types further subdivide those actions for reporting, validation, and posting purposes. The table is owned by the FV schema and is documented as VALID in both 12.1.1 and 12.2.2 reference material, with a documented physical schema of 12 columns.

Under a heuristic Data Vault classification mined from the foreign key structure, the table is modeled as a standalone object. It carries a foreign key to FV_BE_TRANSACTION_TYPES but does not itself appear as the parent in any documented FK relationship within the metadata. A practical modeling suggestion would be to treat it as a satellite attached to the parent transaction type hub, since it stores descriptive and flag-based attributes (description, default flag, enabled flag, authority type) that are functionally dependent on the transaction type and sub type combination. It is not itself a hub or a link based on the documented relationships.

Key Information Stored

The table contains 12 documented columns. The most significant are:

  • BE_TT_ID — Foreign key to FV_BE_TRANSACTION_TYPES, identifying the parent budget transaction type to which the sub type belongs. This is the primary join column for any query that needs transaction type context.
  • SUB_TYPE — The sub type code or value itself, the core business identifier of the record.
  • LEDGER_ID — Identifies the ledger context for which the sub type is defined, supporting multi-ledger deployments where sub types may vary by ledger.
  • DESCRIPTION — Free-text descriptive name for the sub type, used in form display and reporting.
  • DEFAULT_FLAG — Indicates whether this sub type is the default for the associated transaction type.
  • ENABLED_FLAG — Controls whether the sub type is active and selectable in transaction entry.
  • AUTHORITY_TYPE — Captures the authority classification associated with the sub type, supporting federal authority-based reporting.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified the record and when.

No surrogate primary key column is documented separately in the metadata. The unique index FV_BE_TRX_SUB_TYPES_U1 on (SUB_TYPE, BE_TT_ID) establishes the business-key candidate, meaning the combination of sub type and transaction type must be unique. This composite key should be treated as the natural identifier for the record, with LEDGER_ID providing additional scoping where applicable.

Common Use Cases and Queries

Typical use cases include validating that a sub type is enabled before allowing it to be selected during budget transaction entry, reporting the set of sub types configured per transaction type, and identifying the default sub type for a given transaction type during data entry or interface processing.

A common query pattern retrieves all enabled sub types for a specific transaction type:

  • SELECT sub_type, description, default_flag FROM fv.fv_be_trx_sub_types WHERE be_tt_id = :p_tt_id AND enabled_flag = 'Y';

To find the default sub type for a transaction type, filter on DEFAULT_FLAG = 'Y' in addition to the BE_TT_ID predicate. Reporting queries frequently join back to FV_BE_TRANSACTION_TYPES to present the transaction type name alongside the sub type description. Ledger-scoped reporting adds a LEDGER_ID predicate to restrict results to the relevant ledger. Data migration and interface routines use the unique composite key (SUB_TYPE, BE_TT_ID) as the matching criterion when loading or updating sub type definitions.

Related Objects

The most significant related objects based on documented FK relationships and the form usage described in the metadata are:

  • FV_BE_TRANSACTION_TYPES — Parent table referenced by FV_BE_TRX_SUB_TYPES.BE_TT_ID. This is the primary relationship and the principal join in nearly all queries.
  • FV_BE_TRX_SUB_TYPES_U1 — Unique index on (SUB_TYPE, BE_TT_ID), enforcing the business key.
  • Define Budget Transaction Types form (FV) — The application form whose detail block is based directly on this table.

Additional dependencies may exist in budgeting validation logic, budget execution programs, and federal reporting extracts that consume sub type configuration, but the documented metadata supports only the FV_BE_TRANSACTION_TYPES relationship as an explicit foreign key.