General Ledger R12 Alternate Account: Great new functionality

In Release 12 Oracle has introduced new functionality Called ‘Alternate Account’. This new functionality is very usefull when when you have major changes in your account code combinations. Recently we have made major changes in the Accounting Flexfield for a customer and we have end-dated all active code combinations and defined a whole new range of code combinations. The new range was succesfully added to the old disabled range using the alternate account field.

With this great functionality we were able to implement a great and major change fast and at the same time we did not had to change the accounting created on already entered transactions (with old and disabled code combinations) in the subledgers (AP/AR). 

When Transactions in the subledgers are send to GL with old and end-dated code combinations, GL automatically replaces the code combination during Journal import what results into the alternate account when you post the journal. Of course there are some attention points that you have to take into account when implementing this solution but I’m very exited about this functionality!  See below picture the screen where you can use this new field.

Some of the attention points you have to consider are:

1. Alternate account functionality does not work (yet) for encumbrance accounting.
2. When you reconcile GL code combination balances with Subledger (AP/AR) balances at period-end you have to include the alternate account functionality because in the Subledger (AP/AR) the Balance is on the disabled account and in GL the Balance is on the Alternate account.

If you’re interested in using this new and great functionality and you want to know the whole story please let me know.

 Viewed 6975 times by 1938 visitors

Posted by: Menno Koomen (2 post(s)).

Menno Koomen is an Oracle Architect with more than 12 years of Oracle experience, mainly in the Financials area. His first 10 years he worked for Oracle Netherlands.