IDoc is not getting processed automatically

[Former Member]

Hi,

IDoc is not getting processed automatically, it is getting stoped with "Status record" as 64, then I manually run WE19 transaction.

Could you please tell me why it's happening?

Thanks in advance.

Regards,

Balaji Viswanath.

[Former Member]

Hi,

IDoc is not getting processed automatically, it is getting stoped with "Status record" as 64, then I manually run WE19 transaction.

Could you please tell me why it's happening?

Thanks in advance.

Regards,

Balaji Viswanath.

[Former Member]

Hi,

First.

goto WE20 , select ur logical system , select ur inbound parameter & click on the choose button.

then under the tab "Process by function module", choose the Trigger Immdiately" radio button.

try this .. suppose , if it doesnt work ...let usknow

reward points if it is Useful.

Thanks,

Manjunath MS

[Former Member]

Hi Manjunath,

Sorry, I forgot to mention in my question. "Trigger Immediately" option is already selected but still IDoc is not getting processed immediately.

Regards,

Balaji Viswanath.

[Former Member]

Hi,

execute this program <b>RBDAPP01</b>. In the selection screen , give IDOC status & message type .

i Hope this will work.

Thanks,

Manjunath MS

[Former Member]

Thanks Manjunath, it worked.

But my question is why should we run the program RBDAPP01, will it not be processed automatically. Is there any way I can achieve the same result without executing RBDAPP01 program.

Regards,

Balaji Viswanath.

[Former Member]

by having "Trigger Immediately" in your partner profile, your inbound IDoc should be processed immediately.. unless you encounter resource issues then it may get stuck in the tRFC/qRFC queue.

we've run into instances where we are trying to send too many idocs so although we have "trigger immediately", we have RBDAPP01 scheduled as well to clean up any outstanding idocs.

[Former Member]

also, you can use BD87 to process them instead of WE19

[Former Member]

Hi,

If I pass "pi_do_commit = 'X'" parameter to IDOC_INBOUND_SINGLE then IDocs are getting processed immediately without running RBDAPP01 program manually. But the processing is not successful because BOM is getting locked by my user id itself and I am getting an error message in application log saying "BOM 0000027193/000010/19XR 2000 3 is locked by <myuserid>". Actually I am not locking the Sales Order BOM through any transaction. How to overcome this issue?

Thanks in advance.

Regards,

Balaji Viswanath.

[Former Member]

Hi,

I sign-out and sign-in into SAP and above problem got resolved.

[Former Member]

Hi,

I sign-out and sign-in into SAP and above problem got resolved.