Pricing: Provide override for mandatory condition

[Former Member]

Dear All.

We have a mandatory condition in our pricing procedure. And we would like it to be Mandatory some 99% of the time.

However, in rare cases with approval we would like it to not be mandatory for a specific sales order. Probably based on manager approval.

Has anyone done anything like this?

Any ideas?

The field comes from T683s-kobli.

Not sure if there's any standard configuration that would let us do this?

But possibly we could use a pricing requirement or other? Or user exit?

A manager could add some value to the sales order that we could key off of, and check which would allow the mandatory check to be skipped?

Thoughts?

Many Thanks.

[Former Member · Accepted solution]

You need to identify one field in the sales transaction which will not consider the Condition to be Mandatory in that particular business scenario. Let say you create a Price Group (Manager override - 03). In this particular business scenario the Manager will give the price group as 03 i.e. Manager Override @ the Header Level. This price group will ensure not to trigger that particular condition type. Create a requirement routine & assign it in the pricing procedure for that mandatory condition type.

Try this pseudocode in the requirement routine:

sy-subrc = 4.

if komp-kposn ne 0.

check: komk-konda ne '03'. (*Create a price group 03 as mentioned above)

endif.

sy-subrc = 0.

[Former Member]

Hi,

Try to Use the Requirement in the pricing procedure like RV60C602. 602 is the number u need to keep in the pricing procedure opposite to the condition type . When ever u dont want that specific condition type then make it STATIC in the exit.

Please correct me if i m wrong......

Regards,

Srinivas

[Former Member]

Thank you Srinivas.

We'll give that a try, see if we can suppress the condition in the pricing procedure.

Not sure if we'll still get the error message or not as it's a mandatory condition. But if it works it would be an easy solution.

Thanks!

[Former Member]

602 appears to be a custom routine and not provided by SAP. There is no standard routine to address this requirement. you will have to go for development. Please work with your ABAP person, please write logic to make the condition type "Statisical" based on some parameters or user profile.

Also you can look at the user exit MV61AFZA to determine the pricing rule during order processing.

Regards

Sai