Payment Upload Batch C1-PYUP2 Shows Error ORA-12899 when Person Name Exceeds 40 Characters
Last updated on MARCH 09, 2018
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 2]
Information in this document applies to any platform.
On RMB 18.104.22.168.0 version, PY - Payment against FW 22.214.171.124
A batch update with code C1-PYUP2 failed for having long person name.
Customer had setup a person name which was 44 characters. When the payment upload was performed for the account, it failed without showing the reason for failure in UI.
Records in the file were moved to pre staging i.e. C1-PYUP1 worked. Button "Move to Staging" was enabled. After the user clicked on the button nothing happened as batch C1-PYUP2 was in error. "Create Payments" button was not enabled. There was also no batch logs created, error was present in Threadpool worker logs.
Based on the logs from Threadpool worker, it is showing ORA-12899 error for passing a value that the database field is unable to hold as per data structure defined for the field in the Database.
The message is clear and as follow:
00:03:35,651 [Thread-8:WorkProcessor$WorkRunner(WorkProcessor$WorkRunner:487ca34c-6659-4701-b970-16de18c95363)] WARN (org.hibernate.engine.jdbc.spi.SqlExceptionHelper) SQL Error: 12899, SQLState: 72000
00:03:35,651 [Thread-8:WorkProcessor$WorkRunner(WorkProcessor$WorkRunner:487ca34c-6659-4701-b970-16de18c95363)] ERROR (org.hibernate.engine.jdbc.spi.SqlExceptionHelper) ORA-12899: value too large for column "CISADM"."CI_PAY_TNDR_ST"."NAME1" (actual: 49, maximum: 40)
So Name1 column for table CI_PAY_TNDR_ST is not able to hold characters over 40. But it is getting 49 characters and so the process failed and showed this ORA 12899 error.
In RMB UI, no error was shown, but it shows no successful processing of the batch request.
Most likely there will be names longer than 40 characters. Since RMB does not restrict creating such names, it should allow in payment upload as well.
The issue has the following business impact:
Due to this issue, users need to modify many person names and it is not acceptable as System allowed to create those names in the first place.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms