Search Results pjm_project_task_ls_line_sum_v

Overview

PJM_PROJECT_TASK_LS_LINE_SUM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as a VALID object within the PJM – Project Manufacturing product family. It exists to serve the Project Manufacturing Web Inquiry, the browser-based inquiry interface through which users review task-related line schedule information without navigating the full Oracle Forms-based application. The view delivers a summarized, aggregated perspective on line schedules, grouping records by line and task so that each combination of project, task, and line appears exactly once with consolidated quantity figures.

Because it aggregates rather than presenting raw transactional rows, the view is intended for reporting, inquiry, and lightweight integration scenarios where consumers need totals per manufacturing line per task. It does not expose scheduled dates, routing steps, or scheduling detail at the individual operation level; those remain in the underlying schedule view. The object is documented in ETRM for both EBS 12.1.1 and 12.2.2, and its definition is identical across those releases, as it depends only on another APPS view rather than on release-specific base tables.

Underlying Base Objects

The view is defined over a single documented base object: PJM_LINE_SCHEDULES_V, itself a view in the APPS schema. PJM_PROJECT_TASK_LS_LINE_SUM_V therefore forms a second-tier view, inheriting the join logic, security predicates, and column derivations already present in PJM_LINE_SCHEDULES_V. The internal definition of PJM_LINE_SCHEDULES_V is not reproduced in the supplied metadata; it resolves line schedule records against Project Manufacturing and project/task entities.

The aggregation performed in the outer view is a straightforward GROUP BY over LINE_CODE, LINE_ID, PROJECT_ID, and TASK_ID, with SUM aggregates applied to PLANNED_QUANTITY and QUANTITY_COMPLETED, each wrapped in NVL to treat nulls as zero. This construction means any row-level filtering, organization security, or project access restrictions enforced inside PJM_LINE_SCHEDULES_V flow through to consumers of the summary view. No base tables are referenced directly, and the view is not updatable.

Key Columns

• LINE_CODE – The user-facing identifier of the manufacturing line; part of the grouping key.
• LINE_ID – The internal surrogate key for the line; also part of the grouping key and the reliable join column to other line-related objects.
• PROJECT_ID – The project to which the task and line schedule belong; part of the grouping key.
• TASK_ID – The project task associated with the schedule; part of the grouping key. Together with PROJECT_ID it identifies the task context of the summarized quantities.
• PLANNED_QUANTITY – The sum of planned quantities across the grouped line schedule records, with nulls coalesced to zero.
• QUANTITY_COMPLETED – The sum of completed quantities, also NVL-protected. This is the column most directly associated with the search term "quantity_completed," and it represents the cumulative completed output for the project/task/line combination.
• VARIANCE_QUANTITY – Computed as SUM(NVL(PLANNED_QUANTITY,0)) minus SUM(NVL(QUANTITY_COMPLETED,0)); the outstanding balance between planned and completed work, which may be positive (work remaining) or negative (over-completion).

Common Use Cases and Queries

The primary use case is the Project Manufacturing Web Inquiry, which lists line schedules by task and shows planned versus completed quantities with the derived variance. Beyond that, the view is convenient for ad hoc reporting on task progress and for feeding dashboards or extracts that need pre-aggregated quantities.

A typical query retrieving completion status for a given project and task:

• SELECT line_code, line_id, planned_quantity, quantity_completed, variance_quantity FROM apps.pjm_project_task_ls_line_sum_v WHERE project_id = :project_id AND task_id = :task_id ORDER BY line_code;

To identify lines with remaining work across a project:

• SELECT project_id, task_id, line_code, variance_quantity FROM apps.pjm_project_task_ls_line_sum_v WHERE project_id = :project_id AND variance_quantity > 0 ORDER BY variance_quantity DESC;

To total completion at project level, aggregating once more over the summarized rows:

• SELECT project_id, SUM(planned_quantity), SUM(quantity_completed), SUM(variance_quantity) FROM apps.pjm_project_task_ls_line_sum_v GROUP BY project_id;

Because the view performs its own aggregation, queries should filter on the grouping columns (PROJECT_ID, TASK_ID, LINE_ID, LINE_CODE) for efficiency and should avoid joining back to PJM_LINE_SCHEDULES_V at row level unless schedule detail is genuinely required, since that would reintroduce the granularity the summary view is designed to eliminate.