How to fix FND_NUMBER.NUMBER_TO_CANONICAL(CTRN_UID) Error in FNDRSRUN (Doc ID 1929215.1)

Last updated on DECEMBER 20, 2016

Applies to:

Oracle Concurrent Processing - Version 12.1.3 to 12.2.4 [Release 12.1 to 12.2]
Information in this document applies to any platform.
trace file shows
SELECT FND_NUMBER.NUMBER_TO_CANONICAL(CTRN_UID),CTRN_UID VALUE,
TO_CHAR(CTRN_UID) DESCRIPTION, NVL('N', 'N'), NVL(TO_NUMBER(NULL), -1),
'NULL', NVL('Y', 'Y'), NVL(TO_CHAR(TO_DATE(NULL), 'J'), 0),
NVL(TO_CHAR(TO_DATE(NULL), 'J'), 0)
FROM
EB_CALC_TRANSACTIONS ECT WHERE ( ECT.CT_BAT_UID BETWEEN NVL(:b1,0) AND
NVL(:b2,99999999999999)) AND FND_NUMBER.NUMBER_TO_CANONICAL(CTRN_UID) = :X

Goal

 How to overcome some custom value set and its error that cause performance in the FNDRSRUN table .

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms