Results for “fv_events_txn_code_v”

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

Overview

FV_EVENTS_TXN_CODE_V is a Federal Financials (FV) reporting view that associates USSGL transaction codes with Federal transaction events. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a denormalized read interface that joins the USSGL transaction code assignment table to the master transaction event and the GL USSGL transaction code definition. This allows federal accounting users and integrators to resolve, for any given transaction event, the USSGL transaction code, its chart of accounts, and its descriptive text in a single query rather than joining three tables manually.

The object is relevant when users search on "gl_ussgl_transaction_codes," since the view exposes GL_USSGL_TRANSACTION_CODES data in the context of Federal transaction events. It is principally used for federal reporting, USSGL validation, and downstream integration extracts. Per the ETRM documentation, the view is not implemented in the reference database, meaning it may not exist in all environments and its availability depends on whether Federal Financials is installed and configured.

Underlying Base Objects

The view is defined over three base tables through an inner join:

• FV_EVENTS_TRANSACTION_CODE (PSAT) — stores the assignment of a USSGL transaction code to a specific transaction event.
• FV_TRANSACTION_EVENTS (PSAE) — the transaction event header, supplying the chart of accounts context.
• GL_USSGL_TRANSACTION_CODES (T) — the General Ledger definition table holding the transaction code and its description.

The join conditions are strictly equated: PSAT.USSGL_TRANSACTION_CODE equals T.USSGL_TRANSACTION_CODE, PSAT.TRANSACTION_EVENT_ID equals PSAE.TRANSACTION_EVENT_ID, and T.CHART_OF_ACCOUNTS_ID equals PSAE.CHART_OF_ACCOUNTS_ID. Because all three predicates are equality joins, only transaction codes that resolve to a valid GL USSGL transaction code definition and a valid transaction event within the same chart of accounts are returned. The ETRM metadata documents no further referenced base objects.

Key Columns

The view projects the following columns:

• ROW_ID — the ROWID of the underlying FV_EVENTS_TRANSACTION_CODE row, available for row-level addressing.
• TRANSACTION_EVENT_ID — identifies the Federal transaction event to which the code is assigned.
• USSGL_TRANSACTION_CODE — the transaction code value used to drive USSGL postings and reporting.
• CHART_OF_ACCOUNTS_ID — the chart of accounts in which the code and event reside; inherited from the GL definition and matched to the event.
• DESCRIPTION — the descriptive text of the USSGL transaction code from GL_USSGL_TRANSACTION_CODES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle who-columns sourced from the FV_EVENTS_TRANSACTION_CODE assignment row, supporting audit and incremental extraction.

Common Use Cases and Queries

Typical scenarios include auditing which USSGL transaction codes are assigned to transaction events, producing federal USSGL reporting extracts, and building integration views that require code descriptions alongside event identifiers.

List all assignments for a chart of accounts:

• SELECT TRANSACTION_EVENT_ID, USSGL_TRANSACTION_CODE, DESCRIPTION FROM FV_EVENTS_TXN_CODE_V WHERE CHART_OF_ACCOUNTS_ID = :coa_id;

Retrieve codes changed after a given date for incremental feeds:

• SELECT TRANSACTION_EVENT_ID, USSGL_TRANSACTION_CODE, DESCRIPTION, LAST_UPDATE_DATE FROM FV_EVENTS_TXN_CODE_V WHERE LAST_UPDATE_DATE >= :last_run_date;

Validate that an event carries an expected transaction code:

• SELECT COUNT(*) FROM FV_EVENTS_TXN_CODE_V WHERE TRANSACTION_EVENT_ID = :event_id AND USSGL_TRANSACTION_CODE = :code;

Because the view relies on inner joins, rows with unassigned or orphaned transaction codes will not appear. Queries should therefore be validated against the base tables when completeness of the event population is required.