Value of Manual Pricing Condition is becoming zero while saving.

[Former Member]

My clientu2019s pricing calculation requirement is complex. Here I am mentioning :-

We have one pricing condition type YPR4 which is header as well as item condition. Value will come only from condition record . So, we maintained access sequence in the configuration. Beside this we maintained u2018Manual entries u2018 in the configuration as u2018Not possible to process manuallyu2019. Condition record for this pricing condition type we maintain for line items.

We have another pricing condition type Y255 which is also Item condition as well as header condition. For this pricing condition value ( header level) can come from condition records if record exist , or , if condition record is not there or if user wants, user can enter value in header level of the sales order. For getting this functionality we maintained access sequence and u2018Manual Entryu2019 in the condition type configuration we have maintained as u2018No Limitationu2019.

In the line item level Y255 will come only if YPR4 is there for that item. The total value of the Y255 in the header will need to be distributed in the line items accordingly as per existence of YPR4 in the line item.

Issue:

Now the issue is that, when there no condition record for Y255 and when we are entering the value of Y255 manually in the header, the value of Y255 is becoming zero when we are moving from one screen to another screen in the same sales order , or when we are saving the sales order..

Can anybody suggest what we need to do so that manually entered value of Y255 remains in the sales order after moving to another screen or after saving the sales order ?

[Former Member]

Hi ,

Please check the pricing routines funcationality which is assigned to both condition types.check the requirement and alt.cal. type routines of Y225 condition , on what basis condition record is updating manully entry as well as picking value from condition records.