Coding Client Applications and Services

Adapter for SAP has several APIs that you can use in your client applications and services. This chapter shows how to use the built-in services API to invoke SAP RFCs, send IDocs to an SAP system and to receive an IDoc from an SAP system. For descriptions of the available built-in services, refer to Built-in Services.

For more information about building the Java services, see the online API documentation installed with Integration Server at: Integration Server_directory\instances\instance_name\doc\api\Java\index.html

This chapter also shows how to use IBM webMethods Adapter for SAP IDoc Java API to construct an IDoc. For information, refer to packages_directory\WmSAP\pub\doc\api\index.html.

To receive an IDoc from an SAP system and pass it to a service, you can setup an synchronous ALE adapter notification or a routing notification. In either case, you need to assign the service you would like to invoke to the notification. For instructions on establishing routing notifications, refer to Routing Notifications. When choosing the transport for the routing notification, select the IS transport. For instructions on establishing asynchronous ALE listener notifications, refer to Creating a Synchronous RFC Adapter Notification.

When executing HTTP Posts using IDoc-XML and XRFC with transactions, you should make sure that your client correctly handles such calls. It should have transaction management that supports at least the following features:

• Transaction ID generation.
• Resending documents with same transaction ID in error cases.
• After a successful execution of a transaction, a document cannot be sent again.

To transfer the transaction ID to Adapter for SAP, you add an extra header to the HTTP POST, x-tid, that contains the transaction ID.

This example demonstrates how to call a BAPI asynchronously from an SAP system over the Web. For this purpose, you have to create an ABAP program inside the SAP system. This program calls the proxy function module to generate an ALE message for a BAPI. After performing a COMMIT WORKcommand, the SAP system will generate an IDoc through the ALE service layer and send it to Adapter for SAP. There the IDoc will be transformed into the original BAPI representation and sent as XML using HTTP to any remote web system.

To run an example, you should set up your SAP system for ALE processing as described in the SAP system documentation and in this guide. When defining the partner profile for the outgoing IDoc in the SAP system, ensure that the option Transfer IDoc immediatelyis selected because the BAPI conversion tool on Adapter for SAP does not support IDoc packages.

Create the following report in your SAP system to test the BAPI conversion with the BAPI Bank.Create(available as of SAP release 4.6C).

REPORT Z_BAPI_ALE_DEMO .  
parameters receiver like BDI_LOGSYS-LOGSYS.  
parameters country like BAPI1011_KEY-BANK_CTRY default 'DE'.  
parameters bankkey like BAPI1011_KEY-BANK_KEY default '34981255'.  
data: receivers like BDI_LOGSYS occurs 0 with header line,  
      address like BAPI1011_ADDRESS.  
*prepare the distribution information  
move receiver to receivers-LOGSYS.  
append receivers.  
*prepare the BANK addres parameter  
address-BANK_NAME = 'Demo Bank'.  
address-REGION = 'BW'.  
address-STREET = 'Neurottstr. 16'.  
address-CITY = 'Walldorf'.  
address-SWIFT_CODE = 'ABCDDE12'.  
address-BANK_GROUP = 'SB'.  
address-BANK_NO = '12345678'.  
address-ADDR_NO = '123'.  
*send data to ALE  
CALL FUNCTION 'ALE_BANK_CREATE'  
  EXPORTING  
   BANKCTRY = country  
   BANKKEY = bankkey  
   BANKADDRESS = address  
  TABLES  
   RECEIVERS = receivers  
  EXCEPTIONS  
   ERROR_CREATING_IDOCS = 1  
   OTHERS = 2  
.  
IF SY-SUBRC <> 0.  
  write: / 'IDoc could not be created'.  
ELSE.  
  write: / 'IDoc successfully created'.  
ENDIF.  
*trigger processing  
commit work and wait.