Search Results po_attribute_values_tlp_draft




Overview
Explore in AI Chat

Overview

PO_ATTRIBUTE_VALUES_TLP_DRAFT is a table in the PO (Purchasing) schema of Oracle E-Business Suite. It is documented with a status of VALID and is described in the ETRM metadata as a draft table for PO_ATTRIBUTE_VALUES_TLP. Its role in Oracle EBS is to hold staged, transient, or in-progress attribute value records associated with the Template Line Pricing (TLP) attribute framework maintained by Oracle Purchasing, preserving that data until the draft is either promoted to the base table or discarded. The 178 documented columns establish it as a wide, attribute-intensive staging object rather than an operational transaction table.

From a Data Vault modeling perspective, the heuristic classification mined from the FK structure is standalone, meaning the table is not resolved as a hub, link, or satellite. This should be read as a modeling suggestion and a signal that no foreign-key relationships to other tables are documented for this object, so any hub or satellite treatment would need to be derived from its composite primary key and unique business keys rather than from declared referential constraints.

Key Information Stored

The documented composite primary key is the constraint SYS_C00204887, comprising ATTRIBUTE_VALUES_TLP_ID and DRAFT_ID. ATTRIBUTE_VALUES_TLP_ID is the surrogate identifier for the attribute value set; DRAFT_ID identifies the draft context in which the row was staged. Together they distinguish successive draft versions sharing the same attribute value identity.

Two documented unique indexes act as business-key candidates. PO_ATTR_VALUES_TLP_DRAFT_U1 covers (ATTRIBUTE_VALUES_TLP_ID, DRAFT_ID), reinforcing the surrogate pair as a unique key. PO_ATTR_VALUES_TLP_DRAFT_U2 covers (INVENTORY_ITEM_ID, PO_LINE_ID, REQ_TEMPLATE_NAME, REQ_TEMPLATE_LINE_NUM, ORG_ID, LANGUAGE, DRAFT_ID), identifying a draft attribute row by its item, purchasing line, requisition template context, organization, language, and draft.

The most significant stored columns include:

Common Use Cases and Queries

Typical uses center on draft attribute maintenance for template line pricing. Practitioners query the table to inspect pending changes, audit which attributes were modified, and reconcile drafts against the base PO_ATTRIBUTE_VALUES_TLP records before promotion. A representative pattern lists unaccepted draft changes by item and line:

  • SELECT ATTRIBUTE_VALUES_TLP_ID, DRAFT_ID, INVENTORY_ITEM_ID, PO_LINE_ID, CHANGE_STATUS FROM PO.PO_ATTRIBUTE_VALUES_TLP_DRAFT WHERE CHANGE_ACCEPTED_FLAG = 'N' AND DELETE_FLAG = 'N';
  • Joining on the U2 business key to compare draft and base values, using INVENTORY_ITEM_ID, PO_LINE_ID, ORG_ID, LANGUAGE, and REQ_TEMPLATE_NAME as the correlation predicate.
  • Filtering by REQUEST_ID or PROGRAM_ID to trace which concurrent program populated or updated a batch of draft rows.
  • Scanning for REBUILD_SEARCH_INDEX_FLAG set to 'Y' to identify drafts whose attribute text must be re-indexed.

Because the table is a draft staging object, reporting should generally distinguish it from the published attribute records and treat CHANGE_ACCEPTED_FLAG and DELETE_FLAG as the primary state indicators.

Related Objects

The metadata documents no foreign-key relationships for this object, consistent with its standalone Data Vault classification. The most significant related objects are therefore those implied by the published/draft pairing and the shared attribute naming convention:

  • PO_ATTRIBUTE_VALUES_TLP — the base table for which this table is the documented draft counterpart; joins align on ATTRIBUTE_VALUES_TLP_ID.
  • PO_LINES_ALL — the purchasing line referenced by PO_LINE_ID.
  • PO_HEADERS_ALL — the purchasing document header reached through PO_LINE_ID.
  • MTL_SYSTEM_ITEMS_B — the item master referenced by INVENTORY_ITEM_ID and ORG_ID.
  • PO_REQ_TEMPLATES / requisition template views — the source of REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM.
  • FND_LANGUAGES — the installed language referenced by LANGUAGE.
  • FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — resolved through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.
  • FND_USER — resolved through CREATED_BY and LAST_UPDATED_BY for audit reporting.

No views or APIs referencing this object are documented in the supplied ETRM metadata; any additional dependencies should be confirmed against the deployment's data dictionary before being relied upon.