Search Results cn_commission_headers_all_pk

Overview

The CN_COMMISSION_HEADERS_ALL table is a core transactional data object within the Oracle E-Business Suite Incentive Compensation (CN) module. Its primary function is to store the header-level information for direct credit transactions assigned to a salesperson. This table acts as the parent record for commission calculations, capturing the essential context of a transaction, such as the salesperson, the transaction date, and its associated revenue class. The existence of a record in this table signifies a commissionable event that has been processed by the system, forming the foundation for subsequent commission line calculations, payment processing, and financial posting. Its role is critical for the accurate calculation, tracking, and auditing of sales compensation.

Key Information Stored

The table's structure is designed to capture the key attributes of a commission transaction header. The primary identifier is the COMMISSION_HEADER_ID, which uniquely defines each transaction. A critical foreign key is the REVENUE_CLASS_ID, which links the transaction to a defined revenue class in the CN_REVENUE_CLASSES_ALL table, classifying the type of revenue (e.g., product sale, service). Other significant columns typically include identifiers for the salesperson (often a RESOURCE_ID or PARTY_ID), the transaction date, the source document or order number that triggered the commission, and status flags indicating the processing state of the commission (e.g., calculated, paid). The table also includes standard EBS audit columns like CREATION_DATE and LAST_UPDATE_DATE.

Common Use Cases and Queries

This table is central to numerous operational and analytical processes. Common use cases include auditing commission transaction flows, reconciling commission calculations against source system data, and troubleshooting payment issues. For reporting, it is frequently joined to its child lines table to produce detailed commission statements. A typical query pattern involves filtering by salesperson and date range to retrieve a transaction summary:

• SELECT ch.commission_header_id, ch.transaction_date, ch.source_document_num, rc.name revenue_class, SUM(cl.amount) calculated_amount FROM cn_commission_headers_all ch, cn_revenue_classes_all rc, cn_commission_lines_all cl WHERE ch.revenue_class_id = rc.revenue_class_id AND ch.commission_header_id = cl.commission_header_id AND ch.resource_id = :p_resource_id AND ch.transaction_date BETWEEN :p_start_date AND :p_end_date GROUP BY ch.commission_header_id, ch.transaction_date, ch.source_document_num, rc.name;

Data from this table is also essential for integration with General Ledger via the posting details table.

Related Objects

The CN_COMMISSION_HEADERS_ALL table maintains integral relationships with several other key CN tables, as documented in the ETRM metadata. It is the parent table for CN_COMMISSION_LINES_ALL, which holds the detailed, calculated commission amounts for different quota and rate elements. It is also referenced by CN_POSTING_DETAILS_ALL, which links commission transactions to accounting entries for financial reconciliation. Furthermore, it holds a foreign key relationship to CN_REVENUE_CLASSES_ALL to classify the transaction type. These relationships underscore its position as a central hub in the commission data model, with the primary key constraint CN_COMMISSION_HEADERS_ALL_PK ensuring data integrity for all dependent child records.