Search Results approval_sequence

Overview

The OKE_APPROVAL_STEPS table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It functions as the detailed repository for the sequential steps that constitute an approval hierarchy for contract documents. Each record in this table defines a specific step in an approval workflow, linking an approver role to a position within a defined approval path. The table's primary role is to enforce the business rules and routing logic for the approval of contracts, amendments, and other project contract documents, ensuring that documents are reviewed and authorized by the correct parties in the correct order as configured within the application.

Key Information Stored

The table's structure centers on defining the sequence and participants of an approval path. The primary key (OKE_APPROVAL_STEPS_PK) is a composite of APPROVAL_PATH_ID and APPROVAL_SEQUENCE, uniquely identifying each step's position within a path. A notable unique key (OKE_APPROVAL_STEPS_UK) combines APPROVAL_PATH_ID with APPROVER_ROLE_ID, preventing the same approver role from being assigned more than once within a single approval path. The most critical columns include:

• APPROVAL_PATH_ID: Foreign key to OKE_APPROVAL_PATHS, identifying the parent approval hierarchy.
• APPROVAL_SEQUENCE: An integer defining the ordinal position of this step within the path.
• APPROVER_ROLE_ID: The identifier for the role (e.g., Project Manager, Contract Administrator) responsible for approval at this step. This is the column directly referenced in the user's search.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting approval workflow configurations. For instance, to list all approval steps for a specific contract type or document, one would join this table with OKE_APPROVAL_PATHS. The search for "approver_role_id" suggests a user is likely investigating who is assigned as an approver. A common query pattern retrieves the full approval hierarchy:

SELECT oas.approval_sequence, oas.approver_role_id, per.role_name
FROM oke_approval_steps oas,
oke_approval_paths oap,
per_roles_dn_vl per
WHERE oas.approval_path_id = oap.approval_path_id
AND oas.approver_role_id = per.role_id
AND oap.document_type = 'CONTRACT'
ORDER BY oas.approval_sequence;

This table is also central to the runtime engine that determines the next approver when a document is submitted for approval.

Related Objects

OKE_APPROVAL_STEPS has a fundamental relationship with the OKE_APPROVAL_PATHS table via the APPROVAL_PATH_ID foreign key. OKE_APPROVAL_PATHS defines the header-level approval rule (e.g., by document type, amount), to which the steps belong. The APPROVER_ROLE_ID column typically references role definitions stored in the PER_ROLES_DN_VL view (or underlying PER_ROLES_DN table) within the Human Resources (HR) module. During the approval process, runtime data such as current approver and status for a specific document instance is tracked in transactional tables like OKE_DOC_APPROVAL_HISTORY, which references the configured steps.