|gerdpee on Dimension does not contain any…|
|jasmine on Dimension does not contain any…|
|gerdpee on Oracle WebLogic and Hyperion S…|
|OBIEEfan on Oracle WebLogic and Hyperion S…|
Stuff about Hyperion and stuff
EPMA never ceases to amaze me.
The other day, I was getting this error when trying to deploy a Planning app
Detail : An Exception occurred during Application deployment.: Unable to load the following resource: %RESOURCE_NAME%com.hyperion.planning.olap.HspVerifyOutlineException: Verify Outline failed with the following errors:
Error  detected in member formula for member “ABCDEFG”.
After a few hours of troubleshooting, I noticed that this member “ABCDEFG” is enabled on both Plan1 and Workforce plan types but has HSP_NOLINK attached to it. Since Plan1 and Workforce have different dimensionality, the member formula returned with an error on the other plan type. The weird thing is deployment was working earlier that day.
After tracing back my steps, I remember that I reordered some alternate hierarchies in which the shared members were found before the primaries. This didn’t cause any error, only warning messages when deploying. So I tried changing the order back and redeployed. Guess what? It worked. Apparently, this warning stopped EPMA / Planning from erroring out on the member formula.
Apparently in EPMA two wrongs make is right.