Identifying which Number Sequence has been Exceeded in Dynamics AX 2012

Posted on: August 14, 2018 | By: Jarrod Kraemer | Microsoft Dynamics AX/365

Authored by: Rosey McAdams

No matter what type of transaction you are doing within Dynamics AX there is always the possibility that your transaction could error out with the dreaded “Number sequence ########## has been exceeded” error message.  You could be entering a new sales order, receiving a PO, or entering an AP invoice – all of these transactions touch several different number sequences.  If any of these transactions causes the next number in the sequence to exceed the highest number in the number sequence you will run into this error.  The problem with this error is that it is not always straight forward as to which number sequence has been exceeded.    In this post we will go through some simple steps to help you determine which number sequence is causing the error and how to resolve the error.


The problem with this error message is that for less technical folks the number being displayed in this error message may mean nothing to us.  It would be nice if the error message would tell us which number sequence code the error is related to, but instead it displays some random 10-digit number.  In fact, this number is not actually random at all – it is actually the number sequence record ID.  A record ID is a unique identifier for a piece of data in a specific table of Dynamics AX.  Rather than trying to determine what number sequence could be causing the error based on the type of transaction you are trying to perform we can look up the record ID and identify which number sequence is causing our issue.  Follow the steps below to determine which number sequence has been exceeded.

1)     Navigate to the AOT > Data Dictionary > Tables > NumberSequenceTable

2)     Right click on the NumberSequenceTable and click Open.

 

3)     Navigate to the far right of the table, press CTRL+G to pull up your search bar and enter in the 10-digit number from the error message into the RecID field filter.

 

4)     In the NumberSequence field you will now be able to tell which number sequence is causing this error to be thrown.

 

Now that we have identified which number sequence has been exceeded we can navigate back to our Dynamics AX workspace Organization Administration>Number sequences>Number sequences and adjust the number sequence accordingly, either by extending the number of digits and increasing the highest value or restarting the number sequence over again.

We hope this information has given you and your organization the tools to resolve exceeded number sequences a little bit more efficiently!  For additional information please feel free to reach out to us at info@loganconsulting.com or (312) 345-8817.

All the best!
Logan Consulting
www.loganconsulting.com



25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics
25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics

Free Download:

25 Brilliant Ideas to Outsmart Your Competition with Microsoft Dynamics

Download the guide ›

Top 10 Inventory & Operations Decisions Distributors Are Making Blind
Top 10 Inventory & Operations Decisions Distributors Are Making Blind

Free Download:

Top 10 Inventory & Operations Decisions Distributors Are Making Blind

Download the guide ›

2020 Nucleus Research Report on ERP Technology

Free Download:

2020 Nucleus Research Report on ERP Technology

Download the guide ›