Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Commission Management

Introduction

Business Context

In the automotive area, especially the vehicle sales, it is common practice, that the salary of an employee gets together by a lower fixed salary and a variable commission e.g. in sales based on the vehicles and accessories he sells.
To support this commissioning process the proaxia DBM|E Core component provides the business function "Commission Management".
The concept of "Commission Management" is based on the SD invoice, so this business function can be used for all departments, which use the SD invoice within their process, e.g. like parts sales, service workshop, etc.
Because the solution itself is quite flexible and it is difficult to describe some functionalities in a transparent way without a concrete case, we use in the following documentation the process "sales commission" as use case.
Solution Overview

Figure 10: Solution overview
Example "sales process" overview:

  • Based on the customer (SD) invoices the commission is calculated on company individual rules.
    • Message of the SD invoice is the trigger
    • Commission type and other values came from basic settings
    • Formula builder with individual rules will be processed and calculate the commission value
    • Based on the salesman of the invoice the partner roles of the commission and also the commission split values are determined (split only in case of pool commission)
    • This step normally happens automatically in the background


  • The calculation result normally will be checked by the sales administration department.

Are all relevant documents are available (contract, leasing,…)

    • Do the system values fit to the documents and is the calculation correct?
    • If relevant, enter additional special conditions (e.g. special agreements)
    • Release the commission "checked by administration"
    • This step normally happens in the proaxia DBM|Ecommission monitor


  • The calculation result normally must be released by the salesman himself.


    • Check values and if all is fine, then release the commission
    • In case of differences between the calculation result and an individual agreed commission, the salesman will be able to apply the difference.
    • This steps could happen in the proaxia DBM|E commission monitor or e.g. by a customer individual non-SAP frontend.


  • In case of differences the responsible sales team leader has to release / to reject in addition the salesman changes the request.


    • In case of release, the correction is accepted and the transfer to HR can start
    • In case of rejection, the commission returns to the salesman and he must correct again
  • Finally, the released / accepted commission is transferred to the HR department to pay corresponding value with the salesman salary.


Based on the customer's philosophy the salesman and maybe also the salesman team lead, do not directly work in the SAP system. In such a case, it is also possible to integrate e.g. a company own UI5 solution for them. Such an UI5 solution is not part of the DBM|Ebusiness function "Commission Management". But to support such a solution, we provide the corresponding web services for the connection / integration of such a customer solution.
The same philosophy we support for the HR transfer. Some customer use SAP HR and will maybe fully integrate the DBM|Ebusiness function "Commission Management". Others use maybe an external system and just want to have a simple list print out. So here we provide the corresponding web services for the transfer of commission values.


  • No labels