Not all lexical parameters are being bound

Question

Reports SQL parser is binding to only 2 of 4 variables. SQL TRACE option confirms this:
AND CABCHCK_CORT_CODE = :P_COURT_CODE
AND CABCHCK_LOCN_CODE = :P_COURT_LOCATION_CODE
AND CABCHCK.CABCHCK_DATE >= TO_DATE(:P_DATE_FROM)
AND CABCHCK.CABCHCK_DATE <= TO_DATE(:P_DATE_TO)
Bind Variable Value
P_COURT_CODE 23
P_COURT_LOCATION_CODE TC
Note that :P_DATE_FROM and :P_DATE_TO are not shown in the trace as a 'Bind Variable'. The error message when running the report is:
ORA-01008: not all variables bound
This is a report which has previously worked and where the SQL code and the lexical parameters have not changed (but the layout changed slightly). Could this be yet another corrupted .rdf file? If so, how is this circumvented?
Regards,
Steve

Answer 1

The issue has been found and solved.
The SQL code is loaded into a lexiconal variable and run from the query. For example,
:P_WHERE_COURT = 'and cabchck_cort_code = :p_court_code';
This was in the BEFORE_REPORT trigger. It worked.
However, the third and forth lines (with the TO_DATE function call) were not working. In the SQL statement, the functions referenced the :P_DATE fields but they weren't bound.
The date statements were loaded in the same BEFORE_REPORT trigger as the court and location lines. By moving all of the code into the AFTER_PARAMETER trigger, the errors went away and the SQL processed normally.
Why would this move from BEFORE_REPORT to AFTER_PARAMETER have done this?