Search Results oebv_order_approvals




Overview
Explore in AI Chat

Overview

OEBV_ORDER_APPROVALS is a read-only view in the Oracle E-Business Suite Order Entry (OE) module that exposes order approval transaction data. Its name follows the EBS convention for Order Entry business views ("OEBV"), and it is documented in the ETRM repository as a retrofitted object, meaning it was introduced or reconciled to align with a prior release rather than newly authored. The view presents one row per order approval action, joining approval records to the underlying sales order header, order type, action, and result identifiers. In the 12.1.1 and 12.2.2 code lines, it functions primarily as a reporting and integration surface: external reports, custom concurrent programs, and interfaces query it to retrieve the approval trail for sales orders without embedding direct references to the base table. Because the view is defined with WITH READ ONLY, it cannot be used for DML; any write operations against approval data must target the base objects instead.

The ETRM metadata for this object notes that it is "Not implemented in this database" in the source environment and "Retrofitted" in description. This indicates the view definition exists in the repository for reference but may not be deployed in every instance. Developers should verify presence via ALL_VIEWS or DBA_VIEWS before relying on it in production code.

Underlying Base Objects

The documented base object is a single table: SO_ORDER_APPROVALS. The view text is a straightforward projection:

No joins, unions, or aggregations are present, and the ETRM metadata records no additional referenced base objects. All filtering, joining to OE_ORDER_HEADERS_ALL, OE_ORDER_TYPES, or workflow tables must therefore be performed by the consuming query. The literal '_DF:OE:SO_ORDER_APPROVALS:SO_ORDER_APPROVALS' is a descriptive Flexfield (DF) context marker identifying the source entity for the DFF-enabled columns, exposed in the view under the alias "_DF".

Key Columns

  • ORDER_APPROVAL_ID — Primary key of the approval record; unique per approval action.
  • APPROVAL_DATE — The date on which the approval action occurred. Note that the column list documents the name as APPROVAL_DATE, while the view text selects the base column DATE_APPROVED. The user's search term "date_approved" maps directly to this column, which is often aliased or referenced by either name depending on the release and the query tooling.
  • APPROVAL_COMMENT — Free-text comment entered by the approver.
  • APPROVER_ID — Identifier of the user or resource who performed the approval action.
  • HEADER_ID — Foreign key to the order header (OE_ORDER_HEADERS_ALL.HEADER_ID), linking the approval to its sales order.
  • ORDER_TYPE_ID — Identifier of the order type associated with the approval.
  • ACTION_ID and RESULT_ID — References to the workflow or approval action and its outcome.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns.
  • "_DF" — Descriptor Flexfield context literal, not a queryable value.

Common Use Cases and Queries

The canonical use case is auditing the approval history of sales orders, including the date on which each approval was granted. A typical query lists approvals for a given order:

  • SELECT oa.order_approval_id, oa.header_id, oa.approver_id, oa.approval_date, oa.approval_comment FROM oebv_order_approvals oa WHERE oa.header_id = :p_header_id ORDER BY oa.approval_date DESC;

Reporting on approval turnaround joins to the order header:

  • SELECT h.order_number, oa.approver_id, oa.approval_date, oa.result_id FROM oebv_order_approvals oa, oe_order_headers_all h WHERE oa.header_id = h.header_id AND oa.approval_date BETWEEN :p_from AND :p_to;

When the view is not deployed, equivalent results can be produced by selecting DATE_APPROVED directly from SO_ORDER_APPROVALS. Because the view is read-only, all such reports should remain SELECT-only.