I created an a_12_meas.fex cloned from the a_6_meas.fex and added six months in each instance where there had been six months previously:
D07_LEVEL07_VALUE_Edit = '&D07_LEVEL07_VALUE_Edit' \
D08_LEVEL08_VALUE_Edit = '&D08_LEVEL08_VALUE_Edit' \
D09_LEVEL09_VALUE_Edit = '&D09_LEVEL09_VALUE_Edit' \
D10_LEVEL10_VALUE_Edit = '&D10_LEVEL10_VALUE_Edit' \
D11_LEVEL11_VALUE_Edit = '&D11_LEVEL11_VALUE_Edit' \
D12_LEVEL12_VALUE_Edit = '&D12_LEVEL12_VALUE_Edit' \

I also added these lines to this newly-cloned fex - ibi\apps\mainstreet\a_meas_detail01x.fex
and changed the -set to
-SET &THIS_DRILL_RPT = 'A_MEAS_DETAIL01X'.

The report runs for a few seconds and then the error message:

0 ERROR AT OR NEAR LINE 181 IN PROCEDURE ??YYLE01_DATA
(FOC295) A VALUE IS MISSING FOR: &D07_LEVEL07_VALUE_Edit

appears.

I opened a case with TechSupport but wondered if there was an a_meas_12.fex that should have been included in mainstreet.

Sandy Kadish
(904) 874-4713

You're assuming you have to design this report using brute force and magic. Of course you don't.

You would change the range of time values displayed on a report in PMF *not* by editing the report itself, but rather by using Time Range object on the report. There is already a 12 month Time Range object you can use. Otherwise you'd have to create one, which would have taken about a minute.

You can pass &TIME_RANGE to a report as a parameter. PMF_BOOKLET_DATA uses this parameter during extraction. If it is an inclusive (rather than point-to-point) time range, it includes all time buckets from the start to the end of the range as discrete buckets.

You'd then print these are columns on the report to display these. That woudl be the editing you'd do on the report. Although you could design an Analysis Designer report to break data out across any Time Dimension levels. It's only if you want this report to work with the navigation tree that you would need to design it in code, since trees are not a standard component you can just drop into a report on analysis designer (not yet anyway).

My advice:

Try designing the right-hand side of your report using Analysis designer. Have a look at how it works. There is already a 12-month trending period set up, just use that. Then turn ECHO ON in the PMF Settings and have a look at the FOCUS that was generated. Use that as your guideline for what column names to use in your fixed report design.

Meanwhile, the LEVELnn values you were trying to use refer to Dimension levels. Not points in time. There are up to 16 dimension levels in PMF so that number goes up to LEVEL16, not LEVEL12. You also have to provide the Dimension name or use a concatenation with a passed Dimension name. But that is not what you want to do. The values contained in these would be a single value displaying the value of the dimension level to which you were referring. Say it's location and you have location level 1 defined as country, level 2 as region, level 3 as state, level 4 as city. Then for Boston, LOCATION_LEVEL01_VALUE = US, LOCATION_LEVEL02_VALUE = EAST, LOCATION_LEVEL03_VALUE = MASS, LOCATION_LEVEL04_VALUE = BOSTON. Got it?

Time has only three levels. Typically these are Year, Quarter, and Month for Time AutoGen, which most of our customers are using.

thanks

Bob - your advice worked like a charm. I backed out the half-dozen additional lines and changed the time measure to '12MM'. The report is out there for the client to review.