Search Results cn_quota_rules_all

Overview

The CN_QUOTA_RULES_ALL table is a core transactional entity within the Oracle E-Business Suite Incentive Compensation module (CN). It serves as a critical junction table that defines the association between a quota (a performance target) and the specific revenue classes to which that quota applies. This mapping is fundamental to the commission calculation engine, as it determines which revenue transactions are eligible to count toward a salesperson's quota attainment. The table is multi-org enabled, as indicated by the "_ALL" suffix, meaning it stores data for multiple operating units with an ORG_ID column for partitioning. Its primary role is to act as a rule set, linking the financial metrics (quotas) defined in CN_QUOTAS_ALL to the transaction categorization (revenue classes) defined in CN_REVENUE_CLASSES_ALL.

Key Information Stored

The table's structure centers on its primary and unique key columns, which enforce the business rule that a specific revenue class can only be assigned once to a given quota. The QUOTA_RULE_ID is the surrogate primary key, uniquely identifying each rule record. The REVENUE_CLASS_ID is a foreign key referencing CN_REVENUE_CLASSES_ALL, identifying the type of revenue (e.g., Product Sales, Service Revenue). The QUOTA_ID is a foreign key referencing CN_QUOTAS_ALL, identifying the specific performance target or goal. While the provided metadata does not list all columns, typical attributes in such a table would include ORG_ID, START_DATE, END_DATE for rule validity, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The primary use case is to retrieve all revenue classes applicable to a quota for validation during transaction processing or for quota attainment reporting. A common query would join CN_QUOTA_RULES_ALL to CN_QUOTAS_ALL and CN_REVENUE_CLASSES_ALL to produce a readable list of quota rules. For example, to find all rules for a specific quota, one might use: SELECT q.name quota_name, rc.name revenue_class_name FROM cn_quota_rules_all qr, cn_quotas_all q, cn_revenue_classes_all rc WHERE qr.quota_id = q.quota_id AND qr.revenue_class_id = rc.revenue_class_id AND q.quota_id = :p_quota_id;. This table is also central to back-end processes that aggregate transaction amounts by revenue class to measure progress against quota targets, directly impacting commission calculations.

Related Objects

The CN_QUOTA_RULES_ALL table is a central hub with numerous foreign key relationships, as documented. It is a child of CN_REVENUE_CLASSES_ALL and CN_QUOTAS_ALL. Crucially, it is a parent table to several key transactional and configuration entities:

• CN_COMMISSION_LINES_ALL: Commission lines can reference a specific QUOTA_RULE_ID, linking the calculated commission to the quota rule that influenced it.
• CN_QUOTA_RULE_UPLIFTS_ALL: Stores uplift factors (multipliers) that are applied based on the quota rule, allowing for variable commission rates.
• CN_SRP_QUOTA_RULES_ALL: Likely extends the quota rule assignment to specific salespeople (SRPs).
• CN_TRX_FACTORS_ALL: May store additional transaction-level adjustment factors tied to the quota rule.

These relationships underscore the table's importance as a foundational rule that propagates throughout the incentive compensation setup.