Results for “po_headers_all_ext_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO.PO_HEADERS_ALL_EXT_TL is a Purchasing (PO) module table that stores translated user-defined attribute (UDA) data belonging to document headers. Its scope covers the full range of Purchasing documents — purchase orders, purchase agreements, quotations, and RFQs — so that descriptive attribute values attached to a document header can be persisted per language. The _TL suffix denotes a translation table: the table carries both a LANGUAGE column and a SOURCE_LANG column, indicating that attribute content is stored in multiple installed languages rather than in a single base row.

In Oracle EBS 12.1.1 and 12.2.2, UDA functionality is delivered through the Oracle Procurement extensibility framework, in which attribute groups and templates are attached to a document, then populated with values. Because UDA content is user-visible descriptive text, it is stored in the translation layer, while the corresponding non-translated extension rows reside in the base extension table. The documented foreign key on DRAFT_ID referencing PO_DRAFTS indicates that the table participates in the draft-versioning model introduced for document authoring. From a heuristic Data Vault standpoint, the table is best modeled as a standalone satellite: it holds descriptive, language-dependent attributes and inherits its parent identity from the header rather than acting as a hub or link in its own right.

Key Information Stored

The table is physically wide — 58 documented columns in the 12.2.2 schema — but the meaningful content is concentrated in identification, language, and attribute-value fields.

• EXTENSION_ID — the surrogate identifier for the extension row.
• PO_HEADER_ID — the business-key candidate linking the row to its parent document header.
• ATTR_GROUP_ID and UDA_TEMPLATE_ID — identify which attribute group and template definition the values belong to.
• DATA_LEVEL_ID — indicates the level within the document structure at which the attribute data applies.
• PK1_VALUE through PK5_VALUE — composite key components used to anchor the UDA values to a distinct record context.
• LANGUAGE and SOURCE_LANG — the translation language of the row and the source language from which it derives.
• TL_EXT_ATTR1 through TL_EXT_ATTR40 — forty translated extension attribute columns holding the actual UDA values.
• DRAFT_ID — reference to the associated draft document in PO_DRAFTS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS audit columns.

Whereas EXTENSION_ID serves as the surrogate primary key, PO_HEADER_ID combined with the attribute-group, template, level, and PK-value columns forms the practical business-key candidate used to resolve a unique UDA instance per language.

Common Use Cases and Queries

Typical reporting requirements include retrieving all UDA values for a given purchase order in the user's session language, auditing which templates have been applied to agreements, and reconciling draft versus released UDA content.

• Extracting header UDA values for a specific order: join on PO_HEADER_ID and filter LANGUAGE to the appropriate language code.
• Identifying documents that carry a particular attribute group: filter on ATTR_GROUP_ID or UDA_TEMPLATE_ID.
• Comparing translated versus base-language content: compare rows where LANGUAGE differs from SOURCE_LANG.
• Draft analysis: join DRAFT_ID to PO_DRAFTS to trace UDA content through the authoring lifecycle.
• Extensibility auditing: count populated TL_EXT_ATTRn columns to determine template utilization.

Because the attribute payload is spread across forty columns, extraction queries are frequently generated dynamically from UDA_TEMPLATE_ID metadata rather than hard-coded.

Related Objects

• PO.PO_DRAFTS — referenced through DRAFT_ID; supports the draft authoring model.
• PO.PO_HEADERS_ALL — the parent document header table, joined via PO_HEADER_ID.
• The base (non-translated) header extension table in the PO schema, which holds the untranslated counterpart rows.
• UDA template and attribute-group definition tables referenced by UDA_TEMPLATE_ID and ATTR_GROUP_ID.
• Purchasing document views and the PO Attachments/UDA inquiry pages that surface translated attribute values.
• Multi-language and translation maintenance concurrent programs that populate the _TL rows.