Search Results sys_c00204817

Overview

PO_ATTRIBUTE_VALUES_TLP is a valid table in the PO (Purchasing) schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. Its documented purpose is to store translatable descriptor values for records that are searchable in iProcurement. In practical terms, the table functions as the multilingual descriptor store that iProcurement relies upon when rendering and matching searchable purchasing content, such as catalog line descriptions, template line attributes, and category-level descriptor text. The table name carries the _TLP suffix, indicating that it holds translatable values in a denormalized, language-aware layout keyed by a LANGUAGE column and paired with attribute value columns rather than the more typical _TL companion structure.

From a Data Vault modeling perspective, the documented heuristic classification for this object is standalone. This suggests that the table can be modeled as an independent hub-like entity centered on its surrogate identifier, with no enforced outbound foreign keys in the documented metadata. Analysts adopting a Data Vault design should therefore treat ATTRIBUTE_VALUES_TLP_ID as the natural hub key and consider the surrounding descriptive columns as effectivity-satellite content rather than as an enforced link to other hubs.

Key Information Stored

The documented physical schema contains 174 columns, the vast majority of which are repeating translatable attribute buckets. The most functionally significant columns are as follows:

• ATTRIBUTE_VALUES_TLP_ID — the surrogate primary key, enforced by unique index SYS_C00204817 and by PO_ATTRIBUTE_VALUES_TLP_U1. This is the row-level identifier for each translatable descriptor record.
• PO_LINE_ID — the purchasing document line to which the descriptor values belong.
• REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM — the requisition template name and line number that define the descriptor context.
• INVENTORY_ITEM_ID and ORG_ID — the inventory item and operating unit against which the descriptor is scoped.
• LANGUAGE — the language code that makes the row translatable; together with the preceding columns it forms the business-key candidate PO_ATTRIBUTE_VALUES_TLP_U2 (PO_LINE_ID, REQ_TEMPLATE_NAME, REQ_TEMPLATE_LINE_NUM, INVENTORY_ITEM_ID, ORG_ID, LANGUAGE).
• IP_CATEGORY_ID — the iProcurement category associated with the descriptor.
• DESCRIPTION, LONG_DESCRIPTION, MANUFACTURER, COMMENTS, and ALIAS — core human-readable descriptor text fields used for search and display.
• TL_TEXT_BASE_ATTRIBUTE1 through TL_TEXT_BASE_ATTRIBUTE100 — one hundred repeating translatable attribute buckets for base-level descriptor text.
• TL_TEXT_CAT_ATTRIBUTE1 through TL_TEXT_CAT_ATTRIBUTE50 — fifty repeating translatable attribute buckets for category-level descriptor text.
• REBUILD_SEARCH_INDEX_FLAG — a control flag used to signal that the associated iProcurement search index must be rebuilt after descriptor changes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_PROGRAM, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE for concurrent program traceability.

Two unique indexes are documented: SYS_C00204817 on the surrogate key, and PO_ATTRIBUTE_VALUES_TLP_U1 on ATTRIBUTE_VALUES_TLP_ID. The composite business-key candidate is captured in PO_ATTRIBUTE_VALUES_TLP_U2. Note that the metadata does not document an enforced foreign key, consistent with its standalone classification.

Common Use Cases and Queries

Typical scenarios include troubleshooting iProcurement search results, verifying that descriptor text has been translated for a given language, and reconciling which purchasing lines carry translatable attribute content. A representative query to retrieve descriptor rows for a specific line and language is:

• SELECT attribute_values_tlp_id, po_line_id, req_template_name, language, description, alias FROM po.po_attribute_values_tlp WHERE po_line_id = :line_id AND language = USERENV('LANG');
• To find rows awaiting index rebuild: SELECT attribute_values_tlp_id, po_line_id, rebuild_search_index_flag FROM po.po_attribute_values_tlp WHERE rebuild_search_index_flag = 'Y';
• To audit recent changes: SELECT attribute_values_tlp_id, last_updated_by, last_update_date, last_updated_program FROM po.po_attribute_values_tlp WHERE last_update_date > SYSDATE - 7;

Reporting use cases centre on multilingual catalog coverage, identifying items with missing translations, and validating that descriptor buckets (TL_TEXT_BASE_ATTRIBUTE and TL_TEXT_CAT_ATTRIBUTE) are populated consistently across languages.

Related Objects

The documented metadata shows no enforced inbound or outbound foreign keys, so related objects are described by their logical association through shared columns rather than by referential constraint. The most significant related objects are:

• PO_LINES_ALL — the purchasing line master, joined on PO_LINE_ID.
• PO_LINE_LOCATIONS_ALL — shipment-level detail that shares the line context.
• PO_ATTRIBUTE_VALUES — the base (non-translatable) counterpart table holding the same descriptor values.
• PO_ATTRIBUTE_VALUES_TL — the translatable companion table, where present in the release.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORG_ID to resolve item detail.
• PO_REQ_TEMPLATES_ALL / PO_REQ_TEMPLATE_LINES — joined on REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM.
• PO_CATEGORIES / IP_CATEGORIES — joined on IP_CATEGORY_ID for category descriptor context.
• FND_LANGUAGES — joined on LANGUAGE to resolve language names.

Because the table participates in iProcurement search, the purchasing document search index and its concurrent rebuild programs are the primary dependent processes rather than referential constraints.