How To Fix EDESK_CORE136 - Original is obsolete and loaded; transfer again or keep?

SAP Error Message - Details

• Message type: E = Error

• Message class: EDESK_CORE - Engineering Desktop: Central Functions

• Message number: 136

• Message text: Original is obsolete 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_CORE136 - Original is obsolete and loaded; transfer again or keep? ?

  The SAP error message EDESK_CORE136 indicates that the original document or data you are trying to process is considered "obsolete" and has already been loaded into the system. This typically occurs in the context of data transfer processes, such as Electronic Data Interchange (EDI) or other data integration scenarios.
  Cause:
  
  Obsolete Document: The original document has been marked as obsolete in the system, which means it cannot be processed again.
  Duplicate Load Attempt: There may have been an attempt to load the same document multiple times, leading to the system flagging it as obsolete.
  Data Integrity Issues: There could be issues with data integrity or consistency, causing the system to reject the document.
  
  Solution:
  
  Transfer Again: If the document needs to be processed again, you may need to check the status of the original document and ensure it is valid for reprocessing. You might need to delete or archive the obsolete document before attempting to load it again.
  Keep the Document: If the document is indeed obsolete and should not be processed again, you can choose to keep it as is. Ensure that any subsequent processes are aware of this status.
  Check Document Status: Review the status of the document in the system to understand why it is marked as obsolete. This may involve checking logs or transaction codes related to the document.
  Consult Documentation: Refer to SAP documentation or support resources for specific guidance on handling obsolete documents in your particular SAP module or scenario.
  Contact Support: If the issue persists or if you are unsure how to proceed, consider reaching out to SAP support or your internal IT team for assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that can help you view document statuses, such as SE11 (Data Dictionary), SE16 (Data Browser), or specific transaction codes related to your module (e.g., WE02 for EDI).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional context or solutions.
  System Logs: Review system logs for any additional error messages or warnings that may provide more insight into the issue.
  
  By following these steps, you should be able to address the EDESK_CORE136 error effectively.