Search Results cn_srp_plan_assigns




Overview
Explore in AI Chat

Overview

The concurrent program SRP_PLAN_ASSIGNS belongs to the Oracle Incentive Compensation (CN) module. Its user-facing name is Salesperson Plan Assignments, and its underlying executable is CN_SRP_PLAN_ASSIGNS. The program is designed to generate assignment information that links salespersons to the compensation plans to which they are subscribed within a given incentive compensation plan cycle. In practice, this output supports administrators and compensation analysts in verifying which sales representatives are associated with specific plans, eligibility groups, and plan components prior to calculation and payout processing.

Within Oracle EBS 12.1.1 and 12.2.2, Incentive Compensation relies on plan assignment data to determine how quota, credit, and commission rules are applied to each salesperson. The Salesperson Plan Assignments report surfaces that mapping so that discrepancies — such as missing assignments, incorrect plan enrollments, or overlapping effective dates — can be identified and corrected before transactional data is processed. Notably, the documented metadata for release 12.2.2 records this concurrent program as Enabled: No, meaning it is shipped but not active by default. Administrators must explicitly enable it before it can be submitted from the Standard Request Submission (SRS) window.

Execution Details

The ETRM metadata documents the following execution characteristics:

  • Execution Method: Oracle Reports
  • Argument Method: Standard
  • Executable: CN_SRP_PLAN_ASSIGNS
  • Execution File Name: cnsrpass
  • Product: CN – Incentive Compensation
  • User-Facing Name: Salesperson Plan Assignments
  • Enabled: No

Because the execution method is Oracle Reports, the program is driven by an .rdf report definition (execution file cnsrpass) rather than a PL/SQL package or host script. Output is therefore produced as a formatted report that can be viewed online, printed, or archived. The Standard argument method indicates that parameters are defined on the concurrent program definition itself and are prompted at submission time, rather than being populated dynamically by a value set or a custom argument method.

How to Run

Users submit the report through the Standard Request Submission (SRS) flow:

  • Navigate to Requests > Run (or the Incentive Compensation responsibility equivalent).
  • Query or select Salesperson Plan Assignments as the request name.
  • Enter submission parameters, which typically include the plan/plan cycle, salesperson or resource, and effective date range identifying the assignments to be reported.
  • Choose the output format and submit the request; review the report through View > Requests once the concurrent manager completes it.

If the program does not appear in the list of available requests, it has not been enabled on the concurrent program definition. A system administrator with Application Developer privileges enables it by setting the Enabled flag to Yes on the Concurrent Programs form, ensuring an appropriate request group and responsibility mapping exists. Parameter value sets should be validated against the active plan cycle, since reporting on a closed or future cycle may return no rows.

Related Objects

The report draws its data from Incentive Compensation plan assignment and hierarchy tables. Commonly associated objects include:

  • CN_SRP_PLAN_ASSIGNS – the executable and the logical name of the underlying database entity for salesperson plan assignments.
  • Incentive Compensation plan and plan cycle definitions, plus salesperson/resource hierarchy tables that establish eligibility.
  • Related concurrent reports in the CN module covering plan components, quota, and compensation results.
  • Standard CN responsibilities and request groups used to expose incentive compensation reports in SRS.

Because the program is a read-only report, it does not populate or modify interface tables. It is used purely for verification and analysis, complementing the calculation and payment concurrent processes within Oracle Incentive Compensation.