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

SAP Error Message - Details

• 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 requests or tasks within the TMSLT group starts at 1 and follows a continuous sequence without gaps.
  Steps to fix:
  
  
  Check the numbering sequence:
  
  Use transaction SE16 or SE16N to view tables related to transport requests/tasks, such as E070 (Transport Requests) or E071 (Transport Tasks).
  Filter by the relevant TMSLT group and check the numbering sequence.
  
  
  
  Adjust numbering if possible:
  
  If gaps or incorrect starting numbers are found, investigate why these gaps exist.
  If the gaps are due to deleted or canceled requests, consider re-creating missing requests or adjusting the numbering in a controlled manner.
  
  
  
  Reset or reinitialize numbering:
  
  In some cases, you may need to reset the numbering sequence for the TMSLT group.
  This can be done by adjusting the transport layer or TMS configuration.
  Use transaction STMS to check and maintain transport layers and groups.
  Consult SAP notes or your Basis team before resetting numbering to avoid inconsistencies.
  
  
  
  Check for OSS Notes:
  
  Search SAP Support Portal for notes related to W0072 for your specific SAP version.
  Sometimes SAP provides patches or instructions for known issues causing numbering problems.
  
  
  
  Avoid manual changes:
  
  Ensure that transport requests and tasks are created and managed only through standard SAP transactions and tools.
  Avoid manual edits to transport tables or numbers.
  
  
  
  
  Related Information:
  
  TMSLT Group: Logical grouping in SAP Transport Management System that controls transport request/task numbering.
  Transport Requests and Tasks: Objects used to manage changes and transports in SAP systems.
  Transaction STMS: Used to configure and monitor the Transport Management System.
  Tables:
  
  E070 - Transport Requests
  E071 - Transport Tasks
  TMSLT - TMS Logical Transport Groups (configuration)
  
  
  SAP Notes: Check for notes related to transport numbering issues or W0072 warning.
  Best Practices:
  
  Always use SAP standard tools for transport management.
  Regularly monitor transport sequences.
  Avoid deleting transport requests/tasks unless necessary and understand the impact.
  
  
  
  
  If the problem persists or is complex, consider raising a support ticket with SAP, providing details of your TMS configuration and the exact scenario causing the warning.