How To Fix /SCMTMS/MSG125 - &1: Location &2 cannot be used; it is marked for deletion

/SCMTMS/MSG125 - Overview

• Message type: E = Error

• Message class: /SCMTMS/MSG -

• Message number: 125

• Message text: &1: Location &2 cannot be used; it is marked for deletion

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.

/SCMTMS/MSG125 - Details

• The SAP error message /SCMTMS/MSG125 &1: Location &2 cannot be used; it is marked for deletion typically occurs in the context of SAP Transportation Management (TM). This error indicates that a specific location (identified by &2) is marked for deletion and therefore cannot be used in the current transaction or process.
  
  Cause:
  
  Location Marked for Deletion: The primary cause of this error is that the location you are trying to use has been flagged as "marked for deletion" in the system. This could happen due to data maintenance activities where a user or an automated process has set the location to be deleted.
  Data Integrity Issues: Sometimes, data integrity issues or inconsistencies in the master data can lead to this error, especially if the location is referenced in other transactions or master data.
  
  
  Solution:
  
  
  Check Location Status: 
  
  Go to the relevant transaction in SAP (e.g., using transaction code /SCMTMS/LOC or similar) to check the status