Search Results fv_be_transaction_codes

Overview

FV_BE_TRANSACTION_CODES is a Federal Financials (FV) reference table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores transaction code information used when posting budget transactions to the General Ledger. In the federal budgeting model, budget entry and budget execution activity must be accompanied by valid transaction codes (sometimes referred to as TC, or budget transaction identifiers) so that downstream commitments, obligations, and expenditures are properly classified. This table supplies the authoritative set of those codes and their associated attributes to the budget execution posting routines.

Within the standard FV budget execution flow, the table acts as a lookup or validation source. When a budget transaction is prepared for transfer to GL, the posting logic consults FV_BE_TRANSACTION_CODES to resolve the appropriate transaction code and its descriptive or accounting-related attributes before the journal entry is generated. Because it is a reference object rather than a transactional fact table, it is typically maintained as seed or setup data rather than being heavily updated during normal processing.

The ETRM metadata classifies this object, by heuristic mining of its foreign-key structure, as a standalone table. In Data Vault terms, this suggests a hub-style reference entity: it holds a stable business concept (the transaction code) with its own surrogate key, and other tables reference it rather than the reverse. No parent foreign keys were identified, reinforcing its role as an independent reference point for the Federal Financials budget execution model.

Key Information Stored

The documented metadata identifies the following key structural elements:

• BE_TC_ID — the primary key column, defined by the constraint FV_BE_TRANSACTION_CODES_PK1. This is the surrogate identifier for each transaction code record and the value referenced by dependent tables.
• The table as a whole is described as holding "transaction code information for posting the budget transaction to General Ledger." The specific descriptive columns beyond BE_TC_ID are not enumerated in the supplied documentation, but based on the table's stated purpose they would include the transaction code value itself, a description, and enablement/status attributes.

Only BE_TC_ID is explicitly confirmed as a column in the ETRM excerpt. It serves as the surrogate primary key. No unique indexes (business-key candidates) are listed in the provided metadata, so the natural business key — presumably the transaction code value visible to users — is not documented here and should be confirmed by inspecting the physical table definition in the target instance.

Note that the metadata record states "Not implemented in this database," indicating that this object was not present in the specific environment from which the ETRM documentation was generated. Its structure should therefore be verified against the actual FV schema where it is installed.

Common Use Cases and Queries

Typical uses center on validation, reporting, and transformation lookups during budget-to-GL posting:

• Populating a value set or list of values for budget transaction entry.
• Validating a transaction code before a budget journal is submitted.
• Joining to dependent transaction records to enrich budget execution reports with code descriptions.
• Auditing which transaction codes are active versus obsolete before period close.

A representative join pattern follows the documented FK relationship:

SELECT t.be_tc_id, d.* FROM fv_be_transaction_codes t, fv_be_trx_codes d WHERE t.be_tc_id = d.be_tc_id;

Related Objects

The metadata documents a single referencing table, which is the most significant related object:

• FV_BE_TRX_CODES — references FV_BE_TRANSACTION_CODES via BE_TC_ID. This dependent table carries the actual budget execution transaction records and joins back to the transaction code master through BE_TC_ID.

Because the ETRM excerpt lists only this one foreign key, FV_BE_TRX_CODES is the primary and only documented dependent object. In practice, other Federal Financials budget execution tables and the budget-to-GL posting concurrent programs may also consult this reference table, but those relationships are not captured in the supplied metadata.