Results for “wip_pcb_res_ups_dispatch_v”

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

Overview

WIP_PCB_RES_UPS_DISPATCH_V is an APPS-owned view in the Oracle E-Business Suite Work in Process (WIP) module. It is documented as the WIP Production Control Board base view, meaning it supplies the row-level result set that drives the Production Control Board (PCB) graphical dispatch display. The PCB presents discrete job operations as nodes and resources as subordinate elements, allowing shop-floor planners and supervisors to visually monitor work in progress, identify operations on hold, and drill into job and operation detail.

The view is not a transactional entity in its own right. It is a read-only projection that consolidates discrete job headers, operations, operation resources, departments, and standard operation definitions into a single flattened structure suitable for display and reporting. Because it filters on active job statuses and on operations that still carry pending quantities, it returns work that is genuinely dispatchable rather than historical or closed activity.

Underlying Base Objects

The view selects from the following documented base objects, all exposed as APPS synonyms: WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_OPERATIONS (joined twice, as WO1 and WO2), WIP_OPERATION_RESOURCES, BOM_DEPARTMENTS, and BOM_STANDARD_OPERATIONS. The FND_PROFILE package is also referenced in the object metadata, typically for organization or user context resolution.

• WIP_DISCRETE_JOBS (WDJ) — restricts rows to jobs whose STATUS_TYPE is 3 (Released), 4 (Complete — charges allowed), or 6 (On Hold), and requires a non-null PRIMARY_ITEM_ID.
• WIP_ENTITIES (WE) — supplies the WIP_ENTITY_NAME and enforces ENTITY_TYPE = 1 (discrete job).
• WIP_OPERATIONS (WO1) — the primary operation row, providing ORGANIZATION_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and FIRST_UNIT_START_DATE.
• WIP_OPERATIONS (WO2) — a self-join on NEXT_OPERATION_SEQ_NUM that keeps only operations with quantity waiting to move, in queue, or running greater than zero.
• WIP_OPERATION_RESOURCES (WOR) — joined by organization, entity, and operation sequence to associate resources.
• BOM_DEPARTMENTS (BD1) — resolves the department, defaulting to the operation department when the resource department is null.
• BOM_STANDARD_OPERATIONS (BSO) — an outer join retained only where OPERATION_TYPE is 1 and LINE_ID is null, excluding line operations.

Key Columns

• ORGANIZATION_ID — operating unit/warehouse context for the job.
• WIP_ENTITY_ID — the discrete job identifier, and the column most commonly used to join back to WIP_DISCRETE_JOBS, WIP_ENTITIES, or WIP_OPERATIONS. This is the field users typically search for when navigating from this view.
• DEPARTMENT_ID — the department responsible for the resource or operation.
• OPERATION_SEQ_NUM — the routing sequence number of the operation.
• RESOURCE_ID / RESOURCE_SEQ_NUM — the resource assigned to the operation; the sequence number is aggregated, returning a value only when exactly one matching resource row exists.
• JOB_OP_NAME — concatenation of WIP_ENTITY_NAME and operation sequence, used as the node label.
• NODE_TEXT_COLOR / NODE_ICON — both driven by DECODE on WDJ.STATUS_TYPE = 6, yielding 'RED' and 'WPJOBOPH.GIF' for jobs on hold.
• FIRST_UNIT_START_DATE — the scheduled start date for the first unit.

Common Use Cases and Queries

The primary use case is feeding the Production Control Board for a given organization, highlighting hold conditions in red. Reporting and integration scenarios typically filter by organization and status, or resolve a specific job using WIP_ENTITY_ID.

Sample query listing dispatchable operations for a job:

• SELECT wip_entity_id, operation_seq_num, department_id, resource_id, job_op_name, node_text_color, first_unit_start_date FROM wip_pcb_res_ups_dispatch_v WHERE organization_id = :org_id AND wip_entity_id = :wip_entity_id ORDER BY operation_seq_num;
• SELECT department_id, COUNT(*) FROM wip_pcb_res_ups_dispatch_v WHERE organization_id = :org_id AND node_text_color = 'RED' GROUP BY department_id;

Because the view performs aggregation and self-joins, it should be queried with selective predicates on ORGANIZATION_ID and WIP_ENTITY_ID to avoid full scans on large shops.