on 02-24-2017 1:43 AM
Hi Everyone,
We have a special requirement to have few fields as mandatory fields when creating Pricing Condition records in VK11.
Fields like below needs to be made mandatory.
Max.condition value
Max.number.of.orders
Max.cond.base value
Any ideas on how this can be achieved.
Hello Veselina,
Thanks for ur alternative suggestion. I have the same to business but it did not work. So looking for guidance over here. 🙂
The problem you explained is extacly what I'm looking for.
So any other ways to mar this max condition base value field as mandatory?
My main intention is, Sales order needs to be in incomplete status after the value specified in MXKBAS is reached. Is there different way to achieve it?
Thanks
CR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My understanding was that you needed additional checks when the pricing condition is maintained - this is why I proposed to look into the BTE. Personally, I have not used it for this specific case, but from the explanation what the BTE is supposed to do, it seems like a possible solution. If for some reason the BTE does not perform as expected, probably your in-house developer can help you find out the reason.
Your requirement - to set the sales order to incomplete status once the maximum condition value is reached, is not how the functionality is supposed to work in standard: from what I know, the condition is applied until you reach the limit for value or number of orders, but the partial applying of the value (for example, if you have previously used up some of the discount in a sales order) or not applying the condition at all, does not lead to an incomplete document by itself.
I am not very convinced that it is a good idea to set the condition type as mandatory in the pricing procedure and try forcing document incompletion - after all, this is most probably some discount, agreed with a client, there is no reason to prevent additional orders without a discount from being processed. What is your exact business process? Are you trying to use this condition as some form of license or for product allocation purposes?
If I understood you correctly, this has nothing to do with the condition tables themselves, you need validations against KOMXWRT, ANZAUF and MXKBAS.
Explore BTE 00503305.
Read 325551 - Field check and field texts in condition tables.
Or, even cheaper, suggest to the client that if only the support team maintains pricing conditions via upload then they can skip the development completely 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
If you maintain the fields in condition table they will be mandatory by default in Condition record , by default.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
When you maintain the conditions in VK11, by default the fields are mandatory for key combination selected for it.
Regards,
Mukthar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
97 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
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.