If you are deploying an attribute dimension assigned to a ragged sparse base dimension (ragged, meaning the lowest level is not equivalent to the highest generation) within Essbase version 126.96.36.199, you may have trouble deploying from EPMA into Essbase. There is no associated error message and the deploy itself completes successfully. A close examination of the outline in Essbase will reveal that the attributes in Essbase do not match the attributes in EPMA. Attributes exist for some level 0 members in the base dimension, but not others.
This occurs due to an issue related to EPMA and Essbase Studio 188.8.131.52. EPMA deploys Essbase applications through Essbase Studio. In 184.108.40.206, the logic to deploy Essbase attribute associations is based on generation and not Level. Thus, if some level 0 members are (for example) generation 6 while others are generation 5, those that are generation 6 will receive attributes but not those from generation 5.
To be more specific, this behavior occurs when the following criteria are met:
- Installed version of EPMA is 220.127.116.11
- Not an issue with Classic Essbase applications
- Installed version of Essbase Studio is 18.104.22.168
- Deploying into Essbase 22.214.171.124
- Essbase only application
- Affects ASO as well as BSO applications
- Not an issue with Planning applications deploying to Essbase
- Attributes are associated with a ragged base dimension
- Not an issue if the base level of the hierarchy is consistent with the lowest generation (i.e. Level 0 is the same effectively as generation 6 with no exceptions)
This functionality actually worked in previous versions of Essbase, but became an issue in 126.96.36.199. This is not an issue in 188.8.131.52 and forward. This issue can be fixed by patching the environment to the 184.108.40.206.600 release or later. It is highly recommended to consult the Oracle EPM Compatibility Matrix and patch all installed products to ensure version compatibility.
After installing the patches appropriate for your environment (based on installed products), restarting the environment, and re-deploying from EPMA, attributes will now populate correctly into Essbase.
Questions? Comments? Feel free to email us directly!
Nick Suiter, email@example.com
David Grande, firstname.lastname@example.org
Jon Harvey, email@example.com