How To Fix W0072 - Consecutive number must start with 1 and be in sequence (per tmslt group)

W0072 - Overview

• Message type: E = Error

• Message class: W0 - Customizing - ISR

• Message number: 072

• Message text: Consecutive number must start with 1 and be in sequence (per tmslt group)

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 W0072 - Consecutive number must start with 1 and be in sequence (per tmslt group) ?

  SAP Error Message:
  W0072 - Consecutive number must start with 1 and be in sequence (per tmslt group)
  
  
  Cause:
  This warning message occurs when the system detects that the consecutive numbering for a particular transaction or document type within a TMSLT group (Transport Management System Logical Transport group) is not starting at 1 or the sequence is broken (i.e., numbers are missing or out of order).
  In SAP Transport Management System (TMS), transport requests or tasks are assigned numbers that must be consecutive and start from 1 within each TMSLT group. If the numbering sequence is inconsistent, the system raises this warning to prevent potential issues in transport management and tracking.
  Typical causes include:
  
  Manual changes or inconsistencies in transport request/task numbering.
  Importing or creating transport requests/tasks out of sequence.
  Data inconsistencies in the transport layer or TMS configuration.
  Transport requests/tasks deleted or skipped, causing gaps in numbering.
  
  
  
  Solution:
  To resolve the W0072 warning, ensure that the consecutive numbering for transport