Results for “pjm_project_task_ls_daily_v”

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

Overview

The PJM_PROJECT_TASK_LS_DAILY_V view is a predefined Oracle EBS database object owned by the APPS schema within the PJM (Project Manufacturing) product family. Its documented status is VALID, and it is shipped as a standard, read-only reporting view rather than a table. The view supplies task-related line schedule daily summary information to the Project Manufacturing Web Inquiry, and its primary design objective is to aggregate scheduled quantities at a daily granularity keyed by line, project, and task.

Because it collapses detail rows into one row per line, item, and scheduled day, the view is intended for summarization and inquiry rather than transactional maintenance. It is well suited to reporting and lightweight integration scenarios where consumers require planned versus completed quantities without traversing the full underlying line schedule detail. This makes it useful for dashboards, exception reporting, and interfaces that track work in progress against a project task's daily schedule.

Underlying Base Objects

The view is defined over exactly one documented base object: PJM_LINE_SCHEDULES_V, itself a view in the APPS schema. PJM_PROJECT_TASK_LS_DAILY_V therefore inherits the joins and security filtering already applied within PJM_LINE_SCHEDULES_V and applies a further aggregation and filter layer on top.

The view text filters records with WHERE PROJECT_ID IS NOT NULL, excluding any line schedule rows that are not associated with a project. Rows are then grouped by LINE_CODE, LINE_ID, PROJECT_ID, TASK_ID, ITEM_NUMBER, END_ITEM_UNIT_NUMBER, PRIMARY_ITEM_ID, and TRUNC(SCHEDULED_START_DATE). Finally, the result set is ordered by LINE_CODE, ITEM_NUMBER, and the truncated scheduled start date. The use of TRUNC normalizes the schedule timestamp to a calendar day, which is the basis of the view's "daily" semantics.

Key Columns

• LINE_CODE and LINE_ID — the identifying code and surrogate identifier of the project manufacturing line.
• PROJECT_ID and TASK_ID — the project and task to which the summarized schedule rows belong; both participate in grouping.
• ITEM_NUMBER and PRIMARY_ITEM_ID — the inventory item number and its internal primary key.
• END_ITEM_UNIT_NUMBER — the unit number of the end assembly associated with the schedule row.
• SCHEDULED_DATE — the day-level schedule date derived from TRUNC(SCHEDULED_START_DATE). This is the column returned when a user searches for "scheduled_start_date"; the original timestamp column is truncated and aliased here.
• PLANNED_QUANTITY — the summed planned quantity, computed as SUM(NVL(PLANNED_QUANTITY,0)).
• QUANTITY_COMPLETED — the summed completed quantity, computed as SUM(NVL(QUANTITY_COMPLETED,0)).
• VARIANCE_QUANTITY — the open or remaining quantity, computed as the difference between summed planned and summed completed quantities.

Common Use Cases and Queries

Typical uses include daily load reporting, planned-versus-completed analysis by project task, and variance identification for lines behind schedule. The following sample queries illustrate common access patterns.

Listing daily summaries for a project task:

SELECT line_code, item_number, scheduled_date,
       planned_quantity, quantity_completed, variance_quantity
FROM   apps.pjm_project_task_ls_daily_v
WHERE  project_id = :p_project_id
AND    task_id    = :p_task_id
ORDER BY item_number, scheduled_date;

Identifying items with outstanding variance on a given day:

SELECT project_id, task_id, item_number, scheduled_date,
       variance_quantity
FROM   apps.pjm_project_task_ls_daily_v
WHERE  scheduled_date = TRUNC(SYSDATE)
AND    variance_quantity > 0
ORDER BY variance_quantity DESC;

Aggregating planned quantities across tasks for a line:

SELECT line_code, SUM(planned_quantity) planned,
       SUM(quantity_completed) completed
FROM   apps.pjm_project_task_ls_daily_v
GROUP BY line_code;