Results for “pjm_line_schedules_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PJM_LINE_SCHEDULES_V is an Oracle EBS PL/SQL view owned by the APPS schema and classified as VALID. It belongs to the PJM (Project Manufacturing) product family and is described in the ETRM metadata as a "Project related line scheduling details view for web inquiry." The view exposes scheduling information for project-related manufacturing work — both discrete jobs and repetitive flow schedules — filtered to records where a PROJECT_ID is populated, meaning it is scoped specifically to project manufacturing activity rather than standard (non-project) production.

Its role is to provide a consolidated, query-friendly read model over the underlying WIP and inventory tables so that web-based inquiry screens (and downstream reports or integrations) can retrieve project line scheduling details without joining the base transactional tables directly. The presence of ROW_ID in the projection, combined with the "web inquiry" designation, indicates the view is intended to support Forms/web inquiry frameworks that require a row identifier for navigation and drill-down.

Underlying Base Objects

The documented ETRM metadata for the 12.2.2 release lists the referenced base objects as MFG_LOOKUPS (VIEW), MTL_SYSTEM_ITEMS_KFV (SYNONYM), WIP_DISCRETE_JOBS (SYNONYM), WIP_ENTITIES (SYNONYM), WIP_FLOW_SCHEDULES (SYNONYM), and WIP_LINES (SYNONYM). The view text aligns with this: it is a UNION ALL of two branches. The first branch joins WIP_DISCRETE_JOBS (aliased JOB) to WIP_ENTITIES and MTL_SYSTEM_ITEMS_KFV to retrieve discrete-job project line schedules. The second branch joins WIP_FLOW_SCHEDULES (aliased FLOW) to the same item key flexfield view to retrieve repetitive/flow schedules.

MFG_LOOKUPS is referenced twice in the discrete branch — once as WST for the MRP_WIP_SCHEDULE_TYPE lookup (LOOKUP_CODE = 1, schedule type) and once as WJS for the WIP_JOB_STATUS lookup — and once in the flow branch (LOOKUP_CODE = 2). WIP_LINES is joined in both branches on LINE_ID and ORGANIZATION_ID to supply the line code. Because these referenced objects are synonyms, they resolve through the standard APPS public synonyms to the underlying WIP and MTL base tables and item key flexfield views.

Key Columns

The view projects a consistent column set across both UNION ALL branches:

• ROW_ID — the physical ROWID of the source row (JOB.ROWID or FLOW.ROWID), used as a row handle for inquiry navigation.
• PROJECT_ID / TASK_ID — the project and task identifiers that qualify the record as project manufacturing; PROJECT_ID is the mandatory filter (IS NOT NULL) in both branches.
• LINE_ID / LINE_CODE — the scheduling line identifier and its code, sourced from WIP_LINES (e.g., "Line1" in manufacturing line schedules).
• SCHEDULE_TYPE / SCHEDULE_TYPE_TEXT — the schedule type lookup code and its meaning, driven by the MRP_WIP_SCHEDULE_TYPE lookup.
• SCHEDULE_NUMBER — the schedule/document number; for discrete jobs this is WIP_ENTITY_NAME, and for flow schedules it is SCHEDULE_NUMBER.
• ORG — the organization identifier (ORGANIZATION_ID) in which the schedule executes.
• PRIMARY_ITEM_ID / KFV.CONCATENATED_SEGMENTS — the assembled item identifier and its concatenated key flexfield segments (the human-readable item number).
• END_ITEM_UNIT_NUMBER — the unit number of the end product, supporting unit-tracked (e.g., project/serial-tracked) items.
• SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE — planned schedule window for the line.
• DATE_CLOSED — the date on which the schedule was closed, where applicable.
• START_QUANTITY / PLANNED_QUANTITY — the released start quantity for discrete jobs (START_QUANTITY) and the planned quantity for flow schedules (PLANNED_QUANTITY), unified across branches.
• QUANTITY_COMPLETED — quantity completed against the schedule.

Note that the two branches supply slightly different source columns to the shared column names (WIP_ENTITY_NAME vs SCHEDULE_NUMBER; START_QUANTITY vs PLANNED_QUANTITY), which is why a UNION ALL is required to present a single result set.

Common Use Cases and Queries

Typical scenarios include web-based project manufacturing inquiry screens, line-loading and schedule reports, project-status dashboards, and integration extracts that need project-scoped line schedules without touching WIP tables directly. Because the view already enforces PROJECT_ID IS NOT NULL and resolves lookups and item segments, it is convenient for reporting layers.

A representative query retrieving schedules for a given project:

• SELECT schedule_number, line_code, schedule_type_text, concatenated_segments, scheduled_start_date, scheduled_completion_date, quantity_completed FROM pjm_line_schedules_v WHERE project_id = :p_project_id AND org = :p_org_id ORDER BY scheduled_start_date;

To review open project line schedules by task:

• SELECT project_id, task_id, line_code, start_quantity, planned_quantity, quantity_completed FROM pjm_line_schedules_v WHERE date_closed IS NULL ORDER BY scheduled_start_date;

Practical cautions: query the view through the APPS schema or a synonym, not the base tables, to guarantee the lookup and flexfield joins are applied; and be aware that the schedule number is sourced from different columns depending on whether the row is a discrete job or a flow schedule, so downstream logic should not assume a single semantic origin. When the view returns no rows for an organization, verify that the organization is a project manufacturing (PJM) organization and that PROJECT_ID is populated on the underlying jobs and schedules.