Find SAP Action or Function
Description
Finds Actions and Functions available within a specified SAP OData service.
Use this activity to discover SAP OData operations at runtime instead of selecting a specific Action or Function while designing the workflow.
Specify the Service Name containing the operations and optionally provide a Search Term to narrow the results.
Common settings
Use Process Data to bind supported inputs to workflow values or upstream outputs. See Common Activity Features for shared execution, error-handling, and output-persistence settings. Availability depends on the activity.
Design-Time Configuration
Display Text
A user-defined name for the activity, displayed on the workflow canvas to help identify its purpose.
Connection Name
The configured SAP connection used to access the SAP system.
The connection determines the SAP system and the OData services available to the activity.
If you have not yet created or configured an SAP connection, see SAP Connection.
Service Name
The SAP OData service in which to search for Actions and Functions.
You can provide the service name directly or configure it dynamically using Process Data.
For dynamic service discovery, the service information returned by the Find SAP Service activity can be used to provide the required Service Name.
OData Version
Specifies the OData protocol version used when discovering Actions and Functions from the specified SAP service.
| Option | Description |
|---|---|
| Auto | Automatically determines the appropriate OData version based on the configured connection URL. This is the default option. |
| OData V2 | Uses the OData V2 protocol. |
| OData V4 | Uses the OData V4 protocol. |
Use the default Auto option unless you specifically need to use OData V2 or OData V4.
Timeout
Maximum HTTP request duration in seconds. The default 0 uses the selected connection's timeout. Set a positive value to override it for this activity.
Search Term
An optional value used to search for Actions and Functions within the specified SAP service.
The activity searches for operations containing the specified term.
For example, specifying:
purchase
returns Actions and Functions containing purchase in their searchable information.
The search term can be provided directly or configured dynamically using Process Data.
If no search term is provided, the activity returns the available Actions and Functions discovered within the specified SAP service.
Execution settings
Configure Wait All Incoming when execution paths converge, and On Error for failure handling. Select Inherit where available to use the workflow-level error policy.
Output
Operations
A collection of SAP OData Actions and Functions found within the specified SAP OData service.
When a Search Term is provided, the collection contains the operations matching the specified search criteria.
Each operation in the collection contains the following information:
| Property | Description |
|---|---|
| Name | Name of the SAP OData Action or Function. |
| Kind | Indicates the type of operation, either Action or Function. |
| ServiceName | Name of the SAP OData service that exposes the operation. |
| IsBound | Indicates whether the Action or Function is bound to a Business Object. |
| BindingEntitySet | Business Object to which the operation is bound, when the operation is a bound Action or Function. |
| Parameters | Collection of parameters defined by the Action or Function. |
The returned Operations collection can be used by downstream activities through Activity Outputs.
Understanding Bound Operations
An SAP OData Action or Function can be either bound or unbound.
A bound operation is associated with a particular Business Object. The IsBound property is set to true, and BindingEntitySet identifies the Business Object associated with the operation.
An unbound operation is not associated with a particular Business Object. The IsBound property is set to false.
This information can be used when dynamically identifying and invoking SAP operations at runtime.
Remarks
The selected SAP connection must have permission to read the relevant service metadata. A Search Term narrows the returned collection; leave it empty to list the available results in scope. Inspect the collection before selecting an operation or object.
Example: Use a discovery result
Configure the connection and Service Name, enter a Search Term if needed, and run. Iterate over Operations and bind the selected item's Name to Invoke SAP Action → Action or Invoke SAP Function → Function. Use Kind to choose the matching Action or Function activity and IsBound/BindingEntitySet to determine the required entity context.