TM1 Forum

Thx for a comprehensive discussion of the design considerations around this issue, Paul. To be clear, we don't rule Actuals into Forecast for certain months, we rule the base input measure 'amount' into a second measure 'amount_locked' for all months. For us, this as worked fine. We've not suffered ...

One approach:
- say your basic data measure is 'amount', create a rule-based measure 'amount_locked' = amount
- then your actual columns use 'amount_locked' and the open columns use 'amount': the ruled columns are locked

Appreciate the feedback, thx.

Tatiana, did you get any action on your PMR? We are experiencing this same issue in 10.2.2.

I would guess the reason your original code did not work is that the index order (you were looping thru DIMIX) did not reflect the natural month order. You have to be careful when relying on DIMIX to give you an expected sequence.

Your code seems an elegant solution. Wouldn't a simple comment work to help those who come across this later?

I don't believe Essbase is OLE DB compliant, unless that has been added in recent releases. Why not try the Essbase forums?

forums.oracle.com/forums/forum.jspa?forumID=405
network54.com/Forum/58296/