Search Results pricing_attr_value_from




Overview

The APPS.OKC_PRICE_ADJ_ATTRIBS_HV view is a reporting and integration layer within the Oracle E-Business Suite Contracts Core (OKC) module. It exposes the header-level records of price adjustment attributes that drive contract pricing rules. In Oracle Contracts, price adjustments allow pricing terms to be qualified by attribute conditions — for example, applying a discount only when a given pricing context and pricing attribute combination is satisfied. This view presents those attribute definitions together with the descriptive flexfield context (PRICING_CONTEXT), the specific attribute being evaluated, the value range used for comparison, and the operator governing the match.

The view status is VALID and it is owned by the APPS schema, confirming it is a supported, queryable object for customer reporting, BI Publisher data models, and interface development. Because it is a view rather than a table, it carries no independent storage and simply projects the columns of its underlying base object, making it safe for read-only consumption in custom concurrent programs and OAF-based extensions.

Underlying Base Objects

The view is defined over a single base object, identified in the ETRM metadata as OKC_PRICE_ADJ_ATTRIBS_H, referenced through a synonym. The _H suffix in the base table name denotes that this is a history-enabled (or header) table; the _HV suffix on the view is the conventional Oracle EBS naming pattern for a view formed directly over such a table, typically carrying the ROWID through as ROW_ID. The view text is a straightforward SELECT across all columns of the base object, prefixed by the PAAB alias, and it performs no joins, unions, or aggregations. Consequently, every row returned by the view corresponds one-to-one with a row in OKC_PRICE_ADJ_ATTRIBS_H.

Key Columns

Common Use Cases and Queries

The view is typically queried to audit or report the attribute conditions attached to a price adjustment, most often filtered by PAT_ID or by a specific PRICING_CONTEXT. A representative query is:

SELECT pat_id, pricing_context, pricing_attribute,
  comparison_operator, pricing_attr_value_from, pricing_attr_value_to
FROM apps.okc_price_adj_attribs_hv
WHERE pricing_context = :p_context
ORDER BY pat_id, pricing_attribute;

Typical scenarios include reconciling pricing rule configurations during a migration or upgrade, building BI Publisher reports that document the qualification logic behind contract discounts, and troubleshooting why a price adjustment did or did not fire for a given transaction. Joining back to the price adjustment header on PAT_ID allows the attribute condition to be presented alongside its parent adjustment, which is the standard pattern for operational and audit-oriented extracts.