CONVT_OVERFLOW CX_SY_CONVERSION_OVERFLOW SAPLMELOG

Dear Friends,
While executing the tocde me2n and on selecting a particular purchase order from the list ABAP Runtime error occurs attached in screen shot and on analysis of the error through st22 the following occurs.
Category              ABAP Programming Error
Runtime Errors        CONVT_OVERFLOW
Except.                CX_SY_CONVERSION_OVERFLOW
ABAP Program          SAPLMELOG
Application Component MM-PUR
Date and Time          15.07.2014 17:12:40
    Memory consumption
    Roll.... 0
    EM...... 25138752
    Heap.... 0
    Page.... 172032
    MM Used. 6808880
    MM Free. 1567808
User and Transaction
    Client.............. 300
    User................ 100705
    Language key........ "E"
    Transaction......... "ME23N "
    Transaction ID...... "53C28585E41A0840E1008000C0A86333"
    EPP Whole Context ID.... "53BD934778990980E1008000C0A86333"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPLMELOG"
    Screen.............. "SAPMSSY0 1000"
    Screen Line......... 6
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPLMELOG" - in "ME_LOG_READ".
    The main program was "RM_MEPO_GUI ".
    In the source code you have the termination point in line 152
    of the (Include) program "LMELOGU04".
    The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
    occurred in
    procedure "ME_LOG_READ" "(FUNCTION)", but it was neither handled locally nor
    declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLMELOG "; its source code begins in line
    1 of the (Include program "LMELOGU04 ".
Kindly do help.
Regards,
Sayan

Dear Caetano,
The sap note specifies about parked/held PO. But in my case neither of the PO is held/parked.
Please guide.
Regards,
Sayan

Similar Messages

"CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"

When i run the transaction SM35 everything is working property but in the ends that Error:
Error in the ABAP Application Program
The current ABAP program "SAPLGLT0" 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_CONVERSION_OVERFLOW', was not
caught in
procedure "SPLIT_FROM_BASIS" "(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 "-3.34076e+11", an overflow occurred.
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"
"SAPLGLT0" or "LGLT0F61"
"SPLIT_FROM_BASIS"
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
"SPLIT_FROM_BASIS" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Any idea to resolve it???

Hi,
Convert .TXT to .XLS and check the values if you find "-3.34076e+11" select right click --> format cells -->select number if you have decimal places, specify the decimals and click Ok. Save the file and convert to .txt.
If it doesn't work then check with ABAPer.
Regards,
Raj

Run time error CONVT_OVERFLOW

dear Sir
we have window 7 for new oc as soon runned teh program cv01n i got run time error msg CX_SY_CONVERSION_OVERFLOW,plese guide
Runtime Errors         CONVT_OVERFLOW
Except.                CX_SY_CONVERSION_OVERFLOW
Date and Time          03.05.2010 14:26:31
Short text
Overflow when converting from "-1"
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLCV120" 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 "SYS_GET_WINDOW_SYSTEM" "(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 "-1", 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"
    "SAPLCV120" or "LCV120F28"
    "SYS_GET_WINDOW_SYSTEM"
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
    "SYS_GET_WINDOW_SYSTEM" "(FORM)", or its possible occurrence must be declared
     in the
RAISING clause of the procedure.
    To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "APP2"
    Network address...... "132.147.166.13"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x IA64 Level 3"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
Database server... "DB"
    Database type..... "MSSQL"
    Database name..... "ELP"
    Database user ID.. "elp"
Char.set.... "C"
SAP kernel....... 700
    created (date)... "Aug 23 2009 22:38:30"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "SQL_Server_8.00 "
Patch level. 221
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
     NT 6.0"
Memory consumption
Roll.... 16192
EM...... 29328880
Heap.... 0
Page.... 655360
MM Used. 3095760
MM Free. 1091456
User and Transaction
Client.............. 900
    User................ "CPTN_SAPC5"
    Language key........ "E"
    Transaction......... "CV03N "
    Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"
Program............. "SAPLCV120"
    Screen.............. "SAPLCV110 0101"
    Screen line......... 3
regards
kunal

Hi Kunal,
you can display both type of document 2003 and 2007 also. You need to configure these applications in define workstation application by using t-code DC30.
then you can display these files.
Regards,
Ravindra

Error while creation PR to PO in the background job

Hi,
Pl help to assist this error. We have job creatiing PO using PR. there was an error pl advice.
Short text
    Overflow when converting from "3.47025e+13"
hat happened?
   Error in the ABAP Application Program
   The current ABAP program "SAPLV61A" had to be terminated because it has
   come across a statement that unfortunately cannot be executed.
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 "FRM_KONDI_WERT_826" "(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 "3.47025e+13", 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"
    "SAPLV61A" or "RV64A826"
    "FRM_KONDI_WERT_826"
    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".
I have found another link it says there was an OSS note for this error.
Overflow when converting from "1.64174e+11"
Regards,
Kumar

closed

Overflow when converting from "2.42855e+009"(CX_SY_CONVERSION_OVERFLOW )

Hi,
when i try to Active Business content i am getting ABAP run time error CONVT_OVERFLOW Exception CX_SY_CONVERSION_OVERFLOW
Can some one help me how to resolve this problem?
Thanks and Regards,
Goutam

Hi,
Try to declare your variable using Packed Number:
DATA: va_num TYPE P DECIMALS 3.
Hope this helps.
Patrick

CX_SY_CONVERSION_OVERFLOW DUMP IN APD

Hi everybody,
By executing an APD I´m getting a DUMP with the following information
Err.exec. time         CONVT_OVERFLOW
Excep.                 CX_SY_CONVERSION_OVERFLOW
Anál.errors
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 "DT_ODS_F_00001_CU" "(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 100, an overflow occurred.
The source query executes perfectly in all the environments (BEX analyzer, WAD). There is a field 0CFM_CC_CUR in the query in which is the cause of the DUMP. By deleting this charactic from the query the problem disappear.
It looks like, something regarding currency conversion is failling, but really, I can´t find where the problem is.
I appreciate a lot your help in solving this problem.
Best regards

Conversion overflow could be due to
1. Incorrect mapping of fields
2. Field value exceeding maximum possible value - for instance value of an Integer KF cannot be more than 65535 or -65535
If your source is a query - execute the query separatelky and check the values of the Key figures and then if any of the values exceed the integer value limits - change that KF to Float and then try.

Runtime Errors: CONVT_OVERFLOW while executing transaction sm66

Hello Everyone,
There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
Please suggest
Runtime Errors         CONVT_OVERFLOW
Exception              CX_SY_CONVERSION_OVERFLOW
Date and Time          02.04.2011 00:41:01
Short text
     Overflow when converting from "2.90113e+09"
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 "TH_WP_DETAIL_INFO" "(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:
     When attempting to convert the value "2.90113e+09",
     an overflow occurred.
     There is probably an error in the program
     "SAPLTHFB".
How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     You may able to find an interim solution to the problem
     in the SAP note system. If you have access to the note system yourself,
     please use the following search criteria:
     "SAPLTHFB" "CONVT_OVERFLOW"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
    To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
    To obtain this, call the system log with Transaction SM21
    and select the "Print" function to print out the relevant
    part.
3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, you can either use the "PRINT" command in the editor or
    print the programs using the report RSINCL00.
4. Details regarding 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
"TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
tem environment
SAP-Release 700
Application server... "POSDMCI"
Network address...... ""
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "POSDMDB"
Database type..... "ORACLE"
Database name..... "BP2"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 16192
EM...... 8379696
Heap.... 0
Page.... 40960
MM Used. 720912
MM Free. 3466336
Information on where terminated
    Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
    The main program was "SAPMSM66 ".
    In the source code you have the termination point in line 82
    of the (Include) program "LTHFBU26".
    The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
     occurred in
    procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLTHFB "; its source code begins in line
    1 of the (Include program "LTHFBU26 ".

Hello Everyone,
There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
Please suggest
Runtime Errors         CONVT_OVERFLOW
Exception              CX_SY_CONVERSION_OVERFLOW
Date and Time          02.04.2011 00:41:01
Short text
     Overflow when converting from "2.90113e+09"
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 "TH_WP_DETAIL_INFO" "(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:
     When attempting to convert the value "2.90113e+09",
     an overflow occurred.
     There is probably an error in the program
     "SAPLTHFB".
How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     You may able to find an interim solution to the problem
     in the SAP note system. If you have access to the note system yourself,
     please use the following search criteria:
     "SAPLTHFB" "CONVT_OVERFLOW"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
    To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
    To obtain this, call the system log with Transaction SM21
    and select the "Print" function to print out the relevant
    part.
3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, you can either use the "PRINT" command in the editor or
    print the programs using the report RSINCL00.
4. Details regarding 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
"TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
tem environment
SAP-Release 700
Application server... "POSDMCI"
Network address...... ""
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "POSDMDB"
Database type..... "ORACLE"
Database name..... "BP2"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 16192
EM...... 8379696
Heap.... 0
Page.... 40960
MM Used. 720912
MM Free. 3466336
Information on where terminated
    Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
    The main program was "SAPMSM66 ".
    In the source code you have the termination point in line 82
    of the (Include) program "LTHFBU26".
    The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
     occurred in
    procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLTHFB "; its source code begins in line
    1 of the (Include program "LTHFBU26 ".

CONVT_OVERFLOW Error with Message GLT0 004 during Currency Translation

Hi,
We were getting the dump CONVT_OVERFLOW ((exception CX_SY_CONVERSION_OVERFLOW) while doing Currency transalation using FAGL_FC_TRANS. Upon suggestion of SAP we had applied the SAP Notes: 1299593 & 1167551. With the Notes applied the dump has been handled to an Error Message GLT0 004. Upon this SAP had suggested another SAP Solution Note:1072850 to review the configuration for Document Splitting. We are not able to figure out the possible solution.And we are still not able to come out of this error and the Month end closing is stuck as a result. The root cause for this error is ,a verly low balance (.01) in the cash account.
Request your help in coming out of this error.
Regards
SAI

Hi paul,
can you please eloborate your statement. What is that 100 that you are referring to?

CONVT_OVERFLOW Error - Inbound Proxy

Hello,
I have configured an Inbound Proxy and while testing the same, it throws CONVT_OVERFLOW error. I even checked the field whether it is exceeding the required length but it's length is perfect.
Has anyone come acrossed this error.
Regards.
Praveen

Hi,
CATCH SYSTEM-EXCEPTIONS file_access_errors
Exception problem
What is the problem with the code?
Overflow when converting from "2.42855e+009"(CX_SY_CONVERSION_OVERFLOW )
What is the difference between MOVE and WRITE TO ststement?
Converting Char to Quantity field
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8c92d590-0201-0010-5aa0-ee7a993f295c
Extract Numbers from Text Field?
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a2dce90-0201-0010-2b83-f777fb9588f5
Regards
Chilla

Runtime Errors    BCD_FIELD_OVERFLOW Exception CX_SY_CONVERSION_OVERFLOW

Dear All,
I am getting below error in PRD system. We are using ecc6, oracle 10g and windows 2003. The error coming after we have restarted the server. Please suggest how to solve the issues.
SM21 log
09:30:21 DIA 000 000 DDIC                               AB 0 Run-time error "BCD_FIELD_OVERFLOW" occurred
09:30:21 DIA 000 000 DDIC                               AB 1 > Short dump "100913 093034 nodeA " generated
ST22
Runtime Errors         BCD_FIELD_OVERFLOW
Exception              CX_SY_CONVERSION_OVERFLOW
Date and Time          13.09.2010 00:30:19
Short text
     A calculation field is defined too small.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_SWNC_RECORD================CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
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 "DO_TRANSFORMATIONS" "(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:
    A value generated during processing is too large for the
    field "ME->MAIN_RECORD_STR+1020(7)" of the program
     "CL_SWNC_RECORD================CP".
Regards,
Kumar

Dear Friends,
We even got same dump "BCD_FIELD_OVERFLOW" just after system restart. But error was slightly different. Please find below error details and solution:
Error Details:
The current ABAP program "CL_SWNC_RECORD================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error Analysis:
An exception occurred that is explained in detail below. This exception cannot be caught in the context of the current statement.
The reason for the exception is: A value generated during processing is too large for the field " " of the program "CL_SWNC_RECORD================CP".
"BCD_FIELD_OVERFLOW" " "
"CL_SWNC_RECORD================CP" or "CL_SWNC_RECORD================CM002"
"CALCULATE_PROCESSING_TIME"
SOLUTION:
An OSS Note:
Note 1103295 - BCD_FIELD_OVERFLOW in CALCULATE_PROCESSING_TIME (It solves the problem)

Run time error occuring due to the exception "CX_SY_CONVERSION_OVERFLOW",

hi,
Programme which is present in process chain,is getting the error the exception "CX_SY_CONVERSION_OVERFLOW",like this.
Can any body please help me out on this.
Thanks & Regards,
Aswini.

Hi,
Check the shot dump (ST22) and post the logic block where exactly you are getting error.
regards,
raju

Dump: BCD_OVERFLOW showing exception as CX_SY_CONVERSION_OVERFLOW

Hi Experts,
I am getting the dump as BCD_OVERFLOW showing exception as CX_SY_CONVERSION_OVERFLOW. I have tried to go through the standard notes 1151693, 1147593, 754758 & few others. But I am not able to find the note specific to my software component details:
SAP_ABA     700     0011     SAPKA70011
SAP_BASIS     700     0011     SAPKB70011
PI_BASIS     2005_1_700     0018     SAPKIPYJ7I
ST-PI     2005_1_700     0001     SAPKITLQI1
SAP_BW     700     0008     SAPKW70008
LCAPPS     2005_700     0001     SAPKIBHD01
SAP_AP     700     0005     SAPKNA7005
SAP_APPL     600     0005     SAPKH60005
SAP_HR     600     0002     SAPKE60002
EA-IPPE     400     0002     SAPKGPID02
EA-APPL     600     0002     SAPKGPAD02
EA-DFPS     600     0002     SAPKGPDD02
EA-FINSERV     600     0002     SAPKGPFD02
EA-GLTRADE     600     0002     SAPKGPGD02
EA-HR     600     0002     SAPKGPHD02
EA-PS     600     0002     SAPKGPPD02
EA-RETAIL     600     0002     SAPKGPRD02
FINBASIS     600     0002     SAPK-60002INFINBASIS
CPRXRPM     400     0002     SAPK-40002INCPRXRPM
ECC-DIMP     600     0002     SAPK-60002INECCDIMP
ERECRUIT     600     0002     SAPK-60002INERECRUIT
FI-CA     600     0005     SAPK-60005INFICA
FI-CAX     600     0005     SAPK-60005INFICAX
INSURANCE     600     0002     SAPK-60002ININSURANC
IS-CWM     600     0002     SAPK-60002INISCWM
IS-H     600     0002     SAPK-60002INISH
IS-M     600     0002     SAPK-60002INISM
IS-OIL     600     0002     SAPK-60002INISOIL
IS-PS-CA     600     0002     SAPK-60002INISPSCA
IS-UT     600     0002     SAPK-60002INISUT
LSOFE     600     0002     SAPK-60002INLSOFE
SEM-BW     600     0002     SAPKGS6002
SLL-LEG     7.00     0006     SAPK-70006INSAPSLL
WFMCORE     200     0002     SAPK-20002INWFMCORE
AIN     400     0000          -
The reason for the exception is:
In the current arithmetic operation with operands of type P an overflow
has been detected. Possible causes are:
1. The result field of type P is too small to store the result.
2. The result or an intermediate result has more than 31 decimal places.
Request you to please suggest me the solution to overcome this dump.
Thanks & Regards,
Naresh.

Hi,
If the problem occurs from your cutom programs, ask developer to fix them.
If error from SAP standard program and if you did not made any changes to program, raise product error message with SAP.
If it was SAP standard program and you made any changes by yourself/customer, revert back the changes.
Regards.

Back ground job error ABAP/4 processor: CONVT_OVERFLOW

Hi all,
i getting the error ABAP/4 processor: CONVT_OVERFLOW while executing the Zprogram(custom) in background.
This background job is failed at move statement.
what may cause this error?
please help me regarding this issue>
thanks in advance.

Hi PR ,
check ST22 , in that ananlysis screen see for the arrow make from where dump is tiggered .
so here u have to look in.
this error comes when there is type miss match.
Regards
Peram

BCD_OVERFLOW CX_SY_CONVERSION_OVERFLOW /VIRSA/ZVFATBAK

Hi guys,
I have my FF user executing transaction SE38 and upon the execution, the background job /VIRSA/VFATBAK ended in status "Canceled". In the log, its shows the below description for the background job cancallation.
Short text
Overflow during an arithmetic operation (type P) in program "/VIRSA/ZVFATBAK".
What happened?
Error in the ABAP Application Program.
The current ABAP program "/VIRSA/ZVFATBAK" had to be terminated because it has come across a statement that unfortunately cannot be executed. A value is too long for a calculation field.
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 "GET_SE38_CHANGES" "(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:
In the current arithmetic operation with operands of type P an overflow has been detected. Possible causes are:
1. The result field of type P is too small to store the result.
2. The result or an intermediate result has more than 31 decimal places.
How to correct the error
Maybe the result field - if still possible - must be defined larger.
Maybe the current process can be divided into separate units in a way that only smaller values occur.
Anyone shares this experience before and if you have resolve it via the proposed way to coorect the error?
If you have successfully executed the corrections, can you pls share on the steps to be taken?
Thanks.
Raymond

An calculation causes an exception because the result variable is too short to store the result.
You can 2 things to solve the problem :
- Add an error handling mechanisme CATCH or TRY to get the exception and act on it (message or something else)
- change the result variable so that it can store the resulting value
regards,
hans

Convt_overflow error..

Hi,
i am getting an overflow error in the following append statement for a vaue such as 0006000000. but i have defined as kunnr(12) . my code looks like this.. it throws dump everytime and that exception/error is not being caught ..
TYPES: BEGIN OF X_ITAB,
          KUNNR(12),
        END OF X_ITAB.
DATA: WA_ITAB TYPE X_ITAB,
        I_TAB TYPE TABLE OF X_TAB.
CATCH SYSTEM-EXCEPTIONS convt_overflow = 1.
      COMMIT WORK.
      SELECT KUNNR INTO WA_ITAB FROM VBPA WHERE PARVW = 'WE'.
        APPEND WA_ITAB TO I_TAB.
      ENDSELECT.
ENDCATCH.
      IF SY-SUBRC <> 0.
        MESSAGE E000(37) WITH 'RUNTIME ERROR'.
        EXIT.
      ENDIF.

Hi
Use: I_TAB like TABLE OF WA_TAB instead of I_TAB TYPE TABLE OF X_TAB.
Also comment out below code:
IF SY-SUBRC 0.
MESSAGE E000(37) WITH 'RUNTIME ERROR'.
EXIT.
ENDIF
Now check in debug, you internal table is populating.
Now even if you put KUNNR(10), it will work
Regards,
Nisarg

CONVT_OVERFLOW CX_SY_CONVERSION_OVERFLOW SAPLMELOG

Similar Messages

Maybe you are looking for