Search Results po_headers_draft_all




Overview
Explore in AI Chat

Overview

The PO_HEADERS_DRAFT_ALL table is a core transactional table within the Oracle E-Business Suite Purchasing (PO) module. It serves as the primary repository for draft header information for all purchasing documents, including purchase orders, purchase agreements, quotations, and requests for quotation (RFQs). Its role is to temporarily store document header data during the creation or amendment process before the document is finalized and submitted for approval. This draft mechanism allows users to save incomplete work and facilitates collaborative document preparation. The table is multi-org enabled, as indicated by the '_ALL' suffix, meaning it stores data for all operating units, with access controlled by the MOAC (Multi-Org Access Control) security model.

Key Information Stored

The table stores a comprehensive set of attributes that define a purchasing document's header-level details in a draft state. The primary key is a composite of PO_HEADER_ID and DRAFT_ID, ensuring uniqueness for each draft version of a document header. Key columns include SEGMENT1, which holds the unique draft document number, and DRAFT_ID, which links to the PO_DRAFTS table to manage the overall draft session. Other critical columns capture essential header data such as AGENT_ID (the buyer), SHIP_TO_LOCATION_ID and BILL_TO_LOCATION_ID, CURRENCY_CODE, and RATE_TYPE for currency conversion. The FROM_HEADER_ID column is significant for amendments, as it references the original finalized document (PO_HEADERS_ALL.PO_HEADER_ID) from which the draft was created.

Common Use Cases and Queries

A primary use case is tracking and managing incomplete purchasing documents. Administrators may run queries to identify old draft documents that were never submitted for cleanup. Another common scenario involves troubleshooting amendment processes by tracing the lineage from a finalized document to its draft version. Sample SQL patterns include joining to PO_DRAFTS to see draft metadata (like creation date and user) and joining to PO_HEADERS_ALL to compare draft values against the original document.

  • Finding all draft purchase order headers for a specific buyer: SELECT * FROM PO_HEADERS_DRAFT_ALL phda WHERE phda.AGENT_ID = 1234;
  • Listing draft documents created from a specific finalized PO for amendment analysis: SELECT phda.* FROM PO_HEADERS_DRAFT_ALL phda WHERE phda.FROM_HEADER_ID = 1000;
  • Reporting on all draft documents with their status from PO_DRAFTS: SELECT pd.DRAFT_STATUS, phda.SEGMENT1, phda.TYPE_LOOKUP_CODE FROM PO_HEADERS_DRAFT_ALL phda, PO_DRAFTS pd WHERE phda.DRAFT_ID = pd.DRAFT_ID;

Related Objects

PO_HEADERS_DRAFT_ALL has integral relationships with several key EBS tables, primarily through foreign key constraints. The most direct relationship is with the PO_DRAFTS table via DRAFT_ID, which controls the draft session. For finalized documents, it relates to PO_HEADERS_ALL via FROM_HEADER_ID. It references master data tables for validation: HR_LOCATIONS_ALL for ship-to and bill-to locations, PO_AGENTS for the buyer, FND_CURRENCIES for currency, and GL_DAILY_CONVERSION_TYPES for exchange rate types. In a typical data model, this table would be the parent to PO_LINES_DRAFT_ALL and PO_DISTRIBUTIONS_DRAFT_ALL, which store the corresponding draft lines and distributions.

  • PO_DRAFTS (via DRAFT_ID): Manages the overarching draft session and status.
  • PO_HEADERS_ALL (via FROM_HEADER_ID): References the source finalized document header for amendments.
  • HR_LOCATIONS_ALL (via SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID): Validates delivery and invoicing addresses.
  • PO_AGENTS (via AGENT_ID): Validates the purchasing agent/buyer.
  • FND_CURRENCIES (via CURRENCY_CODE) and GL_DAILY_CONVERSION_TYPES (via RATE_TYPE): Validate currency and exchange rate information.