Search Results po_attr_values_draft_u1

Overview

PO.PO_ATTRIBUTE_VALUES_DRAFT is a transactional draft table in the Oracle Purchasing (PO) schema. It is the pending-change shadow of PO_ATTRIBUTE_VALUES, holding edits submitted by suppliers or by catalog administrators when they modify a purchasing document directly through iProcurement or supplier-facing catalog maintenance flows. Rather than immediately overwriting the live attribute row, EBS stages the proposed values in this table so that the change can be reviewed, accepted, or rejected before it is merged back into PO_ATTRIBUTE_VALUES. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10.

Its documented physical schema in ETRM 12.2.2 contains 331 columns, of which the great majority are generated base and category attribute flexfield slots (TEXT_BASE_ATTRIBUTE1–100, NUM_BASE_ATTRIBUTE1–100, TEXT_CAT_ATTRIBUTE1–50, NUM_CAT_ATTRIBUTE1–50), plus the operational and audit columns. The primary key is the system-generated constraint SYS_C00204874 over (ATTRIBUTE_VALUES_ID, DRAFT_ID), and the heuristic Data Vault classification is a standalone structure — it functions most naturally as a satellite hanging off the DRAFT_ID change-request hub, since DRAFT_ID identifies the pending change set to which each staged attribute record belongs.

Key Information Stored

The most significant columns fall into four groups: identity, change control, business context, and descriptive content.

• ATTRIBUTE_VALUES_ID — Surrogate identifier of the corresponding row in PO_ATTRIBUTE_VALUES; documented as a foreign key to the transaction table.
• DRAFT_ID — Foreign key to the draft change request that owns this staged row. Together with ATTRIBUTE_VALUES_ID it forms the primary key SYS_C00204874 and the unique index PO_ATTR_VALUES_DRAFT_U1.
• CHANGE_ACCEPTED_FLAG — Indicates whether the staged change has been accepted and applied.
• DELETE_FLAG — Indicates that the matching record in PO_ATTRIBUTE_VALUES is to be deleted when the draft is applied.
• CHANGE_STATUS and REBUILD_SEARCH_INDEX_FLAG — Operational state markers used during the apply/merge cycle.
• PO_LINE_ID — Positive when the record is a child of a blanket line or quotation line, and -2 otherwise.
• REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM — Identify the requisition template and template line the attribute belongs to, or -2 when not template-driven.
• INVENTORY_ITEM_ID and ORG_ID — Item and operating unit context; these anchor the business-key unique index PO_ATTR_VALUES_DRAFT_U2.
• IP_CATEGORY_ID — Item category used by iProcurement.
• MANUFACTURER_PART_NUM, PICTURE, THUMBNAIL_IMAGE, SUPPLIER_URL, MANUFACTURER_URL, ATTACHMENT_URL, UNSPSC, AVAILABILITY, LEAD_TIME — Supplier-facing descriptive and catalog content presented through punchout and iProcurement catalogues.

PO_ATTR_VALUES_DRAFT_U2, over (INVENTORY_ITEM_ID, PO_LINE_ID, REQ_TEMPLATE_NAME, REQ_TEMPLATE_LINE_NUM, DRAFT_ID, ORG_ID), is the principal business-key candidate; PO_ATTR_VALUES_DRAFT_U1 mirrors the surrogate primary key. Non-unique indexes N1 (PO_LINE_ID), N2 (REQ_TEMPLATE_NAME, REQ_TEMPLATE_LINE_NUM) and N3 (DRAFT_ID) support lookup by line, template, and change set respectively.

Common Use Cases and Queries

Typical work includes reviewing outstanding supplier-proposed attribute changes, diagnosing why a catalogue edit did not appear in iProcurement, and purging stale draft rows after a change request has been applied or abandoned. Because the table is staged data, most reporting filters on CHANGE_ACCEPTED_FLAG, DELETE_FLAG, and CHANGE_STATUS.

• List all pending, unaccepted changes for a draft: SELECT ATTRIBUTE_VALUES_ID, PO_LINE_ID, INVENTORY_ITEM_ID FROM PO.PO_ATTRIBUTE_VALUES_DRAFT WHERE DRAFT_ID = :draft AND NVL(CHANGE_ACCEPTED_FLAG,'N') = 'N';
• Identify attribute rows staged for deletion from the master table: SELECT DRAFT_ID, ATTRIBUTE_VALUES_ID FROM PO.PO_ATTRIBUTE_VALUES_DRAFT WHERE DELETE_FLAG = 'Y';
• Reconcile drafts against the live table by joining on ATTRIBUTE_VALUES_ID to compare staged versus current values.
• Support catalogue administration troubleshooting by joining to item and category masters on INVENTORY_ITEM_ID and IP_CATEGORY_ID, restricted by ORG_ID.

Because drafts are transient, maintenance reporting should always constrain by DRAFT_ID or CHANGE_STATUS to avoid sweeping in historical change sets.

Related Objects

The table is documented as standalone in the relationship data, but its foreign-key comments and column semantics establish these dependencies:

• PO.PO_ATTRIBUTE_VALUES — The master table this draft shadows; joined on ATTRIBUTE_VALUES_ID.
• PO.PO_LINES_ALL — Referenced through PO_LINE_ID for blanket, quotation, and standard purchase order lines.
• PO.PO_HEADERS_ALL — Parent header reached via PO_LINE_ID and ORG_ID when resolving document context.
• PO.PO_REQ_TEMPLATES / requisition template tables — Resolved through REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM.
• INV.MTL_SYSTEM_ITEMS_B — Joined on INVENTORY_ITEM_ID and ORG_ID for item descriptions.
• Draft / change-request tables keyed by DRAFT_ID — The owning change set that governs the accept or reject lifecycle.
• iProcurement category structures — Linked through IP_CATEGORY_ID.
• PL/SQL apply and merge packages in the PO schema — The concurrent programs that move accepted draft rows into PO_ATTRIBUTE_VALUES and honour DELETE_FLAG.

These objects are the practical join points for any query that resolves a staged attribute change into its owning document, item, template, or change request.