Results for “oke_approval_steps”

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

Overview

OKE_APPROVAL_STEPS is a table in the OKE (Project Contracts) schema that stores the individual steps comprising a contract document approval hierarchy in Oracle EBS 12.1.1 and 12.2.2. Each row represents one approver position within an ordered approval path, defining the sequence in which a contract must be routed and the role responsible for approving at that step. The table functions as the operational detail layer beneath OKE_APPROVAL_PATHS, which holds the header-level definition of the approval hierarchy.

Based on the foreign key structure mined from the ETRM metadata, this object carries a satellite-leaning Data Vault classification. Its role is to hold descriptive attributes and sequence-dependent detail about approval steps rather than to serve as a pure hub or link. This classification is a heuristic modeling suggestion derived from the FK topology, not an enforced property of the EBS data model.

Key Information Stored

The most significant columns in OKE_APPROVAL_STEPS are:

• APPROVAL_PATH_ID — Foreign key to OKE_APPROVAL_PATHS, identifying the approval hierarchy to which the step belongs. This column participates in both the primary key and the unique business key.
• APPROVAL_SEQUENCE — Numeric position of the step within the approval path, determining the order in which approvals must be obtained. Combined with APPROVAL_PATH_ID, it forms the OKE_APPROVAL_STEPS_PK surrogate primary key.
• APPROVER_ROLE_ID — Reference to the role authorized to approve the contract at this step. Together with APPROVAL_PATH_ID, it forms the unique key OKE_APPROVAL_STEPS_UK, preventing a role from appearing twice on the same path.
• REQUIRED_FLAG — Indicator of whether the step is mandatory for the approval path to complete.
• RECORD_VERSION_NUMBER — Optimistic locking counter used to detect concurrent updates to the step definition.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in EBS 12.2; it also appears in the unique index OKE_APPROVAL_STEPS_U1 (APPROVAL_PATH_ID, APPROVAL_SEQUENCE, ZD_EDITION_NAME).
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture who created and last modified each step.

The surrogate primary key is OKE_APPROVAL_STEPS_PK (APPROVAL_PATH_ID, APPROVAL_SEQUENCE). The business-key candidates are the unique index OKE_APPROVAL_STEPS_UK (APPROVAL_PATH_ID, APPROVER_ROLE_ID) and the edition-aware unique index OKE_APPROVAL_STEPS_U1.

Common Use Cases and Queries

Typical applications include reconstructing the full approval roadmap for a contract, auditing which role approved at which step, identifying unused roles on a path, and driving workflow notifications in sequence.

To list every step for a given path in order:

• SELECT approval_sequence, approver_role_id, required_flag FROM oke_approval_steps WHERE approval_path_id = :path_id ORDER BY approval_sequence;

To find all paths that include a specific approver role:

• SELECT s.approval_path_id, p.name FROM oke_approval_steps s, oke_approval_paths p WHERE s.approval_path_id = p.approval_path_id AND s.approver_role_id = :role_id;

Reporting use cases include generating approval matrices per contract type, validating that each path contains at least one required step, and reconciling approver roles against FND_ROLES for security reviews.

Related Objects

• OKE_APPROVAL_PATHS — Parent table joined on APPROVAL_PATH_ID; defines the approval hierarchy header.
• OKE_CONTRACTS — Contract header referencing an approval path for document routing.
• OKE_CONTRACT_APPROVALS — Runtime approval records reflecting actions taken against each step.
• FND_ROLES — Source of APPROVER_ROLE_ID role definitions.
• OKE_APPROVAL_STEPS_PK / UK / U1 — Primary and unique indexes enforcing step integrity and editioning.
• OKE_CONTRACT_APPROVAL_API — Programmatic interface for managing approval paths and steps.