Search Results cn_events_all_b




Overview
Explore in AI Chat

Overview

The CN_EVENTS_ALL_B table is a core data object within the Oracle E-Business Suite (EBS) Incentive Compensation (CN) module, specifically in versions 12.1.1 and 12.2.2. It serves as the master repository for defining the various events that drive the Collection and Classification processes. These processes are fundamental to the calculation of commissions, as they govern how raw transaction data is gathered from source systems (Collection) and subsequently categorized and prepared for compensation rule processing (Classification). Each record in this table represents a discrete business event, such as a booking, invoice, or payment, which triggers compensation-related activities. The table is designed to support multi-organization structures through its ORG_ID column, allowing for the definition and management of events across different operating units.

Key Information Stored

The table's primary key is a composite of EVENT_ID and ORG_ID, ensuring uniqueness of events within each operating unit. While the provided metadata does not list all columns, the structure and relationships indicate several critical data points. The EVENT_ID is the unique identifier for the event definition. The ORG_ID links the event to a specific operating unit. The APPLICATION_REPOSITORY_ID is a significant foreign key column that references the CN_REPOSITORIES_ALL table, connecting the event to the specific application repository (source system) from which transaction data is collected. Other columns typically found in such a table would include attributes like the event name, description, status (active/inactive), and technical parameters controlling how the event is processed during data collection.

Common Use Cases and Queries

This table is primarily accessed for configuration, troubleshooting, and reporting on the event-driven architecture of the Incentive Compensation engine. Common scenarios include auditing the list of active events for a given operating unit, identifying the source repository for a specific event, and diagnosing issues in the data collection pipeline. A typical query would join CN_EVENTS_ALL_B to CN_REPOSITORIES_ALL to understand the source system mapping for all events. For example:

  • SELECT e.event_id, e.event_name, r.repository_name FROM cn_events_all_b e, cn_repositories_all r WHERE e.application_repository_id = r.repository_id AND e.org_id = :p_org_id;

Another common pattern involves querying for events used by specific modules or objects, leveraging the foreign key relationships to CN_MODULES_ALL_B and CN_OBJECTS_ALL.

Related Objects

The CN_EVENTS_ALL_B table is central to the Incentive Compensation data model, with documented relationships to several key tables. It references the CN_REPOSITORIES_ALL table via the APPLICATION_REPOSITORY_ID column, defining the data source for the event. More critically, it is referenced as a parent table by two important entities:

  • CN_MODULES_ALL_B: This table references CN_EVENTS_ALL_B using the columns EVENT_ID and ORG_ID. This relationship ties compensation calculation modules to the specific events that trigger them.
  • CN_OBJECTS_ALL: This table also references CN_EVENTS_ALL_B using EVENT_ID and ORG_ID. This links classification objects (like quotas, territories, or performance measures) to the business events that cause them to be evaluated.

These relationships underscore the table's role as a foundational driver, where an event defined in CN_EVENTS_ALL_B can initiate both data collection and the execution of associated compensation rules and object classifications.