Results for “trading_partner_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PON_PRICE_ELEMENT_LISTS is a table within the PON (Sourcing) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. Its documented purpose is to store price element list details — the header-level definitions that group and organize price elements used in sourcing negotiations, quotations, and supplier price schedules. In sourcing workflows, a price element list acts as a reusable container that determines which cost or price components (for example, freight, duty, material, or processing charges) are collected and evaluated against a supplier's response.

Under a heuristic Data Vault classification mined from the foreign key structure, this object is hub-leaning. In Data Vault modeling terms, it is best treated as a hub candidate: a stable, business-defined entity identified by a surrogate key, with dependent descriptive attributes carried in a satellite. The table does not sit on the many-side of a dependent link, confirming its role as a parent entity referenced by other PON objects.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • LIST_ID — The surrogate primary key (PON_PRICE_ELEMENT_LISTS_PK) identifying each list. It is also the sole unique index candidate (PON_PRICE_ELEMENT_LISTS_U1), meaning it serves as both the technical and business key in the documented metadata.
  • LIST_NAME — The descriptive name assigned to the price element list, used to identify it in sourcing setup and negotiation screens.
  • DESCRIPTION — Free-text description providing business context for the list.
  • LIST_STATUS — Controls whether the list is active or inactive, governing its availability for selection in sourcing documents.
  • TRADING_PARTNER_ID — References the trading partner (supplier) associated with the list, indicating that lists may be defined at a supplier-specific level.
  • CREATION_DATE / CREATED_BY — Standard audit columns recording who created the row and when.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard audit columns recording the most recent modification and its author.

The distinction between the surrogate key and any business key is minimal here: LIST_ID is the only documented unique index, so external systems should select or join on LIST_ID rather than on LIST_NAME.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing all active price element lists for a given supplier, auditing the composition of lists referenced in live negotiations, and extracting list headers for data warehouse loads. A representative query retrieving active lists for a trading partner is:

  • SELECT pel.list_id, pel.list_name, pel.description, pel.trading_partner_id FROM pon.pon_price_element_lists pel WHERE pel.list_status = 'ACTIVE' AND pel.trading_partner_id = :partner_id ORDER BY pel.list_name;

A further common pattern is to join this header table to its child detail table to reconstruct the full list definition, or to reconcile the set of lists referenced by sourcing documents against those available in setup. Reporting uses include supplier cost breakdown analysis, price element usage frequency, and validation that inactive lists are not referenced by open negotiations.

Related Objects

The documented foreign key relationship establishes PON_PRICE_ELEMENTS as the principal dependent child, joined on LIST_ID:

  • PON_PRICE_ELEMENTS — Child detail table holding the individual price elements belonging to each list; joined via PON_PRICE_ELEMENTS.LIST_ID = PON_PRICE_ELEMENT_LISTS.LIST_ID.
  • PON_PRICE_ELEMENT_LISTS_PK — Primary key constraint on LIST_ID, enforcing uniqueness.
  • PON_PRICE_ELEMENT_LISTS_U1 — Unique index on LIST_ID.
  • Trading partner entity (via TRADING_PARTNER_ID) — Resolves supplier identity for supplier-specific lists.
  • Sourcing negotiation and quotation tables in PON — Business consumers that reference list definitions during negotiation setup and response evaluation.

Because the metadata documents only the PON_PRICE_ELEMENTS relationship explicitly, additional dependent objects should be confirmed against the live data dictionary for the specific release being queried.