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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Gaps in PSTGNMBR in GL20000

(0) ShareShare
ReportReport
Posted on by

Understood that there's a sequential PSTGNMBR (Posting Number) assigned to each posted JRNENTRY, under what circumstance that there's a gap in the PSTGNMBR?

i'm observing 2 Gaps at least in the entire GL20000 table. Though running the Reconcile Posting Numbers can help close the gap, I'd need to know what could have caused the Gap in the first place, to answer an audit finding.

Thanks n cheers.

*This post is locked for comments

I have the same question (0)
  • Richard Whaley Profile Picture
    25,195 on at

    If you are referring to the journal number, and your firm is using Inventory, it is possible some people posted IV transactions and did not mark the Post to GL button.

  • Community Member Profile Picture
    on at

    Hi Richard,

    i'm actually referring to the Posting Number in this case.

    Inventory module is not in use though. The modules in use are only Payables, Cashbook Bank Management, Fixed Assets, and of course GL.

  • Mahmoud Saadi Profile Picture
    32,738 on at

    There might be un-posted journal entries in [ GL10000 ] Transaction Work, therefore, you need to check the serial in both tables [ GL20000 ] and [ GL10000 ].

    In case you still have variances, you might need to check whether the "Next Journal Entry" number has been changed from ( Tools > Setup > Financial > General Ledger ), which might obviously cause gaps if used every now and then

    Please consider the script below as it might help you find out your Journal Entry Gaps precisely;

    Tables:

    • GL10000 | Transaction Work
    • GL20000 | Year to Date Transaction Open
    • GL30000 | Account Transaction History


    SELECT Row_ID, JE_Status, JRNENTRY,JRNENTRY+JE_Gap AS Next_Journal_Entry, JE_Gap  FROM
    (
        SELECT     ROW_NUMBER() OVER (ORDER BY JRNENTRY ASC) AS Row_ID,
                JE_Status,
                JRNENTRY,
                COALESCE(
                      (
                        SELECT TOP 1 JRNENTRY
                        FROM
                        (
                            SELECT DISTINCT X.JRNENTRY FROM
                            (
                            SELECT JRNENTRY FROM GL10000
                            UNION  ALL
                            SELECT JRNENTRY FROM GL20000
                            UNION ALL
                            SELECT JRNENTRY FROM GL30000
                            ) AS X
                             
                        ) AS Y

                        WHERE Y.JRNENTRY > B.JRNENTRY
                        ORDER BY
                        JRNENTRY ASC
                        ), 0) - B.JRNENTRY AS JE_Gap
                        
                        
        FROM
        
        (
            SELECT DISTINCT A.JE_Status,
                            A.JRNENTRY
                            FROM
            (
            SELECT 'Work' as JE_Status, JRNENTRY FROM GL10000
            UNION  ALL
            SELECT 'Open' as JE_Status, JRNENTRY FROM GL20000
            UNION ALL
            SELECT 'History' as JE_Status, JRNENTRY FROM GL30000
            ) AS A
            
        ) AS B

    ) AS F
      WHERE F.JE_Gap <> 1


  • Community Member Profile Picture
    on at

    Hi Mahmoud,

    thanks for the script for checking gaps in Journal Numbers.

    However, my concern here is the Posting Number (PSTGNMBR). Regardless of the gaps in Journal Numbers, each journal will be assigned a sequential Posting Number during posting. The highlight here is there's gap in the Posting Number sequence, which is strictly system controlled and not user-amendable.

    Thanks and best regards,

    Ivan

  • Tristan Clores Profile Picture
    2,812 on at

    Hi Ivan,

    I believe the PSTGNMBR field is not used as of yet.  The sequential field in the GL20000 table is the SEQNUMBR - which is sequenced by 16384.

    Please let me know if you have further questions.

  • Community Member Profile Picture
    on at

    Hi Tristan,

    The PSTGNMBR field is used when you set "Enable Posting Number in General Ledger" in Company Setup.

    For this case here, the posting number is already enabled for this company, and the running sequence of the Posting Number had a gap hence I'm wondering what could have caused the gap.

    Thanks and best regards,

    Ivan

  • Gururaj B Kulkarni Profile Picture
    15 on at

    Hi Iva,

    May i know the value of SOURCDOC field of GL20000 table. Is it same for all the records where you are finding the gaps? Can you paste some sample records in your next post?

  • Community Member Profile Picture
    on at

    Hi GURURAJ,

    Within the sequence of Posting Number, the SOURCDOC is all 'GJ'. But there are other SOURCDOC as well in the entire range of Posting Number.

    An example is as below.

    JRNENTRY      PSTGNMBR

    14485 35423

    14486 35424

    14488 35426

    14489 35427

    14490 35428

    Thanks and best regards,

    Ivan

  • Victoria Yudin Profile Picture
    22,769 on at

    Hi Ivan,

    This is not a setting I have ever seen used in an implementation of GP. I suspect this is true for others, as well, so that most likely accounts for the lack of responses you are getting to your actual question. :-(

    Based on the description of the functionality for Posting Number in the help files, I would suspect that something went wrong during posting to cause a gap in the numbers. But without ever having seen this before, it's hard to say for sure if there are other things that may cause this. If this is important, it may be worthwhile to start a support incident with Microsoft to get more concrete information.

  • Richard Wheeler Profile Picture
    75,850 Moderator on at

    Enable Posting Numbers in General Ledger   Mark this option to assign each transaction a unique sequence number during posting, in addition to the journal entry number. Use this option if you want solid numbering of transactions, without gaps. Solid numbering is a legal requirement in some countries, for auditing purposes.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans