Results for “event_factor”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The table CN_TRX_FACTORS_ALL resides in the CN (Incentive Compensation) schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores revenue class transaction factors, which drive how transaction revenue is classified and weighted when Incentive Compensation computes quota attainment, credits, and commission earnings for sales representatives. Each row associates a transaction type and revenue class with a quota, a quota rule, and a numeric event factor, producing the multiplier logic that maps raw transactional data into recognisable incentive events.
From a Data Vault modelling perspective, the mined metadata classifies this object heuristically as a link. The classification reflects the table's structure: it resolves many-to-many style relationships between revenue classes, quota rules, quotas, and transaction types rather than holding a natural business entity of its own. This is a modelling suggestion rather than an enforced constraint.
Key Information Stored
The surrogate primary key is TRX_FACTOR_ID, enforced through the index CN_TRX_FACTORS_PK. A second unique index, CN_TRX_FACTORS_U1 (TRX_FACTOR_ID, ORG_ID), supports multi-organisation access, while CN_TRX_FACTORS_U2 (QUOTA_RULE_ID, TRX_TYPE) forms a business-key candidate that prevents duplicate rule/type combinations.
- TRX_FACTOR_ID — surrogate primary key; the identifier most commonly referenced as "trx_factor_id."
- TRX_TYPE_ID and TRX_TYPE — the transaction type identifier and its descriptive code (FK to IGI_EXP_TRX_TYPE).
- REVENUE_CLASS_ID — foreign key to CN_REVENUE_CLASSES_ALL, defining which revenue class the factor applies to.
- QUOTA_ID — foreign key to CN_QUOTAS_ALL, linking the factor to a specific quota.
- QUOTA_RULE_ID — foreign key to CN_QUOTA_RULES_ALL, linking the factor to a quota rule definition.
- EVENT_FACTOR — the numeric multiplier applied to qualifying transactions.
- ORG_ID and SECURITY_GROUP_ID — multi-org and security group context (FK to FND_SECURITY_GROUPS).
- OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
Common Use Cases and Queries
Typical reporting and diagnostic scenarios include resolving a factor from its identifier, tracing which quotas a revenue class impacts, and auditing event factors configured against transaction types.
- Lookup by surrogate key:
SELECT * FROM cn_trx_factors_all WHERE trx_factor_id = :p_id; - Join revenue class and transaction type:
SELECT tf.trx_factor_id, tf.trx_type, rc.revenue_class_name, tf.event_factor FROM cn_trx_factors_all tf, cn_revenue_classes_all rc WHERE tf.revenue_class_id = rc.revenue_class_id; - Audit factors for a given quota rule via the CN_TRX_FACTORS_U2 business key.
- Multi-org reporting filtered on ORG_ID, then cross-referenced with security group assignments.
Related Objects
- CN_REVENUE_CLASSES_ALL — joined on REVENUE_CLASS_ID; defines revenue class attributes.
- CN_QUOTA_RULES_ALL — joined on QUOTA_RULE_ID; supplies rule-level logic and calculation parameters.
- CN_QUOTAS_ALL — joined on QUOTA_ID; provides the quota definition the factor relates to.
- IGI_EXP_TRX_TYPE — joined on TRX_TYPE_ID; describes the transaction type being factored.
- FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs data visibility.
Together these relationships position CN_TRX_FACTORS_ALL as a central linking table within the Incentive Compensation configuration model, mediating between revenue classification, quota rules, and quota definitions.
-
Revenue class transaction factors
-
Revenue class transaction factors
-
This table is used by the payment module to store the details for each payment worksheet. The records that are created in this table are dependent on the value of the profile Pay by Transaction. When this profile is set to Y(es), the data i
-
This table contains detail posting information, including payee salesrep, posting type, processing date.
-
Stores all transactions created as part of calculation.
-
Stores all transactions created as part of calculation.
-
This table is used by the payment module to store the details for each payment worksheet. The records that are created in this table are dependent on the value of the profile Pay by Transaction. When this profile is set to Y(es), the data i
-
This table contains detail posting information, including payee salesrep, posting type, processing date.
-
VIEW: CN.CN_TRX_FACTORS_ALL# 12.2.2
-
VIEW: CN.CN_TRX_FACTORS_ALL# 12.2.2
-
VIEW: APPS.CN_TRX_FACTORS_V 12.1.1
-
VIEW: APPS.CN_TRX_FACTORS_V 12.2.2
-
TABLE: CN.CN_TRX_FACTORS_ALL 12.1.1
-
TABLE: CN.CN_TRX_FACTORS_ALL 12.2.2