Search Results cn_objects_all




Overview
Explore in AI Chat

Overview

The CN_OBJECTS_ALL table is a core metadata repository within the Oracle E-Business Suite Incentive Compensation (CN) module. It functions as a master catalog or registry for all system-defined and custom objects utilized in the configuration and operation of sales compensation plans. Its primary role is to provide a unified reference for diverse object types—including database tables, columns, sequences, and PL/SQL packages—enabling the flexible and complex rule definitions, calculations, and mappings that drive the compensation engine. The inclusion of ORG_ID in its primary key signifies it is a multi-organization table, storing data specific to individual operating units.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the foreign key relationships reveal the critical attributes stored. The table uniquely identifies each object via OBJECT_ID and ORG_ID. It stores classification attributes that define an object's type and relationships, such as REPOSITORY_ID (linking to a source repository), DIMENSION_ID, and EVENT_ID. Crucially, it maintains hierarchical and referential links between objects through self-referencing foreign keys: TABLE_ID, PACKAGE_SPECIFICATION_ID, SEED_OBJECT_ID, PACKAGE_ID, PRIMARY_KEY_COLUMN_ID, and USER_NAME_COLUMN_ID. These self-references allow the table to model complex dependencies, such as a column belonging to a specific table or a package body linking to its specification.

Common Use Cases and Queries

This table is central to administrative and diagnostic tasks within Incentive Compensation. A common use case involves tracing the lineage or dependencies of a compensation object, such as identifying all columns associated with a specific source table used in a plan. System integrators query this table to understand the metadata model before extending it with custom objects. Support personnel use it to diagnose configuration issues by verifying object definitions and their relationships. A typical query pattern retrieves an object's definition and its immediate parent:

  • SELECT child.OBJECT_ID, child.OBJECT_TYPE, parent.OBJECT_ID AS PARENT_OBJECT_ID FROM CN_OBJECTS_ALL child LEFT JOIN CN_OBJECTS_ALL parent ON child.TABLE_ID = parent.OBJECT_ID AND child.ORG_ID = parent.ORG_ID WHERE child.OBJECT_NAME = '&OBJECT_NAME';

Another critical report lists all objects of a specific type, like packages or sequences, for a given operating unit, which is essential for impact analysis during upgrades or migrations.

Related Objects

The CN_OBJECTS_ALL table sits at the center of a dense relational network within the CN schema. As documented, its key relationships are:

This extensive web of foreign keys underscores its role as the foundational metadata entity for the entire Incentive Compensation module.