05-03-2013 10:47 PM
Hello experts,
I had developed a ALV report program in SD module.
When I execute the program for 1 month period.. it is working fine. but when I select 2 months...am getting the short dump. that is pointing error in a standard FM. And the dump description is
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "TSEG_READ_PRESTEP" "(FORM)", 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:
When attempting to convert the value 32768, an overflow occurred.
My points are...
1. the program is correct. and showing correct data when we test for small data.
2. This dump is coming when I execute for 2 months or more..here the error showing is like syntax error....so I am getting confused whether it is syntax error or performance error.
Please suggest...
dk.
05-04-2013 12:47 AM
Hi,
The error indicates an error when it fails to type cast or put the value in. Say either conversion from one type to another like float to packed decimals fails or a variable in small to hold the value like a count field. Go to ST22 and download and attach the dump file as txt. It will help me to find the cause quickly.
Cheers,
Arindam
05-04-2013 12:47 AM
Hi,
The error indicates an error when it fails to type cast or put the value in. Say either conversion from one type to another like float to packed decimals fails or a variable in small to hold the value like a count field. Go to ST22 and download and attach the dump file as txt. It will help me to find the cause quickly.
Cheers,
Arindam
05-08-2013 2:46 PM
05-04-2013 2:06 AM
Hi,
Category ABAP Programming Error
Runtime Errors CONVT_OVERFLOW
Except. CX_SY_CONVERSION_OVERFLOW
ABAP Program SAPLTSEG
Application Component SD-BF
Date and Time 05/03/2013 21:36:26
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Overflow when converting from 32768 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "SAPLTSEG" 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_CONVERSION_OVERFLOW', was not |
| caught in |
| procedure "TSEG_READ_PRESTEP" "(FORM)", 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: |
| When attempting to convert the value 32768, an overflow occurred. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| If the error occurred in your own ABAP program or in an SAP |
| program you modified, try to remove the error. |
| |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW" |
| "SAPLTSEG" or "LTSEGF02" |
| "TSEG_READ_PRESTEP" |
| |
| 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 |
| "TSEG_READ_PRESTEP" "(FORM)", or its possible occurrence must be declared in |
| the |
| RAISING clause of the procedure. |
| To prevent the exception, note the following: |
------------------------------------------------------------------------------------------------
dk
05-04-2013 6:47 AM
Hi,
As evident from the dump. The error occurred when trying to convert the value 32768. The dump text that you posted is not complete. It will also have the exact code line with '>>>' symbol where the error occurs, You can set a breakpoint there to see to what format it tries to convert or post the code here.
Cheers,
Arindam
05-04-2013 7:32 AM
05-08-2013 2:45 PM
Hi,
Thanks to everybody,
Actually..there was some type mismatch between two variables in standard FM TSEG_READ, the dump is coming when the data exceeds the length of the variable.
Regards,
Dileep.