Search Results update_record

Overview

APPS.CN_SRP_RULE_UPLIFTS_PKG is a server-side PL/SQL package belonging to the Oracle E-Business Suite Trade Management (formerly Oracle Sales Compensation / Incentive Compensation) schema. It encapsulates the create, update, and delete (DML) operations required to maintain Sales Rep Quota Rule Uplift records — the multiplier adjustments applied against quota rules assigned to sales representatives within a quota plan. In the 12.1.1 and 12.2.2 architectures the package resides in the APPS schema and is accessed exclusively through the APPS synonym layer, consistent with EBS's shared-entity data model. The package is classified as an OTHER API in the ETRM metadata, meaning it is a supporting internal API rather than a formally published, externally guaranteed interface. Its source header (cnsrprus.pls version 120.0) indicates a long-standing, stable implementation. The package exists to centralize uplift maintenance logic so that the SRP (Sales Rep Plan) forms, concurrent processes, and dependent packages invoke a single, consistent set of routines rather than issuing direct DML against the underlying tables.

Key Procedures and Functions

• INSERT_RECORD — Creates a new quota rule uplift record. It establishes the association between a Sales Rep Plan assignment, a quota, a quota rule, and an optional quota rule uplift, thereby materializing the uplift linkage used when quota credits are calculated.
• UPDATE_RECORD — Updates the Quota Rule Uplift. The documentation shows two overloaded signatures: one that carries standard EBS audit columns (last update date, last updated by, last update login) alongside payment factor and quota factor, and a second, narrower form that accepts only the quota rule uplift identifier, quota factor, and payment factor. The overload allows the caller either to supply audit context explicitly or to let the package maintain it implicitly. This is the procedure most directly relevant to a search for "update_record."
• DELETE_RECORD — Removes uplift data. As documented, deletion may be invoked from multiple points and cascades across the related SRP and quota entities: the SRP rule uplift, SRP quota rules, SRP quota assigns, quota assigns, quota rule uplifts, quota rules, and quotas. This cascade behavior makes DELETE_RECORD the most far-reaching routine in the package and requires careful call-site management.
• Package body — Additional internal procedures/functions exist within the package (four documented procedures/functions in total across the API surface), but the externally referenced entries are the three DML routines above.

Tables Accessed

The package reads and writes the following underlying tables via APPS synonyms:

• CN_QUOTA_RULE_UPLIFTS_ALL — Primary store of uplift definitions associated with quota rules; inserted, updated, and deleted.
• CN_SRP_RULE_UPLIFTS_ALL and CN_SRP_RULE_UPLIFTS_S — SRP-level uplift records (the "_S" denoting the non-ML shadow/summary table), targeted by the SRP-specific procedures.
• CN_QUOTA_RULES_ALL and CN_SRP_QUOTA_RULES_ALL — Quota rule definitions to which uplifts are attached; read for validation and deleted during cascade.
• CN_SRP_QUOTA_ASSIGNS and CN_SRP_QUOTA_ASSIGNS_ALL — Assignment records linking representatives to quotas; cleaned up during cascade delete.

Usage Notes

CN_SRP_RULE_UPLIFTS_PKG is typically invoked from the Sales Rep Plan / quota configuration forms, from concurrent programs that batch-maintain quota uplifts, and from peer packages within the Trade Management module. ETRM metadata records that it is referenced by three other packages, confirming its role as a dependent service in the SRP call graph. Because it is classified as OTHER rather than a public API, customizations should treat its signatures as internal and verify compatibility before relying on them across patches or upgrades. When updating records, callers should prefer the overload that supplies audit columns so that LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN remain accurate; the abbreviated overload is intended for contexts where audit context is set elsewhere. Direct DML against the underlying quota and uplift tables should be avoided in favor of this package to preserve referential discipline, particularly given the multi-table cascade performed by DELETE_RECORD.