This content has been marked as final. Show 5 replies
try putting never shared at parent scenario . looks like implicit sharing issue . Never shared will remove the implicit sharing and two different cells will be created for first child and its parent
There is no implicit sharing here as Scenario is tagged as Label Only. Label only members do not have any storage.
Have a read about two pass at this and this will give you an idea how you should be using them. two pass is generally used with formula/dyna calced members. I am not sure why would you want to tag FieldEstTotal as two pass when you are inputting data to it.
Edited by: sunil k on Feb 4, 2013 9:50 AM
By changing Scenario from Label only to Never Share fixed the data issue. But I am still not sure whether the original issue is caused by implicit share or the two passes. BTW, I inherit the design and I do not know the reason why those members is tagged as two pass. I agree they should not be as none of them as member formulas.
issue was caused from the implicit sharing . My tagging it as never shared essbase created two different cell for parent and its child .
two pass calc is used where you want to recalculate the member again
Well i do not think it should be called implied sharing issue from the definition per se - label only member can never have its own storage and they would always display what their first child has. So the issue of implied sharing does not arise. Implied share is between two members which should get storage space in the database but ESSBASE decides to optimize and provides space only for one. I do not think same mechanism would be at work between label only and a stored member.
Will leave it upto Gurus to provide their closing thought on it !!