Runtime Error ''COMPUTE_BCD_OVERFLOW''
Dear Experts,
I am getting below ABAP Error.
-----------------------------------------------------------------------------------------------
Category ABAP Programming Error
Runtime Errors COMPUTE_BCD_OVERFLOW
Except. CX_SY_ARITHMETIC_OVERFLOW
ABAP Program SAPLMLSH
Application Component MM-SRV
Date and Time 15.04.2013 13:44:49
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Overflow during the arithmetical operation (type P) in program "SAPLMLSH". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "SAPLMLSH" had to be terminated because it has |
| come across a statement that unfortunately cannot be executed. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can you do? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|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 "MS_MOVE_BAPIESLL_TO_ESLL" "(FUNCTION)", 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 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) |
| "SAPLMLSH" or "LMLSHU15" |
| "MS_MOVE_BAPIESLL_TO_ESLL" |
| |
| 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 |
| "MS_MOVE_BAPIESLL_TO_ESLL" "(FUNCTION)", or its possible occurrence must be |
| declared in the |
| RAISING clause of the procedure. |
| To prevent the exception, note the following: |
----------------------------------------------------------------------------------------------------
Please suggest & help.
Regards,
Awadhesh