How To Fix EDESK_CORE117 - Original already exists locally; transfer again or keep?

SAP Error Message - Details

• Message type: E = Error

• Message class: EDESK_CORE - Engineering Desktop: Central Functions

• Message number: 117

• Message text: Original already exists locally; 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_CORE117 - Original already exists locally; transfer again or keep? ?

  The SAP error message EDESK_CORE117 indicates that a document or data object you are trying to transfer already exists in the local system. This typically occurs in scenarios involving data transfers, such as when using the SAP Data Services or SAP Data Transfer Workbench.
  Cause:
  The error arises when:
  
  You attempt to upload or transfer a document that has already been downloaded or exists in the local system.
  There is a conflict between the local and remote versions of the document.
  The system is set to prevent duplicate entries for data integrity reasons.
  
  Solution:
  To resolve this error, you have a couple of options:
  
  
  Transfer Again: If you want to overwrite the existing document with the new version, you can choose to transfer the document again. This will replace the existing local version with the new one.
  
  
  Keep Existing: If the existing document is the one you want to retain, you can choose to keep it. This will prevent the new transfer from occurring and maintain the current local version.
  
  
  Check for Duplicates: Before proceeding with the transfer, check if the document is indeed a duplicate. You may want to verify the content or version of the existing document to ensure that you are not missing any updates.
  
  
  Adjust Settings: If this error occurs frequently and you want to change how the system handles duplicates, you may need to adjust the settings in your SAP configuration. Consult with your SAP administrator or refer to the documentation for your specific SAP module to see if there are options to modify duplicate handling.
  
  
  Related Information:
  
  Documentation: Refer to the SAP Help Portal or specific module documentation for more details on data transfer processes and error handling.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists or if you need further assistance, consider reaching out to SAP Support or your internal IT support team for help.
  
  By following these steps, you should be able to resolve the EDESK_CORE117 error and continue with your data transfer process.