Duplicate JLR throws ORA-00001: Unique Constraint (FUSION.XLA_CONDITIONS_U2) Violated (Doc ID 1986297.1)

Last updated on MARCH 04, 2015

Applies to:

Oracle Fusion Subledger Accounting - Version 11.1.8.0.0 and later
Oracle Fusion Subledger Accounting Cloud Service - Version 11.1.4.0.0 and later
Information in this document applies to any platform.

Symptoms

Fusion Subledger Accounting.

Creating a new Journal Line Rule by duplicating an existing one throws the error;
ORA-00001: Unique Constraint (FUSION.XLA_CONDITIONS_U2) Violated

Also, the accounting attributes in the tab 'Accounting Attribute Assignments' are not populated with the expected values.

 

The issue can be reproduced by the following steps

==================================

In FSM.  
Task List  Define Subledger Accounting for Invoicing and Payments
  > Task List Define Subledger Accounting Rules
   > Task List Define Subledger Accounting Methods
    > Go to Task   Manage Journal Line Rules

1. Query and open a seeded Journal Line Rule (JLR)

2. Actions > Duplicate.   In newly created JLR see Accounting Attributes Tab populated with data
 Save and Close

3. In Manage Journal Line Rules: Payables  UI
 Query back the newly created JLR
 From the overview page click the red cross to delete

4. In Manage Journal Line Rules: Payables  UI
 Query back open the original JLR  

5. Actions > Duplicate.    On save and close the error will appear;
 Error
 ORA-00001: Unique Constraint (FUSION.XLA_CONDITIONS_U2) Violated
 
 Also, the accounting attributes in the tab Accounting Attributes
 Assignments are not populated with the expected values.

Cause

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