 |
|||||
|
As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Join the TIBCO Community
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community. | |||||
Focal Point 
Focal Point Forums Performance Management Framework (PMF) Measure Loader - Requirements for Custom Coding Field Maps
Focal Point Forums Performance Management Framework (PMF) Measure Loader - Requirements for Custom Coding Field Maps Read-Only TopicGo | Search | Notify | Tools |
| Measure Loader - Requirements for Custom Coding Field Maps | Login/Join |
| Member |
We're creating a percent measure for which I need to specify Custom coding instead of Field Mapping for Source Type on the Field Maps tab. We're using Measures Dt determines Time Dim and we have a fixed target for this measure. When I choosed Custome coding, a dropdown list for Define Procedures appears and ACTUAL_NUMERATOR, ACTUAL DENOMINATOR and MEASURE_DATE disappear. My questions is this: what are the requirements for the Define Procedure? Do I need to code a MEASURE_DATE? Do I need to code ACTUAL_NUMERATOR and ACTUAL_DENOMINATOR, or just the final % being calced? If final %, does it need a particular name, i.e. ACTUAL_PERCENT? WF 765 WINTEL Tomcat PMF 42 SAP SQLServer | ||
|
| Member |
PMF 4.2 WF 765 WINTEL Tomcat PMF 42 SAP SQLServer | |||
|
| Member |
And i didn't really 'choosed Custome...' :-) WF 765 WINTEL Tomcat PMF 42 SAP SQLServer | |||
|
| Master |
I'm not sure why you're thinking you need Custom Coding instead of Field Mapping. Nobody has really used this capability since PMF V1.0. The DEFINE procedure must define components which depend on the aggregation method. For additive aggregation in 4.2.x, you need to define: ACTUAL/D20.2 = [code]; TARGET/D20.2 = [code]; MEASURE_DATE/HYYMDS = [real date]; For percent and range aggregation in 4.2.x, you need to define: ACTUAL_NUMERATOR/D20.2 = [code]; ACTUAL_DENOMINATOR/D20.2 = [code]; TARGET_NUMERATOR/D20.2 = [code]; TARGET_DENOMINATOR/D20.2 = [code]; MEASURE_DATE/HYYMDS = [real date]; Hope this helps! 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! | |||
|
| Member |
My original calc for Errors per 1000 Orders Rating (ie a rating of 100 == Perfect) was this: 1 - ( errors / ( orders / 1000 ) ) I was able to reduce the calc to this: ( order - errors ) / ( orders / 100 ) to give me the same mathematical result. So, in the end, i was able to fit it in the numerator / denominator construct, and not need the Define module. Thx for your reply! WF 765 WINTEL Tomcat PMF 42 SAP SQLServer | |||
|
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only TopicFocal Point Focal Point Forums Performance Management Framework (PMF) Measure Loader - Requirements for Custom Coding Field Maps
Focal Point Forums Performance Management Framework (PMF) Measure Loader - Requirements for Custom Coding Field MapsCopyright © 1996-2020 Information Builders
| View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |