80
We have a customer who created a reversing batch, but the batch was not created, and I can’t figure out why. I checked DB tables, event logs, settings, etc.
The GL setup is configured so reversing batch is created upon release.
Any ideas?
*This post is locked for comments
[quote user="Toni Savage"]
Hmmm... makes sense, I guess. but specific to setup screens? Or screens where there is one screen that "owns" the record? BATCH table records are updated by all sorts of "tangential" processes, for example (releasing, posting...).
But that's good to know!
[/quote]
In general, those columns are updated when it makes sense from an audit standpoint. You can get an idea of those events by doing a SELECT DISTINCT LUpd_Prog FROM <TableName> on a database with some use.
Hmmm... makes sense, I guess. but specific to setup screens? Or screens where there is one screen that "owns" the record? BATCH table records are updated by all sorts of "tangential" processes, for example (releasing, posting...).
But that's good to know!
[quote user="Toni Savage"]
Shouldn't the gl setup table update every time they log in? Or AT LEAST every time they create and save any batch (last bat number)??
Could you have looked at the wrong setup table for the update date?
[/quote]
No, internal updates like that are not reflected in its LUpd_DateTime and LUpd_User columns. Those columns get updated only when program code explicitly updates them, i.e. when changes are made through the 01.95 Setup screen. BTW, changing the business date doesn't change the date used for LUpd_DateTime.
Shouldn't the gl setup table update every time they log in? Or AT LEAST every time they create and save any batch (last bat number)??
Could you have looked at the wrong setup table for the update date?
Well, I'm 99.9% sure they didn't do it through a SQL command.
Guess I'll just write this one off to one of those "oddities" that happen.
Thanks for your time. Appreciate it.
If they updated the table through the setup screen, then, yes, GLSetup.LUpd_DateTime would be updated. If it was updated through an SQL command, then all bets are off.
As the reversing batches are created by the same stored procedure (pp_01400) that released the original batch, I don't think you can blame a network issue.
I thought that might have been the case. But when I looked at the GL setup table to check on the last user update to it, there is a date of 4/8/2008. If they had changed that field, wouldn't it have a more recent date of last user update?
I also know they frequently have slow performance and network issues. Would that have prevented the batch from being created as well? You know, the network "hic-up" that some companies experience.
Thanks again.
As Batch.AutoRev is still 1, you're correct that the reversing batch never got created. My best guess is that the GL Setup option was set to generate while closing when the batch was released and subsequently changed to generate while releasing. In any case, this reversal should be done when you close the period.
Version = FP1
Batch status = P
Batch.AutoRev = 1
Period to post = 01/2010
GL period = 02/2010
Thank you...
What version? Are you sure the batch released? If so, is Batch.AutoRev on the original batch 1 or 0? Is this batch in the current period?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (