As I said in the original response we have found that there are occasional transactions in Cardex that the R41542 misses writing to the ASOF. Oracle chalked it up to Average Cost and no action taken. You didn't state what release you are on, so maybe it is fixed in later releases.
I think I did not answer your original question well with my first post. We do the process in my response to keep the ASOF accurate with the Location file. This enables a direct connection/validation from G/L to the Inventory value in the Inventory system (Location file). It also cleans up the ASOF locations which have dollars but no quantity (the result of having Average Cost at the Branch level).
Here is how our accountants validate the G/L:
Daily:
R42542 is run each night after batch processing.
1. Run a Trial Balance by Object
2. Run a custom report that pulls the ASOF by Item, Branch, Location
If the totals don't match (ignoring rounding errors):
1. Run Access query on Cardex by Doc Type
2. Run Access query on G/L by Doc Type
Identify the culprit Doc Type and run detail queries on Cardex and G/L for that Doc Type to find the missing/broken transaction.
We are a manufacturing and distribution company with thousands of transactions daily. Being on Average Cost, our accountants keep a daily watch to fix errors both in the Branch Unit Cost and the GL. They work closely with manufacturing, warehouse, purchasing to educate users and/or modify processes to reduce the errors.
The result, over time, has been very little time spent investigating and fixing errors.
We do run the R41543 every Saturday night, but they rarely reference it.
I hope this helps explain things more clearly.
Jer