Results for “wip_rep_intraop_steps_val_v”

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

Overview

The view WIP_REP_INTRAOP_STEPS_VAL_V (owner APPS) exposes repetitive intraoperation step quantities for discrete and repetitive Work in Process activity in Oracle E-Business Suite. Its documented description is "Repetitive intraoperation steps." Within the WIP (Work in Process) module, intraoperation steps represent the intermediate states through which a job or schedule passes at a given operation — queued, running, waiting to move, rejected, and scrapped. This view consolidates those states into a single row per organization, WIP entity, production line, operation sequence, and step type, aggregating the corresponding quantity.

The view is primarily a reporting and integration object. Because it surfaces both the numeric step type (INTRAOPERATION_STEP_TYPE) and its translated label (INTRAOPERATION_STEP_MEANING), it is well suited to operational dashboards, production floor inquiries, and extracts that require human-readable step descriptions rather than lookup codes. The presence of the literal string intraoperation_step_meaning in user searches reflects the common need to resolve the WIP_INTRAOPERATION_STEP lookup into readable text.

Underlying Base Objects

The view is defined over four documented base objects: MFG_LOOKUPS (VIEW), WIP_OPERATIONS (SYNONYM), WIP_REPETITIVE_SCHEDULES (SYNONYM), and WIP_VALID_INTRAOPERATION_STEPS (SYNONYM). These are joined and aliased as LU, WO, WRS, and WVIS respectively.

• MFG_LOOKUPS supplies the translated meaning where LOOKUP_TYPE = 'WIP_INTRAOPERATION_STEP' and LOOKUP_CODE matches the step type.
• WIP_VALID_INTRAOPERATION_STEPS defines which step types are valid for each organization and operation, carrying the RECORD_CREATOR flag that governs applicability.
• WIP_REPETITIVE_SCHEDULES provides the production LINE_ID and restricts the result to schedule statuses 1, 3, 4, and 6 (released and active states).
• WIP_OPERATIONS provides the operation sequence, next operation sequence, and the queue, running, waiting-to-move, rejected, and scrapped quantities that are summed per step.

Steps are included only where the record is user-defined or the step type is 1 (queued), or, for system-defined steps, where the next operation sequence is null — the terminal operation.

Key Columns

• ORGANIZATION_ID — inventory organization owning the schedule and operations.
• WIP_ENTITY_ID — the work order or repetitive schedule identifier.
• LINE_ID — the repetitive production line from WIP_REPETITIVE_SCHEDULES.
• OPERATION_SEQ_NUM — the operation being reported.
• NEXT_OPERATION_SEQ_NUM — the following operation, used to identify the final operation when null.
• INTRAOPERATION_STEP_TYPE — numeric step code from the WIP_INTRAOPERATION_STEP lookup.
• INTRAOPERATION_STEP_MEANING — the translated meaning resolved via MFG_LOOKUPS.
• INTRAOPERATION_STEP_QUANTITY — the aggregated quantity for that step, derived with a DECODE that maps step types 1–5 to queue, running, waiting-to-move, rejected, and scrapped quantities.

Common Use Cases and Queries

The view supports WIP status inquiries, line-loading and work-in-process reporting, and integration extracts. A typical query retrieving step quantities for a schedule follows:

SELECT organization_id,
       wip_entity_id,
       line_id,
       operation_seq_num,
       intraoperation_step_meaning,
       intraoperation_step_quantity
FROM   apps.wip_rep_intraop_steps_val_v
WHERE  wip_entity_id = :p_wip_entity_id
ORDER  BY operation_seq_num, intraoperation_step_type;

To summarize quantities by step across a production line, aggregate on the meaning column:

SELECT intraoperation_step_meaning,
       SUM(intraoperation_step_quantity) total_quantity
FROM   apps.wip_rep_intraop_steps_val_v
WHERE  organization_id = :p_org_id
AND    line_id = :p_line_id
GROUP  BY intraoperation_step_meaning;

Because the view already resolves INTRAOPERATION_STEP_MEANING from MFG_LOOKUPS, it eliminates the need to join the lookup table directly when displaying intraoperation step labels.