Results for “cn_source_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CN_SOURCE_ALL is a table in the CN (Incentive Compensation) product module of Oracle E-Business Suite, residing in the CN schema. It stores dynamically generated source code produced by the Classification and Collection code generators within Incentive Compensation. When administrators define classification rules or collection plans, the application generates executable source text that is persisted in this table, allowing the incentive compensation engine to compile, execute, or reference the generated logic at runtime. The table is therefore a repository for programmatic artifacts rather than transactional business data.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive and payload attributes (notably the generated TEXT) tied to parent entities through its foreign keys, which is characteristic of satellite treatment. This classification is a heuristic modeling suggestion, not a mandate; architects designing a warehouse layer over EBS should evaluate whether CN_SOURCE_ALL behaves as a satellite of CN_OBJECTS_ALL or warrants a link treatment depending on how source records relate to multiple parent objects.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• SOURCE_ID — Surrogate primary key, enforced by CN_SOURCE_PK. Uniquely identifies each generated source record.
• OBJECT_ID — Foreign key to CN_OBJECTS_ALL, linking the generated source to the owning classification or collection object definition.
• LINE_NO — Sequence number ordering the lines of generated code within a single source record, enabling reconstruction of multi-line source text.
• TEXT — The core payload: the dynamically generated code line produced by the Classification and Collection code generators.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting security group partitioning consistent with standard EBS multi-organization security.
• ORG_ID — Operating unit / organization identifier, participating in the business-key candidate index CN_SOURCE_U1.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who last modified the record, when, and through which login session.
• CREATION_DATE, CREATED_BY — Standard audit columns recording initial insertion.

The unique index CN_SOURCE_U1 on (SOURCE_ID, ORG_ID) represents a documented business-key candidate, reinforcing the surrogate-plus-organization pattern common across EBS tables. Note that SOURCE_ID alone is the enforced primary key via CN_SOURCE_PK.

Common Use Cases and Queries

Typical scenarios include inspecting generated classification or collection code, auditing changes to source logic, and diagnosing compilation or runtime failures in Incentive Compensation processing.

To reconstruct the full source text for a given object, aggregate the ordered lines:

• SELECT s.object_id, s.line_no, s.text FROM cn_source_all s WHERE s.object_id = :object_id ORDER BY s.line_no;
• SELECT s.source_id, s.object_id, s.org_id, s.last_update_date, s.last_updated_by FROM cn_source_all s WHERE s.org_id = :org_id;
• Join to CN_OBJECTS_ALL to identify the owning object: SELECT o.object_name, s.text FROM cn_source_all s JOIN cn_objects_all o ON o.object_id = s.object_id ORDER BY s.line_no;

Reporting uses include tracking the volume of generated source per object, identifying stale generated code by LAST_UPDATE_DATE, and reconciling records across security groups via SECURITY_GROUP_ID.

Related Objects

• CN_OBJECTS_ALL — Parent table referenced via CN_SOURCE_ALL.OBJECT_ID, identifying the classification or collection object owning the generated source.
• FND_SECURITY_GROUPS — Referenced via CN_SOURCE_ALL.SECURITY_GROUP_ID, enforcing EBS security group partitioning.
• CN_SOURCE_PK — Primary key constraint on SOURCE_ID.
• CN_SOURCE_U1 — Unique index on (SOURCE_ID, ORG_ID), the documented business-key candidate.

Together these relationships position CN_SOURCE_ALL as a dependent detail table in the Incentive Compensation data model, anchored to object definitions and constrained by standard EBS security and audit conventions.