Why is SAP Outbound Adapter is not picking up the IDocs when they are available in SM58 Queue in SAP?
Article ID: KB0094165
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
R/3 Adapter publisher gets the IDocs from the SM58 queue and the published IDocs which are lying in SM58 queue need to be republished by SAP for the TIBCO adapter for SAP to pick it up.
In case if the outbound adapter does not pick these idocs, execute transaction SMQS and we can find destinations which are registered. Setting the NO_TRFC parameter as ‘X’ for the corresponding destination prevents tRFC LUWs from being processed by the Outbound Scheduler. This means that the tRFCs for this destination are then executed when the Commit Work is executed.
Also, please check the SAP note: 527481 which explains the possible reasons for tRFC calls are not processed from SAP. Please check this with your BASIS team.
R/3 Adapter publisher gets the IDocs from the SM58 queue and the published IDocs which are lying in SM58 queue need to be republished by SAP for the TIBCO adapter for SAP to pick it up.
In case if the outbound adapter does not pick these idocs, execute transaction SMQS and we can find destinations which are registered. Setting the NO_TRFC parameter as ‘X’ for the corresponding destination prevents tRFC LUWs from being processed by the Outbound Scheduler. This means that the tRFCs for this destination are then executed when the Commit Work is executed.
Also, please check the SAP note: 527481 which explains the possible reasons for tRFC calls are not processed from SAP. Please check this with your BASIS team.
Issue/Introduction
Why is SAP Outbound Adapter is not picking up the IDocs when they are available in SM58 Queue in SAP?
Feedback
Yes
No
Powered by
