Imaging ExpenseReceiptProcessing Faults With Error ORA-01722: invalid number
(Doc ID 1576731.1)
Last updated on SEPTEMBER 21, 2022
Applies to:Oracle WebCenter Content: Imaging - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
After a Receipt is uploaded to Imaging with the CLASSIFICATION of "Expense", the ExpenseReceiptProcessing BPEL process is started but faults with the following message: ORA-01722: invalid number:
<bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'GetEBSTransaction' failed due to: Pure SQL Exception. Pure SQL Execute of select '' as LUCID, REPORT_SUBMITTED_DATE, TOTAL,REPORT_HEADER_ID FROM AP_EXPENSE_REPORT_HEADERS_ALL WHERE REPORT_HEADER_ID = ? failed. Caused by java.sql.SQLSyntaxErrorException: ORA-01722: invalid number . The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-1722" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>ORA-01722: invalid number </detail></part><part name="code"><code>1722</code></part></bindingFault></bpelFault>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document