PO Daily Receipt Registers posting VERY (!) slow

SOLVED

Sage 100c Advanced 2018 v6.00.10.0

When we update a Receipt of Good Register, even for just a small receipt, it can take 30 minutes or more to update.   No other updates in the system take as long


Is there a way to refresh the work/crystal files so as to clear this up?  If so, which files and what should I try?  I tried reinitializing some of the work files but no change.
Any other suggestions?

The process works, just slow as all get out and now starting to affect production.

Thanks

  • 0

    For all users or just one?

    For all workstations or just one?

    Does it take this long when done on the server?

    Any third party solutions?

    Where is the most time spent, is it the generation of the register document (up to the point where you are prompted to update the register) or after you click yes when prompted to update the register?

  • 0 in reply to David Speck

    1)  For all users
    2)  All workstations
    3)  Many 3rd party solutions, but nothing new recently.  This problems just started a month or so ago, last new 3rd party was at least 3 years ago
    4)  The screenshot I left above is where it sits and we wait.  

    We update journals an registers across Sage everyday pretty heavily.    There are no issues, except this one register.  And it DOES work, just takes where it should process in maybe 30 seconds, it is taking 15 minutes.

  • +1 in reply to RobertValencia
    verified answer

    I'd check for environmental changes (eg. new AV software...) and definitely try posting directly from the server.

    After that I'd look for orphaned data in the PO_Receipt... tables, especially PO_ReceiptReturnMatRqByPO. 

    (New framework "work" tables are always empty... and if your delay is after you clicked "Yes" to the update, you're past the report data prep. stage).

  • 0 in reply to Kevin M

    The screenshot appears to be the progress bar displayed while generating the report.

    1. What answers are you providing to each prompt that appears after clicking "Print/Preview?
    2. Has someone modified the default crystal report used for the register? 
      1. If yes, maybe they added a table that could be causing a bad join and causing the delay.
  • +1 in reply to Kevin M
    verified answer

    Thanks Kevin.  This seemed to do the trick.  There was some orphaned data  in PO_ReceiptReturnMatRqByPO.  Cleared it out and it's back to normal.

    Appreciate the time