CMXFR Bank transaction stuck in Update status

  • CMXFR Bank transaction stuck in Update status

    Posted by DSC Communities on December 14, 2018 at 3:25 pm
    • Laura Grewe

      Member

      December 14, 2018 at 3:25 PM

      ??We have had a couple of different instances where our accountant is posting a bank transfer transaction, and the batch will show with a status of Updating.Ā  I’ve done some digging /research on this, and what I think is happening is that the transaction is getting posted to the General Ledger, but according to one post I found, the process is not completing and the entry isn’t removed from a work table?
      When I look in GL10000 I see oneĀ record with the Ā ‘batch number’, Ā journal entry and pstgstus of 2.Ā  When I look at GL10001 for that ‘batch’ there are noĀ records at all.Ā Ā When I look in GL20000 I see 2 records of the journal entry – which I believe means that it did post to the GL?Ā 
      So what causes this to happen?Ā  And should I do something to ‘fix’ the record in the GL10000 table?
      Also there is a record in the SY00500 table for the ‘batch’ with aĀ bchsttusĀ of 6, which I think is because I went into Series posting earlier, found the batch and unchecked the marked box.?
      Any help would be greatly appreciated!

      ——————————
      Laura Grewe
      IT-Application Analyst
      Lakewood Health System
      Staples MN
      ——————————

    • Jo deRuiter

      Member

      December 16, 2018 at 10:51 AM

      Hi ?

      There could be a couple of things going on here, but it sounds like the batch is getting stuck.Ā  First thing is to unstick the batch and try posting again.

      There are too many variables to discuss in why batches get stuck, but some of the main causes are:

      • Third party products not working as expected
      • Customizations on windows not working as expected
      • Orphaned records of users in the Dynamics Database
      • Communications issues from the workstation back to the server (including lack of processing space on either the workstation or the server)

      From the symptoms you note you DO have some duplicated transactions in Work and Open tables.Ā  If you confirm that the transaction did indeed post all the way into the GL Open tables and the Bank Tables then you can delete them from the work tables.

      Exercise extreme caution or reach out to your partner or trusted consultant to clear this up for you.

      It may also be that GP has just NOT finished posting the batch – as part of fully posting GP removes the transaction from the work tables after moving it to the Open tables.

      To clear up “stuck batch” issues, the first thing is to make sure that users are not orphaned in transaction tables.Ā  Run this script to see all users in the system and some of what they are doing:

      SELECT * FROM DYNAMICS..ACTIVITY
      SELECT * FROM DYNAMICS..SY00800
      SELECT * FROM DYNAMICS..SY00801
      SELECT * FROM TEMPDB..DEX_LOCK
      SELECT * FROM TEMPDB..DEX_SESSION

      To make sure that there are no orphans, have all users exit and run this script

      DELETE DYNAMICS..ACTIVITY
      DELETE DYNAMICS..SY00800
      DELETE DYNAMICS..SY00801
      DELETE TEMPDB..DEX_LOCK
      DELETE TEMPDB..DEX_SESSION

      IF YOU CANNOT GET ALL USERS OUT OF THE SYSTEM, I’VE ATTACHED A SCRIPT THAT COMPARES ACTIVE SPIDS TO THE TEMP TABLES TO REMOVE ORPHANS – BUT THE BEST THING IS TO GET EVERYONE OUT AND RUN THE DELETE STATEMENT…. As usual, please make a good backup before running any kind of Delete or update scripts in GP.

      Once you’ve made sure there are no orphaned user records, then you’ll need to update the batch in the SY00500 to make it “Postable” again.

      Here is the script that does that.

      UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB=’XXX
      *where ‘XXX‘ is the batch number in question*

      Once the batch has been “fixed” in the SY00500 you can try to get it posted again.

      Some tips:
      One of the worst things you can do is to “kill” GP while batches are posting – no matter how long it takes.
      Since this has happened more than once, your next priority should be to figure out WHY it’s happening doing these bank transfers and fix that issue.

      Best of luck on this, and let me know if you have any other questions.

      ——————————
      Kindest Regards,
      Jo deRuiter , MCP, DCP
      “That GP Red Head”
      AISLING DYNAMICS CONSULTING, LLC
      WEBSITE: https://aislingdynamics.com/
      BLOG: https://community.dynamics.com/gp/b/gplife
      GPUG Academy Instructor
      Dynamics GP Credentialing Council-Vice Chair
      770-906-4504 (Cell)

      ——————————
      ——————————————-

    • Laura Grewe

      Member

      December 17, 2018 at 4:36 PM

      Can you please confirmĀ for me the question – Ā When I look in tableĀ GL20000 and I see 2 records of the journal entryĀ does that mean thatĀ the transaction did post successfully to the GL?
      Ā 
      Ā 

      ——————————
      Laura Grewe
      IT-Application Analyst
      Lakewood Health System
      Staples MN
      ——————————
      ——————————————-

    DSC Communities replied 6 years, 8 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘CMXFR Bank transaction stuck in Update status’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

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!