on 06-29-2018 10:10 PM
Hello,
We have a business process that if a customer orders more than say 10 quantities then we will waive off the freight charge.
But if the customer orders say 15 qty and we can confirm only 10 then we will not charge freight and open qty will be 5 which will be applicable for freight.
In such cases what business wants is that if same customer orders 5 qty again then we should combine the 5 qty open from previous order and deliver 10 qty so that freight is not charged.
I know we can combine multiple orders to create single delivery but how do we ensure that the pricing is also calculated based on total qty of combined order instead of individual orders.
I know it may be a bit confusing but that is how this requirement is and I would really appreciate any help that can point me in the correct direction.
Thanks,
Karan
I would suggest to enable the delivery pricing and using the group condition concept for the freight condition type along with scale thru which your requirement could also be acheived.
But you had given in your comments that this needs to be reflected at the sale order it self, which is possible by creating a new scale base value routine (which you can see in V/06 under the scales section). Below logic is based on the assumption that you have the freight value/percentage determined based on the scales.
If yes, then this scale base routine needs to have a logic which should consider any open orders of same material, date (or whatever check you have defined) and pick the qty from those order which needs to be added with your current order qty. Once this qty calculation happens, this qty has to be passed into KOMV-KSTBS, as this KSTBS is the scale base value that will be used in the condition records to determine the scale value.
In this case since you are passing the consolidated qty in KSTBS, and if that qty increases by 10 (as per your example) and if the scale is set to zero, then freight will not get determined.
Regards
Raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Raj,
Thanks for your inputs. As I am not aware of scales functionality, can you please explain what should be maintained in other fields under Scales in V/06. Should we maintain Scale Type as A - Base scale.
As KOMV is a structure so the value that we calculate from routine will be updated in KONV-KSTBS?
Thanks,
Karan
Through standard it is not possible to achieve this requirement. You need to go for pricing routine in VOFM where the code validation should happen for KWMENG from VBAP and assign this zee routine to that freight condition type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This way I can check KWMENG for respective order and decide whether freight needs to be applied or not. But how can I check whether the same customer already ordered some qty earlier which was not confirmed and I want to add that qty as will with current order to make it eligible for free freight.
Does it make sense what I am trying to say?
Suppose the cutoff for freight waiver is 20. I created order A with 30 qty and confirmed qty is 20 which will be delivered without any freight charge. Now there is an open qty of 10 which will get confirmed say next week.
In the meantime suppose customer sends another order for 15 qty. Since it is less then 20 so it will be applicable for freight. But Business wants that we should check that already there is open qty of 10 for this customer and material and now we got another order for 15. So total ordered qty is 25 which is more than 20 so freight should not be charged.
We can create two separate deliveries but they just want to make sure that we don't charge freight as long as total cumulative open qty is more than 20.
My doubt is how will system know to check cumulative open qty across multiple orders and determine whether freight is applicable or not.
User | Count |
---|---|
87 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.