Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

How to exclude a Condition type using Pricing routine.

Former Member
0 Likes
2,293

Hi Experts,

I have a small requirement. I need to check the sales order line item, the Higher level item catagory(vbap-UEPOS) more then '0'

( ZERO), for that line item i need to exclude one of our condiition type (ZZ10).

Can anyone help us. I have the pricing routine. My function consultant gave one sales order. Using that how to debug the pricing proccedure? if i change the quantity in one of the line item it will trigger the break point??

Can anyone pls help this issue?

Mohana.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,334

Get the routine number, go to transaction code VOFM and then put implicit debug in the routine code.

Regards

Vinod

Hi Experts,

I have a small requirement. I need to check the sales order line item, the Higher level item catagory(vbap-UEPOS) more then '0'

( ZERO), for that line item i need to exclude one of our condiition type (ZZ10).

Can anyone help us. I have the pricing routine. My function consultant gave one sales order. Using that how to debug the pricing proccedure? if i change the quantity in one of the line item it will trigger the break point??

Can anyone pls help this issue?

Mohana.

4 REPLIES 4
Read only

Former Member
0 Likes
1,334

Hi Mohana,

Put a breakpoint in pricing routine.

Regards,

Raj.

Read only

Former Member
0 Likes
1,334

Please create routine for requirement option in pricing procedure.

So that if the requirement meets, i.e. sy-subrc = 0. then only this condition will be displayed.

Read only

Jelena_Perfiljeva
Active Contributor
0 Likes
1,334

You can set a breakpoint in the VOFM routine. The routine will be called for the condition type it has been configured. Even if some code inside the routine is based on another condition, the routine will not be called for that condition.

Also don't forget to run the report RV80HGEN to generate the routine. Otherwise it won't work. You'll also need to run it in QAS and PRD.

Hope this helps.

Read only

Former Member
0 Likes
1,335

Get the routine number, go to transaction code VOFM and then put implicit debug in the routine code.

Regards

Vinod