!--a11y-->
Selection of Initial Commission
Cases 
The commission clerk selects the commission cases that have to be corrected and recalculated.
Selection is made with transaction CACSRCPFRAME or through the menu. The selected commission cases are then registered in RCP as initial commission cases and can be managed with transaction CACSRCPCASE or through the menu.
There are many reasons for having to correct commission cases that have already been posted, and they may differ from customer to customer. Consequently the selection of initial commission cases has to be largely handled by the customer.
In Customizing for Incentive and Commission Management, you have selected package CACSCP in the Commission Application Construction activity.
SAP standard selection criteria for initial commission case
Transaction CACSRCPFRAME displays the selection criteria of the SAP standard delivery.

Graphic: Tool for the logical service
Customer-specific selection criteria for initial commission case
You can specify your customer-specific selection in method SELECT_CUSTMER_CASES of the BAdI CACS_RCP which is called during selection. Alternatively you can use function module <APPl>_RCP_ADD_INITIAL_CASES to register initial commission cases for RCP.

Initial commission cases are registered in RCP when they are saved in table <APPL>_RCP_CASE.
Retroactive case processing is controlled by the tool of the logical service that is assigned to an initial commission case.
By selecting an initial commission case with a specific error background, the type of processing that has to be carried out for this case and its dependent cases is generally clear.
Commission case processing and initial commission cases selection can be set up according to your own requirements. This applies to the resetting of initial commission cases and their dependent commission cases as well as the recalculation of all cases, where they are first reset cases in reverse posting order and then posted again under the new circumstances and in the original order.
To allow maximum flexibility in retroactive case processing, the process is controlled by a tool of the logical service.
By selecting certain methods individually (object type class: CP) and individually assign function modules to methods of the tool of the logical service you can adjust retroactive case processing to your own business requirements.
When the commission clerk registers initial commission cases, he or she specifies the tool to process them.
The logical service RCP_STANDARD is part of the SAP standard delivery. This includes rolling back all commission cases with processing target 2 and then rolling them forward with processing target 9.
The function modules used in this tool (as well as others that you may use for your own requirements) are implemented in the function group <APPL>_RCP_PROCESSING.
You edit the tools of the logical service for RCP in Customizing for Incentive and Commission Management under Tools ® Logical Service: Edit Tools.

If you use the methods of object type class CP of the logical service for RCP, you should be aware that no assignment to an object type is required in Customizing, unlike the other logical services.
The following methods are provided for object type class CP, and a differentiation is made between initial and dependent commission cases.
Methods for object type class CP
Method |
Description |
01 |
Check worklist |
99 |
Standard checks for each commission case of worklist |
02 |
Check dependent commission case |
03 |
Check initial commission case |
04 |
Prepare rollback of dependent commission case |
05 |
Roll back dependent commission case |
06 |
Prepare rollback of initial commission case |
07 |
Roll back initial commission case |
08 |
Roll forward initial commission case |
09 |
Roll forward dependent commission case |
10 |
Complete RCP processing |
11 |
Check commission case (merge) |
12 |
Prepare roll forward of commission case (merge) |
13 |
Roll back commission case (merge) |
14 |
Roll forward commission case (merge) |
15 |
Postprocess rollfoward of initial commission case |
16 |
Postprocess rollforward of dependent commission case |
17 |
Postprocess rollforward of commission case (merge) |
Method 01:
The check of a worklist for initial commission cases verifies the consistence of this newly created worklist. Unlike all other methods, this method is called during creation of the worklist, and not during processing.
Method 99:
The creation and processing of a worklist can take place at different times, in other words the time that elapses between these processes is irrelevant.
Consequently at the start of retroactive case processing, the system has to check if the conditions have changed since worklist creation, for instance if any new commission cases for a business object have been posted that have to be considered by RCP. These checks are run by method 99. They are mandatory and they are run by each tool automatically, without a corresponding method being implemented in the object type class.
The following checks are carried out for each commission case of the worklist.
· Has a higher version of the business object of the commission case been posted since worklist creation?
· Has a subobject of the business object been rebundled since worklist creation?
· Has a remuneration amount in the commission case been corrected since worklist creation?
Methods 02 and 03:
You may implement additional (customer-specific) checks with method 02 (check dependent commission case) and 03 (check initial commission case) (function modules <APPL>_RCP_CHECK_CASE and. <APPL>_RCP_CHECK_INITIAL_CASE).
Methods 04 and 06:
Methods 04 and 06 are designed for preparing the rollback of dependent commission cases and the initial commission case.
In the standard SAP delivery, the documents (called “transfer documents”) that have transferred remuneration of commission cases of the worklist are cancelled before commission case processing (function modules <APPL>_RCP_PREPARE or <APPL>_RCP_PREPARE_INIT).
Methods 05 and 07:
Dependent commission cases and the initial commission case are rolled backwards with methods 05 or 07.
Depending on the function module assigned, this may mean that a commission case with processing target 2 is “reset” or “set to pending”.
The following function modules can be used to roll back commission cases by assigning methods methods 05 or 07 to the function modules.
· <APPL>_RCP_CASE_CANCEL
· <APPL>_RCP_PENDING
· <APPL>_RCP_PENDING_INIT
If you wish to simulate the rollback of the commission cases, you may use the following function modules:
· <APPL>_RCP_PENDING_SIM
· <APPL>_RCP_PENDING_INIT_SIM
Actual processing only then takes place if the preceding simulation produced no errors.
Methods 08 and 09:
If you wish to roll forward dependent commission cases and the initial commission case, you can do so with methods 08 and 09 (function modules <APPL>_RCP_RELEASE or <APPL>_RCP_RELEASE_INIT).
If you choose to run a simulation before processing, you may use function modules <APPL>_RCP_RELEASE_SIM and <APPL>_RCP_RELEASE_INIT_SIM.
Method 10:
You may use method 10 to perform final activities. This method is executed once at the end of worklist processing (and not for each commission case) using function module <APPL>_RCP_FINAL.
With regard to the dependencies between RCP and entitlement and liability transfer (ELT), you can assign method 10 to function modules <APPL_RCP_ELT_INITIATE> to create an ELT worklist for the ELT documents that were reversed in RCP processing with methods 04 or 06 (for ELT, see also Processing of Worklist).
Methods 11 to 14:
If, during worklist creation, a dependent commission case is detected that belongs to a different worklist B that has not yet been processed, worklists A and B are merged under certain circumstances. (See also Worklist Creation).
To do this, both worklists or their initial commission cases must be assigned the same LOS tool. If this is not the case, creation of the current worklist is terminated.
The merging of worklists has the effect that the initial commission case in worklist B becomes a dependent commission case in worklist A. If different processing methods have been defined for initial and dependent commission cases in the tool of the logical service, a conflict situation arises. Methods 11 and 14 of object type class CP are provided to handle this conflict.
These methods are only used to merge worklists. They are assigned to the exact commission cases that have the “initial commission case” indicator but that are not the initial commission case that triggered the creation of the current worklist.
Methods 15 to 17:
Methods 15 to 17 stop the RCP process after an initial or dependent commission case has been rolled forward in order to manually post a document of the type "entitlement and liability transfer" (see also Processing of Worklist for more information on ELT).
In the tool of the standard delivery RCP_STANDARD, a check is made in the assigned function modules <APPL>_RCP_POSTPROCESS or <APPL>_RCP_POSTPROCESS_INIT) as to whether an ELT document has been canceled during the rollback process for the commission case that has just been processed. If such a document is found, processing is stopped and the status of the worklist is set to manual processing required. Once worklist processing has been restarted, it is assumed that the document has been posted and processing of the next commission case continues.
If it is not possible to post the canceled ELT documents manually and a new worklist has to be created at the end of RCP processing to transfer these, you may use function module <APPL>_RCP_ELT_INITIATE (function group <APPL>_RCP_OA) in method 10 (complete RCP processing) to do so.
An initial commission case can have the following statuses:
· Ready to create worklist
· Worklist is currently being created
· Worklist was successfully created
· Creation of worklist was canceled

If worklist creation is canceled if, say, the initial commission case was reversed, you can change the status to Ready to create worklist and restart the creation process after reactivating the commission case.
Worklists can only be created for commission cases with the status Ready to create worklist.
You can select initial commission cases by calling transaction CACSRCPRAME.

The functions that are provided for selecting initial commission cases are documented in program <APPL>_RCP_PENDING_CASES.
The functions for managing initial commission cases are documented in program <APPL>_RCP_CASE_ADMIN.
