3645227 - Error "Transaction is being Processed by User SAP_WFRT" when Adding Multiple Service Items in Solution Order via Business Solution Order (A2X) API

When adding multiple service items to a Solution Order using the Business Solution Order (A2X) API, the first API request is processed successfully, but a subsequent request fails with the following error:

Transaction is being processed by user SAP_WFRT

This issue may occur when using either:

• Business Solution Order (A2X) API V2
• Business Solution Order (A2X) API V4

SAP S/4HANA Cloud Public Edition

1. Create or update a Solution Order using the Business Solution Order (A2X) API.
2. Add multiple service items by sending multiple API requests.
3. The first API request is processed successfully.

4. One of the following API requests fails with the error:

   Transaction is being processed by user SAP_WFRT

SAP_WFRT is the workflow user used by the system to perform background updates on the Solution Order.

For example, when certain follow-up processes are triggered, the Solution Order may be locked temporarily while SAP_WFRT updates related information such as transaction history.

This can occur for processes such as:

• Released sales items
• Project-related updates
• Subscription billing item updates, depending on the communication setup

For service order or service contract items, the Solution Order is generally not locked by SAP_WFRT unless a valid update is performed on the follow-up Service Order or Service Contract.

This locking behavior is part of the expected Solution Order process flow.

To avoid locking conflicts when using the Business Solution Order API, review the order creation and release sequence.

Recommended actions:

1. Check whether other item types, such as sales items or subscription billing items, are being created in the same Solution Order.
2. Check whether any item release or follow-up processing is triggering background updates by SAP_WFRT.
3. Release all items together at the end of the Solution Order creation process, where possible.
4. Avoid releasing items one by one while additional API requests are still being sent.
5. If items cannot be released together, introduce a delay between API requests so the SAP_WFRT background update can finish before the next request is sent.

Recommended API Processing Approach

Where possible, use the following approach:

1. Create the Solution Order.
2. Add all required items.
3. Complete all required item updates.
4. Release the items together.
5. Send further update requests only after the previous processing has completed.

This helps reduce the chance of lock conflicts caused by background processing.

Additional Information

The error does not necessarily mean that the business user is manually editing the Solution Order.

The user SAP_WFRT is a system workflow user. It may lock the Solution Order temporarily while performing required background updates.

If the lock occurs, wait until the background process is complete and then retry the API request.

• Overview | Business Solution Order (A2X) V2 | SAP Business Accelerator Hub
• Overview | Business Solution Order (A2X) V4 | SAP Business Accelerator Hub

SAP_WFRT, transaction is being processed by user SAP_WFRT, transaction locking, lock error, locked by workflow user, workflow user, Solution Order, Solution Order Management, Business Solution Order API, Business Solution Order A2X, A2X API, API V2, API V4, multiple service items, service item, service order item, service contract item, sales item, subscription billing item, project item, transaction history update, background update, backward update, follow-up document, release items, release all items, API request, subsequent API request, retry, delay between API requests, locking conflict, SAP S/4HANA Cloud Public Edition, Public Cloud , KBA , CRM-S4-SOL-SLO , S4CRM: Solution Order , Problem