Accounts Payable Bank Account Change

[steven_lawrence]

We have recently changed our bank. I have set up new bank account
records in A/P in Bank Account Information (P04130) and a new G/L
account for it as well.

I have changed the A/P AAI's to reflect the new default bank account
and also the Create Payment Groups dreamwriter to pick up this bank
account for cheques and BACS payments.

The problem I have is that all the existing open items (logged and/or
approved) that are waiting for payment were default coded to the old G/L
bank account at the time of entry.

The only way I can find to amend this is to go into Speed Release and
change each open voucher in the fold area. This is a massive task given
the size of our open A/P ledger.

Does anyone know of a program within JDE to update this globally ?
Failing this I'll be forced to revert to the Dangerous Friggin' Utility
route (DFU to some of you!)

I'm not very conversant with World Writer. I did see something about
that doing updates? Any ideas?

Thanks.

Steve.

A7.3 cum 14, V5R2, AS/400 620

 

[noordzee]

In P04570 Create Payment Groups you can override the Bankaccount in the processing options

 

[Colin_Hugill]

Hi Steven,



I have been through this before - as a quick suggestion based on what
you wrote, there are two immediate solutions that come to mind.



I have to advise - I have no access to an AS/400 (iSeries) and I am
rusty on the detail specifics



a) Use WW in update mode to change the bank account ref on the F0411
records for OPEN items only - you need to know how to use WW in update
mode and how to identify records with an OPEN amount. This may be a
problem for later cancelled/voided items (including cheques).



b) Use the "override bank account" processing option in the payment
process - from memory it requires that you nominate the account ID (i.e.
the eight digit internal JDE account reference for you new bank account
- not the usual BU.OBJ.SUB) also known as the short account ID. But you
need to enter it as an eight character value with leading zero's and no
preceding "*" which (at A7.3 cum 9) was what it defaulted to if you use
the F1 lookup from the proc option. From memory you need to define this
override account in the "Create Payment Group" process (somewhere about
Proc Option 13 through 15) - I can't remember any need to further to
specify it but please check your cheque print functions as well



My best guess would be to use option b). I know from practical
experience that this works perfectly once set up correctly.



Sorry I can't be more precise but I am sure you can work your way
through this - especially if you read the User Reference Guides and test
first in your test environment.







Regards,



Colin

 

[phoward]

You can use Speed Release to globally update to your new bank account. Inquire on the old bank account, "C" to change, type the new account over the old account in the header and hit F6 for global update. That should change all your open vouchers to the new account.

 

[Colin_Hugill]

Woops, I forgot to expand or add a point to my initial response. Pardon
the somewhat shorthand English (with some "Aussie" speak/spelling mixed
in). Using the override bank account approach through payment
processing also is more comprehensive in that if a cheque on the "old"
bank account is voided then the related vouchers will be made "OPEN"
again but of course will still have the "old" bank account reference.
If these "reopened" vouchers are to be paid on a new cheque from the
"new" bank account (as opposed to being voided themselves) the override
bank account approach will work fine. Ultimately the problem should go
away as the likelihood of voided cheques on the "old" bank account
diminishes to zero. Now if you have multiple bank accounts in use then
you need to do some deeper analysis/research to fully address the
problem - probably set up multiple DWV's for payment processing.



Regards,



Colin

 

[steven_lawrence]

Thanks for the responses - Colin you were particularly helpful. We have gone down the Dreamwriter/Processing Options route. I have created 3 new DWV's one for each company that we run on JDE. The override bank account field works fine - you just have to remember to use the short ID instead of the user friendly cost centre.object code format !

This problem will go away for us in a matter of weeks once all existing open vouchers are paid. All new vouchers are being coded to the correct bank account due to the AAI change.

Regards

Steve.

A7.3 cum 14, OS V5R2, AS/400 620



Woops, I forgot to expand or add a point to my initial response. Pardon
the somewhat shorthand English (with some "Aussie" speak/spelling mixed
in). Using the override bank account approach through payment
processing also is more comprehensive in that if a cheque on the "old"
bank account is voided then the related vouchers will be made "OPEN"
again but of course will still have the "old" bank account reference.
If these "reopened" vouchers are to be paid on a new cheque from the
"new" bank account (as opposed to being voided themselves) the override
bank account approach will work fine. Ultimately the problem should go
away as the likelihood of voided cheques on the "old" bank account
diminishes to zero. Now if you have multiple bank accounts in use then
you need to do some deeper analysis/research to fully address the
problem - probably set up multiple DWV's for payment processing.



Regards,



Colin!


Colin Hugill (Consultant) (World A7.3 cum12)

 

[Colin_Hugill]

Steve,



Many thanks on behalf of everyone on the lists for spending some time to
say you had some success with solutions to your post. It would be nice
if everyone took the time to do this but I know it is not a practical
reality.



"Yeah mate", the short ID is a gotcha along with the need for leading
zeroes - especially if you take the F1 then the "F" key to return the
ID, it used to insert an '*' in front of the leading zero (probably
still does!). It can be a proper bugger to think through the '*' when
you are under pressure.



Yes, the AAI entries are critical as they always have been in all JDE
application systems - and of course AAI's can be very beneficial once
you get your "head" totally around them.



By the way, if you have multiple "companies" set up in JDE and you want
to draw all AP cheques from one bank account in a one company for the
group then the override bank account "thingo" works fine but you need to
set up automatic inter-company AAI's to enable JDE to generate the
entries between companies. This has been done before (not just by me)
and works a treat. Remember that a "company" in JDE is any self
balancing entity - could be divisions or regions etc. but doesn't have
to be separate legal corporate entities.



Regards,



Colin