Today, was yet another interesting day in our cube design, this time it was when loading to an Essbase’s ASO. We have some numbers that are relevant to only some dimensions and so, I had to come up with a rules file to load these numbers to my ASO cube. In my data loading wizard header section, I included Generation 1 members of these irrelevant dimensions, and validated the rules file to be correct.
However, when I was loading data using this rules file, I consistently hit at the error ” “Aggregate storage applications ignore update to derived cells.  cells skipped”. I have been through Essbase error message descriptions for this message again and again to read that data cannot be loaded at non level-0 members and members with formula. However, I noticed that the same rules file could load data to a BSO, and was wondering why it fails for ASO. After going through my outline, design, etc, I realized one costly mistake in my rules file. The essbase error messages list clearly said, data cannot be loaded to Non Level 0 and members for formula. However, in my rules file I set the header to Generation 1 Members of my irrelevant dimensions and this was the cause.
So, to work around this constraint all I had to do, was create a level 0 member in these irrelevant dimensions (Just say a member : Unidentified ) and set this member in the rules file data loading header section.