Search Results cn_calc_edges




Overview
Explore in AI Chat

Overview

The APPS.CN_RT_QUOTA_ASGNS_PKG package body is a core component of the Oracle E-Business Suite Incentive Compensation (OIC) module, which falls under the Oracle Trade Management / Channel Revenue Management (ETRM) product family. The package manages records in the CN_RT_QUOTA_ASGNS entity — quota assignments that bind a sales quota to a specific resource, role, or territory within the compensation plan hierarchy. Quota assignments form the basis for crediting and measuring a salesperson's attainment against target, and therefore drive the calculations performed by the compensation engine.

As documented in the ETRM 12.2.2 metadata, the package is classified as OTHER (an internal, non-public API), resides in the APPS schema, and is currently VALID. It is not referenced by any other database object but is itself one of five packages that reference five other packages, indicating it operates as a mid-tier service consumed by higher-level logic while delegating to shared utilities such as CN_COMP_PLANS_PKG and CN_SRP_RATE_ASSIGNS_PKG.

Key Procedures and Functions

The package exposes four documented procedures. Parameter lists are deliberately not enumerated here; the descriptions reflect their functional purpose within the quota-assignment lifecycle.

  • BEGIN_RECORD — Initializes the processing context for a quota-assignment operation. It establishes the working state (identifiers, mode, and validation flags) needed before an insert or node-level record can be processed, and is typically the first call in an assignment transaction.
  • INSERT_RECORD — Performs the primary insertion of a quota-assignment row into the underlying CN_RT_QUOTA_ASGNS / CN_RT_QUOTA_ASGNS_ALL tables, applying defaulting, validation, and formula/edge linkage as required.
  • INSERT_NODE_RECORD — Handles insertion of a quota-assignment record specifically tied to a node in the compensation plan or quota hierarchy, ensuring the assignment is correctly associated with the structural node rather than only a flat resource.
  • DELETE_RECORD — Removes a quota-assignment record, maintaining referential integrity with the associated formula and quota definitions.

Together these procedures implement a controlled create/delete cycle for quota assignments, consistent with Oracle's internal API design pattern (BEGIN / INSERT / DELETE).

Tables Accessed

Based on the documented dependency list, the package reads and writes the following APPS objects and synonyms:

  • CN_RT_QUOTA_ASGNS, CN_RT_QUOTA_ASGNS_ALL, CN_RT_QUOTA_ASGNS_S — the base, multi-org (_ALL), and sequence (_S) objects holding the quota-assignment data that the package maintains.
  • CN_QUOTAS_ALL — the quota definitions to which assignments are linked.
  • CN_RT_FORMULA_ASGNS_ALL, CN_CALC_FORMULAS, CN_FORMULA_INPUTS, and CN_CALC_EDGES — the formula and calculation-graph metadata that govern how quota values are computed. The reference to CN_CALC_EDGES is directly relevant to the user's search term: edges define the dependency links within the calculation graph, and this package consults them when validating or resolving formula-driven quota assignments.
  • DUAL / PLITBLM — standard SYS/PL/SQL utilities used for lightweight queries and bulk processing.

The package also depends on APP_EXCEPTION and FND_MESSAGE for error signaling and user-facing message text.

Usage Notes

Because this package is classified as OTHER rather than a public API, it is not intended for direct invocation by external or customer code. It is typically called from within the Incentive Compensation / Trade Management UI flows (Oracle Forms and OAF pages) when an administrator creates, modifies, or deletes quota assignments, and from concurrent programs that batch-load or regenerate quota assignments across a plan. The dependency data shows it is referenced by five other packages, so its primary consumers are internal ETRM components.

When troubleshooting issues involving CN_CALC_EDGES in the context of quota assignments, the relevant path is the formula-resolution logic reached through INSERT_RECORD and INSERT_NODE_RECORD, where formula assignments and calculation edges are validated before the assignment is persisted. Custom extensions should avoid modifying this package and instead rely on the supported public APIs and concurrent programs that ultimately drive it.