Outbound processing for the ALE interfaces

The adapter supports outbound processing (from the adapter to the SAP server) for the ALE 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 using the ALE interface.

Note: The client application that makes the request uses the interface information that was generated by the external service wizard.

The adapter receives a request, which includes an IDoc business object, from a client application.
The adapter uses the IDoc business object to populate the appropriate RFC-enabled function call used by the ALE interface.
The adapter establishes an RFC connection to the ALE interface and passes the IDoc data to the SAP system. If you are using the CWYAP_SAPAdapter_Tx.rar and have provided a Transaction ID, the adapter uses it while posting the IDocs to the SAP system. If you have not provided a Transaction ID, the adapter will create one before posting. 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. The adapter uses the same Transaction ID for all the IDocs in the wrapper and posts all of them using one call.
The adapter throws an exception if the data record is empty. Refer to ALE business object structure for more information on data records.
After passing the data to SAP, the adapter performs one of the following steps:
- If the call is not managed by a J2C local transaction, 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 J2C local transaction, the adapter returns the transaction ID.
  The adapter uses the tRFC protocol to support J2C local transactions.

Import the CWYAP_SAPAdapter_Tx.rar version of the adapter when you create a module that makes use of transactional (tRFC) or queued transactional (qRFC) processing.