Results for “po_drafts_u1”

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

Overview

PO_DRAFTS is the controlling table for the Oracle Purchasing draft-change subsystem. In Oracle E-Business Suite 12.1.1 and 12.2.2, the "draft" architecture allows buyers and suppliers to stage modifications to a purchasing document without immediately committing them to the base transaction tables. Each draft record in PO_DRAFTS represents one pending change request — a proposed revision of a PO header, line, shipment, distribution, or related contract object — and holds the ownership, status, and descriptive context of that change. Drafts are used heavily in the Procurement Contracts authoring flow, in supplier-initiated change requests, and in catalog administration.

The table is owned by the PO schema and physically resides in the APPS_TS_TX_DATA tablespace. The ETRM metadata classifies PO_DRAFTS heuristically as a hub within a Data Vault model: it holds the stable business key (DRAFT_ID) and is referenced as a foreign key target by many dependent draft and archive tables. Practically, PO_DRAFTS functions as the parent/header for the entire draft change set, while the "_DRAFT_ALL" tables store the proposed attribute values that will be merged into the base PO entities upon approval or publication.

Key Information Stored

The table's surrogate primary key is DRAFT_ID (PO_DRAFTS_PK). The unique index PO_DRAFTS_U1 enforces uniqueness on DRAFT_ID as well; the user's search for "po_drafts_u1" therefore resolves to this single-column unique index on the identifying key. There is no separate natural/business key beyond DRAFT_ID — each draft is an internally generated numeric identifier.

Columns of greatest functional importance:

• DRAFT_ID — Surrogate primary key; the draft unique identifier referenced by all child draft tables.
• DOCUMENT_ID — The underlying document being changed. For PO drafts this equals the PO_HEADER_ID, linking the draft back to its source document.
• REVISION_NUM — The revision of the document for which the draft was created.
• OWNER_USER_ID — The user who owns the draft.
• OWNER_ROLE — The owning party's role; valid values include BUYER, SUPPLIER, and CAT ADMIN.
• STATUS — The current lifecycle state of the draft request (for example, draft, submitted, approved, rejected, published).
• DRAFT_TYPE / DRAFT_SUB_TYPE — Classifiers distinguishing the nature of the change (e.g., contract authoring vs. standard PO change).
• JUSTIFICATION — Free-text reason for creating the draft.
• NOTE_TO_SUPPLIER — Message communicated to the supplier regarding the change.
• MODIFICATION_NUMBER / MOD_EFFECTIVE_DATE — Change-order numbering and the effective date of the modification.
• CHANGED_AMT / CHANGED_AMT_EXCL_OPT — Monetary impact of the draft, useful for approval thresholds and reporting.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and REQUEST_ID track audit and concurrent program context.

Two non-unique indexes support access paths: PO_DRAFTS_N1 on (OWNER_ROLE, STATUS) and PO_DRAFTS_N2 on (DOCUMENT_ID).

Common Use Cases and Queries

A frequent operational need is to locate all open drafts for a given purchasing document or owner. Because PO_DRAFTS_N2 covers DOCUMENT_ID, the following is index-driven:

• SELECT draft_id, owner_role, status, revision_num, changed_amt FROM po.po_drafts WHERE document_id = :po_header_id;
• SELECT draft_id, document_id, justification FROM po.po_drafts WHERE status = :status AND owner_role = :role; — supported by PO_DRAFTS_N1.
• Joining to the base header: SELECT d.draft_id, h.segment1, d.status FROM po.po_drafts d, po.po_headers_all h WHERE d.document_id = h.po_header_id;
• Pending approvals / age analysis: filter on STATUS combined with CREATION_DATE to find drafts submitted but not yet approved.
• Change-impact reporting: aggregate CHANGED_AMT by OWNER_ROLE or by DOCUMENT_ID.

The DRAFT_ID key is also the pivot for collecting the proposed line, shipment, and distribution values from the parallel "_DRAFT_ALL" tables, enabling full side-by-side comparison of proposed versus current document state.

Related Objects

PO_DRAFTS is referenced by a broad family of dependent tables via the DRAFT_ID foreign key. The most significant for change-processing work are:

• PO_HEADERS_DRAFT_ALL.DRAFT_ID — Proposed header-level changes.
• PO_LINES_ALL.DRAFT_ID and PO_LINE_LOCATIONS_ALL.DRAFT_ID — Draft lines and shipments reconciled against base lines.
• PO_DISTRIBUTIONS_ALL.DRAFT_ID — Draft distribution (accounting) information.
• PO_HEADERS_ALL.DRAFT_ID — Association of the base document with its active draft.
• PO_ACCEPTANCES.DRAFT_ID — Acceptance records tied to a draft change.
• PO_PRICE_DIFF_DRAFT.DRAFT_ID and PO_MULTI_MOD_DOCS.DRAFT_ID — Price-difference and multi-modification processing.
• PO_NOTIFICATION_CTRL_DRAFT.DRAFT_ID — Notification control for draft workflows.
• Archive counterparts (e.g., PO_HEADERS_ARCHIVE_ALL, PO_LINES_ALL_EXT_B_ARCHIVE) retain draft references for historical reconstruction.

Together these relationships establish PO_DRAFTS as the central hub through which all draft change transactions in Oracle Purchasing are coordinated.