Search Results pjm_mass_transfer_tasks




Overview
Explore in AI Chat

Overview

The table PJM_MASS_TRANSFER_TASKS is a core data object within the Oracle E-Business Suite Project Manufacturing (PJM) module. It functions as a detailed transaction log for mass transfer operations related to project tasks. Specifically, it stores the individual task-level details that comprise a larger "Project Mass Transfer" request. This table is integral to the process of moving or transferring material, costs, or other project-related data en masse from one set of tasks to another, a common requirement for project restructuring, corrections, or consolidation. Its existence enables the system to track and manage the granular components of these bulk operations, ensuring data integrity and providing an audit trail.

Key Information Stored

While the provided ETRM metadata does not list specific columns, the table's description and foreign key relationship define its primary purpose. The key data stored includes a record for each project task involved in a mass transfer. Crucially, each record is linked to a parent request via the MASS_TRANSFER_ID column. Typical data points would include identifiers for the source and destination tasks, project numbers, and the specific transaction data being transferred (such as quantities, costs, or commitments). The table likely contains status flags to indicate the processing state of each individual task transfer within the overall mass request, along with timestamps and possibly error messages for failed lines.

Common Use Cases and Queries

This table is primarily accessed for auditing, troubleshooting, and reporting on mass transfer processes. Common scenarios include verifying the details of a completed transfer, identifying which specific task transfers failed within a larger request, or generating a report of all mass transfer activity for a given project or time period. A typical query would join this table to its parent, PJM_MASS_TRANSFERS, to get a complete picture.

Sample SQL Pattern:

  • SELECT pmt.request_number, pmtt.* FROM pjm_mass_transfer_tasks pmtt, pjm_mass_transfers pmt WHERE pmtt.mass_transfer_id = pmt.mass_transfer_id AND pmt.project_id = 1000;
  • SELECT mass_transfer_id, COUNT(*) task_count, status FROM pjm_mass_transfer_tasks GROUP BY mass_transfer_id, status;

Related Objects

The primary documented relationship for PJM_MASS_TRANSFER_TASKS is with its parent control table. As per the provided metadata, the table contains a foreign key constraint linking it to PJM_MASS_TRANSFERS.

  • PJM_MASS_TRANSFERS: This is the parent header table. The relationship is maintained through the column PJM_MASS_TRANSFER_TASKS.MASS_TRANSFER_ID, which references the primary key of PJM_MASS_TRANSFERS. This join is essential for retrieving header-level information (like request number, requester, date) for the detailed task records.