Search Results pon_negotiation_styles




Overview
Explore in AI Chat

Overview

PON_NEGOTIATION_STYLES is a transaction and configuration table in the PON (Sourcing) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores negotiation style related information, functioning as the master definition repository for the behavioral rules that govern how a sourcing negotiation — an RFQ, RFI, or auction — behaves throughout its lifecycle. Each row represents a single negotiation style, a template of enablement flags that determines which functional capabilities are switched on when buyers create sourcing documents.

Within the Oracle Sourcing architecture, negotiation styles act as reusable configuration templates. Administrators define styles such as "Standard RFQ," "Reverse Auction," or "RFI," and each style controls line-level features, price elements, scoring behavior, supplier registration requirements, and bid visibility. Because the style is applied at negotiation creation time, the table directly influences which DFFs, tabs, and controls appear to both buyers and suppliers.

The ETRM metadata provides a heuristic Data Vault classification of standalone. This is a modeling suggestion rather than a physical constraint, and it reflects the fact that PON_NEGOTIATION_STYLES is a reference/configuration entity that other sourcing tables point to rather than one that aggregates transactional facts. In Data Vault terms it behaves most like a hub surrounded by satellite attributes (the numerous enablement flags).

Key Information Stored

The table contains 37 documented columns. The most functionally significant are the enablement flags that define each style's behavior:

Common Use Cases and Queries

The most frequent operational need is listing all active negotiation styles available for selection when creating a sourcing document.

  • Style lookup for a LOV: SELECT style_id, style_name FROM pon_negotiation_styles WHERE status = 'ACTIVE';
  • Identifying auction-capable styles: query rows where PROXY_BIDDING_ENABLED_FLAG = 'Y' or POWER_BIDDING_ENABLED_FLAG = 'Y' to determine which styles support bidding dynamics.
  • Auditing configuration drift: compare enablement flags across styles to verify consistency after a patch or upgrade.
  • Determining which styles are system-seeded: filter on SYSTEM_FLAG = 'Y' to separate Oracle-delivered templates from customer-defined ones.
  • Reporting on evaluation behavior: join to negotiations to determine which in-flight negotiations use styles with TEAM_SCORING_ENABLED_FLAG = 'Y' for evaluation planning.

Because ZD_EDITION_NAME participates in the unique key, queries used during edition-based redefinition maintenance should include it in predicates.

Related Objects

  • HR_ADE_STYLES — referenced by PON_NEGOTIATION_STYLES.STYLE_ID per the documented foreign key; the parent style definition.
  • PON_AUCTIONS (and related negotiation header tables) — each sourcing negotiation records the style applied, joining on STYLE_ID.
  • PON_AUCTION_HEADERS_ALL — header-level negotiation data driven by style configuration.
  • PON_AUCTION_LINES_ALL — line behavior (attributes, lots, tiers) is controlled by the style's line flags.
  • PON_AUCTION_ATTRIBUTES and PON_AUCTION_PRICE_ELEMENTS — populated according to LINE_ATTRIBUTE_ENABLED_FLAG and PRICE_ELEMENT_ENABLED_FLAG.
  • PON_BID_HEADERS / PON_BID_LINES — supplier bid creation is gated by proxy and power bidding flags.
  • PON_NEGOTIATION_TEAM_MEMBERS — relevant where NEG_TEAM_ENABLED_FLAG is set.
  • Sourcing Setup UI (Negotiation Styles page) — the primary front-end that inserts and maintains rows in this table.