Search Results cn_modules_all_b




Overview
Explore in AI Chat

Overview

The CN_MODULES_ALL_B table is a core repository object within the Oracle E-Business Suite Incentive Compensation module (CN). It serves as the master storage for source modules that are programmatically generated by the system's Classification and Collection code generators. These modules represent executable logic units, such as procedures or packages, that are central to the processing of compensation plans. The table's design supports a multi-organization architecture, as indicated by the ORG_ID column and the "_ALL_" suffix, allowing it to store data for multiple operating units. Its role is foundational to the Incentive Compensation engine's ability to define, execute, and audit complex calculation and attribution rules.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships reveal the critical data points. The table's primary key is a composite of MODULE_ID and ORG_ID, uniquely identifying each module within an organization. The REPOSITORY_ID links the module to its parent source repository in the CN_REPOSITORIES_ALL table. The PARENT_MODULE_ID enables a hierarchical structure, allowing modules to be nested or have dependencies on other modules. The EVENT_ID associates a module with a specific triggering event defined in CN_EVENTS_ALL_B. The SOURCE_REPOSITORY_ID provides a reference to the repository from which the module was sourced, supporting versioning and lineage tracking.

Common Use Cases and Queries

This table is primarily accessed for system administration, troubleshooting, and auditing within the Incentive Compensation setup. Common operational scenarios include analyzing module dependencies before a migration or patch, auditing the modules executed during a specific compensation processing run, and investigating the hierarchy of generated code. A typical query might join to process audit tables to trace execution history:

  • Identifying modules related to a specific event for debugging: SELECT module_id, module_name FROM cn_modules_all_b WHERE event_id = <event_id> AND org_id = <org_id>;
  • Listing all child modules under a parent module: SELECT child.module_id FROM cn_modules_all_b parent, cn_modules_all_b child WHERE child.parent_module_id = parent.module_id AND parent.module_id = <module_id>;
  • Reporting on modules used in active attribute rules: SELECT DISTINCT m.module_id FROM cn_modules_all_b m, cn_attribute_rules_all ar WHERE ar.slice_module_id = m.module_id;

Related Objects

The CN_MODULES_ALL_B table maintains extensive relationships with other core Incentive Compensation tables, as documented by its foreign key constraints.

  • Referenced By This Table (Outgoing Foreign Keys):
    • CN_REPOSITORIES_ALL: Via REPOSITORY_ID and SOURCE_REPOSITORY_ID, linking a module to its repository definitions.
    • CN_MODULES_ALL_B (Self-Reference): Via PARENT_MODULE_ID, establishing module hierarchies.
    • CN_EVENTS_ALL_B: Via EVENT_ID, associating modules with business events.
  • References This Table (Incoming Foreign Keys):