Search Results po_headers_merge_v




Overview
Explore in AI Chat

Overview

PO_HEADERS_MERGE_V is an Oracle E-Business Suite view owned by the APPS schema within the Purchasing (PO) product module. Its purpose is to reconcile the draft editing model introduced by Oracle Procurement's document authoring framework against the authoritative purchasing document headers stored in the base tables. In EBS 12.1.1 and 12.2.2, purchasing documents such as purchase orders, blanket agreements, and contracts are staged as drafts in PO_DRAFTS and PO_HEADERS_DRAFT_ALL before they are accepted and materialized into PO_HEADERS_ALL. This view exposes a merged, read-friendly projection of draft-level control attributes alongside the corresponding header attribute set, allowing callers to inspect draft status and ownership together with the header fields that will ultimately apply once the draft is accepted.

The view therefore plays a supporting role in draft-aware reporting and integration. Rather than joining the draft and header tables manually, consumers can select from a single object that already aligns the draft surrogate keys (DRAFT_ID, OWNER_USER_ID, OWNER_ROLE, STATUS) with the wider set of header columns, including the descriptive flexfield (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) and the WHO/audit and concurrent program columns.

Underlying Base Objects

The documented ETRM 12.2.2 metadata records the referenced base objects as PO_DRAFTS (synonym), PO_HEADERS_ALL (synonym), and PO_HEADERS_DRAFT_ALL (synonym). PO_DRAFTS is the master draft record, defining ownership, role of the author, and the overall draft status. PO_HEADERS_DRAFT_ALL holds the transient or in-progress header values belonging to a draft, carrying the draft-scoped columns such as the change flags, notification preferences, sourcing and retro-price update indicators, and approval or cancellation flags. PO_HEADERS_ALL is the base purchasing document header table against which accepted drafts are written and which supplies the majority of the persistent header columns projected by the view, including key identifiers such as VENDOR_ID, VENDOR_SITE_ID, ORG_ID, CURRENCY_CODE, term and freight attributes, and the amounts and limits used for authorisation.

The view text references the draft alias DFT for the draft control columns and PHDA for the draft header attributes, indicating that the draft layer supplies the mergeable values while remaining ultimately reconcilable with PO_HEADERS_ALL. Because the referenced objects are synonyms, the view remains portable across the standard APPS installation in both 12.1.1 and 12.2.2.

Key Columns

Common Use Cases and Queries

Typical usage centres on reconciling draft documents with their header state, for example listing open drafts by owner and role:

  • SELECT draft_id, owner_user_id, owner_role, status FROM po_headers_merge_v WHERE status = 'DRAFT';
  • SELECT draft_id, vendor_id, org_id, authorization_status FROM po_headers_merge_v WHERE vendor_id = :p_vendor_id;
  • SELECT draft_id, amount_limit, approved_flag, approved_date FROM po_headers_merge_v WHERE org_id = :p_org_id AND authorization_status = 'APPROVED';

Because the view consolidates draft and header attributes, it is well suited to operational dashboards that must display in-progress documents without querying the draft and base tables separately. Queries should always be filtered by ORG_ID to respect multi-org security, and callers should treat columns originating from the draft layer as transient until the draft is accepted.