R12: AP/IBY: Error ORA-1 Violated Constraint IBY.IBY_ACCOUNT_OWNERS_U2 When Running Supplier Merge
(Doc ID 3061605.1)
Last updated on DECEMBER 06, 2024
Applies to:
Oracle Payables - Version 12.2.10 and laterInformation in this document applies to any platform.
Symptoms
Attempting to merge suppliers raises error ORA-1
Supplier Merge program raises the following error:
Error
ORA-00001: unique constraint (IBY.IBY_ACCOUNT_OWNERS_U2) violated
iby.plsql.IBY_SUPP_BANK_MERGE_PUB.BANK_ACCOUNTS_MERGE(MERGE_BANKS)
ORA-00001: unique constraint (IBY.IBY_ACCOUNT_OWNERS_U2) violated
iby.plsql.IBY_SUPP_BANK_MERGE_PUB.BANK_ACCOUNTS_MERGE(MERGE_BANKS)
The Supplier Merge Log file shows the following:
LOG_SEQ. MODULE MESSAGE ---------- --------------------------- ------------------------------------------------------------------------------------------------------------------------ ... ... 1318303795 fnd.plsql.fnd_file.PUT_LINE sid:77528847: Calling IBY API - Start 1318303796 fnd.plsql.fnd_file.PUT_LINE sid:77528847: In IBY merge call, p_last_site_flag:N 1318303797 fnd.plsql.fnd_file.PUT_LINE sid:77528847: Entering IBY_SUPP_BANK_MERGE.BANK_ACCOUNTS_MERGE iby.plsql.IBY_SUPP_BANK_MERGE_PUB.BANK_ACCOUNTS_MERGE 1318303798 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_VENDOR_ID : 2315981 1318303799 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_VENDOR_ID => 2315981 1318303800 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_TO_VENDOR_ID => 2315981 1318303801 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_PARTY_ID => 4172976 1318303802 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_TO_PARTY_ID => 4172976 1318303803 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_VENDOR_SITE_ID => 1620174 1318303804 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_TO_VENDOR_SITE_ID => 1546141 1318303805 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_PARTY_SITE_ID => 3107513 1318303806 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_TO_PARTYSITE_ID => 3028393 1318303807 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_ORG_ID => 893 1318303808 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_TO_ORG_ID => 893 1318303809 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_FROM_ORG_TYPE => OPERATING_UNIT 1318303810 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_TO_ORG_TYPE => OPERATING_UNIT 1318303811 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_KEEP_SITE_FLAG => N 1318303812 fnd.plsql.fnd_file.PUT_LINE sid:77528847: P_LAST_SITE_FLAG => N 1318303813 fnd.plsql.fnd_file.PUT_LINE sid:77528847: Start Merging Bank Accounts at Suppier Site Level 1318303814 fnd.plsql.fnd_file.PUT_LINE sid:77528847: l_to_party_site_id: 3028393 1318303815 fnd.plsql.fnd_file.PUT_LINE sid:77528847: Payee ID => 132866 1318303816 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: Start MERGE_BANKS " 1318303817 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: Start Processing Bank Account Id => 36149" 1318303818 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: Check whether the bank account is already existing for to-supplier " 1318303819 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: End of To Bank account id list Loop" 1318303820 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: Bank Account Does not exist for Supplier2 " 1318303821 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: Inserting record into Instruments l_max_order_of_pref => 2" 1318303822 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: Processing Bank Account Ownership" 1318303823 fnd.plsql.fnd_file.PUT_LINE "sid:77528847: To Supplier Ownership Does not Exist " 1318303825 fnd.plsql.fnd_file.PUT_LINE sid:77528847: Unexpected error: ORA-00001: unique constraint (IBY.IBY_ACCOUNT_OWNERS_U2) violatediby.plsql.IBY_SUPP_BANK_MERGE_PUB.BANK_ACCOUNTS_MERGE(MERGE_BANKS) 1318303826 fnd.plsql.fnd_file.PUT_LINE sid:77528847: End Merging Bank Accounts at Suppier Site Level 1318303830 fnd.plsql.fnd_file.PUT_LINE sid:77528847: Start Merging Bank Accounts at Suppier Address Level ...
Notice the lines highlighted. They show the Record being inserted causing the issue: EXT_BANK_ACCOUNT_ID 36149 + ACCOUNT_OWNER_PARTY_ID 4172976.
The only piece missing to violate the index IBY_ACCOUNT_OWNERS_U2 (See below), is the PRIMARY_FLAG value that can be Yes (Y) or No (N).
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 |