Results for “po_headers_draft_all”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_HEADERS_DRAFT_ALL (owner PO) is the Oracle Purchasing table that stores draft document headers for purchase orders, purchase agreements, quotations, and RFQs. It exists because Oracle E-Business Suite separates the working copy of a procurement document from its approved version. When a buyer initiates or modifies a purchasing document, the change is staged as a draft header row in this table; only upon approval does the draft flow into the corresponding header in PO_HEADERS_ALL. This staging model enables features such as Change Orders, the document approval workflow via Oracle Approvals Management (AME), and controlled revision history.

The table is date-effective throughout: it carries a DRAFT_ID discriminator rather than updating rows in place, so multiple draft versions can coexist for the same document. Under a heuristic Data Vault classification of the documented foreign-key structure, PO_HEADERS_DRAFT_ALL is best described as a link-type modeling candidate: it sits at the intersection of a source document (FROM_HEADER_ID → PO_HEADERS_ALL), a draft envelope (DRAFT_ID → PO_DRAFTS), a supplier, a location, and an agent, capturing the relationships that define a single draft revision.

Key Information Stored

The table contains 202 columns, of which the following are most significant for development and reporting:

Common Use Cases and Queries

Typical usage centers on draft inspection, change order validation, and reporting on documents waiting for approval.

A change order belongs to the same document and draft combination; joining to PO_DRAFTS and PO_HEADERS_ALL confirms the base document and its status.

The most common reporting patterns include:

  • Listing all drafts awaiting approval for a given operating unit.
  • Identifying change orders on a controlled document by matching FROM_HEADER_ID back to PO_HEADERS_ALL.PO_HEADER_ID.
  • Auditing revised blanket amounts by comparing BLANKET_TOTAL_AMOUNT between the draft and the released header.
  • Extracting flexfield attribute values for supplier classification or cost-center analysis.

A representative query joins PO_HEADERS_DRAFT_ALL to PO_DRAFTS and PO_HEADERS_ALL on PO_HEADER_ID to surface pending change orders, filtering on CHANGE_STATUS and ORG_ID. Standard DBA practice when troubleshooting approval errors is to confirm that a row exists here for the DRAFT_ID referenced in the workflow tables.

Related Objects

  • PO_DRAFTS – parent of the draft envelope; joined via PO_HEADERS_DRAFT_ALL.DRAFT_ID.
  • PO_HEADERS_ALL – the released document header; joined via FROM_HEADER_ID and matching PO_HEADER_ID.
  • PO_AGENTS – buyer definition; joined via AGENT_ID.
  • HR_LOCATIONS_ALL – ship-to and bill-to addresses; joined via SHIP_TO_LOCATION_ID and BILL_TO_LOCATION_ID.
  • FND_CURRENCIES – currency descriptions; joined via CURRENCY_CODE.
  • GL_DAILY_CONVERSION_TYPES – conversion type names; joined via RATE_TYPE.
  • PON_UMBRELLA_PROGRAMS – program definitions; joined via UMBRELLA_PROGRAM_ID.
  • PO_LINES_DRAFT_ALL and the draft distributions tables – line and distribution details that accompany each draft header.
  • AME_APPROVAL tables (via AME_APPROVAL_ID) – approval instance linkage for the document lifecycle.