I've got a measure that shows a downward trend when comparing month 04 against month 03. Strangely enough, the aggregated values are exactly the same, so I would have expected a grey dash for the trend instead.
The measure has eight records for one week in month 4 and two records for one week in month 3, like so:
When running the Measures - Compare to Previous report and choosing month 04 from the Time Dimension tree, I see:
Current % of Tgt Current Actual Current Tgt Previous % of Tgt Previous Actual Previous Tgt Variance Trend
Measure Name [111.1%] 100.00% 90.00% [111.1%] 100.00% 90.00% 0.0% down
Any idea why this is a downward trend? Even if it had shown an upward trend instead of a grey dash, I'd have bought it. 8 records at 100% is a "stronger" 100% than 2 records at 100%, right?
Please advise.
JoeyThis message has been edited. Last edited by: Moogle,
-WebFOCUS 8.2.01 on Windows
June 09, 2009, 03:52 PM
Endre
Would you mind copying your two records from Month03 and eight records from Month04?
Just make sure we aren't miss-understunding
thnx Endre
WebFocus 7.6.8 iWay Data Migrator 7.6.8 PMF 5.1
June 09, 2009, 04:45 PM
SethW
Also, would you mind letting us know what is your time aggregation level set to from the measure loader?
Could PMF be comparing week 11 to week 10, instead of month 03 to Month 04?
WF 7.65. Solaris. PMF 5.11 on Oracle 10g
June 12, 2009, 04:29 PM
Moogle
Seth: It's set to a weekly time aggregation in the measure loader, and a default time level of weekly. The report I'm running is the prior vs current multi-measure report, but I've over-ridden the time level by clicking on month 04.
Endre: I'm not sure what you want me to do. do you want me to paste the source table records into the forum?
June 14, 2009, 11:30 AM
Endre
Joey,
Yes, if you could paste the detail data for the two weeks you menstioned. If I understand this correctly, we should see 2 records for week 10 and 8 records for week 14.
thnx Endre
WebFocus 7.6.8 iWay Data Migrator 7.6.8 PMF 5.1
June 15, 2009, 09:52 AM
Moogle
Hi Endre,
Here are the records from the Measures table in the PMF datamart:
Does anyone have any suggestions about this? I'm still curious and would like to be able to tell the client something by early next week.
Cheers,
Joey
-WebFOCUS 8.2.01 on Windows
June 18, 2009, 10:29 AM
SethW
My guess: Sounds like the time aggregation level used for trend for this particular report is hard coded to be at the aggregation level set in the measure loader.
To test, change the aggregation level in the loader to monthly. Reload. Then see if the monthly trend works. If it works after this change then it sounds like there may be bug in the Measures - Compare to Previous report -- OR your customizations to the report may be overriding the time aggregation level.
In your custom fex do you have a line like:
-SET &SORTACROSS='TIME_LEVEL03_VALUE';
If so, then you will override the time sort level regardless of whether you click on the month.This message has been edited. Last edited by: SethW,
WF 7.65. Solaris. PMF 5.11 on Oracle 10g
June 18, 2009, 02:41 PM
Bob Jude Ferrante
Nicely figured out, Seth!
So what can a poor PMF dude or dudette do to make the ACROSS sort more "soft" but still specify it should be Time?
-SET &SORTACROSS = 'TIME';
I do believe this will allow the time level to be set by a passed Time Range, or the context of a Time Dimension value (e.g., if the context is a Month, it's monthly, for example.) But Eric might jump on and correct me...
thanks
Bob Jude Ferrante Director of Business and Development WebFOCUS Performance Management Bob_Ferrante@ibi.com 917-339-5105
I'll take any questions about PMF - business or technical - anytime!
June 22, 2009, 01:19 PM
Bob Jude Ferrante
One other thing. The trend calculation code is by default intolerant of any deviation, even a 0.01 deviation will show up as up or down. It was assumed customers wanted absolute mathmatical accuracy. However, you can expand the calculation's range by changing a line of code in a_prevcurr2_i1.fex:
If you change the 0.0 at the right side of this setting to a value, PMF will expand its tolerance for non-zero disagreements. For example if you changed it to
This worked very well to correct this issue I was experiencing. I don't know if this needs to be a global setting, because it has such a subtle impact. I only found the issue on one Measure on one report for one time period & time level.
By the way, I did try to load the Measure at a monthly level instead of weekly, but the problem persisted.