Results for “fa_mass_transfers_pk”

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

Overview

FA_MASS_TRANSFERS is the Oracle Assets (OFA) transaction table that stores mass transfer request information. It records the header-level definition of a mass transfer — a batch operation in which the location, general ledger account, employee assignment, or expense account distribution of many assets is changed at once — and serves as the anchor record that the Mass Transfers concurrent program uses to drive the underlying asset-level transfers. Each row represents a single mass transfer request entered against a specific asset book, identified by its book type code, and is linked to the concurrent request that executed (or will execute) it.

From a Data Vault modeling perspective, the mined FK structure suggests this table is best treated as a link entity: it captures a relationship among parties and reference entities (a from/to location pair, a from/to GL account pair, a category, and a book) rather than representing an independent business concept or a pure descriptive satellite. In practice, it functions as a transactional header with a small number of stable descriptive attributes.

Key Information Stored

The table contains 119 documented columns. The most significant are:

• MASS_TRANSFER_ID — the surrogate primary key (FA_MASS_TRANSFERS_PK, with unique index FA_MASS_TRANSFERS_U1), generated by the FA sequence and used to join to the asset-level mass transfer lines.
• BOOK_TYPE_CODE — the asset book against which the transfer is executed; foreign key to FA_BOOK_CONTROLS and the primary partitioning driver of any query.
• CONCURRENT_REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, linking the request to the batch that processed it; essential for debugging incomplete or errored runs.
• FROM_LOCATION_ID and TO_LOCATION_ID — foreign keys to FA_LOCATIONS defining the source and target locations of the transfer.
• FROM_GL_CCID and TO_GL_CCID — foreign keys to GL_CODE_COMBINATIONS defining the source and destination asset clearing/distribution accounts.
• CATEGORY_ID — foreign key to FA_CATEGORIES_B, used to restrict the population of assets affected by category.
• TRANSACTION_DATE_ENTERED and DATE_EFFECTIVE — the entry timestamp and the accounting-effective date that determines the period in which the transfer posts.
• FROM_EMPLOYEE_ID and TO_EMPLOYEE_ID — the assignee reassignment pair for employee-assigned assets.
• DESCRIPTION — free-text narrative describing the request.
• SEGMENT1 … SEGMENT30 (LOW/HIGH ranges) — the concatenated key flexfield segment ranges that constrain which assets are selected; these act as the selection criteria for the mass transfer.
• ATTRIBUTE1 … ATTRIBUTE15, ATTRIBUTE_CATEGORY_CODE — the standard Oracle descriptive flexfield columns for capturing client-specific information.

Common Use Cases and Queries

Typical reporting scenarios include auditing mass transfer activity by book and period, resolving a request back to its concurrent program output, and reconciling asset location/account changes against the general ledger.

• Recent transfers by book: SELECT mass_transfer_id, book_type_code, transaction_date_entered FROM fa_mass_transfers WHERE book_type_code = :book ORDER BY transaction_date_entered DESC;
• Resolve request status: join to FND_CONCURRENT_REQUESTS on CONCURRENT_REQUEST_ID to obtain phase_code and status_code.
• Location master data: join FA_LOCATIONS on FROM_LOCATION_ID and TO_LOCATION_ID to display location codes.
• Account validation: join GL_CODE_COMBINATIONS on FROM_GL_CCID and TO_GL_CCID to reconstruct the full account string.
• Category-scoped extract: join FA_CATEGORIES_B on CATEGORY_ID where a mass transfer was restricted to a single asset category.

Note that FA_MASS_TRANSFERS holds only request-level attributes; the per-asset detail is held in the FA_MASS_TRANSFERS_... distribution/line tables, so most operational reports join both levels.

Related Objects

• FND_CONCURRENT_REQUESTS — joined on FA_MASS_TRANSFERS.CONCURRENT_REQUEST_ID; supplies execution status and log/out file references.
• FA_LOCATIONS — joined twice, on FROM_LOCATION_ID and TO_LOCATION_ID.
• GL_CODE_COMBINATIONS — joined twice, on FROM_GL_CCID and TO_GL_CCID.
• FA_CATEGORIES_B — joined on CATEGORY_ID to resolve the asset category.
• FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE to validate the asset book and its period status.

These relationships define the referential integrity of the mass transfer request and form the standard join set for both transactional and reporting queries against FA_MASS_TRANSFERS.