Results for “as_scorecard_rules_qual_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_SCORECARD_RULES_QUAL_V is a database view belonging to the AS — Sales Foundation product family in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. The Oracle ETRM (E-Business Suite Technical Reference Manual) metadata explicitly marks this object as obsolete, and the extracted dictionary data records it as Not implemented in this database. In practical terms, the view is a legacy artifact associated with Oracle Sales scorecarding functionality — the subsystem that evaluated sales lead, opportunity, and forecast data against configurable scoring rules to produce qualification and ranking values. Within the EBS reporting stack, such _V views were historically exposed as read-only, joined representations of the underlying scorecard rule tables, intended to simplify custom reports, discoverer workbooks, and integration extract points without requiring customers to hand-code joins across the qualifier and seed lookup tables. Because it is documented as obsolete and unimplemented, the view should not be relied upon in new development; it is catalogued here primarily to assist troubleshooting of legacy SQL, historical upgrade scripts, and older customizations that may still reference the name.

Underlying Base Objects

The ETRM metadata for AS_SCORECARD_RULES_QUAL_V lists no documented referenced base objects for the 12.2.2 dictionary — consistent with its obsolete status. The captured view text, however, indicates the historical definition joined scorecard rule qualifier data with qualification-column lookup values. The fragments reference AS_SCORECARD_RULES_QUALIFIERS (aliased QUAL), AS_CARD_RULE_QUAL_VALUES, AS_SALES_LEAD_QUALCOLS_VL, and AS_SALES_LEAD_SEED_QUAL_VL (aliases COLS), joined on the qualifier and qualified identifiers such as QUALIFIED_ID. Because several fragments appear to be merged from different historical revisions of the view, and because no base objects are formally documented for the shipped 12.2.2 release, no authoritative dependency chain can be asserted. Consultants should treat the underlying tables as internal to the Sales Foundation scoring engine and validate joins against the actual dictionary on site.

Key Columns

The documented column list exposes the scoring-rule attributes and the associated descriptive lookup values:

• SCORE_QUALIFIER_ID — Primary identifier for the scorecard rule qualifier record, used to link back to the governing scorecard rule.
• SCORE_RULE_ID / QUALIFIED_COL_ID / QUALIFIED_ID — Foreign keys tying the qualifier to a scorecard rule and to the qualification column being scored.
• SCORE_FUNC — The scoring function or operator applied to the source value.
• HIGH_RANGE_VALUE / LOW_RANGE_VALUE — Bounds for range-based scoring conditions.
• EQUAL_STRING — Literal match value used for equality-based scoring conditions.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating that governs when the qualifier is active.
• COLUMN_NAME / MEANING — Descriptive attributes sourced from the qualification-column lookup, providing the business-friendly label for the scored field.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns (the captured text shows minor typographical variants such as CREATTION_DATE and COULMN_NAME, which are artifacts of the extraction rather than intended column names).
• ROW_ID — Exposed ROWID pseudo-column retained from the underlying qualifier table.

Common Use Cases and Queries

Given its obsolete classification, the primary use case is diagnostic: confirming whether the object exists in a given instance and tracing legacy customizations. The canonical check is:

• SELECT * FROM all_views WHERE view_name = 'AS_SCORECARD_RULES_QUAL_V'; — verifies presence and owner in the data dictionary.
• SELECT score_qualifier_id, score_rule_id, qualified_col_id, score_func, low_range_value, high_range_value, equal_string FROM as_scorecard_rules_qual_v WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active >= SYSDATE); — reproduces the effective-dated set of scoring qualifiers for a given rule, as legacy scorecard reporting would have done.

Where the view is absent — the expected condition in 12.2.2 — equivalent data must be sourced directly from the current scorecard rule and qualification-column tables. Any integration or report still referencing AS_SCORECARD_RULES_QUAL_V should be re-pointed to the supported base tables during upgrade remediation.