Managment Reporter – Unposted Journal Entries GP2018

  • Managment Reporter – Unposted Journal Entries GP2018

    Posted by Jeff-Ralph on May 9, 2024 at 1:11 pm

    Hi,

    I have discovered an issue with Managment Reporter (MR) and unposted Journal Entries not appearing in MR Reports that are run (posted and unposted activity).

    When we looked at the Table GL10001, we found that the missing entries were missing the Batch ID, but the users name was in the field instead.

    When we replaced the username with proper batch number and restarted Managment Report or posted these batches the problem was solved.

    Microsoft could not offer an explanation why some entries had username while the majority had the correct Batch ID.

    Has anyone else experienced these issues?

    Thanks,

    Jeff.

    Chris Giesbrecht replied 1 week, 5 days ago 2 Members · 2 Replies
  • 2 Replies
  • Chris Giesbrecht

    Member
    May 10, 2024 at 12:07 pm
    Up
    0
    Down
    ::

    Hi Ralph,

    In my experience the transactions that are posted from in the transaction (not saved to a batch and then post the batch) usually show the person’s name who posted the transaction as there is technically no batch name to show for those transactions. If you are wanting to use the batch name for reporting purposes you will need to guide your staff to save the documents in a batch and post the batch instead of just posting the transaction.

    Hope that helps you out!

    • Chris Giesbrecht

      Member
      May 10, 2024 at 1:02 pm
      Up
      0
      Down
      ::

      Sorry, just realized you were looking at the open table. Then I would think those are likely stranded records. Could be caused by one or more of the following.

      1. GP crashed while someone was entering a JE and had not assigned a batch to it. Because GP will write the transaction to the database as it is entered it will put the user name in place for the batch before the document is saved in a batch.
      2. Posting error. If there was an error while posting a document that wasn’t in a batch and it didn’t finish moving the JE properly to the open year table. You could check if the document exist in open and current year tables.
      3. 3rd party product. If you have ISV products that are creating transactions, that could be another road to explore.

Log in to reply.

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!