Search Results wip_dept_ups_dispatch_v




Overview
Explore in AI Chat

Overview

WIP_DEPT_UPS_DISPATCH_V is a Work in Process (WIP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Department upstream dispatch list." The view consolidates discrete job header data, operation-level routing detail, department definitions, item master descriptions, and Workflow job status information into a single denormalized result set. This makes it suitable for shop-floor dispatch reporting, where a planner or production supervisor requires a list of operations awaiting release to a department from an upstream (feeding) department.

The view resolves the master-detail relationships that otherwise require multiple joins between WIP_DISCRETE_JOBS, WIP_ENTITIES, and WIP_OPERATIONS. It also joins the current operation to its predecessor operation so that the upstream department responsible for feeding the current department is identified. Because the view includes quantity columns for every WIP operation status and both operation and department codes, it functions as a ready-to-query source for custom reports, Oracle Discoverer worksheets, BI Publisher data templates, and third-party MES integration extracts.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

  • WIP_ENTITIES (synonym) — job header, supplying WIP_ENTITY_NAME.
  • WIP_DISCRETE_JOBS (synonym) — discrete job scheduling, status type, and project/task attributes.
  • WIP_OPERATIONS (synonym) — operation sequence numbers, quantities, and dates. Appears twice (WO1, WO2) to derive current and previous operation sequences.
  • BOM_DEPARTMENTS (synonym) — department code and ID, appearing twice (BD1, BD2) for the current and upstream departments.
  • BOM_STANDARD_OPERATIONS (synonym) — standard operation code.
  • MTL_SYSTEM_ITEMS_KFV (synonym) — concatenated item segments, description, and primary UOM.
  • MFG_LOOKUPS (view) — lookup meanings for count point and backflush flags.
  • PJM_PROJECT (package) — project and task number conversion via ALL_PROJ_IDTONUM and ALL_TASK_IDTONUM.
  • FND_PROFILE (package) — referenced in the view definition for profile-based filtering or security.

Key Columns

Common Use Cases and Queries

Typical usage includes generating department dispatch lists, identifying operations waiting to move from an upstream department, and building shop-floor dashboards. Project and task filtering supports project manufacturing reporting.

Sample query listing pending dispatch operations for an organization:

  • SELECT job_op_name, department_code, from_department_code, quantity_in_queue, quantity_waiting_to_move, scheduled_start_date FROM apps.wip_dept_ups_dispatch_v WHERE organization_id = :org_id;

Sample query to identify bottlenecks by upstream department:

  • SELECT from_department_code, department_code, SUM(scheduled_quantity) FROM apps.wip_dept_ups_dispatch_v WHERE organization_id = :org_id GROUP BY from_department_code, department_code;

Because the view spans many base objects, queries should always be filtered by ORGANIZATION_ID and, where possible, by department or job to avoid unnecessary full scans. As with all APPS views, access is governed through responsibilities and the FND_PROFILE references embedded in the definition.