Results for “as_sales_lead_card_rules”

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

Overview

AS_SALES_LEAD_CARD_RULES is a configuration table owned by the OSM schema within the AS – Sales Foundation product of Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). It holds the score and description information that defines the individual rules belonging to a sales lead scorecard. In the Oracle Sales Foundation lead-qualification model, a scorecard is a reusable evaluation template composed of one or more card rules; each rule carries the evaluation criteria, an assigned score, and an active date range. This table is therefore the primary definitional object behind lead scoring, driving how leads are prioritized, ranked, and routed to sales representatives.

The relationship metadata classifies this table as satellite-leaning within a heuristic Data Vault model. This suggests the table behaves as a descriptive satellite attached to a parent hub-like entity represented by AS_SALES_LEAD_SCORECARDS, with the SCORECARD_ID foreign key acting as the link to that parent. Treat this classification as a modeling suggestion rather than a documented architectural commitment.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• CARD_RULE_ID — the surrogate primary key, enforced by AS_SALES_LEAD_CARD_RULES_PK and also covered by the unique index AS_SALES_LEAD_CARD_RULES_U1. It is the business-key candidate for uniquely identifying a rule and is referenced by dependent qualification tables.
• SCORECARD_ID — foreign key to AS_SALES_LEAD_SCORECARDS, identifying the parent scorecard to which the rule belongs. This is the principal join column for scorecard-level reporting.
• DESCRIPTION — free-text definition of the rule, typically describing the evaluation criterion or qualification question.
• SCORE — the numeric or weighted value awarded when the rule criterion is satisfied, directly determining the lead's cumulative score.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range controlling when the rule is active within the scorecard. These drive date-effective query logic.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-tenant and organizational data security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS WHO columns capturing the creation and last-modified audit trail.
• LAST_UPDATE_LOGIN — the login identifier associated with the most recent update, supporting concurrent-user auditing.

Common Use Cases and Queries

The most frequent scenario is enumerating the active rules of a scorecard to validate or troubleshoot lead scoring behavior. A typical query joins the rule to its parent scorecard and filters on the active date window:

• SELECT r.CARD_RULE_ID, r.DESCRIPTION, r.SCORE, r.START_DATE_ACTIVE, r.END_DATE_ACTIVE FROM AS_SALES_LEAD_CARD_RULES r WHERE r.SCORECARD_ID = :p_scorecard_id AND SYSDATE BETWEEN NVL(r.START_DATE_ACTIVE, SYSDATE) AND NVL(r.END_DATE_ACTIVE, SYSDATE);
• Totaling the maximum available points per scorecard: SELECT SCORECARD_ID, SUM(SCORE) FROM AS_SALES_LEAD_CARD_RULES GROUP BY SCORECARD_ID;
• Security-scoped extraction using SECURITY_GROUP_ID, particularly in multi-org or shared-services reporting environments.
• Reconciliation of orphaned or misconfigured rules by outer-joining to AS_SALES_LEAD_SCORECARDS and AS_CARD_RULE_QUAL_VALUES to detect rules lacking qualification values or parent scorecards.

Typical reporting uses include scorecard composition analysis, change-history auditing via the WHO columns, and impact analysis when score weights are revised.

Related Objects

• AS_SALES_LEAD_SCORECARDS — parent entity; joined via AS_SALES_LEAD_CARD_RULES.SCORECARD_ID = AS_SALES_LEAD_SCORECARDS.SCORECARD_ID.
• AS_CARD_RULE_QUAL_VALUES — child table holding qualification values for each rule; joined via AS_CARD_RULE_QUAL_VALUES.CARD_RULE_ID = AS_SALES_LEAD_CARD_RULES.CARD_RULE_ID.
• FND_SECURITY_GROUPS — security partition reference; joined via AS_SALES_LEAD_CARD_RULES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• AS_SALES_LEAD_CARD_RULES_PK and AS_SALES_LEAD_CARD_RULES_U1 — the primary key constraint and unique index, both defined on CARD_RULE_ID.
• Lead scoring and qualification interfaces within Sales Foundation that consume scorecard rule definitions during runtime lead evaluation.