Dealer Business Management 7.0 ICM Configuration Guide

Dealer Business Management 7.0

ICM Configuration Guide

DBM 7 .0

Dealer Business Management 7.00 ICMConfiguration

for DBM

© 2009 SAP AG Dealer Business Management 7.00Incentives and Commissions for Vehicle SalesVersion: 2.0

Page2 of 73

Copyright© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 componentsof other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, SystemStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBMCorporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks ofAdobe Systems Incorporated 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 orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 inventedand implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAPproducts and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of Business Objects S.A. in the United States andin other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warranty of anykind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.


for DBM


Page3 of 73

Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at aglance. For more information, see Help on Help General Information Classes and Information Classes forBusiness Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.


for DBM


Page4 of 73

Table of Contents1 INTRODUCTION 6

1.1 PREREQUISITE 71.2 OBJECTIVE OF THIS DOCUMENT 81.3 DOCUMENT VERSION 81.4 LEGEND 81.5 BUSINESS SCENARIO AND COMPONENTS 81.6 SAP NOTES 9

2 SCENARIO SETUP CUSTOMIZING 10

2.1 DEPLOY ICM PACKAGES FOR DBM 102.1.1 Create ICM application 102.1.2 Apply the ICM Application Wizard 10

2.2 MAINTAIN DBM CUSTOMIZING 152.2.1 Maintain the newly created ICM application In DBM customizing 152.2.2 Define business object and triggering object for ICM 152.2.3 Setup DBM Order Engine 16

2.3 MAINTAIN ICM CUSTOMIZING (TR: CACSIMG) 162.3.1 Copy the Cross-Client Customizing from Template 162.3.2 Application Maintenance 162.3.3 .Define commission model currency 172.3.4 Number Ranges 172.3.5 Maintain valuation types 212.3.6 Maintain conditions for VALUATION_LIGHT (CACS_DET_VAMMAP) 222.3.7 Maintain Selection Table <APPL>_VSTABA0 in Determination 222.3.8 Define Account Assignment Types 232.3.9 Configure Account Assignments for remuneration types for settlement system FI: Maintain AccountAssignment Type ID and GL Account. 232.3.10 Configure Account Assignments for remuneration types for settlement system HCM: Maintain AccountAssignment Type ID, Company Code and Wage type. 242.3.11 Configure Account Assignments for settlement types for settlement system FI: Maintain AccountAssignment Type ID, Company Code and Document Type. 242.3.12 Configure Account Assignments for settlement types for settlement system HCM: Maintain AccountAssignment Type ID and Company Code. 242.3.13 Application design check 252.3.14 Assign Business Transaction Categories to Business Object Categories 262.3.15 Edit Entitlement Categories for Each Business Transaction/Business Obj.Type 262.3.16 Enter transaction CACS_APPL_AA and enter the following values: 272.3.17 RFC scenario 272.3.18 Define Assignment Event Management Data 282.3.19 Define Assignment Event Management Data 292.3.20 Define Contract Types 302.3.21 Edit Settings for Indirect Participants (Evaluation Paths etc.) 312.3.22 Other Evaluation Paths and FMs (Active Versions) 312.3.23 Create condition tables 312.3.24 Define Access Sequences 332.3.25 Create Condition Table Entries in Customizing of Remuneration Agreement 332.3.26 Edit Update Mode For Totals Tables 34

3 SETTING UP THE ORGANIZATIONAL STRUCTURE 35


for DBM


Page5 of 73

3.1 CREATE ORGANIZATIONAL HIERARCHY 353.1.1 Setup an organizational structure of the sales department 353.1.2 Create a HR master for internal vehicle sales representatives 353.1.3 Assign HR masters to organizational structure 35

3.2 COMMISSION CLERK AND COMMISSION CONTRACT PARTNERS 363.2.1 Create Business Partner Roles 363.2.2 Assign Business Partner to HR master 36

3.2.2.1 Manual Assignment 373.2.2.2 Setup automatic interface for BP-HCM master synchronisation 38

3.2.3 Assign user to commission clerk role 453.2.4 Assign commission clerk to organizational structure 45

4 OPERATING ICM 49

4.1 MAINTAIN STANDARD CONTRACTS 494.2 DEFINE COMMISSION CONTRACT TYPES 494.3 ASSIGN COMMISSION CONTRACT TYPES TO PARTNER TYPES 494.4 CONTROL OF STANDARD CONTRACT FOR EACH APPLICATION 504.5 EDIT AGREEMENT TYPES FOR EACH APPLICATION 504.6 ASSIGN AGREEMENT TYPES FOR EACH CONTRACT TYPE 514.7 CONFIGURE DETERMINATION COMBINATIONS/COMBINATION ASSIGNMENTS 524.8 EDIT STANDARD AGREEMENT FOR PERFORMANCE-RELATED REMUNERATION 544.9 STANDARD CONTRACT SETTING WITH ENTERPRISE PORTAL 55

4.9.1 Portal Standard Contract Creation 554.9.2 Personalization of application 554.9.3 Create Contract for Sales Rep 564.9.4 Create Contract for Sales Agent 634.9.5 Create Contract for Sales Manager 644.9.6 Create Sales Rep Team 67

4.10 MAINTAINING STANDARD CONTRACTS WITHOUT ENTERPRISE PORTAL 684.11 MIGRATING STANDARD CONTRACTS 704.12 CREATE COMMISSION CONTRACTS 704.13 CREATE CONDITION RECORDS 724.14 SIMULATING A COMMISSION CASE 734.15 CREATING A COMMISSION CASE 73


for DBM


Page6 of 73

1 Introduction

In order to automate commission processes at a dealership, DBM features a standard integration toIncentive and Commission Management (ICM). ICM was developed with open interfaces to any upstream(DBM) or downstream (HR/FI) system. SAP ICM provides standard functionality for:

Designing incentive plans

Calculating commissions

Settling commissions

ICM provides a DBM package containing standard DBM fields for commission application generation.

The DBM interface to ICM transfers order and vehicle data included in the DBM vehicle sales order forcommission simulation and for commission case creation. The interface includes DBM order type, salesorganization, distribution channel, division, partner functions, customer advisor, item data, vehicle andvehicle model data, and many other fields that may be incentive relevant. The interface can also beenhanced by customer-specific fields.


for DBM


Page7 of 73

When transferring a DBM order and vehicle data into ICM, ICM calculates the commission and returnscalculated commissions into the DBM order. Commission contracts can be set up in ICM with conditionscorresponding to DBM data such as brand, vehicle model, vehicle type, etc.

The commission case master data consists of three parts:

1. The commission contract containing all commission rules

2. The organizational hierarchy (assigned in commission contracts to determine additionalindirect participants, such as sales manager)

3. The employee responsible or other involved parties (for example, external agents)

The trigger to create and process the commission case is set with a DBM event that can be linked to theBilling button, that is, the commission case is created when an invoice is created for the customer. Thecommission case is deleted when the invoice is cancelled. Settled commissions are claimed back.

Processing of the commission case consists of four major steps.

1. Participant determination: Any kind of commission recipient is either handed over directly fromDBM (direct participants like sales reps and agents) or determined via the organizationalstructure (indirect participants like managers).

2. Object valuation: In the standard DBM Customizing, the gross profit is passed to remunerationon a calculation basis. The commission-relevant value is determined in DBM function module/DBM/ICM_GET_GROSS_PROFIT and can be updated in ICM, for example:

Commitments made to the end customer, such as “first standard maintenance forfree,” impact commission calculation

For a particular model range, the calculation basis is increased for a particular timeperiod

3. Remuneration calculation: Any kind of commission (used car, new car, fleet sales, accessoriesetc.) is calculated via condition technique.

4. Posting of results: Calculated amounts are transferred to settlement systems for payout. Anycommission is settled to a commission account (behaves like a pool for settlement amounts).The account is cleared when transferring the settlement amounts to the settlement systems forpayout.

The purpose of this document is to guide on the setup of commission processes with DBM 7.0 and ICM. WithECC 6.0 EhP4, packages containing some preconfiguration of this scenario are delivered with ICM whichfacilitate the setup.

Some manual steps which are still required to be performed are listed in this document

1.1 Prerequisite

You have DBM 7.0 based on ECC 6.0 EhP4 installed

You have activated enterprise extension EA-ICM in transaction SFW5

You have activated enterprise business functions EA_ICM_ICM_CORE_01 andEA_ICM_ICM_CORE_02 in transaction SFW5


for DBM


Page8 of 73

1.2 Objective of this Document

This document should be considered as a guide to setup a basic example on commission calculation in aDBM vehicle sales scenario. It is not to be viewed as a comprehensive documentation of every customizingstep required, the ICM online and customizing help needs to be referred to in addition to this document.

1.3 Document Version

Date Name Alteration Reason Version

24.07.2009 Christopher Naab First draft 1.0

16.08.2009 Laszlo Gombos 2nd draft 1.4

08.10.2009 Laszlo Gombos 3nd draft 1.5

09.10.2009

23.11.2009

Christopher Naab

Christopher Naab

4th draft

Final

1.6

2.0

1.4 Legend

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

1.5 Business Scenario and ComponentsBusiness Scenario ERP application component with minimum release


for DBM


Page9 of 73

DBM and ICM Required Application Components:

SAP ECC 6.0

DBM 7.0

Optional Application Components required for the scenario

HR-Payroll for internal payouts

SAP Financials A/P for external payouts

1.6 SAP Notes

Note 1022451


for DBM


Page10 of 73

2 Scenario Setup Customizing

2.1 Deploy ICM packages for DBM

2.1.1 Create ICM application

In the central customizing transaction for ICM, transaction CACSIMG, follow the below menu path or entertransaction CACSNEWAPPL.

Menu path Transaction code

CACSIMG General Application Modellingand Administration Installation ofApplication Name Application

CACSNEWAPPL

Enter a short and a long text.

Example

2.1.2 Apply the ICM Application Wizard

In transaction CACSIMG, select the application wizard.


for DBM


Page11 of 73

1. Select existing application ZDBM01 and choose Continue.

2. Confirm the header data of the application and choose Continue.

3. Select “Dealer” and choose Continue.


for DBM


Page12 of 73

4. Select Process and Scenario: Auxiliary Processes Automotive => Dealer Vehicle Sales

5. Choose Region: no selection required


for DBM


Page13 of 73

Choose Continue

6. Select languages

7. Select clients


for DBM


Page14 of 73

7. Final activities

8. Finish.


for DBM


Page15 of 73

Then press complete.

Track the progress of commission application generation in transaction SM37 and wait until completed.

2.2 Maintain DBM customizing

2.2.1 Maintain the newly created ICM application In DBM customizing


SPRO Logistics Execution DealerBusiness Management Order SpecificProcesses Incentive and CommissionManagement Define Application

SPRO, /DBM/SPRO

Maintain your ICM application generated with the application wizard and save.

2.2.2 Define business object and triggering object for ICM


SPRO Logistics Execution DealerBusiness Management Order SpecificProcesses Incentive and CommissionManagement Define Business Object andtriggering object

SPRO, /DBM/SPRO


for DBM


Page16 of 73

Maintain the table according to your order types.

2.2.3 Setup DBM Order Engine

In order to enable commission simulation and commission case creation, the DBM Order Engine has toinclude the event COMMISSION_SIM and the following actions

COMMISSION_SIM

COMMISSION_CRE

COMMISSION_CAN

For more information, please refer to OSS note 1022451.

2.3 Maintain ICM customizing (tr: CACSIMG)

2.3.1 Copy the Cross-Client Customizing from Template

Go to the target client and perform this activity.

In the Implementation Guide (IMG) for the Commission System, select the following path to copy the Cross-Client Customizing from Template:

Menu path Final Node

Incentive and Sales Force ManagementGeneral Application Modeling andAdministration-> Copy Cross-ClientCustomizing from Template

Copy Cross-Client Customizing from Template

Enter the commission application you created in aprevious step and execute.

CACS_CUSTCOPY_CLNT

Check log.

2.3.2 Application Maintenance

1. Enter transaction SM30.


for DBM


Page17 of 73

2. Enter view V_TISIS_APPL and press Maintain.

3. Maintain your generated commission application, enter a text for it and save.

2.3.3 .Define commission model currency


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel Processing-> DefineCommission Model Currency

Define Commission Model Currency

2.3.4 Number Ranges

1. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for commission contract partner:


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> CommissionContract Partner

Commission Contract Partner

Nothing to enter, just available in display mode. Themaintenance is done by BP.

2. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Commission Contracts and Contract Bundles:


Incentive and Sales ForceManagement Incentiveand CommissionManagement-> BasicFunctions-> Preparation ofPosting Processing andParallel ProcessingMaintain Number Ranges->Commission Contracts andContract Bundles

Commission Contracts and Contract Bundles:Store Number Ranges

No From Number To Number CurrentNumber

Ext.

01 00000000000000000001 0000000099999999999

Commission Contract: Control NumberAssignment Category

No Short Name Ext.

01 Internal NrRange

Contract Bundle: Control Number AssignmentCategory

No Short Name Ext.

01 Internal NrRange


for DBM


Page18 of 73

Commission Contract: Define Number Ranges forInd. Agreement


Ext.

01 000000000001 099999999999

3. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Partnerships:


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> Partnerships

Define Number Ranges forDistribution Ratios


Ext.

01 000000000001 099999999999

4. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Commission Cases and Triggering Objects:


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> CommissionCases and Triggering Objects

Commission Cases: Define Number Ranges

No Year From Number To Number Current N. Ext.

01 2009 000000000001 099999999999 0

Commission Cases: Assign Number Ranges toProcess Categories

Commission Cases: Specify Number Ranges forImported Variants


Ext.

01 000000000001 099999999999

Triggering Objects: Define Number RangesNo From Number To Number Current

NumberExt.

01 000000000001 099999999999


for DBM


Page19 of 73

Triggering Objects: Assign Number Ranges toProcess Categories

5. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Commission Documents, Settlement & Closing Processes andReferences in Disbursement System:


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> Comm.Docs,Stt. & Closing Processes, References inDisbursement System

Commission Documents: DefineNumber Ranges

Commission Documents: AssignNumber Ranges to ProcessCategories

Edit Update Mode For Totals TablesTable Update Mode

DBM001_SUMRE V1

DBM001_SUMSE V1DBM001_SUMVA V1

Run Number: Define Number RangesNo From Number To Number Current

NumberExt.

01 000000000001 099999999999

References in the Payment System:Define Number Ranges


Ext.

01 000000000001 099999999999

6. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Segment Assignment:



for DBM


Page20 of 73

Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> SegmentAssignment

Define Number Range for SegmentAssignment

Out of scope – no need to add a number range

7. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Settlement Schedules:


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> SettlementSchedules

Define Number Ranges forSettlement Schedules

Assign Number Ranges to ProcessCategories

8. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Fulfillment Levels (Actual Commission):


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> FulfillmentLevels (Actual Commission)

Define Number Ranges forFulfillment Level Headers


Define Number Ranges forFulfillment Level Items


for DBM


Page21 of 73


9. In the Implementation Guide (IMG) for the Commission System, select the following path todefine and assign number ranges for Retroactive Case Processing (RCP):


Incentive and Sales Force ManagementIncentive and Commission Management->Basic Functions-> Preparation of PostingProcessing and Parallel ProcessingMaintain Number Ranges-> RetroactiveCase Processing (RCP)

Define Number RangesNo From Number To Number Current

NumberExt.

01 000000000001 999999999999


2.3.5 Maintain valuation types


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission Contract ValuationAgreement Edit Valuation Types

CACS_APPL_AF

Maintain the following table

ValuationType

TriggeringObject

ValResCat. Complx. Effectivefrom

EffectiveUntil

NameValuation Type

2000 20000 1 AbsoluteValuation

Today’s date Future date DBM VehicleSales


Today’s date Future date DBM VehicleSales


1 Today’s date Future date DBM TargetAgreementsComplex Target


Today’s date Future date DBM TargetAgreementsElementaryTarget

For valuation type 2000 and 2001 in this table, assign the following entry in below folder “assign tool”.


for DBM


Page22 of 73

Version Tool Define Effective from Effective until

1 VALUATION_LIGHT Today’s date Future date

For valuation type 2900 in this table, assign the following entry in below folder “assign tool”.


1 VALUATION -TARGETSCOMPLEX

Today’s date Future date

For valuation type 2901 in this table, assign the following entry in below folder “assign tool”.


1 VALUATION -TARGETS SIMPLE

Today’s date Future date

2.3.6 Maintain conditions for VALUATION_LIGHT (CACS_DET_VAMMAP)

In the central customizing transaction for ICM, transaction CACSIMG, follow the below menu path or entertransaction CACS_DET_VAMMAP.


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission Contract ValuationAgreement Condition Tables andValuation Procedures (Copy Services)Edit Conditions

CACS_DET_VAMMAP

a. Valuation Type 2000, Value Quantity 100, Value Unit %

b. Valuation Type 2001, Value Quantity 100, Value Unit %

(Additional Valuation_Light functions can be found in General Tools->Logical Service: Edit Tools)

2.3.7 Maintain Selection Table <APPL>_VSTABA0 in Determination


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractRemuneration Agreements Agreement forPerformance-Related RemunerationsDefine Determination Criteria

CACS_DET

If popup comes choose the table <APPL>_VSTABA0 and add the fields:

a. a. Multiple Selection 1, Triggering Object Type 20010, Participant Role 200, DBM Business Transaction CUS,Selection ID 2001


for DBM


Page23 of 73

Multiple Selection 1, Triggering Object Type 20010, Participant Role 200, DBM Business Transaction NEC, Selection ID2001

b. Multiple Selection 1, Triggering Object Type 20010, Participant Role 200, DBM Business Transaction USC, SelectionID 2004

c. Multiple Selection 1, Triggering Object Type 20010, Participant Role 201, DBM Business Transaction NEC, SelectionID 2000

d. Multiple Selection 1, Triggering Object Type 20010, Participant Role 202, DBM Business Transaction NEC, SelectionID 2003

e. Multiple Selection 1, Triggering Object Type 20010, Participant Role 202, DBM Business Transaction USC, SelectionID 2003

f. Multiple Selection 2, Triggering Object Type 20010, Participant Role 200, DBM Business Transaction NEC, SelectionID 2002

g. Multiple Selection 2, Triggering Object Type 20010, Participant Role 200, DBM Business Transaction USC, SelectionID 2002

2.3.8 Define Account Assignment Types


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractAgreement for Settlement Define AccountAssignment Types

CACS_APPL_05

1. Enter a period for the effective validity

2. List your account assignment type via F4 help.

2.3.9 Configure Account Assignments for remuneration types for settlement systemFI: Maintain Account Assignment Type ID and GL Account.



for DBM


Page24 of 73

CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractAgreement for Settlement ConfigureAccount Assignments Configure AccountAssignments for Remuneration TypesConfigure Account Assignments forSettlement System FI

CACS_DET_ACRFI

Should there be problems in accessing the generated views, regenerate the ICM application usingtransaction CACSGENERATOR.

2.3.10 Configure Account Assignments for remuneration types for settlementsystem HCM: Maintain Account Assignment Type ID, Company Code and Wagetype.


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractAgreement for Settlement ConfigureAccount Assignments Configure AccountAssignments for Remuneration TypesConfigure Account Assignments forSettlement System HCM

CACS_DET_ACRHR

2.3.11 Configure Account Assignments for settlement types for settlement systemFI: Maintain Account Assignment Type ID, Company Code and Document Type.


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractAgreement for Settlement ConfigureAccount Assignments Configure AccountAssignments for Settlement TypesConfigure Account Assignments forSettlement System FI

CACS_DET_ACSFI

2.3.12 Configure Account Assignments for settlement types for settlement systemHCM: Maintain Account Assignment Type ID and Company Code.



for DBM


Page25 of 73

CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractAgreement for Settlement ConfigureAccount Assignments Configure AccountAssignments for Settlement TypesConfigure Account Assignments forSettlement System HCM

CACS_DET_ACSHR

2.3.13 Application design check


CACSIMG General Application Modelingand Administration Design Adjustment ofApplication Application Construction

CACSDESIGN

On the left side select the 'Settlement to Payroll' and on the right side select 'Calculation-> R/3 ConditionTechnique-> Append Structure for CACS_S_CUST_COND

Verify that the following fields are added to the structure YYYALL_A_CUST_COND from the left side:

DBM_BUSTYPE

DEVLINE

MODLINE

MCODESD

GROSS_PROFIT

VHVIN

VHCLE

You can add more fields with drag and drop.

Additional available:

http://help.sap.com/erp2005_ehp_04/helpdata/EN/2a/c77b3c25c2877be10000000a114027/content.htm

After the fields are added, regenerate the maintenance dial ICM application using transactionCACSGENERATOR including

Including Cross-Application Objects if the structure YYYALL_A_CUST_COND is changed.

Structures and tables

Views for DB and Maintenance

Programs (Delete All and Regenerate)

Function Groups (Delete All and Regenerate)

Classes and Interfaces (Delete All and Regenerate)

Maintenance dialogs

http://help.sap.com/erp2005_ehp_04/helpdata/EN/2a/c77b3c25c2877be10000000a114027/content.htm


for DBM


Page26 of 73

2.3.14 Assign Business Transaction Categories to Business Object Categories


CACSIMG Incentive and CommissionManagement Business Objects, BusinessSubobjects and Business Transactions AssignBusiness Transaction Categories to BusinessObject Categories

CACS_APPL_23

Make the following settings

2.3.15 Edit Entitlement Categories for Each Business Transaction/BusinessObj.Type


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission Contract ParticipationAgreement Edit Entitlement Categories forEach Business Transaction/Business Obj.Type

CACS_APPL_60


for DBM


Page27 of 73

Make the following settings

Business Object Category 200, Business Transaction Category 1, Entitlement Category 1




Assign Business Transaction Categories to Business Object Categories

2.3.16 Enter transaction CACS_APPL_AA and enter the following values:

Settings 042, Values X

2.3.17 RFC scenario

In case ICM is used in the same application server, ignore this step.

Create the following tables in the DBM System according to the tables available in ICM System:

<APPL>_CAS

<APPL>_PAR

<APPL>_INV

<APPL>_ACT

<APPL>_OBJ

<APPL>_LIN

<APPL>_REL

<APPL>_BDL

<APPL>_DOCACT

<APPL>_DOCDT

<APPL>_DOCHD

<APPL>_DOCINV

<APPL>_DOCOBJ

<APPL>_DOCPAR

<APPL>_DOCRE


for DBM


Page28 of 73

<APPL>_DOCREL

<APPL>_DOCSE

<APPL>_DOCVA

2.3.18 Define Assignment Event Management Data

In the central customizing transaction for ICM, transaction CACSIMG, follow the below menu path.


CACSIMG General Tools CopyServices Define Assignment EventManagement Data

Select Event 1002 and switch to folder “Assignment, Administration (Active)”.

Enter the following table with effective date from today

For both below entries for source structure KOMV

Enter new source fields

KWERT with target field name REM_LEDAMNTKBETR with target field name REM_RATE. For this new field, include factor 0,1.


for DBM


Page29 of 73

For below entry for source structure KOMV

Enter new source fieldKWERT with target field name REM_LEDAMNT

Save the new entry.

2.3.19 Define Assignment Event Management Data

In the central customizing transaction for ICM, transaction CACSIMG, follow the below menu path or entertransaction CACS_APPL_21


CACSIMG Incentive and CommissionManagement Business Objects, BusinessSubobjects and Business TransactionsEdit Business Object Categories

CACS_APPL_21

Make the following entries with the appropriate validity

BusObjCat. Vers. Subobject Type BOR Comb Type Rem. Bus Obj Cat


for DBM


Page30 of 73

0 0 AAA Commission Contract200 20000 DBM Vehicle Order290 29000 DBM Target Agreements

For the last entry (BusObj Cat. 290), make the following entry in subfolder “Assign Tool”

ToolTARGET AGREEMENT CASE

2.3.20 Define Contract Types

In the central customizing transaction for ICM, transaction CACSIMG, follow the below menu path.


CACSIMG Incentive and CommissionManagement Basic and Master DataOrganizational Structure Evaluation Pathsof Indirect Participants, Commission Clerks,etc. Define Contract Types

CACS_APPL_57

Make the following 3 entries.

Cont. cat Name

01 Std. Contract

02 Ind. Contract

03 Contract Bundle


for DBM


Page31 of 73

2.3.21 Edit Settings for Indirect Participants (Evaluation Paths etc.)


CACSIMG Incentive and CommissionManagement Basic and Master DataOrganizational Structure Evaluation Pathsof Indirect Participants, Commission Clerks,etc. Edit Settings for Indirect Participants(Evaluation Paths etc.)

CACS_APPL_61

2.3.22 Other Evaluation Paths and FMs (Active Versions)


CACSIMG Incentive and CommissionManagement Basic and Master DataOrganizational Structure Evaluation Pathsof Indirect Participants, Commission Clerks,etc. Edit Other Evaluation Paths andFunction Modules

CACS_APPL_35

Make the following entry

2.3.23 Create condition tables


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractRemuneration Agreements Agreement forPerf.-related Remuneration ConditionTables and Procedures Condition Tables

Create condition tables

CACSCOND0002


for DBM


Page32 of 73

Change the following condition tables and switch in technical viewCreate Condition Table 705 (DBM Target Agreement): define Commission Application, Standard

Agreement Number, Complex Target Type, Version Date, and Status as footer fields

uncheck field “with release status”

Create Condition Table 704 (DBM Vehicle Sales): define Agreement Number, Development Line, SalesModel Number, Version Date, Vehicle Bus.Transaction as footer fields

uncheck field “with release status”

Condition Table 706 (DBM Promotion): define Version Date and Vehicle Bus.Transaction as footer fields uncheck field “with release status”


for DBM


Page33 of 73

2.3.24 Define Access Sequences


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractRemuneration Agreements Agreement forPerf.-related Remuneration ConditionTables and Procedures Define AccessSequences

CACSCOND0006

2.3.25 Create Condition Table Entries in Customizing of Remuneration Agreement



for DBM


Page34 of 73

CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission ContractRemuneration Agreements Agreement forPerf.-related Remuneration ConditionTables and Procedures Edit Contents ofCondition Tables

CACSCONDMAINT

Enter condition values for your vehicle models (model sales codes) for the condition types created above.

2.3.26 Edit Update Mode For Totals Tables


CACSIMG Incentive and CommissionManagement Processes CommissionCase Edit Update Mode For Totals Tables

CACS_APPL_BH

Assign the following tables to update mode.

<name commission application>_SUMRE

<name commission application>_SUMSE

<name commission application>_SUMVA


for DBM


Page35 of 73

3 Setting up the Organizational Structure

3.1 Create Organizational Hierarchy

3.1.1 Setup an organizational structure of the sales department

Create the organizational structure of the sales department including all positions of junior and senior salesrepresentatives and sales manager.


Human Resources OrganizationalManagement Organizational PlanOrganizational and StaffingCreate/Change

PPOCE/PPOME

3.1.2 Create a HR master for internal vehicle sales representatives

In order to have internal vehicle sales rep’s commission paid out via HR payroll, a minimum set of infotypesmust be maintained for the relevant sales employees by using transaction PA30 (Maintain HR Master Data).


Human Resources PersonnelManagement Administration HR MasterData Maintain

PA30

Maintain the following infotypes:

0000 - Actions

0001 - Organizational Assignment

0002 - Personal Data

3.1.3 Assign HR masters to organizational structure

Assign your HR masters to positions (e.g. junior sales representative) of the organizational structure of yoursales department.


Human Resources OrganizationalManagement Organizational PlanOrganizational and Staffing Change

PPOME


for DBM


Page36 of 73

3.2 Commission Clerk and Commission Contract Partners

3.2.1 Create Business Partner Roles

In transaction BP, create commission contract partners and commission clerks.

Function BP role

Commission recipient: all internal sales staff who receive commissions CACSA1

Commission clerk: internal commission admin to manage commission contracts CACSA2

Agent: external agent who receives commission for sales transactions CACSA3

In tab “Control”, assign BP Type according to role (e.g. 9001 for Manager, 9002 for SalesRepresentative, 9003 for Sales Agent)

At least one commission clerk is required in order to create commission contracts. Assign a userID to tab “Identification” in role “CACSA2”.

3.2.2 Assign Business Partner to HR master

The main idea in developing an integration between the employees in HCM (P = Person) and the ICMBusiness Partners (BP) is to avoid redundant maintenance of master data. The overhead of changing theaddress (e.g.) of an employee in both the employees master data and its business partner has to bereduced.

The relation between P and BP is realized by an object called “Central Person” (CP). The CP itself has noattributes and is just a capsule for this kind of relation. The CP also allows relating a user (US) to P or BPetc.

For ICM, the HCM is the leading system, this means that once the integration is activated it is no longerpossible to maintain the master data for a BP. Maintenance of master data has always to be done in HCM’semployee maintenance and is afterwards synchronized with the BP.

Data changes into HCM are recorded and then synchronized by the next run of the adjustment report.

The synchronization affects some attributes of the following info types:- 0002 personal data- 0006 addresses- 0009 bank account data- 0105 communication

An early design says that the synchronization process will only work if HCM and ICM are in the samesystem. In fact the RFC-connection should also work.

When assigning HCM employees to ICM business partners, several constellations are possible:- New HCM employee without ICM business partner- New HCM employee with existing ICM business partner- Manual assignment between existing HCM employee and existing ICM business partner


for DBM


Page37 of 73

New HCM employee without ICM business partner

If a new HCM employee has been created, the adjustment process will create a new ICM business partneron its next run.

New HCM employee with existing ICM business partner

When a new HCM employee should be assigned to an existing ICM business partner, this assignment has tobe defined manually in transaction CACS_PERNRBP.

On the next run of the adjustment process this assignment will be stored in the database table HRP1001 andthe employee’s data will be synchronized with the business partner.

Manual assignment between existing HCM employee and existing ICM business partner

If both employee and business partner already exist, the assignment has to be defined in transactionCACS_PERNRBP like described before.

An automatic creation of employees out of business partners in not possible with standard functionality.

This workaround is not recommended for the DBM-ICM interface.

3.2.2.1 Manual Assignment

In the Implementation Guide (IMG) for the Commission System (transaction CACSIMG), select the followingpath to control explicit assignments of ICM Business Partners to HCM Employees.

Incentive and Sales Force Management GeneralTools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Control of Business Partner/ HR EmployeeAdjustment Linking HR Employees with Commission Business Partner Control Explicit Assignmentof Business Parnters to HR Employees Maintain Assignment of Business Partners to HR Staff

Transaction code CACS_PERNRBP

Choose Maintain Explicit Assignment of Business Partners to HR Staff.

Enter HCM personnel numbers and / or ICM business partner numbers.

Alternatively you can automate the assignment; you need to setup the HCM-ICM interface.


for DBM


Page38 of 73

Even if you decide for manual assignment, you still need to do the following

Compare transaction OO_CENTRAL_PERSON with settings in step 3.2.2.2

Run report CACS_ADJUST_HR_PARTNER

3.2.2.2 Setup automatic interface for BP-HCM master synchronisation

In the CACSIMG, there is a separate area for functions in the context of the HR integration. You’ll find allreferred transactions under:

Incentive and Commission Management Tools Interfaces and User Exits Interface HR Employees ->Commission Contract Partner

(1) In the Implementation Guide (IMG) for the Commission System, select the following path to execute themost important activation steps.

Incentive and Commission Management Tools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Basic Settings

Activate Interface, System Set up: Set the flag for interface active. If you want to use a RFC connection,insert it into the corresponding field. If you created a run automatically, enter a user that is allowed to run thejob.

Maintain RFC Connection: If you want to use a RFC connection, you have to configure it here.

Setup Central Person (transaction OO_CENTRAL_PERSON): For Activation of the interface, fill in thefollowing settings:


for DBM


Page39 of 73

(2) In the Implementation Guide (IMG) for the Commission System, select the following path to check theBusiness Partner settings.

Incentive and Commission Management Tools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Check Business Partner Settings

Check, if a standard grouping for an internal number range for Business Partners is available.

This is only required in the target system.

(3) In the Implementation Guide (IMG) for the Commission System, select the following path to configure aUser Exit that assigns ICM Business Partner roles to newly created ICM Business Partners.

Incentive and Commission Management Tools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Control of Business Partner/ HR Employee Adjustment

Define Roles for Newly Created Business Partners

Define a product:

Select Settings Products …of a customer in the menu.

Create a customer product (e.g. ZDBM01) and save it as active.

Define an event:

Select Settings Process Modules …of a customer in the menu.

Create a new entry for process CACS3000 and a function module (e.g.ZICM_CACS_SAMPLE_PRC_3000) for the product defined before.

Define a function module:

Create the function module (e.g. ZICM_CACS_SAMPLE_PRC_3000) by copying thedelivered sample function module CACS_SAMPLE_PRC_3000. The function module musthave the same name as the one that was entered for the process CACS3000.


for DBM


Page40 of 73

FUNCTION ZICM_CACS_SAMPLE_PRC_3000 .

*"--------------------------------------------------------------------*"*"Local Interface:*" IMPORTING*" REFERENCE(IV_EMPLOYEE_ID) TYPE PERNR_D*" REFERENCE(IS_P0001) TYPE BAPIP0001*" EXPORTING*" REFERENCE(ET_ROLES) TYPE BU_ROLE_T*"--------------------------------------------------------------------

DATA: lv_role TYPE bu_role.

lv_role = 'CACSA1'.

APPEND lv_role TO et_roles.

ENDFUNCTION.

(4) In the Implementation Guide (IMG) for the Commission System, select the following path to compareaddress, marital status and title.


Define Conversion of Keys for Form of Address, Marital Status and Title

Use the description given in the IMG or read SAP note 577361.

View T522G – HCM Address:

View V_TCACS_ANRED – Assignment between HCM and ICM address:

View V_T502T – HCM Marital Status:


for DBM


Page41 of 73

View V_TCACS_FAMST – Assignment between HCM and ICM marital status:

View V_TSAD2 – Academic Title:

(5) In the Implementation Guide (IMG) for the Commission System, select the following path to definedynamic measures.


Linking HR Employees with Commission Business Partners Define Dynamic Measures

You can define dynamic measures to ask users to enter a corresponding business partner when makingthe settings (e.g. by calling a dialog box in using information category 0000).

(6) In the Implementation Guide (IMG) for the Commission System, select the following path to schedule abatch job for transferring change information to the target system.


for DBM


Page42 of 73


Schedule Job for Transferring Change Information to Target System

In this step, you control the transfer of HCM exchange information from a separate HCM system to thebusiness partner system containing ICM.

Define a job in which you specify the CACS_TRANSFER_HRLOG report as the ABAPprogram.

Once the transfer has been completed successfully, the adjustment is triggered in the target system as astandard procedure. If you want to avoid this, create an appropriate variant for the report and specify this inthe job definition.

If HCM and ICM are installed on the same server and thus are not connected by RFC, you will not need thisworkaround. The setting is only required in the source system.

(7) In the Implementation Guide (IMG) for the Commission System, select the following path to check thetransfer log.


Check Transfer Log

In this step, you control the transfer of HCM exchange information from a separate HCM system to thebusiness partner system containing ICM.

Check the log.

Transfer the transaction CACS_DISPHRLOG to the area menu of the HCM employeeresponsible.

Once the transfer has been completed successfully, the adjustment is triggered in the target system as astandard procedure. If you want to avoid this, create an appropriate variant for the report and specify this inthe job definition.

If HCM and ICM are installed on the same server and thus are not connected by RFC, you will not need thisworkaround. The setting is only required in the source system.

(8) In the Implementation Guide (IMG) for the Commission System, select the following path to schedule abatch job for periodic adjustment.


Schedule Job for Periodic Adjustment

In this step, you schedule a job to adjust the business partner master data changes registered in HCM usingchange recording.

Define a job in which you specify the CACS_ADJUST_HR_PARTNER report as the ABAPprogram.


for DBM


Page43 of 73

The setting is only required if source and target system are the same or if the adjustment is not automaticallystarted after the transfer of HCM log data. In this case, the setting needs to be made in the target system.



Check Adjustment Log

In this step, you control the transfer of HR exchange information from a separate HCM system to thebusiness partner system containing ICM.

Check the log.

Transfer the transaction CACS_DISPHRLOG to the area menu of the HCM employeeresponsible.

The setting is only required in the target system.

(10) In the Implementation Guide (IMG) for the Commission System, select the following path to define theassignment of existing HCM employees and ICM Business Partners.

Incentive and Commission Management Tools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Legacy Data Transfer Define Assignment of ExistingHR Employees and Business Partners

You can define which ICM Business Partners are assigned to which HCM Employees when the first link isestablished through a Central Person. For this, you can implement a User Exit for the BTE event CACS3001.

In the standard, the link is established through the fields "External partner number" (Business Partner, fieldBUT000-GPEXT) and "Old personnel number" (HR, field P0032-PNALT).

Define an event:

Select Settings Process Modules …of a customer in the menu.

Create a new entry for process CACS3001 and a function module (e.g.ZICM_CACS_SAMPLE_PRC_3001).

Define a function module:

Create the function module (e.g. ZICM_CACS_SAMPLE_PRC_3000) by copying thedelivered sample function module CACS_SAMPLE_PRC_3001. The function module musthave the same name as the one that was entered for the process CACS3001.

This setting is only necessary in the target system. As a reference, you can use the function module normallyused for this: CACS_HR_FIND_EMPLOYEE.

function cacs_hr_find_employee.*"----------------------------------------------------------------------*"*"Lokale Schnittstelle:*" IMPORTING


for DBM


Page44 of 73

*" REFERENCE(IV_PARTNER) TYPE BU_PARTNER*" EXPORTING*" REFERENCE(EV_EMPLOYEE_ID) TYPE PERNR_D*" REFERENCE(EV_EMPLOYEE_FOUND) TYPE XFELD*"----------------------------------------------------------------------

statics: lt_pa0032 type standard table of pa0032, lv_ini_flag type xfeld value ' '.

data: lv_bpext type bu_bpext, lv_srcdes type cacs_srcdes, ls_pa0032 type pa0032.

if lv_ini_flag is initial. select single srcdes from tcacs_hrgp_ctrl into lv_srcdes where kdummy eq ' '.

call function 'CACS_HR_GETPA0032' destination lv_srcdes tables t_pa0032 = lt_pa0032 "#EC ENHOK exceptions communication_failure = 1 message gs_bapireturn-message system_failure = 2 message gs_bapireturn-message.

* fuba_exception ct_bapireturn.

sort lt_pa0032 by pnalt.

lv_ini_flag = 'X'. endif.

clear ev_employee_found.

select single bpext from but000 into lv_bpext where partner eq iv_partner.

if sy-subrc eq 0 and not lv_bpext is initial. read table lt_pa0032 into ls_pa0032 with key pnalt = lv_bpext binary search.

if sy-subrc eq 0. move: ls_pa0032-pernr to ev_employee_id, 'X' to ev_employee_found. endif. endif.

endfunction.

If the source and target system differ, then the data must be read from the source system, using the RFC.You need to create a function module that is compatible with RFC, and which needs to be transported to theHCM system and is called from the User Exit. An example of this is CACS_HR_GETPA0032, which is calledfrom CACS_HR_FIND_EMPLOYEE.

(11) In the Implementation Guide (IMG) for the Commission System, select the following path to create alink between ICM Business Partners and HCM Employees.

Incentive and Commission Management Tools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Legacy Data Transfer Create Link between BusinessPartners and HR Employees

In this step, you can create the link between HCM employees and ICM business partners after old datatransfer, by using PD objects from the "central person" ("CP") category.

If there are business partners that were not created using the HCM interface and that are not assigned to aHCM employee in accordance with linking HCM employees with ICM Business Partners, the comparison forany existing HCM employees that correspond would result in the creation of new business partners.


for DBM


Page45 of 73

If the source and target systems differ, then central persons are initially created in the target system for allHCM employees that are in the source system.

The assignment between HCM employee and ICM business partner must be defined before. The setting isonly required in the target system. You can view the log afterwards again.


Incentive and Commission Management Tools Interfaces and User Exits Interface HREmployees -> Commission Contract Partner Legacy Data Transfer Make First Adjustment

In this step, you can adjust ICM business partners and HCM employees for the first time. From the selectionscreen in the adjustment report, choose "Compare all employees" as otherwise only the employees whohave changes recorded are taken into consideration.

ICM business partners and HCM employees must be linked by means of a PD object of the category "centralperson" ("CP"). The setting is only required in the target system. You can view the adjustment log here.

3.2.3 Assign user to commission clerk role


Central Business Partner Transaction BP

Assign a system user ID to the business partner who is creating commission contracts.

Enter the user ID in role CACSA2 “commission clerk” tab “Identification”

3.2.4 Assign commission clerk to organizational structure


Human Resources OrganizationalManagement Organizational PlanGeneral Structures Change

PPSM

1. Enter Object Type O (Organizational Unit)

2. Select Object ID of organizational unit

3. Select evaluation path CACS_GP


for DBM


Page46 of 73

4. Right mouse click on the top organizational unit and click on “Create Object (F7)”

5. Create a new position “commission clerk”

6. Create a relationship to the new position


for DBM


Page47 of 73

7. Select “Holder”

8. Assign the commission clerk created in previous steps by searching for BP role “CACSA2”

9. Save your updated structure of your sales organization


for DBM


Page48 of 73


for DBM


Page49 of 73

4 Operating ICM

4.1 Maintain Standard Contracts

With ECC 6.00 EhP3, the ICM standard contract maintenance was moved into Enterprise Portal. It isassumed that only a minority of DBM customers are using Enterprise Portal and will therefore need tomaintain standard contracts in a SAP GUI transaction.

4.2 Define Commission Contract Types


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission Contract DefineCommission Contract Types

CACS_APPL_13

Contr. Type Sht Nme StdComnCont Agent w.o Own… Indicator: Contra…

200 DBM Sales Rep

201 DBM Sales Agent

202 DBM Sales Manager

203 DBM Sales Team X

4.3 Assign Commission Contract Types to Partner Types


CACSIMG Incentive and CommissionManagement Basic and Master DataStandard Commission Contract AssignCommission Contract Types to PartnerTypes

CACS_APPL_45

ContType PartnerTy. Version Effec.From EffecUntil

200 0003 1 01.01.1900 00:00:00 31.12.9999 00:00:00

201 9003 1 01.01.1900 00:00:00 31.12.9999 00:00:00

202 0003 1 01.01.1900 00:00:00 31.12.9999 00:00:00

203 0003 1 01.01.1900 00:00:00 31.12.9999 00:00:00


for DBM


Page50 of 73

The partner type is usually maintained on the Business Partner side. The standarddelivery is with partner type = 0003 (Employee). You have to select this value under the controltab where you create the Business Partner in Role CACSA1 (Commission Contract Partner).

4.4 Control of Standard Contract for Each Application

This activity is used to control the manner the standard contracts can be edited for the ICM application. Thiscan be accessed in the


CACSIMG Incentive and Sales ForceManagement->Incentive and CommissionManagement->Basic and Master Data->Standard Commission Contract->Control ofStandard Contract for Each Application.

CACS_APPL_D3

Select your ICM application.

Check all the checkboxes in the table for the application ZDBM01.

4.5 Edit Agreement Types for Each Application


CACSIMG Incentive and Sales ForceManagement->Incentive and CommissionManagement->Basic and Master Data->Standard Commission Contract-> EditAgreement Types for Each Application

CACS_APPL_D1

Agremt Type Allowed DetermUsed Multiple Load All

01

02

07


for DBM


Page51 of 73

09

14

24

26

42

´

4.6 Assign Agreement Types for Each Contract Type

This activity is used to control the manner the standard contracts can be edited for the ICM application.


CACSIMG Incentive and Sales ForceManagement->Incentive and CommissionManagement->Basic and Master Data->Standard Commission Contract->AssignAgreement Types for Each Contract Type

CACS_APPL_D2

Select the application as ZDBM01.

Click on ‘New Entries’ and link your commission contract types with agreement types.

Make the entries as shown in the image below:


for DBM


Page52 of 73

4.7 Configure Determination Combinations/Combination Assignments


CACSIMG Incentive and Sales ForceManagement->Incentive and CommissionManagement Basic and Master DataStandard Commission ContractRemuneration Agreement Agreement forPerformance-Related RemunerationConfigure DeterminationCombinations/Combination Assignments

CACS_APPL_40

Make the following entries

CombTypeNo. Eff fr. Eff un. Selection Table OT ObjID Description

BRO 01 2BRO DBM Brokerage

DBM ZDBM03_SELTABA0

NVS 01 2NVS DBM New Vehicle SalesCommission

PRO 01 2PRO DBM Promotion Commission


for DBM


Page53 of 73

SUP 01 2SUP DBM Overriding Commission

TAR 01 2TAR DBM Target Agreements Bonus

UVS 01 2UVS DBM Used Vehicle SalesCommission

For the second entry (CombTypeNo. = DBM), make the following entry under subfolder “CombinationAssignment Active”

Selection Table SelNo. ….. Combination

ZDBM03_SELTABA0 2000 BRO

ZDBM03_SELTABA0 2001 NVS

ZDBM03_SELTABA0 2002 PRO

ZDBM03_SELTABA0 2003 SUP

ZDBM03_SELTABA0 2004 UVS


for DBM


Page54 of 73

4.8 Edit Standard Agreement for Performance-Related Remuneration


CACSIMG Incentive and Sales ForceManagement->Incentive and CommissionManagement Basic and Master DataStandard Commission ContractRemuneration Agreement Agreement forPerformance-Related Remuneration EditStandard Agreement for Performance-Related Remuneration

CACS_APPL_17

Standard Agreement …… CombTypeNo. Description

AGENT DBM DBM: Sales Agent

MANAGER DBM DBM: Sales Manager

REP DBM DBM: Sales Representative

TAR TAR DBM: Target Agreements

TEAM DBM DBM: Sales Team


for DBM


Page55 of 73

4.9 Standard Contract setting with Enterprise Portal

If you do not have Enterprise Portal, skip this chapter.

4.9.1 Portal Standard Contract Creation

Login into the portal linked to the system that all the customizing were done.

ICM application should have been configured in the system along with all the standard agreements.

User should have the portal role “Sales Compensation Analyst” added to the profile.

4.9.2 Personalization of application

Click on the link as shown in the image


for DBM


Page56 of 73

Set the ICM application as shown in the Image

4.9.3 Create Contract for Sales Rep

Click on create to start the creation of standard contract DBM1


for DBM


Page57 of 73

Create – DBM1

Enter the data as shown in the image

A screen will come up. Click on next


for DBM


Page58 of 73

On the screen that come up click on the first drop down as shown in the diagram


for DBM


Page59 of 73

Click on the standard agreement DBMREP from performance related. The screen will look as follows.


for DBM


Page60 of 73

Click on the arrow marked in red. This will add the selected agreement to the standard contract.

The Standard Agreement DBMREP has been added to the Standard contract. Similarly the other standardagreements DBM70001 (07 Participation) DBM90001 (09 Payment and Settlement) T1 (26 Target


for DBM


Page61 of 73

Agreement) TGT (24 Commission Case Trigger) ZBVO (01 Performance-Related Remuneration) has to beadded to the Contract in the same screen.

Click on Next

No action to be performed on this document. Click on next.

No action to be performed on this document. Click on next.


for DBM


Page62 of 73

No action to be performed on this screen. Click on Activate. The status should be green. If not the user mayhave forgotten to add some must agreement.


for DBM


Page63 of 73

No action to be performed on this screen. With this the Standard contract DBM1 is ready for use.

4.9.4 Create Contract for Sales Agent



Click on next



for DBM


Page64 of 73

Similar to the manner the standard agreements were added to standard contract DBM1, DBMAGENT (01Performance-Related Remuneration)

DBM70002 (07 Participation)

DBM90002 (09 Payment and Settlement)

has to be added to the Contract DBM2. The steps mentioned for DBM1 after the agreement addition have tobe replicate for contract DBM2.

4.9.5 Create Contract for Sales Manager



for DBM


Page65 of 73



for DBM


Page66 of 73

Click on next



for DBM


Page67 of 73

Similar to the manner the standard agreements were added to standard contract DBM1, DBMMANAGER (01Performance-Related Remuneration)




4.9.6 Create Sales Rep Team



for DBM


Page68 of 73

Enter the data for DBM Sales Rep Team

Click on next


Similar to the manner the standard agreements were added to standard contract DBM1, DBMREP (01Performance-Related Remuneration)




4.10 Maintaining Standard Contracts without Enterprise Portal

It is assumed that most DBM customers do not have Enterprise Portal installed, therefore the followingworkaround is provided.


NA CACS_APPL_08


for DBM


Page69 of 73

Create standard contracts….

….assign them to contract types….

…..and assign standard agreements

Example:


for DBM


Page70 of 73

DBM Sales Rep (commission contract type 200) by assigning standard remuneration agreements REP andTAR, participation agreement REP, settlement agreement REP and target agreements REP

DBM Sales Agent (commission contract type 201) by assigning standard remuneration agreement AGENT,participation agreement AGENT and settlement agreement AGENT

DBM Sales Manager (commission contract type 202) by assigning standard remuneration agreementMANAGER, participation agreement MANAGER and settlement agreement MANAGER

DBM Sales Rep Team (commission contract type 203) by assigning standard remuneration agreement TEAM,participation agreement TEAM and settlement agreement REP

4.11 Migrating Standard Contracts

If Enterprise Portal is not used to maintain Standard Contracts, the following report needs to be executedafter creating or changing existing standard contracts

Enter transaction SE38 and execute report CACS_700_XPRA_STDCTR_INTERNAL.

Marking the checkbox at field P_NEW will cause that all fields in the standard contract will be overwritten.

Enter the client and execute the program every time a standard contract is maintained or changed.

After the report has been executed, the standard contracts created earlier will be available for use withoutEnterprise Portal.

4.12 Create Commission Contracts


Standard Menu Accounting Incentiveand Commission Management MasterData Commission Contract Create

CACSMD101

Number assignment 01 (internal NrRange)

Commission contract partner (BP role CACSA1)

Refer to standard contract (e.g. ZDBM1 for DBM Sales Rep)


for DBM


Page71 of 73

In the contract, assign the organizational unit….


for DBM


Page72 of 73

4.13 Create Condition Records


NA CACSCONDMAINT

Enter a value for the condition records created above depending on which commission scenario you want todeploy.


for DBM


Page73 of 73

4.14 Simulating a commission case

When creating a vehicle quotation, DBM event COMMISSION_SIM can simulate a commission case and tellthe sales representative how much commission would be in for him if he closes the vehicle sales deal.

4.15 Creating a commission case

The standard vehicle sales scenario includes the creation of a commission case after billing creation (eventBILLING_CREATE. The commission case document can be accessed via the document flow of the DBMorder.

Once a commission case is created, further commission processes such as approval settlement are handledin ICM using the commission case as a central document.

Dealer Business Management 7.0 ICM Configuration Guide

Documents

Transcript of Dealer Business Management 7.0 ICM Configuration Guide