How To Fix /SCMTMS/TOR255 - Number range has been changed, new ID for &1 is &2

/SCMTMS/TOR255 - Overview

• Message type: E = Error

• Message class: /SCMTMS/TOR -

• Message number: 255

• Message text: Number range has been changed, new ID for &1 is &2

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 /SCMTMS/TOR255 - Number range has been changed, new ID for &1 is &2 ?

  The SAP error message /SCMTMS/TOR255 indicates that there has been a change in the number range for a specific object, and as a result, a new ID has been assigned. This typically occurs in the context of SAP Transportation Management (TM) when the system detects that the number range for a particular document or object has been modified.
  
  Cause:
  
  Number Range Change: The number range for the object (e.g., transportation order, shipment, etc.) has been altered, which can happen due to configuration changes in the system.
  Data Migration or Upgrade: If there has been a data migration or system upgrade, the number ranges may have been reconfigured, leading to the assignment of new IDs.
  Custom Development: Custom developments or enhancements may inadvertently affect the number range settings.
  
  
  Solution:
  
  
  Check Number Range Configuration:
  
  Go to the transaction code SNRO (Number Range Objects) and check the configuration for the relevant number range object.
  Ensure that the number range is correctly