
For the callable objects that you create, you can define input and output parameters. When the callable object is attached to an action, the parameters are inherited by the action and are then propagated further to the block and process level.
At action, block, and process level, you can define additional parameters, expose existing parameters, configure default values for them, or change their technical names.
At callable object level, you can reuse parameters defined for one callable object in another.
More information: Authorizations
Viewing Parameter Properties
The object's design time opens.
All root-level parameters in the local context of the object are displayed.
To be able to view all nested parameters, choose Expand All if no selection is made. If you select a particular Structure parameter, choose Expand to view its nested parameters only. To hide nested parameters, use Collapse All and Collapse by analogy.
For each parameter, you can view the following properties:
| Icon | Description |
|---|---|
|
|
Input parameter |
|
|
Output parameter |
|
|
Parameter that is both input and output. For example, groups that contain both input and output parameters are represented by this icon. |
More information: Searching in the Parameter List
Configuring Parameter Properties
Switch to edit mode by choosing (Edit) and, where required, configure the following options:
Click in the Technical Name field of a root-level parameter and enter the new technical name.
Since technical names must be unique within a namespace, the system automatically renames duplicate parameters in the format <user-defined technical name>.<sequence_number>. For example, parameters with technical name myParameter appear as myParameter.1 , myParameter.2 , and so on.
In more complicated scenarios where you have Structure parameters containing numerous child parameters, you can decide to expose only some of them. However, it is not possible to expose a child parameter without exposing the Structure itself.
For example, you may need to specify the processor of a step dynamically at runtime. Instead of creating a separate callable object, you can create a parameter that holds the logon ID of the user. You can then configure the relevant process role with the option Filled from Context Parameter.
To define additional parameters:
Additional parameters at action and block level differ from other parameters only in their fixed namespace, which is by default http://www.sap.com/nw/eup/gp/local/additionalparameters .
Reusing Parameters
Guided Procedures allows you to reuse parameters already defined for a particular callable object in another callable object. You can do this when you want to create identical parameters that need to be consolidated.
There are two basic ways to reuse parameters:
Parameters are saved in an XML file which you can download to your local machine using the Download link provided. If you want to use the parameters in a process on a different system, make sure that you transfer the file in advance.
To avoid duplicate names (if any), the system appends a sequence number to the display and technical names of the parameters that are copied or exported. For example, My Parameter with a technical name myParameter , becomes My Parameter 1 with a technical name myParameter1 .
Once you have configured parameters, you can consolidate them if necessary.
More information: Consolidating Parameters