Skip to Content

Pricing issue in the condition type, in Production

I have a problem in production. Lets say I create an order Va01 and go to item conditions. I have 2 discounts.

1. Z949-Mat Grp Discount, 2. Z952-General Discount

Both conditions are Active(green).

1st condition z949 has 0 % discount

2nd condition z952 has 30%-

So when User prints the order it shows 0% as the discount for that material.

By the way lets say I put 29%- instead of 0% it then becomes active the z952 becomes inactive which is what we want.

Question is why when one condition discount is 0% it shows it as being active which in reality 2 discount should not be active at the same time. So again the problem is in the 0% when I do put a digit other then 0 it works fine.

User is telling me that he wants 0% to show yellow as inactive.

Please help

Thanks in advance

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Sep 17, 2008 at 06:35 AM

    Hi Muhammad,

    Whether or not a condition with a 0 value shows in pricing, is controlled via pricing configuration. In your configuration for the condition type pls check what is entered in the field "Manual Entries" and let us know.

    Add comment
    10|10000 characters needed characters exceeded

    • Dear Kookie

      I would like to thank you very much in trying to help me. Though the manual entry thing helped me understand a few things. It can make changes to the system but the user wants to see some liniency with its printout. So it is definately an abap problem now. Because I just showed him (the user) what can be done in terms of functional side in the system. I told him why in the first place would u want to have 2 discounts 1 with 0% if ur not gonna use it in the first place. He saids lets just just asume for printing and showing customer to please them. So yes if u go to pricing procedure clicking the manual will allow the user to enter manually. So this is a very good observation u showed me.

      Though the problem is more of a script issue. Thank you once again.