Search Results mod_obj_depends_id

Overview

The CN_MOD_OBJ_DEPENDS_ALL table is a core data repository within the Oracle E-Business Suite Incentive Compensation (CN) module. Its primary function is to manage and enforce the dependency relationships between modules and objects. In the context of Oracle EBS 12.1.1 and 12.2.2, this table is critical for maintaining the integrity and structure of compensation plans, rules, and formulas. It ensures that changes to a parent object or module are properly assessed for their impact on dependent components, thereby supporting complex configuration management and preventing orphaned or invalid data. As a multi-org enabled table, it stores dependency records specific to individual operating units, allowing for a shared services deployment model.

Key Information Stored

The table's structure centers on linking identifiers to define dependencies. The primary key, MOD_OBJ_DEPENDS_ID, uniquely identifies each dependency record. The core relationship is defined by three critical foreign key columns: MODULE_ID, which references a specific module in CN_MODULES_ALL_B; OBJECT_ID, which references a dependent object in CN_OBJECTS_ALL; and PARENT_OBJECT_ID, which references the parent or container object, also in CN_OBJECTS_ALL. The ORG_ID column is present on all foreign key relationships, enforcing data security and partitioning by operating unit. This design allows the system to track hierarchical and associative links, such as which calculation formulas (objects) are used within a specific compensation plan (module) and which plan components (parent objects) they rely upon.

Common Use Cases and Queries

A primary use case is impact analysis during maintenance or upgrade activities. Administrators can query this table to identify all objects dependent on a module slated for modification. For example, to find all objects dependent on a specific module ID, a query would be: SELECT object_id FROM cn_mod_obj_depends_all WHERE module_id = <module_id> AND org_id = <org_id>;. Conversely, to understand the module and parent object context for a given object, one might execute: SELECT module_id, parent_object_id FROM cn_mod_obj_depends_all WHERE object_id = <object_id>;. This data is essential for generating dependency reports, validating configurations before deployment, and troubleshooting errors related to missing or invalid object references within the Incentive Compensation engine.

Related Objects

The CN_MOD_OBJ_DEPENDS_ALL table is centrally connected to other key master data tables in the CN schema through its documented foreign key constraints. Its relationships are as follows:

• CN_MODULES_ALL_B: Joined via the MODULE_ID and ORG_ID columns. This table stores definitions of compensation modules.
• CN_OBJECTS_ALL (for OBJECT_ID): Joined via the OBJECT_ID and ORG_ID columns. This table stores the definitions of various objects, such as formulas, rates, and rules, that are the dependents in the relationship.
• CN_OBJECTS_ALL (for PARENT_OBJECT_ID): Joined via the PARENT_OBJECT_ID and ORG_ID columns. This second reference to the objects table identifies the parent or container object for the dependent object.

The primary key constraint CN_MOD_OBJ_DEPENDS_PK ensures the uniqueness of each dependency record, forming the foundation for these relationships.