Search Results planned_quantity




Overview
Explore in AI Chat

Overview

The PJM_PROJECT_PROJ_LS_ITEM_SUM_V view is a reporting and inquiry object within the Oracle E-Business Suite Project Manufacturing (PJM) module. It is owned by the APPS schema and holds a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. The view delivers a project-related line schedule summary aggregated by item, and its documented purpose is to serve the Web Inquiry interface. In practical terms, it functions as a summarized, query-friendly presentation layer that condenses the granular rows of the line schedule source into one row per item per project line, exposing planned and completed quantities along with the resulting variance. Because aggregation is performed inside the view, Oracle Forms-based inquiries and self-service web pages can retrieve item-level progress figures without repeatedly joining or grouping the underlying transactional data.

Underlying Base Objects

The view is defined over a single documented base object: PJM_LINE_SCHEDULES_V, which is itself a view. The dependency chain is therefore two layers deep, with PJM_PROJECT_PROJ_LS_ITEM_SUM_V summarizing the rows produced by PJM_LINE_SCHEDULES_V. The defining query selects LINE_CODE, LINE_ID, PROJECT_ID, ITEM_NUMBER, END_ITEM_UNIT_NUMBER, and PRIMARY_ITEM_ID, and applies SUM(NVL(...,0)) to the PLANNED_QUANTITY and QUANTITY_COMPLETED columns. Grouping is performed on the non-aggregated columns, and a derived arithmetic column, PLANNED_QUANTITY minus QUANTITY_COMPLETED, supplies the variance figure. The use of NVL guards against null quantities in the source, ensuring aggregation returns zero rather than null values.

Key Columns

  • LINE_CODE — Identification code for the project line schedule, used for display and filtering.
  • LINE_ID — Internal identifier of the line, forming part of the grouping key.
  • PROJECT_ID — The project to which the summarized line schedule belongs.
  • ITEM_NUMBER — The item identifier as presented to inquiry users.
  • END_ITEM_UNIT_NUMBER — The end item unit number associated with the project line, supporting unit-level tracking.
  • PRIMARY_ITEM_ID — Internal primary key of the item, useful for joins in custom reporting.
  • PLANNED_QUANTITY — Sum of planned quantities from the source schedules (nulls treated as zero).
  • QUANTITY_COMPLETED — Sum of completed quantities for the aggregated item line.
  • VARIANCE_QUANTITY — The difference between planned and completed quantities, revealing outstanding work.

Common Use Cases and Queries

The view is typically used to present project manufacturing progress in web inquiry screens and in ad hoc reporting. A representative query retrieves the summary for a given project:

  • SELECT line_code, item_number, planned_quantity, quantity_completed, variance_quantity FROM apps.pjm_project_proj_ls_item_sum_v WHERE project_id = :p_project_id;
  • Filtering on variance_quantity > 0 isolates items with outstanding completion work.
  • Joining on primary_item_id to MTL_SYSTEM_ITEMS_B enriches the summary with item descriptions.
  • Aggregating across line_code supports line-level rollups for dashboards.

Because it encapsulates its own aggregation and null handling, the view is well suited to direct consumption by inquiry pages and lightweight custom reports without additional transformation.