ORA-06502

R11i/R12: Payments Workbench Error: ORA-06502 PL/SQL: numeric or value error (APXPAWKB.FMB) [ID 1303443.1]

Applies to:

Oracle Financials for the Americas - Version: 11.5.10.0 and later   [Release: 11.5 and later ]
Oracle Payables - Version: 11.5.10.0 to 12.1.3   [Release: 11.5 to 12.1]
Information in this document applies to any platform.
Form:APXPAWKB.FMB - Payment Workbench

Purpose

Troubleshooting Payment Workbench Errors: Comprehensive Listing of Errors and Solutions >Note 1303443.1

The purpose of this note is to explain steps in diagnosing and troubleshooting the ORA-06502database error in the EBS Payables module, payment workbench.  This note attempts to step the reader through all known setup issues as well as known bugs that can cause this error to occur. 


Note:  If you are on older code versions (10.7, 11.0, 11.5.0 - 11.5.9, 12.0.0 - 12.0.5), your solution may not be included in this article.  Please expand your search to include the archived solutions using the selection method shown below


Last Review Date

April 11, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details


     1) Payment Entry

#ReleasePresentation / Error Stack Root CauseFixed File (or fix)Recommended Patch
112.0When trying to pay in full with a quick payment an invoice whose invoice
number has 46 characters or more the following error happens:


APP-SQLAP-10000: ORA-06502:
PL/SQL: numeric or value error occurred in
ap_calculate_interest<-AP_PAY_IN_FULL_PKG.CREATE_SINGLE_PAYMENT
<-AP_PAY_IN_FULL_PKG.AP_CREATE_PAYMENTS
<-APXPAWKB with parameters
(Invoice_id = ...Payment_num =1, ...Currency_code = CHF)
 while performing the following operation:
Get the interest Invoice Num

Bug 7612309 APXPAWKB: ORA-06502 IN AP_CALCULATE_INTEREST WHEN DOING PAY IN FULL and fixed on fileapayfulb.pls 120.16.12000000.4Patch 11772495
211.5Paying a single payment the following error is encountered:

"APP-SQLAP-10000 ORA-06502-PLSQL NUMBERIC Or VALUE ERROR
character string buffer too msall
occurred in ap-calculated_interest
ap_pay_in_full.pkg.get_singlePayment amount->
ap_pay_in_full_pkg(ap_create_payments)
Bug 4744701: Error When Try To Pay In Full Invoice With Long Invoice_Num Ora-06502 APXINWKB.fmb 115.858Apply latest patch from Note 1303110.1
312.0During payment processing , clicking on payment error message is received

ERROR:
======
APP-SQLAP-10000: ORA 06502: PL/SQL NUMERIC OR VALUE ERROR OCCURRED IN
AP_PAY_IN_FULL_PKG.AP_LOCK_INVOICES<--APXPAWKB
With parameters (P_invoice_id=...) while performing the following operation:
Get vendor and currency info for invoice_id: ...

In some cases after the original fix for Bug 7721348 the following error was then encountered in the Invoice Workbench (Tracked via Bug 8374272):

ORA-1403: no data found
FRM-40735:WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-6502

Bug 7721348 ORA-6502: PL/SQL: NUMERIC OR VALUE ERROR IN PAY-IN-FULAPXPAWKB.fmb 120.183.12000000.102 Apply latest patch from Note 1303110.1

Secondary bug is included ad a dependent fix in the latest patch for payment workbench

411.5Argentina Localizations
Create a payment and save, the following error occurs:

APP-JL-62481:
ORA 06502 : PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "APPS.JL_ZZ_AP_WITHHOLDING_PKG", line 2533
ORA-01403: no data found occured in
JL_ZZ_AP_WITHHOLDING_PKG.Get_cumulative_supp_exemp
<--JL_ZZ_AP_WITHHOLDING_PKG.Process_Withholding_Name with parameters...
The issue is caused by the following setup: Period definition.

The following script appear in the package that failed.

SELECT start_date, end_date
FROM ap_other_periods
WHERE application_id = 200
AND module = 'AWT'
AND period_type = '&AWT_Period_Type'
AND period_name = '&period_name'; 		Setup > Calendar > Special Calendar

The tax calculation is only performed after opening periods to this calendar.
Make sure you have an AWT period defined (AWT calendar) and the correct range of dates entered.

Note 198651.1 APXAMDOP How to Define a Special Calendar
512.0Unable to pay invoice using Actions> Pay In Full which throws the following errors:


AP_PAY_IN_FULL_PKG is Invalid.

AP_PAY_IN_FULL_PKG
PLS-00323: subprogram or cursor 'AP_LOCK_INVOICES' is declared in a package specification and must be defined in the package body

ORA-6502: PL/SQL: NUMERIC OR VALUE ERROR
Bug 7721348 ORA-6502: PL/SQL: NUMERIC OR VALUE ERROR IN PAY-IN-FULL

Package specification out of synch with package body		apayfulb.pls-120.16.12000000.7

apayfuls.pls-120.7.12000000.3		Patch 7721348
611.5When trying to pay an invoice in full for a supplier setup to charge interest, the following error happens:


APP-SQLAP-10000 ORA-1722 invalid number occured in
ap_calculate_interest<
AP_PAY_IN_FULL_PKG.GET_SINGLE_PAYMENT_AMOUNT<
AP_PAY_IN_FULL_PKG.
AP_GET_CHECK_AMOUNT .....
while performing the following operation :
Calling custom interest package

APP-SQLAP-10000 ORA-06502 AP_CALCULATE_INTEREST
Bug 6114459

Similar report in Bug 4254258 was fixed in AP.N		apcstiib.pls 115.5Patch 6238802
(Requires AP.O)
712.1When creating a single payment with payment method that have a length greater than 25 characters and attempting to pay in full, error message is received.

ERROR:
======

-> APP-SQLAP-10000: ORA-6502 : numeric or value error occured in
-> AP_PAY_IN_FULL_PKG.AP_LOCK_INVOICES<-APXPAWKB with
-> parameters (P_invoice_id_list = 21750) while performing the following
-> operation: Get vendor and currency info for invoice_id: ...
Bug 9109346 TST1212.XB5.QA:NOT ABLE TO SINGLE PAY AFTER PAYMENT METHOD NAME IS TOO LONG

Bug 9113244 (12.1 fix)		APXPAWKB.fmb 120.183.12000000.180

APXPAWKB.fmb 120.223.12010000.136		Apply latest patch from Note 1303110.1
@ Original patches reported to fix (use in a pinch if customer cannot apply latest code)

     2) Void / Refund Processing

#ReleasePresentation / Error Stack Root CauseFixed FileRecommended Patch
112.1Federal Financials:

When an interest invoice that is paid alone through a
check, and the check is void attempted with invoice action
set to CANCEL, the following unhandled database error
is thrown:


APP-SQLAP-10000: ORA-06502: PL/SQL: numeric or value
error occurred in:
AP_CANCEL_PKG.AP_CANCEL_INVOICES<-AP_VOID_PKG.AP_REVERSE_CHECK
<-APXPAWKB-> with parameters (......)
while performing the following operation:
Open invoices_cursor and do bulk fetch
Bug 11781836 ORA-06502: WHEN VOIDING PAID-ALONE INTEREST INVOICE CHECK WITH CANCEL ACTIONapicancb.pls 120.35.12010000.21Patch 11781836

     3) Invoice Selection

#ReleasePresentation / Error Stack Root CauseFixed File (or fix)Recommended Patch
111.5When attempting to add an invoice to payment batch, the following error occurs:

APP-SQLAP-10000: ORA-06502 PL/SQL numeric or value error character string too small occurred in
ap_calculate_interest<-Pay Invoice Forms<-Bat Mdfy Pdet Item.
Bug 5858773 Apxpawkb Add Invoice To Payment Batch With Error APP-SQLAP-10000: ORA-6502APXPAWKB.fmb 115.501 Apply latest patch from Note 1303110.1
211.5 - 12.0Payment workbench throws error when loading/entering large number of invoices in Enter/Adjust invoice and attempting quick payment.

ERROR
-----------------------
ORA-01403: no data found
FRM-40735: WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-06502.
Bug 8420992 and Bug 9601535 APXPAWKB FRM-40735:WHEN-VALIDATE-ITEM TRIGGER UNHANDLED EXCEPTIONQuick Payments do not support large volume invoice processing. (300+) Users are required to use PPR for payment processing when large-numbers of invoices are involved.

Can occur in 11i with as few as 100 invoices.		No Patch Available
@ Original patches reported to fix (use in a pinch if customer cannot apply latest code)
By Sujeet jha at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

ORA-00059: Maximum Number Of DB_FILES Exceeded in 19C database

When I am adding datafile to my 19C database facing the below error. SQL> alter tablespace DATA  add datafile '/u01/data/data15.dbf...