R11i:AP: Build Program Error - Cannot Complete Check Numbering (Doc ID 563111.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

Problem Statement:
The build program fails when the check number has more than 11 characters. Initially the same bug
was opened (6647918 ),the <patch 6909124> was applied but this patch included the fix only in the
cepaymentdocumentseoimpl.java file but the problem is still there and the build program fails
with the following error:

IBY_DISBURSE_UI_API_PUB_PKG.unlock_pmt_entity: EXIT
IBY_DISBURSE_SUBMIT_PUB_PKG.submit_payment_process_request: EXIT
**Ends**
BUILD PROGRAM ERROR - CANNOT COMPLETE CHECK NUMBERING

This is the module where the code is failing:

ibyckprb.pls 120.56.12000000.9

The function isContigPaperNumAvlbl has a for loop "FOR i IN p_start_number .. p_end_number LOOP"
that creates a ORA-01426: numeric overflow because i is an integer and the 10 digit check number
is larger than an integer and the 10 digit check number is larger than an integer.

The check numbers are in the range 2300000000 - 2399999999 which is larger then a pls_integer used
in the for loop.

From PL/SQL User's Guide and Reference 10.2 page 4-10 on For loops.

Internally, PL/SQL assigns the values of the bounds to temporary PLS_INTEGER variables, and, if
necessary, rounds the values to the nearest integer. The magnitude
range of a PLS_INTEGER is -2147483648 to 2147483647, represented in 32 bits. If a bound evaluates
to a number outside that range, you get a numeric overflow error when
PL/SQL attempts the assignment. See "PLS_INTEGER Datatype" on page 3-4.

Cause

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