How To Fix CX_WDK_CONTROLLER104 - Data changed between subsequent transaction runs

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CX_WDK_CONTROLLER104 - Data changed between subsequent transaction runs ?

  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 you are working with the most current version. This can often be done by reloading the screen or re-fetching the data.
  Check for Locks: Investigate if there are any locks on the data that might be causing the issue. You can use transaction codes like SM12 to check for locks.
  Handle Concurrent Changes: Implement logic in your application to handle concurrent changes gracefully. This may involve notifying users of changes or allowing them to re-confirm their actions.
  Review Business Logic: Ensure that the business logic is correctly implemented and that it accounts for potential changes in data state.
  Error Handling: Implement robust error handling in your application to catch this exception and provide a user-friendly message or a way to retry the operation.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM21 (System Log), ST22 (Dump Analysis), and SLG1 (Application Log) to investigate further.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for specific notes that might address this error.
  Documentation: Review the documentation for the specific module or application you are working with to understand how it handles data transactions and any specific configurations that might be relevant.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or development team for further investigation and support.