Journal Import Fails with "ORA-00001: unique constraint (FUSION.GL_JE_BATCHES_U2) violated" Error
(Doc ID 1930417.1)
Last updated on JANUARY 23, 2024
Applies to:
Oracle Fusion General Ledger Cloud Service - Version 11.1.8.0.0 and laterOracle Fusion General Ledger - Version 11.1.8.0.0 and later
Information in this document applies to any platform.
Symptoms
On : 11.1.8.0.0 version, Capture Transactions-Record and Edit Standard Journal Entries
When attempting to Import Journals, the following error occurs.
ERROR
-----------------------
Error in: gllcbh
Function return status: 0
Function Err Message: Executing bch_prep
Function warning number: -1
*****************************************************
sqlcaid: sqlabc: 0 sqlcode: -1 sqlerrml: 64
sqlerrmc:
ORA-00001: unique constraint (FUSION.GL_JE_BATCHES_U2) violated
sqlerrp: sqlerrd: 0 38 0 0 0 538976288
sqlwarn: sqltext:
*****************************************************
The unique constraint violation error can also happen with the index on the headers table:
ORA-00001: unique constraint (FUSION.GL_JE_HEADERS_U2) violated
STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Load journals with long name using Spreadsheet
2. Import Journals
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |