My Oracle Support Banner

R12: AP: Trying To Query Invoices For One Supplier Via The Invoice Inquiry Screen Generates Errors FRM-40735 And ORA-1403 (Doc ID 2395734.1)

Last updated on APRIL 28, 2023

Applies to:

Oracle Payables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Invoice Issues & MassAdd

AP - Cannot open Invoice for One Supplier

Trying to Open Invoice Inquiry screen for One Supplier to look the invoices and getting this error.
FRM-40735 post-query trigger raised unhandled exception ORA-01403

ERROR
-----------------------
FRM-40735 post-query trigger raised unhandled exception ORA-01403



FND Debug Log of the issue reproduced shows Error ORA-1422 in program unit IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute

...

per.resource.HRKPI.hr_kpi_extlib.event #event_name#WHEN-NEW-ITEM-INSTANCE*formname*APXINWKB
per.resource.HRKPI.hr_kpi_extlib.event end
AP.PLSQL.AP_ACCOUNTING_EVENT_PKG.update_invoice_events_status Begin of procedure update_invoice_events_status
...
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable AP_ETAX_UTILITY_PKG.Is_Incl_Tax_Driver_Updatable<-APXINWKB.Inv_Sum_Folder_Item_Tax.Taxation_Country_Name.POST-QUERY
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable Step 0: Invoice Id and Invoice Line Number
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable Step 1: Check if Posted or Encumbered Distributions exist : 0
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable AP_ETAX_UTILITY_PKG.Is_Incl_Tax_Driver_Updatable<-APXINWKB.Inv_Sum_Folder_Item_Tax.Trx_Business_Category_Name.POST-QUERY
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable Step 0: Invoice Id and Invoice Line Number
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable Step 1: Check if Posted or Encumbered Distributions exist : 0
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable AP_ETAX_UTILITY_PKG.Is_Incl_Tax_Driver_Updatable<-APXINWKB.Inv_Sum_Folder_Item_Tax.Document_Sub_Type_Name.POST-QUERY
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable Step 0: Invoice Id and Invoice Line Number
AP.PLSQL.AP_ETAX_UTILITY_PKG.Is_Inclusive_Tax_Driver_Updatable Step 1: Check if Posted or Encumbered Distributions exist : 0
...
...
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Applicable_Payment_Method : Match Found
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Applicable_Payment_Method : Applicable Payment Methods Count : 5
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Applicable_Payment_Method : RETURN
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : ENTER
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Application_id   : 200
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : 1st party LE id  :
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Org Id           : 2
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Org Type         : OPERATING_UNIT
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Payer Id         :
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Payee Site Id    :
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Supplier Site Id :
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Trxn Type Code   : PAYABLES_DOC
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Payment Currency : USD
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Payment Amount   :
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : Payment Function : PAYABLES_DISB
iby.plsql.IBY_VALIDATIONSETS_PUB IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromConte : ENTER
iby.plsql.IBY_VALIDATIONSETS_PUB IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromConte : Given payee context: payee party id , party site id , supplier site id , or
iby.plsql.IBY_VALIDATIONSETS_PUB IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromConte : Fatal: Exception when attempting to perform exact match for given payee context.
iby.plsql.IBY_VALIDATIONSETS_PUB IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromConte : SQL code: -1422
iby.plsql.IBY_VALIDATIONSETS_PUB IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromConte : SQL err msg: ORA-01422: exact fetch returns more than requested number of rows
iby.plsql.IBY_VALIDATIONSETS_PUB IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromConte : EXIT
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : ERROR: Exception occured during call to API
iby.plsql.IBY_DISBURSEMENT_COMP_PUB IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : SQLerr is :ORA-01422: exact fetch returns more than requested number of rows
...


The following query returns duplicate records for the payee party id, party site id, supplier site id, Org(Id & type), and payment function


Changes

Upgrade to R12.1.3

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.