Dealer Commission strategy

[Former Member]

Hi gurus,

We have a scenario. Scenario is as follows:

Our client sales few products to customer and gives commission to the dealer. The commission rate varies from product to product, dealer to dealer customer wise.

Also there are two ways on which dealer commission is decided viz: 1. fixed rate on the list price of the product, based on which discount and sales price is arrived.

2. Based on the billed amount(before taxes)

Client wants to generate a Credit note for the commission in the name of dealer at the time of invoicing automatically.

I want to know how we can configure this scenario with both pricing strategy.

Awaiting for quick response.

Points will be rewarded to all solutions as no solution is wrong.

Kind regards,

Ravi

[ranjeetrajendra_jain]

Hiya

Please refer below, and incorporate in your scenario

1) Establish Partner Functions for the Commissionee(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

2) Assign the Partner Functions to Partner Procedures

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

3) Create a Partner Procedure for the Commissionees

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

4) Create New Customer Account Group(s) for Commission Agents

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER

Transaction Code: OVT0

5) Assign the Partner Functions to the Customer Account Group(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENT

Transaction Code: VOPA

6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header

Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions ->; Partner Determination ->; Define Partner Functions

Transaction Code: VOPA

7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

😎 Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent)

Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY

Transaction Code: SE11

9) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

10) Edit RV60AFZZ - user exit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

11) Edit MV45AFZB - user exit_new_pricing_vbkd changing new_pricing (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing if the user makes a change to the relevant partner function (alteration, addition, deletion).

13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES

Transaction Code: OV24

14) Create Condition Tables (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES

Transaction Code: V/03

15) Create an access sequence containing the new tables (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES

Transaction Code: V/07

16) Create a new condition type

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES

Transaction Code: V/06

17) Add the Condition Type to the Pricing Procedure

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES

Transaction Code: V/08

11) Create Commission Report ZZCOMMISSION (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

Regards

[Former Member]

Thanks for the reply.

I have few more queries.

What can i have understood from the solution u gave, we have a create a new partner function for dealer. But my query is whether this partner function will be assigned with KU (customer) or LI(vendor).

Also what will be the condition tables for the access sequence for the dealer commission condition type.

Looking forward for reply.

regards,