Subtotal 3 vbrp-kzwi3 does not populate randomly

[Former Member]

We have a pricing condition where subtotal 3 appears on two conditions at the line item (Znet and zrr0) we would expect the two conditions to sum into subtotals 3. In our case, the second condition which uses a custom routine 999 is actually not valid for most billing documents and so the condition does not show up in the pricing of the line item as expected.  Everything looks ok, but once in a while the subtotal 3 vbrp-kzwi3 is zero even though vbap-kzwi3 is correctly equal to znet.  When we run ovg1 on this billing doc the subtotal 3 reappears correctly as znet  

We suspect it might have something to do with the subtotal being entered twice in the pricing procedure.

This is the Sales Pricing procedure and all the docs that have error seem to use this pricing procedure but it doesn't happen frequently.

it is hard to debug as it is difficult to replicate. Is there a bug in SAP or any ideas what it might be?  We are on 4.7 SAP. Many thanks!

[phanikumar_v3]

as per you --you are facing this problem only in occasional cases...

Can you please provide screen shot of your pricing procedure and also ZNET,ZRR0 with and without condition values in sales order pricing..

Phanikumar

[Lakshmipathi]

If any issue is occurring on a regular basis, then you can revisit your configuration / customization / master data.  But with the same settings, if the issue is happening once in a while, then, as you said, it will be very difficult to identify the root cause.  Hope, in normal circumstances, you should be knowing how to populate a value in Subtotal 3.

G. Lakshmipathi

[Former Member]

further to what lakshmi said check few things

1. Are your both condition types using sub-total 3 are of same condition class ? If different use different sub-totals.

2. Check if Zrr0 condition record removed manually in issue cases ?

3. Re-visit steps in pricing procedure on what basis value these condition types are calcualted from and also check if any calcualtion routines used against these condition types.

This is to provide a view for functional checks. As i can understand difficulty of debugging in these cases.

thanks

rama