Category ABAP Programming Error
Runtime Errors COMPUTE_BCD_OVERFLOW
ABAP Program SAPLSDNT
Application Component BC-DWB-DIC-AC
Date and Time 13.07.2017 12:04:57
Overflow during the arithmetical operation (type P) in program "SAPLSDNT".
Error in the ABAP Application Program
The current ABAP program "SAPLSDNT" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
procedure "DD_PUT_TATAF" "(FUNCTION)", nor was it propagated by a RAISING
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 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
"BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
"SAPLSDNT" or "LSDNTU12"
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
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
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
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
"DD_PUT_TATAF" "(FUNCTION)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
SUM, SAP ABAP system, on SYBASE
KBA , BC-DWB-DIC-AC , Activation Prog., Conversion Prog., DB-Utility, MC, SPDD , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.