Parameter is not working properly in BCM . Why?

Parameter is not working properly in BCM . Why?

The parameter names should be defined with the following conventions daydiff, weekdiff monthdiff: datediff, wdiff, monthdiff.

    • Related Articles

    • Parameter not working fine.

      In "admin_db2_warehouse.xml", for the queryid "WWCAL14", we need to change the database name as highlighted below: SELECT (SELECT MONTH_IN_YEAR FROM DIM_DATE WHERE DATE_FLD = ?) - (SELECT MONTH_IN_YEAR FROM DIM_DATE WHERE DATE_FLD = ? ) AS MONTH_DIFF ...

    • Weekdiff parameter not working. Why?

      The ' weekdiff' parameter must be defined as 'wdifT' in the measure wherever you are using this parameter.

    • BCM report is not working. Why?

      One of the reasons could be jrxml files wouldn't have been compiled properly. Ensure that jrxml files are compiled in the Report Designer. ARC uses the version, jasperreports-3.1.4.jar in Report Designer."

    • Why is BCM report not working?

      One of the reasons could be: BCM reports may not work if the jrxml file is not compiled properly in the Report Designer. Also ensure that you use the jasperreports-3.1.4.jar file in the Report designer because this version is used in ARC.

    • The BCM reports, though defined correctly, are not working. Why?

      The parametres 'Start Date Key' and 'End Date Key' are mandatory for BCM reports. Ensure that they are defined properly.