How does the interaction between R/3 adapter (publication service) and SAP Application server happen while receiving an IDoc from SAP system?
Article ID: KB0092391
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
When the SAP transaction we19 (this is a test transaction used to publish IDoc from SAP system) is executed, the IDoc is first moved into the sm58 queue by SAP, from here they are picked up by the clients (example TIBCO adapter for SAP). The various stages of processing and pre-processing that an IDoc goes through can be monitored from this transaction (sm58).
The SAP R/3 adapter polls this sm58 queue for new IDoc on a configured port. Once the IDoc is successfully picked up from this sm58 queue (by the adapter), it is removed from the queue. If due to some issue the IDoc is not picked up by the client (TIBCO Adapter for SAP), it will continue to remain in the sm58 queue and the status will indicate error/time out as appropriate.
In case of error scenario, the IDocs that were published by SAP in the duration of error will remain in the sm58 queue, with an entry indicating the cause of error. Once the adapter has re-established connection or the error has been overcome, the IDocs left out in sm58 queue will have to be re-published for the adapter to pick them up. This can be done by using the “Execute LUW” function of the sm58 queue. In this way we can ensure all IDocs are successfully processed.
When the SAP transaction we19 (this is a test transaction used to publish IDoc from SAP system) is executed, the IDoc is first moved into the sm58 queue by SAP, from here they are picked up by the clients (example TIBCO adapter for SAP). The various stages of processing and pre-processing that an IDoc goes through can be monitored from this transaction (sm58).
The SAP R/3 adapter polls this sm58 queue for new IDoc on a configured port. Once the IDoc is successfully picked up from this sm58 queue (by the adapter), it is removed from the queue. If due to some issue the IDoc is not picked up by the client (TIBCO Adapter for SAP), it will continue to remain in the sm58 queue and the status will indicate error/time out as appropriate.
In case of error scenario, the IDocs that were published by SAP in the duration of error will remain in the sm58 queue, with an entry indicating the cause of error. Once the adapter has re-established connection or the error has been overcome, the IDocs left out in sm58 queue will have to be re-published for the adapter to pick them up. This can be done by using the “Execute LUW” function of the sm58 queue. In this way we can ensure all IDocs are successfully processed.
Issue/Introduction
How does the interaction between R/3 adapter (publication service) and SAP Application server happen while receiving an IDoc from SAP system?
Feedback
Yes
No
Powered by
