Hi, What does Close Statement Cycle do? Does it prevent certain items from being changed, for example, open Invoice Entries that haven't been printed/processed yet? Thanks.
Hi, What does Close Statement Cycle do? Does it prevent certain items from being changed, for example, open Invoice Entries that haven't been printed/processed yet? Thanks.
The Age Customer Detail (08.530.00) screen will update the Aging Balances. It is usually run in conjunction with the Close Statement Cycle (it is an option on that screen), but can be run separately using the 08.530.00 screen. See below from Help menu:
Age Customer Detail (08.530.00)
Used to recalculate the aging information of customer balances according to the due dates on open customer invoices, debit memos, and finance charges. This process can be performed as many times during the statement cycle as needed for reporting purposes.
Interesting regarding the ARStmt table update. This field used to be updated but, looking at a few of my client's current data, it appears that it is no longer updated. However, I did look at the AR_Balances table and those fields appear to be updated so I am not sure what you are seeing in that table unless no one has run the Close Statement Cycle or the Age Customer Detail process.
I am not aware of any other process that would affect the movement of values between the aging columns in the AR_Balances table. However, I need to qualify that my clients only utilize the core SL modules so it is possible that one of the modules other than AR might also do this. There is a column called LUpd_Prog that reflects the program that last updated the row in that table. Of course, if your table does not have any current updated information in it then this column contents would be old as well.
Thank you Mark and Rick.
Unfortunately, tables ARStmt and AR_Balances don't get their LUpd_* columns updated during AR Aging and Statement Closing.
We don't utilize the statements, only AR Aging. The last time AR Aging and Statement closing occurred was 12-2016, but nobody said they run either processes. Could there be some other automated process that does AR Aging on a monthly bases?
Could AR Aging and/or Statement Closing be done by running a SQL stored proc?
Thanks
Also, to add to what Mark posted, if you utilize a balance forward statement presentation then Close Statement Cycle also determines the balance forward amount for those statements. It does this by summing up all open documents with a previous statement date (previous to the current close date). It also sets the statement date to any new documents (those without a statement date) to the current close date.
You can see who last closed a statement cycle with the following query
Select LUpd_User, LUpd_DateTime from ARStmt
You can see who last aged balances with the following query
Select LUpd_User, LUpd_DateTime from AR_Balances
Note the first query will have a line for each statement cycle you have created. The second query will have a line for every AR customer.
You can query the ARStmt table, and look at the CloseDateTime field, as well as the LUpd_DateTime and LUpd_User fields.
Is it possible to find out who closed the last Statement Cycle and/or Aged the Balances?
All it does is create/update the aging data necessary for the AR Statements to print.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,558 Super User 2024 Season 2
Martin Dráb 228,647 Most Valuable Professional
nmaenpaa 101,148