|
ATTENTION |
From Release 8.1, the Management Ledger replaces the Ledger/Stat table as the central repository for management accounting within OFSAA Enterprise Performance Management solutions. Ledger/Stat will continue to be supported for existing or upgrading customers, but it will not be included as part of a new installation. |
The new Management Ledger supports the same functionality as historically has been supported by Ledger/Stat and stores the same kinds of data as has always been housed in Ledger/Stat including:
· General Ledger Data
§ Reconciled to instrument level data
§ Typically provides a starting point for management accounting processes
· Budget or Forecast Data
§ From OFSAA Balance Sheet Planning or from other budgeting and forecasting sources
· Multidimensional Statistical or Volumetric Data
§ Used or created by allocation rules
· Value-Added data From
§ OFSAA Profitability Management allocation rules
§ OFSAA Funds Transfer Pricing processes
§ Other value-added processes
1. How do OFSAA Infrastructure and Applications interact with the Management Ledger table?
Loading Staging Data into the Management Ledger Table
§ OFSAA Infrastructure 8.0 and above includes a T2T rule (T2T_MANAGEMENT_LEDGER) for loading the Management Ledger table from STG_GL_DATA
OFSAA Funds Transfer Pricing
§ Funds Transfer Pricing 8.0 and above supports the same functionality with the Management Ledger as historically has been available with the Ledger/Stat table
— Direct transfer pricing of ledger-level balances
— Aggregation/migration of instrument-level transfer pricing results to the ledger-level (weighted average rates and charges & credits for multiple FTP components)
OFSAA Enterprise Financial Performance Analytics
§ OFSAA Enterprise Financial Performance Analytics 8.0 and above includes data movement processes for loading its results tables from either Ledger/Stat or Management Ledger
Other OFSAA Applications
In future maintenance releases, all other OFSAA applications that interact with the Ledger/Stat table will be enhanced to offer substantially identical functionality with the Management Ledger table
§ OFSAA Profitability Management
— Distribution of balances within the management ledger level
— Aggregation and posting of instrument or transaction summary level data to the management ledger level
— Distribution of ledger-level balances to the instrument or transaction summary level
— Any other kind of Profitability Management process involving management ledger level data
§ OFSAA Balance Sheet Planning
— Bi-directional data integration between OFSAA relational stores of ledger-level data and Balance Sheet Planning
2. What are the functional advantages of the new table structure?
Enhanced multi-currency model
§ Functional & Entered balances for each row
§ More straightforward integration to multi-currency General Ledger systems
§ Simplified reconciliation of ledger-level data with multi-currency instrument data
§ All value-add processes post simultaneously to both Entered & Functional balances
— Funds Transfer Pricing
— Profitability Management
Daily posting/monthly processing
§ Supports daily posting to the Management Ledger level
§ Particularly useful for customers who want to post daily FTP results to the ledger level
Multi-Entity/Multi-Tenant functionality
§ Multi-entity functionality, also introduced in release 8, is available with the Management Ledger table but is not supported for Ledger/Stat.
— See Multi-Entity Appendix for details
Future Enhancements
All future enhancements to OFSAA applications that utilize ledger-level data will be built to support the Management Ledger structure
3. What are the technical advantages of the new table structure?
§ The structure of the Management Ledger table eliminates of the need to
— Generate YTD balances for every row at time of insertion
— Refresh YTD balances for every row at time of update
— Store YTD balances on every row
§ YTD balances may still be referenced in Profitability Management rules
— The engine can easily generate this data when needed but the cost of calculation and storage for every row is eliminated
4. Can I have multiple Management Ledger tables?
Yes. The Management Ledger table is a seeded table but Management Ledger is also a table class. If you do establish multiple Management Ledger tables, you must manage the data in each table and its relationship to instrument level data or to other data in your Information Domain. See “Adding Management Ledger Class Tables” in the OFSAA Data Model Utilities User Guide for Release 8.0.
5. Will customers need multiple Management Ledger tables?
Most customers will not need multiple Management Ledger tables. Utilization of multiple Management Ledger tables might be useful for some multi-entity or multi-tenant implementations.
6. Can different Management Ledger tables have different dimensions?
Yes, different Management Ledger tables may have different dimensionality.
7. Can I move data between Ledger/Stat and the Management Ledger table?
No. All rules and processes that post to or read from the ledger-level can utilize only one ledger table.
8. How long will the Ledger/Stat table be supported?
§ Release 8.1 as well as all previous OFSAA releases will always support the Ledger/Stat table and its related application functionality
§ Ledger/Stat and its related application functionality will be de-supported in a future release. The timing of this de-support has not been determined, but Oracle intends to continue supporting Ledger/Stat and the Management Ledger table for the foreseeable future.
9. Which table does Oracle recommend that customers use?
New Customers
§ Customers beginning new implementations are advised to use the new Management Ledger table and are advised not to use the Ledger/Stat table
— Customers who elect to use Ledger/Stat should be aware that support for application functionality that utilizes the Ledger/Stat table may be withdrawn in a future release
— Customers who want to migrate to a future release for which Ledger/Stat is no longer supported will be required to migrate their Ledger/Stat processes to the Management Ledger prior to upgrading to that release
— The need to eventually move to the Management Ledger structure can be avoided by starting with the Management Ledger table
Upgrading Customers
§ Customers upgrading or considering upgrading to release 8.1 from a prior release are advised to continue using the Ledger/Stat table
— This will minimize the time and effort required for the migration to release 8 by retaining all rules and processes that currently involve the Ledger/Stat table
§ Customers upgrading to release 8.1 must be aware that support for application functionality that utilizes the Ledger/Stat table may be withdrawn in a future release
— Application rules and processes that involve the Ledger/Stat table will need to be migrated from Ledger/Stat to the Management Ledger at some point in the future.