Results for “step_no”

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

Overview

IGI_EXP_WKF_STEP_ALL is an Oracle E-Business Suite table owned by the IGI schema (Public Sector Financials International). It stores individual workflow step setup information created through the workflow profile creation form. In practice, each row defines one step within a procurement or expenditure workflow profile, tying a workflow header, a flow definition, a step sequence number, and the organizational position structure responsible for executing that step. This makes the table the operational backbone of approval routing in IGI-sponsored workflow configurations.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. This suggests that, rather than serving as a hub or link, the table behaves as a self-contained setup/reference entity whose grain is the individual workflow step. It is not decomposed into separate hub/link/satellite structures in the source system.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 10 columns. The most significant are:

• WKF_ID — identifier of the workflow profile (header) to which the step belongs. Part of the primary key.
• FLOW_ID — identifier of the specific flow within the workflow. Part of the primary key.
• STEP_NO — ordinal sequence of the step within the flow, defining execution order. Part of the primary key.
• POSITION_STRUCTURE_ID — foreign key to PER_POSITION_STRUCTURES, identifying the organizational position structure designated as the approver/responsible party for the step. Part of the primary key.
• ORG_ID — operating unit / organization identifier, enabling multi-org security and filtering.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle WHO columns for audit and concurrency tracking.

The unique index IGI_EXP_WKF_STEP_PK on (WKF_ID, FLOW_ID, STEP_NO, POSITION_STRUCTURE_ID) is the business-key candidate; there is no separate single-column surrogate key documented, so the composite represents both the uniqueness constraint and the natural key.

Common Use Cases and Queries

Typical scenarios include reconstructing a workflow's approval chain, validating that each step maps to a valid position structure, and reporting on which organizational units participate in a given flow.

• List all steps in a workflow order: SELECT STEP_NO, POSITION_STRUCTURE_ID FROM IGI_EXP_WKF_STEP_ALL WHERE WKF_ID = :wkf_id AND FLOW_ID = :flow_id ORDER BY STEP_NO;
• Join to position structures to resolve approver names: join on POSITION_STRUCTURE_ID = PER_POSITION_STRUCTURES.POSITION_STRUCTURE_ID.
• Multi-org reporting filtered by ORG_ID.
• Audit queries using CREATION_DATE / LAST_UPDATE_DATE to detect recently reconfigured workflows.
• Identify duplicate or orphaned steps where POSITION_STRUCTURE_ID no longer resolves.

Related Objects

• PER_POSITION_STRUCTURES — referenced via POSITION_STRUCTURE_ID; the sole documented foreign key relationship.
• IGI_EXP_WKF_ALL (workflow header) — parent of WKF_ID.
• IGI_EXP_WKF_FLOW_ALL (flow definition) — parent of FLOW_ID.
• PER_ALL_PEOPLE_F / PER_ALL_ASSIGNMENTS_F — used downstream to resolve positions to employees.
• FND_LOOKUPS — commonly joined for step type or status decode values.

Because the table is standalone and setup-oriented, its principal dependency is the position structure hierarchy rather than other transactional IGI tables.