on 10-30-2014 6:50 PM
Hi,
I need rolling periods for planning, which requires me to use 0FISCPER instead of 0FISCPER3 in my planning queries
Within the planning query the user selects a period range, e.g. 010..2015 to 009.2016.
The challenge I have is that I see 000.2015 as well as 013.2015 in the query output in spite of the fact that I only have 12 period defined.
How do I get rid of 000 and 013 period within the query. ( I do not want to use characteristic relationships due to performance reasons, and neither can I run the query on posted values ).
This issue creates another problem.. I am using current member variable and have an off on it of -12. The challenge I have is that this offset considers 000 as well as 013 period.
Any suggestions ?
Dheeraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gregor,
I got an exit variable implemented to find out the periods and then excluded them. This worked.
From my investigation I found out that the Query does not consider the table T009C to read the fiscal periods, which only has 12 periods. The additional periods I saw were dependent upon the no. of special periods that were defined as part of the fiscal period definition.
Luckily the current member functionality does not consider the special periods and thus is not plagued by the problem of periods 013 000 etc
Regards,
Dheeraj
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.