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

Excluding idoc processing from user exit code

Former Member
0 Likes
552

Hi all,

In a user exit (for VA01 Create Sales Order) we are currently excluding certain order types by hardcoding the document type in the code. This is because some orders are created by IDoc and in this case the IDocs fail if they use the eser exit code (because the code creates pop-up messages intended for online users only). Not the best solution.

Does anybody know if we can use different code so that this part of the user exit does not get triggered by IDocs?

Thanks,

Mike

2 REPLIES 2
Read only

Former Member
0 Likes
491

I've figured out another solution - you can do a test on the field IDOC_NUMBER. If it is filled, then the sales order is created/changed via an Idoc.

Read only

Former Member
0 Likes
491

.