An error in a_getperid, regardless of where you
first get it, always indicates your current default date in PMF Settings is pointing to something your Time Dimension doesn't have. Much of PMF depends on that default. Once you get this error it might bring things to a standstill.
The remedy is changing the PMF default Time setting in the System Settings panel (Manage: Settings > System) to something that relates to your Time Dimension.
3 Examples:
1: If you auto-generate a Time Dimension hierarchy of Year/Qtr/Month, from 2002-2010, and have PMF is set to Use System Clock and it's 2011, PMF doesn't know how to set a default point in time to show KPI data. The problem is the Time Dimension is the reference point for the default point in Time. If the system default points to something the Time Dimension doesn't have loaded, it's a problem.
2: If you custom-generate a Time Dimension hierarchy - something like Year/Month/Day, or Year/Quarter/Month/Week, PMF's default was never changed to point to one period in this custom Time Dimension, again, PMF doesn't know how to set a default point in time to show KPI data.
3: If you customize Time Ranges and somehow deleted the Time Range called Current (CURR). We need to make PMF shipped Time Ranges immutable.
a_getperid refers to "a system function to get the Current period failed to get a valid period." I'd say we need to give this a friendlier error message.
For IBI support please make sure you are taking to a PMF expert. Tell you CS rep you want to talk to one; IB wants to have you talk to one.
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!