Reply from jim-wolfe on Jan 18 at 11:28 AM Since a zero value loaded in the condition record is automatically outside of the upper & lower limit, I don't think you're going to be able to do what you're trying to do this way. The plus/minus configuration setting in the condition type only controls the sign of the condition record, not a manually entered value. I don't understand what you intend to happen if the condition record with a zero value is pulled into the order, but is not manually changed, i.e. stays at zero. Is that an error that should be caught? Or should the user delete the condition if the cost of installation is not applicable?
My recommendation is to attach a formula to the condition type in the pricing procedure to check for a negative value, and then set komp-cepok = 'B' if it is not, and add vbap-cepok to the incompletion procedure attached to the item category. Look at pricing formula routines 8 & 9 which do something similar (value check a manually entered condition) but for customer expected price.
| | | ---------------Original Message---------------
From: Laurie Crow
Sent: Wednesday, January 18, 2012 11:00 AM
Subject: Condition Type Upper and Lower Limits
The condition type is not a surcharge, it is statistical only, and checked as accrual to post cost of installation as quoted by the sales rep. Perhaps using upper or lower limit is not the correct technique, I agree.
Creating the condition record with a value of zero causes the condition type to appear when appropriate so my people do not have to remember to add it manually. Now I am looking for a way to force people to populate a value other than zero before the order can be saved and/or delivered.
Hope this clarifies. |
| Reply to this email to post your response. __.____._ |  _.____.__ |
