Saturday, April 28th, 2012 by Ian Boyling
Oracle introduced new functionality in R12 called ‘Alternate Account’. This functionality is very useful when you have a need to disable and/or end date an account combination within your chart of accounts or you have a significant requirement to change mass chart of account values. There are two key uses of this functionality. Firstly, you may wish to make specific account combination(s) obsolete and replace it with new account combination(s). You may also wish to change a range of combinations that contain a specific value within a single segment (e.g. natural account XXXX) disabling all associated combinations and then add ’Alternate Accounts’ that have been changed. Alternate accounts can therefore be very useful if you have a significant account combination change requirements within your chart of accounts. The screen shot below shows the definition of an alternate account on single combination.
Secondly, the functionality is particularly helpful when you have open transactions created against the end dated/disabled account combinations. This is the interesting element to defining alternate accounts. For example, where you have a number of sub ledger transactions that have already been accounted against the end dated or disabled combinations and are transactions that are still in process, e.g. an invoice on hold, you do not need to change the accounting created on these existing transactions. When these transactions are subsequently imported into General Ledger (GL), the old combinations are automatically replaced with the alternate account combination(s) during the journal import and create accounting process. This adds value and efficiency to transaction processing and prevents the need for mass changes to ‘In Process’ transactions. It also prevents import errors and reduces the amount of manual intervention from a user.
There are some considerations that require thought when using this functionality:
- Alternate Accounts do not currently work with encumbrance accounting
- When reconciling GL and AP/AR code combinations balances at period end you will need to include the alternate account related transactions since the sub ledger balance will be based on the disabled accounts, however, the GL balance will include alternative account based balances.
I hope you find this useful.
Ian
Tags: Account Combinations, Accounts Payable, Accounts Receivable, Alternate Account, AP, AR, Chart of Accounts, Code Combinations, E-Business Suite, EBS, EBusiness Suite, General Ledger, GL, Oracle, R12, Reconciliation, Release12, Segments, Values
Posted in E-Business Suite, Functional | No Comments »
Thursday, September 3rd, 2009 by Barry Crawley
This question comes up at some stage on most Oracle implementations where Projects and GL are involved. Every implementer has an opinion. So how do you come up with decision, without endless meetings and writing papers to highlight advantages and disadvantages, etc.? Well, I think the decision can be crystalised into a couple of salient points.
- If you have a Project segment in GL, which application has primacy for reporting by Project? By any measure this has always got to be Oracle Projects, and if not there is little point in implementing OP at all. There will almost certainly be constant disputes between the applications user community about which application is correct for project reporting - it is OP.
- There must be some significant advantage if an organisation wants to have a Project segment in the GL. One reason often given is to simplify reconciliation between OP and GL. A Project segment in GL will not simplify reconciliation and it will not help keep GL and OP the same from a Cost and Revenue perspective. A good reconciliation report will do this without a Project segment in GL.
No further examination into specific advantages and disadvantages is required.
I am interested to hear people’s experiences and views on this.
I posted a similar question on a LinkedIn Group discussion - Oracle Projects Application Gurus. The post got lots of excellent responses, which I am happy to share on request. Or if you want to join the forum, go to Oracle Projects Application Gurus Group. Once you have joined go to Project Segment in the GL or Not?
Tags: GL, Key Flexfield, Project Segment, Projects, Reconciliation
Posted in E-Business Suite, Functional | 1 Comment »
Tuesday, July 7th, 2009 by Andy Coates
As a Projects user, an annoyance that I continue to encounter with Payables is that the pa_addition_flag is not shown as a column for Payables invoice distributions. The pa_addition_flag shows the status of Projects-coded invoice distributions, and among other things, indicates whether an invoice distribution has interfaced successfully to/from Projects. Therefore, if this flag were shown in the form, it would be immediately useful for functional Projects users trying to reconcile discrepancies with Payables. I was hoping that this flag would appear in R12.1.1, alas it has not.
For more information on the pa_addition_flag and for the meanings of the values it holds please refer to Metalink note 226881.1
Read the rest of this entry »
Tags: Invoices, Payables, pa_addition_flag, Projects, R12, Reconciliation, Release12
Posted in E-Business Suite, Functional, Technical | 4 Comments »
