My Oracle Support Banner

APAYDSFR Batch Is Failing Due To CNT Field Error And Depicts Incorrect Status (Doc ID 2631918.1)

Last updated on JANUARY 30, 2020

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.6.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.6.0.1.0 version

There are Multiple issues with APAYDSFR Batch.

1. Batch is failing due to the error below:

ERROR (com.splwg.base.api.program.AbstractProgram) Exception encountered in executing StringField (
  name=ProgramName
  value=StringFieldValue(value=CIPPSBIX)
  ). Please see log for details.
com.splwg.base.api.program.types.MathOverflowException: Numeric Overflow: 19263. Can't write to Numeric Field: NumberFieldMD (
  name=Cnt
  primaryName=CNT
  index=4
  byteRange=[44,47] size=4
  precision=4
  scale=0
  signed=true
  )
According to the Cobol converted Code's Metadata, the size of the field CNT should be only four digits.  We  have scenarios where the value is five digits.

2. When we check the Metadata on the UI, the size of CNT field is five. So there is some problem with the Base Metadata generated for Cobol converted code.
3. Even after the batch failed with the error, the job status was still in progress. This is not a true depiction of  the job status.
4. Batch is very slow. There is a query which searches a specific settlement_id_nbr in CI_FT table. Since settlement_id_nbr is not an indexed field in CI_FT, the query is slow.

ERROR
-----------------------
ERROR (com.splwg.base.api.program.AbstractProgram) Exception encountered in executing StringField (
  name=ProgramName
  value=StringFieldValue(value=CIPPSBIX)
  ).


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


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