ICM Incentive and Commission Management SAP ERP Central Component

ICM Incentive and Commission Management
SAP ERP Central Component

Release 6.0
Release Notes
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, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and
OS/400 are registered trademarks of IBM Corporation.
ORACLE is a registered trademark of ORACLE Corporation.
INFORMIX-OnLine for SAP and Informix Dynamic Server
Incorporated.
TM
are registered trademarks of Informix Software
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML 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.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,
SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered
trademarks of their respective companies.
Design: SAP Communications Media
Release-Informationen
Inhaltsverzeichnis
SAP AG
______________________________________________________________
9
9.1
9.2
9.2.1
9.2.2
9.2.3
9.2.4
9.2.5
9.2.6
9.2.7
9.2.8
9.3
9.3.1
9.3.2
9.3.3
9.4
9.4.1
9.5
9.5.1
9.5.2
9.5.3
9.5.4
9.5.5
9.5.6
9.5.7
9.5.8
9.5.9
9.5.10
9.5.11
9.5.12
9.6
9.6.1
9.6.2
9.6.3
9.6.4
9.6.5
ICM Incentive and Commission Management

Terminology (Changed)
ICM-IM Implementation/Customizing
BW Extractors (New)
Database Conversion (Changed)
Conversion of Fixed-Value Domain to E Tables
Structural Changes to IMG of Incentive and
Management
Changes to Menu of Incentive and Commission Management (New)
Remuneration Clearing (Changed)
Customer Enhancements Possible to TCACS_APPLCUST (Changed)
Target Agreements (New)
ICM-MD Master Data
Portfolio Assignment (New)
Partnerships (New)
ICM-PP Periodic Processes
ICM-TA Transaction Data
Entitlement and Liability Transfer (New)
BW Extractors (New)
Database Conversion (Changed)
Dropdown Menus in Commission Case (Changed)
Settlement to Accounts Receivable Accounting (New)
Liability Type Determination and Calculati
Liability
Retroactive Case Processing (RCP) (New)
Remuneration Inquiry (New)
Remuneration Clearing (Changed)
User Exit CACS2010: Change Customer Fields
Document
Valuation Determination Using Copy Service (New)
ICM-TO Tools
Framework for Object Assignment (FOA) (New)
Settlement Using Framework for Parallel Processing (New)
Detach or Enhance SAP Condition Technique (Changed)
User Exit CACS2010: Change Customer Fields
Document
Commission Case Connected to Workflow (New)
1
1
1
1
2
3
3
6
7
8
9
10
10
12
14
16
16
17
17
19
20
21
22
23
23
24
25
27
28
29
30
30
32
32
34
35
______________________________________________________________
SAP AG
iii
SAP-System
______________________________________________________________
9 ICM
Incentive and Commission Management
9.1 Terminology (Changed)

Use
As of SAP ECC 6.0, Incentive & Commission Management (EA-ICM 600), certain terminology changes
have been implemented. Here is an overview of the most import changes and additions.
Old (ERP2004)
Ledger currency
Due date
->
->
or
with "document" character)
Old (ERP2004)
Commission application (technical context)
context)
New (ERP2005) Changed to:

Commission model currency
Due date (time context) or
Due line item (technical context)
Settlement item (business context
New (ERP2005)
Commission model (business
New Terms
Portfolio assignment
Target agreements
Partnership
Remuneration inquiry
Framework for Object Assignment
Framework for Parallel Processing
Entitlement and liability transfer
Retroactive case processing
9.2 ICM-IM
Implementation/Customizing
9.2.1 BW Extractors (New)
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
Use
As of AP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you can
extract all the relevant document data from Incentive and Commission Management (ICM) for
Business Warehouse (BW). You can connect multiple commission applications to BW.
Document extraction is a delta procedure, hence it replaces the function for extracting remuneration
provided in previous releases.
Effects on Existing Data
Note:
To connect an existing commission application to BW, you must first execute the database
conversion.
In ICM, document extraction has no effect on the dataset.
New data store objects are used in BW and the reports must be changed accordingly. The old
remuneration data remains in BW, but this is no longer supported.
Effects on Customizing
-
In Customizing for Incentive and Commission Management, select package CACSBW (Extraction
for SAP BW) under Application Administration -> Commission Application Installation -> Select
Commission Packages.
Modify the extraction structures in Customizing for Incentive and Commission Management under
Application Administration -> Design Adjustment of Commission Application -> Commission
Application Construction.
In Customizing for Incentive and Commission Management, choose Application Administration ->
Commission Application Generation.
Set up the BW system accordingly.
9.2.2 Database Conversion (Changed)

Use
As of SAP ECC 600 Incentive & Commission Management (EA-ICM 600) there are fundamental changes
to the database. You must convert existing data.
To carry out the database conversion, you should start report CACS_FPP_DBC_FRAMEWORK.
You need to carry out the database changes for the following areas:
-
In all ERP systems with commission applications
In all clients with commission applications
In all commission applications
As of the current release certain date and time details (two fields) in the document and commission case
tables are stored on the database in time stamps (one field). The document tables also have a change time
stamp that logs the time of the last change.
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
The new generation templates (for instance CACS00) now only contain time stamps for these date and
time specifications. In existing applications, the Date and Time fields must still exit until the database
conversion is fully implemented.
The database conversion is a prerequisite of BW Extraction . The same applies to Entitlement and
Liability Transfer (ELT).
We highly recommend carrying out the complete database conversion immediately after the upgrade.
Effects on Data Transfer
The database conversion is relevant for the above reasons. You will find a detailed description of how to
carry out the individual steps in SAP Note 833306.
For further information on the upgrade, see the Installation & Upgrade Guide in the Internet under the
address help.sap.com -> Documentation and in the SAP Note 833306.
For more information on the database conversion see the SAP Library under Financials -> Incentive and
Commission Management.
9.2.3 Conversion of Fixed-Value Domain to E Tables

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you can
add values to domains that were previously excluded from enhancements through fixed-value domains by
processing the following tables:
Domain
CACSCALCOBJTYPE
CACSCLAIMTYPEDO
CACS_AGR_TYP
Table
TCACS_COT
TCACS_CLT
TCACS_AGR
Customer Namespace
Z* (data element CHAR 2)
T-Z (data element CHAR 1)
Z* (data element CHAR 2)
In previous releases these values were stored in a fixed-value domain and could not be enhanced by
customers without modification; this is now possible.
9.2.4 Structural Changes to IMG of Incentive and Commission Management

Use
As of SAP ECC 6.0 Incentive & Commission Management (EA-ICM 600) the structure of the
Customizing Implementation Guide (IMG) for Incentive and Commission Management has changed. To
transfer these changes to the IMG project, you must regenerate the IMG project.
Deleted IMG Activities
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
Incentive and Commission Management -> Information Systems -> Link from Commission System to
Business Information Warehouse -> Commission Settings for BW Extractors -> Configure Events for
Determining Organizational Structure
Added IMG Activities

Incentive and Commission Management -> Basic Functions -> Preparation of Posting Processing and
Parallel Processing
Partnerships -> Define Number Ranges for Distribution Ratios
Target Agreements -> Edit Number Range for Target Agreement Run
Retroactive Case Processing (RCP)
-> Define Number Ranges
-> Assign Number Ranges to Process Categories
Incentive and Commission Management -> Basic and Master Data -> Standard Commission Contract ->
Valuation Agreement -> Edit Valuation Types
-> Condition Tables and Valuation Procedures (Copy Services)
-> Edit Conditions
-> Define Formulas
-> Complex Valuation
-> Set Up Complex Valuation
-> Configure Complex Valuation Types
Incentive and Commission Management -> Basic and Master Data -> Standard Commission Contract
-> Target Agreements
-> Target Definition
-> Elementary Targets
-> Complex Targets
-> Calculation Rule
-> Target Assignment
-> Classification
-> Define Classification Categories
-> Define Classification Types
-> Assign Classification Types to Complex Target Types
-> Complex Valuation
-> Make Settings for Valuation Assignment for Target Agreements
-> Configure Complex Valuation Types
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
-> Business Add-Ins (BAdIs)

-> Master Data
-> Calculation Rule
-> Target Evaluation Metastructure
-> Dynamic Values
-> Target Evaluation
Incentive and Commission Management -> Basic and Master -> Standard Commission Contract
-> Partnerships
-> Set Switch for 'Dedicated Commission Contracts'
-> Define Separation Rules for Partnerships
-> Define Characteristics Combinations for Distribution Ratios
for Determining Distribution Ratios
-> Define Methods
-> Configure Partnership Types

Incentive and Commission Management -> Processes
-> Commission Case
-> Construction of Participations

-> Global Settings
-> Define Determination Criteria
-> Determination Combinations /Configure Combination Assignments
-> Define Construction Method
-> Commission Case
-> Retroactive Case Processing (RCP)

-> Status of Commission Case at Worklist Creation
-> BAdI: Add Own Commission Cases to Worklist
-> Entitlement and Liability Transfer
-> Define ELT Rule
-> Set Remuneration Types
-> BAdI: Posting of Transfer Document
-> Connection for Framework for Object Assignment (FOA)
-> Reserve Standard Delivery for Commission Application
-> Determination of ELT Rule
-> Process Determination
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
-> Process Start

Incentive and Commission Management -> Information Systems
-> Remuneration Inquiry
-> Define Structures for Remuneration Inquiry
Incentive and Commission Management
-> Portfolio Assignment
-> Definition and Attributes for Object Types
-> Define Object Types
-> Define Attributes for Object Types
-> Define Segment Types
-> Determine Origin of Business Object and Assignment Object By System
-> Assignments
-> Determine Assignments Between Business Objects and Segments
-> Determine Assignments Between Assignment Objects and Segments
-> User-Defined Enhancements
-> Customizing Includes
Renamed ICM Activities

ERP2004 (EA-ICM 500)
Define Ledger Currency
ERP2005 (EA-ICM 600)
Define Commission Model Currency
9.2.5 Changes to Menu of Incentive and Commission Management (New)

Use
As of SAP ECC 6.0 Incentive & Commission Management (EA-ICM 600) the menu of Incentive and
Commission Management has changed. Here is an overview of the changes and additions:
New Structure
-
Master Data -> Portfolio Assignment
Info Center -> Reports
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
Reassigned Structures
Old
Info Center -> Line Items Account
Transactions
Info Center -> Totals Account
New
Info Center -> Reports ->
Info Center -> Reports -> Total
New Menu Options

Under Master Data -> Portfolio Assignment
-
Segment PFO_SEG
Business Object PFO_GZO
Assignment Object PFO_SZO
Under Info Center

-
My Remuneration CACSACC1N
Under Info Center -> Reports

-
Remuneration Inquiry CACSREMDIS
Under Administration -> Current Administration

-
Edit Target Rules CACSTRU
Retroactive Case Processing CACSRCPWORKLIST
Object Transfer CACS_OA11
Under Administration -> System Administration

-
Parallel Processing FPP_STMT

Deleted Menu Options
Under Commission Document

-
Settlement Schedule CACSSESDIS
9.2.6 Remuneration Clearing (Changed)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) the
functions of remuneration clearing have been modified. This lets you carry out the determination of the
global remuneration clearing agreement with the data of a subobject (previously only possible for
business objects). Additionally, all remuneration lines in each process step are now only processed with
the selection protection rule with priority 9999 (previously with the last selection rule used). The
sequence of processing remuneration clearing rules has also changed:
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
1.
Global rules with indicator before standard rules
2.
Standard rules
3.
Global rules without indicator before standard rules
As of this release the sequence is determined for each rule and no longer for each agreement. It still
applies that only one global agreement and one standard remuneration clearing agreement should be
found.
The functional change has no effect on the database. Only the Customizing tables CACS_STCAGR and
TCACS_OFFRULING are automatically converted.
Effects on System Administration

On system upgrade, the Customizing tables CACS_STCAGR and TCACS_OFFRULING must be
automatically adjusted by program CACS_600_XPRA_REMMOFFS.
Program CACS_600_XPRA_REMMOFFS adapts the Customizing tables CACS_STCAGR and
TCACS_OFFRULING to the new functions without affecting the processing result; in other words
downwards compatibility is ensured for the enhanced functions.
Additionally, a selection protection rule with priority 9999 with the corresponding entries in
TCACS_OFFRULING, TCACS_OFFRULE and TCACS_OFFCLCRULE is generated:
1.
For the global remuneration clearing agreement when the priority indicator (FLG_FIRST) that
determines the processing sequence is set in the agreement.
The program transfers the priority indicator from the remuneration clearing agreement to the
corresponding remuneration clearing rules.
2.
One for each standard remuneration clearing agreement.
To have full use of the new functions, you have the option of changing the priority indicator in the
remuneration clearing rule, which now determines for each global remuneration clearing rule whether this
is processed before or after the standard rules. You can also edit the selection protection rule.
Editing selection protection rule with priority 9999:
You can restrict the number of remuneration lines that are processed in the next step using the selection
protection rule. The priority 9999 plays a key role. This is the key of the remuneration clearing rule. This
determines whether the selection applies to processing. The selection protection rule must contain a
selection rule that influences the selection. The grouping and calculation rules must also be entered,
however they are not considered in processing. Consequently, no logical tools are required for this tool.
See also
For more information on the remuneration clearing agreement see the SAP Library under Financials ->
Incentive and Commission Management -> Application.
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
9.2.7 Customer Enhancements Possible to TCACS_APPLCUST (Changed)

Use
As of SAP ECC 6.0 Incentive & Commission Management (EA-ICM 600) you have the option of adding
your own transactions to table TCACS_APPLCUST. This table contains application-specific
maintenance transactions in which the attributes of parameter APPL are automatically transferred.
This change makes it easier to use the new activities in the SAP Implementation Guide.
Application-specific IMG activities can be automatically supplied by parameter APPL.
See also
For more information see the SAP Library under Financials -> Incentive and Commission Management.
9.2.8 Target Agreements (New)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) Target
Agreements is available.
Many enterprises pay out commissions or incentives on the basis of target agreements that are concluded
with their agencies or employees. The Target Agreements function supports this accepted practice of
sales control in businesses. It was previously not possible to define target agreements in the standard ICM
system. Target agreements were only supported in specific customer projects. Here, some adjustments
had to be made to the ICM processes.
With the new Target Agreements function you can define abstract target types for similar business
partners to map target agreements. For each individual business partner you can link target values, actual
values and correction values to the abstract target types and define individual values for commission
contract, period and subobject. The level of target achievement (LoT) is calculated on the basis of the
individually defined target values, actual values and correction values.
The system uses the LoT to determine the target remuneration and post is as a commission document.
Commission documents created in this way are settled for the business partner, and the remuneration can
be disbursed accordingly.
You must select package CACS26 when you generate the application so that the new Target Agreements
tab is displayed when you process contract master data.
Target agreements are calculated as an independent periodic process similar to the commission case. A
commission case is generated for each contract, complex target type and period.
Additional target agreements as well as target values, actual values and correction values can be
transferred to the contract. ICM can serve as the target administration system for data transfer.
Standard agreements are generally transferred to contract master data using Business Data Toolset (BDT).
______________________________________________________________
SAP AG
SAP-System
______________________________________________________________
You must write your own report program for the transfer of target values, actual values and correction
values. This program retrieves the required data for each contract ID, elementary target type and period.
With this data you call the function module CACS_TGT_VALUES_MAINTAIN_DI in the program.
You start the program after the transfer of contract data for target agreements.
Depending on the way your system is set up, to activate Target Agreements you should execute the
following existing IMG activities in Customizing for Incentive and Commission Management (not always
necessary):
1.
Under Application Administration -> Installation of Commission Application -> Select Commission
Packages select packages CACS26 and CACSTX.
You have the option of also selecting package CACS29 for a sample Customizing of Target
Agreements. If you use portfolio assignment (PFO) to classify your portfolio, you should also select
package PFO.
2.
Copy Cross-Client Customizing from Template.
3.
Under Design Adjustment of Commission Application, execute Commission Application

Construction.
4.
Compare Local Copies of Structures with Originals in Operational Systems.
5.
Execute Commission Application Generation.
6.
In Customizing of Incentive and Commission Management, execute Copy Customizing from

Template (Client-Specific).
7.
Make all the settings under Basic and Master Data -> Standard Commission Contract -> Target
Agreements. The settings for the elementary and complex valuation for target agreements are
particularly important.
8.
Make the settings for the remuneration of complex targets under Basic and Master Data ->
Standard Commission Contract -> Remuneration Agreement.
9.
Make settings for the settlement of remuneration from target agreements.
10. If you use portfolio assignment as the classifying system, then you must also make the settings in
the corresponding IMG activity for Portfolio Assignment.
The following IMG activity is new and must also be carried out:
-
Basic Functions -> Preparation of Posting Processing and Parallel Processing -> Target
Agreements -> Edit Number Range for Target Agreement Run.
See also
For more information on Target Agreements see the SAP Library under Financials -> Incentive and
Commission Management -> Application.
______________________________________________________________
SAP AG
10
SAP-System
______________________________________________________________
9.3 ICM-MD
Master Data
9.3.1 Portfolio Assignment (New)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) portfolio
assignment (PFO) is available. You use portfolio assignment to make assignments between objects in the
external system and commission contracts on the basis of certain assignment criteria. You can define the
assignment criteria to suit the requirements of your business model or sales model.
You can define the following attributes to correspond with your assignment criteria and then make the
assignments:
-
Business object categories (possible assignment criteria: policy, insurance contract) and their
specific attributes to business objects (e.g. specific life insurance no. 65487981, specific "variable"
cell phone contract number: 9873245)
Segment types (possible assignment criteria: geographic, product-related, customer groups) and
their specific attributes to segments (possible assignment criteria: country, district, postal code)
Assignment object types (possible assignment criteria: commission contract for insurance contract,
commission contract for motor insurance) and their specific attributes to assignment objects (e.g. a
specific commission contract).
You can define the dependendies through assignment roles in Customizing.

Portfolio assignment provides the means to manage these objects and their assignments. You can select
and read information from portfolio assignment and evaluate it in subsequent processes, such as
commission for portfolio support, cross-selling, etc.
Portfolio assignment is an independent function that does not rely on a particular application;
consequently it is technically not an element of the commission system or policy management system.
The business objects and assignment objects that are managed in portfolio assignment are mirrored in the
external system. In principal, you could add attributes of the original objects to these mirrored objects,
however we do not recommend this option in order to avoid massive synchronization problems.

The mechanisms for data transfer are provided through external data transfer. The transfer type is 160.
The system administrator must ensure that portfolio assignment is integrated with the relevant external
systems (such as policy management or commission system). This means in particular:
-
Setting up the RFC destinations
Establishing a synchronization mechanism
Taking account of the large data volume that is anticipated on the database
______________________________________________________________
SAP AG
11
SAP-System
______________________________________________________________
Taking account of the effects on performance, depending on the portfolio assignment operations that
are used to manage portfolio
For information on the settings made for portfolio assignment, see the documentation in the
Implementation Guide (IMG) of Incentive and Commission Management under Portfolio Assignment.
See also
For more information on portfolio assignment see the SAP Library under Financials -> Incentive and
9.3.2 Partnerships (New)

Use
Partnerships function is available. This lets you map non-hierarchical relationships between commission
contracts. These are evaluated in commission cases and may be used as the basis for distributing
remuneration resulting from the distribution of valuations. You use the group contract to map
contractual agreements for the whole partnership.
Depending on the characteristics combinations, you may also determine which share each member of a
partnership is entitled to due to the participation of this partnership in a commission case.
It is still possible to link commission cases based on their contractual relationships in a hierarchy that
provides a subfunction of partnerships for a maximum of two contracts.
In the following areas, the new functions are only visible if you have selected package CACS42:
-
You may create partnerships with the Create Contract Bundle transaction. Depending on the
contract bundle type you choose, new views are displayed in the contract bundle where you may
define or edit a group contract, separation rules and distribution ratios.
On the initial screen of the commission case, the following new fields have been added to the
Participation tab page: Group Contract and Person Responsible. These fields have also been
added to the remuneration document and participation document.
Participation of partnerships in the commission case is mapped with the new entitlement object type
5 (representing the direct participant of group) and entitlement category 6 (partnership/group),
which appears accordingly in the documents.
In the Partnerships function, the grouping of commission contracts into partnerships is achieved through
the concept of the contract bundle that has been available in past releases. The contract bundle function
has been enhanced in this release.
The remuneration of partnerships is integrated in the commission case. Here, partnerships may:
-
Act in their own right
Act together with the already known direct participants
Be omitted completely
______________________________________________________________
SAP AG
12
SAP-System
______________________________________________________________
Depending on a setting that is valid throughout the whole application (Dedicated Commission Contracts
switch), partnerships can be registered for the commission case either by specifying a commission case of
a member at the case interface or they must be specified together with the group contract to identify the
partnership. Similar to the direct participants, the concept of indirect participants is supported for
partnerships. However, the effect and the calculation mechanisms are slightly different.
The way in which certain commission cases are treated at the case interface differs slightly from previous
releases after you have installed partnerships. The system checks whether the contracts are registered as
so-called "own business" or in the framework of a partnership. In the latter case, the new function applies
and, instead of the direct participants being passed on at the case interface the entire partnership is
considered to participate in the case. The partnership actually represents a separate entitlement group with
the (new) entitlement category 6 (partnership/group). The determination of the remuneration of indirect
participants of the members of a partnership differs from the determination of the remuneration of direct
participants.
Apart from the new fields in the commission case and documents, there is a new field External
Identification of Commission Contract (CTRTBU_ID_EXT) in the commission contract.
You will find the new Partnerships function in Customizing for Incentive and Commission Management
under Basic Functions -> Partnerships. You access the processing transactions for Partnerships in the
SAP Easy Access menu under Accounting -> Incentive and Commission Management -> Master Data ->
Contract Bundle and in the main menu of Incentive and Commission Management (transaction CACS)
under Master Data -> Contract Bundle.

You should take account of the new fields in the interfaces mentioned above. These fields have to be
filled if you intend to use partnerships.
To execute the IMG activities of partnerships. you must first select the Partnerships package (CACS42).
Depending on the current status of your system, to activate Partnerships you may have to execute the
following IMG activities again in Customizing for Incentive and Commission Management not always
necessary:
1.
Application Administration -> Installation of Commission Application -> Select Commission

Packages
2.
Copy Cross-Client Customizing from Template
3.
Design Adjustment of Commission Application -> Construction of Commission Application
4.
Compare Local Copies of Structures with Originals in Operational Systems
5.
Commission Application Generation
6.
Copy Customizing from Template (Client-Specific)
7.
Organizational Structure -> Evaluation Paths of Indirect Participants and Commission Clerks etc.
Edit Settings for Indirect Participants (when you execute Copy Customizing from Template
(Client-Specific), entries are imported here that you should check)
______________________________________________________________
SAP AG
13
SAP-System
______________________________________________________________
8.
Basic and Master Data -> Standard Commission Contract -> Define Commission Types
9.
Assign Commission Contract Types to Partner Types
10. Assign Commission Contract Types to Activity Filters

11. Carry out all the activities under Participation Agreement to define roles for partnerships and
provide a standard participation agreement for standard contracts of the group contract type.
12. Carry out the required activities to create standard agreements for standard contracts of group
contracts as well as for standard contracts for members of partnerships.
13. Create Standard Contracts and Assign Standard Agreements
14. Basic and Master Data -> Contract Bundle -> Edit Contract Bundle Types
15. You may also have to carry out further activities under Contract Bundle to configure bundle types
that are partnerships.
You must also carry out the following new IMG activities:
1.
Basic Functions -> Preparation of Posting Processing and Parallel Processing -> Partnerships ->
Define Number Ranges for Distribution Ratios
2.
All activities under Commission Contract -> Partnerships
See also
For more information on Partnerships see the SAP Library under Financials -> Incentive and

Use
______________________________________________________________
SAP AG
14
SAP-System
______________________________________________________________
necessary):
1.
package PFO.
2.
3.

Construction.
4.
5.
6.

7.
8.
9.
-
______________________________________________________________
SAP AG
15
SAP-System
______________________________________________________________
See also
9.4 ICM-PP
Periodic Processes

Use
______________________________________________________________
SAP AG
16
SAP-System
______________________________________________________________
necessary):
1.
package PFO.
2.
3.

Construction.
4.
5.
6.

7.
8.
9.
-
See also
9.5 ICM-TA
Transaction Data
9.5.1 Entitlement and Liability Transfer (New)

Use
functions of entitlement and liability transfer (ELT) are available. ELT enables you to transfer
entitlements and liability between commission contracts using Framework for Object Assignment (FOA).
The services of FOA provide the following functions:
______________________________________________________________
SAP AG
17
SAP-System
______________________________________________________________
Managing worklists for entitlement and liability transfer
Processing worklists in a dialog and as background jobs for carrying out or reversing entitlement
and liability transfer
Automated transfer in assignment processes with workflow support for processing release, dialog
checks of worklists and error handling
You can adjust the standard delivery of ELT to your own requirements without modifications by adapting
the configuration of FOA.
FOA provides user interfaces for managing worklists for ELT and assignment processes. A number of
parameters are provided for you to carry out ELT in the required way:
-
Transfer share as a percentage
Instruction to recalculate before transfer
Type of remuneration scheduling after transfer
Type of payout
Negotiated payoff
Discount interest
Enterprise commission contract
To access ELT, in the SAP Easy Access menu choose Accounting -> Incentive and Commission
Management -> Administration -> Current Administration -> Object Transfer. You edit worklists for
object assignment here. You can create a worklist for ELT by selecting a definition for worklist 0ELT,
which is part of the standard delivery.
You can access all the FOA functions for worklists and assignment processes through the interfaces
provided using the menu entries and pushbuttons.
For the purposes of ELT, the standard delivery of the current release provides the connection between the
commission contract and FOA. If a commission contract is terminated effectively, the system can
automatically start an assignment process if a preconfigured termination reason is specified (see: Effects
on System Administration).
In ELT, individually selected remuneration entitlements of a commission contract can be transferred on
an ad hoc basis to one or more other commission contract. You can also undertake mass assignments
based on assignment rules. This may be necessary, for instance, if an agent leaves the organization and
his or her entire entitlement has to be transferred to new recipients on the basis of predefined rules (that
may be based on legal requirements). You can use BAdI implementations to define your own rules for
worklist creation.
In ELT, transfer documents are written that have to be unloaded by the archiving tools of Incentive and
FOA provides deletion programs to clean up its own transactional dataset. This applies to content of
database tables that holds the worklists or assignment processes for ELT.
In the standard delivery of ELT, the attributes of the commission contract of the commission recipient
______________________________________________________________
SAP AG
18
SAP-System
______________________________________________________________
leaving the organization decide the rules on the basis of which the worklist for ELT is created. It must be
ensured that the required attributes of the commission contract are retained.
SAP Business Workflow is used to support the assignment processes for automated ELT. It is the task of
the system administrator to configure the runtime environment for the workflow and to provide
operational support.
If you wish the assignment processes of ELT to start automatically on the effective termination of
commission contracts, you need to schedule program CACS_OATRG1EXEC. There is a corresponding
IMG activity for this in the settings of ELT.
You make settings for ELT in Customizing for Incentive and Commission Management under Processes
-> Entitlement and Liability Transfer. Here you will find all the settings and the documentation
describing how to configure the standard delivery of ELT. Since ELT uses the services of FOA, the
settings for the FOA connection are also located here.
You make the settings for FOA itself in Customizing for Incentive and Commission Management under
Tools -> Framework for Object Assignment. Since ELT uses FOA, the configuration of FOA is part of the
standard delivery. You can change the configuration accordingly to adjust the functions of ELT. You will
find suggested settings in the Implementation Guide (IMG) for Incentive and Commission Management
in the documentation of the individual IGM activities for ELT.
You can use elements of organizational management (such as positions and organizational units) to
assign processors to certain steps in the assignment process. To edit organizational management, in the
SAP Easy Access menu choose Incentive and Commission Management -> Master Data ->
Organizational Plan.
To improve the performance of ELT, you can activate the index 'CAS' on database table <Name of
application>_DOCRE, if necessary. An inactive version of the index is delivered to minimize the effects
of the system upgrade.
Before you decide to activate the index or not, you should use the Performance Trace (System -> Utilities
-> Performance Trace) to check if the database access on table <Name of application>_DOCRE is the
major cause of the unsatisfactory performance during posting of transfer documents. Since the new index
creates additional runtime for the posting of remuneration lines, you should not just activate it unless you
are absolutely sure.
See also
For more information on ELT and FOA see the system documentation, for instance by pressing the info
button on the initial screen of transactions CACS_OA01 and CACS_OA11.
For more information on ELT, see the SAP Library under Financials -> Incentive and Commission
Management -> Application.
9.5.2 BW Extractors (New)

Use
As of AP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you can
______________________________________________________________
SAP AG
19
SAP-System
______________________________________________________________
extract all the relevant document data from Incentive and Commission Management (ICM) for
Business Warehouse (BW). You can connect multiple commission applications to BW.
Document extraction is a delta procedure, hence it replaces the function for extracting remuneration
provided in previous releases.
Note:
To connect an existing commission application to BW, you must first execute the database
conversion.
In ICM, document extraction has no effect on the dataset.
New data store objects are used in BW and the reports must be changed accordingly. The old
remuneration data remains in BW, but this is no longer supported.
-
In Customizing for Incentive and Commission Management, select package CACSBW (Extraction
for SAP BW) under Application Administration -> Commission Application Installation -> Select
Commission Packages.
Modify the extraction structures in Customizing for Incentive and Commission Management under
Application Administration -> Design Adjustment of Commission Application -> Commission
Application Construction.
In Customizing for Incentive and Commission Management, choose Application Administration ->
Commission Application Generation.
Set up the BW system accordingly.
9.5.3 Database Conversion (Changed)

Use
As of SAP ECC 600 Incentive & Commission Management (EA-ICM 600) there are fundamental changes
to the database. You must convert existing data.
To carry out the database conversion, you should start report CACS_FPP_DBC_FRAMEWORK.
You need to carry out the database changes for the following areas:
-
In all ERP systems with commission applications
In all clients with commission applications
In all commission applications
As of the current release certain date and time details (two fields) in the document and commission case
tables are stored on the database in time stamps (one field). The document tables also have a change time
stamp that logs the time of the last change.
The new generation templates (for instance CACS00) now only contain time stamps for these date and
time specifications. In existing applications, the Date and Time fields must still exit until the database
______________________________________________________________
SAP AG
20
SAP-System
______________________________________________________________
conversion is fully implemented.

The database conversion is a prerequisite of BW Extraction . The same applies to Entitlement and
Liability Transfer (ELT).
We highly recommend carrying out the complete database conversion immediately after the upgrade.
The database conversion is relevant for the above reasons. You will find a detailed description of how to
carry out the individual steps in SAP Note 833306.
For further information on the upgrade, see the Installation & Upgrade Guide in the Internet under the
address help.sap.com -> Documentation and in the SAP Note 833306.
For more information on the database conversion see the SAP Library under Financials -> Incentive and
9.5.4 Dropdown Menus in Commission Case (Changed)

Use
following input fields in the commission case were changed from F4 help to dropdown menus:
Commission Case Selection Screen
-
Business Object
Business Transaction
After Selecting Header Tab Page

-
Processing Target
Business Object
Remunerating Business Transaction
Triggering Business Transaction
Group Box Template for Participation

-
Business Object
Remunerating Business Transaction
Depending on your selection, the permitted objects are now displayed according to the Customizing
settings that were implemented.
The individual messages of class CACSIB and the calling function modules with which this data is
retrieved and formatted were changed.
The grouped conversion exit BOBJ is not affected by these changes.
We recommend selecting the business object and the business transaction on the initial screen and not on
the Header tab page so that the subsequent permitted selection options are made automatically.
______________________________________________________________
SAP AG
21
SAP-System
______________________________________________________________

In the primary entry (commission case header), the above input fields are only available in the dropdown
menu with their descriptions.
However you have the option of displaying the technical ID with the descriptions in the input field.
1.
To do so, in the Commission Case screen click on the symbol with the quick link Customizing of
Local Layout.
2.
Choose Options and then the Expert tab page in the Controls group box and set the indicator
Show Keys in All Dropdown Lists.
3.
Save your entries.
The technical ID is displayed in the input field, along with the description.
See also
9.5.5 Settlement to Accounts Receivable Accounting (New)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600)
settlement to Accounts Receivable Accounting is possible. Settlement to Accounts Receivable
Accounting (FI-AR) complements the existing settlement to Accounts Payable Accounting (FI-AP)
The customer account is available in the commission contract in the Account of Recipient in Payment
System field. The end user is only confronted with the settlement to Accounts Receivable Accounting in
connection with the selection of settlement types and the target system.
Depending on the settlement type chosen, the logical service calls the corresponding function module to
transfer the disbursable settlement data to Accounts Receivable Accounting or Accounts Payable
Accounting in Financial Accounting.
The existing settlement processes and integration of the following settlement and disbursement systems
remains unchanged:
-
Collections and Disbursements (FS-CD)
Payroll (HR-PY)

The data volume is similar to that of the settlement to Accounts Payable Accounting.
Settlement types are assigned as previously to a group of remuneration types on the basis of a new target
ID. The target ID controls the settlement to Accounts Receivable Accounting.
______________________________________________________________
SAP AG
22
SAP-System
______________________________________________________________
See also
9.5.6 Liability Type Determination and Calculation of Remuneration Liability for

Absolute Valuation (Changed)
Use
As of Release SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600)
you can define liability types with the determination function and process them further in the commission
case.
You can also calculate the liability on remuneration on the basis of an absolute valuation, in addition to
the existing difference valuation.
If you do not wish the liability types to be defined by the determination, you should not enter any values
in Customizing for the liability determination.
If you make changes to your dataset, for example to existing commission cases, the changed liability
functions may produce different results.
See also
9.5.7 Retroactive Case Processing (RCP) (New)

Use
functions of retroactive case processing (RCP) are available.
You use RCP to automatically process commission cases that have to be recalculated. These commission
cases may be located in any position of a chain of business object versions. Processing includes
determining all the commission cases that may be affected by a change to the one initial commission
case (these are referred to as 'dependent commission cases'). An initial commission case for the purposes
of RCP is a commission case for which the commission system detects a change requirement. Possible
reasons for a change could be a Customizing error or coding changes.
To edit the initial commission case, you first have to reset the latest business object versions; this returns
the case to a processing status in which it is permitted to change the initial commission case.
You can either roll back or roll forward individual commission cases using a tool of the logical services
during standard commission case processing. This applies both to initial commission cases as well as to
dependent ones. Below is an example of how commission cases are rolled back or forward.
______________________________________________________________
SAP AG
23
SAP-System
______________________________________________________________
(i)
<==
(a1)
<==
(a2)
<==
(a3)
==>
(a1)
==>
(a2)
==>
(a3)
||
(i)
Cases i, a1, a2 and a3 are sorted from left to right according to their historical creation date. Using this
pattern, the system starts to roll back the cases from the top right to left, corrects them (below) and then
rolls forward. RCP rolls back the dependent commission cases until it reaches the initial commission case
and makes the required changes there. The initial commission case (i) represents the turning point: First
the dependent cases are rolled back (a1-a3), and then the initial cases.
Hence RCP automates the work that previously had to be done manually.
You access RCP in the SAP Easy Access menu by choosing Accounting -> Incentive and Commission
Management -> Administration -> Current Administration -> Retroactive Case Processing.
You can navigate from worklist management to initial commission case management and, from here, to
the creation of initial commission cases.
A number range object was created in Customizing for Incentive and Commission Management to
uniquely identify commission cases. You edit the intervals and their assignment to processes in Basic
Functions -> Preparation of Posting Processing and Parallel Processing -> Retroactive Case Processing
(RCP).
You can make the following additional settings under Processes -> Commission Case -> Retroactive
Case Processing (RCP) :
-
You can define the commission case statuses that are considered to be permitted at worklist
creation.
You can use two BAdI methods to include individual or selected incorrect commission cases in the
worklist.
See also
For more information on retroactive case processing see the SAP Library under Financials -> Incentive
and Commission Management and in the following program documentation:
-
CACSCP_RCP_CASE_ADMIN (transaction CACSRCPWORKLIST)
CACSCP_RCP_WORKLIST_ADMIN (transaction CACSRCPCASE)
CACSCP_RCP_PENDING_CASES (transaction CACSRCPFRAME)
9.5.8 Remuneration Inquiry (New)

Use
As of SAP ECC 6.0 Incentive and Commission Management (EA-ICM 600) the functions of
remuneration inquiry are available. You access the remuneration inquiry either from the main menu or
from the individual commission contract.
______________________________________________________________
SAP AG
24
SAP-System
______________________________________________________________
The remuneration items and settlement items are displayed identically in the commission case and
commission document under the new Remuneration Inquiry tab page.
The remuneration inquiry and remuneration result provide a comprehensive overview of the settlement
schedule items and the settlement items for the context in question.
Since the introduction of settlement scheduling in the previous release ERP 2004 it was not possible to
display all related settlement data. Previously you could only display the settlement schedule items and
the converted items. Transaction CACSSESDIS is now obsolete and should no longer be used since it
only displays the settlement schedule. You should now use transaction CACSREMDIS instead; this gives
you comprehensive information on the entire settlement data, such as that of a commission contract
partner.
A new menu path has been added to the main menu of Incentive and Commission Management under
Info Center -> My Remuneration (this calls transaction CACSACC1N, which replaces the transactions
CACSACC1 and CACSACC). When you access this menu path, the system determines the business
partner identification of the user who is logged on, and his or her commission contracts are determined
and the remuneration inquiry with the corresponding default data is called.
You make settings for the remuneration inquiry in Customizing for Incentive and Commission
Management under Information Systems -> Remuneration Inquiry .
To access remuneration inquiry from the individual contract, in Customizing for Incentive and
Commission Management, assign program CACS_CALL_REM_INQUIRY under Information Systems
-> Reporting/Drilldown -> Reports -> Assign Reports to Menu Item.
You only have to carry out the Customizing activities if you wish to add your own detail lines or columns
to the standard display. The standard display of remuneration inquiry does not require any Customizing
activities.
The remuneration inquiry (accessed from the main menu of Incentive and Commission Management and
from an individual commission contract) and the remuneration result (displayed in the commission case
and commission document) comprises three ALV grid controls in which the remuneration data,
settlement data and remuneration detail lines of the particular context are displayed.
To read more individual lines for remuneration, remuneration detail and settlement data, you use the
display structures for the three ALV grid controls in the standard SAP delivery. To do this, you can use
BAdI Read Additional Lines for Display of Remuneration Inquiry (CACS_REMINQ_ADD_ROWS).
If you wish to display individual data with its own structures in the remuneration inquiry or the
remuneration result, you need to carry out the following Customizing activities:
1.
Depending on the ALV grid control, define a DDIC structure in the IMG activity: Define Structures
for Remuneration Inquiry .
2.
For the defined structures, you must define the corresponding data retrieval methods in a BAdI
implementation (separately for remuneration lines, settlement lines and remuneration detail lines).
See also
For more information on the remuneration inquiry see the SAP Library under Financials -> Incentive and
Commission Management .
______________________________________________________________
SAP AG
25
SAP-System
______________________________________________________________
9.5.9 Remuneration Clearing (Changed)

Use
functions of remuneration clearing have been modified. This lets you carry out the determination of the
global remuneration clearing agreement with the data of a subobject (previously only possible for
business objects). Additionally, all remuneration lines in each process step are now only processed with
the selection protection rule with priority 9999 (previously with the last selection rule used). The
sequence of processing remuneration clearing rules has also changed:
1.
Global rules with indicator before standard rules
2.
Standard rules
3.
Global rules without indicator before standard rules
As of this release the sequence is determined for each rule and no longer for each agreement. It still
applies that only one global agreement and one standard remuneration clearing agreement should be
found.
The functional change has no effect on the database. Only the Customizing tables CACS_STCAGR and
TCACS_OFFRULING are automatically converted.

On system upgrade, the Customizing tables CACS_STCAGR and TCACS_OFFRULING must be
automatically adjusted by program CACS_600_XPRA_REMMOFFS.
Program CACS_600_XPRA_REMMOFFS adapts the Customizing tables CACS_STCAGR and
TCACS_OFFRULING to the new functions without affecting the processing result; in other words
downwards compatibility is ensured for the enhanced functions.
Additionally, a selection protection rule with priority 9999 with the corresponding entries in
TCACS_OFFRULING, TCACS_OFFRULE and TCACS_OFFCLCRULE is generated:
1.
For the global remuneration clearing agreement when the priority indicator (FLG_FIRST) that
determines the processing sequence is set in the agreement.
The program transfers the priority indicator from the remuneration clearing agreement to the
corresponding remuneration clearing rules.
2.
One for each standard remuneration clearing agreement.
To have full use of the new functions, you have the option of changing the priority indicator in the
remuneration clearing rule, which now determines for each global remuneration clearing rule whether this
is processed before or after the standard rules. You can also edit the selection protection rule.
Editing selection protection rule with priority 9999:
You can restrict the number of remuneration lines that are processed in the next step using the selection
protection rule. The priority 9999 plays a key role. This is the key of the remuneration clearing rule. This
______________________________________________________________
SAP AG
26
SAP-System
______________________________________________________________
determines whether the selection applies to processing. The selection protection rule must contain a
selection rule that influences the selection. The grouping and calculation rules must also be entered,
however they are not considered in processing. Consequently, no logical tools are required for this tool.
See also
For more information on the remuneration clearing agreement see the SAP Library under Financials ->
9.5.10 User Exit CACS2010: Change Customer Fields in Cancellation Document

(New)
Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you may
use user exit CACS2010 to change your own fields in cancellation documents.
It may be necessary, for example, to supply your own fields with additional information in the event of a
cancellation so that it is easily recognizable if the cancellation is to be assigned to the current business
year or the previous one. These attributes are required for account assignment.
As of this release it is possible to change a cancellation document accordingly. Since the cancellation
document reverses another document, the amounts in the amounts fields of the original document were
transferred to the cancellation document with a changed plus/minus sign and the original document is
identified as being invalid (since it was cancelled).
When the cancellation document is created, the cancellation line items valuation lines, remuneration lines
and settlement document lines are transferred to the user exit CACS2010 in the form of internal tables to
allow changes to customer fields to be made.
The standard fields are copied to internal tables before the user exit is called. After the call, these internal
tables are rewritten to the tables received from the function module of the user exit with MOVE
CORRESPONDING (only replaces the relevant fields).
Only the customer fields that may have been changed remain; the standard SAP fields that may also have
been changed are overwritten again by the previously saved contents of the internal tables.
You must only use function module MESSAGE_STORE_WITH_DISPLAY to display system messages.
You must activate your own function module in Customizing. Customer function modules may be
assigned to an event and to a customer-specific production object.
For more information see Customizing for Incentive and Commission Management under Tools ->
Interfaces and User Exits -> Settings for User Exits .
______________________________________________________________
SAP AG
27
SAP-System
______________________________________________________________
Since the changes can only be made in the cancellation document itself, you must also make the table
settings in Customizing so that the document is fully read.
See also
For more information on user exits see the SAP Library under Financials -> Incentive and Commission
Management -> Administration.

Use
______________________________________________________________
SAP AG
28
SAP-System
______________________________________________________________
necessary):
1.
package PFO.
2.
3.

Construction.
4.
5.
6.

7.
8.
9.
-
See also
9.5.12 Valuation Determination Using Copy Service (New)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you have
the option of implementing the valuation with the SAP standard condition technique as in previous
releases or by using the copy service.
The copy service lets you quickly implement a simple valuation with minimum Customizing effort. To
use the valuation through copy service, you must select package CACSM2 in the commission
application construction.
______________________________________________________________
SAP AG
29
SAP-System
______________________________________________________________
To carry out a valuation determination using the copy service, you must first perform the following steps
in Customizing for Incentive and Commission Management:
1.
Select package CACSM2 and generate a commission application.
2.
Under Basic and Master Data -> Standard Commission Contract -> Valuation Agreement -> Edit
Evaluation Types, choose a valuation type and assign it to tool VALUATION_LIGHT.
3.
Under Tools -> Copy Services -> Define Assignment Event Management Data define attributes for
each valuation type of the copy services.
4.
Carry out the activity Tools -> Copy Services -> Reset Copying Services.
Display in Commission Contract

The valuation types that you have defined in table <APPL>_VVAMMAP are displayed in the
commission system under the Global Agreements tab page of the commission contract.
See also
9.6 ICM-TO
Tools
9.6.1 Framework for Object Assignment (FOA) (New)

Use
functions of Framework for Object Assignment (FOA) are available. Framework for Object
Assignment provides the technical context for assigning objects to target objects. In the standard delivery,
the services of FOA are used for entitlement and liability transfer and portfolio assignment.
Here is an overview of the services provided by Framework for Object Assignment:
-
Managing worklists for object assignment
Processing worklists in a dialog and as background jobs
Automated object assignment in assignment processes with workflow support
The configuration of FOA provides the framework for assigning any object types to any target object
types. You can implement other types of object assignment using FOA in your own customer projects or
adapt the standard delivery of entitlement and liability transfer or portfolio assignment .
FOA provides a user interface for managing worklists for object assignment and a user interface for
managing assignment processes. With these interfaces you can assign objects to target objects and
manage the assignment processes.
To access FOA, in the SAP Easy Access menu choose Accounting -> Incentive and Commission
Management -> Administration -> Current Administration -> Object Assignment. Here you can edit
worklists for object assignment. All functions of FOA for worklists and assignment processes are
______________________________________________________________
SAP AG
30
SAP-System
______________________________________________________________
available on the user interface through the menu paths and pushbuttons.
You can use FOA to make individual assignments of objects to target objects on an ad hoc basis. In
entitlement and liability transfer you can, for instance, transfer individually selected remuneration
entitlements of a commission contract to another one. You can also carry out mass assignments on the
basis of assignment rules. This is useful, for instance, in entitlement and liability transfer if a commission
recipient leaves the organization and his or her entire (legal) entitlement is transferred to new recipients
on the basis of predefined rules.
Through the reuse of FOA for various forms of object assignment in the standard delivery (entitlement
and liability transfer and portfolio assignment), the same functions are used and hence the efficiency is
optimized in the execution of tasks in the context of object assignment.
FOA provides deletion programs to clean up its own transactional dataset. This is the content of database
tables that map the worklist for object assignment or the assignment process.
Applications that use FOA are responsible for their own archiving or deletion of transactional data that
are created by object assignment. In entitlement and liability transfer, for example, transfer documents are
written that have to be unloaded by the archiving tools of Incentive and Commission Management.
If you use the functions of FOA, there are no requirements for initial data transfer. This is only required if
applications connecting to FOA use information in the master data area. For instance, in the standard
delivery of entitlement and liability transfer the attributes of the commission contract of the commission
recipient leaving the organization decide the rules on the basis of which the worklist is created. If a
dependency is defined, it must be ensured that the required attributes of the master data are retained.
SAP Business Workflow is used to support the assignment processes for automatically carrying out object
assignments. It is the task of the system administrator to configure the runtime environment for the
workflow and to provide operational support.
You make settings for FOA in Customizing for Incentive and Commission Management for example
under Tools -> Framework for Object Assignment (FOA) . For functions like entitlement and liability
transfer that use FOA and are part of the standard delivery, the standard settings are predefined. To adjust
the functions, you can change the configuration to suit your requirements. You can find help on the
settings in the Implementation Guide (IMG) of Incentive and Commission Management under the
documentation on the individual IMG activities of FOA.
You can use elements of organizational management to assign processors to certain steps in the
assignment process. To edit organizational management, in the SAP Easy Access menu choose Incentive
and Commission Management -> Master Data-> Organizational Plan.
See also
You will find information on FOA in the corresponding system documentation, for instance by pressing
the information on the initial screen of transaction CACS_OA01 or CACS_OA11.
For more information on Framework for Object Assignment see the SAP Library under Financials ->
______________________________________________________________
SAP AG
31
SAP-System
______________________________________________________________
9.6.2 Settlement Using Framework for Parallel Processing (New)

Use
Framework for Parallel Processing is available. The execution of the ICM settlement on different
servers is simplified with user-friendly administration functions. The total runtime of the settlement is
consequently reduced.
You can start the ICM settlement using Framework for Parallel Processing in the menu of Incentive and
Commission Management:
On the SAP Easy Access screen, choose Accounting -> Incentive and Commission Management ->
Administration-> System Administration -> Parallel Processing or enter transaction FPP_STMT in the
command field.
See also
For more information on Framework for Parallel Processing see the SAP Library under Financials ->
Incentive and Commission Management.
9.6.3 Detach or Enhance SAP Condition Technique (Changed)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you have
the option of replacing the SAP standard condition technique with another rule machine in ICM and
connecting it through the specified interfaces.
As of the current release you can choose which rule machine you intend to use in Incentive and
-
SAP condition technique
A non-SAP rule machine
If you do not use the SAP condition technique, you do not have to carry out the following steps in the
Customizing implementation. Note that you cannot carry out these steps after you have detached the
condition technique.
-
Set up the field transports (under Incentive and Commission Management -> Tools -> Copy Services
-> Define Assignment Events)
Define the F4 help as required
Make sure that the following areas are served by the non-SAP rule machine. To do so, carry out the
following:
-
Set up scales
Create standard conditions
______________________________________________________________
SAP AG
32
SAP-System
______________________________________________________________
Create individual conditions
Determine valuations on the basis of their conditions
Contract settlements should be made on the basis of their condition technique (empty controls)
You integrate the non-SAP rule machine in Customizing of Incentive and Commission Management in
the following activities:
1.
Create your own remuneration type. To do so, choose Basic and Master Data -> Standard
Commission Contract -> Remuneration Agreements -> Edit Remuneration Type Activity.
2.
Replace the SAP tool REMUNERATION_STANDARD with your own tool. To do so, choose
Tools-> Logical Service: Edit Tools.
3.
Assign the tool to the remuneration type. To do this, choose Basic and Master Data -> Standard
Commission Contract -> Remuneration Agreements -> Edit Remuneration Type Activity -> Assign
Tool.
Changing the condition technique has the following effect on the commission case (transaction data):
Under the Performance-Related Remuneration tab page, the data of the non-SAP condition technique
is displayed if this data is transferred to the tree structure in a new XML file. You can use the following
SAP events or create your own:
-
Valuation (1001)
Remuneration (1002)
Liability (1003)
This change has no effect on the commission contract (master data).

This change has the following effect on the interface:
-
No change to the user interface if you use the standard XML file to display the condition records.
The user interface may change depending on whether you wish to transfer the calculated values to
the tree structure in your own XML file.

If you continue to use the SAP condition technique and only add your requirements, this has effects on
the data transfer since the append structures are also processed.
To use the SAP condition technique, you select it in the same way as in the past.
To use a non-SAP condition technique, do not select the SAP condition technique on the installation CD
when you install the current release.
Depending on where you intend to carry out the calculation of conditions for the valuation, remuneration
or liability, you should make the presettings according to the respective subprocess steps in the
commission case either under SAP condition technique or in the non-SAP rule machine.
______________________________________________________________
SAP AG
33
SAP-System
______________________________________________________________
See also
For more information see the SAP library under Financials -> Incentive and Commission Management.
9.6.4 User Exit CACS2010: Change Customer Fields in Cancellation Document

(New)
Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) you may
use user exit CACS2010 to change your own fields in cancellation documents.
It may be necessary, for example, to supply your own fields with additional information in the event of a
cancellation so that it is easily recognizable if the cancellation is to be assigned to the current business
year or the previous one. These attributes are required for account assignment.
As of this release it is possible to change a cancellation document accordingly. Since the cancellation
document reverses another document, the amounts in the amounts fields of the original document were
transferred to the cancellation document with a changed plus/minus sign and the original document is
identified as being invalid (since it was cancelled).
When the cancellation document is created, the cancellation line items valuation lines, remuneration lines
and settlement document lines are transferred to the user exit CACS2010 in the form of internal tables to
allow changes to customer fields to be made.
The standard fields are copied to internal tables before the user exit is called. After the call, these internal
tables are rewritten to the tables received from the function module of the user exit with MOVE
CORRESPONDING (only replaces the relevant fields).
Only the customer fields that may have been changed remain; the standard SAP fields that may also have
been changed are overwritten again by the previously saved contents of the internal tables.
You must only use function module MESSAGE_STORE_WITH_DISPLAY to display system messages.
You must activate your own function module in Customizing. Customer function modules may be
assigned to an event and to a customer-specific production object.
For more information see Customizing for Incentive and Commission Management under Tools ->
Interfaces and User Exits -> Settings for User Exits .
Since the changes can only be made in the cancellation document itself, you must also make the table
settings in Customizing so that the document is fully read.
See also
For more information on user exits see the SAP Library under Financials -> Incentive and Commission
______________________________________________________________
SAP AG
34
SAP-System
______________________________________________________________
Management -> Administration.
9.6.5 Commission Case Connected to Workflow (New)

Use
As of SAP ECC Enterprise Extension Incentive & Commission Management 6.0 (EA-ICM 600) the ICM
commission case workflow connection is available. This allows work items to be sent to commission
clerks (or system administrators) via workflow when a commission case is set to pending or is rejected at
the commission case interface.
The workflow function is available for commission cases that are created manually as well as those
subject to mass processing.
The workflow avoids the risk of pending commission cases being overlooked since responsible
processors are determined and informed quickly and in a flexible way.
The incurred work items are displayed in Business Workplace.
Two new application tables CACS_WFCAS and CACS_WFPFNR are filled by EDT with the IDs of the
incorrect commission cases for which no workflow has been started. After the (automatic) start of the
workflow, the entries are deleted. No user action is normally required.
The workflow runtime environment must be configured, if this has not already been done. The
configuration of this may be rather complex.
To prepare the commission application for using the workflow connection, you should carry out the
following activities in Customizing for Incentive and Commission Management:
-
Application Administration -> Installation of Commission Application -> Select Commission

Packages
Application Administration -> Commission Application Generation
Copy Customizing from Template (Client-Specific)
Also carry out the configuration specific to the workflow function in the following IMG activities:
In Customizing for Incentive and Commission Management, choose Tools -> Workflow:
-
Define Message Groups
Define Type of Processor Determination
under Rejected Commission Cases and Resolved Pending -> Configure Message Groups for
Commission Case
Sort Messages into Message Groups
______________________________________________________________
SAP AG
35
SAP-System
______________________________________________________________
In the SAP Customizing Implementation Guide (transaction SPRO) you can determine dynamic columns
for Business Workplace. To do this, carry out the following (optional) IMG activity:
-
SAP NetWeaver -> SAP Web Application Server -> Business Management -> SAP Business
Workflow -> Basic Settings -> Determine Dynamic Columns for Business Workplace
Use of Evaluation Paths

To use the workflow connection, you must use the relevant evaluation paths.
Here is it necessary that the user known to the system who is assigned to a commission clerk position as
the business partner (or more generally, to a position relevant for processor determination) is also
assigned as user of the same position and can be determined by an evaluation path.
See also
______________________________________________________________
SAP AG
36

ICM Incentive and Commission Management SAP ERP Central Component

Uploaded by

Copyright:

Available Formats

You might also like

ICM Incentive and Commission Management SAP ERP Central Component

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ICM Incentive and Commission Management SAP ERP Central Component

Uploaded by

Copyright:

Available Formats

ICM Incentive and Commission Management

SAP ERP Central Component

Copyright 2005. SAP AG. All rights reserved.

are registered trademarks of Informix Software

ICM Incentive and Commission Management

Incentive and Commission Management

9.1 Terminology (Changed)

New (ERP2005) Changed to:

9.2.1 BW Extractors (New)

Set up the BW system accordingly.

9.2.2 Database Conversion (Changed)

In all ERP systems with commission applications

In all clients with commission applications

In all commission applications

9.2.3 Conversion of Fixed-Value Domain to E Tables

9.2.4 Structural Changes to IMG of Incentive and Commission Management

Added IMG Activities

-> Business Add-Ins (BAdIs)

-> Define Methods

-> Configure Partnership Types

-> Commission Case

-> Construction of Participations

-> Commission Case

-> Retroactive Case Processing (RCP)

-> Process Start

Renamed ICM Activities

Define Ledger Currency

ERP2005 (EA-ICM 600)

Define Commission Model Currency

9.2.5 Changes to Menu of Incentive and Commission Management (New)

Master Data -> Portfolio Assignment

Info Center -> Reports

New Menu Options

Business Object PFO_GZO

Assignment Object PFO_SZO

Under Info Center

Under Info Center -> Reports

Remuneration Inquiry CACSREMDIS

Under Administration -> Current Administration

Edit Target Rules CACSTRU

Retroactive Case Processing CACSRCPWORKLIST

Object Transfer CACS_OA11

Under Administration -> System Administration

Parallel Processing FPP_STMT

Under Commission Document

Settlement Schedule CACSSESDIS

9.2.6 Remuneration Clearing (Changed)

Global rules with indicator before standard rules

Global rules without indicator before standard rules

Effects on System Administration

One for each standard remuneration clearing agreement.

9.2.7 Customer Enhancements Possible to TCACS_APPLCUST (Changed)

9.2.8 Target Agreements (New)

Copy Cross-Client Customizing from Template.

Under Design Adjustment of Commission Application, execute Commission Application

Compare Local Copies of Structures with Originals in Operational Systems.

Execute Commission Application Generation.

In Customizing of Incentive and Commission Management, execute Copy Customizing from