Exposing BSPs as Callable Objects 

Use

You can expose a BSP application as a callable object and attach it to an action in a process flow.

Prerequisites

To complete the procedure, you need:

·        A configured portal system alias for the back-end system where the BSP application resides

See: System Aliases

·        The name and the start page for the BSP application

·        A configured logical destination for remote function calls (RFC)

See: Maintaining RFC Destinations

Procedure

...

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

       2.      From the Type list, select User Interface → Business Server Page (BSP) and enter the required basic data as follows:

Parameter	Value
Name	Enter a name for the callable object.
Description	Describe the callable object by entering a brief description of its functions, for example.
Original Language	From the dropdown menu, choose the language in which the translatable texts of the callable object definition are being created.
Folder	Select a folder where the callable object is stored. You can either use an existing folder, or create a new one.

       3.      Choose Next to open the Define Object screen.

Configure the parameters as follows:

Parameter	Description
Portal System Alias	Select the appropriate portal system alias from the dropdown list. The GP framework uses the parameters from the alias configuration to generate the URL for the BSP application at runtime.
Start Page	Enter the name of the HTML page that you want to be displayed as a start page when the BSP callable object is executed.
Customer Namespace	If you use a specific namespace to store your objects in the SAP system, enter it here. By default, the namespace is sap.
Application Namespace	If the BSP application that you want to expose as a callable object is stored in a specific namespace in the SAP system, enter it here. By default, the namespace is sap.
Business Server Page (BSP) Application	Enter the name of the BSP application.
Endpoint Alias – RFC destination (optional)	Use Choose… to select the appropriate RFC destination for the system where the BSP application resides. Enter the RFC destination if you want to define input and output parameters for the BSP application. Otherwise, it is executed in display mode at runtime, and you cannot interact with the back-end system using the application.

       4.      Choose Next to open the Define Input screen.

If you have selected an RFC destination in the previous step, you can define the input parameters for the callable object as follows:

                            a.      Choose Insert New.

                            b.      Fill in the required data for the parameter.

For more information, see Callable Object Parameters.

       5.      Choose Next to open the Define Output screen.

Use the procedure described in the previous step to define the output parameters.

If the callable object implements result states and process exceptions, you must also define them here.

       6.      Choose Next to open the Set Configuration screen.

To add a configuration parameter, choose Add. The system adds a new row to the Configuration Parameters table. Maintain the name and the value of the parameter directly in the table.

You can also choose whether a Complete button is to be displayed when the callable object is executed. The button enables the user to send an explicit completion event to the framework.

       7.      Choose Next, and then Finish and Open.

The design time for the callable object opens. You can edit the object definition if necessary.

Optionally, you can grant read and write permissions for the callable object to other users. To do that, choose Grant Permissions from the contextual panel.

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

Example

For an example of how you expose a BSP application as a callable object, see Creating an Instance of the BSP Callable Object.