Personalization, Customization and Productivity Tools

[Elena]

A client has a very simple AR report, using the AR customer and AR terms tables in version 4.3 and is using the report to extract High balance, Current balance Ageing Categories 1-4 and a formula for total outstanding.  They are excluding some clients from the report.  The tables are linked  by the terms field - with an outer join.

If a cash receipt it posted in AR for a customer on this list and you select the refresh button, it does not refresh the data with this new entry immediately.  Try again in half and hour or so, and there it is.

This does not happen with sales invoices posted.  They appear right away.

I have tried to duplicate this off-site from the client, using test data,  but cannot.  It seems to work as designed.

Anyone have any ideas as to why there could be this delay ?

Many thanks.

[DFeller]

Are they saving the data with the report?

Dawn

[Elena]

No it is not checked.  Looks like this happens when they run the report for the first time after cash receipts have been posted.  The receipts are no included on the report at this time.  They then refresh, and then they see the result of the cash receipt entry.

Your thought on the 'save data with report' is a good one - but it is not, so that is not it.

thanks for the response.

[connex]

I would temporarily remove the outer join to the terms table to see if the performance issue goes away.  Since the terms could be in a group header then you have the option of making it a tiny sub report and eliminating the terms table and thus the outer join.

Another option would be to change the outer join to an inter join. The outer join is only necessary if there are some terms codes in the customer table that are not in the terms table. This shouldn't be the case. Should it?

[TomTarget]

There is a setting in A/R for when the aging buckets are recalculated.  If I recall, the options are always, never(?).  That doesn't sound quite but you'll get the point.  When trying to recreate the issue at your office, do you have this setting the same as your client?

Prior to 4.1,   the aging buckets were calculated only if you ran a statement or an aged invoice report.  This option if set to always would recalculate the number if you went in to customer maintenance,  however I don't believe that it recalculated at the time of postings.  

Because of this,  inquiries of these fields with crystal,  business insights explorer,  customized ALE lookups would not return current data.   I mentioned this to Sage and requested some way of updating the aging automatically when using these other methods but I never heard anything more about it.

Can't say I ever stumbled upon a difference between how A/R and S/O updates these items, but then again I wasn't looking for this..