Search Results wip_res_ups_dispatch_v




Overview
Explore in AI Chat

Overview

WIP_RES_UPS_DISPATCH_V is a Work in Process (WIP) reporting view owned by the APPS schema and defined over the resource upstream dispatch entity model. Its documented description is "Resource upstream dispatch list," which positions it as a purpose-built query surface for producing dispatch information that flows upstream from a resource operation to the preceding department. In Oracle EBS 12.1.1 and 12.2.2, the view is part of the standard WIP view set shipped with the product and is used by shop-floor dispatch and work-in-process inquiry functions that need to identify, for each resource assigned to an operation, the department from which the work is arriving.

The view's specific relevance to the search term "from_department_code" is direct: it projects BD2.DEPARTMENT_CODE under the alias "FROM_DEPARTMENT_CODE", alongside the corresponding "FROM_DEPARTMENT_ID" and "FROM_OPERATION_SEQ_NUM". This allows consumers to determine the upstream department without joining BOM_DEPARTMENTS a second time. The view also carries a discharge of the earlier operation sequence number, resource identifiers, and detailed quantity and date metrics for the operation, making it a self-contained dispatch row.

Underlying Base Objects

The ETRM 12.2.2 metadata records the following referenced base objects: BOM_DEPARTMENTS, BOM_STANDARD_OPERATIONS, FND_PROFILE, MFG_LOOKUPS, MTL_SYSTEM_ITEMS_KFV, PJM_PROJECT, WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_OPERATIONS, and WIP_OPERATION_RESOURCES_V. Several of these are synonyms or views rather than base tables; notably, WIP_OPERATION_RESOURCES_V is itself a view that supplies the resource-level rows, and MTL_SYSTEM_ITEMS_KFV is the key flexfield view providing concatenated item segments. MFG_LOOKUPS is joined twice to resolve lookup meanings, and PJM_PROJECT is invoked as a package to translate project and task identifiers into names.

BOM_DEPARTMENTS appears twice in the underlying structure to supply both the current department (BD1) and the upstream, "from" department (BD2). FND_PROFILE, referenced in the metadata, is used for profile option resolution commonly associated with dispatch and shop-floor behavior. WIP_DISCRETE_JOBS and WIP_ENTITIES provide the job header and entity naming, while WIP_OPERATIONS supplies operation sequencing and a basis for the previous and next operation references.

Key Columns

Common Use Cases and Queries

Typical uses include shop-floor dispatch reports, resource loading inquiries, and integration extracts feeding manufacturing execution systems. A common query filters on the upstream department:

SELECT JOB_OP_NAME,
       WIP_ENTITY_NAME,
       ITEM_NAME,
       DEPARTMENT_CODE,
       FROM_DEPARTMENT_CODE,
       FROM_OPERATION_SEQ_NUM,
       RESOURCE_CODE,
       QUANTITY_IN_QUEUE,
       QUANTITY_RUNNING,
       SCHEDULED_START_DATE
  FROM APPS.WIP_RES_UPS_DISPATCH_V
 WHERE FROM_DEPARTMENT_CODE = :p_from_dept_code
   AND ORGANIZATION_ID = :p_org_id
 ORDER BY SCHEDULED_START_DATE, OPERATION_SEQ_NUM;

Because the view exposes both the current and upstream department, it supports ready-to-run dispatch lists without additional joins. It should be treated as operational, read-only data; validation of the row set per organization and job status remains advisable before using it as an integration source.