Showing posts with label Oracle. Show all posts
Showing posts with label Oracle. Show all posts

Wednesday, 31 October 2007

Oracle Release 12 - Sub Ledger Accounting

The new Global Architecture with R12 introduced the concept of ledgers each capable of providing differing accounting representations; one ledger for example could conform to IFRS, another to local GAAP.One of the key components is the new sub-ledger functionality.

This generates the actual accounting entries for each ledger dependant upon defined rules. In some respects this is similar to the dual posting in the Global Accounting Engine (AX).


In the above example, a single invoice generates the accounting for the Global COA, and the French statutory COA. The new terminology identifies a Transaction COA and an Accounting COA.
The mechanism to provide this functionality is the Accounting Methods Builder (AMB).

The AMB can derive accounts for individual segments or for the full code combination based upon the rules. This looks to continue the account generator /auto-accounting type functionality which has been used in various applications over the years.

Differing charts of accounts is only one feature of the sub-ledger engine; derivation rules at different levels from journal line to application can be specified, GL summarisation (summary / detail), reversal methods, and reporting sequences are other components. The AMB therefore provides the mechanism to build the rules that may apply for global management accounting, deriving accounting for corporate financial reporting, and individual country tax rules. This looks to be a powerful tool extending beyond the Alternative Accounting Representation functionality currently available in 11.5.7+, replacing the Global Accounting Engine (AX), as well as replacing many of the GL globalisation reports particularly within Europe.
Given the scale and complexity of the Oracle e-Business suite, the Accounting methods Builder looks as if it may become one of the key focus areas of the future.

Wednesday, 12 September 2007

Oracle ReportingStrategy




With the final completion of Oracle’s acquisition of Hyperion,the postioning of the reporting elements of their recent aquisitions is starting to emerge.

Oracle's go forward strategy is termed Enterprise Performance Management (EPM). This has has three elements, Performance Management Applications, Business Intelligence Applications and Transactional Systems.

Performance Management Applications will be based upon Hyperion System 9, and includes Financial Consolidation, and Planning and Budgeting. Performance Management Applications extend beyond Oracle EBS, and can sit over non-Oracle systems ( and includes certification for SAP). This continues Hyperions position as the market leader in reporting from disparate systems. Oracle Press Release

The Oracle BI financial analytical application is based upon Siebel reporting tools. This will supply analytical subject areas such as revenue analysis, working capital and profitability. The ad hoc reporting capability will be provided through a tool called Oracle Answers.

One of the key questions is what now happens to existing products such as Discoverer, Daily Business Intelligence, Enterprise Planning and Budgeting, Consolidation Hub, and other existing reporting products? Many of the products will now become part of Applications Unlimited (AU), though the investment in development may be low, which would steer users to the EPM framework. It has been indicated that Discoverer will essentially become part of AU, though investment would continue and workbooks can be included in various dashboards, though Oracle Answers looks to become the go forward ad hoc reporting tool of the future.




Oracle's reporting strategy has been confusing for users. Various reporting tools and intelligence products have been released over the last 10 years with no real continuity. Let us hope we will get stability and see tools develop and not have to contend with a new offering evey two or three years.

Monday, 3 September 2007

Oracle Release 12 - Ledgers and Ledger Sets

The organisational structures in release 12 include a new classification of ledgers, and together with ledger sets have the characteristics of sets of books, with the period close taking place at ledger set level.

Oracle outline 3 organisational axis - legal, business and functional.

Ledgers fall on the legal axis, providing a mechanism to record Establishments, Registrations, Jurisdictions, Legal Authorities and Associations. Legal entities own assets, financial transactions and have regulatory obligations. At it’s simplest a legal organisation (including public sector bodies) has a balance sheet, journal entries and some form of company return. Any Oracle set up needs to support these basic requirements.

Equating ledgers to the old sets of books we still have the 3 Cs – Chart of Accounts, Currency and Calendar, with a new C – Accounting Method (ok it needs some imagination).

So what can be considered within the fourth C – Accounting Method?

Country – Statutory charts of accounts have long defined the requirement for different sets of books, however with the use of sub-ledger accounting rules a further dimension is added to country specific requirements.

Jurisdiction – Even within a country there may be more than one set of rules that may necessitate separate ledgers

Case Study: One company found the tax laws between Beijing and Shanghai differed significantly for their organisation so 2 sets of books were deemed to be required.]

Case Study: Specific indirect taxation rules applied to one part of a business so separate sub-ledgers were required to handle that requirement.


Corporate Governance – Directors of a company are legally responsible for the activities of a company. With 11i, the sharing of a set of books can raise questions as to who has overall responsibility.

Case Study: Single set of books shared by 4 balancing entities caused reconciliation, control and responsibility problems. Company directors welcomed own set of books as it improved their control and corporate governance.

In release 12, 4 ledgers –essentially legal entities – and legal associations could solve 12 the problem encountered in the case study.


Accounting Sequencing – Many tax jurisdictions require that a legal entity has it’s own set of accounting sequence numbers, and that all the transactions in a ledger apply to that sequence. This is imperative where accounting entry reports such as the Libro Giornale in Italy, and the Brazilian General Ledger Daily Book. This requirement is common in Southern Europe, Eastern Europe and Latin America, with much of continental Europe looking for distinct sequence numbers.

What release 12 brings is a greater use of the Legal Entity organisational classification than we saw in previous versions. The key features being tax calculations, inter-company balancing and bank ownership at legal entity level.


Oracle R12 Financial Concepts - Organisational Structures

Oracle's new Financial Concepts manual provides a useful and practical overview of the structural elements within release 12.

Getting the structural elements correct within Oracle is a critical success factor for any Oracle system, notably organisational structures and flexfield design, particularly the chart of accounts, as these elements dictate the transactional and information flow through the applications.

In terms of structure, release 12 highlights the concept of system entities building upon the existing organisational classifications with 2 new crucial additions - Government Reporting Legal Entity and Ledger, giving the following "important system entities:

• Business Group and Departments
• Government Reporting Legal Entity (GRLE)
• Legal Entity
• Ledgers
• Operating Unit
• Inventory Organization
• Human Resources Organization


In terms of how these organisations are used, Oracle recommends looking at 3 axis - legal axis, business axis and reporting access.

Looking at the legal axis - business groups hold legislative codes determining what country specific HR / Payroll functionality is used, Government Reporting Legal Entities define which organisations hold contracts of employments, with Ledgers defining the financial legal dimension.

It should be noted that operating units hold transactions relating to a particular legal entity, and inventory is owned by legal entities. Any movement between them being an inter-company transaction.

Business organisations can be defined using HR organisations, the key here is to ensure that employee related transactions can be tied to ledger. A common example in global organisations being an employee who is on secondment may belong to a particular business organisation for business reporting, but his transactions would be required to be processed in the correct legal organisation.

If we equate ledgers to sets of books (SOB), then in terms of organisational structures there is no real change. The replacement of SOB by an organisational classification being an architectural change, though it is recognised that the ledger set up consolidates and develops existing functionality to produce a more comprehensive solution.

The use of Government Legal Reporting Entities is very useful, as it allows business organisations to be flexed to meet the challenges within a business, whilst still allowing for a separate legal employing structure which tens to be a lot less flexible.

One very welcome addition to the Oracle Documentation is the Oracle Financials Concepts Guide Release 12 authored by Seamus Moran. This manual not only outlines the concepts, but provides practical examples and tips for existing Oracle users.

Information: Oracle Documentation Library

http://www.foresightglobal.co.uk/Resources/oracle_R12Resources.htm#Oracle%20Documentation

Sunday, 2 September 2007

Oracle Integration Architecture

Oracle Integration Architecture is part of the Applications Unlimited policy. "Oracle has bought many best-of-breed and industry specific applications, and now we need to make them work together"

When Oracle EBS 11i was launched in 2001, the key message was "suite not kit", that is have an integrated business system rather than a number of different applications bolted together. Memories of the Oracle Rocky Horror show at Appsworld Paris, saw an Oracle musical outlining the folly of the best of breed approach.

So have Oracle done a U-Turn?

In terms of market penetration, the Oracle EBS would have needed to take customers away from their best of breed applications and to use Oracle HR, CRM, Financials etc., as well as meeting the needs of the SME's. Given the investment by many organisations in PeopleSoft, Siebel, JD Edwards, and a host of other applications, it would have taken Oracle many years to persuade customers to move to the Oracle EBS replacing their existing systems. The quickest way to gain that market and customer base was through acquisition. Within 6 years of the launch of 11i, Oracle have the customer base of the best of breed applications.

Fusion is still the ultimate goal of Oracle, so ultimately the "suite" should become more dominant than "kit". However, as Jose Lazares, Oracle VP for Applications Development outlines, Oracle Application Integration Architecture is an alternative migration strategy to Fusion "Adopting this looser abstraction between systems means that CIO's can plug in Oracle Fusion modules and evolve to it over time"

So with Applications Unlimited providing ongoing development with Oracle release 12, Lifetime Support protecting investment in 11i systems, and Application Integration Architecture bringing the best of breed applications together, it would seem that organizational investment will be preserved and business driven migration plans can be drawn up.

However - what are the timescales, and what precisely will be integrated, and what happens to current investments with Fusion?

Information:
Interview with John Wookey and Jose Lazares
(Oracle SVP & VP Applications Development)

Oracle Applications Integrated Architecture
.

Wednesday, 29 August 2007

Oracle aquires Hyperion

Oracle have continued with their acquisition policy by buying Hyperion.


Hyperion has been widely used as the consolidation tool to bring together data from different sources to provide the composite organization financial results.

The target customers identified by Oracle are the CFO office for Hyperion, and Oracle BI applications for line business managers. This would indicate the current Oracle BI products (Sales, Finance, Projects, Procurement, Supply Chain) will continue. The inclusion of Discoverer in the BI family, and the use in some product families of embedded workbooks provides further integration in the overall reporting concept.

So where does this leave the Oracle EBS user?

Hyperion has been the preferred choice of many Corporations, bringing together a myriad of ledger systems around the globe to consolidate corporate results. The integration with the Oracle EBS is often minimal, with a surprising number of major Companies relying on the key punching of of information from existing ledger systems, including Oracle, into the Corporate consolidation model. Before the acquisition of Hyperion, Oracle produced their own Consolidation Hub, which aimed to expand the consolidation functionality within the Oracle EBS to non-Oracle systems.

For users of Hyperion the key question will be around greater integration into the EBS, with Companies currently consolidating globally using existing functionality asking if Hyperion is part of the core EBS, or does it sit outside, continuing as the Oracle / non Oracle consolidation tool?

Information:
Hyperion web site with links through to the Oracle Hyperion page

Oracle Lifetime Support

The announcement of a new release can raise concerns for organizations as to the level of support they will receive for older versions and when that version will be de-suported.


To meet these concerns Oracle have announced a Lifetime Support Policy.


The implementation of the oracle E-Business Suite is often a significant investment in terms of expenditure, time and organizational change. Whilst the announcement of a new release can be potentially good news to Organizations, the downside is that having made that investment, or reviewing the new functionality and no cost benefit accrues, upgrading may make to business sense.


The Oracle support mechanism of announcing de-support dates for versions can lead to upgrades that organizations feel


The policy outlines 3 levels of support for the Oracle E-Business Suite:

  • Premier Support
  • Extended Support
  • Lifetime Support

    Whilst offering a Lifetime Support Policy, this looks to be an evolutionary process for customers on 11i7 onwards. Careful review of the ongoing support mechanism for your organization is recommended.

Information and Data sheet:
Oracle Support Page

Oracle Applications Unlimited

Applications Unlimited is Oracle's commitment to existing users of JD Edwards, Oracle EBS, Peoplesoft and Siebel to maintain and improve current product lines. The protection of investment in current software packages is vital, many organizations being concerned they would need to switch to a new product or forced to upgrade as a result of Oracle's new acquisitions.


To protect investment Oracle has outlined:

  • Brand new releases - commitment to existing product families
  • No forced migrations - upgrade when it is right for the organisation
  • Dedicated development teams - ongoing development and support

As part of the Applications Unlimited commitment to the E-Business Suite, Oracle announced the general availability of Release 12.


This is obviously a welcome step for all users within the new wider Oracle community. Fusion is still some way off, users of JD Edwards, Sieble and Peoplesoft find they are not been driven to use the Oracle EBS, with EBS users able to move ahead with release 12. In addition, Oracle's lifetime support policy potentially secures the investment for users EBS 11.5.7+, by providing sustained indefinite support. Release 12 focuses on global users, so unless there is specific functionality or technical enhancements which may benefit organisations, staying on 11i is a valid strategy.


Oracle seem to have all bases covered - let us hope with the diversity of products, applications and architecture that they can all be effectively supported.


Information: Oracle Applications Unlimited Program
Interview with John Wookey SVP Applications Development at Oracle

Tuesday, 14 August 2007

Oracle Release 12

Oracle's latest version Release 12 was made generally available in January 2007. The release aims to provide greater levels of control and transparency by use of a centralised financial architecture, whilst supporting local regulatory and cultural country specific requirements.

The key messages are:
· Think Globally - using business intelligence and analysis tools
· Work Globally - using the global capabilities of the applications
· Manage Globally - using the latest system architecture and middleware

The focus is on global operations and shared service efficiencies, as well as application specific improvements. One of the most fundamental changes occurs with the new Global Financial Architecture, which introduces 6 Major Initiatives.
· Ledger and Ledger Sets
· Multi-Org Access Control
· Sub-ledger Accounting
· Tax Engine
· Inter-company
· Bank Model

Ledger and Ledger Sets
Ledgers essentially replace Sets of Books, and introduce a 4th C to Calendar, Currency and Chart of Accounts, Accounting Method. The use of ledger sets replaces the Alternative Accounting Representation introduced in 11.5.7, and provides a rule-based mechanism for each ledger, overcoming some of the limitations of the current functionality.
The use of ledger sets streamlines the set up process; a single set of rules could be defined for all IFRS ledgers and attached to each ledger in turn. The local GAAP ledgers having the appropriate country specific rules.



Multi-Org Access Control (MOCA)
Very much aimed at shared service operations, access to operating units (OU) is role based, with a single responsibility able to access multiple OU.


Sub-Ledger Accounting
Sub-ledger accounting supports ledgers by generating the accounting entries for each ledger from a set of event based rules. A single transaction could therefore generate distribution lines for IFRS ledgers and local GAAP ledgers.


Tax Engine
The tax engine generates indirect tax entries based upon pre-defined rules - the 4 P's Parties / Places / Products / Processes. Tax entries are now held in a Tax Transactions repository to streamline reporting.


Inter-company
The Global Inter-company System (GIS), becomes Advanced GIS. The most significant feature being is the generation of invoices between companies, overcoming a major shortfall in existing functionality.


Bank Model
The biggest change to the bank model is that bank accounts are now attached at Legal Entity level rather than Operating Unit in current versions. The capability to pay across operating units is also been introduced. Banks accounts can be shared by applications and can be designed for use by Payables, Receivables and Payroll.

Thursday, 9 August 2007

Foresight Global Website



The Foresight Global website is up and running.

http://www.foresightglobal.co.uk/




The aim of the site is to provide resources to assist everyone in meeting the challenges of their E-Business suite implementations.

The main pages are:


  • Resource Centre Useful links to Oracle Sites / User groups /Reference Info / Books
  • Oracle EBS Overview of EBS Applications / Reporting Tools / Global Support
  • Global Information Reference of Globalisations /MLS /Local Books
  • EBS Framework Information on managing EBS / Support / Training
  • Oracle News Latest from Oracle / User Groups / Events

There are links to additional pages including information on release 12.