Reply from LaurieCrow on Jan 19 at 1:46 PM Thank you for all of the input. My conclusion is that upper/lower limits will not work for my situation. First, because the limits not only control manual value entry, but also control the value on my condition record. If I set the limits so that $0.00 is not allowed, I will not be able to create a condition record with the value of $0.00.
My business requirement is:
--Condition type must appear on the conditions tab for ONLY the materials for which I have created condition records.
--The value for the condition type must be zero until the user changes it.
--The user MUST change it to something other than zero.
--It is necessary for the user to enter the correct value that is not zero. This value is not known by SAP in any way. It is a cost that is negotiated order-by-order with the installer vendor after a phone call.
Typewriter, to your points:
1. I have set the condition type field Manual entry = A Free. This is the only setting that causes the condition type to appear only for the materials that have condition records AND does not allow the condition type to be added to other materials manually. This is a huge improvement over my current situation where the condition type appears for all materials and it is a training issue to populate a value only for certain materials. (We also did not have an access sequence assigned previously).
2. On the pricing procedure, manual and required are both unchecked for this condition type. ( Required does not work for me because I only want it on 6 materials -- the ones with condition records. Manual does not work for me because I don't want the users to have to add it manually for those 6 materials, nor do I want them to be able to add it to any other materials.)
3. On the pricing procedure, statistical is checked because this condition type is for accruals only, it does not affect our charges to the customer.
I will look into the incompletion procedure suggestion. I am not familiar with procedure for CEPOK or PRSOK. I will also look at formulas 8 and 9. My own team suggests a report that runs every 30 minutes and sends a message to someone to fix the order. That would be my last resort. I would really rather have a hard stop message or an incomplete order so it has to be fixed before it is delivered.
| | | ---------------Original Message---------------
From: Laurie Crow
Sent: Monday, January 16, 2012 2:24 PM
Subject: Condition Type Upper and Lower Limits
I have a condition type that is set to Condition Class A-Discount or surcharge, Calculation Type B-Fixed amount and is Negative only. It has an access sequence so that I can create condition records for select materials at $0.00. This restricts the condition type to appear only on the selected materials and allows the dollar value to be entered manually during order entry, which is our business requirement.
I want to make it required that a value "greater than zero" be entered for this condition type but only if this condition type appears via the existing condition record. I have been unsuccessful using pricing procedure manual/required settings and also with condition type changesmanual entries settings.
So, I was hoping to use the condition upper and lower limits. However, I am having difficulty getting those settings set correctly because my values are all negative. I know that I have to stay on the same side of zero, but nothing I have tried is working. Lower Limit won't let me enter a positive nuber. Upper limit of $0.01 tells me that my condition record rate of $0.00 is no longer valid and automatically enters a value of -999999,999.00 in the Lower Limit field.
Can anyone help me with this? Or is there another way to accomplish my goal? |
| Reply to this email to post your response. __.____._ |  _.____.__ |
