Pricing requirement routine

[Former Member]

Hi,

I have a requirement wherein to be able to execute step 20 of my pricing procedure, step 10 condition value should be greater than 550.

I am moving the condition value of step 10 to subtotal field XWORKD (D)

I created a pricing requirement routine and attached it to step 20.In the routine I check if XWORKD >550.

This does not work. The system always supresses step 20 condition record, even if the requirement is satisfied.

Upon debugging, I see that XWORKD is not populated when the requirement is checked, hence the requirement always fails.

Can someone tell me to which subtotal field to move the step 10 condition value so that it is available during the requirement check.

I tried using KOMP-KZWI1, but see that this has the condition value of the step 20 condition record.

Can someone help me out?

I also want to know the difference between FORM KOBED and FORM KOBEV, while coding the requirement routine.

What is the significance?

Thanks

[christian_wohlfahrt]

Hi Anand!

The requirements are executed BEFORE condition determination -> your check is to early.

KOBED is executed <i>very</i> early on a header level, so if you can define a test just with header fields (e.g. never this condition in sales org x), it's faster to fill this already in KOBED.

All checks should also be repeated in KOBEV, that's executed on line level - but depending on transaction and circumstances, the execution is not necessarily header/position.

Exclusion groups won't help you either, so I (currently) only see one option: use a condition formula. In here you are allowed to change the condition value of line 20 - just set this to zero in case your requirement is not fulfilled. There is also a flag, with which you can set this line inactive, should be called KINAC or something like this. Just have a look in some standard formulas to search for the correct name (and usage).

Regards,

Christian