This content has been marked as final. Show 6 replies
Just a hunch here but I'm guessing that you have more than 3 dimensions in the outline. You need to specify a member for all of the dimensions in the fix. For example, if there is a 4th dimension named scenario, your logic will automatically process all of the scenario members meaning that "c" will get incremented more times then you are expecting.
You need a better understanding of the essbase order of execution and how it relates to the FIX. The admin guide doc will help you with this. Once you understand how essbase cycles through the dimensions you will see that "loop" is not commonly used.
one question regarding your answer.,
I have these dimesions : company , costcenter , person , period.
company has comp1 , comp2 members
costcenter has cc1 , cc2 members
person has p1 , p2 members
period as usual.
I have only two data blocks which are ; comp1->cc1->p1->begbalance and comp1->cc1->p2->begbalance
I dont have any data for comp2 or cc2.
And my whole script as below.When I check the app.log I see the script created data for comp2 and cc2 aswell.
But in the script I didnt even used "SET CREATENONMISSINGBLK ON".is this typical for essbase.
I even tried "SET CREATENONMISSINGBLK OFF" nothing changed.
So how can I manage my script to work for only existing data.
FIX(@RELATIVE ("company",0),@RELATIVE ("costcenter",0),@RELATIVE ("person",0))
SET MSG DETAIL;