Search Results wip_valid_intraop_steps_u1

Overview

WIP.WIP_VALID_INTRAOPERATION_STEPS is a Work in Process (WIP) reference table that stores the set of enabled intraoperation steps for each organization. In Oracle EBS manufacturing, an operation in a discrete job, repetitive schedule, or flow schedule moves through intraoperation steps such as Queue, Run, To Move, Reject, and Scrap. This table records which of those steps are enabled for a given organization, and Oracle Work in Process consults it to determine whether an assembly may legally be moved into or out of a particular intraoperation step. Because the Queue step is automatically enabled for every operation, at least one row always exists per organization.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. It holds descriptive, organization-scoped reference data keyed by a business composite rather than acting as a transaction hub or a relationship link. Under this suggestion, ORGANIZATION_ID, RECORD_CREATOR, and STEP_LOOKUP_TYPE form the natural composite business key, with the descriptive attributes behaving as satellite payload.

Key Information Stored

The table is defined in the WIP schema, resides in the APPS_TS_TX_DATA tablespace (PCT Free 10), and comprises 25 documented columns. The most important columns are:

• ORGANIZATION_ID — Numeric identifier of the inventory organization. This is a foreign key to WIP_PARAMETERS and scopes all other data in the row.
• RECORD_CREATOR — Distinguishes who enabled the step. The value SYSTEM identifies the automatically enabled Queue step; the value USER identifies steps enabled by an administrator.
• STEP_LOOKUP_TYPE — Numeric code identifying the intraoperation step type (Queue, Run, To Move, Reject, Scrap).
• STEP_MEANING — VARCHAR2(10) description of the intraoperation step, providing the human-readable label.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS Who columns recording audit and user context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive Flexfield (DFF) columns reserved for organization-specific extensions. ATTRIBUTE_CATEGORY defines the DFF structure; ATTRIBUTE1–15 hold segment values.

The documented primary key is WIP_VALID_INTRAOPERATION_ST_PK, defined on (ORGANIZATION_ID, RECORD_CREATOR, STEP_LOOKUP_TYPE). A parallel unique index, WIP_VALID_INTRAOP_STEPS_U1, is defined on the identical column set in the APPS_TS_TX_IDX tablespace and serves as the principal business-key candidate. There is no single-column surrogate key; the composite is itself the identifying key, which is characteristic of organization-scoped reference tables.

Common Use Cases and Queries

Typical scenarios include validating which intraoperation steps are permitted before a move transaction, reporting configuration differences between organizations, and auditing who enabled non-Queue steps. The following patterns are representative:

• List all enabled steps for an organization: SELECT STEP_LOOKUP_TYPE, STEP_MEANING, RECORD_CREATOR FROM WIP.WIP_VALID_INTRAOPERATION_STEPS WHERE ORGANIZATION_ID = :org_id;
• Identify user-enabled (non-Queue) steps: SELECT * FROM WIP.WIP_VALID_INTRAOPERATION_STEPS WHERE RECORD_CREATOR = 'USER' AND ORGANIZATION_ID = :org_id;
• Compare configuration across organizations by grouping on ORGANIZATION_ID and counting STEP_LOOKUP_TYPE values.
• Join to WIP_PARAMETERS on ORGANIZATION_ID to report the owning organization alongside its enabled steps.

Reporting use cases center on readiness checks before go-live, post-clone configuration verification, and diagnosing move-transaction errors caused by a step not being enabled.

Related Objects

• WIP.WIP_PARAMETERS — Referenced by the ORGANIZATION_ID foreign key; supplies organization-level WIP parameters.
• WIP.WIP_DISCRETE_JOBS — Discrete jobs whose operations move through the enabled intraoperation steps.
• WIP.WIP_OPERATIONS — Operation records that use these steps to control material movement.
• WIP.WIP_REPETITIVE_SCHEDULES — Repetitive manufacturing schedules governed by the same step configuration.
• WIP.WIP_FLOW_SCHEDULES — Flow manufacturing schedules that reference intraoperation step settings.
• WIP.MTL_PARAMETERS / WIP_PARAMETERS — Organization definition tables sharing the ORGANIZATION_ID key.
• WIP Intraoperation Move APIs (e.g., WIP_MOVE_TXN / move transaction interfaces) — Programmatic consumers that validate against this table.

Because the table is small and organization-scoped, it is frequently queried during transaction validation and configuration audits.