How To Fix EDESK_CORE138 - Original is modified and loaded; transfer again or keep?

SAP Error Message - Details

• Message type: E = Error

• Message class: EDESK_CORE - Engineering Desktop: Central Functions

• Message number: 138

• Message text: Original is modified and loaded; transfer again or keep?

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDESK_CORE138 - Original is modified and loaded; transfer again or keep? ?

  The SAP error message EDESK_CORE138 typically occurs in the context of data transfer processes, particularly when dealing with the Electronic Data Interchange (EDI) or similar data exchange scenarios. This message indicates that the original data has been modified after it was loaded into the system, and the system is prompting the user to either transfer the modified data again or keep the existing data.
  Cause:
  
  Data Modification: The original data that was loaded into the system has been changed or updated after the initial load. This could happen due to manual changes, automated processes, or external systems updating the data.
  Concurrency Issues: If multiple users or processes are trying to access and modify the same data simultaneously, it can lead to conflicts and modifications that trigger this error.
  Incomplete Data Transfer: If the data transfer process was interrupted or not completed successfully, it may lead to inconsistencies in the data.
  
  Solution:
  
  Review Changes: Check the changes made to the original data. Determine if the modifications are valid and necessary.
  Re-transfer Data: If the modifications are valid and you want to keep the updated data, you can choose to re-transfer the modified data. This will overwrite the existing data with the new changes.
  Keep Existing Data: If the original data is still valid and you do not want to overwrite it, you can choose to keep the existing data. This will discard the modifications made after the initial load.
  Check for Concurrency Issues: Ensure that no other processes or users are modifying the same data simultaneously. Implement locking mechanisms if necessary to prevent such issues.
  Consult Logs: Review system logs or error logs to identify the source of the modification and understand the context in which the error occurred.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use specific transaction codes to manage data transfers, such as WE02 for monitoring EDI messages or WE19 for testing EDI.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Refer to SAP documentation for guidelines on data transfer processes, EDI configurations, and best practices to avoid such errors in the future.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical support team for further assistance.