Search Results moved_against_planned_qty

Overview

APPS.WIP_WS_PTPKPI_AGG_V is a database view in the Oracle E-Business Suite Applications schema (APPS) that consolidates shop floor production activity against planned and unplanned quantities at the work-in-process (WIP) operation level. The object is classified as Internal / Oracle Internal Use Only, meaning Oracle Corporation does not support direct customer access to the underlying data except through standard Oracle Applications programs and concurrent requests. The view is exposed in ETRM with a Status of VALID across Oracle EBS 12.1.1 and 12.2.2.

Functionally, the view supplies aggregated Plan-to-Produce (PTP) key performance indicator (KPI) metrics for discrete and repetitive manufacturing. It combines planning figures — what a department expected to produce during a shift — with actual execution figures such as moved, scrapped, and rejected quantities. Its principal role is to feed Oracle Work in Process reporting, shop floor dashboards, and the Workstation / shop floor data collection clients that track throughput performance per organization, department, WIP job, operation sequence, and shift.

This view is the object a user is pointed to when searching for the column moved_against_planned_qty, which is the measure of quantity completed at an operation that counted toward the planned quantity for that operation within a given shift.

Underlying Base Objects

The ETRM metadata documents that WIP_WS_PTPKPI_AGG_V references two base objects, both reached through APPS synonyms:

• APPS.WIP_WS_PTPKPI_ACTUAL (SYNONYM) — provides the execution side of the metrics: quantities moved against planned and unplanned, scrapped quantity, rejected quantity, and the shift-level actual timing detail.
• APPS.WIP_WS_PTPKPI_PLAN (SYNONYM) — provides the planning side: the planned quantity for an operation and the operation lead time used for comparison.

The view joins these two sources on the shared key dimension columns — ORGANIZATION_ID, DEPARTMENT_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and SHIFT_ID — producing a single denormalized row per operation/shift combination. The metadata states that WIP_WS_PTPKPI_AGG_V is not referenced by any other database object, confirming it as a terminal reporting view rather than an intermediate construct used by other views or packages.

Key Columns

• ORGANIZATION_ID — Organization (inventory/plant) identifier.
• DEPARTMENT_ID — Department against which the operation is performed.
• WIP_ENTITY_ID — WIP job or repetitive schedule identifier.
• OPERATION_SEQ_NUM — Operation sequence number within the job routing.
• SHIFT_ID — Shift identifier (VARCHAR2, length 100).
• PLANNED_QTY — Quantity planned for the operation in the shift.
• MOVED_AGAINST_PLANNED_QTY — Quantity moved at the operation that was attributable to the planned quantity; the central PTP KPI measure.
• MOVED_AGAINST_UNPLANNED_QTY — Quantity moved that exceeded or fell outside the plan, useful for measuring unplanned yield.
• SCRAPPED_QTY — Quantity scrapped at the operation.
• REJECTED_QTY — Quantity rejected at the operation.
• PRIMARY_UOM_CODE — Unit of measure in which quantities are expressed.
• OP_LEAD_TIME — Operation lead time, used to assess scheduled versus actual duration.
• SHIFT_START_TIME — Date/time the shift began, providing the time dimension for trend analysis.

Common Use Cases and Queries

Typical scenarios include shift-level throughput analysis, planned-versus-actual attainment reporting, and scrap/reject Pareto analysis by department. The following query returns moved-against-planned attainment by department for a given organization and shift window:

 SELECT department_id,
         wip_entity_id,
         operation_seq_num,
         SUM(planned_qty)                   AS planned_qty,
         SUM(moved_against_planned_qty)     AS moved_planned,
         SUM(moved_against_unplanned_qty)   AS moved_unplanned,
         SUM(scrapped_qty)                  AS scrapped_qty,
         SUM(rejected_qty)                  AS rejected_qty
    FROM apps.wip_ws_ptpkpi_agg_v
   WHERE organization_id = :org_id
     AND shift_start_time BETWEEN :from_date AND :to_date
   GROUP BY department_id, wip_entity_id, operation_seq_num;

Because the view is flagged Oracle Internal Use Only and unsupported for direct access, production integrations should normally consume the corresponding Oracle Work in Process KPI concurrent programs or the supported shop floor data collection flows rather than reading the view directly. Where direct querying is unavoidable, access should be restricted to read-only reporting users and the view treated as subject to change between releases.