Search Results trx_factor_id

Overview

The CN_TRX_FACTORS_ALL table is a core data object within the Oracle E-Business Suite (EBS) Incentive Compensation (CN) module. It functions as a repository for transaction factors, which are critical multipliers or weights applied to revenue transactions during the compensation calculation process. These factors enable the system to adjust the credited value of a transaction based on specific business rules, such as product type, sales channel, or performance against a quota. The table's role is to store the definitions that link these adjustment factors to specific revenue classes and quota rules, thereby directly influencing the final payout calculations for sales representatives and other compensated personnel. Its "ALL" suffix indicates it is a multi-organization enabled table, storing data partitioned by the operating unit (ORG_ID).

Key Information Stored

The table's primary purpose is to define the relationship between a revenue class, a quota (or quota rule), and a specific numeric factor. While the full column list is not provided in the metadata, the documented foreign keys and primary key reveal its essential structure. The primary key, TRX_FACTOR_ID, uniquely identifies each factor record. The REVENUE_CLASS_ID column links to the CN_REVENUE_CLASSES_ALL table, specifying the type of revenue to which the factor applies. The QUOTA_ID links to the CN_QUOTAS_ALL table, and the QUOTA_RULE_ID links to CN_QUOTA_RULES_ALL, allowing the factor to be associated with either a specific quota or a more granular quota rule. A typical record would store a factor value (likely in a column such as FACTOR or MULTIPLIER) alongside these foreign key references, effective dates, and the ORG_ID.

Common Use Cases and Queries

This table is central to configuring complex compensation plans. A common use case is applying a higher crediting factor (e.g., 1.5x) to strategic product sales within a specific quarter to drive behavior. Administrators would insert or update records in this table to implement such rules. For reporting and validation, common queries involve joining to related tables to list all active factors. A typical SQL pattern is:

• SELECT tf.trx_factor_id, rc.name revenue_class, q.name quota, tf.factor FROM cn_trx_factors_all tf, cn_revenue_classes_all rc, cn_quotas_all q WHERE tf.revenue_class_id = rc.revenue_class_id AND tf.quota_id = q.quota_id AND tf.org_id = :org_id AND SYSDATE BETWEEN tf.start_date AND NVL(tf.end_date, SYSDATE);

Data from this table is also critical for auditing compensation calculations, allowing analysts to trace why a transaction was credited at a particular value.

Related Objects

The CN_TRX_FACTORS_ALL table maintains documented foreign key relationships with several key Incentive Compensation tables, as per the provided metadata:

• CN_REVENUE_CLASSES_ALL: Joined via CN_TRX_FACTORS_ALL.REVENUE_CLASS_ID. This defines the classification of the revenue (e.g., New Business, Renewal) to which the factor is applied.
• CN_QUOTA_RULES_ALL: Joined via CN_TRX_FACTORS_ALL.QUOTA_RULE_ID. This links the factor to a specific rule within a quota, allowing for very granular adjustments.
• CN_QUOTAS_ALL: Joined via CN_TRX_FACTORS_ALL.QUOTA_ID. This links the factor directly to a quota, applying the adjustment broadly to all transactions credited against that quota.

These relationships position CN_TRX_FACTORS_ALL as a pivotal junction table connecting compensation plan components (quotas) with transaction classifications (revenue classes) to determine final credited amounts.