Search Results fv_transaction_headers_pk

Overview

FV_TRANSACTION_HEADERS is a table in the FV (Federal Financials) product family of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores header-level information describing a transaction event activity, including the application, user, responsibility, or transaction type associated with that activity. In practice, it functions as the controlling parent record for transaction event activities processed through the Federal Financials transaction subsystem, providing the attribution and context that downstream detail lines and processing routines rely upon.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling scheme, meaning it does not participate in the mined foreign-key structure as a hub, link, or satellite in the conventional sense. Where it is referenced, it behaves most like a hub: its primary key, TRANSACTION_HEADER_ID, is a stable surrogate identifier assigned to each transaction header, while descriptive attributes such as ACTIVITY_NAME and the various ID columns act as satellite-style context. Modeling this table as a hub keyed on TRANSACTION_HEADER_ID, with a satellite carrying the descriptive columns, reflects the documented structure.

Key Information Stored

The table is documented with twelve columns, of which the following are the most significant:

• TRANSACTION_HEADER_ID — the surrogate primary key, defined by constraint FV_TRANSACTION_HEADERS_PK. It also appears in the unique index FV_TRANSACTION_HEADERS_U1, making it the documented business-key candidate and the join anchor for related objects.
• CUST_TRX_TYPE_ID — identifies the transaction type, drawn from the receivable transaction type definitions. This is the only documented foreign key, referencing RA_CUST_TRX_TYPES_ALL.
• APPLICATION_ID — identifies the Oracle application that owns or generated the transaction event activity.
• ACTIVITY_NAME — the descriptive name of the transaction event activity represented by the header.
• USER_ID — the application user associated with the header.
• RESPONSIBILITY_ID — the responsibility under which the activity was executed, supporting security and audit tracing.
• SET_OF_BOOKS_ID — the ledger context for the transaction, enabling multi-organization and multi-ledger reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit trail columns recording who created and last modified the record and when.

Because the table is standalone in the mined relationship data, the descriptive columns above should be treated as denormalized context rather than as references to separate hub tables.

Common Use Cases and Queries

Typical reporting scenarios include auditing which user or responsibility initiated a transaction event activity, reconciling transaction headers to receivable transaction types, and filtering activity by ledger. A representative query joining the documented foreign key is:

• SELECT h.transaction_header_id, h.activity_name, h.user_id, h.responsibility_id, h.set_of_books_id, t.name FROM fv.fv_transaction_headers h, ra.ra_cust_trx_types_all t WHERE h.cust_trx_type_id = t.cust_trx_type_id AND h.set_of_books_id = :ledger_id;
• SELECT transaction_header_id, activity_name, application_id, last_update_date, last_updated_by FROM fv.fv_transaction_headers WHERE creation_date >= :from_date AND creation_date < :to_date ORDER BY creation_date DESC;
• SELECT responsibility_id, COUNT(*) FROM fv.fv_transaction_headers GROUP BY responsibility_id ORDER BY 2 DESC;

These patterns support audit review, activity tracing, and volume analysis by ledger or responsibility. All queries should be schema-qualified with FV, since the object resides in the FV schema.

Related Objects

The documented relationship data identifies a single foreign-key dependency, but practical integration extends to surrounding Federal Financials and Receivables objects:

• RA_CUST_TRX_TYPES_ALL — referenced through CUST_TRX_TYPE_ID; the only foreign key documented in the ETRM metadata.
• FND_APPLICATION — resolves APPLICATION_ID to an application name.
• FND_USER — resolves USER_ID to a user name.
• FND_RESPONSIBILITY — resolves RESPONSIBILITY_ID to a responsibility name.
• GL_SETS_OF_BOOKS / GL_LEDGERS — resolves SET_OF_BOOKS_ID to ledger context.
• FV_TRANSACTION_HEADERS_PK / FV_TRANSACTION_HEADERS_U1 — the primary key constraint and unique index enforcing TRANSACTION_HEADER_ID uniqueness.

Consult the FV schema object list and the Federal Financials technical reference for any detail tables that may reference TRANSACTION_HEADER_ID, as those are not captured in the mined relationship data provided here.