Results for “intraoperation_step_type”

50+ results




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

Overview

The APPS.WIP_DISC_INTRAOP_STEPS_VAL_V view is a Work in Process (WIP) reporting and integration object that exposes the discrete intraoperation step status of released jobs and schedules. In Oracle EBS 12.1.1 and 12.2.2, WIP tracks shop floor quantities across five discrete intraoperation steps — Queue, Running, Waiting to Move, Rejected, and Scrapped — and this view consolidates those quantities into a single denormalized result set keyed by organization, WIP entity, and operation sequence. It serves as a validated, stable read interface for reports, dashboards, and external integrations that must determine how much material currently sits at each intraoperation step.

Because the object is a view rather than a table, it presents no stored data of its own; it derives its rows dynamically from WIP operation quantity columns and WIP intraoperation step configuration. It is registered as VALID in the APPS schema and is documented under the WIP - Work in Process product for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over three documented objects:

The join is on ORGANIZATION_ID between WIP_OPERATIONS and WIP_VALID_INTRAOPERATION_STEPS, with a lookup join on LOOKUP_CODE = STEP_LOOKUP_TYPE. Row eligibility is constrained by a compound predicate: steps recorded as USER-created are always returned, step type 1 (Queue) is returned regardless of creator, and SYSTEM-created steps are returned only when the next operation sequence is null (that is, the final operation). This logic prevents system-seeded steps from appearing prematurely on intermediate operations.

Key Columns

Common Use Cases and Queries

Typical uses include shop floor status reporting, WIP quantity reconciliation, and feeders for MES or analytics extracts. A representative query returning current step quantities for a job is:

SELECT organization_id
     , wip_entity_id
     , operation_seq_num
     , intraoperation_step_meaning
     , intraoperation_step_quantity
  FROM apps.wip_disc_intraop_steps_val_v
 WHERE organization_id = :p_org_id
   AND wip_entity_id   = :p_wip_entity_id
 ORDER BY operation_seq_num, intraoperation_step_type;

Aggregated queue-versus-running comparisons across an organization are equally straightforward:

SELECT operation_seq_num
     , intraoperation_step_meaning
     , SUM(intraoperation_step_quantity) total_qty
  FROM apps.wip_disc_intraop_steps_val_v
 WHERE organization_id = :p_org_id
 GROUP BY operation_seq_num, intraoperation_step_meaning;

Because the view already resolves step types to meanings, it is preferable to joining MFG_LOOKUPS manually, and it respects the same creator and final-operation rules applied by the WIP discrete intraoperation validation logic.