Search Results pon_price_element_types_vl




Overview
Explore in AI Chat

Overview

PON_PRICE_ELEMENT_TYPES_VL is an APPS-owned, valid database view in the Oracle E-Business Suite PON (Sourcing) product family. Its documented purpose is to expose price element type names and descriptions in the session language, making it the translation-aware (VL, or "view language") interface to the underlying price element type definition. Price element types form the foundation of Oracle Sourcing and Procurement pricing structures: each row describes a component that contributes to the total price of a negotiation, quote, or award, such as material, freight, duty, or surcharges. The view is primarily used for lookups, user-interface value lists, and reporting, since it resolves the language-specific NAME and DESCRIPTION columns without requiring the caller to join the translation table explicitly. Because it is a VL view, it joins to the non-translated base table and the translation table, filtering translation rows to the language returned by USERENV('LANG'). This makes it appropriate for concurrent programs, Oracle Reports, Oracle Application Framework (OAF) pages, and integration extracts that must present price element data in the user's own language.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS synonyms:

The view text joins these on PRICE_ELEMENT_TYPE_ID and restricts the translation row with T.LANGUAGE = USERENV('LANG'), returning one row per price element type in the current session language. The ROW_ID column is derived from the base table ROWID (aliased B), preserving a stable row identifier for the non-translated record.

Key Columns

  • PRICE_ELEMENT_TYPE_ID — primary identifier of the price element type; the join key between the base and translation tables.
  • NAME / DESCRIPTION — translated display name and description for the session language, sourced from PON_PRICE_ELEMENT_TYPES_TL.
  • PRICING_BASIS — the basis on which the element is priced; this is the column most directly relevant to the user's "pricing_basis" search, and it drives how the price element is applied during pricing calculations.
  • PRICE_ELEMENT_CODE — internal code identifying the price element type, commonly used for seeded or system-defined lookups.
  • TRADING_PARTNER_ID — the trading partner (typically a supplier or operating unit context) to which the price element type is scoped.
  • ENABLED_FLAG / SYSTEM_FLAG — indicate whether the element type is active and whether it is seeded by Oracle (system) rather than user-defined.
  • ALLOCATION_BASIS — determines how the price element is allocated across lines.
  • INVOICE_LINE_TYPE — the invoice line type associated with the element for downstream invoicing.
  • COST_COMPONENT_CLASS_ID, COST_ANALYSIS_CODE, COST_ACQUISITION_CODE — cost accounting attributes that map the element to cost components and analysis/acquisition codes.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include building value lists of active price element types for a given trading partner, reporting on pricing basis distribution, and extracting translated pricing metadata for integration. A representative query listing enabled, system-defined elements and their pricing basis is:

  • SELECT price_element_type_id, name, price_element_code, pricing_basis, enabled_flag FROM pon_price_element_types_vl WHERE enabled_flag = 'Y' ORDER BY name;
  • SELECT pricing_basis, COUNT(*) FROM pon_price_element_types_vl WHERE trading_partner_id = :partner_id GROUP BY pricing_basis;
  • SELECT t.name, t.description, b.allocation_basis FROM pon_price_element_types_vl t WHERE t.system_flag = 'Y';

Because the view restricts output to the session language, queries return only translated rows for the active language; callers requiring all languages must query PON_PRICE_ELEMENT_TYPES_TL directly. Oracle Proprietary, Confidential Information — Legal Notices apply.