Search Results schedule_type_text




Overview
Explore in AI Chat

Overview

APPS.PJM_PROJECT_PROJ_LS_DETAIL_V is a reporting view in the Oracle EBS Project Manufacturing (PJM) module. It exposes line-level scheduling detail for project and task combinations, projecting the schedule of a line item against its scheduled dates, ordered quantities, and completion quantities. The view is defined over PJM_LINE_SCHEDULES_V, itself a view, and calls the PJM_PROJECT package for ID-to-number and ID-to-name conversions. In both 12.1.1 and 12.2.2, the view serves as a stable read-only interface for reporting, inquiry, and integration, shielding consumers from the join logic and the package calls embedded in the underlying source. Its ORDER BY on LINE_CODE, ITEM_NUMBER, and SCHEDULED_START_DATE gives deterministic sequencing suitable for report layouts and extracts.

Underlying Base Objects

The view's FROM clause references exactly one object, PJM_LINE_SCHEDULES_V, a view rather than a base table. Two package functions from PJM_PROJECT are invoked in the SELECT list: ALL_PROJ_IDTONUM and ALL_PROJ_IDTONAME (applied to PROJECT_ID), and ALL_TASK_IDTONUM and ALL_TASK_IDTONAME (applied to TASK_ID). ETRM documents PJM_PROJECT as a PACKAGE and PJM_LINE_SCHEDULES_V as a VIEW. Because the projection layer is a view, no materialization occurs; each execution re-evaluates the underlying schedule query and the package calls. Consumers should note that the derived project and task number/name columns are computed per row, which can add cost in high-volume extracts.

Key Columns

  • LINE_CODE — Line identifier used as the primary ordering key.
  • LINE_ID — Internal identifier for the schedule line.
  • PROJECT_ID / TASK_ID — Internal keys, retained for joins to project and task tables.
  • ALL_PROJ_IDTONUM(PROJECT_ID) / ALL_PROJ_IDTONAME(PROJECT_ID) — Project number and project name derived via the PJM_PROJECT package.
  • ALL_TASK_IDTONUM(TASK_ID) / ALL_TASK_IDTONAME(TASK_ID) — Task number and task name derived via the same package.
  • SCHEDULE_TYPE_TEXT — Descriptive text classifying the line schedule. This is the column most frequently searched as "schedule_type_text" and is used to distinguish schedule categories in reports.
  • SCHEDULE_NUMBER — The schedule document number.
  • ITEM_NUMBER, END_ITEM_UNIT_NUMBER, PRIMARY_ITEM_ID — Item identifiers, including the end-item unit number and the internal primary item key.
  • SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE — Planned schedule window.
  • NVL(PLANNED_QUANTITY,0) — Planned quantity, defaulted to zero.
  • NVL(QUANTITY_COMPLETED,0) — Completed quantity, defaulted to zero.
  • NVL(PLANNED_QUANTITY,0) - NVL(QUANTITY_COMPLETED,0) — Open (remaining) quantity; a computed column with no alias in the view definition.

Common Use Cases and Queries

Typical usage includes schedule-versus-completion reporting, open-quantity analysis, and extracts feeding downstream systems that consume schedule type, item, and date information.

SELECT line_code
     , project_id
     , task_id
     , schedule_type_text
     , schedule_number
     , item_number
     , scheduled_start_date
     , scheduled_completion_date
     , (NVL(planned_quantity,0) - NVL(quantity_completed,0)) AS open_qty
  FROM apps.pjm_project_proj_ls_detail_v
 WHERE schedule_type_text = :p_schedule_type
   AND scheduled_start_date >= :p_from_date
 ORDER BY line_code, item_number, scheduled_start_date;

For project-level roll-ups, consumers join PROJECT_ID to PJ_PROJECTS and TASK_ID to PJ_PROJ_ELEMENTS rather than relying on the packaged name functions. Because the view applies its own ORDER BY, ordering clauses in the consuming query are redundant unless an alternate sequence is required. All access should be granted through the APPS schema, consistent with standard EBS responsibility-driven security.