Creating Callable Objects in the GP Design
Time
Prerequisites
To expose a service or application as a callable object, make sure that:
● The connections to the relevant service providers are configured – for example, RFC destinations.
● The relevant services or applications are available in the system – for example, the Web Dynpro component is deployed on the SAP NetWeaver Application Server.
Procedure
The procedure for exposing a service or application as a callable object in Guided Procedures, goes through the following general steps:
...
1. Basic Data – in this step, you define the basic parameters for the callable object, such as name, description, and so on.
2. Define Object – in the second step you define which service or application you want to expose as a callable object, and the parameters to connect to it – for example, URL, RFC destination, and so on.
3. Define Input – if the callable object requires input, you can define the input parameters in this step. For certain callable object types, these parameters are displayed automatically.
4. Define Output – in this step you can configure the output parameters of the callable object, if any. For certain callable object types, they are displayed automatically.
Once you set the technical name of the input or output parameter of the callable object, you cannot change it. The technical name is the unique identifier of the parameter by which it is attached to the callable object, inherited by the action and then further propagated to the upper levels in the process. You can only change the parameter technical name on action, block or process level in the design time of the respective process element.
For more information, see Configuring Parameters.
5. Set Configuration – finally, you can maintain any specific configuration parameters that the callable object defines. Certain callable object types have standard predefined configuration parameters.
Not all of these steps are obligatory for all callable object types. For some of them, the steps Define Input, Define Output, or Set Configuration might be skipped.
For more information about the specific procedure for each callable object type, see:
● Exposing Web Dynpros as Callable Objects
● Creating Web Dynpro Form Callable Objects
● Exposing WD4VC Applications as Callable Objects
● Exposing Web Services as Callable Objects
● Exposing RFCs as Callable Objects
● Exposing BSPs as Callable Objects
● Creating Portal Callable Objects
● Exposing Web Pages as Callable Objects
● Creating Callable Objects for Background Execution
● Creating Business Logic Callable Objects
● Exposing Composite Forms as Callable Objects
● Creating Pass Through Form Callable Objects
GP also provides a set of ready-to-use components that you can directly expose as callable objects and use in your processes.
More information: Predefined Callable Objects
Result
At the end of the procedure described above, the callable object becomes visible in the gallery.
You can:
● Edit the object definition
● Grant read, write, and full control permissions for other users.
More information: Granting Permissions
● Check if the object functions correctly.
More information: Testing Callable Objects
● Add version-specific information or comments using the Additional Info tab. Several rules and restrictions apply when you add or edit info:
○ You can add comments for the current version of any callable object in the gallery to which you have access.
○ You can only edit your own comments.
○ You cannot edit comments added for previous versions of the object.