Search Results pon_price_element_types_tl




Overview
Explore in AI Chat

Overview

The PON_PRICE_ELEMENT_TYPES_TL table is a core data object within the Oracle E-Business Suite (EBS) Sourcing (PON) module, specifically in versions 12.1.1 and 12.2.2. As a translation table (denoted by the "_TL" suffix), its primary function is to store multilingual descriptions and names for price element types. This table enables the Sourcing application to present user-defined price components—such as freight, tax, discounts, or surcharges—in the language of the user's session, supporting global deployment and localization requirements. It operates in conjunction with its base table, PON_PRICE_ELEMENT_TYPES, to provide a complete, language-aware definition of the price constructs used in negotiations, auctions, and purchase orders.

Key Information Stored

The table's structure is designed to manage translated text for discrete price element types. Its primary key is a composite of PRICE_ELEMENT_TYPE_ID and LANGUAGE, ensuring a unique entry for each type-language combination. The PRICE_ELEMENT_TYPE_ID is a foreign key that links directly to the PON_PRICE_ELEMENT_TYPES base table, which holds the non-translatable attributes. The LANGUAGE column stores the standard Oracle language code (e.g., 'US' for American English). The most critical data columns typically include NAME and DESCRIPTION, which hold the translated, user-facing label and explanatory text for the price element type. Additional standard columns common to EBS translation tables, such as SOURCE_LANG, CREATION_DATE, and LAST_UPDATE_DATE, are also present to manage data origin and lifecycle.

Common Use Cases and Queries

This table is primarily accessed by the application's internal logic to render UI elements and reports in the correct language. Common functional use cases include generating localized negotiation documents and displaying price breakdowns on purchase orders. From a reporting and support perspective, queries often join this table to its base table to analyze price element setup across installations. A fundamental sample SQL pattern is retrieving all translations for a specific price element type:

  • SELECT petl.language, petl.name, petl.description FROM pon_price_element_types_tl petl WHERE petl.price_element_type_id = :1;

Another common query is to verify the setup for a given language or to identify missing translations by joining to the base table and filtering on the desired language code.

Related Objects

The PON_PRICE_ELEMENT_TYPES_TL table has a direct and essential relationship with the PON_PRICE_ELEMENT_TYPES table, as defined by its sole foreign key constraint. This relationship is foundational; every record in the TL table must correspond to a master record in PON_PRICE_ELEMENT_TYPES. The table is also intrinsically linked to the broader pricing and negotiation data model within the Sourcing module. It is referenced by views and application programming interfaces (APIs) that handle price element configuration and display. While specific dependent view names are not provided in the metadata, objects such as PON_PRICE_ELEMENTS, which store the actual price values for documents, ultimately rely on the definitions stored in this translation table for proper user interface presentation.