RE:[sap-log-sd] Condition Type Upper and Lower Limits

Reply from Typewriter on Jan 18 at 11:40 AM
Hi Laurie,

I have tested this requirement SUCCESSFULLY.

There were absolutely NO problems!

The configuration and steps used for testing are as follows -
1. In V/06, for K004, field Plus/Minus = A (positive), field Manual entry = No limitations
2. In VK11, for K004, value = 1 EUR (or 0 EUR) for a specific S Org., D channel and Material
3. In VA01, for a cmr and this particular material, at line item level -
- K004 is populating with relevant price (from the condition record data)
- I can change this value to ANY value
and then save the sales order.

FYI - In V/08, in my pricing procedure, Mandatory, Required and Statistics are de-activated.

PS - If you are marking a condition type as STATISTICAL, in the pricing procedure, then that would not add up in your Net value.

Please comment, if I have missed something.

---------------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.
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
Copyright © 2012 and message author. 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251

Mark as helpful
View this online
Ask a new question
In the Spotlight
Become a blogger at and share your expertise with the community. Start today.