Oracle describes R12 as "the global business release," and much of the focus has been on improving the ability of EBS to better manage complex global businesses, especially where organizations are centralizing their applications into a shared service environment. Some of the key enhancements include the introduction of a Common Accounting Engine with Subledger Accounting (SLA) and Multi-Org Access Control (MOAC). This article examines how to best use a single chart of accounts and a single instance to leverage R12 functionality to meet the globalization challenges.
Ledgers have replaced the concept of sets of books in EBS. A ledger can have its own accounting method, calendar, currency, and chart of accounts. Ledgers can be combined into ledger sets for processing all transactions. This means that a user can enter a single transaction in the primary ledger, and by defining create accounting rules and events, can update multiple ledgers without having to reenter the same information for each transaction. In a global environment, a company might have ledgers to comply with statutory requirements of a particular region or to report on the same data in a different way. For example, most organizations with foreign subsidiaries need to prepare their consolidated financial statements according to IFRS (International Financial Reporting Standards) and also US GAAP standards. Using SLA, a company can have one ledger that complies with IFRS and one that complies with GAAP accounting methods, post the transactions one time, and generate the consolidated reports from both ledgers. When a user posts a transaction type to the primary ledger, the “Create Accounting Function” uses a set of rules to update the statutory ledger. In R12, Oracle also introduces a single accounting engine to manage all posting activities into the general ledger. In prior releases, modules such as AR and AP contained their own rules for posting accounting events into the general ledger. The universal posting engine streamlines the close process. By applying standard accounting rules to all business transactions, SLA ensures consistent financial reporting. If the business uses a single chart of accounts, the user only needs to define the rules to create the transactions for posting to the GL or to subledgers one time, and then all the related subsidiary ledgers in a ledger set will be updated automatically. Users need to support only one set of rules, and maintenance of rules is simplified. A single global Chart of Accounts and a single global instance reduces the time spent compiling, reconciling, and consolidating financial data from disparate systems and spreadsheets and reduces the close time between the different modules and the general ledger. With a single chart of accounts and SLA, accounting policies are standardized across the entire enterprise and everyone adheres to the same set of rules and definitions. The data remains consistent, has full drill-down and roll-up capability, auditability, and visibility into all of the activity for the entire ledger set.
Multi-Org Access Controls provide the ability to manage customers and suppliers across operating units without changing responsibilities. Users can be assigned to multiple operating units, and processes and transactions can span operating units. MOAC increases the efficiency of operating a shared service center with streamlined access, processing, and reporting across operating units. Operating from a single global instance ensures global corporate consistency and global visibility. From a single global instance, MOAC provides the ability to negotiate with suppliers and leverage purchasing power across the enterprise. A single global instance with MOAC implemented allows customers to make decisions based on complete information, even when the business crosses regions and divisions.
eprentise is in the business of helping organizations that run Oracle E-Business Suite by providing transformation software. These customers have particular Oracle-related challenges when they “upgrade” their business at a macro level and want their Oracle instance or instances to follow and support the new “release” of the business. EBS’s strength is in running the business. The implementation of EBS is a model of the business’ organization and processes. EBS was not engineered to make it easy to change certain key aspects of the implementation — the model of the business — for a business “upgrade”.
The complexity of EBS meant that customers had few options other than reimplementing if they wanted to keep their systems aligned with the business changes. A series of reimplementations is not only costly, it is unnecessary.
eprentise Transformation software was architected from the ground up with the purpose of providing enterprise agility to organizations that rely on OEBS for their financials and day-to-day operations.
eprentise also works with System Integrators, Consultants, and Professional Service firms who help EBS customers.
