Search Results wip_pcb_dept_ups_dispatch_v




Overview
Explore in AI Chat

Overview

WIP_PCB_DEPT_UPS_DISPATCH_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the Work in Process (WIP) product. It serves as a base view for the WIP Production Control Board (PCB), the graphical dispatch and shop-floor monitoring interface used by production supervisors to sequence and track discrete manufacturing work orders by department and operation.

The view supplies the node-level data consumed by the Production Control Board when it renders the "UPS Dispatch" layout — a graphical network of jobs and operations flowing through departments. It exposes a single row per active job operation that is ready to be dispatched, together with the color and icon indicators the PCB uses to flag jobs currently on hold. Because it is an APPS-owned view with no column-level security beyond standard EBS responsibility and organization access, it is commonly referenced in custom reports, dashboard queries, and integration extracts that need a dispatch-oriented snapshot of shop-floor activity.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over the following base objects (all accessed through APPS synonyms): BOM_DEPARTMENTS, BOM_STANDARD_OPERATIONS, WIP_DISCRETE_JOBS, WIP_ENTITIES, and WIP_OPERATIONS. The FND_PROFILE package is also referenced in the underlying dependency set.

  • WIP_ENTITIES / WIP_DISCRETE_JOBS — Restrict the result set to discrete jobs (ENTITY_TYPE = 1) whose status is Released (3), Complete Charges Allowed (4), or On Hold (6), and whose primary item is populated.
  • WIP_OPERATIONS (aliased WO1 and WO2) — WO1 supplies the current operation; WO2 is joined on NEXT_OPERATION_SEQ_NUM to ensure the operation actually has work pending.
  • BOM_DEPARTMENTS — Provides the department context (DEPARTMENT_ID) for the operation.
  • BOM_STANDARD_OPERATIONS — Outer-joined (via the (+) operator) on STANDARD_OPERATION_ID and filtered to OPERATION_TYPE = 1 with LINE_ID null, so routings without a matching standard operation are still eligible.

Key Columns

  • ORGANIZATION_ID — Operating unit/warehouse organization that owns the job.
  • DEPARTMENT_ID — Department associated with the routing operation; used to group nodes by department on the PCB.
  • WIP_ENTITY_ID — Identifier of the discrete job; joins to WIP_DISCRETE_JOBS and WIP_ENTITIES.
  • OPERATION_SEQ_NUM — Sequence number of the operation shown for the job.
  • JOB_OP_NAME — Concatenation of WIP_ENTITY_NAME and OPERATION_SEQ_NUM (e.g., "JOB123:20"), used as the node label.
  • NODE_TEXT_COLOR — Returns 'RED' when the job status type is 6 (On Hold); otherwise null.
  • NODE_ICON — Returns the icon filename 'WPJOBOPH.GIF' for on-hold jobs; otherwise null.
  • FIRST_UNIT_START_DATE — Scheduled start date of the first unit, used for dispatch sequencing and priority.

Common Use Cases and Queries

Typical scenarios include building departmental dispatch lists, identifying held operations for escalation, and extracting pending work for shop-floor integration. Because the view already filters to operations where WO2 has waiting-to-move, in-queue, or running quantities greater than zero, it returns only operations with active work.

To list all dispatched operations for an organization and department:

  • SELECT wip_entity_id, job_op_name, node_text_color, first_unit_start_date
  • FROM apps.wip_pcb_dept_ups_dispatch_v
  • WHERE organization_id = :org_id AND department_id = :dept_id
  • ORDER BY first_unit_start_date;

To isolate jobs on hold that require supervisory attention:

  • SELECT job_op_name, department_id, first_unit_start_date
  • FROM apps.wip_pcb_dept_ups_dispatch_v
  • WHERE node_text_color = 'RED'
  • AND organization_id = :org_id;

The view is read-only (WITH READ ONLY) and should be queried rather than modified. Access is governed by standard WIP and organization-level security, so reports should always filter by ORGANIZATION_ID to respect multi-org boundaries.