Search Results calc_edge_id

Overview

The CN_CALC_EDGES_ALL table is a core data structure within the Oracle E-Business Suite Incentive Compensation module (CN). It functions as a repository for defining and storing the dependencies, or "edges," between different calculation components. Specifically, it models the relationships between formulas, performance measures, and formula inputs. This table is essential for the calculation engine's ability to correctly sequence the evaluation of compensation plans, ensuring that dependent calculations are processed in the correct order. Its role is foundational to the accurate and efficient computation of commissions, bonuses, and other incentive payouts in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to link a parent object to a child object, defining a directional dependency. The central columns that facilitate this are PARENT_ID and CHILD_ID. These columns hold foreign key references to the identifiers of the connected objects, which can be formulas (CN_CALC_FORMULAS_ALL), performance measures (CN_PERF_MEASURES_ALL), or formula inputs (CN_FORMULA_INPUTS_ALL). The unique identifier for each edge record is the CALC_EDGE_ID column, which serves as the table's primary key. While the provided metadata focuses on these relationship columns, typical implementations may also include audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, as well as an ORG_ID column for multi-organization support, consistent with the "_ALL" naming convention.

Common Use Cases and Queries

This table is primarily accessed for dependency analysis and calculation debugging. A common use case is tracing the calculation graph for a specific formula to identify all its prerequisites. For instance, an administrator troubleshooting a commission calculation might query for all dependencies of a particular formula. Conversely, to understand the impact of a change, one might query for all objects that depend on a specific performance measure. The table is also critical for batch calculation engines, which use the edge data to topologically sort calculations.

• Sample Query - Find Dependencies: SELECT child_id, child_object_type FROM cn_calc_edges_all WHERE parent_id = <formula_id>;
• Sample Query - Find Impact: SELECT parent_id, parent_object_type FROM cn_calc_edges_all WHERE child_id = <measure_id>;
• Reporting Use Case: Generating a map of all calculation dependencies within a compensation plan for documentation or validation purposes.

Related Objects

The CN_CALC_EDGES_ALL table has defined foreign key relationships with several key Incentive Compensation tables, as documented in the ETRM metadata. These relationships are bidirectional, allowing the table to reference different object types as either a parent or a child.

• CN_CALC_FORMULAS_ALL: Linked via both PARENT_ID and CHILD_ID columns. An edge record can represent a formula depending on another formula (child) or a formula being a prerequisite for another object (parent).
• CN_PERF_MEASURES_ALL: Linked via both PARENT_ID and CHILD_ID columns. This stores relationships where a performance measure is an input to a formula (child) or where a formula's output populates a measure (parent).
• CN_FORMULA_INPUTS_ALL: Linked via the PARENT_ID column. This relationship models a formula input being a prerequisite (parent) for a calculation object (child).

The primary key constraint CN_CALC_EDGES_PK on CALC_EDGE_ID ensures the uniqueness of each dependency record.