Out-of-balance Posting

Jeff73

Well Known Member
Hi everybody!
Does anybody out there know how to make it possible to post even though entries are "slightly" out of balance? If that's possible, is there a way to tell JDE to only allow this if difference is smaller than a certain threshold?
Thanks a ton,
J.
 
The only way I know how to do so is to go into the batch header itself and
change the flag.


What version are you running by the way? They are NOT all the same, believe
it or not, and we are not able to look over your shoulder.

Dale
a7.3c9
 
Well, you have the infamous F12 in journal entry that will let you exit data
entry out of balance. Do not know of anyway to only allow if smaller than a
certain amount. Now if you are talking about something other than journal
entry (going through applications that hit the P09800 program), I am not
aware of a way to make those post out of balance.

John Dickey
JDE Financial Systems
Administrator/Programmer/Analyst
White-Rodgers, Division of Emerson
St. Louis, MO
314-577-1466
 
Re: RE: Out-of-balance Posting

Change the batch header to post out of balance and change the intercompany settlements in the system setup to * (do not create intercompany settlements). The system will reset the batch status to Y after the update program is run.
 
Re: RE: Out-of-balance Posting

Thank you guys a ton. We're running A7.3... I hope what you said applies to this version.
Thanks again,
J.
 
Re: RE: Out-of-balance Posting

Bouncer,
Thanks. Could you please describe in more detail what I should exactly do? I am more concerned with posting AP entries resulting from vouchers...
Appreciate it.
J.
 
RE: RE: Out-of-balance Posting

Go to menu G0931 use option #2 Inquire on the batch and then change the
"Post Out of Balance (Y/N)" flag. I assume you only want to do this once,
and this is not an ongoing process?
 
Are you trying to post because you need, or you are not able to fix the batch?

All the thing was told by the people are correct, but it is mostly applied to not legal ledger. To the legal ledger (AA), the balance is mandatory, no matter how small is the diference.

If you are taking problems to realize which transactions are out of balance, run the integrity reports to find out. But if you are sure enough to post anyway, just change the batch header and do it (the menu is G0931 option 2).

hugs,
 
It is a known issue for JDE to get AP Voucher batches to be out of balance -
because of rounding issues. In a few companies that I have been at, we have
created reports that assist the users to review the vouchers to find the
offending entry.

An update WW was created to allow them to select a specific entry and change
it in the file and then post the batch.

Posting out of balance would not be a recommended way of fixing the problem.
 
Thanks a ton. Really appreciate your reply, which was very helpful.

I'm actually trying to post out-of-balance transactions that are related
to foreign purchases. According to our accountant, most of the time the
differences are tiny (pennies) due mostly to rounding errors and exchange
rates. So, ideally, she'd like to be able to post them anyways provided
the difference is smaller than a certain amount. Since I haven't been
able to find a way of doing so, I suggested she run her batch in proof
mode first so she could check out the figures for herself. If she decides
that's small enough, she can go ahead and run her batch final after she's
changed the batch header. I don't know if I can automate the "header
changing to Y" so she only clicks a button so to speak...

Thanks again and have a great day,

J.
 
Thanks. What happens after one posts out-of-balance entries? I guess one'll still have to get into the system later on and make new entries to balance out. Is that correct?
J.
 
At my last job, an accountant used to run a query to look at which batches were out of balance in the CA ledger and give me a list at the end of the month so that I could DFU the pennies back in to make it balance. JDE has never gotten the currency rounding thing straight.
 
Same thing here Jean - especially on AR - it's almost daily.
I ended up creating a DFU specially for the accountants to use, displaying a
few key fields and only allowing them to update the amount field on the
posting record.
That at least allowed them to correct the batches quickly without having to
wait for MIS.

Another BIG problem we found when there was a delay in correcting the
information is that it is possible to allocate cash receipts to sales
invoices that are not yet posted (ie: the batch did not balance and it has
not yet been corrected). When you try to post the batch of sales invoices,
because some of them are now partially / fully paid, the GL postings are
incorrect, and it's a nightmare to correct.

This wouldn't happen if JDE modified the programs so that the total value of
an invoice in base currency was calculated as the sum of the base currency
amounts in the invoice details, rather than converting the invoice total in
currency to base currency, which will almost always give roundings. This is
one of the first things a programmer ought to learn when dealing with
multiple currencies, however whoever modified JDE to handle multiple
currencies didn't appreciate this for some reason.

I have no idea why they won't fix this, since it does not add to the
credibility of their accounting modules.

Just my 2cents worth...




Tony Payne - Senior Systems Analyst
Conn-Selmer Inc.
Elkhart, Indiana 46516
 
How did you do that exactly? Just via JEs or is there a specific way recommended by JDE?
Thanks,
J.
 
Not recommended by JDE. Via AS/400 database tool Data File Utility (STRDFU)
or SQL.



Jean Driscoll
AS/400 Co-existent Xe 17.1, Update 4/A73Cum12
 
Re: RE: Out-of-balance Posting

Hi,

Would really appreciate it if you could describe that WW in further detail.

Thanks,
J.
 
RE: RE: Out-of-balance Posting

Here are the specs on the WW for the update. Basically after finding the JE
Line number in error, the WW would be changed to reflect the line number,
batch type, batch number, document type, and document number (not all are
needed, but since allowing the users to fix it, it is probably better to be
overly cautious).

The user will also have to be authorized to update field GLAA in F0911 and
be authorized to do an update in that group.

82104 Output Field Specifications Group. . Q04AP
Version. UPDATE1
Total Width . . 79

Seq W P Col Sup Edt Prt Num
Output
Opt No. Description Size L W Sp Hdg Cde Dec Scl
Field
10 Document Type. . . . . . 2 N A *DF N GLDCT
20 Document Number. . . . . 8 N A *DF N Z 0 0 GLDOC
30 G/L Date . . . . . . . . 8 N A *DF N W 0 0 GLDGJ
40 Journal Entry Line Number 7 N A *DF N 4 1 0 GLJELN
50 Batch Number . . . . . . 8 N A *DF N Z 0 0 GLICU
60 Batch Type . . . . . . . 2 N A *DF N GLICUT
70 Amount . . . . . . . . . 15 N A *DF N K 2 0 GLAA
80 new amount 15 N A *DF N K 2 0 NEWAA









Opt: 1=Calcs 5=Fld Det 9=Del F13=Layout F15=Dsp Tag'd F16=Dsp All



82107 Data Selection Group. . Q04AP
Version. UPDATE1
. . . . . . Selection . . . . .
Opt And/Or Description Test Value
AND Document Type. . . . . . . . . EQ 'P3'
AND Document Number. . . . . . . . EQ 289177
AND Journal Entry Line Number. . . EQ 4.0
AND Batch Number . . . . . . . . . EQ 346654
AND Batch Type . . . . . . . . . . EQ 'V'
AND G/L Posted Code. . . . . . . . NE 'A'





Opt: 5=Values 9=Delete F4=Dtls F15=Dsp Tag'd F16=Dsp All F24=More




















82108 Data Sort & Totaling Group. . Q04AP
Version. UPDATE1


Tot Page Line Sum Sort
From
Opt Description Seq A/D Lvl Skip Spc Fnc Field
File
Journal Entry Line Number. . . 10 A N *DF Y GLJELN
F01







Opt: 1=Tot Flds 9=Dlt F4=Tot Txt F13=Layout F15=Tag'd F16=Dsp All
 
Back
Top