Reply To: Managment Reporter – Unposted Journal Entries GP2018

  • 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.

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .

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!