RFC BAPI Listener

Use the RFC BAPI Listener activity to listen to the SAP system and receive RFC/BAPI requests from the SAP system.

Only request/reply requests are supported. Asynchronous requests are not supported.

Note: In a project, the RFC BAPI Listener activities cannot have the following configurations:
  • Retrieve the same RFC/BAPI and use the same SAP Connection shared resource.
  • Retrieve the same RFC/BAPI and use the SAP Connection shared resources with the same combination of the gateway host, the gateway service, and the program ID.

If you want to control the number of messages being processed concurrently in the activity, choose one of the following configurations:

  • Configure the Max Connections field of the referenced server connection according to the number of all the IDoc Listener and RFC BAPI Listener activities.
  • Configure the RFC Destination accordingly by using the SAP transaction code SMQS.
Note: The RFC BAPI Listener activity does not support the job tuning property, FlowLimit.

See Job Tuning for details.

General

In the General tab, you can establish connections to the SAP system, and download the schema of the RFC/BAPI to be retrieved.

The following table lists the fields in the General tab:

Field Module Property? Description
Name No The name to be displayed as the label for the activity in the process.
SAP Connection Yes Click to select an SAP Connection shared resource. The SAP Connection shared resource establishes connections between the plug-in and the SAP system.

Ensure that you have created an SAP Connection shared resource accordingly first. See Creating and Configuring an SAP Connection for details.

Note:
  • You cannot create a new connection by clicking Create Shared Resource because the server connection that you created cannot be enabled this way.
  • When the server connection of an SAP Connection shared resource is not enabled, you still can select this shared resource by selecting the corresponding process property. Therefore, if you want to select an SAP Connection shared resource by selecting corresponding process property, ensure that the server connection of the shared resource has been enabled.
RFC/BAPI No Click Fetch Function Module to download the schema of the RFC/BAPI to be received from the SAP system.
In the Search RFC/BAPI dialog, complete the following tasks:
  1. Specify the RFC/BAPI filter or the RFC/BAPI group filter to filter out the required RFC/BAPI types with the RFC/BAPI type name.

    Both the RFC/BAPI filter and the RFC/BAPI group filter support wildcard search.

  2. Click Fetch RFC/BAPIs.
  3. Select the RFC/BAPI type that you want to download and click OK.

    Ensure that the selected RFC/BAPI type has been released in the SAP system.

Once the RFC/BAPI schema is downloaded, an XSD file is created. The XSD file cannot be visible in the project but it can be picked from the activity if required.

Note: The plug-in does not supported basXML and class-based exceptions.

If the SAP system publishes the request of an RFC/BAPI that is not configured in the RFC BAPI Listener activity, an exception occurs in the SAP system but no error or exception occurs in the plug-in.

Description

In the Description tab, you can enter a short description for the RFC BAPI Listener activity.

Advanced

In the Advanced tab, you can specify timeout value for the activity to wait for a response to be sent to the SAP system.

The following table lists the fields in the Advanced tab:

Field Module Property? Description
Sequence Key No This field contains an XPath expression that specifies the order in which the process runs. Process instances with sequencing keys that have the same value are executed sequentially in the order in which the process instances were created.
Custom Job Id No This field contains an XPath expression that specifies a custom job ID for the process instance. This ID is displayed in the TIBCO Administrator View Service dialog, and it is also available in the $_processContext process variable. The custom job ID for the process instance.
Response Timeout(ms) Yes The timeout value in milliseconds for the activity to wait for a response to be sent to the SAP system.

The default value is 300000.

Note:
  • When the value of the Response Timeout(ms) field inherits a module property, if you set the module property to 0 or a negative number, the value of the field defaults to 300000.
  • When setting the log level to debug or trace, you have to adjust the value of the Response Timeout(ms) field accordingly.

Output

The Output tab shows the request of the RFC/BAPI.

Contents
Search Results