Adapter Connections

Overview

This chapter describes how to configure and manage Adapter for SAP connections. For more information about how adapter connections work, see Adapter Connections.

Before Configuring or Managing Adapter Connections

About this task

To prepare to configure or manage adapter connections

Procedure

  1. Install IBM webMethods Integration Server and Adapter for SAP on the same machine. See Installing, Upgrading, and Uninstalling the adapter for details.
  2. Make sure you have webMethods administrator privileges so that you can access Adapter for SAP's administrative screens. For information about setting user privileges, see IBM webMethods Integration Server Administrator’s Guide for your release.
  3. Start your Integration Server and Integration Server Administrator, if they are not already running.
  4. Using Integration Server Administrator, make sure the WmSAP package is enabled. See Enabling Packages for instructions.
  5. Using Designer, create a user-defined package to contain the connection, if you have not already done so. For more information about managing packages for the adapter, see Managing the Adapter Package.

Configuring Adapter Connections

About this task

Use the following procedure to define the parameters that Adapter for SAP will use to establish a connection to an SAP system. Adapter for SAP requires a connection to the SAP system whenever functionality from the SAP system is to be invoked; that is whenever Adapter for SAP acts as a client for an SAP system. But also when Adapter for SAP receives a call from an SAP system, it needs to make a call back to the calling system to look up the function interface or IDoc definition from the SAP Data Dictionary (DDIC).

To configure an adapter connection

Procedure

  1. In the Adapters menu in the Integration Server Administrator navigation area, click IBM webMethods Adapter for SAP.
  2. On the Connections screen, click Configure New Connection.
  3. On the Connection Type screen, click RFC Connection as the connection type.
  4. For a basic connection, complete the following fields in IBM webMethods Adapter for SAP section:
    Field Description/Action
    Package Package in which to create the connection. You must create the package using Designer before you use in this parameter. For information about creating packages, see IBM webMethods Service Development Help for your release.
    Note: Configure the connection in a user-defined package rather than in the adapter's package. See Package Management for other important considerations when creating packages for Adapter for SAP.
    Folder Name Folder in which to create the connection.
  5. In the Connection Properties section, complete the following fields using the values from your configured SAP system:
    Field Description/Action
    Connection Alias RFC connection name. This is the name by which the SAP system are known to Adapter for SAP developers, clients, and partners.
    Note: The Connection Alias must be unique for each connection.
    User Name SAP default user for this RFC adapter connection. If no other SAP user name is provided during runtime then this SAP user account is used to execute the client request in the SAP System.
    Note: The default user of Adapter for SAP Connection is also used to execute lookups to the DDIC for RFC, BOR and ALE metadata. So, it is necessary to set an SAP logon user with the authorization to the following SAP standard function groups: RFC1, SDIF, SG00, and SRFC.

    It is a recommended best practice to set a technical SAP user account with the minimum necessary set of authorizations as the SAP default user. If the execution of an RFC adapter service requires additional access rights then the name of an SAP user with sufficient rights must be passed during runtime.

    Password SAP password of the default user.
    Repository User Name SAP repository user for this RFC adapter connection. If a repository user is provided, all meta data and repository lookups are executed with this user account. This field is optional.
    Repository Password Password of the SAP user specified in the Repository User Name field.
    Client Three-digit SAP client number.
    Language(optional) SAP language code. This field is optional. If connecting to a version 3 SAP system, this is one character. For a version 4 or later SAP system, it is two characters.
  6. To configure logon properties, complete one of the following steps:
    • Complete the following fields to set up the group logon:
      Field Description/Action
      Load Balancing
      • Select On to activate the group login concept. Complete the remaining fields in the section.
      • Select Off to connect to one dedicated application server. Skip to "Complete the following fields to set up the single server logon:" in step 6.
      Logon Group Name of the group you want to login.
      Message Server Host Host name or IP address of the message server.
      Message Server Service Optional. Message server service or port number. Message Server Service can be used instead of the System ID field.
      System ID Optional. System ID of the SAP system or SID. System ID field can be used instead of the Message Server Service field.
    • Complete the following fields to set up the single server logon:
      Field Description/Action
      Application Server IP address or host name of the SAP system.
      System Number SAP system number (00-99).
    • Complete the following fields if you are using an external RFC Server:
      Important:
      • The settings must point either to the Gateway at which this RFC server is registered or to the Repository Server selected.
      • The load balancing and single server logon settings are ignored if you configure an RFC server.
      Field Description/Action
      External RFC Server
      • Select On to use an external RFC server. Complete the remaining fields in the section.
      • Select Off if you do not want to connect use an external RFC server.
      Program ID Program ID of the external RFC Server
      Gateway Host Gateway Host for accessing your RFC Server. Must be the IP- or DN-address of the Gateway the RFC Server is registered on.
      Gateway Service Value corresponds to the system number of the RFC Server. The format is sapgwXXX, where XX is a value from 00 to 99.

      For example: sapgw07 or sapgw00s

      Repository Server Value is the SAP server taken from the existing SAP system list. All repository lookups such as metadata lookups for structures and function interfaces are done there. This helps using third-party RFC Servers from Adapter for SAP as client. They can provide their functionality without being extended by a specific interface, for example: RFC_GET_FUNCTION_INTERFACE
      Note: Any server program that is enabled for RFC communication can be an external RFC Server. In order to use an external RFC Server with Adapter for SAP, the RFC Server must implement at least the following function modules:
      • RFC_FUNCTION_SEARCH
      • RFC_GET_FUNCTION_INTERFACE
      • RFC_GET_STRUCTURE_DEFINITION (if the server is running with a 3.x Lib)
      • DDIF_FIELDINFO_GET (if the server is running with a 4.x Lib)

      The last three function modules are required only if the RFC Server is to be its own Repository Server.

  7. Complete the following fields to enable security(Optional):
    Field Description/Action
    SNC Enabled Determines whether this server should use Secure Network Communications (SNC). Possible Values are:
    • Yes.
    • No. Default
    SNC Quality of Service SNC Quality of service, possible values:
    • Use global built-in default settings.
    • Plain text, but authorization.
    • Each data packet will be integrity protected.
    • Each data packet will be privacy protected.
    • Use maximum available security.
    SNC Name Your own SNC name if you do not want to use the default SNC name. This is the name you chose when generating a Personal Security Environment (PSE).
    SNC Partner Name SNC name of the SNC partner (RFC server) or SNC name of the message server (Load Balancing).
    SNC Authentication Select one of the following possible SNC authentication types:
    • User and Password. Uses the username and password fields for authentication. If the SNC mode is enabled, then SNC is specifically used to encrypt the connection data and not for authentication. SSO authentication is not used.
    • SNC Credential. Uses the credential in the SNC PSE file for the authentication if the SNC mode is enabled.
      Note: At runtime, if a valid X.509 certificate is available in the current HTTPS Integration Server session, the X.509 certificate takes precedence over the credentials in the SNC PSE file.
    • X.509 Certificate. Uses the X.509 certificate available in the current HTTPS Integration Server session for authentication.
      Note: At runtime, if a valid X.509 certificate is not available in the current HTTPS Integration Server session and the SNC mode is enabled, the credentials in the SNC PSE file is used for authentication.
  8. Optionally, set SAP Router String:
    Field Description/Action
    SAP Router String SAP router string. The router string contains a substring for each SAP Router to set up a connection in the route: the host name, the port name, and the password, if one was given.

    For example: /H/127.0.0.1/H/, where H indicates the host name.

    The SAP router string is only needed if a firewall exists between the SAP System and Integration Server. For more information on configuring the SAP router, go to the SAP Service Marketplace at: http://service.sap.com/connectors.

  9. Optionally, complete the advanced settings for the connection:
    Field Description/Action
    Use SAPGui Run with/without/hide the SAP GUI between two RFC functions. Possible values are:
    • Off. Default. Run without SAP GUI between two RFC functions.
    • On. Run with SAP GUI between two RFC functions.
    • Hidden. Run an invisible SAP GUI between two RFC functions.
    RFC Trace Enables the creation of RFC trace information for this client connection. Possible values are:
    • Off. Default.
    • On.

    For detailed information on using the RFC trace, see Logging and Monitoring.

    Log Transaction Status Switch to save the processed logs. Possible values are:
    • Off. Default. Processed logs are not saved, although a transaction is created (or maintained), and the transaction can be monitored later on in the transaction list.
      Tip: Setting this switch to Off reduces the amount of disk space needed and the time it takes to log the transaction status. It still allows you to check the current transaction status on Adapter for SAP.
    • On.
    Store Message Body Switch to store the message body of the incoming document to disk. Possible values are:
    • Off. Default. Message body of the incoming document is not stored to disk, although a transaction is created (or maintained), and the transaction can be monitored later on in the transaction list.
      Tip: Setting this switch to Off reduces the amount of disk space needed and the time it takes to persist the message body. It still allows you to track the message status on Adapter for SAP.
    • On.
    Note: IBM webMethods Adapter 10.1 for SAP does not support the ABAP Debugger utility. Instead, use the external debugger provided with SAP 6.2 and later versions.
  10. Click Save Connection to commit these changes.

Setting Up the SAP System for SNC Connections

If you want to use SNC connections with the SAP system, you must configure the SAP system to accept both SNC and non-SNC connections from Adapter for SAP.

When connecting to the SAP system, Adapter for SAP creates two types of connection pools for each connection alias: an SAP repository connection pool and an SAP runtime connection pool. The following table describes each adapter connection pool.

Connection Pool Type Description
Repository
  • Used internally for metadata lookup
  • No business data is processed over the connections
  • Supports both RFC and SNC connections
Runtime
  • Managed by the Adapter Runtime
  • All business data is processed over the connections
  • Supports both RFC and SNC connections

To use SNC connections, you must configure the following settings in the SAP system.

SAP system settings for SNC Table/Parameter
General SAP system settings for SNC: Table SNCSYSACL (SM30, view VSNCSYSACL, TYP=E)

SNC name entry of Adapter for SAP.

Certificate log in: General Settings:
  • Profile Parameter:
    • SNC/libsapsecu=./libsecude.sl (for HP-UX)
    • SNC/extid_login_diag=1
    • SNC/extid_login_rfc=1
  • Table SNCSYSACL (SM30, view VSNCSYSACL, TYP=E), activate:
    • Certificate log in
    • Diag
    • RFC
Certificate log in: User specific settings: Table USREXTID (view VUSREXTID), Category DN

Entry with DN (Distinguished Name) from user certificate

The Seq.No. 000 is the default entry.

Set entry active.

For detailed information about the SAP application server settings for SNC, see your SAP documentation.

Dynamically Changing a Service's Connection at Run Time

For Adapter for SAP, you can change the service's connection in one of two ways.

The adapter services that ship with Adapter for SAP in the WmSAP package in the pub.sap namespace include a field called serverName. By using this field, you can specify at run time the SAP system to be updated.

Additionally, Integration Server enables you to override the default connection associated with the service at design time. To override the default, you must code your flow to pass a value through the pipeline into a service's $connectionName field.

For example, you have a flow whose primary purpose is to create an entry on the production SAP system. However, you want the flow to have the capability to create the entry on the test server, with the decision of which SAP system to update to be made programmatically at run time. The output signature of the flow's first service contains a field called Target. The flow could branch based on the value in Target.

  • If Target contains the value "production," the second service in the flow would ignore $connectionName-thus using its default connection to connect to (and then update) the production SAP system.
  • However, if Target contains the value "test," the second service in the flow would use the value in the $connectionName from the pipeline and connect to (and then update) the test SAP system.

Keep in mind that both connections-the default and override-must have the same SAP classes and methods metadata, RFCs, and BAPIs.

For more information, see Changing the Connection Associated with an Adapter Service at Run Time.

Enabling Adapter Connections

About this task

A connection must be enabled before you can configure any adapter service using the connection, or before an adapter service can use the connection at run time. You enable adapter connections using Integration Server Administrator.

Note: When you reload a package that contains enabled connections, the connections will automatically be enabled when the package reloads. If the package contains connections that are disabled, they will remain disabled when the package reloads.

To enable a connection

Procedure

  1. In the Adapters menu in the Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.
  2. On the Connections screen, click No in the Enabled column for the connection you want to enable.

    Integration Server Administrator enables the adapter connection and displays a and Yes in the Enabled column.

    • If you receive an error message, click the Edit button to view the configuration. Verify that your configuration information is correct. See Editing Adapter Connections.
    • In case of an RFC error message, an RFC trace file named dev_rfc.trc will be written to Integration Server_directory directory. This file contains a more detailed description of the error cause.

Viewing Adapter Connections

You can view adapter connections and each connection's parameters from the Integration Server Administrator or from Designer.

Viewing Adapter Connections Using Integration Server Administrator

About this task

To view the adapter connections using Integration Server Administrator

Procedure

  1. In the Adapters menu in the Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.

    You can sort and filter the list of connections that appears on the Connections screen.

    • To sort information on the Connections screen, click the Up and Down arrows.
    • To filter the list of connections:
      1. On the Connections screen, click Filter Connections.
      2. Type the criterion by which you want to filter into the Filter criteria box. Filtering is based on the node name, not the connection alias. To locate all connections containing specific alphanumeric characters, use asterisks (*) as wildcards. For example, if you want to display all connections containing the string "abc", type *abc* in the Filter criteria box.
      3. Click Submit. The Connections screen displays the connections that match the filter criteria.
      4. To re-display all connections, click Show All Connections.

    The Connections screen appears, listing all the current connections. You can control the number of connections that are displayed on this screen. For more information, see Controlling Pagination.

  2. On the Connections screen, click the icon for the connection you want to view.

    The View Connection screen displays the parameters for the connection. For descriptions of the connection parameters, see Configuring Adapter Connections.

  3. Click Return to IBM webMethods Adapter for SAP to return to the Connections screen.

Viewing Adapter Connections Using Designer

About this task

To view the adapter connections using Designer

Procedure

  1. Start Designer if it is not already running.
  2. From Designer Package Navigator view, open the package and folder in which the connection is located.
  3. Double-click the connection you want to view.

    The parameters for the connection appear on the Connection Information tab. For descriptions of the connection parameters, see Configuring Adapter Connections.

Editing Adapter Connections

About this task

If a connection parameter changes, or if you want to redefine parameters that a connection uses when connecting to an SAP system, you can update a connection's parameters using Integration Server Administrator.

After you edit a connection, you must reload the WmSAP package for the change to take effect.

To edit a connection

Procedure

  1. In the Adapters menu in the Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.
  2. Make sure that the connection is disabled before editing it. See Disabling Adapter Connections for instructions.
  3. On the Connections screen, click the icon for the connection you want to edit.

    The Edit Connection screen displays the current parameters for the connection. Update the connection's parameters by typing or selecting the values you want to specify.

    For descriptions of the connection parameters, see Configuring Adapter Connections.

  4. Click Save Changes to save the connection and return to the Connections screen.

Copying Adapter Connections

About this task

You can copy an existing Adapter for SAP connection to configure a new connection with the same or similar connection properties without having to re-type all of the properties for the connection. You copy adapter connections using Integration Server Administrator.

To copy a connection

Procedure

  1. In the Adapters menu in the Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.
  2. On the Connections screen, click for the connection you want to copy.

    The Copy Connection screen displays the current parameters for the connection you want to copy. Name the new connection, specify a package name and folder name, and edit any connection parameters as needed by typing or selecting the values you want to specify.

    Note: When you copy a connection, the new connection does not save the password of the original connection. You must enter and then retype the password before you can save the new connection.

    For descriptions of the connection parameters, see Configuring Adapter Connections.

  3. Click Save Connection to save the connection and return to the Connections screen.

Deleting Adapter Connections

About this task

If you no longer want to use a particular Adapter for SAP connection, you can delete it by following the instructions in this section. You delete adapter connections using Integration Server Administrator.

If you delete a connection, the adapter services or notifications that are defined to use the connection will no longer work. However, you can change which connection an adapter service uses. Therefore, if you delete a connection, you can assign a different connection to an adapter service and re-use the service. To do this, you use the built-in webMethods function setAdapterServiceNodeConnection. For more information, see Changing the Connection Associated with an Adapter Service at Design Time.

To delete a connection

Procedure

  1. In the Adapters menu in Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.
  2. Make sure that the connection is disabled before deleting. To disable the connection, click Yes in the Enabled column and click OK to confirm. The Enabled column now shows No (disabled) for the connection.
  3. On the Connections screen, click the icon for the connection you want to delete.

    The Integration Server deletes the adapter connection.

Disabling Adapter Connections

About this task

Adapter for SAP connections must be disabled before you can edit or delete them. You disable adapter connections using the Integration Server Administrator.

To disable a connection

Procedure

  1. In the Adapters menu in the Integration Server Administrator's navigation area, click IBM webMethods Adapter for SAP.
  2. On the Connections screen, click Yes in the Enabled column for the connection you want to disable.

    The adapter connection becomes disabled and you see a No in the Enabled column.

Testing the Execution of an RFC

About this task

After you have verified that you can connect to an SAP system, you can use the following procedure to verify that the SAP system accepts and processes an RFC request from Adapter for SAP.

To test an RFC from Adapter for SAP

Procedure

  1. In the Adapters menu in the Integration Server Administrator navigation area, click IBM webMethods Adapter for SAP.
  2. In IBM webMethods Adapter for SAP menu, click Lookup.
  3. From the drop down list in the System ID field, select the system ID of the SAP system that hosts the function module you want to test.
  4. In the Function Name field of the Function Search group, enter the name of the function module you want to test. For example, enter RFC_FUNCTION_*. Click Search. Adapter for SAP searches for all RFCs that begin with RFC_FUNCTION_.
  5. In the list of matching RFCs that is returned, follow the link of the RFC you want to test. For this example, select RFC_FUNCTION_SEARCH. Adapter for SAP displays the function signature for the selected function module. It lists the imports, exports, and tables comprising this function module.
  6. Select Test Function to invoke the function module on the SAP system you selected in step 3 of this procedure.
  7. Enter RFC_* in the field FUNCNAME and click Test Functionagain to proceed. After a few moments, a screen displays the number of functions found.
  8. Follow the entries link beside this row count to view the functions found.

Testing the Execution of an RFC-XML

About this task

You can invoke a function module with RFC-XML from Adapter for SAP user interface via the Lookup screen. This screen contains an RFC-XML template you can use to invoke function modules. Perform the following procedure to access the Lookup screen and invoke a function module via RFC-XML.

To invoke a function module via XML from Adapter for SAP

Procedure

  1. In the Adapters menu in the Integration Server Administrator navigation area, click IBM webMethods Adapter for SAP.
  2. In IBM webMethods Adapter for SAP menu, click Lookup.
  3. Enter the function module you would like to invoke via XML in the Function Name field of the Function By Name section.
  4. Select RFC-XML.

    This generates a form containing the XML template necessary to invoke the function module. Fill in the appropriate inputs and select Invoke on System ID. You will see the XML response in the browser (you may have to select View Source to see the actual XML source in your browser).

Testing the Execution of a BAPI Via XML

The lookup-tool comes with a built-in BAPI Browser. You can use this tool for an overview of the BAPI interfaces inside your SAP system, and also to directly call a BAPI via XML.

Starting to Browse

About this task

You can start browsing your BAPIs using the Lookup tab. Here you can enter the name of a business object and a BAPI. This selection always applies to the SAP system selected in the field System ID.

There are several ways you can fill out the form:

  • In the group BAPI By Name enter the full name of the business object and BAPI. You can either view the details of the BAPI by selecting Lookup or directly invoke the BAPI via XML by clicking bXML.
  • In the group BAPI By Name enter only the name of the business object. Select Lookup to view details of the business object and select one BAPI from the list of available BAPIs for the business object.
  • In the group BAPI By Name enter *in the business object field to view a list of all business objects available in the selected system.
Note: Business object names and BAPI names are case sensitive.

Displaying a List of Business Objects in the System

About this task

By entering * in the business object field on the Lookup main page, you can view a list of all business objects available on the selected system.

Each link in this list represents a business object. If you follow the link, you will get a detailed view of this business object. This list can also contain business objects that do not contain BAPI methods.

Displaying a Business Object

About this task

By entering a correct name of a business object in the corresponding field on the Lookup main page, you can view detailed information for this business object. The detailed information consists of a list of all the key fields of a business object and a list of all its BAPI methods. For business objects, which only provide instance-independent methods ("static" methods in programming languages like C or JAVA), the Key fields list is empty.

For business objects that do not provide BAPIs, the list of BAPIs will be empty.

Just follow the links to the corresponding table fields to display more information on a specific key field or BAPI.

Displaying a BAPI

By entering the full name of the business object and BAPI in the corresponding field on the Lookup main page, you can display detailed information of the BAPI. You can also display this information by following the corresponding link on the display page for a business object.

Field Description
Static method The Static method flag is true if the BAPI is an instance-independent method. In practice, that means that you do not have to specify the business objects key fields when calling this method.
Dialog method The Dialog method flag is true if the method is a dialog method. If the method is not using a dialog, the flag is false. Dialog BAPIs require a SAPGui.
Factory method The Factory method flag is true if the BAPI is used to create an object instance inside the SAP system. Factory methods return the key fields of the business object.
Function module The Function module is the message type that has to be used to set up routing for synchronous calls coming from an SAP system. This is technically realized via RFC, so here the name of the corresponding RFC function module inside the SAP system is provided. Although it is possible at the moment, it is not recommended to call BAPIs directly via RFC-XML, as this would only be an implementation-dependent view of the BAPI.
ALE message type The ALE message type is the message type that has to be used to set up routing for asynchronous calls coming from an SAP system. This is technically implemented via IDoc transfers, but when using the BAPI styled XML calls, the ALE message type is only needed to set up routing.
Parameters The Parameters field contains a list of all parameters in the BAPI interface. By selecting this link, you can display more information on each parameter. Please note that the key fields of a business object are not displayed in this parameter area but in the Key fields area on the business object detail page.

By clicking the Create XML template button, you can generate the XML message that has to be used to invoke this BAPI via XML. After it has been generated, you can immediately send the XML to the SAP system for testing purposes (see below).

Displaying a BAPI Parameter

By selecting a specific parameter from the list of parameters provided on the BAPI detail page, you can display additional information for this parameter.

Field Description
Internal Name Parameter name of the underlying RFC.
Direction The use-direction of the parameter is displayed. BAPIs use importing, exporting and changing (= importing and exporting) parameters.
Optional If the flag Optional is set to true, you can omit this parameter in an XML message. Usually, the implementation inside the SAP system uses specific default values for optional parameters that were omitted.
Table If the flag Table is set to true, this parameter may consist of several lines. Each line has the data type specified in the ABAP Dictionary Type field.
ABAP Dictionary Type The ABAP Dictionary Type is a link to the data type description used for this parameter. This may be a whole structure or just a field of a structure. By following the hyperlink, you will always see the whole structure.

Displaying a Key Field

By selecting a specific key field from the list of key fields provided on the business object detail page, you can display additional information for this key field.

Field Description
Internal Name Parameter name of the underlying RFC.
ABAP Dictionary Type The ABAP Dictionary Type is a link to the data type description used for this parameter. This is usually a field of a structure inside the SAP Data Dictionary. By following the hyperlink, you will see the whole structure.
Note: Key fields are used with instance-dependent (non-static) methods and with factory methods.

In calls to these methods, the key fields of the corresponding business object have to be specified as attributes of the business document root element.

For example, using the key field CompanyCodeId in a call to the CompanyCode.GetDetail: 

<?xml version="1.0" encoding="iso-8859-1"?>   
<biztalk_1 xmlns="urn:biztalk-org:biztalk:biztalk_1">   
  <header>   
    …..   
  </header>   
  <body>   
    <doc:CompanyCode.GetDetail CompanyCodeId="0001"   
         xmlns:doc="urn:sap-com:document:sap:business"   
         xmlns="" >   
    </doc:CompanyCode.GetDetail>   
  </body>   
</biztalk_1>

Generating XML Calls for a BAPI

By entering the full name of the business object and BAPI in the corresponding field on the Lookup main page and then choosing Create XML Template, you can generate an XML message representing the call to this BAPI. You can also generate this message by following the corresponding link on the display page for a BAPI.

The page displays the XML message needed to call the BAPI which is wrapped in the BizTalk XML envelope. You can edit the XML and enter your specific data into the pre-generated XML elements for parameters and key fields.

You can also adjust the pre-generated information in the BizTalk XML header fields that are filled with default data.

There are three ways of calling the BAPI, which can be selected through the list:

  • Synchronously calling the BAPI in an SAP system.
  • Asynchronously calling the BAPI in an SAP system. This only works for BAPIs that are mapped to an ALE interface. To see whether the BAPI is mapped to an ALE interface, check the BAPI detail page. If an ALE message type is specified, the BAPI can be called asynchronously.
  • Applying routing notification: The call will be sent to the BAPI inbound process of the routing listener that will check if a routing notification for this BAPI call exists and will forward the call to the specified service. This will only work if a correct routing notification has been setup, otherwise you will receive an XML error message.

After clicking Invoke, the result of your XML call is displayed. In the case of synchronous processing, this will be a BizTalk message with either the exporting parameters of the BAPI or with an error message.

For asynchronous calls, this will be a BizTalk message with an empty body in the case of success or with an error message, if the message could not be delivered to an SAP system. Application specific errors are not returned in the case of asynchronous calls, but you can use the ALE monitoring tools in the target SAP system to check these errors.