Skip to main content
Question

Apps 10 Quick Report Issues

  • January 23, 2026
  • 0 replies
  • 9 views

We recently updated our IFS Apps 10 which has resulted in multiple quick report related issues. We were a bit behind on updates, so I can’t specifically say any single patch was the cause, but here are a couple issues I’m now seeing:

 Parameters get re-populated with their previous values when you re-run a report. After generating a quick report, opening up the same report pre-populates the previously used parameters in the dialog box. It is especially annoying when using a date parameter, since IFS will convert date parameters to a SQL TO_DATE(...) expression. 

This is after searching with the date 1/21/2026 once, then trying to view the report again

 

Bind variables break SQL function calls. It seems like the way IFS is modifying the SQL to add bind variables for parameters breaks SQL function calls. I set up a very basic quick report example to demonstrate this:

SELECT * 
FROM CUSTOMER_ORDER
WHERE TRUNC(wanted_delivery_date) = TRUNC(&CUSTOMER_ORDER.WANTED_DELIVERY_DATE)

Attempting to generate this report will error. Opening the debugger and looking at the SQL that is actually generated and sent to Quick_Report_API.Get_Datatypes__ shows this:

SELECT * FROM CUSTOMER_ORDER WHERE TRUNC(wanted_delivery_date) = TRUNCTO_DATE(:paramArray,'YYYY-MM-DD-HH24.MI.SS')

So it’s replaced my parameter with a bind variable but also a TO_DATE function and more importantly, it removed the parentheses from my TRUNC() function call. 
Rewriting my query to put extra spaces before and after the parameter does result in a working query. This quick report code:

SELECT * 
FROM CUSTOMER_ORDER
WHERE TRUNC(wanted_delivery_date) = TRUNC( &CUSTOMER_ORDER.WANTED_DELIVERY_DATE )

Gets through the Get_Datatypes__ call and eventually runs the SQL:

SELECT * 
FROM CUSTOMER_ORDER
WHERE TRUNC(wanted_delivery_date) = TRUNC(TO_DATE(:p0 ,'YYYY-MM-DD-HH24.MI.SS'))

Which works but isn’t ideal having to add a bunch of extra spaces into the SQL. 

I’m mostly looking for a way to stop the saved parameters issue, but any insight on the second issue would be appreciated as well.

Thanks.