Exposing RFCs as Callable Objects 

Use

You must expose an RFC-enabled function module as a callable object to be able to execute it within a process modeled with Guided Procedures (GP).

The GP framework enables you to import any function module, thus allowing you to reuse the modules you have implemented in your system without having to modify their implementation.

Prerequisites

A connection is configured to the system where the RFC-enabled function module resides. For more information, see Configuring Endpoints in the Administration Guide.

Procedure

...

       1.      Open the gallery and choose Create Callable Object from the contextual panel.

       2.      From the Type list, select Service → External Service and enter the required basic data as follows:

Parameter	Description
Name	Enter an arbitrary name for the callable object.
Description	Describe the callable object by entering a brief description of its functions, for example.
Original Language	Choose the language, in which the translatable texts of the object definition are being created.
Folder	Select a folder where the callable object definition is stored.

       3.      Choose Next to open the Define Object screen.

You must choose:

                            a.      Endpoint alias

Click Choose under Endpoint aliases. Select a predefined alias of type Endpoint alias definition for SAP Remote Function Calls (RFCs).

To confirm your selection, use Choose.

                            b.      Service

Click Choose under Service.

To search for a service, enter either its name in the field Function Name, or the group name in the field Function Group, and then choose Go.

You can use wildcard characters.

To confirm your selection, use Choose.

       4.      Choose Next to open the Define Input screen.

The input parameters of the service are automatically detected.

       5.      Choose Next to open the Define Output screen.

The output parameters of the service are automatically detected.

       6.      Choose Next to open the Set Configuration screen.

Configure the exception handling for the service. The possible configurations are described in the following table.

Parameter	Value	Description
Case 1: No Exception Handling
Error Handling Mode	No Error Handling	Choose this option if the service does not implement fault handling.
Case 2: Reporting to a Structure
Error Handling Mode	Reported in Structure	BAPIs can implement error handling using reference structures. For such services, you can choose this option to enable errors to be reported in the relevant structure. For more information about the implementation of error handling in BAPIs, see Return Parameters (Error Handling).
Error Structure Reference		Select the structure that is to hold the error information.
Error Field Name		Select the name of the field that is to contain the error identifiers.
Error Values	For example, E, A, and so on	Enter an error identifier as defined in the BAPI implementation. For more information about identifiers, see Return Parameters (Error Handling).
Error Message Field Name		Select the appropriate name of the field that is to contain the error details.

       7.      Choose Next, and then Finish and Open.

The callable object design time opens. You can edit the object definition here.

Optionally, you can grant permissions to other users to view or modify the object. To do that, open the Permissions tab page.

       8.      To activate the object, choose  (Activate). 

Example

For an example of exposing an RFC-enabled function module as a callable object, see Importing a BAPI in Guided Procedures.