Results for “pjm_project_task_ls_item_sum_v”

16 results




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

Overview

PJM_PROJECT_TASK_LS_ITEM_SUM_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PJM - Project Manufacturing product. Its documented purpose is to provide a task-related line schedule summary by item for the Web Inquiry. In practice, the view aggregates line schedule data so that project and task level demand and completion information can be presented at the item level without exposing the full detail held in the underlying line schedule objects.

The view is defined as a single SELECT statement that reads from PJM_LINE_SCHEDULES_V and applies GROUP BY aggregation. This makes it a summarization layer rather than a transactional object: it does not store data, and it is regenerated at query time from its base object. Because the object is documented as VALID in ETRM 12.2.2 and is referenced by the Project Manufacturing Web Inquiry functionality, it is typically consumed by inquiry pages and by custom reports that need a compact, pre-aggregated picture of scheduled versus completed quantities per task and item.

Underlying Base Objects

The only documented referenced base object is PJM_LINE_SCHEDULES_V, itself a view. PJM_PROJECT_TASK_LS_ITEM_SUM_V therefore does not read directly from base tables; it inherits the join and filter logic embedded in PJM_LINE_SCHEDULES_V and then groups the result set. This dependency chain is important when troubleshooting: a change or invalidation in PJM_LINE_SCHEDULES_V propagates to this view, and column-level lineage must be traced through the intermediate view before reaching physical tables such as the PJM line schedule and project/task tables.

The aggregation groups on LINE_CODE, ITEM_NUMBER, LINE_ID, PROJECT_ID, TASK_ID, END_ITEM_UNIT_NUMBER, and PRIMARY_ITEM_ID. All remaining quantity columns are rolled up with SUM and NVL handling, which means null quantities are treated as zero and every task/item combination produces exactly one summary row.

Key Columns

  • LINE_CODE — Identifier code for the line schedule entry, used as a grouping key.
  • LINE_ID — Internal identifier of the line, also a grouping key.
  • PROJECT_ID — Project that owns the line schedule records.
  • TASK_ID — Task within the project, reflecting the task-related nature of the summary.
  • ITEM_NUMBER — Item on the line schedule; part of the grouping set.
  • END_ITEM_UNIT_NUMBER — End item unit number used to distinguish units of the same end item.
  • PRIMARY_ITEM_ID — Primary item identifier, grouped for consistency with item numbering.
  • PLANNED_QUANTITY — Sum of NVL(PLANNED_QUANTITY, 0) across the detail rows.
  • QUANTITY_COMPLETED — Sum of NVL(QUANTITY_COMPLETED, 0) across the detail rows.
  • VARIANCE_QUANTITY — Computed as SUM(NVL(PLANNED_QUANTITY,0)) minus SUM(NVL(QUANTITY_COMPLETED,0)), representing the open or uncompleted balance.

Common Use Cases and Queries

Typical usage includes the Project Manufacturing Web Inquiry screens, task-level progress reports, and custom extracts that compare planned against completed quantities. A representative query retrieving variance for a project and task is:

  • SELECT project_id, task_id, item_number, planned_quantity, quantity_completed, variance_quantity FROM apps.pjm_project_task_ls_item_sum_v WHERE project_id = :p_project_id AND task_id = :p_task_id ORDER BY item_number;
  • Filtering by variance_quantity > 0 isolates items with outstanding scheduled quantities.
  • Joining on primary_item_id to item master or on project_id/task_id to project and task tables enriches the summary with descriptive attributes.

Because the view is pre-aggregated, it is well suited to dashboards and inquiry pages where row-level detail is unnecessary and performance benefits from reduced row counts.