Posts Tagged ‘Oracle’
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 »
Tuesday, March 20th, 2012 by Andy Coates
A question came up recently during an OBIEE 10g training course we were running which merits a note on the blog. As part of the training, a request was built that displayed the TopN most expensive projects within an organisation for a specified year. The question posed by a delegate was “how do I display the TopN most expensive projects across a range of years? For example, the top 3 most expensive projects on a year-by-year basis.
Read the rest of this entry »
Tags: Function, OBIEE, Oracle, rank, syntax, TopN
Posted in Business Intelligence, OBIEE | No Comments »
Friday, March 9th, 2012 by Andy Coates
Having worked with Oracle Business Intelligence (BI) products for several years, some colleagues and I recently spent some time evaluating a third party offering called “QlikView”. Whilst our main interest at Projected has always been Oracle’s BI Applications for E-Business Suite, the buzz being generated around QlikView intrigued us. The Oracle BI Applications provide pre-packaged analytics reporting built on OBIEE, so we were keen to see if QlikView was a suitable competitor to BI Applications for our E-Business Suite customers.
Read the rest of this entry »
Tags: BI Applications, Business Intelligence, compare, OBIEE, Oracle, qliktech, qlikview, scalability
Posted in BI Applications, Business Intelligence, OBIEE | 3 Comments »
Friday, February 17th, 2012 by Ian Boyling
If you are experiencing difficulties in seeing all your required Legal Entities as a List of Values (LoV) within the bank account definition form in Oracle Cash Management, following these simple steps will rectify the issue and unlock the LoV. This process will also explain how to grant permissions to a specific role or responsibility based on bank account use and maintenance.
- Login to Oracle Applications as sysadmin
- Select the User Management Responsibility
- Select the navigation path of ‘Roles and Role Inheritance’
- Within the field ‘Type‘, select Roles and Responsibilities
- Following step 4, a new field appears called ’Category‘, select ‘Miscellaneous’ as the value
- Within the ‘Application‘ field, select ‘Cash Management‘. Note: Add the name of the role or responsibility if known
- Click Go
- Search for the role or responsibility that you intend to use to create bank accounts. Note: The permissions you assign during the rest of this procedure will be aligned to the choice you make here.
- Click on the update icon against the desired role or responsibility
- A new window (update Role) will be displayed. Click the ‘Security Wizards‘ button
- Click Save and Proceed (if requested)
- Click the ‘Run Wizard‘ icon against ‘CE UMX Security‘ row
- Bank Account Security Management Window: In this window you can add all legal entities to which you wish to grant access and assign permissions based on the selected role or responsibility. Click the ‘Add Legal Entities‘ button and select any required legal entities that are not already listed.
- Choose each permission that you wish to assign to the Legal Entity for the role or responsibility relating to bank accounts and further use within the applications. Choices include Use, Maintenance and Bank account Transfers. Note: Each permission is explained at the foot of this procedure.
- Apply the changes and then verify in the Cash Management responsibility if you are now able to see the Legal Entities in bank account creation form.
Bank Account Grants: Permissions
Use: Allows the user to view the bank accounts for the selected legal entity in Cash Positioning, Cash Forecasting and Cash flows, as well as reconcile cash flows for the selected legal entity.
Bank Account Transfer: Allows the user to transfer funds from and to the bank accounts for the selected legal entity.
Maintenance: Allows the user to create and update bank accounts for the selected legal entity
Tags: Bank Account definition, Bank Accounts, Banks, Cash Management, CE, E-Business Suite, EBS, Legal Entities, Legal Entity, LoV, Oracle, Oracle Cash Management, Payables, R12, R12.1.2, Release12, Roles and Role Inheritance, User Management
Posted in E-Business Suite, Functional | No Comments »
Friday, June 24th, 2011 by Andy Coates
Budgetary control (or “funds checking”) functionality exists in both the Oracle Projects (PA) and Oracle Grants (GMS) eBusiness Suite applications. The purpose of the functionality is to provide an extra level of control over a project budget, preventing or warning users of overspends when or if they occur.
Read the rest of this entry »
Tags: Budgetary Control, Funds Checking, GMS, gms_bc_packets, Grants, Oracle, pa, pa_bc_packets, Projects
Posted in E-Business Suite, Functional | 1 Comment »
Oracle 
