Search Results po_attr_values_tlp_draft_u2

Overview

PO.PO_ATTRIBUTE_VALUES_TLP_DRAFT is a draft (staging) table in the Oracle E-Business Suite Purchasing (PO) schema, documented as VALID and registered under FND Design Data PO.PO_ATTRIBUTE_VALUES_TLP_DRAFT. It is the draft counterpart of PO_ATTRIBUTE_VALUES_TLP, and its stated purpose is to hold pending changes entered by a supplier or a catalog administrator when they edit a purchasing document directly. Rather than writing changes immediately to the base attribute-values table, EBS captures them here until the draft change request is accepted or rejected, which preserves the integrity of the committed document while allowing in-flight edits.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10. Its documented physical schema in ETRM 12.2.2 shows 178 columns, making it a wide descriptive table whose bulk consists of flexfield-style text attribute columns. Mined FK/PK relationship data classifies the object as standalone, with no enforced foreign keys to other tables in the vault. Under a Data Vault modeling suggestion, this object is best treated as a satellite: it is keyed by a composite identifier, carries descriptive and state attributes, and is loaded in response to changes to a parent business entity (the draft change request). It is not a hub or link, since its identifiers are not independent business keys of their own.

Key Information Stored

The primary key is the system-named constraint SYS_C00204887, defined over (ATTRIBUTE_VALUES_TLP_ID, DRAFT_ID). This surrogate pair ties each draft row to a base attribute-values record and to the draft change request that owns the pending edit. Two unique indexes act as business-key candidates: PO_ATTR_VALUES_TLP_DRAFT_U1 on (ATTRIBUTE_VALUES_TLP_ID, DRAFT_ID), which mirrors the primary key, and PO_ATTR_VALUES_TLP_DRAFT_U2 on (INVENTORY_ITEM_ID, PO_LINE_ID, REQ_TEMPLATE_NAME, REQ_TEMPLATE_LINE_NUM, ORG_ID, LANGUAGE, DRAFT_ID), which identifies the item, line, requisition template context, operating unit, language, and draft in which the attribute values are defined.

The most significant columns include ATTRIBUTE_VALUES_TLP_ID (foreign key to the transaction table) and DRAFT_ID (foreign key to the draft change request). CHANGE_ACCEPTED_FLAG records whether the draft has been accepted, while DELETE_FLAG indicates that the corresponding row in PO_ATTRIBUTE_VALUES should be deleted on approval. PO_LINE_ID is populated with a positive value when the row is a child of a blank or quotation line, and -2 otherwise. REQ_TEMPLATE_NAME (25 characters) and REQ_TEMPLATE_LINE_NUM identify the requisition template context, again using -2 when not applicable. IP_CATEGORY_ID holds the iProcurement item category; INVENTORY_ITEM_ID and ORG_ID identify the item and operating unit; LANGUAGE records the language of the descriptor values; DESCRIPTION (240), MANUFACTURER (700), COMMENTS (700), and ALIAS complete the descriptive set. The remaining 100+ TL_TEXT_BASE_ATTRIBUTE and TL_TEXT_CAT_ATTRIBUTE columns store multi-language descriptor values, while standard WHO columns and REQUEST_ID/PROGRAM_ID support concurrent-program auditing.

Common Use Cases and Queries

Typical usage centers on reviewing pending supplier or catalog edits before approval. A common query lists unaccepted drafts for a given item and organization:

• SELECT ATTRIBUTE_VALUES_TLP_ID, DRAFT_ID, PO_LINE_ID, INVENTORY_ITEM_ID, ORG_ID, CHANGE_ACCEPTED_FLAG, DELETE_FLAG FROM PO.PO_ATTRIBUTE_VALUES_TLP_DRAFT WHERE CHANGE_ACCEPTED_FLAG = 'N';
• Joining on DRAFT_ID to the draft change request header to identify the requesting supplier and submission date.
• Comparing draft rows against the base PO_ATTRIBUTE_VALUES_TLP table on ATTRIBUTE_VALUES_TLP_ID to produce a before/after attribute diff.
• Filtering by REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM to audit template-driven attribute changes.

Reporting scenarios include pending-change aging reports, purge candidates where a draft has been accepted or superseded (index PO_ATTR_VALUES_TLP_DRAFT_N3 on DRAFT_ID supports such deletes), and reconciliation between CTL and BASE attribute text columns.

Related Objects

• PO.PO_ATTRIBUTE_VALUES_TLP — the base table this object stages changes for; join on ATTRIBUTE_VALUES_TLP_ID.
• PO_ATTRIBUTE_VALUES — referenced by DELETE_FLAG semantics; a set flag signals a deletion of the corresponding base row.
• The purchasing draft change request header, joined via DRAFT_ID, which governs acceptance or rejection of the pending edit.
• PO_LINES_ALL / PO_HEADERS_ALL — provide the document context for PO_LINE_ID.
• MTL_SYSTEM_ITEMS_B — supplies descriptions for INVENTORY_ITEM_ID in iProcurement reporting.
• FND_FLEX_VALUES_TL and the DFF value tables — interpret the TL_TEXT_BASE_ATTRIBUTE and TL_TEXT_CAT_ATTRIBUTE descriptor columns.
• PO_ATTR_VALUES_TLP_DRAFT_U1, _U2, and the _N1–_N3 indexes — enforce uniqueness and accelerate line- and template-based access.