Non standard Year member in Planning Years dimension

Question

We have a non standard (to Planning) member of the Years dimension called 'No Year'. In order to add it initially, I had to go to the back end of Planning (HSP_OBJECT and HSP_UNIQUE_NAMES tables) and modify the members there. This was in version 9. The order of the Years members was then FY95 through FY14, then came No Year, then FY15. This worked for our start and end years within Planning, as our start year was FY09 and our end year was No Year, which allowed us to Plan through FY14 and also entered non-year specific data to No Year on forms. It also allowed us to omit 'No Year' from our scripts using a range of years FY09:FY14 (using substitution variables). Now that the year has rolled over (and, incidentally, we've upgraded to version 11), and our Planning years are FY10 through FY15, I would like to move No Year to be after FY15. However, I don't seem to be able to do that by updating the underlying tables above. I make the changes to the two tables, but it is not reflected in Planning (they display in the same order), and if I try to edit either of the two members in Planning (No Year or FY15), it gives me an error saying the member already exists. Does anyone know how I can accomplish moving the No Year member? I need to do it not only this year, but to have a process my client can follow each year, moving that member in the outline to be directly after the last Planning year.
Thanks,
Sabrina

Answer 1

If you want to go about hacking the tables and changing the order of 'No Year'.
If you run the following SQL against your planning application
select * from hsp_object where object_type = 38
You will see the position column and will have values like 1000000 = First place, 1000010 = Second Place and so on.
To alter the position then you need to note down the position value of 'No Year' and 'FY15'
update hsp_object set position = '1000070'
where object_type = 38 and object_name='No Year'
update hsp_object set position = '1000080'
where object_type = 38 and object_name='FY14'
Restart planning. Now this is all done at your own risk and when you app goes boom don't blame me :)
If 'No Year' was added in the correct way when you add year's it should always stay as the last position.
Planning assigns object ids between set ranges, normal year values (FY..) are 50002 onwards
No Year is out of that range e.g 50412
When No Year is added correctly then planning will add a new to the normal range of values for year (last year value + 1) and then alters the position order
Cheers
John
http://john-goodwin.blogspot.com/