Last updated on MARCH 08, 2017
Applies to:Oracle Fusion Payables Cloud Service - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The problem is with the next document sequence number which is being assigned. Either the document sequencing max number is reached causing the code to pick the next one which is already existing in the data base. Please see below error from log.
Caused by: javax.faces.el.EvaluationException:
oracle.jbo.DMLConstraintException: JBO-26048: Constraint "AP_INVOICES_ALL_U2"
is violated during post operation "Insert" using SQL statement "INSERT INTO
Caused by: oracle.jbo.DMLConstraintException: JBO-26048: Constraint
"AP_INVOICES_ALL_U2" is violated during post operation "Insert" using SQL
statement "INSERT INTO AP_INVOICES_ALL
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001:
unique constraint (FUSION.AP_INVOICES_ALL_U2) violated
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