Skip to main content
Version: Current

Delete Records

Description​

Deletes one or more records from an SAP Business Object based on specified filter conditions.

The activity uses SAP OData APIs and supports SAP systems that expose OData services, including SAP S/4HANA Cloud and SAP S/4HANA On-Premises environments.

Use the Filter tab to define the conditions that identify the records to delete.

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​

The SAP OData service containing the Business Object from which you want to delete records.

The available services are retrieved based on the selected SAP connection.

Business Object​

The Business Object containing the records you want to delete.

The available Business Objects depend on the selected Service.

OData Version​

Specifies the OData protocol version used to communicate with the selected SAP service.

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

Use the default Auto option unless you specifically need to force the activity 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.

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.

Filter​

The Filter tab allows you to define the conditions used to identify the SAP Business Object records to delete.

The available fields for defining filter conditions depend on the selected Business Object.

Filter values can be provided directly or configured dynamically using Process Data.

caution

Ensure that the filter conditions identify only the intended records before executing the activity.

A filter that matches multiple records may result in multiple records being deleted.

tip

When deleting a specific record, use fields that uniquely identify the record whenever possible.

Concurrency and partial failures​

PropertyBehavior
ETag ModeAutoFetch reads the current ETag before writing; Provided uses If-Match ETag; Ignore sends a wildcard; None sends no version condition. Default: AutoFetch.
If-Match ETagRequired for Provided mode. Obtain it from Get Record when appropriate.
ETag Retry MaxMaximum ETag refresh/retry attempts after a version conflict in AutoFetch mode. Default: 1.
Continue On ErrorContinue the batch after an individual SAP request fails. Default: False, which stops at the first failure.

This batch setting is distinct from the workflow's On Error policy. Completed record writes are not undone when a later record fails. With Continue On Error enabled, inspect Failures, whose items include Key, ErrorCode, and Message.

Matched Records Count reports the selected records; Affected Records Count reports successful writes. An empty selection produces zero counts. Filter-based writes require a concrete, nonempty Filter; the activity rejects a missing filter rather than treating it as permission to change all records.

For a normal workflow activity, an operation-level exception follows On Error. When used as an AI tool, the activity can return zero counts and a Failures message so the agent can inspect the error. Check Failures as well as the counts.

Output​

  • Affected Records Count: records successfully deleted.
  • Matched Records Count: records matching the filter.
  • Failures: per-record errors when batch continuation is enabled, or an operation-level failure message.

Remarks​

  • The available Business Objects depend on the selected Service.

  • The fields available in the Filter tab depend on the selected Business Object.

  • The authenticated SAP user must have permission to delete records from the selected Business Object.

  • Use appropriate filter conditions to ensure that only the intended records are deleted.

  • When deleting a specific record, use a unique identifier or a combination of filter conditions that uniquely identifies the record.

  • SAP may prevent deletion based on business rules, record dependencies, or other validations configured in the SAP system.

Example: Target one business record​

Use the connection, service, and Business Object for the intended record. Build a filter on its unique technical key, such as PurchaseOrder = '4500001237' for a compatible object. Keep ETag Mode at AutoFetch unless another concurrency policy is required.

After execution, compare matched and affected counts and inspect Failures. A filter can match several records; use unique-key conditions when exactly one write is intended.

Help improve this page