Inbound IDoc with Inbound BAPI
The InboundIDocWithInboundBAPI example shows how to use the Subscription and the Request-Response Service services.
This example contains the Vendor process.
Once you update the VendorInputFile.xml file, the Vendor process is triggered. The Request-Response Service service invokes the BAPI_GL_ACC_EXISTENCECHECK functional module to validate the G/L account in the VendorInputFile.xml file.
You can find the VendorInputFile.xml file in the TIBCO_HOME\adapter\adr3\version_number\examples\BusinessWorks5\InboundIDocWithInboundBAPI directory.
If the G/L account in the VendorInputFile.xml file is valid, the Vendor process publishes a message to the adapter to create a vender based on the information in the VendorInputFile.xml file. Once the Subscription Service service receives the message as a CREMAS04 IDoc, the CREMAS04 IDoc is used to create a vendor in the SAP system.
If the G/L account is invalid, an error message is written to the output file.