Search Results qualifier_attribute100

Overview

OKC_PRICE_ATT_VALUES_HV is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. It belongs to the family of _HV ("history view") objects used throughout Oracle Contracts to expose the current and historical pricing attribute values that Drive contract pricing and qualification logic. The view presents the row-level pricing attribute records stored in the underlying history table, resolving the physical table into a reporting-friendly, APPS-visible object. Because it carries the ROW_ID pseudo-column exposed through PAVB.ROWID, the view preserves row identity while flattening the pricing attribute structure into a single navigable result set.

In both EBS 12.1.1 and 12.2.2 the view is registered as VALID and is used for reporting, extension development, and integration interfaces that need to read contract pricing attribute assignments without directly touching the base history table. The _HV suffix signals that the object is anchored on a history-enabled ("_H") table, so it reflects the effective, versional data used by the pricing engine.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the only referenced base object is OKC_PRICE_ATT_VALUES_H, exposed in the APPS schema as a synonym. All columns in the view are sourced directly from this history table through its alias PAVB; the view performs no joins, unions, or aggregation. The ROWID of the history table row is surfaced as ROW_ID, and the primary key ID is carried through as ID.

The view therefore acts as a pure projection layer over OKC_PRICE_ATT_VALUES_H. Its history-aware lineage means that rows are versioned and are governed by the same effective-dating and version semantics that Oracle Contracts applies to all "_H" tables (typically the interplay of the ID, CHR_ID and CLE_ID columns). Organizations that need committed, version-controlled pricing attribute data should query the view rather than the table to remain insulated from physical changes to the underlying history object.

Key Columns

• ROW_ID — derived from PAVB.ROWID; provides unique row identification for the underlying history record.
• ID — the surrogate primary key of the pricing attribute value record.
• CHR_ID — the change (revision) identifier used by the Contracts history model to track versions of a record.
• CLE_ID — the primary key of the owning entity record (the parent contract line, document, or pricing entity to which the attribute value belongs).
• FLEX_TITLE — identifies the descriptive flexfield context or structure under which the pricing attributes are defined and interpreted.
• PRICING_CONTEXT — the pricing context that determines which attribute set applies (for example, the qualifier context).
• qualifier_attribute2 — Since the user search term "qualifier_attribute2" is a common naming pattern, this value normally resides within the numbered PRICING_ATTRIBUTEn columns or the qualifier attribute columns, keyed by the pricing context; each such column holds the value of one attribute for the given record.
• PRICING_ATTRIBUTE1 … PRICING_ATTRIBUTE38 (and beyond) — the ordered set of pricing attribute value columns. These store the flexible, context-driven attribute values (such as qualifier attributes) that Oracle Advanced Pricing and Contracts evaluate. Attribute names are resolved from the flexfield definition identified by FLEX_TITLE and PRICING_CONTEXT rather than stored explicitly.

Common Use Cases and Queries

Typical uses include reconciling contract pricing attributes, building custom reports on contract qualification values, and feeding pricing attribute data into downstream pricing or order capture interfaces. A frequent requirement is locating a specific qualifier attribute value for a given contract entity:

• Retrieve attribute values for a parent record:
  SELECT id, chr_id, cle_id, flex_title, pricing_context, pricing_attribute1, pricing_attribute2 FROM okc_price_att_values_hv WHERE cle_id = :p_cle_id;
• Locate records by a qualifier attribute value:
  SELECT id, cle_id, pricing_context, pricing_attribute2 FROM okc_price_att_values_hv WHERE pricing_context = :p_context AND pricing_attribute2 = :p_value;
• Trace versioned history for a single logical record:
  SELECT id, chr_id, cle_id FROM okc_price_att_values_hv WHERE id = :p_id ORDER BY chr_id DESC;

Because the view exposes ROW_ID and ID together, it is also suitable for use as a RowSource in custom OAF or Forms-based extensions where row-level navigation and locking must be preserved. When joining to contracts headers or lines, use CLE_ID as the foreign key to the owning entity.