Scenarios for qRFC
Definition
The usage of qRFC functionality for IDoc processing requires specific adaptions on the server as well as on the client side of the JRA component:
Server Scenario (qRFC)
The function module IDOC_INBOUND_IN_QUEUE needs to be considered when dealing with IDocs sent by an ABAP Client. To handle such calls from an ABAP Client, a new Listener interface com.sap.mw.jco.jra.QueuedIDocMessageListener has to be introduced to JRA. This Listener extends the already existing com.sap.mw.jco.jra.IDocMessageListener and needs to be implemented by a message driven bean dealing with queued IDocs.
Client Scenario (qRFC)
On the client side the affected APIs do consider now the queue that processes the call on the backend. The constant IDOC_VERSION_QUEUED has been introduced to identify queued processing. Using queued IDocs requires an interaction specification with the parameters TID and queue name to identify the target inbound queue on the backend. Use the API ConnectionFactoryImpl.createInteractionSpec(String tid, String queueName) for that purpose. To the Mapped Record, which holds the IDoc, the key-value pair JRAIDocMappedRecord.IDOCDOCUMENT_VERSION / JRAIDocMappedRecord.IDOCDOCUMENT_VERSION also needs to be added.
More Information