Search Results pon_price_element_types_u1

Overview

PON.PON_PRICE_ELEMENT_TYPES is a foundational setup table in the Oracle E-Business Suite Procurement (PON) schema that stores the master definitions of cost factors, historically referred to as "Price Elements" or "Price Factors" in earlier releases. A price element represents any discrete cost associated with moving goods from one location to another, as well as intangible costs such as the expense of switching to a new supplier when the record is used within the Sourcing process. Each row defines one price element type that sourcing, purchasing, and cost roll-up processes can later reference.

Within ETRM 12.2.2, the object is owned by the PON schema, resides in the APPS_TS_TX_DATA tablespace, and exposes 16 documented columns. A heuristic Data Vault classification based on the mined foreign-key structure places this table in a hub-leaning role: it is the anchor entity whose PRICE_ELEMENT_TYPE_ID is referenced by numerous downstream transactional and interface tables. Under this modeling suggestion, PON_PRICE_ELEMENT_TYPES maps to a hub, while its language, transaction, and staging consumers behave as links or satellites.

Key Information Stored

The surrogate primary key is PRICE_ELEMENT_TYPE_ID (NUMBER), the system-generated unique identifier of each price element. Two unique indexes are documented. PON_PRICE_ELEMENT_TYPES_U1 is a NORMAL UNIQUE index on PRICE_ELEMENT_TYPE_ID (expanded to include ZD_EDITION_NAME in 12.2.2 terminology). PON_PRICE_ELEMENT_TYPES_U2 is a FUNCTION-BASED NORMAL UNIQUE index on UPPER("PRICE_ELEMENT_CODE"), making the upper-cased code the principal business-key candidate.

• TRADING_PARTNER_ID — identifies the company trading partner that owns the price element definition.
• PRICE_ELEMENT_CODE — user-defined alphanumeric code for the price element; the business-key candidate enforced by the functional unique index.
• PRICING_BASIS — how the factor is calculated, using lookup PON_PRICING_BASIS with values PER_UNIT, FIXED_AMOUNT, or PERCENTAGE.
• ENABLED_FLAG — Y/N flag indicating whether the price element type is active.
• SYSTEM_FLAG — Y/N flag identifying pre-seeded elements such as "item price."
• ALLOCATION_BASIS — method for prorating summary charges to the line level (for example weight, volume, or value).
• INVOICE_LINE_TYPE — the Oracle Payables invoice line type applied to this cost factor.
• COST_COMPONENT_CLASS_ID — identifier of the cost component class, used to bucket component costs making up total cost.
• COST_ANALYSIS_CODE, COST_ACQUISITION_CODE — classification codes supporting cost analysis and acquisition reporting.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard Who columns for audit lineage.

Common Use Cases and Queries

Typical scenarios include reviewing the active cost factor catalogue, validating pricing-basis configuration before sourcing events, and reporting on which elements feed cost roll-ups or Payables invoicing. A standard lookup joins the base table to its translation table on PRICE_ELEMENT_TYPE_ID:

• SELECT pet.PRICE_ELEMENT_TYPE_ID, pet.PRICE_ELEMENT_CODE, pet.PRICING_BASIS, pet.ALLOCATION_BASIS, pet.ENABLED_FLAG FROM PON.PON_PRICE_ELEMENT_TYPES pet WHERE pet.ENABLED_FLAG = 'Y';
• SELECT pet.PRICE_ELEMENT_CODE, tl.DESCRIPTION FROM PON.PON_PRICE_ELEMENT_TYPES pet JOIN PON.PON_PRICE_ELEMENT_TYPES_TL tl ON tl.PRICE_ELEMENT_TYPE_ID = pet.PRICE_ELEMENT_TYPE_ID WHERE tl.LANGUAGE = USERENV('LANG');
• Identifying user-defined versus seeded elements with SYSTEM_FLAG = 'N', and grouping elements by PRICING_BASIS to reconcile percentage, fixed-amount, and per-unit charges.
• Reconciling interface feeds by joining PON_BID_PRICE_ELEMENTS_INT or PON_AUC_PRICE_ELEMENTS_INT back to the type master via PRICE_ELEMENT_TYPE_ID.

Related Objects

The PK is referenced through PRICE_ELEMENT_TYPE_ID by several significant dependents. PON_PRICE_ELEMENTS holds the transactional price element values applied to documents, while PON_PRICE_ELEMENT_TYPES_TL supplies language-specific descriptions for the type. PO_COST_MST carries cost master records tied to the type, and PON_BID_PRICE_ELEMENTS_INT and PON_AUC_PRICE_ELEMENTS_INT stage auction and bid price element data prior to processing. PON_FPK_DELETED_PRICE_ELEMENTS and PON_LARGE_NEG_PF_VALUES track deleted and exception pricing factor values, and PON_INTERFACE_ERRORS records rejected interface rows referencing the type. These relationships confirm the hub-leaning classification and make the master a central lookup for procurement cost modelling.