Results for “first_unit_start_date”

50+ results




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

Overview

The WIP_PCB_RES_IMM_DISPATCH_V view is a Work in Process (WIP) Production Control Board base view owned by the APPS schema. It is a read-only view, as indicated by the WITH READ ONLY clause in its definition, and serves as a foundational data source for the Production Control Board (PCB) graphical dispatch interface used by production supervisors to monitor and dispatch shop floor operations. The view assembles discrete job operation and resource information into a row-per-resource presentation that is consumed by the PCB applet to render node objects and their status indicators.

In Oracle EBS 12.1.1 and 12.2.2, the Production Control Board is a critical shop floor tool. This view supplies the job-operation naming, node colour coding, node icons, and the identifying keys required to link dispatched entities to downstream PCB actions. Because the view filters defensively at the SQL level — restricting to discrete jobs and to operations with pending or active quantities — it delivers exactly the records the PCB expects for immediate dispatch display.

Underlying Base Objects

Per ETRM metadata, the view is defined over the following base objects:

An inline comment in the view text notes that joining the repetitive schedule is unnecessary, confirming the view targets discrete jobs exclusively.

Key Columns

  • ORGANIZATION_ID — the inventory organization key.
  • WIP_ENTITY_ID and WIP_ENTITY_NAME — job identifiers.
  • OPERATION_SEQ_NUM — the operation sequence within the job.
  • JOB_OP_NAME — concatenation of WIP_ENTITY_NAME, a colon, and the operation sequence, used as the display label.
  • RESOURCE_ID and RESOURCE_SEQ_NUM — resource-level identifiers; the sequence number is summed and only returned when a single resource sequence exists, otherwise NULL.
  • DEPARTMENT_ID — the department, resolved from the resource or, failing that, the operation.
  • NODE_TEXT_COLOR — returns 'RED' when the job status is 6 (On Hold), otherwise NULL.
  • NODE_ICON — returns 'WPJOBOPH.GIF' when the job is On Hold, otherwise NULL; this drives the PCB graphic.
  • FIRST_UNIT_START_DATE — the scheduled first-unit start date for the operation.

Common Use Cases and Queries

Typical use cases include PCB dispatch rendering, shop floor status queries, and custom dashboards that need operation-level job data with resource details. A representative query filters by organization and status colour:

  • Retrieve all jobs that the PCB would currently present for an organization.
  • Identify On Hold operations using the red node indicator.
  • Report the department or resource distribution across active discrete jobs.

Example:

SELECT wip_entity_name, operation_seq_num, job_op_name, department_id, resource_id, node_text_color, first_unit_start_date FROM apps.wip_pcb_res_imm_dispatch_v WHERE organization_id = :org_id ORDER BY wip_entity_name, operation_seq_num;

Because the view is read-only and already applies the discrete-job and status filters, custom queries should not re-implement those filters. Users with access to the APPS schema or a synonym may query it directly. Note that the FND_PROFILE dependency means WIP_DISPLAY_SCRAP_REJECT must be correctly set per user or responsibility for scrap rows to appear.