How To Fix /SCWM/TDC139 - Entry for edge &1 and resource type &2 already exists

/SCWM/TDC139 - Overview

• Message type: E = Error

• Message class: /SCWM/TDC -

• Message number: 139

• Message text: Entry for edge &1 and resource type &2 already exists

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.

/SCWM/TDC139 - Details

• The SAP error message /SCWM/TDC139 Entry for edge &1 and resource type &2 already exists typically occurs in the context of SAP Extended Warehouse Management (EWM) when there is an attempt to create or modify a resource (like a transportation lane or a resource type) that already has an existing entry in the system.
  
  Cause:
  
  
  Duplicate Entry: The error indicates that there is already an existing entry for the specified edge (which could refer to a location or a transportation route) and resource type in the system. This could happen if:
  
  You are trying to create a new resource that has the same parameters as an existing one.
  There was an attempt to import or upload data that includes duplicates.
  
  
  
  Data Consistency Issues: Sometimes, inconsistencies in the data or configuration settings can lead to this error, especially if the system has been recently updated or modified.
  
  
  
  Solution:
  
  
  Check Existing Entries: 
  
  Go to the relevant transaction in SAP