Search Results fv_be_trx_codes_u1

Overview

FV_BE_TRX_CODES is a table in the FV schema, the database schema that supports Oracle E-Business Suite's Federal Financials and Budget Execution (BE) functionality. The table stores the valid transaction codes associated with budget execution transaction types, providing the code-level detail that distinguishes individual transaction types beyond the type identifier itself. In Oracle EBS 12.1.1 and 12.2.2, the object resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and its unique index, FV_BE_TRX_CODES_U1, is stored in APPS_TS_TX_IDX.

The ETRM metadata designates this table as "No longer used." This status indicates that the table is a legacy object retained in the schema for historical data and backward compatibility, but it is no longer actively populated or referenced by current application logic. Consultants should treat it as a read-only historical artifact. From a Data Vault modeling perspective, the mined FK structure classifies FV_BE_TRX_CODES as a standalone table; it can be viewed as a hub-like structure keyed by the combination of transaction type and transaction code, with standard WHO columns functioning as satellite attributes.

Key Information Stored

The table contains nine columns. The most significant are:

• BE_TC_ID (NUMBER(15)) — the unique system-generated surrogate primary key for each row. It is documented as a foreign key to FV_BE_TRANSACTION_CODES.
• BE_TT_ID (NUMBER(15)) — the transaction type identifier, documented as a foreign key to FV_BE_TRANSACTION_TYPES. This column anchors the table to the budget execution transaction type hierarchy.
• TRANSACTION_CODE (VARCHAR2(30)) — the transaction code value being defined for the given transaction type.
• SET_OF_BOOKS_ID (NUMBER(15)) — the set of books identifier, indicating the ledger context under which the transaction code applies. In 12.2.2 this concept maps to the ledger/legal entity configuration, though the column name reflects the pre-12.2 accounting model.

The documented business-key candidate is the unique index FV_BE_TRX_CODES_U1, defined on the column pair (BE_TT_ID, TRANSACTION_CODE). This establishes that a given transaction code is unique within a transaction type. The remaining columns are standard WHO audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. CREATED_BY and LAST_UPDATED_BY carry foreign key semantics to FND_USER.USER_ID, and LAST_UPDATE_LOGIN references FND_LOGINS.LOGIN_ID.

Common Use Cases and Queries

Because the table is flagged as no longer used, the primary use cases are historical reporting, data migration reconciliation, and audit investigations. A typical query joins the table to its parent transaction type table to present the code alongside the type description:

• Validation of historical transaction codes: SELECT BE_TT_ID, TRANSACTION_CODE, SET_OF_BOOKS_ID FROM FV.FV_BE_TRX_CODES WHERE BE_TT_ID = :type_id;
• Audit queries relying on the WHO columns: filter on LAST_UPDATE_DATE ranges, then resolve LAST_UPDATED_BY against FND_USER to identify the responsible user.
• Reference-data comparisons between environments (for example, comparing setups across two instances) using the unique key (BE_TT_ID, TRANSACTION_CODE) as the match point.
• Data lineage checks when migrating budget execution configurations into a current release, verifying that legacy codes map cleanly to their modern equivalents.

The full column projection is available through the standard SELECT on FV.FV_BE_TRX_CODES, and the unique index on (BE_TT_ID, TRANSACTION_CODE) supports efficient single-row lookups by transaction type and code.

Related Objects

The following objects are most directly associated with FV_BE_TRX_CODES:

• FV_BE_TRANSACTION_TYPES — the parent table of the transaction type referenced by BE_TT_ID. This is the most important join target for describing the type behind each code.
• FV_BE_TRANSACTION_CODES — documented as the referenced table for BE_TC_ID, representing the broader transaction code definition.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY for audit queries.
• FND_LOGINS — resolves LAST_UPDATE_LOGIN for login-level auditing.
• FV_BE_TRX_CODES (APPS synonym/view) — the APPS-level synonym or view through which the application layer accesses the table, permitting queries without the FV schema prefix.

No dependencies are documented in which FV_BE_TRX_CODES references other objects beyond the two foreign keys noted above, and its primary consumers are the budget execution configuration and reporting components that resolve transaction codes. Given the "No longer used" status, new development should avoid this table; existing integrations should be reviewed and redirected to the currently supported equivalents within the FV schema.