When the GL Interface processes ends in Error and the process log displays the following message this indicates that there are problems with the item type setup, according to Oracle (see below for details on the cause and resolution provided by Oracle for this issue).
INSERT ITEM SF HIST (DUPL KEY)
With Return Code: 00805
Error Message : ORA-00001: unique constraint (SYSADM.PS_ITEM_SF_GL_HIST) violated
Cause
Oracle indicates the cause for this issue is the GL Interface setup on an Item Type. An item type being processed by the GL Interface has different Timing values specified on the Debit and Credit Entries for a term. One of the entries uses a Timing value of Assessed, and the other uses a Timing Value of Satisfied. When the debit and credit entries on an item type for a term use the same Timing Value, one row is inserted into the PS_ITEM_SF_GL_HIST table. When different Timing Values are used within the setup for the same term, two rows will be inserted into the PS_ITEM_SF_GL_HIST, causing the ORA-00001: unique constraint (PS_ITEM_SF_GL_HIST) error.
Solution
To identify which item types have this setup issue, please run the following custom query - VXX_GL_ERROR_GL_TIMING. Listed below are the steps recommended by Oracle to resolve the issue.
From Oracle’s Knowledge Base -
Please try the following in a test environment.
1. Identify all item types having rows on the Item Type GL Interface page with different Timing values for a term;
2. Navigate to Set Up SACR, Product Related, Item Types, Item Types;
3. Enter the item type identified as having different Timing Values;
4. Click on the GL Interface Tab;
5. Locate the Term where the Timing issue exists;
6. Change the Timing value on the incorrect row to the same value as the correct row. For a term, the debit and credit entries must use the same Timing Value;
7. Save the change;
8. Navigate to Student Financials, GL Interface, Generate Accounting Entries;
9. Populate the run control page with the Student Financials Business Unit, Journal Template and Term;
10. Submit the GL Interface process to the process scheduler;
11. If the issue is resolved, please migrate the solution as appropriate to other environments.