Results for “cross_reference”

1 result




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

Overview

APPS.WIP_OPSM_WORK_ORDER_EXPORT_V is a Work in Process (WIP) view that exposes discrete work orders destined for consumption by Oracle Production Scheduling (OPSM) and related manufacturing execution or shop-floor integration layers. Its purpose is to surface a work-order record in a shape suitable for export: job identity, organization, item, quantities, dates, status, lot information, and the cross-reference designation that marks the item as eligible for OPSM export. The view is registered with status VALID in the APPLS schema under the WIP product family.

The view is not a general-purpose work-order inquiry. It is deliberately filtered, and those filters are the most important thing to understand about it. The user search term mtl_cross_references is directly relevant: this table is the gating mechanism that determines which work orders appear.

Underlying Base Objects

The documented referenced base objects are:

Joins run from WIP_ENTITIES to WIP_DISCRETE_JOBS on WIP_ENTITY_ID, to MTL_PARAMETERS on ORGANIZATION_ID, and to MTL_SYSTEM_ITEMS_B_KFV on INVENTORY_ITEM_ID and ORGANIZATION_ID. Lot joins are outer, keyed on lot number, organization, and item.

Key Columns

The projection includes ORGANIZATION_ID and ORGANIZATION_CODE; WIP_ENTITY_NAME; a literal 'DISCRETE' job-type discriminator; START_QUANTITY; a decoded overcompletion tolerance (percentage applied to start quantity when tolerance type is 1, otherwise the raw value); QUANTITY_COMPLETED (repeated); the lookup meaning in upper case; and the date set — scheduled start, scheduled completion, date released, date completed, date closed.

Audit columns are carried through: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Lot columns include the job lot number and the joined LOT_NUMBER, PARENT_LOT_NUMBER, EXPIRATION_DATE, ORIGINATION_DATE, RETEST_DATE, and BEST_BY_DATE. Item columns are CONCATENATED_SEGMENTS, DESCRIPTION, and PRIMARY_UOM_CODE. FIRM_PLANNED_FLAG indicates firm-planned status.

Common Use Cases and Queries

The filter logic is the defining behavior. An organization must have OPSM_ENABLED_FLAG = 'Y' and a master organization whose ORGANIZATION_ID matches the cross-reference row. The item must be lot-controlled (MSIK.LOT_CONTROL_CODE = 2) and must carry a cross-reference of type 'OPSM INTEGRATED' with CROSS_REFERENCE = 'YES' in the master organization. A NOT EXISTS subquery then excludes any item that also holds an 'OPSM INTEGRATED' cross-reference equal to 'NO' in the work order's own organization, so an explicit opt-out overrides an opt-in.

A typical export query is a direct projection:

  • SELECT WIP_ENTITY_NAME, ORGANIZATION_CODE, CONCATENATED_SEGMENTS, START_QUANTITY, QUANTITY_COMPLETED FROM APPS.WIP_OPSM_WORK_ORDER_EXPORT_V WHERE ORGANIZATION_ID = :p_org;

Diagnostic usage commonly inspects the gating cross-reference data directly:

  • SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, CROSS_REFERENCE_TYPE, CROSS_REFERENCE FROM MTL_CROSS_REFERENCES WHERE CROSS_REFERENCE_TYPE = 'OPSM INTEGRATED';

Because the view resolves item and lot descriptions, it also serves as a readable operational report of OPSM-eligible discrete jobs, filtered by scheduled start or completion dates.