Search Results pjm_project_proj_ls_line_sum_v




Overview
Explore in AI Chat

Overview

PJM_PROJECT_PROJ_LS_LINE_SUM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Project Manufacturing (PJM) product family. The view is documented as VALID in ETRM for both release 12.1.1 and 12.2.2. Its stated purpose is to provide a project-related line schedule summary, aggregated by line, for consumption by the Project Manufacturing Web Inquiry pages. Rather than exposing the granular rows maintained by the underlying line schedule view, PJM_PROJECT_PROJ_LS_LINE_SUM_V collapses planning data to one row per line and project combination, which makes it suitable for summary display, at-a-glance status review, and lightweight integration queries that do not require transaction-level detail. Because it is a view and not a table, it stores no data of its own and always reflects the current state of its base object at query time.

Underlying Base Objects

The view is defined over a single documented base object: PJM_LINE_SCHEDULES_V, itself a view within the Project Manufacturing schema. The dependency is a straightforward aggregation. PJM_PROJECT_PROJ_LS_LINE_SUM_V selects from PJM_LINE_SCHEDULES_V, applies NVL to substitute zero for null quantities, applies SUM to the planned and completed quantity measures, and groups the result by LINE_CODE, LINE_ID, and PROJECT_ID. Two derived measures are computed during the aggregation: total planned quantity, total completed quantity, and the variance between them. No joins to independent base tables are performed at this level, so all dimensional and transactional context is inherited from PJM_LINE_SCHEDULES_V. Administrators troubleshooting the view should therefore validate the underlying line schedule view and its own dependencies before investigating the summary layer.

Key Columns

  • LINE_CODE — The user-facing identifier of the manufacturing line; participates in the GROUP BY and is the primary descriptive key for reporting.
  • LINE_ID — The internal unique identifier for the line, carried through the aggregation to support joins to other Project Manufacturing entities.
  • PROJECT_ID — The project against which the line schedule quantities are accumulated; the third grouping attribute, allowing the same line to appear once per project.
  • PLANNED_QUANTITY — The sum of NVL(PLANNED_QUANTITY, 0) across the constituent schedule rows, representing total planned output for the line and project.
  • QUANTITY_COMPLETED — The sum of NVL(QUANTITY_COMPLETED, 0), representing total quantity reported complete.
  • VARIANCE_QUANTITY — The arithmetic difference between total planned and total completed quantity, i.e. SUM(NVL(PLANNED_QUANTITY,0)) minus SUM(NVL(QUANTITY_COMPLETED,0)). This is the principal progress indicator exposed by the view.

Common Use Cases and Queries

Typical consumers include the Project Manufacturing Web Inquiry, which requires a compact line-level schedule summary, and custom reports or interfaces that need planned-versus-completed position by project without the volume of the detail view. A representative query filters by project and orders by line code:

  • SELECT line_code, line_id, project_id, planned_quantity, quantity_completed, variance_quantity FROM apps.pjm_project_proj_ls_line_sum_v WHERE project_id = :project_id ORDER BY line_code;
  • Identifying lines behind plan: SELECT line_code, project_id, variance_quantity FROM apps.pjm_project_proj_ls_line_sum_v WHERE project_id = :project_id AND variance_quantity > 0 ORDER BY variance_quantity DESC;
  • Totalling across all lines for a project: SELECT project_id, SUM(planned_quantity), SUM(quantity_completed), SUM(variance_quantity) FROM apps.pjm_project_proj_ls_line_sum_v GROUP BY project_id;

Because the view performs aggregation internally, additional grouping at the caller level should be applied only where a coarser grain is required. Queries should always constrain by PROJECT_ID or LINE_ID where possible, since unfiltered access scans the full line schedule view.