cancel
Showing results for 
Search instead for 
Did you mean: 

"Last (n) " variables in SPM reports

0 Kudos

Hi:

We are at SPM 2.1 SP6.

we have data for 2008-9-10-11 (up to a certain point in 2011).

When I create a SPM report with Last (1) year, It shows me data for Year 2009.

When I create a report with Last (12) month, it shows me some months in 2008, some in 2009, some in 2010 and one in 2011.

So - few questions:

1. Any time variable with Last (n), do they use date of execution to calculate the starting point? Or "Last data upload date" - or any other logic?

2. How come Last (1) year goes back to 2008? Or random months in when chosen Last (12) months?

Any help is appreciated...

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Harin,

There are numerous fixes for time analysis options in SP7. More generally, there are a lot of other fixes that are pretty important. Suggest you apply SP7 and give it another go.

There's a good section in the SPM 2.1 central release note - 1424521 - that details out the limitations of SP7 time analysis.

I have pasted these below.

If you're still having problems, i suggest you open an OSS message as with these options there's not a lot that's very customisable beyond defining the time dimensions properly in the Data Source properties.

Hope that helps,

Neil

Known Limitations in Advanced Time Analysis

Year over Year dropdown selections get reset after report execution. Results of the report are accurately based on the original user date selection. As a workaround users can save the report with an appropriate description. Another workaround would be to add Time as dimension to the report and filter appropriately.

For all Period over Period analysis options (except Year over Year), when a saved report is opened the period dropdown selections get reset to default values. Results of the report are accurately based on the saved user date selection. As a workaround users can, in the first place, save the report with an appropriate description

Last (n) fiscal period display results for last (n-1)

For all period over period options the Run Report button is disabled for more than 2 consecutive years apart (e.g. 2007 to 2009). Same applies to quarter over quarter, weeks over weeks. This is intentional and has been done to limit the number of columns, added to the report, to a usable width

Dropdown values for weeks and days have a format issue (they show negative sign)

For Fiscal Year over Fiscal Year the first year dropdown is blanked out after opening a saved report

For Period over Period options, after making the year selection from the dropdown, the period dropdown becomes empty. As a workaround the user can select a year from the other dropdown which will reinitialize the first period dropdown. Selections can be made properly after that.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Harin,

SP7 Patch 1 also has these additional fixes that may be useful for you:

u2022 Year over Year dropdown selections get reset after report execution. Results of the report are accurately based on the original user date selection.

u2022 For all Period over Period analysis options (except Year over Year), when a saved report is opened the period dropdown selections get reset to default values. Results of the report are accurately based on the saved user date selection.

u2022 Last (n) year, quater, month, fiscal year and fiscal period display results for last (n-1)

u2022 For all period over period options the Run Report button is disabled for more than 2 consecutive years apart (e.g. 2007 to 2009). Same applies to quarter over quarter, weeks over weeks.

u2022 For Fiscal Year over Fiscal Year the first year dropdown is blanked out after opening a saved report

u2022 For Period over Period options, after making the year selection from the dropdown, the period dropdown becomes empty.

u2022 Scheduled reports fail to run at the scheduled time/day. They will now run and be cached in BW OLAP cache.