Search Results count_point




Overview
Explore in AI Chat

Overview

WIP_INST_EMP_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 purpose is to present an employee resource instance upstream dispatch list. In discrete manufacturing, an operation may draw on employee resources whose individual assignments (instances) are dispatched from a supplying — or "upstream" — operation. This view exposes that dispatch relationship in a single flattened row per job, operation, resource, and employee instance, including quantities, department routing, count point indicators, backflush flags, and scheduling dates. It is intended primarily for inquiry, dispatch-list reporting, and integration surfaces (for example, shop-floor dispatch or MES-style extracts) rather than for transactional update. Because the view is a join of many WIP, BOM, and HR objects, it should be queried with selective predicates and is not a substitute for a base-table DML path.

Underlying Base Objects

ETRM documents the following referenced objects: BOM_DEPARTMENTS, BOM_RESOURCES, BOM_RESOURCE_EMPLOYEES, BOM_STANDARD_OPERATIONS, FND_PROFILE (package), MFG_LOOKUPS (view), MTL_SYSTEM_ITEMS_KFV, PER_ALL_PEOPLE_F, PJM_PROJECT (package), WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_OPERATIONS, WIP_OPERATION_RESOURCES_V (view), and WIP_OP_RESOURCE_INSTANCES. The structure is anchored on WIP_DISCRETE_JOBS (the job header), joined to WIP_ENTITIES for the entity name, WIP_OPERATIONS for the current and adjacent operation sequences, and WIP_OPERATION_RESOURCES_V for resource assignments. Employee instances come from BOM_RESOURCE_EMPLOYEES and WIP_OP_RESOURCE_INSTANCES, with the person's name resolved from PER_ALL_PEOPLE_F. Departments (BOM_DEPARTMENTS) supply both the current and the "from" routing context, BOM_STANDARD_OPERATIONS supplies the operation code, MTL_SYSTEM_ITEMS_KFV supplies the concatenated item and description, and MFG_LOOKUPS is joined twice to decode the count point and backflush lookup meanings. PJM_PROJECT provides project and task name resolution, and FND_PROFILE is referenced for profile-driven behavior.

Key Columns

Common Use Cases and Queries

Typical uses include employee dispatch lists for a department, count-point verification, and quantity-in-queue reporting. The sample below filters count-point operations for one organization.

SELECT WIP_ENTITY_NAME, OPERATION_SEQ_NUM, DEPARTMENT_CODE, RESOURCE_CODE, FULL_NAME, COUNT_POINT, SCHEDULED_QUANTITY, QUANTITY_RUNNING, QUANTITY_COMPLETED FROM APPS.WIP_INST_EMP_UPS_DISPATCH_V WHERE ORGANIZATION_ID = :org_id AND COUNT_POINT IS NOT NULL ORDER BY WIP_ENTITY_NAME, OPERATION_SEQ_NUM;

A second pattern lists employee instances awaiting dispatch from a feeding operation:

SELECT JOB_OP_NAME, ITEM_NAME, FROM_DEPARTMENT_CODE, DEPARTMENT_CODE, FULL_NAME, INSTANCE_ID FROM APPS.WIP_INST_EMP_UPS_DISPATCH_V WHERE ORGANIZATION_ID = :org_id AND DEPARTMENT_CODE = :dept AND FULL_NAME IS NOT NULL;

Because the view aggregates resource sequences across many joins, consumers should bind ORGANIZATION_ID and job or operation keys, and treat results as read-only.