About the SAP call out to a synchronous system sample

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:

Main flow

Subflow:

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:

  1. Configuring SAP to define an integration node endpoint (RFC Program ID)
  2. Configuring the integration node SAP adapter to communicate with your SAP system
  3. Rebuilding a BAR file with the newly configured adapter
  4. Deploying the BAR file
  5. Initiating SAP to call a BAPI that is implemented by a message flow
  6. Checking the export parameters that are returned to SAP from the message flow

The sample provides:

Back to sample home