Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

IDOC_INPUT_ORDERS

Former Member

‎2009 Oct 02 2:33 AM

0 Likes
817

Hey Guys,

My developer has built a logic to error out Incoming 850 Idoc in case of multiple Ship to Customers. This logic works fine when I process the Idoc (we19)in Background using standard function module IDOC_INPUT_ORDERS, however when I process the Idoc (we19) in foreground using the same function module the logic seems not working and the Idoc gets status 53. I am not sure why this is happng. Please advise.

Same function module giving different results when processed in foregroung and background.

Thanks

Sunny

Answers will be rewarded

4 REPLIES 4
Read only

Former Member

‎2009 Oct 02 5:15 AM

0 Likes
630

What do you mean Multiple Ship-to customers.

In VA01 there will be only one Ship-to customer. I am not sure what you are referring to Multiple-ship-to customers.

The user-exit will be triggered whether you execute the program through background or foreground.

In foreground may be you are missing/putting some correct data.

BTW, why do you worry about the foreground mode. Always your IDocs will be executed background. when it is working fine why worry about WE19/foreground. After all, it is a test tool.

Read only

Former Member
In response to Former Member

‎2009 Oct 02 1:07 PM

0 Likes
630

Creasy... Don't worry about the multiple ship to logic it has got nothing to do with my question. I repaeat my logic doesn't work when I process the Idoc in foreground.

Yes I have to worry... When my Idocs fail in background because of the condition not being fulfilled.. it's comes to my workflow, and I have to process them in foreground after assigning the correct Ship to.. but in thic case it doesn't stop at the error, but instead processes the Idoc Succesfully.

Sunny

Read only

Former Member
In response to Former Member

‎2009 Oct 03 11:49 PM

0 Likes
630

Which user exit did you use? Did you verify that it is not written within any condition that checks sy-batch = 'X'. Because if the code is written only for sy-batch = 'X', it will run only in background.

Read only

Former Member

‎2009 Oct 04 7:25 AM

0 Likes
630

Pikle is right. Check out the code whether the code in user-exit has dependency on batch mode flag SY-BATCH.

The multiple ship-to scenario is very akward to think of. Even if some outer system is sending the multiple Ship to. Logic should be built in Source or middleware to error out if such scenario exists.

Moreover, I would suggest to describe your scenario once more probably with code snippets also.

This will help us to get the hold of issue.