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

IDoc is not getting processed automatically

Former Member
0 Likes
1,364

Hi,

IDoc is not getting processed automatically, it is getting stopped 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.

6 REPLIES 6
Read only

Former Member
0 Likes
1,096

Hi,

Just check the partner profile setup in WE20.

There maybe some sender and receiver related config needed.

Hope it works.

Thanks,

Sandeep.

Read only

Former Member
0 Likes
1,096

Hi,

check once the RFC destinations and partner profile settings.

then go to we19 for error processing.

Thanks,

usha

Read only

Former Member
0 Likes
1,096

Try to execute idoc with 64 in program:RBDAPP01.

If posted successfully, then you have change partner profile(WE20) settings from Trigger by background program to Trigger immediatly.

Thanks,

Narayan

Read only

0 Likes
1,096

Once the inbound Idoc is created then you have to process it using transaction BD20 (i.e., through the program RBDAPP01). you can set up the back ground job for the particular message type/ partner etc.,

Thanks,

Srinivas

Read only

0 Likes
1,096

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.

Read only

Former Member
0 Likes
1,096

Hi,

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