Search Results node_icon




Overview
Explore in AI Chat

Overview

The APPS.WIP_PCB_DEPT_IMM_DISPATCH_V view is a Work in Process (WIP) reporting object that supplies the base data set for the Production Control Board (PCB) in Oracle E-Business Suite 12.1.1 and 12.2.2. Unlike a transactional entity view, this object is purpose-built to feed a graphical dispatch and scheduling interface: it returns one row for each discrete job operation that is currently eligible for shop-floor dispatch activity within a department. The view exposes the identifiers, display text, status-driven visual attributes, and the earliest start date required to render jobs on the control board.

The object is owned by the APPS schema and carries a reported status of VALID. It is defined with the READ ONLY clause and includes a GROUP BY, which means it cannot be used as the target of DML and is intended strictly for query, reporting, and interface consumption. Consultants searching on the term "job_op_name" are typically attempting to locate the concatenated job and operation label used by the PCB; that label is generated directly within this view.

Underlying Base Objects

The view is defined over the following documented referenced objects: WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_OPERATIONS, BOM_DEPARTMENTS, and BOM_STANDARD_OPERATIONS (all exposed through synonyms), together with the FND_PROFILE package used for a profile-option check.

  • WIP_OPERATIONS — supplies the core rows (job, organization, operation sequence, department, and quantities), aliased as WO.
  • WIP_ENTITIES — supplies the WIP entity name used to build the job operation label, aliased as WE.
  • WIP_DISCRETE_JOBS — supplies job status, used both to filter eligible jobs and to derive display color and icon, aliased as WDJ.
  • BOM_DEPARTMENTS — supplies department and organization references, aliased as BD.
  • BOM_STANDARD_OPERATIONS — outer-joined to restrict rows to standard operations of the appropriate type, aliased as BSO.
  • FND_PROFILE — read via FND_PROFILE.VALUE('WIP_DISPLAY_SCRAP_REJECT') to determine whether scrap and reject quantities participate in the row-inclusion logic.

Key Columns

  • ORGANIZATION_ID and DEPARTMENT_ID — identify the inventory organization and the department where the operation is dispatched.
  • WIP_ENTITY_ID — the discrete job identifier used for drill-down.
  • OPERATION_SEQ_NUM — the operation sequence number within the job.
  • JOB_OP_NAME — the display label built as WIP_ENTITY_NAME concatenated with ':' and the operation sequence number (the resource sequence segment is commented out in the definition).
  • NODE_TEXT_COLOR — DECODE on WIP_DISCRETE_JOBS.STATUS_TYPE; returns 'RED' when status is 6 (On Hold), otherwise NULL.
  • NODE_ICON — DECODE on the same status; returns 'WPJOBOPH.GIF' for status 6, otherwise NULL.
  • FIRST_UNIT_START_DATE — the scheduled start of the first unit, used for board sequencing.

Common Use Cases and Queries

Typical uses include building custom dispatch lists, replicating PCB content in reports, and identifying held operations within a department. Eligible jobs are limited to discrete jobs (ENTITY_TYPE = 1) with status types 3, 4, or 6 (released, complete-charges-allowed, or on hold) and a non-null primary item, and operations must have open quantities (or open plus scrap/reject when the profile permits).

  • Retrieve all dispatchable operations for a department: SELECT job_op_name, operation_seq_num, node_text_color, first_unit_start_date FROM wip_pcb_dept_imm_dispatch_v WHERE organization_id = :org AND department_id = :dept.
  • Isolate on-hold operations requiring attention: add WHERE node_icon = 'WPJOBOPH.GIF'.
  • List jobs by operation name for a report parameter: SELECT DISTINCT job_op_name FROM wip_pcb_dept_imm_dispatch_v WHERE organization_id = :org ORDER BY job_op_name.

Because the view is READ ONLY and grouped, all access must be through SELECT statements.