©SAP AG 2005

Retroactive Case Processing

Incentive & Commission ManagementSAP AG

©SAP AG 2005

Retroactive Case Processing: RequirementsRetroactive Case Processing: Initial CasesRetroactive Case Processing: Worklist CreationRetroactive Case Processing: Worklist Processing

© SAP AG 2005

Case ID 4913 BusObjVersion 2SO

Business Requirements

Time

Business Object ABC Business Object XYZ

Case ID 4711SO SO

BusObjVersion 1

Case ID 4812BusObjVersion 1 SO

Case ID 5014BusObjVersion 2 SO SO

Case ID 5115BusObjVersion 3 SO SO

SO

© SAP AG 2005

Steps in RCP Processing

=> Steps in RCP processing:Step 1: Add cases as INITIAL cases for further RCP processingStep 2: Find all DEPENDENT cases for every initial case Step 3: Start RCP processing

What must a commission clerk to do before he or she is able to change commission case 4711?

1. Find all dependent cases for which the calculation results might also change when commission case 4711 is changed.

2. “Cancel” all dependent cases before system allows you to change commission case 4711

3. Change commission case 4711

4. Post again all “cancelled” commission cases under newconditions

© SAP AG 2005

Add Commission Cases to Initial Cases

Identify all commission cases that have to be processed again and add them to the table of initial cases

The reasons for processing commission cases again differ from customer to customer, for example:

All commission cases that have been posted in a certain periodAll commission cases with a special error message in their log

Access interface from the main menu for selection of commission casesand add them as initial cases.

Administration -> Current Administration -> Retroactive Case Processingand then click twice on the NEW icon

Access transaction CACSRCPFRAME

© SAP AG 2005

User Interface - Selection of Cases (1)

User interface allows the selection of cases using the selection criteria: business object, business case and status of commission case

Business Object

Business Case

Status of Case

© SAP AG 2005

User Interface - Selection of Cases (2)

Select commission case that should be added to initial cases

© SAP AG 2005

Worklist Creation for an Initial Case

RCP: this question is addressed in the worklist that is created for every initial case

To be considered by commission clerk:WHICH COMMISSION CASES should be processed IN WHICH WAY and IN WHICH ORDER?

WHICH COMMISSION CASES…?Find all dependent commission cases, e.g. all commission cases that have to be calculated again after changing the initial case

…IN WHICH WAY…?Define in which way the initial case and the dependent cases have to be processed using the standard processes of the ICM, for example cancel all cases, set all cases to pending and post themagain after initial case has been changed

…IN WHICH ORDER?System checks determine the order in which commission cases have to be “cancelled” first and released again (if required)

© SAP AG 2005

Worklist Creation – Which Commission Cases?

WHICH COMMISSION CASES are dependent on the initial case?

1. Business object reference: all commission cases that process the same business object with a later start date of business object version and/or a higher version of the business object

2. Rebundling: all commission cases that rebundlesubobject(s) of the business object of the initial case

3. Remuneration corrections: all commission cases that correct remuneration in the initial case

(CORRTO-/CORRBY relation in remuneration document)

SO

Case ID 4711BusObjVersion 1SO SO

Case ID 5014SO SO

Case ID 5216SO SO

Cases dependent on the initial case can also have dependent cases, for example through rebundling a subobject from a business object of a dependent case

SO

Case ID 4812BusObjVersion 2SO

SOSO SO

SOSO SO

SOSO SO

SOSO SO

© SAP AG 2005

Worklist Creation – In Which Way?

⇒ When identifying the initial case, the commission clerk already knows why it is necessary to process this case again and therefore he or she alreadyknows how to process the initial case and all dependent cases

⇒ i.e. the way the initial case is processed again (and the dependent cases) depends on the individual reason for processing it again, for example all dependent cases only have to be cancelled, all cases have to be set to pending status and then posted again

⇒ Therefore in RCP the way of processing the initial case and the dependent cases is connected with the initial case

⇒ To provide maximum flexibility of processing the initial case and the dependent cases, the processing method can be defined by the customer ina tool for logical services (object type class CP)

Initial Case LOS Tool

IN WHICH WAY should the cases be processed?

© SAP AG 2005

Worklist Creation – LOS Tool Determines Processing

Customer creates his or her own tool by defining the methods thatare used and the function modules for initial and dependent cases

Note: this logical service tool cannot be assigned to an object type,for example a valuation type

several methods are offered for the individual configuration of the RCP process:Method 01: Check Worklist

02: Check Dependent Commission Case03: Check Initial Commission Case04: Roll Back Prep. of Dependent Case05: Roll Back Dependent Comm. Case06: Roll Back Prep. of Initial Comm. Case07: Roll Back Initial Comm. Case08: Roll Forward Initial Comm. Case09: Roll Forward Dependent Comm. Case10: Complete RCP processing 11: Check Comm. Case (Merge)12: Roll Back Prep. of Comm. Case (Merge)13: Roll Back Comm. Case (Merge)14: Roll Forward Comm. Case (Merge)99: Standard checks (obligatory)

© SAP AG 2005

Worklist Creation – LOS Tool RCP_STANDARD

Tool in standard delivery: RCP_STANDARD

© SAP AG 2005

Configuration of RCP

© SAP AG 2005

Worklist Creation – Customizing of Case Status (1)

The status of the commission cases in the worklist determines the success of the function module that operates during worklist processing

Example: for the cancellation of cases the status is irrelevant whereas for setting cases to pending the status should not be “pending due to errors”because it will then not be possible to process this case without errors

Since customers creates their own tools for processing the cases of a worklistwe do not know which function modules they will use, i.e. we do not know the acceptable statuses of the cases

© SAP AG 2005

Worklist Creation – Customizing of Case Status (2)

In Customizing, you configure for each tool and method the permitted statuses of the commission case during worklist creation -> if a case version is found with a status that has not been customized and therefore is not acceptable then the creation of the worklist will be aborted

© SAP AG 2005

Worklist Creation – BAdI Methods

BAdI: ACS_RCP

Method GET_CUSTOMER_CASES: adds commission cases to the worklist that have been found by dependencies other than standard dependencies, i.e. business object reference, rebundling of subobjects, remuneration corrections

Method CHECK_ERROR_CASES: checks which cases in “pending due to errors” (STATUS_VERSION = 0, STATUS_WORK = 3 or 2) should be added to the worklist

It generally makes no sense to consider cases that are “pending due to errors” because processing them will probably cause the same error as before

BUT: in some cases it might be necessary to explicitly add thesecases because the reason for the error has been repaired and allcases can be calculated again

Example: one customer has a list of commission cases with error message CACSVC009 which he/she wants to process again

© SAP AG 2005

User Interface - Starting the Creation of Worklists

Select the initial case to start creation of worklist (transaction CACSRCPCASE)

Worklist no. 381 has been created

© SAP AG 2005

User Interface - Display of Created Worklist

Transaction CACSRCPWORKLIST

© SAP AG 2005

Start Processing Worklist

Start processing a worklist: select the worklists and execute

© SAP AG 2005

Restart Aborted Worklists

If processing of worklists aborts then restart should be possible at the

point of termination

1. Status of worklist is “Manual processing required”

2. Commission clerk has to fix the failed task, i.e. post new version(s) of the commission case

3. Commission clerk has to change the status of the worklist to “New start after manual processing”

4. System finds new active version of commission cases and changes worklist accordingly

5. Worklist can be restarted

©SAP AG 2005

ICM 2005 Overview PartnershipsParallelization Target AgreementsBusiness WarehouseSeveral Small Topics

Object Assignment Framework

Entitlement & Liability Transfer

Portfolio Assignments & Transfer

Valuation by CopyServices

Retroactive Case Processing

Workflow for ICM Cases

©SAP AG 2005

Workflow for ICM Cases: OverviewWorkflow for ICM Cases: Events for WorkflowWorkflow for ICM Cases: Message GroupWorkflow for ICM Cases: Agent Determination

© SAP AG 2005

Motivation and Overview

In the past there have been several requests to connect ICM’s commission case to the SAP workflow system.

The idea is to make treatment of pending commission cases and errors in the commission case EDT run simpler by increasing the level of automation.

Starting with the current release, a basic workflow support is provided which includes:

Triggering events in manual commission case run and in EDT runSimple workflow templates and standard tasks with an example function module for agent determination using ICM relationships in organizational management (assignment of clerk using relation 290)Functionality to make agent determination dependent on commission case data (ID of error messages, commission contractsinvolved etc) by introducing the concept of message groups.

© SAP AG 2005

Functionality

Connection to the workflow system is realized using the new ABAP OO classes CL_CACS_WFCASE and CL_CACS_WFEDT.

The functionality is activated by selecting ICM package CACSWF and generating the commission application.

Afterwards:

The commission case triggers event PENDED of class CL_CACS_WFCASE if the commission case is set to pending when it is saved. Also, context information is transferred into a container.

The commission case EDT run keeps track of how many and which commission cases are set to pending during a run.Afterwards, program CACS_WFCASTRIG can be used to trigger eventsPENDED_EDT and/or REJECTED_EDT of class CL_CACS_WFEDT for all pending or rejected commission cases.

© SAP AG 2005

Workflow Templates and Standard Tasks

Using the events (seven in all), the customer may create standard tasks and workflows according to their needs.

ICM delivers three standard tasks and three (corresponding) workflow templates which may be set up to inform commission clerks about pending or rejected commission cases. You may navigate to commission cases from the work items displayed in the business workplace.

Click

© SAP AG 2005

Message Groups and Agent Determination

The concept of message groups has been introduced in order to enable thecustomer to deliver work items to commision clerks or other agentsdepending on the cause of the problem.

ECACSIB138: Role 801 does not haveentitlement category 1

ECACSIB140: Entitlement does not refer to any triggering participant

MSGGRP 001

ECACSIB039: Inconsistent commission case; Data inconsistent

MSGGRP 002

i) Define message groups and add messages to them (in theIMG):

ii) Assign message groups to processor.

Some possibleselections are:

US SMITHJOHN

C 50001238

In the above example, assume a commission case is set to pending witherror message CACSIB 039. Then all possible agents holding a position to which job C50001238 is assigned will receive a work item.

© SAP AG 2005

By using a rule, customer may use their own function module for agent determination. An example would be to assign work items only to clerks who are responsible for the commission contracts involved in thecommission case.

A sample function module CACS_WF_ROLE_RES_AC is provided. Depending on additional Customizing, this module determines:

The agent responsible for one contract involved (the one withthe highest COMM_SHARE), or

Every agent responsible for any contract involved in thecommission case in question

Using a Rule

© SAP AG 2005

Using the Workflow Templates

In order to use the ICM workflow templates with the new events, you use Business Workflow Event Linkage:

In the Easy Access menu, choose “Type Linkages”

Make sure each of the CACS events has the “Receiver Type” defined as shown in the screenshot.

© SAP AG 2005

Copyright 2005 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.