Search Results fv_transaction_headers_u1

Overview

FV.FV_TRANSACTION_HEADERS is a transactional header table within the Oracle E-Business Suite Federal Financials / FV (Advances and Miscellaneous Transactions) module. It stores the header-level information for financial transactions processed through the FV sub-ledger, capturing the activity context, transaction type classification, accounting context, and standard audit trail identifiers required by Oracle's multi-org and multi-ledger architecture. The table resides in the APPS_TS_TX_DATA tablespace with the standard 10 percent PCT FREE setting typical of EBS transactional data segments.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. This heuristic indicates that the table has no inbound foreign key dependencies from other tables within the documented ETRM metadata and functions as a self-contained record set rather than a central hub or an expressed link. In practice, TRANSACTION_HEADER_ID serves as the surrogate primary key (FV_TRANSACTION_HEADERS_PK) and appears as the sole business-key candidate through the unique index FV_TRANSACTION_HEADERS_U1.

Key Information Stored

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

• TRANSACTION_HEADER_ID — Surrogate primary key. Documented as NUMBER(15), enforced by both the primary key constraint and the unique index FV_TRANSACTION_HEADERS_U1 in the APPS_TS_TX_IDX tablespace.
• ACTIVITY_NAME — VARCHAR2(30) descriptor of the FV activity associated with the transaction, distinguishing transaction categories processed by the module.
• CUST_TRX_TYPE_ID — Foreign key to RA_CUST_TRX_TYPES_ALL, linking the header to the Receivables transaction type definition used to classify the financial event.
• APPLICATION_ID — Identifies the originating Oracle application within the shared Applications schema.
• SET_OF_BOOKS_ID — The accounting ledger context, essential for multi-ledger EBS deployments and subledger accounting derivation.
• USER_ID and RESPONSIBILITY_ID — Capture the creating application user and the EBS responsibility active at transaction entry, supporting audit and segregation-of-duties reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS "WHO" audit columns maintained by the framework for every transactional row.

Common Use Cases and Queries

Because this is a header table, typical use cases revolve around transaction lineage, audit reporting, and reconciliation of FV activity against downstream accounting entries. A common query joins the header to the transaction type to resolve descriptive meaning:

• Header-to-type lookup: SELECT h.transaction_header_id, h.activity_name, t.name FROM fv.fv_transaction_headers h, ra_cust_trx_types_all t WHERE h.cust_trx_type_id = t.cust_trx_type_id;
• Audit trail extraction by user: filtering on created_by or user_id to identify who entered specific FV transactions.
• Ledger-scoped reporting: filtering by set_of_books_id to isolate activity for a specific accounting ledger.
• Responsibility-based segregation analysis: aggregating counts by responsibility_id to detect unusual entry patterns.
• Unique key verification: querying via FV_TRANSACTION_HEADERS_U1 to confirm header uniqueness during data-migration or interface validation.

Related Objects

• RA_CUST_TRX_TYPES_ALL — Referenced via CUST_TRX_TYPE_ID; provides the transaction type classification.
• FV_TRANSACTION_HEADERS (APPS synonym/view) — The APPS-layer object exposing this table to EBS applications and concurrent programs.
• FV_TRANSACTION_HEADERS_PK — Primary key constraint on TRANSACTION_HEADER_ID.
• FV_TRANSACTION_HEADERS_U1 — Unique index on TRANSACTION_HEADER_ID; the business-key candidate and the object referenced in the user's search.
• FV subledger accounting and line-level objects in the FV schema, which typically key off TRANSACTION_HEADER_ID for detail retrieval.