Search Results po_approval_list_headers




Overview

PO_APPROVAL_LIST_HEADERS is a core Purchasing table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the PO schema. It stores the header-level records of the purchasing document approval list, acting as the master record for the routing and approval state of a document as it progresses through the Oracle Workflow-driven approval process. Each row represents a single approval list instance tied to a specific purchasing document, its document type and subtype, and its revision.

In terms of Data Vault modeling, the mined foreign key structure classifies this object heuristically as standalone, meaning it does not behave as a classic hub, link, or satellite. This classification is a modeling suggestion only: the table holds both descriptive state (sequence numbers, revision flags, workflow keys) and a foreign key to a business entity (approval path), so it functions as a self-contained transactional header rather than a pure hub.

Key Information Stored

The table contains 32 documented columns. The most operationally significant columns are the following:

The distinction between the surrogate key and business keys is important: APPROVAL_LIST_HEADER_ID is both the primary key and the only documented unique business-key candidate, while the foreign-key column APPROVAL_PATH_ID is descriptive of the routing source rather than a business key of this table.

Common Use Cases and Queries

Typical uses include identifying which approval list is active for a given document, determining who is the current approver, and auditing the approval history for a PO. A common query pattern joins the header to its lines to retrieve the ordered routing:

  • Active approval for a document: SELECT h.approval_list_header_id, h.current_sequence_num, h.first_approver_id FROM po_approval_list_headers h WHERE h.document_id = :p_document_id AND h.latest_revision = 'Y';
  • Approval path used: join h.approval_path_id to oke_approval_paths to report the routing template.
  • Workflow tracing: use wf_item_type and wf_item_key to correlate the approval list with the workflow runtime item.
  • Line detail: join to po_approval_list_lines on approval_list_header_id to expand each approver step.

These queries support purchase order status dashboards, approval cycle-time reporting, and reconciliation of stuck or re-routed documents.

Related Objects

The most significant related objects, based on the documented FK structure, are:

  • PO_APPROVAL_LIST_LINES — child table; joins on APPROVAL_LIST_HEADER_ID and holds the individual approver steps.
  • OKE_APPROVAL_PATHS — parent table supplying the approval path definition via APPROVAL_PATH_ID.

Beyond these explicit relationships, the DOCUMENT_ID and DOCUMENT_TYPE columns logically link to the purchasing document tables (such as PO_HEADERS_ALL and related PO document entities), and the WF_ITEM_TYPE / WF_ITEM_KEY columns link to the Oracle Workflow runtime tables. Together these objects complete the approval-list data model within the PO module.