Search Results tl_text_base_attribute48

Overview

PO_ATTR_VALUES_TLP_MERGE_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, documented as VALID under ETRM 12.2.2 and applicable to 12.1.1 as well. It presents attribute value records associated with two-level (TLP) purchasing, exposing template-driven descriptive and category attribute data captured against purchase lines, sourcing rules, and requirement templates. The view functions as a merge or union surface that consolidates records from the accepted base table PO_ATTRIBUTE_VALUES_TLP and the staged draft table PO_ATTRIBUTE_VALUES_TLP_DRAFT, together with the PO_DRAFTS header and PO_LINES_ALL line information, so that consumers see a single, unified projection of attribute values regardless of whether the underlying row has been committed or is still held in a draft. This makes it a convenient reporting and integration layer: external systems, custom reports, and conversion routines can query one object rather than reconcile multiple tables and draft states themselves. Attribute values such as manufacturer, alias, long description, comments, and the TL_TEXT_BASE_ATTRIBUTE1 through TL_TEXT_BASE_ATTRIBUTEn columns flow through unchanged from the base tables, preserving multilingual (TL) text and interface identifiers.

Underlying Base Objects

The documented base objects referenced by the view are:

• PO_ATTRIBUTE_VALUES_TLP — the committed attribute values table for two-level purchasing.
• PO_ATTRIBUTE_VALUES_TLP_DRAFT — the draft (uncommitted) counterpart holding staged changes.
• PO_DRAFTS — the drafts header that identifies and governs pending change sets.
• PO_LINES_ALL — the purchasing line table supplying line context for the attribute values.

Each of these is exposed in the view definition through APPS synonyms (for example PO_ATTRIBUTE_VALUES_TLP appearing as a synonym). The view selects from the attribute values data (aliased PAVTD) and merges committed and draft rows using the common key columns INTERFACE_ATTR_VALUES_TLP_ID, ATTRIBUTE_VALUES_TLP_ID, PO_LINE_ID, and ASL_ID. Draft filtering through PO_DRAFTS ensures only the currently active change set participates in the merge, while PO_LINES_ALL anchors each attribute record to its parent line. Because the view spans both base and draft tables, it reflects the state of the data as Oracle Purchasing expects to see it, without requiring the caller to join drafts manually.

Key Columns

• ATTRIBUTE_VALUES_TLP_ID — primary identifier for an attribute value record.
• INTERFACE_ATTR_VALUES_TLP_ID — the interface (staging) identifier used during import and merge processing.
• PO_LINE_ID — foreign key to the purchasing line (PO_LINES_ALL) the values belong to.
• ASL_ID — identifies the Approved Supplier List entry associated with the values.
• REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM — the requirement template and template line from which the attributes originated.
• IP_CATEGORY_ID, INVENTORY_ITEM_ID, ORG_ID — categorization and organization context.
• LANGUAGE — language code for the TL text columns.
• DESCRIPTION, MANUFACTURER, COMMENTS, ALIAS, LONG_DESCRIPTION — descriptive attribute values.
• TL_TEXT_BASE_ATTRIBUTE1 through TL_TEXT_BASE_ATTRIBUTE48 — the translated text attribute slots carrying template-defined values.

Common Use Cases and Queries

The view is used to report or integrate attribute values across committed and draft states, to validate attribute capture during sourcing and template-based line creation, and to reconcile staged values before a draft is committed. The user search term "change_accepted_flag" often arises when inspecting whether a draft or interface row has been accepted into the base table; while that flag is not part of this view's documented column list, it is typically checked on the draft/interface tables, and rows surviving the merge can be correlated accordingly.

A representative query is:

SELECT attribute_values_tlp_id, po_line_id, asl_id, req_template_name, req_template_line_num, manufacturer, alias, long_description, org_id FROM apps.po_attr_values_tlp_merge_v WHERE po_line_id = :p_line_id ORDER BY attribute_values_tlp_id;

Additional filters on ORG_ID, REQ_TEMPLATE_NAME, or specific TL_TEXT_BASE_ATTRIBUTEn columns are common for template-specific reporting and for verifying the merged output of draft versus base rows.