Select only the highest freight condition at Sales document

The header condition has to be reflected on to the item level as pricing data is stored in tables at the item level(even for header condition type). So by making all items’ ZDEL as inactive status except the highest ZDEL at the Item level, then only the highest ZDEL will active at the header level.

Looks quite straight forward by set XKOMV-KINAK as blank for not the highest ZDEL item after comparing all item’s ZDEL amount with help of user exit like userexit_xkomv_bewerten_init at the program RV61AFZB. It’s working fine for normal order creation, but it’ll fail if any changes happen, as the inactive ZDEL at item level will not re-join the calculation process after it’s been set as inactive especially for group conditions.

Take below scale setting as an example:

Scale value from	Scale value to	Freight fee
1.0 GBP	1000.00 GBP	150 Eur
1000.01GBP	maximum	Free, no charge

If two items belong to the same condition group and the system can’t calculate per item directly and have to calculate the total quantity at the header level, then split the total freight fee into items level. If item 2’s quantity been changed and item 2’s ZDEL will been always inactive as haven’t waited for total quantity been sum, the result of ZDEL amount per item been compared too earlier which lead to the wrong item been selected as the highest ZDEL.

Even try to trigger new pricing by user exit userexit_new_pricing_vbkd at program MV45AFZB will not work after item changes. Cause loop XKOMV at userexit_xkomv_bewerten_init is triggered by earlier than group conditions calculation, it’s impossible to get which item contains the highest ZDEL at that time. The key debug point is to find where all ZDEL been calculated correctly at the function module: PRICING_COMPLETE. You can check this article for more details about this FM.

 

Thought 2. Using freight condition as statistics

There’re so many customer user exits existed for pricing process, I try many of them and didn’t find the right place to catch the “final” highest ZDEL. Even if it’s achievable by some enhancement or with the help of access key to modify the pricing calculation function, the above method still has a major issue as only the highest ZDEL item been collected into the header item. This means other items are free of charge, the header ZDEL amount from a specific item is not split into all items which leaves a huge potential problem for delivery processing.

From the above experience, we know that ZDEL must keep active status all the time during the calculation, otherwise, it’ll impact the calculation of header level ZDEL for special cases like group condition or exclusion been involved. So the new idea is:

ZDEL must keep active status but should not show at the header level, otherwise will be very confused for the user as so many freight conditions been listed at the header level. It can be done by set XKOMV-KINAK=’L’. For other values like ‘X’, it’s the inactive status(will display as Red traffic Icon)then it’ll impact the calculation of final ZDEL.

Plus set XKOMV-KSTAT = ‘X’ will help to set ZDEL which displays with statistic icon at the Item level.