Results for “distribution_id”

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

Overview

FA_TRANSFER_DETAILS is an Oracle Assets (OFA) table residing in the FA schema. Its documented purpose is to define the historic relationship between active FA_BOOKS rows and FA_DISTRIBUTION_HISTORY rows. In practical terms, the table records which asset distribution history records correspond to which asset book records following a transfer transaction. It therefore acts as a persistent cross-reference that survives the movement of assets between locations, employees, or other distribution dimensions.

The table contains only three documented columns: TRANSFER_HEADER_ID, DISTRIBUTION_ID, and BOOK_HEADER_ID. This narrow structure is characteristic of an associative or junction object rather than a transaction header or a descriptive entity. In a heuristic Data Vault classification, FA_TRANSFER_DETAILS is best modeled as a link table. It captures the association between a transfer transaction header (FA_TRANSACTION_HEADERS), an asset distribution history record (FA_DISTRIBUTION_HISTORY), and an asset book (FA_BOOKS) without holding descriptive attributes of its own.

Key Information Stored

The documented schema exposes three columns, all of which function as relationship keys:

• TRANSFER_HEADER_ID — A foreign key to FA_TRANSACTION_HEADERS. It identifies the transfer transaction under which the relationship was created. It is also the first component of the composite primary key.
• DISTRIBUTION_ID — A foreign key to FA_DISTRIBUTION_HISTORY. It identifies the specific distribution history row, capturing the assignment of the asset to a distribution set (such as employee, location, or expense account). It is the second component of the composite primary key.
• BOOK_HEADER_ID — A foreign key to FA_BOOKS. It identifies the asset book in which the affected asset is held. This column completes the link between the book and the distribution history.

The surrogate primary key is defined by the constraint FA_TRANSFER_DETAILS_PK, comprising (TRANSFER_HEADER_ID, DISTRIBUTION_ID). A unique index, FA_TRANSFER_DETAILS_U1, covers the same two columns and serves as the documented business-key candidate, enforcing that a given distribution history row can be tied to a transfer header only once. No other uniqueness constraint is documented. Because the table is a pure link, the only meaningful business keys are the foreign keys themselves; there is no independent surrogate or sequence-derived identifier beyond the composite primary key.

Common Use Cases and Queries

The primary use case for FA_TRANSFER_DETAILS is reconstructing transfer history: given an asset book row, determine which distribution history records were created or affected by a transfer, and through which transaction. This supports fixed asset audit reporting, reconciliation of transfer transactions, and analysis of asset reassignment over time.

A typical join pattern resolves the full transfer context across the related tables:

• Join FA_TRANSFER_DETAILS to FA_TRANSACTION_HEADERS on TRANSFER_HEADER_ID to obtain transaction-level information such as transaction type and date.
• Join FA_TRANSFER_DETAILS to FA_DISTRIBUTION_HISTORY on DISTRIBUTION_ID to retrieve distribution details, including assignment and location data.
• Join FA_TRANSFER_DETAILS to FA_BOOKS on BOOK_HEADER_ID to reach the asset book and its underlying asset number, book type, and cost information.

Reporting queries frequently aggregate transfer counts per book or per period by grouping on BOOK_HEADER_ID and the transaction date obtained from FA_TRANSACTION_HEADERS. Reconciliation queries compare FA_DISTRIBUTION_HISTORY rows that appear in FA_TRANSFER_DETAILS against the expected set of assignments for a given book to detect missing or orphaned transfer links. Because the table is narrow and confined to key relationships, it is usually filtered first and then expanded through its foreign keys rather than scanned independently.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships:

• FA_TRANSACTION_HEADERS — referenced by TRANSFER_HEADER_ID; supplies transaction type, date, and header-level context for each transfer.
• FA_DISTRIBUTION_HISTORY — referenced by DISTRIBUTION_ID; holds distribution assignments and their history.
• FA_BOOKS — referenced by BOOK_HEADER_ID; holds the active asset book rows whose historic relationship this table records.
• FA_TRANSFER_DETAILS_PK / FA_TRANSFER_DETAILS_U1 — the primary key constraint and unique index that enforce the composite uniqueness of (TRANSFER_HEADER_ID, DISTRIBUTION_ID).

Together these objects form the transfer lineage chain: transaction header to transfer detail to distribution history, anchored by the asset book. Any inquiry into the provenance of a distribution history row, or into the distributions tied to a specific transfer, must traverse FA_TRANSFER_DETAILS.