Results for “fa_distribution_history_v”

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

Overview

FA_DISTRIBUTION_HISTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the Oracle Assets (OFA) product. Its status is VALID, and the ETRM documentation classifies it as "Retrofitted," indicating that the view was re-implemented during an upgrade cycle to preserve the original interface while adapting to a changed data model — in this case the migration of person data into the PER_PEOPLE_X view. The view presents asset distribution history records joined to employee identity information, exposing the person assigned to each distribution line alongside the distribution attributes themselves.

The object exists primarily to support inquiry and reporting against asset assignment history without forcing consumers to perform the join to Oracle HR tables manually. The most commonly searched column, ASSIGNED_TO_NAME, is not a native column of FA_DISTRIBUTION_HISTORY but is derived within the view from PER_PEOPLE_X.FULL_NAME, which explains why users searching for "assigned_to_name" land on this view rather than on the base table.

Underlying Base Objects

The documented base objects referenced by this view are:

• FA_DISTRIBUTION_HISTORY (SYNONYM) — the primary source of distribution rows.
• PER_PEOPLE_X (VIEW) — supplies the employee number and full name of the assignee.
• PER_PERIODS_OF_SERVICE (SYNONYM) — joined on PERSON_ID.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (PACKAGES) — invoked indirectly where name and security processing are required.

The view text joins these with outer joins on PERSON_ID (DH.ASSIGNED_TO = P.PERSON_ID (+) and P.PERSON_ID = S.PERSON_ID (+)), so distribution rows are retained even when no matching person or period-of-service record exists. The view projects DH.ROWID as ROW_ID, giving downstream tools a stable row identifier for the joined result set.

Key Columns

• DISTRIBUTION_ID — primary identifier of the distribution history record.
• BOOK_TYPE_CODE — the asset book in which the distribution applies.
• ASSET_ID — the asset being distributed or reassigned.
• UNITS_ASSIGNED — number of units assigned to the distribution line.
• DATE_EFFECTIVE / DATE_INEFFECTIVE — the active window of the assignment.
• CODE_COMBINATION_ID — accounting flexfield combination associated with the distribution.
• LOCATION_ID — location to which the asset or units are assigned.
• ASSIGNED_TO — the PERSON_ID of the employee holding the asset; this is the join key to PER_PEOPLE_X.
• ASSIGNED_TO_NUMBER — employee number, sourced from PER_PEOPLE_X.EMPLOYEE_NUMBER.
• ASSIGNED_TO_NAME — employee full name, sourced from PER_PEOPLE_X.FULL_NAME.
• TRANSACTION_HEADER_ID_IN / TRANSACTION_HEADER_ID_OUT — inbound and outbound transaction headers that generated the distribution movement.
• TRANSACTION_UNITS, RETIREMENT_ID — supporting transactional context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically consumed for asset custodian reporting, audit of assignment history, and reconciliation of distributions to transaction activity. Because ASSIGNED_TO_NAME and ASSIGNED_TO_NUMBER are already resolved, reports can avoid direct joins to HR tables. A representative query listing current assignments for a book follows:

SELECT distribution_id, asset_id, book_type_code, units_assigned, assigned_to_number, assigned_to_name, date_effective, date_ineffective FROM fa_distribution_history_v WHERE book_type_code = :book AND date_ineffective IS NULL ORDER BY assigned_to_name;

A second pattern traces the movement history of a single asset to identify the successive custodians:

SELECT asset_id, assigned_to_name, location_id, date_effective, date_ineffective FROM fa_distribution_history_v WHERE asset_id = :asset_id ORDER BY date_effective;

Analysts also group by assignee to measure the number of assets or units held per employee, and filter on TRANSACTION_HEADER_ID_IN or TRANSACTION_HEADER_ID_OUT when correlating distributions with specific asset transactions. Because the underlying HR joins use outer joins, rows with a null ASSIGNED_TO or an employee record missing from PER_PEOPLE_X will still appear, with ASSIGNED_TO_NAME returned as null.