Skip to main content
Version: Current

Find SAP Service

Description

Finds SAP OData services available through the configured SAP connection.

Use this activity to discover SAP services at runtime instead of selecting a specific service while designing the workflow.

You can optionally provide a Search Term to narrow the services returned by the activity.


Common Capabilities

Process Data Support

info

This activity supports dynamic configuration using variables from the Process Data drawer.

You can bind values from Model Data, Form Data, System Data, Enterprise Variables, and Activity Outputs.

Learn more → Using Process Data


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.


OData Version

Specifies the OData protocol version used when discovering services from the connected SAP system.

OptionDescription
AutoAutomatically determines the appropriate OData version based on the configured connection URL. This is the default option.
OData V2Uses the OData V2 protocol.
OData V4Uses the OData V4 protocol.
tip

Use the default Auto option unless you specifically need to search for services using OData V2 or OData V4.

Timeout

Specifies the maximum amount of time, in seconds, that the activity waits for the SAP request to complete.

If the request does not complete within the configured duration, the activity times out.

Search Term

An optional value used to search for SAP OData services.

The activity searches for services containing the specified term. For example, if you specify purchase, the activity returns the available services that contain purchase in their searchable service 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 services discovered from the connected SAP system.


Wait All Incoming

Execution Control

Controls how this activity behaves when multiple incoming execution paths converge.

Determines whether the activity executes when:

  • Any incoming path completes, or
  • All relevant incoming paths complete before execution

Learn more → Execution Control


On Error

Error Handling Strategy

Defines how the workflow behaves if this activity encounters a runtime error.

Supported strategies include:

  • Fault
  • Continue
  • Suspend
  • Retry

Learn more → Error Handling


Output

Services

A collection of SAP OData services matching the specified Search Term.

Each service in the collection contains the following information:

PropertyDescription
IdUnique identifier of the SAP service.
NameTechnical name of the SAP service.
DisplayNameDisplay name of the SAP service.
DescriptionDescription of the SAP service.

The returned Services collection can be used by downstream activities through Activity Outputs.

Error Message

Contains information about any error encountered while searching for SAP services.

This output can be used by downstream activities to inspect or handle errors as part of the workflow.


Remarks

  • The selected SAP connection must have access to the SAP system from which services are discovered.

  • The services returned by the activity depend on the OData services available through the connected SAP system.

  • Search Term performs a term-based search. For example, specifying purchase returns services containing that term.

  • Leave Search Term empty when you want to retrieve all services available through the configured connection.

  • Each item in the returned Services collection provides the service Id, Name, DisplayName, and Description.

  • The authenticated SAP user must have sufficient permissions to discover and access the required OData services.

  • Use the returned Services collection when SAP service discovery needs to be performed dynamically at runtime.