Search Results oks_qualifiers




Overview
Explore in AI Chat

Overview

OKS_QUALIFIERS is a Service Contracts (OKS) transactional table that stores pricing qualifier definitions used by Service Authoring. Qualifiers determine the conditions under which particular prices, price list lines, or pricing rules apply to a service contract or entitlement. The table lives in the OKS schema and is owned by the Service Contracts module, but it is tightly coupled to Oracle Advanced Pricing through foreign keys to QP_QUALIFIER_RULES and QP_LIST_LINES. Each row represents a qualifying predicate or condition — a context, an attribute, an operator, and an expected value — that Advanced Pricing evaluates when resolving a price for a service line.

From a Data Vault modeling perspective, the metadata marks this object as standalone (no downstream child tables were mined through FK analysis). The heuristic classification suggests it behaves primarily as a satellite-like descriptive record keyed by QUALIFIER_ID, with soft links outward to the pricing rule and price list line hubs rather than participating in a dense link structure. This is a suggestion only; the operational design is a standard EBS transactional table with WHO columns, a security group column, and a request/program audit trail.

Key Information Stored

The surrogate primary key is QUALIFIER_ID, enforced by OKS_QUALIFIERS_PK and also carried by the unique index OKS_QUALIFIERS_U1. There is no separate business-key column documented beyond QUALIFIER_ID itself, so integration code should treat QUALIFIER_ID as the stable handle.

Common Use Cases and Queries

The most frequent reporting need is to list active qualifiers for a given price list line or pricing rule. A typical query joins OKS_QUALIFIERS to QP_LIST_LINES on LIST_LINE_ID and filters by ACTIVE_FLAG and effective dates:

SELECT q.QUALIFIER_ID, q.QUALIFIER_CONTEXT, q.QUALIFIER_ATTRIBUTE, q.COMPARISON_OPERATOR_CODE, q.QUALIFIER_ATTR_VALUE FROM OKS.OKS_QUALIFIERS q WHERE q.LIST_LINE_ID = :p_line_id AND q.ACTIVE_FLAG = 'Y' AND SYSDATE BETWEEN NVL(q.START_DATE_ACTIVE, SYSDATE-1) AND NVL(q.END_DATE_ACTIVE, SYSDATE+1) ORDER BY q.QUALIFIER_PRECEDENCE;

Other scenarios include diagnosing why a service price did not resolve (checking EXCLUDER_FLAG and precedence ordering), auditing multi-org visibility through SECURITY_GROUP_ID, reconciling Service Authoring setup against Advanced Pricing rules via QUALIFIER_RULE_ID, and tracking concurrent program loads through REQUEST_ID. Reconciliation extracts commonly compare OKS_QUALIFIERS rows against QP_QUALIFIER_RULES to detect orphaned or duplicated qualifier definitions.

Related Objects

  • QP_QUALIFIER_RULES — joined on OKS_QUALIFIERS.QUALIFIER_RULE_ID = QP_QUALIFIER_RULES.QUALIFIER_RULE_ID; the parent rule owning the qualifier.
  • QP_LIST_LINES — joined on OKS_QUALIFIERS.LIST_LINE_ID = QP_LIST_LINES.LIST_LINE_ID; the price list line the qualifier gates.
  • QP_LIST_HEADERS — reached via QP_LIST_LINES.LIST_HEADER_ID; provides the price list context referenced by LIST_HEADER_ID.
  • FND_SECURITY_GROUPS — joined on OKS_QUALIFIERS.SECURITY_GROUP_ID; enforces data security / org visibility.
  • OKS_CONTRACTS / OKS_HEADERS — service authoring entities whose priced lines depend on qualifier resolution.
  • FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — reachable through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for load run auditing.