Results for “rate_dsp”

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

Overview

PON_AUCTION_CURRENCY_RATES is a transactional table in the PON (Sourcing) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the currency conversion rate applied between the negotiation (auction) currency and the response (bid) currency for a sourcing negotiation. Because suppliers may respond in a currency different from the one in which the buyer published the negotiation, Oracle Sourcing must retain an explicit conversion rate so that all responses can be normalized, compared, and scored on a common basis. This table is the persistent record of those rates.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is best modeled as a link table. It resolves the many-to-many relationship between auction headers and the response currencies quoted against them, carrying descriptive rate attributes alongside the association. Each row represents a single (auction, bid currency, template list) combination, and it is keyed by a unique constraint named PON_AUCTION_CURRENCY_RATES_UK.

Key Information Stored

The table comprises 17 documented columns. The most significant are:

• AUCTION_HEADER_ID — the negotiation to which the rate belongs; a foreign key to PON_AUCTION_HEADERS_ALL and part of the unique key.
• BID_CURRENCY_CODE — the currency in which the supplier responds; part of the unique key.
• LIST_ID — the sourcing template reference; a foreign key to PON_AUCTION_TEMPLATES and part of the unique key.
• AUCTION_CURRENCY_CODE — the negotiation currency against which conversion occurs.
• RATE and RATE_DSP — the numeric conversion rate and its display-format counterpart.
• RATE_TYPE and RATE_DATE — the Oracle GL rate type and effective date used when the rate was derived.
• NUMBER_PRICE_DECIMALS — the rounding precision applied to converted prices.
• DERIVE_TYPE — indicates how the rate was obtained (for example, derived versus entered).
• SEQUENCE_NUMBER — ordering value for multiple rate rows.
• MODIFIED_FLAG and the standard CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE audit columns.

The surrogate/physical primary key is the unique index PON_AUCTION_CURRENCY_RATES_UK, defined over (BID_CURRENCY_CODE, LIST_ID, AUCTION_HEADER_ID). There is no separate single-column surrogate; the business-key candidate is therefore that same composite. LAST_AMENDMENT_UPDATE supports amendment versioning.

Common Use Cases and Queries

Typical scenarios include auditing currency normalization on a negotiation, reconstructing the rate history used for bid comparison reports, and validating decimal rounding applied to supplier prices. A representative query joining the rate to its negotiation is:

• SELECT h.auction_header_id, h.auction_title, r.bid_currency_code, r.rate, r.rate_type, r.rate_date FROM pon_auction_currency_rates r, pon_auction_headers_all h WHERE r.auction_header_id = h.auction_header_id;
• Joining to PON_AUCTION_TEMPLATES on LIST_ID to report the template associated with each rate row.
• Filtering on MODIFIED_FLAG to isolate rows changed during an amendment.
• Aggregating by RATE_TYPE and RATE_DATE to verify which GL rate types were consumed.

Because the table is small relative to bid volumes, it is well suited to direct SQL reporting rather than requiring dedicated extract programs.

Related Objects

The most significant related objects are:

• PON_AUCTION_HEADERS_ALL — joined on AUCTION_HEADER_ID; the parent negotiation.
• PON_AUCTION_TEMPLATES — joined on LIST_ID; the sourcing template.
• PON_AUCTION_HEADERS and the auction line/bid tables such as PON_BID_HEADERS_ALL, which use the stored rate when normalizing supplier pricing.
• PON_AUCTION_CURRENCY_RATES paired with GL currency-rate views (for example, GL_DAILY_RATES) that supply the underlying conversion values.
• Standard EBS Sourcing reports and Oracle iSupplier/Supplier Portal response pages that read these rows to render converted prices.

Together these relationships confirm the table's role as the currency-conversion bridge within Oracle Sourcing negotiations.