time.pngcustomqtd.pngcustomqtd.txtHi,
We have cutsomperiodic and customQTD on YTD model.
but we need 6 months(TTD- termtodate) custom measure. Can any one help me how to create a custom measure for 6 months.
I have attached customQTD measure and TIME dimension for reference.
Regards,
Srikant
Sorry, but I am unable to see what do you mean by TTD measure. No sample, no algorithm.
And why you are providing links to the pictures instead of inserting pictures directly? Hard to read.
Hi Vadim,
Thanks or your reply.
currently we are using customqtd measure which is aggregated value for 3 months in a YTD model.
Similarly user want to see the aggregated value or 6 months (Term -to-date).please see the sample below.
the CustomQTD measure giving correct results with the below formula.
This is our time dimension.
please let me know i you require any other details.
Regards,
Srikant
Looks like your time dimension is configured incorrectly - you use P0x instead of month names and half year members has empty property - has to be WEEK.
Hi Vadim,
I have maintained week for all half year members and changed the formula week in place of quarter.
but still i am getting QTD numbers.
Could you please suggest any formula for this scenario.
Regards,
Srikanth
Hi Vadim,
I am out of office and no access to the system now. Time dimension is same as below , only change is i have maintained level property week for half year members(2017.H1,2017.H2).
Regards,
Srikanth
Hi Vadim,
I have used month names instead of POx now.
Could you please have a look and let me know if you need any other details.
Thanks for your help.
Regards,
Srikanth
Please post text (not picture) of standard QTD measure. Ensure that standard QTD measure is working properly!
P.S. Looks like PERIOD property is set incorrectly - first month of the year 2016.P01 has to be JAN! P02 - FEB etc...
Hi Vadim,
standard QTD measure is not working properly on YTD model, we are getting the below error( the execution of report default report failed).
that is why we have created customQtd measure and it is working fine as expected( we created one property BEGINPERIOD and we used this property in customqtd measure) .
please see attached for both standard and customQtd measures.
Also for period property i have set first month as Apr because in our project the financial year starts from Apr - Mar.
standard-qtd.txtcustom-qtd.txt
Regards,
Srikanth
Absolutely incorrect approach with custom measure!
The reason for the error - INP months don't have all levels!
Please show screenshot with INP months
"Also for period property i have set first month as Apr because in our project the financial year starts from Apr - Mar."
INCORRECT IDEA!!!
First month of the year has to be JAN in this property!
You can create another property like CALPERIOD and fill it with calendar month!
I have explained it here many times, please search!
On the screenshot I don't see 2016.INP member with PARENTH1
Also - correct PERIOD property!
Hi Vadim,
we have n't maintained any .INP members , me maintained 2016.INP in TIMEINP property only.
Regards,
Srikant
Are you sure??? Then what for you put 2016.INP in TIMEINP??? Strange logic!
Please also provide BW and BPC version and SP
Hi Vadim,
Yes, we haven't maintained .INP members.
Regards,
Srikant
BPC 800 SP07???? Is it a joke? Upgrade absolutely required! BW upgrade is also absolutely required.
Standard QTD measure has to work without issues (with correct PERIOD property)
P.S. And how TIMEINP property is used if you don't have INP members?
"I know our BW/BPC is too old and we already requested for up gradation. For the time being is that possible to create custom formula for 6 months using formula customqtd."
First - upgrade!
Then ensure that standard QTD is working correctly
Then - new measure TTD
Other options - just a waste of time!
Hi Vadim,
Thanks for your time and suggestions, anyway upgrade will take time .
Just a question : Do you think with our time dimension set up, is it possible to write the formula for measure TTD?
do you any idea on how to proceed atleast?
Regards,
Srikant
Sorry, but it's impossible to provide any solutions for old SP with a lot of unsolved bugs...