EPMA 11.1.2.1 (Interface Tables) Working with Shared Upper Level Members

Question

Hi Everyone,
I am building a hierarchy with interface tables in which I specify a shared member. In the interface table, I assign a null datastorage and a 0 for the ISPrimary to designate the shared member. The stored member has a datastorage of storedata and an ISPrimary of 1. The sort order for the shared member is set at 999999 and the sort order for the stored member is 6.
We have an org hierarchy that goes Division->Business Group->Department. Please reference the member that is highlighted for the two questions I have below.
I just made up some hierarchy names and placed in parenthesis what the member name would look like in our real hierarchy.
Example Hierarchy:
Organization
|--Main_Hierarchy
|--|--Division1 (DV_XYZ)
|--|--|--BusinessGroup1 (BG_ABCD)
|--|--|--|--Department1 (DP_1234)
|-Alternate Rollup
*|--|--Division2 (DV_ABC) [stored]*
|--|--|--BG_123
|--|--|--|--DP_9999
|--|--|--|--DP_9876
|--|--Research Division (DV_ZZZ)
*|--|--|--Division2(DV_ABC) [shared]*
I have 2 issues with this setup.
1) When I run an import into the shared library, I see the shared member with children underneath it (the same children that are under the stored member) Is this supposed to look like that, or is there an additional configuration that I need to make? When I look in the application library, I see it correctly with the shared members having no children, but the shared library shows the shared members with children.
2) When I run a deploy to the application, the application library shows the hierarchy correctly, but Planning and the Essbase Outline reversed the members (The stored member comes in as shared and the shared member comes in as stored in essbase and planning, but the application library shows it the correct way). Just wondering if someone could suggest a starting point for me to try and troubleshoot this issue.

Answer 1

Is this an essbase only application? It seems like the property is defaulting to stored and then flipping the initial stored member to shared because Essbase isn't interpreting the deployment correctly. I would try using ShareData as the datastorage property (I think that is the correct spelling). Also, I believe the correct way to set IsPrimary is Y/N and not 0/1.
If that did not work I would try the following in this order:
1 - I would first extract the dimension in question using the file generator and confirm that the properties are indeed correct.
2 - If they were correct. I would toggle the dimension from shared->local->shared. EPMA is still a little nutty and this will fix a fair amount of issues as it will 'refresh' the application's version of the dimension. I would then deploy
3 - deploy from EPMA->Planning only (no essbase creation), then deploy to essbase separately after ensuring the property represents itself in planning. If it is essbase only - create the outlnie instead of refresh.
4 - create a duplicate app in EPMA and deploy the copy of the app - and see if it has the same problem
Try that and see how it goes.