Search Results database_link

Overview

The CN_REPOSITORIES_ALL table is a core system parameters table within the Oracle E-Business Suite Incentive Compensation (CN) module for releases 12.1.1 and 12.2.2. It functions as the master repository definition table, centralizing the configuration and connection details for different data repositories used by the Incentive Compensation engine. These repositories are logical containers that hold critical components such as compensation plans, calculation rules, modules, and transactional data. The table supports the multi-org architecture of Oracle EBS, as indicated by the ORG_ID column and its inclusion in the primary key, allowing for separate repository configurations across different operating units.

Key Information Stored

While the provided metadata does not list all columns, the primary and unique keys reveal the table's fundamental structure. The REPOSITORY_ID and ORG_ID columns together form the primary key (CN_REPOSITORIES_PK), uniquely identifying a repository configuration within a specific operating unit. The SCHEMA and DATABASE_LINK columns constitute a unique key (CN_REPOSITORIES_UK1), indicating that the table stores the database schema name and, if applicable, a database link required to connect to the physical database instance hosting the repository data. The foreign key on SET_OF_BOOKS_ID links the repository to the General Ledger's set of books, establishing the accounting context for financial transactions processed through Incentive Compensation.

Common Use Cases and Queries

This table is primarily accessed for system configuration, administration, and diagnostic queries. Common use cases include identifying all configured repositories for an organization, validating database connectivity parameters, and tracing the source of objects or rules within the compensation setup. A typical administrative query would list repository details for a given operating unit. For example:

• SELECT repository_id, schema, database_link, set_of_books_id FROM cn_repositories_all WHERE org_id = :p_org_id;

Another critical use case involves troubleshooting or auditing data lineage by joining to related transactional tables. For instance, to find which repository a specific compensation rule belongs to, one would join CN_RULESETS_ALL_B to CN_REPOSITORIES_ALL on REPOSITORY_ID and ORG_ID.

Related Objects

The CN_REPOSITORIES_ALL table sits at the center of the Incentive Compensation data model, with several key transactional and setup tables referencing it via foreign key relationships. As documented, the following tables reference CN_REPOSITORIES_ALL, establishing dependencies for repository-specific data:

• CN_EVENTS_ALL_B: References via APPLICATION_REPOSITORY_ID and ORG_ID, linking business events to their application repository.
• CN_MODULES_ALL_B: References twice—via REPOSITORY_ID and ORG_ID for the module's primary repository, and via SOURCE_REPOSITORY_ID and ORG_ID for the source repository.
• CN_OBJECTS_ALL: References via REPOSITORY_ID and ORG_ID, tying compensation objects to their repository.
• CN_RULESETS_ALL_B: References via REPOSITORY_ID and ORG_ID, associating calculation rulesets with a repository.

Conversely, CN_REPOSITORIES_ALL itself references another object via its SET_OF_BOOKS_ID foreign key, linking to the General Ledger's accounting setup.