A record selection problem with a string field when UNICODE database

Question

We used report files made by Crystal Reports 9 which access string fields
(char / varchar2 type) of NON-UNICODE database tables.
Now, our new product needs to deal with UNICODE database, therefore,
we created another database schema changing table definition as below.
(The table name and column name are not changed.)
    char type -> nchar type
    varchar2 type -> nvarchar2 type
When we tried to access the above table, and output a report,
the SQL statement created from the report seemed to be wrong.
We confirmed the SQL statement using Oracle trace function.
    SELECT (abbr.) WHERE "XXXVIEW"."YYY"='123'.
We think the above '123' should be N'123' because UNICODE string
is stored in nchar / nvarchar2 type field.
Question:
How can we obtain the correct SQL statement in this case?
Is there any option setting?
FYI:
The environment are as follows.
    Oracle version: 11.2.0
    ODBC version: 11.2.0.1
    National character set: AL16UTF16

Answer 1

With further investigating, we found patterns that worked well.
Worked well patters:
    Oracle version: 11.2.0
    ODBC version: 11.2.0.1
    National character set: AL16UTF16
    Report file made by Crystal Reports 2011
    Crystal Reports XI
Not worked patters:
    Oracle version: 11.2.0 (same above)
    ODBC version: 11.2.0.1 (same above)
    National character set: AL16UTF16 (same above)
    Report file made by Crystal Reports 2011 (same above)
    Crystal Reports 2008 / 2011
We think this phenomenon is degraded behavior of Crystal Reports 2008 / 2011.
But we have to use the not worked patters.
Anything wrong with us? Pls help.
-Nobuhiko