Search Results max_multiplier

Overview

PO_PRICE_DIFFERENTIALS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the PO - Purchasing product family. Per the documented description, the view serves as the base view for the Price Differentials form. It presents one row per price differential record, combining transactional attributes from the underlying differential entity with descriptive lookup information used by the form. Because the view joins the differential table to the lookup view, it exposes both the code values and the translated display and description text, allowing the form and downstream reporting to render meaningful labels without additional lookup logic. For consultants and developers searching on the column name max_multiplier, this view is the authoritative exposure point for the MAX_MULTIPLIER column, which is used to cap tolerance or adjustment calculations driven by price differential definitions.

Underlying Base Objects

The documented base objects referenced by this view are:

• PO_PRICE_DIFFERENTIALS (SYNONYM) — the primary source table, aliased as PD, holding the price differential master records.
• PO_PRICE_DIFF_LOOKUPS_V (VIEW) — the lookup source, aliased as PDLK, supplying the display and description text keyed by price differential type.
• FND_GLOBAL (PACKAGE) — referenced in the documented metadata, typically used for session and responsibility context such as org or user identification within the form's runtime environment.

The join between PO_PRICE_DIFFERENTIALS and PO_PRICE_DIFF_LOOKUPS_V is defined on PD.PRICE_TYPE = PDLK.PRICE_DIFFERENTIAL_TYPE. The view text selects PD.ROWID along with the primary key and business columns from the differential table, and PRICE_DIFFERENTIAL_DSP and PRICE_DIFFERENTIAL_DESC from the lookup view. In 12.1.1 and 12.2.2 the table and column definitions are consistent, and the view remains VALID in both releases.

Key Columns

• ROW_ID / ROWID — the physical row identifier of the underlying differential record; used by the form for row-level operations.
• PRICE_DIFFERENTIAL_ID — the surrogate primary key of the price differential.
• PRICE_DIFFERENTIAL_NUM — the user-facing differential number.
• ENTITY_TYPE / ENTITY_ID — identifies the entity the differential applies to.
• PRICE_TYPE — the differential type code, joined to the lookup view.
• PRICE_TYPE_DSP / DESCRIPTION — the translated display label and description sourced from PO_PRICE_DIFF_LOOKUPS_V.
• MULTIPLIER — the base multiplier applied to the differential calculation.
• MIN_MULTIPLIER — the lower bound applied to the multiplier.
• MAX_MULTIPLIER — the upper bound capping the multiplier; this is the column users typically search for when investigating tolerance ceilings.
• ENABLED_FLAG — indicates whether the differential record is active.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and who-columns.

Common Use Cases and Queries

Typical scenarios include diagnosing why a purchase order price deviation was accepted or rejected, verifying the maximum allowed multiplier configured for a given price type, and building reports on active differential definitions. A representative query listing active differentials with their multiplier bounds is:

SELECT price_differential_num, price_type_dsp, multiplier, min_multiplier, max_multiplier, enabled_flag FROM apps.po_price_differentials_v WHERE enabled_flag = 'Y' ORDER BY price_differential_num;

To isolate records with a specific ceiling, filter directly on the column of interest:

SELECT price_differential_id, price_differential_num, price_type_dsp, min_multiplier, max_multiplier FROM apps.po_price_differentials_v WHERE max_multiplier IS NOT NULL;

Because the view encapsulates the lookup join, reports gain human-readable PRICE_TYPE_DSP and DESCRIPTION values without replicating lookup resolution, making it suitable for both form-driven inspection and custom BI Publisher or Discoverer reporting in 12.1.1 and 12.2.2.