on 06-24-2015 4:24 PM
Issue in Calculating YTD Values to PERIODIC In YTD Model
My model name is a REPORTING which is a YTD model & inputted data in YTD as Below
When I run the report (shown below) with measures as PERIODIC system is displaying months 1/4/7 system is taking YTD values and showing them as periodic values.
As per standard behaviour by default the YTD data must be shown in PERIODIC as
PERIODIC Value = {Present Month YTD Value} – {Previous Month YTD Value}
But in my report I got below values in periodic
So if see above for every quarter first month PERIODIC value is posting same as YTD value
But it is not repeating for the rest of the months in every quarter so please rectify the issue & locate where the issue…is.
MEMBER [MEASURES].[YTD] AS 'IIF(([%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%TIME%].[%TIMEBASELEVEL%])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%TIME%].[%TIMEBASELEVEL%])))' SOLVE_ORDER=3
MEMBER [MEASURES].[PERIODIC] AS 'IIF(([%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR [%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1" OR [%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN"), [MEASURES].[YTD]-([MEASURES].[YTD],[%TIME%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
And also let me know how the “LAG()” searches & on what bases it will identify the previous month
Hi Aravind,
Please upgrade to the LATEST SP your core BPC and BW!
Vadim
P.S. About LAG and other MDX functions you can read on the Microsoft site: Lag (MDX)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim,
Thank you for your suggestion .
Our system is already up to date & it is BPC 10.1 & BW 7.40....Patches up to date.
But issue is LAG() is not referring the correct month it is repeating the same month so if you could help me in referring the previous month in the measures code instead of LAG() it will be a great favor to me..
Hi Aravind,
You measure formula is absolutely correct! Just for reference - same formula from IFS kit for YTD model:
MEMBER [MEASURES].[YTD] AS 'IIF(([%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%TIME%].[%TIMEBASELEVEL%])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%TIME%].[%TIMEBASELEVEL%])))' SOLVE_ORDER=3
MEMBER [MEASURES].[PERIODIC] AS 'IIF(([%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%ACCOUNT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR [%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1" OR [%TIME%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN"), [MEASURES].[YTD]-([MEASURES].[YTD],[%TIME%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
Please provide SP levels for BPC and BW!
Also, please provide screenshot of administration screen of TIME dimension!
Vadim
I agree with you vadim this issue doesn't occur for the default "TIME" dimension that is in the environment shell.
But the issue raises when we modified the TIME dimension master data.
1) The main issue is in the "Measures" Formula at the end the LAG() function is not referring the correct "NODEID" of the "TIME" master data .
So i need a solution to overcome this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.