Planning dimensions are modified every time during the development phase, and when multiple developers are working on the same Planning cube, nobody knows who is adding or deleting what. So one fine day you open up the Financial Report you had created just to find out that it doesnt work because some member that existed before is not available now.
That was one of the many things you can do with ODI and Planning tables. I will be posting more such things as I get time.
You can use HSP_AUDIT_RECORDS table of your planning application to find out who-did-it !
Setting Audit trails in Hyperion Planning is an age old method of doing this. Read on here http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin_11122/frameset.htm?launch.html
(search HSP_AUDIT_RECORDS)
However, whats difficult is presenting this information to users who are not given details of underlying database schema. So ODI can be used beyond this point, where you can print the records to a flat file, journalize the table for tracking additions and firing mails containing this information the moment someone modifies the Planning app.
Setting Audit trails in Hyperion Planning is an age old method of doing this. Read on here http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin_11122/frameset.htm?launch.html
(search HSP_AUDIT_RECORDS)
However, whats difficult is presenting this information to users who are not given details of underlying database schema. So ODI can be used beyond this point, where you can print the records to a flat file, journalize the table for tracking additions and firing mails containing this information the moment someone modifies the Planning app.
That was one of the many things you can do with ODI and Planning tables. I will be posting more such things as I get time.
No comments:
Post a Comment