2009 Jun 12 5:18 PM
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
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
2009 Jun 12 5:27 PM
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,
2009 Jun 12 7:45 PM
Thanks reply,
can let me know where exactly can I check the process mode and output mode?
Thanks,
punjaala
2009 Jun 12 7:57 PM
2009 Jun 12 10:03 PM
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,
2009 Jul 17 11:57 AM
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |