Posts Tagged ‘Release12’
Thursday, May 10th, 2012 by Ian Boyling
A new feature within Release 12 of Oracle General Ledger is the ability to copy previously created journals. You can now copy entire journal batches with any status by using the AutoCopy button which is strategically placed on the Journals Workbench, Journal Batches and Journal forms. When copying Journals, you are prompted to create a batch name, select a period and/or the effective date.
Clicking OK will then submit a concurrent request called ‘Autocopy Journals’. Once this is complete, you can modify and update the batch, journal and lines in the normal way.
This is useful functionality and will reduce the amount of effort required to re-create common journals should the recurring journal functionality not be suitable.
I hope you find this useful.
Ian
Tags: Copy Journals, E-Business Suite, EBS, General Ledger, GL, Journals, R12, Release12
Posted in E-Business Suite, Functional | No Comments »
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 »
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 »
Tuesday, January 31st, 2012 by Barry Goodsell
In Part 1 of this article, we showed how to customise the values in the Mileage UoM drop-down list. However, we feel that customisations should only be used as the last resort, when all other options have been exhausted. A change to the View Object’s XML file (as suggested by Oracle) will not be resilient across patches and upgrades.
The Oracle Application Framework (OAF) provides a mechanism for us to provide a substitute definition for a View Object, With this mechanism, any time the Framework asks for the UnitOfMeasuresVO it will actually get our personalised version. The easiest way to create a personalisation of this type is to use the appropriate version of JDeveloper. You cannot use the mainstream version of JDeveloper from OTN – you need to download one that has the correct version of JDeveloper that has the OA Extension built-in (see MOS Note 416708.1 for more details).
Read the rest of this entry »
Tags: BC4J, E-Business Suite, OA Framework, Personalisation, Personalization, R12, Release12, View Objects
Posted in E-Business Suite, Technical | No Comments »
Thursday, November 25th, 2010 by Steve Harfield
Summary
In R11 and earlier releases, the sub ledgers are the source of reference for the account coding of Project transactions via Distributions. With the introduction of Subledger Accounting (SLA) in R12, this is no longer the case. Subledger Accounting is a rule-based accounting engine that defines how journal entries are generated for subledger transactions in Oracle E-Business Suite. All subledger accounting is managed by SLA, i.e. journals are not posted directly to the GL from a subledger but are now “processed” by and through SLA. SLA does not exist as a separate discreet module. It is an underlying engine that provides a set of functions, supported by a new schema and underlying tables, that will allow configuration and maintenance of accounting rules. These are accessible within the subledgers as additional menu functions.
Subledger Accounting Menu Functions
For Projects, the Subledger Accounting inquiries appear under the new heading Accounting Inquiries and include:
- Accounting Events
- Journal Entries
- Journal Entry Lines
The Setup menu options for SLA have also been added to the Setup Navigation branch of the menu.
Subledger Accounting Setup Menu
The SLA Accounting Process
As the subledgers record new transaction entries and adjustments, and validate them, they become eligible for accounting by SLA. Eligible transactions are processed by the running of SLA-specific concurrent requests. These requests will vary from subledger to subledger but ultimately, SLA accounting is completed by performing two steps.
Read the rest of this entry »
Tags: R12, Release12, SLA, Subledger Accounting
Posted in E-Business Suite, Functional | No Comments »
