Results for “transaction_header_id_out”

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

Overview

FA_ASSET_HISTORY_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, belonging to the Oracle Assets (OFA) product family. It presents the transactional movement history of fixed assets by combining the raw history rows held in FA_ASSET_HISTORY with descriptive data drawn from FA_ADDITIONS, FA_LOOKUPS, and FA_TRANSACTION_HEADERS. In ETRM metadata the object is marked VALID and carries the description "Retrofitted," indicating that its definition was reconciled to the current Applications release, notably 12.1.1 and 12.2.2. The view is not a base table; it is a reporting and integration convenience layer that exposes de-normalized asset history, thereby sparing developers the effort of repeatedly joining history to asset descriptions and transaction lookup values. The presence of a documented column named TRANSACTION_HEADER_ID_IN reflects the search term that led to this object: the column records the transaction header through which an asset entered a given history event, making the view particularly useful when tracing how a specific transaction affected one or more assets. Because the view is defined over APPS-owned synonyms to the underlying OFA tables, it is directly queryable by custom reports, interfaces, and extracts, subject to the standard EBS read consistency and privileges surrounding the APPS schema.

Underlying Base Objects

The ETRM metadata documents four referenced base objects, all presented as synonyms in the APPS schema: FA_ADDITIONS, FA_ASSET_HISTORY, FA_LOOKUPS, and FA_TRANSACTION_HEADERS. The core driving table is FA_ASSET_HISTORY (aliased AH), which supplies the transaction identifiers, asset identifier, units, asset type, and category identifier. FA_ADDITIONS (aliased AD) is joined on ASSET_ID and provides the asset number and description, which the view concatenates as ASSET_NUMBER. FA_TRANSACTION_HEADERS (aliased TH) is joined on TRANSACTION_HEADER_ID and supplies TRANSACTION_NAME, surfaced in the view as COMMENTS. FA_LOOKUPS (aliased LO) is constrained to LOOKUP_TYPE = 'FAXOLTRX' and matches LOOKUP_CODE to the header's TRANSACTION_TYPE_CODE to yield the TRANSACTION_TYPE meaning. The view is a UNION of two branches: the first selects each history row once using TRANSACTION_HEADER_ID_IN as the key, and the second additionally re-selects rows where TRANSACTION_HEADER_ID_OUT is not null, using TRANSACTION_HEADER_ID_OUT as the key. This union structure ensures that an asset appears under both the incoming and outgoing sides of a transfer or reclassification transaction.

Key Columns

• TRANSACTION_HEADER_ID_IN — Identifier of the transaction header through which the asset entered the history event; used as the join key in the first UNION branch.
• TRANSACTION_HEADER_ID_OUT — Identifier of the outgoing transaction header; populated when a transfer or reclassification removed the asset from its prior assignment.
• KEY — A synthetic key that resolves to TRANSACTION_HEADER_ID_IN in the first branch and TRANSACTION_HEADER_ID_OUT in the second, providing a single consistent identifier for row-level linking. Note that this is not unique in the strict sense and should be combined with ASSET_ID in joins.
• ASSET_ID — Foreign key to the asset in FA_ADDITIONS.
• ASSET_NUMBER — Concatenation of the asset number and description, formatted as "number - description," suitable for display in reports.
• TRANSACTION_TYPE — The meaning derived from FA_LOOKUPS for the transaction type code, describing the nature of the movement.
• UNITS — Number of units affected by the transaction.
• ASSET_TYPE — Classification of the asset row within the history record.
• CATEGORY_ID — Asset category identifier associated with the history row.
• COMMENTS — The transaction name from FA_TRANSACTION_HEADERS, providing a human-readable label for the transaction.

Common Use Cases and Queries

Typical uses include asset movement reporting, audit trails of transfers between employees, locations, or cost centers, reconciliation of transaction headers to affected assets, and extracting history for data warehousing. A common query retrieves all history for a specific asset:

SELECT asset_number, transaction_type, units, comments FROM fa_asset_history_v WHERE asset_id = :p_asset_id ORDER BY key;

Because the search term was TRANSACTION_HEADER_ID_IN, a frequent pattern selects all assets touched by a given transaction header:

SELECT asset_id, asset_number, transaction_type, comments FROM fa_asset_history_v WHERE transaction_header_id_in = :p_header_id;

To obtain both the incoming and outgoing sides of a transfer, query with an IN condition across both keys:

SELECT asset_id, asset_number, key, transaction_type FROM fa_asset_history_v WHERE transaction_header_id_in = :p_header_id OR transaction_header_id_out = :p_header_id;

Joins back to FA_TRANSACTION_HEADERS on KEY or to FA_ADDITIONS on ASSET_ID are common when additional header attributes, such as transaction date or posting status, are required, since the view itself exposes only transaction name and descriptive asset text.