Remove pricing condition on pricing procedure

[Former Member]

Hi all,

I would like to remove an existing pricing condition on a pricing procedure. Can or should it be removed and the impact.

Any opinion would be greatful.

Thanks,

Rebella

[Former Member · Accepted solution]

Hi Rebella,

I think in stand of make it as a manual condition we can give the validity period of that condition so it will not affect after that period.Like if you don't want to use the condition on 5.02.2009 than change the validity period of that condition type in detail serean.

Thanks.

[Former Member]

Closed as no longer needed. Thanks for all

the opinions.

[former_member183879]

Hi,

My ideas on this.

A condition type entered in a pricing procedure should not be removed for any reason.

As already mentioned you can do one of the following.

1. If it is a manual condition type, dont enter the values from now onwards. Even you can enable a error message when the condition type has non-zero value in the condition screen.

2. Restrict the validity of the condition records if the condition type can be automatically determined.

3. Also another way can be to convert the c.type into statistical one in pricing procedure and remove the account key / accrual key whatever is applicable

After doing this, you can reprice all the open orders so that the correct values are present now.

Please let us know if there is any special concern.

[Lakshmipathi]

Dear Rebella

May I know the reason for that ??

Incidentally, I would like to caution you that it will hit all your existing open sale orders and you cannot generate billing.

Rather what I would suggest is that you make whatever changes in the existing procedure itself, close all open orders and create fresh sale orders.

If this does not address your requirement, you have to enlighten more on why you want to do so.

thanks

G. Lakshmipathi

[Former Member]

Dear G. Lakshmipathi,

The reason why I would like to remove the pricing condition was that the company has decieded that condition will no longer be allows to use. It is a manual entry condition, and we want to stop them from adding it in Sales order.

As you stated, we should not be remove it. Can we block it in someway at the pricing procedure so the user cannot add it in Sales order?

Thanks & Regards,

Rebella

Edited by: Rebella Rivera on Feb 4, 2009 3:21 AM

[Former Member]

Hi Rebella

It is not advisable to delete the Condition type from the Pricing procedure.

Just try this, it may work as it is a Manual condition, as you are saying.

If it is a Manual condition, then go to the condition type (V/06) and put value "D"(not possible to process manually) in the "Manual Entries " field.

I hope, this will work and at the same time it will not affect your other earlier processing while creating billing etc .

Next time, when you require this condition again, that time just remove the value D.

Remember in this process, the said Manual condition type will not be seen in the drop down(F4),so the End-user can not select the condition type , but if he remembers the condition type then he can make the entry( by typing) and system will accept it.

If it still does not serve your purpose, then in addition to the above seettings, in the Pricing procedure, remove the "tick mark"from the manual check box and save it.

Now, even if the End-user remembers the condition type and if he tries to enter the condition type by typing , then system will give error as "condition can not be enterd manually".

Please let me know, whether it is working or not.

Edited by: pradyumna on Feb 4, 2009 11:39 AM

[Former Member]

Hi pradyumna,

Thanks. It works BUT I got into another issue as the condition were being used in 2 different pricing procedure. If I changes it to "D"(not possible to process manually), then the other pricing procedure will not allows to use it also.

Let me update my requirement in a little more detail.

1. Condition are used in TWO pricing procedure

2. Want to disable the condtion in only ONE pricing procedure.

thanks,

Rebella

[Former Member]

In that case, remove the activation from the "Manual" check box and activate the "Statistical" check box for the Header condition type in the required Pricing procedure.

Now, even if the End-user will use the Condition type , still system wiil not take the condition type for net value calculation.

Hope, this may serve your purpose.