Last month, Tyler Feddersen was featured in a blog post by Cameron Lackpour, a well-known veteran in the EPM community with specialties in Hyperion Essbase, Planning, ODI, Financial Reporting, and system automation.
Tyler is featured again in the closing segment of this two-part series on Planning validations – a small snippet is below.
“If you recall from Part 1, I created two validation members: AllocValidate and Validate. AllocValidate was created in the dense Accounts dimension while the Validate member was created within a sparse dimension, to give us block suppression capabilities. For this portion of the validation process, I created an additional Accounts member, LockFlag. This new member will be used in coordination with the previously created member, AllocValidate, to create a locking “flag” that all business rules can use to decide whether the rule should continue to process or not.
Additionally, I added a “NO_XXXX” for each dimension. The flag only needs to be stored at the Entity level, so each dimension outside of Accounts, Period, Scenario, Version, Year (although, I use No Year), and the dimension containing “Validate” will need the “NO_XXXX” member.”
To continue reading please visit Cameron’s Blog For Essbase Hackers.
We want to thank Cameron again for featuring some of our expertise.
Author: Melanie Mathews, Performance Architects