web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

SOP Numbers going back to fill in gaps

(0) ShareShare
ReportReport
Posted on by 75,852 Moderator

This is an oldie but goodie that I thought had long been fixed. Every now and then when users go to create a new SOP document the number that is generated is an old number. What is happening is GP is trying to fill in gaps in the sequence. Is there a different stored procedure I can load that will not behave this way?

Categories:
I have the same question (0)
  • Nicole Hellerud Profile Picture
    1,712 on at

    Hello Richard,

    Thank you for your post and I look forward to all the great feedback others in the community will be able to offer.

    Would you in the meantime offer some further details around this?

    How are SOP documents being brought into GP?

    Is this all SOP documents or specific types?

    When the system reverts to this older number, do you need to go into the system and reset it? or does it auto jump back to the next available  number?

    Is the number you talking about the document number and/or master number?

    I look forward to your feedback when available.

    Take care,

    Nicole Fiskum

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    Nicole, we are talking about the SOPNUMBE not the MSTRNUMB. These are data entry people just typing away. One user will notice that an old order number has been assigned while others have the most recent number. The next time this same user goes to create an order the more recent number in sequence will be assigned. I remember back in the 1990's we were given a revised script to correct this. Alas, I have been unable to find that script.

  • Tim Wappat Profile Picture
    5,713 on at

    For others picking this up through search, this is normal behaviour for GP, the application attempts to reuse numbers that have not been consumed, say the user went into the document number field, so was issued with a number, but just closed the window and never used it. 

    As I understand it this activity happens in both stored procedures for eConnect and in DEX too for the user interface forms. 

    I've not seen the script(s) you refer to though.

    Tim.

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    Tim, we first noticed back in the 1990's. I remember being sent a script that did not behave this way.  I am unable to find it. What I will do is create a script to find the gaps and fill them in.  The same client who complained about this then is complaining about this now.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 586 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 551

#3
CP04-islander Profile Picture

CP04-islander 408

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans