Reply from jim-wolfe on Jan 18 at 11:58 AM Correction, the plus/minus field does control manual entry also
| | | ---------------Original Message---------------
From: Jim Wolfe
Sent: Wednesday, January 18, 2012 11:29 AM
Subject: Condition Type Upper and Lower Limits
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. |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.  _.____.__ |
