Results for “transfer_date”

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

Overview

PJM_MASS_TRANSFERS is the header table for Project Mass Transfer requests within the Oracle E-Business Suite Project Manufacturing (PJM) module. It records each mass transfer transaction initiated in Oracle Projects Manufacturing, capturing the intent to move material, inventory items, or project costs from a source project to a destination project. The table functions as the parent entity in a master-detail relationship with PJM_MASS_TRANSFER_TASKS, which stores the individual task-level lines associated with each mass transfer request.

In an Oracle EBS 12.1.1 or 12.2.2 environment, this table participates directly in the Project Manufacturing transfer workflow, which supports inter-project and intra-project material movement. Each row represents a single mass transfer request, uniquely identified by MASS_TRANSFER_ID. The table includes standard Oracle EBS "WHO" audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) that capture row-level audit metadata.

Under a Data Vault modeling heuristic derived from its foreign key structure, PJM_MASS_TRANSFERS leans toward a hub classification, since it holds the durable business key MASS_TRANSFER_ID and is referenced by dependent child tables.

Key Information Stored

The most operationally significant columns documented in the ETRM 12.2.2 schema include:

• MASS_TRANSFER_ID — the surrogate primary key (PJM_MASS_TRANSFERS_PK) and also the sole unique index column (PJM_MASS_TRANSFERS_U1), making it both the surrogate and the business-key candidate for this entity.
• ORGANIZATION_ID — identifies the inventory organization in which the transfer is executed.
• ACCT_PERIOD_ID — associates the transfer with a specific accounting period.
• FROM_PROJECT_ID and TO_PROJECT_ID — define the source and destination projects for the mass transfer.
• TRANSFER_DATE — the effective date of the transfer transaction.
• TRANSFER_MODE and PROCESS_MODE — control how the transfer is executed and processed.
• INVENTORY_ITEM_ID — the inventory item being transferred.
• CATEGORY_SET_ID and CATEGORY_ID — capture item categorization for the transfer.
• TRANSFER_REASON_ID — the reason code associated with the transfer.
• TRANSFER_REFERENCE — a user-supplied reference identifier for traceability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns for extensible attributes.

Common Use Cases and Queries

Typical use cases include auditing project-to-project material movements, reconciling mass transfer activity by accounting period, and reporting on transfer volumes by organization or project.

A basic query to retrieve transfer headers for a given project:

• SELECT mass_transfer_id, from_project_id, to_project_id, transfer_date, organization_id FROM pjm_mass_transfers WHERE from_project_id = :project_id;

To count transfers per period:

• SELECT acct_period_id, COUNT(*) FROM pjm_mass_transfers GROUP BY acct_period_id;

To join headers with their task-level detail:

• SELECT h.mass_transfer_id, h.transfer_date, t.task_id FROM pjm_mass_transfers h, pjm_mass_transfer_tasks t WHERE h.mass_transfer_id = t.mass_transfer_id;

Reporting extracts commonly filter by TRANSFER_DATE ranges or TRANSFER_MODE to isolate specific transfer types.

Related Objects

The following objects are most significant in relation to PJM_MASS_TRANSFERS:

• PJM_MASS_TRANSFER_TASKS — the principal child table, joined via PJM_MASS_TRANSFER_TASKS.MASS_TRANSFER_ID = PJM_MASS_TRANSFERS.MASS_TRANSFER_ID, storing task-level transfer lines.
• PJM_MASS_TRANSFERS_PK — the primary key constraint on MASS_TRANSFER_ID.
• PJM_MASS_TRANSFERS_U1 — the unique index on MASS_TRANSFER_ID.

Additional dependent objects (project, organization, and item master tables referenced by the documented foreign-key-style columns such as FROM_PROJECT_ID, TO_PROJECT_ID, and INVENTORY_ITEM_ID) are implied through the module's standard integration points, though the ETRM excerpt explicitly documents only the PJM_MASS_TRANSFER_TASKS relationship.