I am trying to close my current period but I have a batch in the Post Transactions screen that will not post. It is from the BI module. I ran a Invoice register report and the batch it not on there. I think this is due to someone cancelling a posting process and it being corrected in Project Parameter Maintenance. Can you please tell me how to fix my post transactions so that I can close my period? Thank You
*This post is locked for comments
Thanks Rick for your help.
I want to pop in on this issue to tell everyone that we do have a bug that is often or likely the issue when you have a BI batch that says it is out of balance.
We have bug 16261
Flexible Billings invoice batch numbers and AR batch numbers can overlap and cause issues.
KB 2953578 gives the update for this for 2011 sp1.
Change from this bug:
Billings Setup (BI.SET.00) now contains a new field "Last Invoice Register Batch#". The field may be used to change the Flexible Billings AR batch numbers so they do not overlap with batches created in Accounts Receivable.
But, if you don't know to make the batches so that they don't overlap, you can still run into this issue. Documents that are already released in AR batch number 123456 get included with BI batch 123456 and visa versa. Batch out of balance is the usual message but that may be at release time rather than at posting time.
This is fixed in ver 2015 via bug 25080. Per the change noted:
The Billings Setup screen now defaults the "Last Invoice Register Batch#" field to "000000" for new databases. The Invoice & Adjustment Posting screen creates an Accounts Receivable (AR) Batch alongside the Flexible Billings (BI) batch that it had made previously. The BI ARDoc can no longer be incorrectly retrieved with a selection of ARDoc’s from an AR Batch.
Programs changed.
BISET00.exe, BIREG00.exe
So there will no longer be an issue in 2015 (which is now in beta) regardless of batch number overlap.
Thanks for your help. I was able to get this taken care of through Initialize mode.
That message normally means that the sum of the transactions does not equal the batch control total. If you have access to the SQL Server Management Studio and know how to run queries, run the following:
SELECT SUM(CRAMT) FROM GLTRAN WHERE MODULE = 'BI' AND BATNBR = '106868'
compare what the query returns to the batch control total. If that matches, run the following:
SELECT SUM(DRAMT) FROM GLTRAN WHERE MODULE = 'BI' AND BATNBR = '106868'
compare that result to the batch control total.
If you do not have access to SQL Server Management Studio you can turn on initialize mode and open the GL Journal Transaction screen. Select BI as the module and then select this batch. Add up the credit column amounts and the debit column amounts and make sure both match the control total and the amounts showing on the screen.
If everything matches (debits and credits and control total) then you must have an invalid account number being used or an account number that is flagged as inactive. However, the event log would normally tell you if this were the case.
One other possibility is that the batch, somehow, ending up with an extra transaction line that needs to be found and removed but let's cross that bridge if nothing else is found.
The event log says the following;
Module: 'BI'
Batch: '106868'
Processing: Module: 'BI' , Batch: '106868'
System Message 3011: is not in balance and not posted.
You need to run post transactions again and see if it finishes with a dialog box saying that an entry was made in the event log. If so, one the event log and see what was recorded as the reason the batch did not post. Report back what it says.
#1
Community Member
136
#2
Mohamed Amine Mahmoudi
102
Super User 2025 Season 1
#3
REUser
8
Share
Report
All responses (
Answers (
