Results for “po_drafts”

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

Overview

PO_DRAFTS is the control table for draft changes in the Oracle Purchasing (PO) module. It records the header-level context for every draft revision created against a purchasing document, functioning as the anchor or parent record for the family of _DRAFT and _DRAFT_ALL tables that hold the proposed (unapproved) versions of purchase order headers, lines, line locations, distributions, and related attributes. In Oracle EBS 12.1.1 and 12.2.2, this table underpins the "draft" and change-order functionality that allows buyers to stage modifications to an existing document, route them through approval, and only then promote the changes to the base transactional tables.

The table resides in the PO schema and is a core element of the Purchasing document change-management model. Its primary key is PO_DRAFTS_PK, defined on the DRAFT_ID column, and this single-column key is also exposed through the unique index PO_DRAFTS_U1. Practically every draft-related child table joins back to PO_DRAFTS on DRAFT_ID, confirming the object's role as the governing record for a single change set.

From a heuristic Data Vault modeling perspective, PO_DRAFTS is best classified as a hub. It holds the unique business key (the draft identifier) around which satellites and link relationships for draft content are organized. This classification is a suggestion derived from the foreign-key topology, not an Oracle-imposed designation.

Key Information Stored

The table contains 32 documented columns. The most significant are summarized below.

• DRAFT_ID — surrogate primary key (PO_DRAFTS_PK) and the unique business-key candidate (PO_DRAFTS_U1) that links all draft child tables.
• DOCUMENT_ID — identifies the base purchasing document to which the draft applies.
• REVISION_NUM — the revision level associated with the draft.
• OWNER_USER_ID / OWNER_ROLE / AGENT_ID — ownership and buyer/agent context for the draft.
• STATUS — the workflow state of the draft (for example, in progress or approved).
• DRAFT_TYPE / DRAFT_SUB_TYPE — classify the nature of the change being staged.
• JUSTIFICATION / NOTE_TO_SUPPLIER — descriptive text captured with the change.
• MOD_EFFECTIVE_DATE / MODIFICATION_NUMBER — effective dating and sequence of the modification.
• CHANGED_AMT / CHANGED_AMT_EXCL_OPT — monetary impact of the change.
• CHANGEDESCRIPTION_DATA — structured description of the changed fields.
• CONCURRENT_REQID / REQUEST_ID — concurrent program context that created or processed the draft.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Additional columns such as CLM_NOOFCOPIES, CLM_STANDARD_FORM, CLM_DOCUMENT_FORMAT, CLM_CONTRACT_OFFICER, and the CD_GENERATED_* flags relate to contract/document generation and printing behavior.

Common Use Cases and Queries

Typical usage centers on identifying open drafts, reporting change history, and reconciling drafts against their base documents. A buyer-facing query to list active drafts and their status resembles:

• SELECT h.segment1, d.draft_id, d.draft_type, d.status, d.modification_number FROM po_drafts d JOIN po_headers_all h ON h.po_header_id = d.document_id WHERE d.status = 'IN PROGRESS';
• Change-impact reporting joining PO_DRAFTS to PO_HEADERS_DRAFT_ALL to compare drafted values against PO_HEADERS_ALL.
• Audit queries using CREATED_BY, CREATION_DATE, and CONCURRENT_REQID to trace which concurrent program produced a draft.
• Monitoring drafts that have never been promoted by checking DRAFT_ID in PO_DRAFTS with no matching base revision.

Because PO_DRAFTS is a hub, most reporting joins proceed child-to-parent on DRAFT_ID; direct queries are usually filtered by DOCUMENT_ID or STATUS.

Related Objects

PO_DRAFTS is referenced by numerous tables through the DRAFT_ID column. The most significant relationships include:

• PO_HEADERS_DRAFT_ALL.DRAFT_ID — drafted header values.
• PO_LINE_LOCATIONS_DRAFT_ALL.DRAFT_ID — drafted shipment/schedule values.
• PO_DISTRIBUTIONS_DRAFT_ALL.DRAFT_ID — drafted distribution values.
• PO_PRICE_DIFF_DRAFT.DRAFT_ID — price difference information for the draft.
• PO_GA_ORG_ASSIGN_DRAFT.DRAFT_ID — drafted accounting organization assignments.
• PO_NOTIFICATION_CTRL_DRAFT.DRAFT_ID — draft notification control records.
• PO_HEADERS_ALL.DRAFT_ID and PO_LINES_ALL.DRAFT_ID — base tables that carry the DRAFT_ID once changes are applied.
• PO_HEADERS_ARCHIVE_ALL.DRAFT_ID — archived headers retaining draft lineage.

These relationships confirm that PO_DRAFTS is the central reference point for all draft change data in Purchasing, with the base PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL tables linked through the same DRAFT_ID key after promotion.