Outbound processing for the ALE interface

The adapter supports outbound processing (from the adapter to the SAP server) for the ALE interface and the ALE pass-through IDoc interface. ALE uses IDocs for data exchange, and the adapter uses business objects to represent the IDocs.

The following list describes the sequence of processing actions that result from an outbound request that uses the ALE interface and ALE pass-through IDoc interface.

The message flow that makes the request uses the interface information that was generated by the Adapter Connection wizard.
  1. The adapter receives a request, which includes an IDoc business object, from a message flow.

    For pass-through IDocs, the Message tree contains a BLOB field that represents the IDoc. No separate IDoc business object exists for pass-through IDocs.

  2. The adapter uses the IDoc business object to populate the appropriate RFC-enabled function call used by the ALE interface.
  3. The adapter establishes an RFC connection to the ALE interface and passes the IDoc data to the SAP system. If you are using the qRFC protocol, the adapter passes the IDoc data in the order specified in the wrapper business object to the specified queue on the SAP server.
  4. After passing the data to SAP, the adapter performs one of the following steps:
    • If the call is not managed by a local transaction that uses the integration node's Local Transaction Manager, the adapter releases the connection to SAP and does not return any data to the caller. When no exceptions are raised, the outbound transaction is considered successful. You can verify whether the data is incorporated into the SAP application by inspecting the IDocs that have been generated in SAP.
    • If the call is managed by a local transaction that uses the integration node's Local Transaction Manager, the adapter returns the transaction ID.

      The adapter uses the tRFC protocol to support J2C local transactions.