Search Results scheduled_completion_date

Overview

The PJM_PROJECT_PROJ_LS_DETAIL_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the Project Manufacturing (PJM) product family. Its documented status is VALID, and it is described in the ETRM metadata as presenting "project-related line schedule detail information for the Web Inquiry." In practice, this view serves as a reporting and inquiry layer that flattens and enriches the underlying line schedule data with project and task context so that self-service web pages, concurrent reports, and integration extracts can retrieve manufacturing line schedule detail without directly joining the base manufacturing tables.

The view is particularly relevant to users searching on terms such as schedule_number, since the schedule number is one of its exposed columns and one of its primary descriptive attributes. It is defined with an ORDER BY clause on LINE_CODE, ITEM_NUMBER, and SCHEDULED_START_DATE, which produces a stable, report-friendly ordering out of the box.

Underlying Base Objects

The documented referenced base objects for this view are PJM_LINE_SCHEDULES_V (a view) and PJM_PROJECT (a package). The view is defined as a SELECT over PJM_LINE_SCHEDULES_V, with transformation functions supplied by the PJM_PROJECT package applied inline to the PROJECT_ID and TASK_ID columns.

Specifically, PJM_PROJECT.ALL_PROJ_IDTONUM and PJM_PROJECT.ALL_PROJ_IDTONAME convert the numeric project identifier into the user-facing project number and project name, while PJM_PROJECT.ALL_TASK_IDTONUM and PJM_PROJECT.ALL_TASK_IDTONAME perform the equivalent resolution for task identifiers. This design allows the view to present both surrogate keys and descriptive values without requiring the consuming report or interface to call the PJM_PROJECT conversion APIs itself.

Because the view selects from another view (PJM_LINE_SCHEDULES_V), it inherits that view's own compilation and security behavior, including any organization or operating unit filtering defined within it. This layered approach is typical in EBS, where detail views frequently build on top of other public views rather than directly on base tables.

Key Columns

The view exposes a well-defined set of columns that combine identifiers, descriptive text, dates, and quantities:

• LINE_CODE, LINE_ID — The line identifier as displayed and its internal primary key.
• PROJECT_NUMBER, PROJECT_NAME, PROJECT_ID — The project number and name resolved via PJM_PROJECT, alongside the raw project identifier.
• TASK_NUMBER, TASK_NAME, TASK_ID — The task number and name resolved via PJM_PROJECT, alongside the raw task identifier.
• SCHEDULE_NUMBER — The line schedule identifier, the key search term for this view; it associates detail rows with a specific schedule.
• SCHEDULE_TYPE_TEXT — Descriptive text indicating the schedule type (the underlying column mapped to the documented SOURCE attribute).
• ITEM_NUMBER, END_ITEM_UNIT_NUMBER, PRIMARY_ITEM_ID — The item being scheduled, its end-item unit number, and the internal item identifier.
• SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE — The planned start and completion dates for the scheduled item.
• PLANNED_QUANTITY, QUANTITY_COMPLETED, VARIANCE_QUANTITY — The planned quantity, the completed quantity, and the variance computed as NVL(PLANNED_QUANTITY,0) - NVL(QUANTITY_COMPLETED,0). The NVL handling ensures the variance never returns NULL.

Common Use Cases and Queries

This view is most commonly used in project manufacturing inquiries where users need to review schedules by project, task, line, or item, and to monitor completion status against plan. A representative query filtering on the schedule number is shown below:

• SELECT project_number, task_number, schedule_number, item_number, scheduled_start_date, planned_quantity, quantity_completed, variance_quantity FROM pjm_project_proj_ls_detail_v WHERE schedule_number = :p_schedule_number ORDER BY line_code, item_number;
• SELECT project_number, project_name, schedule_number, item_number, variance_quantity FROM pjm_project_proj_ls_detail_v WHERE project_id = :p_project_id AND variance_quantity > 0;
• SELECT line_code, item_number, scheduled_completion_date, planned_quantity FROM pjm_project_proj_ls_detail_v WHERE scheduled_start_date BETWEEN :p_start AND :p_end ORDER BY scheduled_start_date;

Typical scenarios include web inquiry pages that display line schedule detail for a selected project, exception reports highlighting schedules with open variance, and integration extracts that feed downstream planning or shop-floor systems. Because descriptive project and task values are resolved within the view, reports can present meaningful business identifiers directly, reducing the need for additional lookups or custom PL/SQL in the calling layer.