Search Results as_card_rule_qual_values_u1

Overview

The OSM.AS_CARD_RULE_QUAL_VALUES table is a seed-data table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environment, owned by the OSM schema and registered under the FND Design Data application AS (Sales Foundation / Sales Scorecard). It stores the qualifying parameter values that are assembled when a scorecard rule is defined for sales lead and card-based qualification processing. Where the parent qualifier table identifies the name and type of a rule parameter, AS_CARD_RULE_QUAL_VALUES holds the actual value — or value range — bound to a specific rule within a specific scorecard.

Because each row represents the association between a card rule and a seeded qualifier definition, the table functions as a junction or cross-reference structure. Under the heuristic Data Vault classification mined from its foreign key topology, this table is best modelled as a link — it resolves many-to-many relationships between card rules, scorecards, and seeded qualifier definitions, and it should not be treated as a standalone reference or hub entity. Its business content is consequently dependent on the parent rule and scorecard records for full meaning.

Key Information Stored

The 21-column physical schema is organized around an identifier, standard audit columns, foreign keys, and typed value/range fields. The most significant columns are:

• QUAL_VALUE_ID — Surrogate primary key (AS_CARD_RULE_QUAL_VALUES_PK) and the leading column of the unique index AS_CARD_RULE_QUAL_VALUES_U1. In the documented 12.2.2 schema this unique business-key candidate is composed of (QUAL_VALUE_ID, ZD_EDITION_NAME), supporting edition-based redefinition.
• CARD_RULE_ID — Foreign key to AS_SALES_LEAD_CARD_RULES; identifies the card rule to which the qualifier value belongs. Indexed by AS_CARD_RULE_QUAL_VALUES_N1.
• SCORECARD_ID — Foreign key to AS_SALES_LEAD_SCORECARDS, linking the value to its owning scorecard. Indexed by AS_CARD_RULE_QUAL_VALUES_N2.
• SEED_QUAL_ID — Foreign key to the seeded qualifier definition (AS_SALES_LEAD_SEED_QUAL_B / AS_SALES_LEAD_QUALS_B), providing the qualifier name and data type context.
• HIGH_VALUE_NUMBER / LOW_VALUE_NUMBER — The upper and lower bounds when the qualifier's data type is numeric, enabling range-based rule evaluation.
• HIGH_VALUE_CHAR / LOW_VALUE_CHAR — Corresponding bounds for character-based qualifiers (length 60).
• HIGH_VALUE_DATE / LOW_VALUE_DATE — Corresponding bounds for date-typed qualifiers.
• CURRENCY_CODE — Currency context for monetary qualifier values.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating synchronized with the parent scorecard's active window, used to control rule applicability over time.
• SCORE and SECURITY_GROUP_ID — The score contribution and the subscriber security group (FK to FND_SECURITY_GROUPS) governing row-level visibility.

Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and ZD_EDITION_NAME complete the documented column set.

Common Use Cases and Queries

Typical usage centers on auditing, reporting, and troubleshooting scorecard rule configuration. A frequent pattern resolves qualifier values back to their seeded definitions:

• Rule-value extraction: join AS_CARD_RULE_QUAL_VALUES to AS_SALES_LEAD_CARD_RULES on CARD_RULE_ID to list all qualifier values bound to a rule.
• Scorecard rule audit: join to AS_SALES_LEAD_SCORECARDS on SCORECARD_ID to report which qualifiers and ranges apply to a given scorecard's rules.
• Type-aware range reporting: select COALESCE(HIGH_VALUE_NUMBER, HIGH_VALUE_CHAR, TO_CHAR(HIGH_VALUE_DATE)) to present the effective upper bound regardless of data type.
• Effective-dating checks: filter on START_DATE_ACTIVE / END_DATE_ACTIVE to identify currently active qualifier values.
• Duplicate or orphan detection: validate that every QUAL_VALUE_ID is unique and that SEED_QUAL_ID and CARD_RULE_ID resolve to valid parents.

A representative query joining the primary relationships:

SELECT q.QUAL_VALUE_ID, r.CARD_RULE_ID, s.SCORECARD_ID, q.LOW_VALUE_NUMBER, q.HIGH_VALUE_NUMBER, q.SCORE FROM OSM.AS_CARD_RULE_QUAL_VALUES q, OSM.AS_SALES_LEAD_CARD_RULES r, OSM.AS_SALES_LEAD_SCORECARDS s WHERE q.CARD_RULE_ID = r.CARD_RULE_ID AND q.SCORECARD_ID = s.SCORECARD_ID AND q.START_DATE_ACTIVE <= SYSDATE AND (q.END_DATE_ACTIVE IS NULL OR q.END_DATE_ACTIVE >= SYSDATE);

Related Objects

The following tables and definitions are the most significant dependencies, based on the documented foreign keys:

• AS_SALES_LEAD_CARD_RULES — joined via CARD_RULE_ID; the parent rule definition.
• AS_SALES_LEAD_SCORECARDS — joined via SCORECARD_ID; the owning scorecard. (Note: the SCORECARD_ID column appears in the documented 12.2.2 column list.)
• AS_SALES_LEAD_SEED_QUAL_B / AS_SALES_LEAD_QUALS_B — joined via SEED_QUAL_ID; provides qualifier names and data types.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for subscriber-based data security.
• FND_USER — referenced through the standard LAST_UPDATED_BY and CREATED_BY who-columns.
• AS_CARD_RULE_QUAL_VALUES_U1 / _N1 / _N2 — the unique and non-unique indexes that support primary-key enforcement and join performance on QUAL_VALUE_ID, CARD_RULE_ID, and SCORECARD_ID respectively.

Collectively these dependencies confirm the table's role as a seeded, link-style configuration store bridging rules, scorecards, and qualifier definitions within the OSM scorecard subsystem.