The Agent Commission reports in BW is part of the global sales folder. It provides visibility on the commission paid to the companies appointed by Solvay to sell the products locally. It has been designed for controllers that supervise the commission paid. |
Describe the key User profiles that exist for the application. General role/Viewer role: Approver role: |
Target Users:
|
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 19.12.2023 | Azadeh Nasiri | Initial draft |
|
There are four types of commission processes:
The "6155 - Training March 2017 - global overview" presentation gives a good explanation of the processes.
The current agent commission process has been implemented by the project 6155 "New agency contract management and remuneration" that went live on January 2017. Please note these processes are common across PF1 and WP1.
Agent Master Data
Each Agent is represented by both a customer and a vendor because the customer is needed for the commission note (see below) and the vendor is needed for the payment in FI.
TODO : self-invoicing / ITI vendors
Variable commissions are set up using sales pricing condition records so that a pricing condition is created automatically in the sales order. The commission rate is a percentage of the sales price.
For example, sales in sales org CGDE (company 0005) with company code 7523 in WP1 as agent will have a pricing condition record of type CVA or CV1 with the search term "W7523P0005".
The program ZZV_COMM_VAR will runs once a month in the background to automatically create the commission notes to pay the agents based on the billing docs with condition types CV, CV2, CVA and CV1.
For PF1 companies, the "commission" sales area is ccPn/99/99 where "cc" is the company's country code and "n" is running number. For example, KRP1/99/99 is the "commission" sales area for Solvay Specialty Polymers Korea. For WP1 companies, the "commission" sales area is ccZn/TA/99 where "cc" is the company's country code and "n" is running number. For example, BRZ1/TA/99 is the "commission" sales area for Rhodia Brasil.
The sales office and sales group are both "MBU".
The material used in this sales order depends on the BFC market / activity 1 of the sold materials (see view ZZV_COMM_MAT_V for the list of materials). The BFC market / activity 1 is linked with the business area (itself coming from the plant and the material division via the table T134H) through the table ZZF_BFC_DIV_CONV.
The plant is linked to the company code via the table Z1FCYWERKS.
Examples of flows
Flow | Description |
|---|---|
Set up of new commissions in company code 3383 / sales org KRP1 Paid commissions:
Received commissions:
|
TBC - no info can be found
The User guide on errors of ZZV_COMM_VAR and ZZV_COMM_FIX explains how to manage common errors in these two transactions.
Tables / views
Project Playbook
Procedures for the rollout, merger, carve-in/carve-out of Solvay company and its impact on the agent commission processes can be found in the folder "Rollout: Useful documents" of the project 6155. Some documents in the project folder need to be updated when implementing a project.
The APDM team and the IS-RtR-Interco team are also involved in the set up of commission in case of rollout, merger, carve-in/carve-out of Solvay company.
For most key combinations, there is a LSMW to create or change the validity end date of CV* pricing condition records. The templates are also available in the folder "Rollout: Useful documents" of the project 6155.
Open orders containing a CV* pricing condition which has been modified needs to be corrected manually. The CV* condition types in the billing documents are copied from the sales order rather than being re-determined based on the pricing condition records so old CV* conditions may remain in the system after the condition records have been updated.
The sales orders containing a CV* pricing condition can be listed with the transaction ZZV_PR_CHECK_PC then the ones that are open can be found with the transaction Z1V_LIST_ORDERS.
Information about the existent Workbooks and the respective BW queries.
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.
Could be specific fields, closing activities, additional information to work and understand the reports.
| Domain | <insert name> |
|---|---|
| Application | >insert name> |
| Provider | <insert name> |
| Existing Documentation | <insert link> |
This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.