Search Results wip_valid_intraoperation_steps




Overview
Explore in AI Chat

Overview

WIP_VALID_INTRAOPERATION_STEPS is a Work in Process (WIP) configuration table owned by the WIP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the set of intraoperation steps that are valid within a given organization for a specific usage context. In Oracle EBS manufacturing, an intraoperation step represents the state a job or schedule operation moves through while it is being executed, such as Queue, Run, To Move, and Scrap. Because intraoperation steps are resolved through a lookup mechanism, this table acts as the organization-specific control list that governs which steps are offered and processed for each operation type.

The table is keyed by the combination of ORGANIZATION_ID, RECORD_CREATOR, and STEP_LOOKUP_TYPE, exposed through the primary key constraint WIP_VALID_INTRAOPERATION_ST_PK and mirrored by the unique index WIP_VALID_INTRAOP_STEPS_U1. The presence of the RECORD_CREATOR column is notable: rather than representing an audit user, it participates in the business key, indicating that distinct sets of valid steps are maintained per creator context. Under the heuristic Data Vault classification derived from foreign-key structure, this table leans toward a satellite role, since it references WIP_PARAMETERS and serves as a descriptive, keyed extension of organization-level WIP parameters rather than an independent transactional hub.

Key Information Stored

The table consists of 25 documented columns. The most important are identified below.

  • ORGANIZATION_ID — Identifies the inventory organization whose valid intraoperation steps are defined. This column also forms the foreign key to WIP_PARAMETERS, tying the configuration to that organization's WIP setup.
  • RECORD_CREATOR — Part of the composite business key. It distinguishes the definition set by creator context, allowing multiple valid-step configurations to coexist.
  • STEP_LOOKUP_TYPE — The lookup type that classifies the intraoperation step, forming the third component of the business key.
  • STEP_MEANING — The descriptive meaning associated with the step, used for user-facing display and reporting.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row and when.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard descriptive flexfield (DFF) segment columns, providing extensible, customer-defined attributes attached to each valid step definition.

The surrogate primary key is WIP_VALID_INTRAOPERATION_ST_PK, while the business-key candidate is WIP_VALID_INTRAOP_STEPS_U1 over (ORGANIZATION_ID, RECORD_CREATOR, STEP_LOOKUP_TYPE). The two are functionally aligned here because the composite business key itself is used as the primary key.

Common Use Cases and Queries

The primary use case is validating and interpreting intraoperation steps during job and schedule processing. Applications and reports query this table to determine which steps a user may enter or which steps are recognized for an organization. Typical operation-level validation queries join the step definitions to transactional WIP tables by ORGANIZATION_ID and step reference.

  • Confirming valid intraoperation steps for a given organization: SELECT STEP_LOOKUP_TYPE, STEP_MEANING FROM WIP.WIP_VALID_INTRAOPERATION_STEPS WHERE ORGANIZATION_ID = :org_id;
  • Retrieving the configuration for a specific creator context: filter on all three key columns — ORGANIZATION_ID, RECORD_CREATOR, and STEP_LOOKUP_TYPE.
  • Reporting on step usage and configuration completeness for an organization, driving discrepancy analysis or setup auditing.
  • Extracting descriptive flexfield attributes for downstream reporting or interfaces via ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15.

Related Objects

The most significant relationships are defined by the documented foreign-key structure and the shared business key.

  • WIP_PARAMETERS — Referenced through WIP_VALID_INTRAOPERATION_STEPS.ORGANIZATION_ID, providing organization-level WIP parameters and enforcing that valid step sets belong to a defined WIP organization.
  • WIP_DISCRETE_JOBS — Discrete job headers whose operations reference the valid step definitions for their organization.
  • WIP_OPERATIONS — Operation-level records that carry intraoperation step identifiers validated against this table.
  • WIP_MOVE_TRANSACTIONS — Move transactions that post against intraoperation steps and rely on the validity of those steps.
  • WIP_TRANSACTIONS — Material and resource transactions associated with the defined steps.
  • FND_LOOKUP_VALUES / FND_LOOKUP_TYPES — Underlying lookup framework that supplies the values referenced by STEP_LOOKUP_TYPE.

Together these objects make WIP_VALID_INTRAOPERATION_STEPS the organization-scoped reference that keeps WIP operation-step processing consistent across discrete manufacturing transactions.