Planning Analytics

Is there a reason why you do not have Year-To-Date (YTD) roll-ups (dimension consolidation or "C" elements) in your time dimension? YTD reporting is very commonly needed in financial applications, so our approach is to always have those available in the PA database itself. If I put my thinking cap on I am sure I could do it in MDX, but it would require some effort and (more importantly) be difficult to maintain in the long run. If you have many reports that need it, it would be a maintenance nightmare. Dimension consolidation calculations are also the fastest and most efficient calculations you can do in Planning Analytics, and easy to maintain (once and for all) through a TI process. 

If you don't want the line to disay you need to make the Actuals zero for future months in the YTD context. 

As Ann-Grete suggests, if you have YTD consolidations, you could write a rule that makes Actuals 0 for future month YTD consols.

If you're just doing this within a PAW report using some MDX calculated member, you would do that by modifying the calculated member to return 0 when it intersects with future months.

Really depends how you've got things set up but the important thing is: TM1/PAW will display all the nonzero values it finds within the context of your view query, so to not display things you need to make it think there is nothing to display. 

Hi Vicky

On top of the comments from AG and Tom, I see two things you have to address.

Visually: there is a setting for a line visualization that is suppose to hide zero/null data point. It used to work but lately I am having problems with this setting.

Data: it does require that your actuals YTD logic for future periods are somehow set to zero and not an accumulation of previous periods.