Results for “score_rule_id”

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

Overview

The view AS_SALES_LEAD_SCORECARD_RULE_V belongs to the AS – Sales Foundation product family in Oracle E-Business Suite, and is part of the Sales Leads scorecard rule infrastructure. It presents a denormalized, reporting-friendly projection of the lead scoring rules defined in the underlying sales lead scorecard tables. In scorecard-driven lead management, individual scoring rules are stored as rows referencing a scorecard and a score rule, while the specific qualification criteria (customer name, contact role, budget status, channel, and so on) are stored in a companion qualification view. AS_SALES_LEAD_SCORECARD_RULE_V joins that rule data with one alias of the qualification view per criterion, so each output row carries the rule's score and description alongside eight discrete qualification attributes. This makes the view the natural read layer for administrators, reporting tools, and integrations that need to display or exchange complete rule definitions without reproducing the multi-alias join logic themselves.

Underlying Base Objects

The view is defined over the base table AS_SALES_LEAD_SCORECARD_RULE (aliased ASLSR) and eight instances of the view AS_SCORECARD_RULES_QUAL_V (aliased ASRQ1 through ASRQ8). The ETRM metadata records that this object is not implemented in the current database, so it may be deployed in some environments but not others, and the base objects are not fully documented in the metadata. Each alias of AS_SCORECARD_RULES_QUAL_V is joined to the rule table with an outer join on SCORE_RULE_ID, further constrained by a specific COLUMN_NAME value: CUSTOMER_NAME, CONTACT_ROLE_CODE, DECISION_TIMEFRAME_CODE, SOURCE_PROMOTION_ID, CHANNEL_CODE, BUDGET_STATUS_CODE, BUDGET_AMOUNT, and VEHICLE_RESPONSE_CODE. Because the joins are outer joins (the (+) operator), rules that do not specify a given criterion still appear in the result with a NULL value for that criterion rather than being dropped.

Key Columns

• SCORECARD_ID — Identifier of the parent scorecard to which the rule belongs.
• SCORE_RULE_ID — Identifier of the scoring rule row; the join key across the rule table and all qualification aliases.
• COMPANY_NAME — Qualification string derived from the CUSTOMER_NAME criterion.
• CONTACT_ROLE — Qualification derived from CONTACT_ROLE_CODE.
• DECISION_TIMEFRAME — Qualification derived from DECISION_TIMEFRAME_CODE.
• SOURCE_PROMOTION — Qualification derived from SOURCE_PROMOTION_ID.
• CHANNEL — Qualification derived from CHANNEL_CODE.
• BUDGET_STATUS — Qualification derived from BUDGET_STATUS_CODE.
• BUDGET_AMOUNT_LOW_RANGE / BUDGET_AMOUNT_HIGH_RANGE — The low and high boundaries of the BUDGET_AMOUNT range criterion.
• VEHICLE_RESPONSE_CODE — Qualification derived from the vehicle response code criterion.
• SCORE — Numeric score assigned when the rule qualifies.
• DESCRIPTION — Free-text description of the rule.

Common Use Cases and Queries

Typical uses include scorecard rule review screens, lead scoring audits, and data migration or integration extracts that must move rule definitions between environments. The most common access pattern filters by scorecard, as shown below.

SELECT SCORECARD_ID,
       SCORE_RULE_ID,
       COMPANY_NAME,
       CONTACT_ROLE,
       BUDGET_STATUS,
       BUDGET_AMOUNT_LOW_RANGE,
       BUDGET_AMOUNT_HIGH_RANGE,
       SCORE,
       DESCRIPTION
  FROM AS_SALES_LEAD_SCORECARD_RULE_V
 WHERE SCORECARD_ID = :p_scorecard_id
 ORDER BY SCORE_RULE_ID;

A second pattern retrieves all rules that include a budget threshold, useful for reviewing monetary qualification logic:

SELECT SCORE_RULE_ID, BUDGET_STATUS,
       BUDGET_AMOUNT_LOW_RANGE, BUDGET_AMOUNT_HIGH_RANGE, SCORE
  FROM AS_SALES_LEAD_SCORECARD_RULE_V
 WHERE BUDGET_AMOUNT_LOW_RANGE IS NOT NULL
    OR BUDGET_AMOUNT_HIGH_RANGE IS NOT NULL;

Because the view is documented as not implemented in the reference database, callers should verify its presence before depending on it in custom code, and should treat SCORE_RULE_ID and SCORECARD_ID as the stable keys for correlation with the underlying scorecard rule table.