Topics:
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.
There is a utility available for migrating the allocations defined in the Ledger/Stat table to the FSI_D_MANAGEMENT_LEDGER table. For more details, see the MOS Doc ID 2398698.1.
The new Management Ledger supports the same functionality as historically is 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 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
In the future, functional enhancements to Profitability Management are directed towards the Management Ledger table class. New enhancements may or may not be extended to apply to the Management Ledger table.
FAQ: How do OFSAA Infrastructure and Applications interact with the Management Ledger table?
Loading Staging Data into the Management Ledger Table:
§ OFSAA Infrastructure 8.0.4.0.0 includes a T2T rule (T2T_MANAGEMENT_LEDGER) for loading the Management Ledger table from STG_GL_DATA
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 Funds Transfer Pricing:
§ Funds Transfer Pricing supports the same functionality with the Management Ledger as historically has been available with the 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 includes data movement processes for loading its results tables from either or Management Ledger
FAQ: 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.
Future Enhancements:
§ All future enhancements to OFSAA applications that utilize ledger-level data will be built to support the Management Ledger structure
FAQ: What are the technical advantages of the new table structure?
The structure of the Management Ledger table eliminates the need to:
§ Generate YTD balances for every row at the time of insertion.
§ Refresh YTD balances for every row at the time of update.
§ Store YTD balances on every row.
YTD balances can 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
FAQ: Can I have multiple Management Ledger tables?
Yes. The Management Ledger table is seeded 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 other data in your Information Domain. For more information, see the Adding Management Ledger Class Tables section in the OFS Data Model Utilities User Guide.
FAQ: Will customers need multiple Management Ledger tables?
Most customers will not need multiple Management Ledger tables. The utilization of multiple Management Ledger tables might be useful for some multi-entity or multi-tenant implementations.
FAQ: Can different Management Ledger tables have different dimensions?
Yes, different Management Ledger tables may have different dimensionality.
FAQ: Can I move data between 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.
FAQ: How long will the table be supported?
§ Release 8 and all the previous OFSAA releases will always support the table and its related application functionality.
§ All the related application functionality may not be supported in future releases, but and its related application functionality will be supported for current releases and Oracle intends to continue supporting for the near future. New application enhancements are unlikely to be extended to the table.
FAQ: 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 table.
§ Customers who elect to use should be aware that support for application functionality that utilizes the table is withdrawn in a future release.
§ Customers who want to migrate to a future release, for which it is no longer supported, are required to migrate their processes to the Management Ledger before upgrading to that release.
§ The need to 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 from a prior release are advised to continue using the 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 table.
§ Customers upgrading to release 8 should be aware that support for application functionality that utilizes the table may be withdrawn in a future release.
§ Application rules and processes that involve the table may need to be migrated from the Management Ledger table in the future.