This content has been marked as final. Show 9 replies
Running scripts (business rules / calculations) can change / delete / update values in locked versions.
We understand it, But there is no Business rule execution reported in Job console or Audit trail.
Then maybe someone have used Smart view for Essbase
Have a look at essbase logs to see who accessed application.
Might be a calcscript run or lock and send directly to essbase without visiting job console or audit trial layer.
We are in 11.1.2 Planning and we too had same issue. But we were sure that its not actually bug in Hyperion. Later we found that we have few exceptional cases in Calc scripts where the logic was copying data from one intersection to another which was the source for data clear (remember data copy can overwrite your existing values). This will be very hard to find but still you have to go through this excercise to make your application stable.
Even though this might not be the exact issue of yours, but still this might click you what can be wrong in your side.... Moreover, Hyperion can never clear data by itself unless we program so. :-) Hope everyone can agree with this...
How did u know that its problem with some calc script? For investigation purpose, we have enabled audit trail for "DATA" and "BUSINESS RULES" for our application. But the codes whose data have been changed or removed is not available in audit trail.
When we run a business rule and if it change any value then it should be appear in audit trail.
you are right... Audit should track... Anyone tried this before??
Audit will capture the script launch only when they are ran from planning/smartview. There is still a chance that thay may have kicked-off from EAS/MAXL/Add-In and you don't see that in audit.
There is no chance to run Business Rule from anywhere except planning/smartview. We dig out Audit trail and finally we found the cause of data manipulation in Planning. But we are not in a position to find out 100% data manipulation occur in Planning Forms. Because as per our information, Audit trail do not store any data uploading changes. So, we are assuming that the rest of the data have been changed as a result of any data uploading through Informatica.