COMPUTE_BCD_OVERFLOW (New GL Migration)

Question

Hi Experts,
I'm doing the migration from Classic GL to New GL when I encountered this dump during migration of current fiscal year documents.
Runtime Errors: COMPUTE_BCD_OVERFLOW
Exception: CX_SY_ARITHMETIC_OVERFLOW
ABAP program "CL_FAGL_OI_READ===============CP" was terminated.
Error analysis:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
caught in
procedure "P_SPLINFO_COMPRESS" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
An overflow was discovered in an ongoing arithmetical operation with
operands of type P. Possible causes are:
1. The result field of type P is too small for the result.
2. The result or a intermediate result has more than 31 decimal places.
How to Correct Error:
How to correct the error
    The result field must be enlarged, if this is still possible. It may
    also be possible to break up the current process into subprocesses so
    that only smaller values occur.
    There may already be a solution to the error in the SAP notes system.
    If you have access to the SAP notes system first try searching with the
    following keywords:
     "COMPUTE_BCD_OVERFLOW"
     "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
     position)
     "CL_FAGL_OI_READ===============CP" or "CL_FAGL_OI_READ===============CM00L"
     "P_SPLINFO_COMPRESS"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"P_SPLINFO_COMPRESS" "(METHOD)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
SAP-Release 700
Application server... "cixusr"
Network address...... "10.216.15.219"
Operating system..... "HP-UX"
Release.............. "B.11.31"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 12
Shortdump setting.... "full"
Database server... "fh007204"
Database type..... "ORACLE"
Database name..... "CIX"
Database user ID.. "SAPERP"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700

Answer 1

Hi Dear,
In the running system if you add any additional depreciation area we have to run the program for data consistence. Please check with SAP. I hope there will be a Note.
Regards
Radha