CUSTOMER STATEMENTS

Why is it impossible to print statement of accounts reports in SAGE 300 simultaneously across a number of workstations?

When one of the users in a given workstation tries to print a report and their is another user who has opened this module, the error message below pops up. 

This is the Error that the user experiences. 

"Description: Incomplete statements exist. You must finish the incomplete statements before generating new statements."


Top Replies

  • Hi  its impossible because there is a lot going on behind the scenes when you print statements.  The statements report is designed so that you can do a statement run every day, week or month (whatever…

Parents
  • Hi  its impossible because there is a lot going on behind the scenes when you print statements.  The statements report is designed so that you can do a statement run every day, week or month (whatever cycle you choose) without having to think or manually keep track of who has received what, avoiding bombarding customers with duplicate statements, only receiving new statements once they've moved into a new aging period along with a new dunning message.  When you perform a statement run it gathers all the past statement information regarding each open document, calculates what action is required, and places those into a temporary table.  You can then email out all the statements easily via bulk SMTP or Microsoft Graph integration.  I haven't had any clients want to run this across several workstations as even if several hundred statements are going out - or more - they just run it over lunch, at end of day, from an RDS session or a spare workstation if they don't want to be tied up during the send.  If the bulk email send-out, or collating of statements is taking a very long time, then review network throughput to the server, and check for any giant logos/graphics in the statement template.  Good luck!  

Reply
  • Hi  its impossible because there is a lot going on behind the scenes when you print statements.  The statements report is designed so that you can do a statement run every day, week or month (whatever cycle you choose) without having to think or manually keep track of who has received what, avoiding bombarding customers with duplicate statements, only receiving new statements once they've moved into a new aging period along with a new dunning message.  When you perform a statement run it gathers all the past statement information regarding each open document, calculates what action is required, and places those into a temporary table.  You can then email out all the statements easily via bulk SMTP or Microsoft Graph integration.  I haven't had any clients want to run this across several workstations as even if several hundred statements are going out - or more - they just run it over lunch, at end of day, from an RDS session or a spare workstation if they don't want to be tied up during the send.  If the bulk email send-out, or collating of statements is taking a very long time, then review network throughput to the server, and check for any giant logos/graphics in the statement template.  Good luck!  

Children
No Data