Search Results cn_revenue_classes_uk1

Overview

The CN_REVENUE_CLASSES_ALL table is a core master data table within the Oracle E-Business Suite Incentive Compensation (CN) module, specifically in versions 12.1.1 and 12.2.2. It serves as the central repository for defining and storing revenue classes. A revenue class is a critical classification used to categorize different types of revenue transactions, such as product sales, service contracts, or software licenses. This classification is fundamental to the incentive compensation engine, as it enables the precise application of compensation rules, quotas, and performance calculations. The table supports multi-organization access control (MOAC) through its "_ALL" suffix, meaning it can store data for multiple operating units, with access typically controlled by the ORG_ID context.

Key Information Stored

The table's structure is designed to uniquely identify and describe revenue classes within a given repository. While the full column list is not detailed in the excerpt, the primary and unique keys provide insight into its critical attributes. The primary key is REVENUE_CLASS_ID, a unique system-generated identifier for each revenue class record. The table also enforces a unique composite key (CN_REVENUE_CLASSES_UK1) on the combination of REPOSITORY_ID and NAME. This indicates that within a specific compensation repository (a logical grouping of plans and rules), each revenue class name must be unique. Typical columns in such a table would include NAME, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and the standard ORG_ID for multi-org partitioning.

Common Use Cases and Queries

This table is primarily referenced for setup, validation, and reporting. Administrators use it to maintain the list of valid revenue classes when configuring compensation plans. Common operational queries include listing all active revenue classes for a specific repository or validating a revenue class ID before applying it in a transaction. For reporting, it is frequently joined to transaction fact tables to group and analyze commission earnings by revenue type. A typical query pattern is:
SELECT rc.name, rc.description, COUNT(ch.commission_header_id)
FROM cn_revenue_classes_all rc, cn_commission_headers_all ch
WHERE rc.revenue_class_id = ch.revenue_class_id
AND rc.repository_id = :p_repo_id
GROUP BY rc.name, rc.description;
This provides a count of commission transactions categorized by revenue class, essential for payout analysis and plan effectiveness reviews.

Related Objects

As documented by its foreign key relationships, CN_REVENUE_CLASSES_ALL is a key parent table referenced by numerous transactional and setup objects in the Incentive Compensation schema. The REVENUE_CLASS_ID column is the primary join point. Key dependent tables include:

• CN_COMMISSION_HEADERS_ALL: Links processed commission transactions to their revenue class.
• CN_QUOTA_RULES_ALL & CN_SRP_QUOTA_RULES_ALL: Associates quota definitions with specific revenue classes.
• CN_RULES_ALL_B: Ties compensation calculation rules to a revenue class.
• CN_SRP_PER_QUOTA_RC_ALL: Stores salesperson-specific quota assignments per revenue class.
• CN_TRX_FACTORS_ALL: Applies adjustment factors to transactions based on revenue class.

These relationships underscore the table's central role in ensuring revenue-based logic is consistently applied across the entire compensation lifecycle, from quota setting and transaction processing to final commission calculation.