Search Results oe_approver_transactions




Overview
Explore in AI Chat

Overview

OE_APPROVER_TRANSACTIONS is an Oracle Order Management (ONT) transactional table that stores runtime, transaction-level approval information and the associated approval statuses. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 architecture, it functions as the persistent store for the approval workflow state generated when orders or order-related transactions are submitted for approval against the Order Management approval hierarchy and approval rules configured by the implementing organization. The table is owned by the ONT schema and is marked VALID across both releases.

Under the heuristic Data Vault classification mined from its foreign key structure, OE_APPROVER_TRANSACTIONS is satellite-leaning. This suggests a modeling approach in which the transaction identifier acts as a parent or hub-style key, while the approval-specific attributes (role, sequence, phase, and status) are descriptive satellite attributes that accumulate and change over the lifetime of the approval process. Modelers should treat the table as a state-and-status store rather than as a source of independent master data.

Key Information Stored

The table is documented with 11 columns. The most significant ones are:

  • TRANSACTION_ID — The surrogate identifier linking each approval record to the underlying order or transactional entity being approved. It is the principal join and correlation key.
  • TRANSACTION_TYPE_ID — Classifies the transaction being approved, distinguishing order types or approval transaction categories at runtime.
  • TRANSACTION_PHASE_CODE — Indicates the phase of the approval lifecycle in which the record applies (for example, submission, review, or completion phases).
  • ROLE — Identifies the approver role or user acting on the transaction. This column participates in the documented foreign key to FND_USER.
  • APPROVER_SEQUENCE — Establishes the ordering of approvers in a multi-step approval chain.
  • APPROVAL_STATUS — Captures the current disposition of the approval, such as pending, approved, or rejected.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard EBS audit columns recording who created and last modified each approval record and when.

No unique index is documented in the supplied metadata. Based on FK relationships, TRANSACTION_ID together with APPROVER_SEQUENCE, TRANSACTION_TYPE_ID, and ROLE are the practical business-key candidates for identifying a distinct approval step.

Common Use Cases and Queries

Typical scenarios include auditing which approver is pending on an order, reporting on approval cycle times, and diagnosing stalled approvals. A representative query joining the approver role to FND_USER is:

  • SELECT t.transaction_id, t.approver_sequence, t.approval_status, u.user_name FROM ont.oe_approver_transactions t, fnd_user u WHERE t.role = u.user_id AND t.approval_status = 'PENDING' ORDER BY t.transaction_id, t.approver_sequence;
  • Filter by TRANSACTION_PHASE_CODE to isolate approvals at a particular lifecycle phase.
  • Aggregate by APPROVAL_STATUS to produce approval workload and bottleneck reports.

Because the table records runtime state, it is also useful for reconciliation between submitted orders and completed approval chains.

Related Objects

The primary documented relationship is the foreign key from OE_APPROVER_TRANSACTIONS.ROLE to FND_USER, joining approval records to the application user or role definition. Beyond that documented link, the table is closely associated with the core ONT order tables (such as OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL) via TRANSACTION_ID, with the approval management and workflow tables that drive order approvals, and with ONT order approval APIs and concurrent programs that populate and update approval status. Reporting views in the Order Management module typically join this table to order and user data to present approval status to business users.