Results for “transaction_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FV_BE_TRX_CODES is a Federal Financials (FV) module table that stores the transaction codes associated with a budget transaction type. It functions as the base table for the detail block of the Define Budget Transaction Types form within Oracle E-Business Suite 12.1.1 and 12.2.2. The table resides in the FV schema with status VALID and contains nine documented columns. Its role is to define the valid combinations of transaction codes and transaction types used in federal budget execution processing, enabling the application to validate and categorize budget transactions consistently across a set of books.

Based on the heuristic Data Vault classification mined from its foreign key structure, FV_BE_TRX_CODES is best modeled as a link object, since it resolves and binds two parent entities: FV_BE_TRANSACTION_CODES and FV_BE_TRANSACTION_TYPES. This is a modeling suggestion rather than a mandated design.

Key Information Stored

The table captures the association between a transaction type and its permitted transaction codes. The most significant columns include:

• BE_TC_ID — Foreign key to FV_BE_TRANSACTION_CODES; identifies the transaction code.
• BE_TT_ID — Foreign key to FV_BE_TRANSACTION_TYPES; identifies the parent transaction type. Together with TRANSACTION_CODE it forms the unique business key.
• SET_OF_BOOKS_ID — Identifies the ledger/set of books under which the transaction code association applies.
• TRANSACTION_CODE — The business-facing code value associated with the transaction type.
• CREATION_DATE, CREATED_BY — Standard audit columns capturing row creation metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification.

The surrogate primary key is not explicitly documented; the unique index FV_BE_TRX_CODES_U1 on (BE_TT_ID, TRANSACTION_CODE) serves as the business-key candidate, ensuring no duplicate code per transaction type. The BE_TC_ID and BE_TT_ID columns act as the foreign-key pairing that defines the link.

Common Use Cases and Queries

Typical use cases include validating that a transaction code is permitted for a given transaction type, driving the Define Budget Transaction Types form, and producing conversion or reconciliation reports for federal budget data.

• Listing all transaction codes for a transaction type:

SELECT tt.transaction_type, tc.transaction_code
FROM   fv.fv_be_trx_codes tc,
       fv.fv_be_transaction_types tt
WHERE  tc.be_tt_id = tt.be_tt_id
AND    tc.set_of_books_id = :p_sob_id;

• Checking whether a specific code is valid for a type:

SELECT COUNT(*)
FROM   fv.fv_be_trx_codes
WHERE  be_tt_id = :p_tt_id
AND    transaction_code = :p_code;

Reporting extracts frequently join to FV_BE_TRANSACTION_CODES to retrieve code descriptions for display, and to FV_BE_TRANSACTION_TYPES for type-level attributes. Filtering by SET_OF_BOOKS_ID is essential in multi-ledger environments.

Related Objects

The following objects are most significant in relation to FV_BE_TRX_CODES:

• FV_BE_TRANSACTION_CODES — Referenced via BE_TC_ID; provides the master transaction code definition.
• FV_BE_TRANSACTION_TYPES — Referenced via BE_TT_ID; the parent transaction type definition and owner of the detail-block form relationship.
• Define Budget Transaction Types form — The Oracle Forms UI for which this table is the base detail block.
• FND_SET_OF_BOOKS (GL_SETS_OF_BOOKS) — Provides the ledger context for SET_OF_BOOKS_ID.
• FND audit columns — Standard WHO columns link to FND_USER for CREATED_BY and LAST_UPDATED_BY resolution.

These relationships confirm FV_BE_TRX_CODES as a configuration-level link table central to federal budget transaction type setup.