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 status

Former Member
0 Likes
857

Hi Friends,

I have maintained all required system settings in the partners profile to trigger the IDocs immediately inorder make it process simultaneously. But, when Idoc comes from system instead of processing immediately it reaching the status 64 with particular Idoc.

Any suggestion on this would be appreciatable.

Thanks,

Punjaala

Thanks reply,

can let me know where exactly can I check the process mode and output mode?

Thanks,

punjaala

5 REPLIES 5
Read only

jaideepsharma
Active Contributor
0 Likes
832

Hi,

Status 64 in the IDoc can normally only occur in conjunction with processing mode 3 and output mode 2. Check the configuration in your system. Have you set Trigger immediately in the inbound options or it is Trigger by background program.

KR Jaideep,

Read only

0 Likes
832

Thanks reply,

can let me know where exactly can I check the process mode and output mode?

Thanks,

punjaala

Read only

Former Member
Read only

0 Likes
832

Hi,

go to tcode WE20. Choose your partner systems. In the inbound double click on your message type.

There you can see the Inbound parameters and under Inbound options tab you can find trigger immediately option.

If an IDocs remains in status 64, it means that the processing within the IDoc engines did not reach its end, where the new status could be set. There are two principal reasons:

1. In the matching partner profile the processing is not set to "Trigger immediately"

2. The application that processes the IDoc abnormally ends with a fatal error (crashes). If this happened you will see a trace in the system log (ST22).

KR Jaideep,

Read only

0 Likes
832

This was help full in my scenario.

Thanks.