RFC BAPI Listener

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

The RFC BAPI Listener supports the Request/Reply and one way invocation protocols tRFC and qRFC.
Note: In a project, RFC BAPI Listener activities cannot have the following configurations:
  • The same RFC/BAPI and use the same SAP Connection shared resource.
  • 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 Tab

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

The following table lists the configurations on the General tab of the RFC BAPI Listener activity:

Field Module Property? Description
Name No Specify 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 first created an SAP Connection shared resource accordingly. See Creating and Configuring an SAP Connection for details.

Note:
  • The server connection created by clicking Create Shared Resource cannot be enabled.
  • 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 the 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 Fetch Function Module dialog, you can use the RFC/BAPI tab or BOR tab to download the schema of the RFC/BAPI to be invoked in the SAP system.

The RFC/BAPI tab is useful when the name of the function module, function group, or both are known. The BOR tab is useful for browsing SAP business objects based on application objects.

In the RFC/BAPI tab, 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 the 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.

In the BOR tab, complete the following tasks:
  1. Specify values for the Object Type Filter, Object Name Filter, and Object Text Filter fields to filter out the required business objects.

    All the object type filter, object name filter, and object text filter support the wildcard search. The values of the preceding three fields are case sensitive.

  2. Click Fetch Object Types.
  3. Expand one object type in the Object Type column, select the method that you want to download, and click OK.

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

Note:
  • The plug-in does not support basXML and class-based exceptions.
  • When you download more than one page of the RFC/BAPI schema spanning, only the first page is cached for subsequent activities.
  • If one RFC/BAPI function group is inactive in the SAP system, the RFC/BAPIs in the function group are still displayed in the search result.
  • If a business object does not contain any released key attributes, non-key attributes, or methods, the business object is still displayed in the object type search result.
  • 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.
  • If the schema for one RFC/BAPI activity is refreshed, then the other RFC/BAPI activities in the same process that using are using the same schema may not be refreshed.
Invocation Protocol No There are three types of Invocation Protocols:
  • Request/Reply
  • tRFC
  • qRFC

The default value is Request/Reply.

SAP TID Manager Yes

This field is available only when tRFC or qRFC is selected in the Invocation Protocol field

Click to select an SAP TIDManager shared resource. The SAP TIDManager shared resource can manage the check of duplicate tRFC or qRFC calls from SAP system.

If no matching SAP TIDManager shared resources are found, click Create Shared Resource to create one. For more details, see Creating and Configuring an SAP TIDManager Shared Resource.

Acknowledgment Mode No When tRFC and qRFC are selected in the Invocation Protocol field, the following types of Acknowledgment Modes are displayed:
  • Auto
  • Client

The default value is Auto.

When Auto is selected, the activity automatically acknowledges the transaction in SAP system when the output is successfully sent.

When Client is selected, the activity does not automatically acknowledge the transaction in SAP system and waits for the confirmation from the Confirm activity.
Note:
  • When the TID Manager Shared Resource is configured as Active, Client can be used as the Acknowledgment Mode. If the TID Manager Shared Resource is configured as None, then the acknowledgment mode is defaulted to Auto.
  • When a fault occurs prior to the Confirm activity, the RFC BAPI Listener activity times out and the transaction is rolled back.
  • If transactions are pending in the RFC BAPI Listener activity, then those transactions need to be completed prior to the stopping of the application.

Description Tab

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

Advanced Tab

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

The following table lists the configurations on the Advanced tab of the RFC BAPI Listener activity:

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 $_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.
Confirmation Timeout (ms) Yes This field is available only when tRFC or qRFC is selected in the Invocation Protocol field and Client is selected in the Acknowledgment Mode field on the General tab.

The timeout value in milliseconds waiting to commit the transaction.

The default value is 300000.

Note: While configuring Confirmation Timeout(ms) for tRFC or qRFC, define the value in milliseconds, which should be large enough to allow the subsequent activities prior to the Confirm activity to complete. If the value is not sufficient, then timeout would occur and the transaction would rollback.

Output Tab

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

The following table lists the output elements on the Output tab of the RFC BAPI Listener activity:

Output Item Data Type Description
SAPJCO_RFCDESTINATION String Displays the RFC destination that connects an ABAP system to an external system.
SAPJCO_CLIENT String Displays the SAP client number.
SAPJCO_CPICCONVID String Displays the low-level CPIC conversion ID for the SAP connection.
SAPJCO_HOST String Displays the SAP application server used for dispatching the call from the SAP system.
SAPJCO_SYSID String Displays the SAP system ID.
SAPJCO_USER String Displays the valid user name used to log on to the specified SAP client.