Don't know if anyone might have any ideas on this one. We're moving our Customer Service Metrics in PMF to Production from QA and everything appears to be the same in both systems. However, on one dimension, our Customer Service dimension, we are showing a different set of parameters being passed when calling the same operational report. Below, see the values passed in the filter in QA - which are correct and then at the bottom, an attempt to pass the same values in Production - incorrect (a series of numbers and then a partial key). Any thoughts on what might be causing this? I've recreated the synonym and reloaded the dimension with no effect.


In QA
### Applying CSR FILTER ...
************************* Starting cus_fltr_orditms_on_csr.fex
### Adding FILTER for ALEXANDERTJ ...
### Adding FILTER for ANGELKA ...
### Adding FILTER for DILLINGHAMM ...
### Adding FILTER for FERGUSONTA ...
### Adding FILTER for HELKEYDJ ...
### Adding FILTER for JENSENTJ ...
### Adding FILTER for JOHNSONDR ...
### Adding FILTER for JOHNSONMI ...
### Adding FILTER for JOSEPHRD ...
### Adding FILTER for KELLYBR ...
### Adding FILTER for LEHMANVL ...
### Adding FILTER for LESKOVACM ...
### Adding FILTER for LEWISDL ...
### Adding FILTER for LONGACREC ...
### Adding FILTER for MANCINIBR ...
### Adding FILTER for MARTINSJ ...
### Adding FILTER for MYERSKA ...
### Adding FILTER for PEREZM ...
### Adding FILTER for PUGHCA ...
### Adding FILTER for ROBAKNJ ...
### Adding FILTER for ROCKWELLCM ...
### Applied FILTER ON YWF_ZZJRNORDERITEMS FOR 21 CSRs ...


In Production:

### Applying CSR FILTER ...
************************* Starting cus_fltr_orditms_on_csr.fex
### Adding FILTER for 000011ALEXAN ...
### Adding FILTER for 000007ANGELK ...
### Adding FILTER for 000011DILLIN ...
### Adding FILTER for 000010FERGUS ...
### Adding FILTER for 000008HELKEY ...
### Adding FILTER for 000008JENSEN ...
### Adding FILTER for 000009JOHNSO ...
### Adding FILTER for 000009JOHNSO ...
### Adding FILTER for 000008JOSEPH ...
### Adding FILTER for 000007KELLYB ...
### Adding FILTER for 000008LEHMAN ...
### Adding FILTER for 000009LESKOV ...
### Adding FILTER for 000007LEWISD ...
### Adding FILTER for 000009LONGAC ...
### Adding FILTER for 000009MANCIN ...
### Adding FILTER for 000008MARTIN ...
### Adding FILTER for 000007MYERSK ...
### Adding FILTER for 000006PEREZM ...
### Adding FILTER for 000006PUGHCA ...
### Adding FILTER for 000007ROBAKN ...
### Adding FILTER for 000010ROCKWE ...
### Applied FILTER ON YWF_ZZJRNORDERITEMS FOR 21 CSRs ...

Mike

This looks suspiciously like you are using an AnV field in production but an An in QA. The numbers (I6) at the start look like the length of the field value that you get with AnV type fields.

You are right. The numbers to the left are the length of the string I'm trying to pull out. Given that I'm using the same program code, the same .MAS and .ACX and the same PMF configuration in QA and Prod, I'm at a loss to understand where the difference can be. How do I distinguish between An and AnV and where do I find this setting? Thanks.

We're assuming your source data is what's in question; PMF deals with the ANV fields internally in its mart structure and master files.

If the ACTUAL format for the fields on these source database tables is specified in the WebFOCUS Master File for this as AnnnnV (where nnnn is the field length) then WebFOCUS will automatically deal with taking the length off the strings and using it as the length descriptor. You can then specify a USAGE of Annnn (where nnnn is the field length) and get the results you expect in your measure loads.

thanks

Thanks. You answered my question. We did have the data type set incorrectly on one field in our synonym. That has been updated in production and the problem is resolved. Thanks Bob and Alan for your help on this.