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

Similar Messages

  • 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

  • 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?

  • 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

  • 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 ".

  • 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

  • Runtime Error upon posting Goods Receipt: CONVT_OVERFLOW

    Hi Experts,
    My user is encountering this error when she tried to define the delivery amount or qty.. and post it. Well last time, she was able to post a GR. The only thing I did was to define a TIN# in Maintenance of Additional Details for Company Code.
    Is this something to do with the configuration?
    Points will be rewarded... thanks!

    I don't get an error in DEV server.
    Overflow when converting from "1.08844e+013"
    What happened?
    The current ABAP/4 program "SAPLMBGB " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your
    SAP system administrator.
    Error analysis
    When attempting to convert the value "1.08844e+013",
    an overflow occurred.
    There is probably an error in the program
    "SAPLMBGB ".
    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 SAP note system yourself,
    please use the following search criteria:
    "CONVT_OVERFLOW"
    "SAPLMBGB " or "LMBGBFSU "
    "WERT_V_RECHNEN"
    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.
    System environment
    SAP Release.............. "40B"
    Application server....... "prosap"
    Network address.......... "192.168.0.80"
    Operating system......... "Windows NT"
    Release.................. "0"
    Hardware type............ "PENTIUM"
    Database server.......... "prosap"
    Database type............ "INFORMIX"
    Database name............ "PRO"
    Database owner........... "sapr3"
    Character set............ "E"
    SAP kernel............... "40B"
    Created on............... "May 25 1999 02:20:08"
    Created in............... "NT 4.0 1381 Service Pack 3 x86 MS VC++ 11.00?"
    Database version......... "inf INF_723_TC2"
    Patch level.............. "400"
    Patch text............... " "
    Supported environment....
    Database................. "INFORMIX 7.2*.*"
    SAP database version..... "40B"
    Operating system......... "Windows NT 0 4"
    User, transaction...
    Client.............. 400
    User................ "SAPUSR_FI05"
    Language key........ "E"
    Transaction......... "MB01 "
    Program............. "SAPLMBGB "
    Screen.............. "SAPMM07M 0210"
    Screen line......... 71
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLMBGB " in
    "WERT_V_RECHNEN".
    The main program was "SAPMM07M ".
    The termination occurred in line 779
    of the source code of program "LMBGBFSU " (when calling the editor 7790).
    Source code extract
    007490                             W-BETRAG LIKE BETRAG.
    007500
    007510     DATA: RMENGE LIKE MENGE.
    007520     RMENGE = 0 - W-MENGE.
    007530     IF ( W-EXWRT IS INITIAL AND W-EXWOB IS INITIAL ) OR
    007540        ( W-LBKUM < 0 AND ( W-SHKZG = H OR W-LBKUM < RMENGE ) ).
    007550       PERFORM WERT_WERTPROPORTIONAL USING W-SALK3
    007560                                           W-VERPR
    007570                                           W-LBKUM
    007580                                           W-PEINH
    007590                                           W-MENGU
    007600                                           W-WERTU
    007610                                           W-BWSPA
    007620                                           W-MENGE
    007630                                           W-BETRAG.
    007640     ELSE.
    007650       DATA: REXWRT LIKE EXWRT.
    007660       IF W-SHKZG = H.
    007670         IF ( W-LBKUM > W-MENGE AND NOT W-SALK3 < W-EXWRT )
    007680            OR NOT W-LBKUM > 0.
    007690           W-BETRAG = W-EXWRT.
    007700         ELSEIF NOT W-LBKUM < W-MENGE.
    007710           W-BETRAG = W-SALK3.
    007720         ELSE.
    007730           RMENGE = W-MENGE - W-LBKUM.
    007740           W-BETRAG = ( RMENGE * W-EXWRT ) / W-MENGE.
    007750           W-BETRAG = W-BETRAG + W-SALK3.
    007760         ENDIF.
    007770       ELSE.
    007780         RMENGE = W-MENGE + W-LBKUM.
    ----->         REXWRT = W-EXWRT + W-SALK3.
    007800         IF ( RMENGE < 0 AND NOT REXWRT > 0 )
    007810            OR NOT W-LBKUM < 0.
    007820           W-BETRAG = W-EXWRT.
    007830         ELSEIF NOT RMENGE > 0.
    007840           W-BETRAG = 0 - W-SALK3.
    007850         ELSE.
    007860           W-BETRAG = ( RMENGE * W-EXWRT ) / W-MENGE.
    007870           W-BETRAG = W-BETRAG - W-SALK3.
    007880         ENDIF.
    007890       ENDIF.
    007900       IF W-BETRAG > MAXIMUM OR W-BETRAG < MINIMUM.
    007910         MESSAGE E302 WITH 'WERT_V_RECHNEN' 'W-BETRAG'.
    007920       ENDIF.
    007930     ENDIF.

  • Runtime Error  CONVT_OVERFLOW in MIGO

    Hi,
    We have this issue:
    When we try to do a Good Receipt for a particular material,  the good receipt is posted, but the system show this message: Runtime Error  CONVT_OVERFLOW  (Overflow when converting from "2.1252e+09") and the good receipt can not be displayed.
    This material has a price (VEF 64.400,00) and the material quantity has not decimals (for example: 1,00).
    When we changed the price in the purchase order (for example: VEF 10,00) the good receipt was posted and the good receipt can be displayed.
    Would you please help us with this situation?
    Best Regards,
    Marielita

    Hi Mariela,
    Please refer the below notes
    SAP Note No. 192057  CONVT_OVERFLOW in MB_UPDATE_MATERIAL_VALUES  <<<<<<<<<<<<<
    SAP Note No. 831197>> Dump CONVT_OVERFLOW in goods movements with ML
    SAP Note No. 192057 Should solve your issue .
    Rgs
    SB

  • Run-time error "CONVT_OVERFLOW" occurred

    Hi all,
    we are getting the above dump in our production System from last week.
    we are using HP-UX OS and Oracle 10.0.2 DB.
    Thanks,
    Chaitanya

    Hi,
    Try to paste the complete dump, need to understand exactly at which stage your number get overflow.
    Thanks
    Anil

  • 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

  • Error in Posting GR (mb01)

    Hi Experts,
    My user is encountering this error when she tried to define the delivery amount or qty.. and post it. I'm just wondering why they were able to post a GR before July even the amount is 7 digits. The user tried to breakdown the amount but there's still an error.
    Is this something to do with the configuration? Though there was no changes in the configuration or any user exits connected to it.
    I have checked the runtime error logs in st22 and released it. But until now those errors ar still n the list. Do you think that's the reason why they get errors?
    Can I change the length of Rexwrt field? Exwert has a length of 13 characters and I want to change it to WERTV12 that has 23 characters.
    they are using SAP release 4.0:
    007650 DATA: REXWRT LIKE EXWRT.
    > REXWRT = W-EXWRT + W-SALK3.
    from SAP 6
    DATA: rexwrt TYPE wertv12.
    I don't get an error in DEV server.
    Overflow when converting from "1.08844e+013"
    What happened?
    The current ABAP/4 program "SAPLMBGB " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your
    SAP system administrator.
    Error analysis
    When attempting to convert the value "1.08844e+013",
    an overflow occurred.
    There is probably an error in the program
    "SAPLMBGB ".
    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 SAP note system yourself,
    please use the following search criteria:
    "CONVT_OVERFLOW"
    "SAPLMBGB " or "LMBGBFSU "
    "WERT_V_RECHNEN"
    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.
    System environment
    SAP Release.............. "40B"
    Application server....... "prosap"
    Network address.......... "192.168.0.80"
    Operating system......... "Windows NT"
    Release.................. "0"
    Hardware type............ "PENTIUM"
    Database server.......... "prosap"
    Database type............ "INFORMIX"
    Database name............ "PRO"
    Database owner........... "sapr3"
    Character set............ "E"
    SAP kernel............... "40B"
    Created on............... "May 25 1999 02:20:08"
    Created in............... "NT 4.0 1381 Service Pack 3 x86 MS VC++ 11.00?"
    Database version......... "inf INF_723_TC2"
    Patch level.............. "400"
    Patch text............... " "
    Supported environment....
    Database................. "INFORMIX 7.2*.*"
    SAP database version..... "40B"
    Operating system......... "Windows NT 0 4"
    User, transaction...
    Client.............. 400
    User................ "SAPUSR_FI05"
    Language key........ "E"
    Transaction......... "MB01 "
    Program............. "SAPLMBGB "
    Screen.............. "SAPMM07M 0210"
    Screen line......... 71
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLMBGB " in
    "WERT_V_RECHNEN".
    The main program was "SAPMM07M ".
    The termination occurred in line 779
    of the source code of program "LMBGBFSU " (when calling the editor 7790).
    Source code extract
    007490                             W-BETRAG LIKE BETRAG.
    007500
    007510     DATA: RMENGE LIKE MENGE.
    007520     RMENGE = 0 - W-MENGE.
    007530     IF ( W-EXWRT IS INITIAL AND W-EXWOB IS INITIAL ) OR
    007540        ( W-LBKUM < 0 AND ( W-SHKZG = H OR W-LBKUM < RMENGE ) ).
    007550       PERFORM WERT_WERTPROPORTIONAL USING W-SALK3
    007560                                           W-VERPR
    007570                                           W-LBKUM
    007580                                           W-PEINH
    007590                                           W-MENGU
    007600                                           W-WERTU
    007610                                           W-BWSPA
    007620                                           W-MENGE
    007630                                           W-BETRAG.
    007640     ELSE.
    007650       DATA: REXWRT LIKE EXWRT.
    007660       IF W-SHKZG = H.
    007670         IF ( W-LBKUM > W-MENGE AND NOT W-SALK3 < W-EXWRT )
    007680            OR NOT W-LBKUM > 0.
    007690           W-BETRAG = W-EXWRT.
    007700         ELSEIF NOT W-LBKUM < W-MENGE.
    007710           W-BETRAG = W-SALK3.
    007720         ELSE.
    007730           RMENGE = W-MENGE - W-LBKUM.
    007740           W-BETRAG = ( RMENGE * W-EXWRT ) / W-MENGE.
    007750           W-BETRAG = W-BETRAG + W-SALK3.
    007760         ENDIF.
    007770       ELSE.
    007780         RMENGE = W-MENGE + W-LBKUM.
    ----->         REXWRT = W-EXWRT + W-SALK3.
    007800         IF ( RMENGE < 0 AND NOT REXWRT > 0 )
    007810            OR NOT W-LBKUM < 0.
    007820           W-BETRAG = W-EXWRT.
    007830         ELSEIF NOT RMENGE > 0.
    007840           W-BETRAG = 0 - W-SALK3.
    007850         ELSE.
    007860           W-BETRAG = ( RMENGE * W-EXWRT ) / W-MENGE.
    007870           W-BETRAG = W-BETRAG - W-SALK3.
    007880         ENDIF.
    007890       ENDIF.
    007900       IF W-BETRAG > MAXIMUM OR W-BETRAG < MINIMUM.
    007910         MESSAGE E302 WITH 'WERT_V_RECHNEN' 'W-BETRAG'.
    007920       ENDIF.
    007930     ENDIF.
    need your knowledge badly.... thanks!

    Hi Maui,
    for this problem, u should ask to your ABAP programmer to debug the problem, he can only identify  the exact problem and solution for that.
    As per my understanding, this is the problem for input space in your PRD. only ABAP programmer can resolve this problem.
    Sachin

  • Handling unexpected errors/situations in an ABAP program

    Hi,
    if i come across a situation where i need to handle a runtime error unexpectedly what should be my approach.
    for eg. if i build a dynamic select statement and if my logic goes wrong the program flow should proceed normally as if nothing has happened 'with out giving me a short dump' . what if im not sure about the type of error thats going to show up, is there any way?
    your help will be appreciated.
    Regards,
    ravi.

    Hi Ravi
    Not all exceptions can be overridden. FYI, Below are a list of exceptions that can be handled:
    Alphabetical Overview of Catchable Runtime Errors
    Below you find an alphabetical list of all catchable runtime errors. For each runtime error, the predefined exception class assigned is specified which is used to handle the respective runtime error as of Release 6.10. If an exception class is assigned to more than one catchable runtime error, it may contain as many message texts as required which you can find in the Class Builder on the Texts tab.
    Almost all of the runtime errors listed here are combined together in exception groups. These exception groups are also assigned those ABAP keywords at which the runtime errors contained can be caught.
    ADDF_INT_OVERFLOW
    Overflow at addition, type I ( ADD ... UNTIL / ADD ... FROM ... TO)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    ASSIGN_CASTING_ILLEGAL_CAST
    The components of the source field type and the target type which are strings, tables, or references do not have exactly the same offset and type.
    Exception class: CX_SY_ASSIGN_CAST_ILLEGAL_CAST
    ASSIGN_CASTING_UNKNOWN_TYPE
    The type specified at runtime is unknown.
    Exception class: CX_SY_ASSIGN_CAST_UNKNOWN_TYPE
    ASSIGN_FIELD_NOT_IN_RANGE
    The field is not within the RANGE specified.
    Exception class: CX_SY_ASSIGN_OUT_OF_RANGE
    BCD_FIELD_OVERFLOW
    Overflow at conversion / arithmetic operation (type P, with specified length)
    Exception class: CX_SY_CONVERSION_OVERFLOW
    BCD_OVERFLOW
    Overflow at conversion / arithmetic operation (type P)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    BCD_ZERODIVIDE
    Division by 0 (type P)
    Exception class: CX_SY_ZERODIVIDE
    COMPUTE_ACOS_DOMAIN
    Invalid call of the mathematical function ACOS
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_ASIN_DOMAIN
    Invalid call of the mathematical function ASIN
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_ATAN_DOMAIN
    Invalid call of the mathematical function ATAN
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_BCD_OVERFLOW
    Overflow at arithmetic operation (all operands of type P)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_COSH_DOMAIN
    Invalid call of the mathematical function COSH
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_COSH_OVERFLOW
    Overflow at mathematical function COSH
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_COS_DOMAIN
    Invalid call of the mathematical function COS
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_COS_LOSS
    Inaccurate result of function COS
    Exception class: CX_SY_PRECISION_LOSS
    COMPUTE_EXP_DOMAIN
    Invalid call of the mathematical function EXP
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_EXP_RANGE
    Overflow or underflow at mathematical function EXP
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_FLOAT_DIV_OVERFLOW
    Overflow at division (type F)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_FLOAT_MINUS_OVERFLOW
    Overflow at subtraction (type F)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_FLOAT_PLUS_OVERFLOW
    Overflow at addition (type F)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_FLOAT_TIMES_OVERFLOW
    Overflow at multiplication (type F)
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_FLOAT_ZERODIVIDE
    Division by 0 (type F)
    Exception class: CX_SY_ZERODIVIDE
    COMPUTE_INT_ABS_OVERFLOW
    Integer overflow while calculating the absolute value
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_INT_DIV_OVERFLOW
    Integer overflow at division
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_INT_MINUS_OVERFLOW
    Integer overflow at subtraction
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_INT_PLUS_OVERFLOW
    Integer overflow at addition
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_INT_TIMES_OVERFLOW
    Integer overflow at multiplication
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_INT_ZERODIVIDE
    Division by 0 (type I)
    Exception class: CX_SY_ZERODIVIDE
    COMPUTE_LOG10_ERROR
    Invalid call of the mathematical function LOG10
    Exception classes: CX_SY_ARITHMETIC_OVERFLOW, CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_LOG_ERROR
    Invalid call of the mathematical function LOG
    Exception classes: CX_SY_ARITHMETIC_OVERFLOW, CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_MATH_DOMAIN
    Invalid call of a mathematical function
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_MATH_ERROR
    Error performing a mathematical function
    Exception class: None since this runtime error can no longer be caught
    COMPUTE_MATH_LOSS
    Inaccurate result of a mathematical function
    Exception class: CX_SY_PRECISION_LOSS
    COMPUTE_MATH_OVERFLOW
    Overflow at a mathematical function
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_MATH_UNDERFLOW
    Underflow at a mathematical function
    Exception class: None since exception no longer occurs
    COMPUTE_POW_DOMAIN
    Invalid argument when using powers
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_POW_RANGE
    Overflow or underflow when using powers
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_SINH_DOMAIN
    Invalid call of the mathematical function SINH
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_SINH_OVERFLOW
    Overflow at mathematical function SINH
    Exception class: CX_SY_ARITHMETIC_OVERFLOW
    COMPUTE_SIN_DOMAIN
    Invalid call of the mathematical function SIN
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_SIN_LOSS
    Inaccurate result of the function SIN
    Exception class: CX_SY_PRECISION_LOSS
    COMPUTE_SQRT_DOMAIN
    Invalid call of the mathematical function SQRT
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_TANH_DOMAIN
    Invalid call of the mathematical function TANH
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_TAN_DOMAIN
    Invalid call of the mathematical function TAN
    Exception class: CX_SY_ARG_OUT_OF_DOMAIN
    COMPUTE_TAN_LOSS
    Inaccurate result of the function TAN
    Exception class: CX_SY_PRECISION_LOSS
    CONNE_IMPORT_WRONG_COMP_DECS
    Import error; a component of a structured type in the dataset has wrong decimal places
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_COMP_LENG
    Import error; a component of a structured type in the dataset has the wrong length
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_COMP_TYPE
    Import error; a component of a structured type in the dataset has the wrong type
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_FIELD_DECS
    Import error; a field in the dataset has wrong decimal places
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_FIELD_LENG
    Import error; a field in the dataset has the wrong length
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_FIELD_TYPE
    Import error; a field in the dataset has the wrong type
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_OBJECT_TYPE
    Import error; type conflict between simple and structured data types
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONNE_IMPORT_WRONG_STRUCTURE
    Import error; type conflict between structured objects
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    CONVT_CODEPAGE
    Character set conversion not possible for one or more characters
    Exception class: CX_SY_CONVERSION_CODEPAGE
    CONVT_CODEPAGE_INIT
    Conversion of texts between code pages not supported
    Exception class: CX_SY_CODEPAGE_CONVERTER_INIT
    CONVT_NO_NUMBER
    Value to be converted cannot be interpreted as a number
    Exception class: CX_SY_CONVERSION_NO_NUMBER
    CONVT_OVERFLOW
    Overflow at conversion (all types, not type P)
    Exception class: CX_SY_CONVERSION_OVERFLOW
    CREATE_DATA_ILLEGAL_DECIMALS
    Invalid value for the addition DECIMALS
    Exception class: CX_SY_CREATE_DATA_ERROR
    CREATE_DATA_ILLEGAL_INIT_SIZE
    Invalid value for the addition INITIAL SIZE
    Exception class: CX_SY_CREATE_DATA_ERROR
    CREATE_DATA_ILLEGAL_LENGTH
    Invalid value for the addition LENGTH
    Exception class: CX_SY_CREATE_DATA_ERROR
    CREATE_DATA_LEN_NOT_ALLOWED
    The addition LENGTH was used for a type other than C, N, X, or P
    Exception class: CX_SY_CREATE_DATA_ERROR
    CREATE_DATA_NOT_ALLOWED_TYPE
    The type specified dynamically in the addition TYPE is not typed completely.
    Exception class: CX_SY_CREATE_DATA_ERROR
    CREATE_DATA_UNKNOWN_TYPE
    The type specified in the addition TYPE is unknown.
    Exception class: CX_SY_CREATE_DATA_ERROR
    CREATE_OBJECT_CLASS_ABSTRACT
    You attempted to instantiate an abstract class.
    Exception class: CX_SY_CREATE_OBJECT_ERROR
    CREATE_OBJECT_CLASS_NOT_FOUND
    The class specified in the dynamic CREATE OBJECT was not found.
    Exception class: CX_SY_CREATE_OBJECT_ERROR
    CREATE_OBJECT_CREATE_PRIVATE
    You attempted to create an object of a class defined as 'CREATE PRIVATE'.
    Exception class: CX_SY_CREATE_OBJECT_ERROR
    CREATE_OBJECT_CREATE_PROTECTED
    You attempted to create an object of a class defined as 'CREATE PROTECTED'.
    Exception class: CX_SY_CREATE_OBJECT_ERROR
    DATA_LENGTH_NEGATIVE
    Invalid subfield access: Length negative
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    DATA_LENGTH_0
    Invalid subfield access: Length 0
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    DATA_LENGTH_TOO_LARGE
    Invalid subfield access: Length too large
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    DATA_OFFSET_NEGATIVE
    Invalid subfield access: Offset negative
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    DATA_OFFSET_LENGTH_TOO_LARGE
    Invalid subfield access: Offset + length too large
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    DATA_OFFSET_LENGTH_NOT_ALLOWED
    Invalid subfield access: Inadequate type
    Exception class: CX_SY_OFFSET_NOT_ALLOWED
    DATASET_CANT_CLOSE
    File could not be closed; there might be no more space in the file system.
    Exception class: CX_SY_FILE_CLOSE
    DATASET_CANT_OPEN
    File cannot be opened
    Exception class: CX_SY_FILE_OPEN
    DATASET_NO_PIPE
    OPEN DATASET with the addition FILTER is not supported on the current operating system.
    Exception class: CX_SY_PIPES_NOT_SUPPORTED
    DATASET_NO_POSITION
    Access to current read/write position of file not possible
    Exception class: CX_SY_FILE_POSITION
    DATASET_NOT_OPEN
    File not open
    Exception class: CX_SY_FILE_OPEN_MODE
    DATASET_OFFSET_TO_LARGE
    Offset specified exceeds the system limit
    Exception class: CX_SY_FILE_POSITION
    DATASET_PIPE_CLOSED
    Pipe for file closed
    Exception class: CX_SY_PIPE_REOPEN
    DATASET_READ_ERROR
    Error reading a file
    Exception class: CX_SY_FILE_IO
    DATASET_READ_ONLY
    File opened in read-only mode
    Exception class: CX_SY_FILE_OPEN_MODE
    DATASET_SEEK_ERROR
    Error positioning in a file
    Exception class: CX_SY_FILE_POSITION
    DATASET_TOO_MANY_FILES
    Maximum number of open files exceeded
    Exception class: CX_SY_TOO_MANY_FILES
    DATASET_WRITE_ERROR
    Error writing a file
    Exception class: CX_SY_FILE_IO
    DYN_CALL_METH_CLASSCONSTRUCTOR
    You attempted to call the class constructor.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_CLASS_ABSTRACT
    You attempted to call an abstract method.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_CLASS
    DYN_CALL_METH_CLASS_NOT_FOUND
    You attempted to call a method of a class that does not exist.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_CLASS
    DYN_CALL_METH_CONSTRUCTOR
    You attempted to call the instance constructor.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_EXCP_NOT_FOUND
    You attempted to catch an unknown exception.
    Exception class: CX_SY_DYN_CALL_EXCP_NOT_FOUND
    DYN_CALL_METH_NOT_FOUND
    You attempted to call an unknown method.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_NOT_IMPLEMENTED
    You attempted to call a method not yet implemented.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_NO_CLASS_METHOD
    You attempted to call an instance method through a class.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_PARAM_KIND
    You attempted to pass a parameter with a wrong parameter type.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_TYPE
    DYN_CALL_METH_PARAM_LITL_MOVE
    You attempted to pass a constant actual parameter to a formal EXPORTING, CHANGING, or RETURNING parameter.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_TYPE
    DYN_CALL_METH_PARAM_MISSING
    A required parameter was not filled.
    Exception class: CX_SY_DYN_CALL_PARAM_MISSING
    DYN_CALL_METH_PARAM_NOT_FOUND
    You attempted to pass an unknown parameter.
    Exception class: CX_SY_DYN_CALL_PARAM_NOT_FOUND
    DYN_CALL_METH_PARAM_TAB_TYPE
    You attempted to pass a parameter with a wrong table type.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_TYPE
    DYN_CALL_METH_PARAM_TYPE
    You attempted to pass a parameter with a wrong type.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_TYPE
    DYN_CALL_METH_PARREF_INITIAL
    An initial data reference was passed for a required parameter.
    Exception class: CX_SY_DYN_CALL_PARAM_MISSING
    DYN_CALL_METH_PRIVATE
    You attempted to call a private method outside.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_PROTECTED
    You attempted to call a protected method outside.
    Exception class: CX_SY_DYN_CALL_ILLEGAL_METHOD
    DYN_CALL_METH_REF_IS_INITIAL
    You attempted to call a method to an initial reference.
    Exception class: CX_SY_REF_IS_INITIAL
    EXPORT_BUFFER_NO_MEMORY
    The EXPORT data cluster is too large for the application buffer.
    Exception class: CX_SY_EXPORT_BUFFER_NO_MEMORY
    EXPORT_DATASET_CANNOT_OPEN
    The IMPORT/EXPORT statement was unable to open the file.
    Exception class: CX_SY_FILE_OPEN
    EXPORT_DATASET_WRITE_ERROR
    The Export statement could not write the file.
    Exception class: CX_SY_FILE_IO
    GENERATE_SUBPOOL_DIR_FULL
    The system is unable to generate another temporary subroutine pool.
    Exception class: CX_SY_GENERATE_SUBPOOL_FULL
    IMPORT_ALIGNMENT_MISMATCH
    Import error; identical sequence of components but with type conflict or with different integration into structured data types
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    IMPORT_TYPE_MISMATCH
    Import error; only at IMPORT...FROM MEMORY | FROM SHARED BUFFER...
    Exception class: None since this runtime error can not longer be caught
    IMPORT_WRONG_END_POS
    Import error; dataset has a different length.
    Exception class: CX_SY_IMPORT_MISMATCH_ERROR
    MOVE_CAST_ERROR
    Type conflict assigning between object and/or interface references (only MOVE...?TO... or operator ?=)
    Exception class: CX_SY_MOVE_CAST_ERROR
    OPEN_DATASET_NO_AUTHORITY
    No authorization to access a file
    Exception class: CX_SY_FILE_AUTHORITY
    OPEN_PIPE_NO_AUTHORITY
    No authorization to access a file (OPEN DATASET...FILTER...)
    Exception class: CX_SY_FILE_AUTHORITY
    PERFORM_PROGRAM_NAME_TOO_LONG
    Invalid program name in the PERFORM statement
    Exception class: CX_SY_PROGRAM_NOT_FOUND
    REFI_WRONG_SECTION
    Wrong offset/length specification in the REPLACE statement
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    REPLACE_INFINITE_LOOP
    SECTION of length 0 in the REPLACE statement
    Exception class: CX_SY_REPLACE_INFINITE_LOOP
    RMC_COMMUNICATION_FAILURE
    Communication error during Remote Method Call
    Exception class: CX_SY_RMC_COMM_FAILURE
    RMC_INVALID_STATUS
    State error during Remote Method Call
    Exception class: CX_SY_RMC_INVALID_STATUS
    RMC_SYSTEM_FAILURE
    System error during Remote Method Call
    Exception class: CX_SY_RMC_SYSTEM_FAILURE
    STRING_LENGTH_NEGATIVE
    Invalid access with negative length to a string
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    STRING_LENGTH_TOO_LARGE
    Invalid access to a string (length too large)
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    STRING_OFFSET_NEGATIVE
    Invalid access with negative offset to a string
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    STRING_OFFSET_TOO_LARGE
    Invalid access to a string (offset too large)
    Exception class: CX_SY_RANGE_OUT_OF_BOUNDS
    STRING_OFFSET_LENGTH_TOO_LARGE
    Invalid access to a string (offset + length too large)
    Exception class: CX_SY_LOCALIZATION_ERROR
    TEXTENV_CODEPAGE_NOT_ALLOWED
    Character set not released in the system (SET LOCALE...)
    TEXTENV_INVALID
    Error setting the text environment (SET LOCALE...)
    Exception class: CX_SY_LOCALIZATION_ERROR

  • "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

  • 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

  • Receiving a run time error BCD_OVERFLOW

    Hello,
    While executing the Zprogram ...I am receiving a run time error.
    Got Runtime Error BCD_OVERFLOW
    When I analysed the issue in ST22....Type P
    Result is larger than one which is defined...
    Any suggestion would be appreciated ...
    Regards,
    Kittu

    Hi,
    You may need to define the result field to be larger, if it is still
    possible to do so.
      Or
    there is another way you can handle this error...
    You can give a try  using this sample code:
    Data : l_number_str type string.
    Catch system-exceptions convt_no_number    = 1
                           convt_overflow     = 2
                           bcd_field_overflow = 3
                           bcd_overflow       = 4. 
    l_number = l_number_str.
    endcatch
    Regards
    Lekha

Maybe you are looking for