How To Fix CX_WDK_CONTROLLER104 - Data changed between subsequent transaction runs

CX_WDK_CONTROLLER104 - Overview

• Message type: E = Error

• Message class: CX_WDK_CONTROLLER - FP/BE/BDC Controller Messages

• Message number: 104

• Message text: Data changed between subsequent transaction runs

What causes this issue?

Data has changed between subsequent transaction runs, the data this
session is working with is outdated. Most likely a different user as
changed the data in the meantime.
The changed data was field &V1& on screen &V2& of prorgram &V3& and has
value &V4&.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CX_WDK_CONTROLLER104 - Details

• The SAP error message CX_WDK_CONTROLLER104 indicates that there has been a change in the data between subsequent transaction runs. This typically occurs in scenarios where the data being processed is expected to remain consistent throughout the transaction, but it has been modified by another user or process in the meantime.
  
  Cause:
  
  Concurrent Data Changes: Another user or process has modified the data after it was initially read but before the current transaction could complete.
  Session Timeout: The session may have timed out, leading to a refresh of the data that is no longer in sync with the original read.
  Data Locking Issues: If the data is locked by another transaction, it may lead to inconsistencies when trying to access or modify it.
  Business Logic: Certain business rules or validations may have been triggered that require the data to be in a specific state, which has changed.
  
  
  Solution:
  
  Refresh Data: Refresh the data in your transaction to ensure