How To Fix EDATEX153 - Save canceled; Tasks generated after date of change

EDATEX153 - Overview

• Message type: E = Error

• Message class: EDATEX - Messages for Data Exchange Processes

• Message number: 153

• Message text: Save canceled; Tasks generated after date of change

What causes this issue?

You have changed the due date control or the transfer type for the data
exchange definition. This change affects due dates for which data
exchange tasks have already been generated.

System Response

Processing is terminated.

How to fix this error?

You have the following options:
Prorate the change (click on time slice symbol) so that the change lies
after &V3&, which is when the last data exchange task was generated.
Reverse the generation of data exchange tasks for the following data
exchange definition:
Data exchange process: &V1&
Third party/own service provider: &V2&
Reversal date: &V4&
Note that the reversal does not work if data exchange tasks have already
been executed for the data exchange definition and the participating
service providers after the reversal date.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDATEX153 - Save canceled; Tasks generated after date of change ?

  The SAP error message EDATEX153: Save canceled; Tasks generated after date of change typically occurs in the context of the SAP system when dealing with data changes that affect task management, particularly in the area of logistics or production planning. This error indicates that there are tasks that were generated after a specified date of change, which can lead to inconsistencies in the data.
  
  Cause:
  
  Date of Change: The error is triggered when there are tasks that were created after the date of change specified in the system. This can happen if a user attempts to save changes to a document or record that has associated tasks that are not aligned with the current state of the data.
  Data Integrity: The system is designed to maintain data integrity, and if there are tasks that depend on the data being changed, the system will prevent the save operation to avoid potential inconsistencies.
  Concurrent Changes: If