Search Results pon_auction_headers_ext_tl

Overview

The PON_AUCTION_HEADERS_EXT_TL table is a Purchasing (PO) module object in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2 releases. It stores the descriptive and translated values of User-Defined Attribute (UDA) extensions captured at the negotiation (auction) header level. In the sourcing domain, administrators and buyers define UDA templates that extend standard negotiation headers with customer-specific fields; this table holds the entered attribute values for those extended fields, linked back to the parent negotiation, attribute group, and UDA template definition.

The object is owned by the PO schema. It carries a _TL suffix, indicating it is a translation-enabled table. This means the same logical attribute value may exist in multiple language rows, distinguished by LANGUAGE and SOURCE_LANG, with the base (source) language row serving as the fallback for any language that lacks a translated record. Access patterns therefore typically filter on LANGUAGE or join through the associated base extension table.

Based on the foreign-key structure mined from the ETRM metadata, this table can be modeled, heuristically, as a satellite in Data Vault terms — it hangs off the negotiation header hub (via AUCTION_HEADER_ID) and holds descriptive, non-key attribute payload around a business parent. The metadata classifies its relationship profile as standalone, meaning it does not itself act as a hub or link for downstream dependents in this definition.

Key Information Stored

The physical schema documents 57 columns. The most functionally significant are:

• EXTENSION_ID — the surrogate identifier for the extension row; the closest candidate for a technical primary key.
• AUCTION_HEADER_ID — the business foreign key to the parent negotiation header in PON_AUCTION_HEADERS_ALL.
• ATTR_GROUP_ID — identifies the attribute group within the UDA template to which the row belongs.
• UDA_TEMPLATE_ID — links the row to the user-defined attribute template governing the extended fields.
• DATA_LEVEL_ID — indicates the data level context for the extension.
• PK1_VALUE through PK5_VALUE — composite key value segments used to resolve the owning record in generic UDA infrastructure.
• LANGUAGE and SOURCE_LANG — the language of the current row and the source (base) language used for translation fallback.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS WHO columns for auditing and concurrency.
• TL_EXT_ATTR1 through TL_EXT_ATTR40 — the translated extended attribute value slots that carry the actual user-defined data entered at the negotiation header level.

The surrogate key is EXTENSION_ID; the business linkage is established through AUCTION_HEADER_ID, and uniqueness within the translation model is further scoped by LANGUAGE combined with the attribute/template identifiers.

Common Use Cases and Queries

The table is principally queried to report and extract user-defined negotiation attributes alongside their standard auction header data. A typical reporting join resolves the negotiation, its language, and the associated template definition:

• Negotiation extension reporting — joining PON_AUCTION_HEADERS_EXT_TL to PON_AUCTION_HEADERS_ALL on AUCTION_HEADER_ID to surface UDA values for a specific auction number.
• Language-specific extraction — filtering on LANGUAGE (with fallback to SOURCE_LANG) to retrieve the correctly translated attribute values for a given user session.
• Template-based analysis — grouping by UDA_TEMPLATE_ID and ATTR_GROUP_ID to validate that all required UDA fields were populated for a negotiation.
• Audit and compliance — reviewing LAST_UPDATED_BY and LAST_UPDATE_DATE to trace when header-level UDA values were last changed.

Because the attribute values are stored in generic TL_EXT_ATTR slots, queries must always be joined to the UDA template metadata to map a populated slot to its meaningful business field name.

Related Objects

The most significant objects related to PON_AUCTION_HEADERS_EXT_TL are:

• PON_AUCTION_HEADERS_ALL — the parent negotiation header table, joined on AUCTION_HEADER_ID = AUCTION_HEADER_ID. This is the only documented foreign-key relationship.
• PON_AUCTION_HEADERS_EXT — the base (non-translated) extension table, providing the source-language fallback and the surrogate row identity.
• UDA template definition objects (for example, the PO user-defined attribute template tables referenced by UDA_TEMPLATE_ID and ATTR_GROUP_ID) — required to translate generic slot names into business labels.
• PON_AUCTION_HEADERS_TL and related _TL siblings of the negotiation header family — used when building fully translated negotiation reports.
• PON_AUCTION_HEADERS_EXT_TL consumers via the Sourcing/Oracle iProcurement user interfaces, which read and write UDA values through the standard PO extension APIs rather than direct SQL.