Search Results qualifier_attribute1

Overview

OKC_PRICE_ATT_VALUES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKC – Contracts Core product family and exposes the contents of the pricing attribute values table, OKC_PRICE_ATT_VALUES, in a contract pricing context. The view is registered as VALID in the ETRM data model and is used primarily as a read interface for concurrent programs, forms, and external integrations that need to resolve qualifier and pricing attribute values associated with contract pricing structures.

In practice, users searching for "qualifier_attribute1" encounter this object because pricing attributes and qualifier attributes share the flexible attribute framework used by Oracle Contracts and Oracle Advanced Pricing. The view provides a stable, named column surface over the base table, insulating calling code from underlying storage details.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over the synonym OKC_PRICE_ATT_VALUES, which resolves to the base table of the same name. The view text in the documentation shows a straightforward projection of the base table columns, aliased with the PAVB table alias. Columns carried through include ROWID (exposed as ROW_ID), ID, CHR_ID, CLE_ID, FLEX_TITLE, PRICING_CONTEXT, and the full contiguous set of PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE37 and beyond.

Because the view is a direct projection with no joins, filters, or aggregations, it behaves as a synonym-like wrapper. Row counts, data types, and nullability mirror the base table. The ID, CHR_ID, and CLE_ID columns serve as the identifying keys that link pricing attribute value rows to their parent pricing, charge, or contract line entities.

Key Columns

• ROW_ID – The base table ROWID, retained for direct row addressing and performance-sensitive updates.
• ID – The primary identifier of the pricing attribute value row.
• CHR_ID / CLE_ID – Identifiers linking the attribute value set to the associated charge or price list entity.
• FLEX_TITLE – Identifies the descriptive flexfield context or title governing the attribute set.
• PRICING_CONTEXT – The pricing context code that determines which attribute columns are meaningful.
• PRICING_ATTRIBUTE1 … PRICING_ATTRIBUTE37+ – The repeating set of pricing attribute value columns. Qualifier attribute values are commonly stored and retrieved through these columns depending on the configured context.

Common Use Cases and Queries

Typical usage includes retrieving the attribute values for a given pricing context or charge, and correlating qualifier values during debugging of pricing or contract qualification rules. A common query pattern retrieves the key identifiers along with the first pricing attribute columns:

• SELECT id, chr_id, cle_id, flex_title, pricing_context, pricing_attribute1 FROM okc_price_att_values_v WHERE pricing_context = :context;
• SELECT id, pricing_attribute1, pricing_attribute2 FROM okc_price_att_values_v WHERE cle_id = :cle_id;
• SELECT flex_title, COUNT(*) FROM okc_price_att_values_v GROUP BY flex_title;

These queries support reconciliation, troubleshooting of qualifier_attribute1 resolution, and extraction of contract pricing attribute data for downstream reporting. Because the view is unfiltered, appropriate WHERE clauses and indexed columns such as CLE_ID or ID should be used to control performance on large volumes.