Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Hierarchy Developer's Guide for Oracle Self-Service E-Billing > Hierarchy Manager and OMF Architecture > Working with ReportingIn order to run report based on hierarchy structures, changes made to hierarchies must be synchronized over to OLAP. In addition to hierarchy tree structure, each OMF object linked into hierarchy must be synchronized as well. Each OMF object has implemented an OLAP handler to handle their specific synchronization logic for being linked into a hierarchy. Changes made to the OLTP hierarchies are categorized into different types of events. An event handler is called directly by the hierarchy API code to process the corresponding event. As a result, the same changes are then be propagated into the OLAP side of the hierarchy tables. The changes made in OLTP and OLAP are bounded into a single transaction to guarantee the data integrity between the OLTP and OLAP databases. Distributed database transaction management is used to achieve this. For each OMF object that needs to be linked into Hierarchy Manager, you must implement the |
![]() |
![]() ![]() |
Hierarchy Developer's Guide for Oracle Self-Service E-Billing | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |