Search Results fv_be_transaction_type_pk1

Overview

FV_BE_TRANSACTION_TYPES is the base configuration table for appropriation transaction types within the Oracle E-Business Suite Federal Financials (FV) product family. It stores the user-defined budget and appropriation transaction type definitions that govern how budget execution activity is categorized, rolled up, and posted against a given set of books and budget level. The table is the underlying data store for the Define Budget Transaction Type form, which administrators use to establish the allowable transaction categories, their rollup behavior, and their relationship to legislative and regulatory controls.

From a data-modeling perspective, the metadata classifies this object as a standalone entity, indicating that it neither resolves into a pure hub, link, nor satellite pattern and functions as an independent reference table. Each record represents a single appropriation transaction type scoped to a set of books and budget level, making it a foundational lookup consumed by downstream federal budget execution processing.

Key Information Stored

The table contains 37 documented columns. The most significant include:

• BE_TT_ID — the surrogate primary key (FV_BE_TRANSACTION_TYPE_PK1) that uniquely identifies each transaction type.
• APPRN_TRANSACTION_TYPE — the appropriation transaction type identifier, which combines with set of books and budget level as a business-key candidate (FV_BE_TRANSACTION_TYPES_U1).
• SET_OF_BOOKS_ID — the ledger context restricting the definition to a specific accounting set of books.
• BUDGET_LEVEL_ID — the budget level to which the transaction type applies; part of the unique business key.
• DESCRIPTION — the user-facing name of the transaction type.
• ROLLUP_TYPE and ROLLUP_AMOUNT — control how transaction amounts consolidate into higher-level budget categories.
• DEFAULT_TRANSACTION_CODE — the transaction code applied by default during entry.
• LEGISLATIVE_INDICATOR, PUBLIC_LAW_CODE_FLAG, and AUTHORITY_TYPE — flags and attributes supporting statutory and appropriations-law reporting.
• ADVANCE_FLAG, TRANSFER_FLAG, UPDATE_FLAG, and SUB_TYPE_FLAG — behavioral controls governing whether the type supports advances, transfers, updates, or sub-types.
• ENABLED_FLAG — determines whether the type is active for use.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns for extensible client-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on configuration validation and budget execution reporting. A common query retrieves all enabled transaction types for a ledger:

• SELECT BE_TT_ID, APPRN_TRANSACTION_TYPE, DESCRIPTION, ROLLUP_TYPE FROM FV_BE_TRANSACTION_TYPES WHERE SET_OF_BOOKS_ID = :p_sob AND ENABLED_FLAG = 'Y';

Reporting queries frequently join this table to FV_BE_TRX_CODES and FV_BE_TRX_SUB_TYPES to resolve transaction code hierarchies for a given budget level, or to FV_BE_ACCOUNT_PAIRS to confirm which account pairings are configured for each transaction type. Administrators also use it to audit which Legislative Indicator or Public Law Code flags are set for statutory compliance reviews.

Related Objects

The following objects reference FV_BE_TRANSACTION_TYPES through the shared BE_TT_ID column:

• FV_BE_ACCOUNT_PAIRS — links account pair definitions to a transaction type (BE_TT_ID).
• FV_BE_TRX_CODES — stores transaction codes belonging to each transaction type (BE_TT_ID).
• FV_BE_TRX_SUB_TYPES — defines sub-types subordinate to a parent transaction type (BE_TT_ID).

These child tables collectively form the budget execution configuration hierarchy, with FV_BE_TRANSACTION_TYPES acting as the parent reference that governs code, sub-type, and account pairing setup for federal appropriation processing.