IDoc Processing without Messaging Service
This section contains information on how to use the TIBCO ActiveMatrix BusinessWorks™ Plug-in for SAP Solutions IDoc activities without using messaging service, such as TIBCO Enterprise Message Service or Apache Kafka.
- Outbound IDoc Processing
For receiving IDocs from the SAP system, the IDoc Listener activity is used.
If no messaging service is used, then the Messaging Source field on the General tab of the IDoc Listener activity must be configured to NoMessaging.
When the IDoc is received from the SAP system, the raw IDoc is provided as output.Note:- When multiple IDocs are received in batch, a job is created for each IDoc.
- Confirmation to SAP is given only when the output from the IDoc Listener activity is successful. After the output is successful, to avoid any loss of IDoc data in subsequent processing, TIBCO recommends that you configure the project accordingly to make it resilient if there is any disruption or errors during the processing.
If the IDoc received requires to be transformed to XML, then the IDoc Converter activity is required. The transformation to XML by the IDoc Converter activity is consistent to that of the IDoc Parser activity.
- Inbound IDoc Processing
To post IDocs to the SAP system without requiring TIBCO Enterprise Message Service, the Post IDoc to SAP activity is used.
The Post IDoc to SAP activity receives IDoc in XML as input or raw IDoc format and sends the IDoc to the SAP system. The processing and posting of IDoc to SAP system is consistent to the IDoc Reader activity that requires TIBCO Enterprise Message Service.
If IDoc Confirmation mode is required to post IDoc to SAP system then the IDoc Confirmation Mode field in the Advanced tab of Post IDoc to SAP activity must be configured to NoMessaging, for IDoc Confirmation Mode to provide confirmation of the IDoc as part of the output activity.