Search Results node_icon




Overview
Explore in AI Chat

Overview

The APPS.WIP_PCB_DEPT_IMM_DISPATCH_V view is a reporting and integration object within the Oracle E-Business Suite Work in Process (WIP) application, specifically oriented toward printed circuit board (PCB) manufacturing environments. The view name — a departmental "immediate dispatch" view — indicates that it exposes the current operational dispatch information for discrete jobs by department, providing the descriptive attributes required by a shop-floor dispatch or scheduling presentation layer. The view is owned by the APPS schema and carries an ETRM status of VALID. It is registered in FND Design Data as WIP.WIP_PCB_DEPT_IMM_DISPATCH_V, confirming it is a seeded, Oracle-delivered object rather than a customer extension.

The view is flagged with Oracle's standard internal-use notice: Oracle does not support direct access to application data through this object except from standard Oracle Applications programs. Its view type is documented as Internal, and it is not referenced by any other database object in the ETRM dependency graph, indicating it functions as a terminal, presentation-oriented view rather than a reused building block.

Underlying Base Objects

WIP_PCB_DEPT_IMM_DISPATCH_V is defined over several application synonyms that resolve to the following base entities:

  • WIP_DISCRETE_JOBS — the discrete job header, supplying the WIP entity reference and scheduling context.
  • WIP_ENTITIES — the central WIP entity master that carries the WIP_ENTITY_ID primary key and links jobs to their identifiers.
  • WIP_OPERATIONS — the job operation rows, providing operation sequence numbers and department routing.
  • BOM_DEPARTMENTS — the department definition, supplying the DEPARTMENT_ID and associated organizational context.
  • BOM_STANDARD_OPERATIONS — the standard operation definition, contributing operation naming information such as JOB_OP_NAME.
  • FND_PROFILE — the Oracle profile package, used at runtime to resolve profile option values governing the presentation attributes exposed by the view.

The join pattern across WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_OPERATIONS, BOM_DEPARTMENTS, and BOM_STANDARD_OPERATIONS produces one row per job operation per department, enriched with display metadata. FND_PROFILE is referenced to drive organizational or user-dependent behavior rather than to produce rows.

Key Columns

  • ORGANIZATION_ID (NUMBER) — the inventory organization in which the job resides; the primary multi-org filter key.
  • DEPARTMENT_ID (NUMBER) — the department to which the operation is dispatched, resolved from BOM_DEPARTMENTS.
  • WIP_ENTITY_ID (NUMBER) — the discrete job identifier linking the row back to WIP_ENTITIES.
  • OPERATION_SEQ_NUM (NUMBER) — the operation sequence within the job, ordering the routing steps.
  • JOB_OP_NAME (VARCHAR2, 281) — the descriptive job operation name presented to the user.
  • NODE_TEXT_COLOR (VARCHAR2) — the display color for the node text, driven by profile-derived logic.
  • NODE_ICON (VARCHAR2, 12) — the icon identifier rendered as the node graphic in the dispatch display. This column corresponds directly to the user's "node_icon" search term.
  • FIRST_UNIT_START_DATE (DATE) — the date on which the first unit of the operation is scheduled or actually started, supporting sequencing and priority decisions.

Common Use Cases and Queries

This view supports departmental dispatch boards, work-center status reporting, and integrations that need a flat, presentation-ready list of jobs by department with visual indicators. A typical query filters by organization and department:

  • SELECT WIP_ENTITY_ID, DEPARTMENT_ID, OPERATION_SEQ_NUM, JOB_OP_NAME, NODE_ICON, FIRST_UNIT_START_DATE FROM APPS.WIP_PCB_DEPT_IMM_DISPATCH_V WHERE ORGANIZATION_ID = :org_id AND DEPARTMENT_ID = :dept_id ORDER BY FIRST_UNIT_START_DATE, OPERATION_SEQ_NUM;
  • SELECT NODE_ICON, NODE_TEXT_COLOR, COUNT(*) FROM APPS.WIP_PCB_DEPT_IMM_DISPATCH_V WHERE ORGANIZATION_ID = :org_id GROUP BY NODE_ICON, NODE_TEXT_COLOR;
  • SELECT j.WIP_ENTITY_ID, j.JOB_OP_NAME, j.FIRST_UNIT_START_DATE FROM APPS.WIP_PCB_DEPT_IMM_DISPATCH_V j WHERE j.ORGANIZATION_ID = :org_id AND j.FIRST_UNIT_START_DATE <= SYSDATE ORDER BY j.FIRST_UNIT_START_DATE;

Because the view is marked internal and unsupported for direct external access, integrations should be implemented cautiously, and any reliance on NODE_ICON or NODE_TEXT_COLOR should account for profile-dependent variation across environments in both 12.1.1 and 12.2.2.