topic Re: Issue when specific code is processed during a standard inbound Idoc in Application Development and Automation Discussions

Issue when specific code is processed during a standard inbound Idoc

Former Member — Thu, 12 Feb 2015 15:28:11 GMT

Hi Gurus,

I've a problem to submit to you : I've modified the standard FM IDOC_INPUT_ORDERS in order to insert two specific functions during input of the standard IDoc.

One function which aims at sending a mail including data of the input Idoc (using standard classes and methods),

another which aims at modifying the status of the created purchase order (using standard FM STATUS_UPDATE).

The fact is that this two specific codes run properly when I process an inbound IDoc through the transaction WE19. (all work perfectly : a mail is sent, and the statuses are moved as I want).

My problem is that, when this inbound IDoc is processed in an automatic mode, thanks to background processes, none of the two specifics are executed : no mail is sent, no status is updated...

I tried to add "COMMIT WORK..." or "WAIT UP TO...", expecting that this problem was created by a problem of buffer... But no effects...

Has somebody an idea to understand what happens, or, more, to correct this issue ?

Thanks in advance,

Pascal

Re: Issue when specific code is processed during a standard inbound Idoc

roberto_vacca2 — Thu, 12 Feb 2015 17:00:18 GMT

Hi.

If Mail is first process to be executed, probably it goes in error. What's the function used for mail sending?

I would call this function in a separate task.

Did you check out st22 for dumps?

Hope to help

Bye

Re: Issue when specific code is processed during a standard inbound Idoc

Former Member — Fri, 13 Feb 2015 07:48:13 GMT

Hello Roberto,

The fact is that the IDoc is processed : we can see it through WE02 as a green process. No dump...

I continue to check, and will come beck if i find others elements,

Pascal

Re: Issue when specific code is processed during a standard inbound Idoc

Former Member — Fri, 27 Feb 2015 09:25:05 GMT

Back of the damned abaper !

Sorry for the delay (I was in holidays).

The source of this dysfunction is very tricky : somewhere in the specific code, the table which contains the IDOC_CONTROL records is read in order to test the result of the process of the IDoc.

The fact is that the final IDoc status is not the same when you use "Standard Inbound" or "Inbound function module". In one case, the status is 53, in the other 64... So beware of the value you test !

Have a nice day !