This sample demonstrates how to use two SAP nodes, the SAPInput node and the SAPReply node, to allow a message flow application to act as a synchronous BAPI. The customer details are received by the SAPInput node in the form of BAPI import parameters, processed by the Compute nodes and a response with the export parameters for the BAPI is sent back to the SAP system by the SAPReply node.
A single SAPInput node represents four BAPIs:
The sample has one main flow and a subflow that are generated by dragging the SAP inbound adapter onto the canvas:
Main flow:
Subflow:
All four BAPIs manipulate customer objects:
Within the message flow the customer details are stored inside an ESQL shared variable, which can be interchanged with a database.
The message is automatically routed to the correct label depending on which BAPI is called by the SAP system. The message is read, and a reply is constructed in one of the four Compute nodes. If an error occurs; for example, a customer does not exist, the appropriate fields are set in the return object.
The SAP call out to a synchronous system sample demonstrates the following tasks:
The sample provides: