XQE-PLN-0098 error while publishing package in FM

[sunny8]

Hi,

I'm facing issue in the cognos reports as "XQE-PLN-0098 - to_char function is not supported" some times. For this report I have connected to a dynamic query mode framework package. But, the same report I'm not facing this issue when it is connected to normal package without dynamic mode.

My Cognos version is 10.2, DB: Oracle 11g. Please help !!!!!

Thanks

[MFGF]

Hi,

I'm facing issue in the cognos reports as "XQE-PLN-0098 - to_char function is not supported" some times. For this report I have connected to a dynamic query mode framework package. But, the same report I'm not facing this issue when it is connected to normal package without dynamic mode.

My Cognos version is 10.2, DB: Oracle 11g. Please help !!!!!

Thanks

Is there a spacific reason for using to_char() which is an Oracle-specific function? The Cognos cast() function can be used to convert values to character data types - try using this instead, perhaps?

MF.

[sunny8]

The reason I'm using to_char is to convert current date format to mm/dd/yyyy format. Note that I'm facing this error only few times not all the time while running report. I think the issue could be with the FM package while publishing in dynamic query mode. The same report works fine for non dynamic query mode FM package.

[MFGF]

The reason I'm using to_char is to convert current date format to mm/dd/yyyy format. Note that I'm facing this error only few times not all the time while running report. I think the issue could be with the FM package while publishing in dynamic query mode. The same report works fine for non dynamic query mode FM package.

Why are you doing this? You can just go to the Data Format property of the item in Framework Manager and define the desired date format there. No casting or conversion is required.

MF.

[sunny8]

If I do that it will impact to other report as well. So, I can't do this...

[MFGF]

If I do that it will impact to other report as well. So, I can't do this...

If you do it in your package, it will be inherited by all reports using the item from the package where a format is not explicitly defined in the report. It sounds like you don't want this to happen? Is there a reason why not?

If it is just for one report, why are you doing this in your package? Why not just define the format in the one report it is relevant to?

MF.