Search Results cn_srp_payee_assigns_pkg




Overview
Explore in AI Chat

Overview

CN_SRP_PAYEE_ASSIGNS_PKG is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as an OTHER API in the ETRM repository. It encapsulates the data manipulation logic required to maintain records in the Sales Resource Planning (SRP) payee assignment entity. Specifically, the package provides the insert, update, and delete operations that together form the DML layer for the CN_SRP_PAYEE_ASSIGNS_ALL table.

The package header carries the source header identifier cntspab.pls 120.1, dated 10-JUN-2005, indicating it belongs to the Oracle TeleSales / Sales Resource Planning module family. The original creation comment, dated 10-JUN-99 by Kumar Sivasankaran, documents the purpose as holding all server-side packages used to insert an SRP payee assignment. An SRP payee assignment links a payee to a quota assignment, a quota, and a sales representative, effective over a defined start and end date. This relationship forms the foundation for quota-based compensation calculations within Oracle Sales.

Key Procedures and Functions

The package body exposes three documented DML procedures:

  • INSERT_RECORD — The main insert procedure. It obtains a new primary key by selecting the next value from the CN_SRP_PAYEE_ASSIGNS_S sequence into an IN OUT NOCOPY parameter, then inserts a row into CN_SRP_PAYEE_ASSIGNS_ALL. It populates the assignment identifier, quota assignment identifier, organization identifier, payee, quota, sales representative, the effective start and end dates, and the standard WHO audit columns (last update date, last updated by, creation date, created by, and last update login).
  • UPDATE_RECORD — Documented as the procedure used to update an existing SRP payee assignment. It applies changes to the corresponding row identified by the primary key, preserving the audit trail and following the same WHO column conventions as the insert path.
  • DELETE_RECORD — The procedure relevant to callers searching for delete_record. It removes a payee assignment record from CN_SRP_PAYEE_ASSIGNS_ALL, typically resolving the target row by the SRP payee assignment identifier supplied by the caller.

Together these procedures implement the complete CRUD lifecycle for the payee assignment entity behind a PL/SQL API boundary, allowing UI layers and batch processes to manipulate data without coding direct SQL against the base table.

Tables Accessed

  • CN_SRP_PAYEE_ASSIGNS_ALL — The central transactional table. All three DML procedures operate against this table: INSERT_RECORD adds rows, UPDATE_RECORD modifies rows, and DELETE_RECORD removes rows.
  • CN_SRP_PAYEE_ASSIGNS_S — The Oracle sequence that supplies unique primary key values for new assignments. It is referenced exclusively by INSERT_RECORD to generate the srp_payee_assign_id.
  • DUAL — The standard Oracle dummy table used as the SELECT source when fetching the sequence's NEXTVAL into the OUT parameter.

Usage Notes

This package is a low-level data access API rather than a business rules engine; it does not appear to enforce additional validation logic beyond the audit column population. It is referenced by two other packages in the ETRM metadata, indicating it is called internally by composite SRP APIs rather than directly by end-user forms. Typical invocation paths include Oracle Forms-based SRP maintenance screens, concurrent programs that mass-assign payees to quotas, and custom extensions that need to programmatically create, amend, or delete SRP payee assignments. Because the procedures accept identifier and audit values as parameters, callers are responsible for supplying accurate foreign key values and the correct WHO audit information derived from the FND_GLOBAL context. Deployments on both 12.1.1 and 12.2.2 resolve the CN_SRP_PAYEE_ASSIGNS_ALL and CN_SRP_PAYEE_ASSIGNS_S objects through APPS synonyms.