Search Results oks_qualifiers_v




Overview
Explore in AI Chat

Overview

OKS_QUALIFIERS_V is a valid, APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2, defined within the OKS (Service Contracts) product family. As documented in the ETRM metadata, its purpose is to support Pricing Qualifier setup for Service Authoring. Pricing qualifiers determine which modifiers, price lists, or pricing rules apply to a given service contract or service line, based on contextual attributes such as customer, service, or attribute values. The view exposes the qualifier definitions maintained through the Service Contracts authoring and pricing setup flows.

The view performs a projection over its base table without joins, filters, or transformations, presenting the columns directly. This makes it a convenient, read-only interface for concurrent programs, Oracle Forms LOVs, OAF pages, pricing engine lookups, and custom reports requiring qualifier data. The column CREATED_FROM_RULE_ID reflects the originating rule from which a qualifier row was generated, allowing consumers to trace qualifier lineage — particularly relevant when qualifiers are programmatically derived from pricing rules.

Underlying Base Objects

The documented DBA metadata identifies a single referenced base object: the synonym OKS_QUALIFIERS, which resolves to the underlying table in the APPS schema. The view text selects all listed columns directly from this source alias, using the alias QUAB in the definition. Because the view is a simple one-to-one projection over OKS_QUALIFIERS, it inherits the table's row population, auditing columns, descriptive flexfield segments, and date-effectivity rules. No DBA-level denormalization or aggregation is applied.

Key Columns

Common Use Cases and Queries

Typical usage includes auditing active qualifiers for a price list, tracing qualifiers back to their originating rules, and validating qualifier ranges before pricing runs.

Qualifiers active for a given price list:

SELECT qualifier_id, qualifier_attribute, qualifier_attr_value, comparison_operator_code
FROM oks_qualifiers_v
WHERE list_header_id = :p_list_header_id
AND active_flag = 'Y'
AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Lineage by originating rule:

SELECT qualifier_id, qualifier_rule_id, qualifier_grouping_no, qualifier_precedence
FROM oks_qualifiers_v
WHERE created_from_rule_id = :p_rule_id;

Ordered by precedence for evaluation:

SELECT qualifier_id, qualifier_grouping_no, qualifier_precedence, excluder_flag
FROM oks_qualifiers_v
WHERE qualifier_rule_id = :p_rule_id
ORDER BY qualifier_grouping_no, qualifier_precedence;

Because the view is a plain projection, query predicates are pushed to the base OKS_QUALIFIERS table; filtering on QUALIFIER_ID, LIST_HEADER_ID, or CREATED_FROM_RULE_ID leverages base indexes efficiently.