COMPUTE_BCD_OVERFLOW----CX_SY_ARITHMETIC_OVERFLOW runtime error

Hi all,
In MIGO tcode, while preparing GRN, after quoting batch no. & classification i am getting the following dump error.  please suggest me to resolve this.
Thank you.
Regards,
Nagenrda.
COMPUTE_BCD_OVERFLOW
CX_SY_ARITHMETIC_OVERFLOW
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
was neither
caught nor passed along using a RAISING clause, in the procedure
"J_1IEX_DEFAULT_EXCISE_DUTY" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
An overflow has been determined in the current arithmetical operation
containing operands of type P. Possible causes include:
1.  The results field of type P is to small and the result does not fit
    into it.
    places.
2.  The result or partial result has more than 31 decimal places.
The exception must either be prevented, caught within the procedure
"J_1IEX_DEFAULT_EXCISE_DUTY"
"(FUNCTION)", or declared in the procedure's RAISING clause.

Check the values which you are passing to the BDC.. the data type should be changed for a field.
You can execute the BDC with mode 'A' & check.
Best regards,
Prashant

Similar Messages

  • ABAP runtime errors    COMPUTE_BCD_OVERFLOW

    ABAP runtime errors    COMPUTE_BCD_OVERFLOW
           Occurred on     12/08/2010 at 06:44:17
    >> Short dump has not been completely stored. It is too big.
    Error analysis
    An overflow has been determined in the current arithmetical operation
    containing operands of type P. Possible causes include:
    1.  The results field of type P is to small and the result does not fit
        into it.
        places.
    2.  The result or partial result has more than 31 decimal places.
    How to correct the error
    You may need to define the result field to be larger, if it is still
    possible to do so.
    It may be possible to split the current process so that only smaller
    values occur.
    Eine Vorablösung zu dem aufgetretenen Fehler findet sich vielleicht
    If the error occurred in one of your own programs or in an SAP program
    that you modified, try to correct it yourself.
    If you require an interim solution to this error, you can look in the
    SAP note system. If you have access to
    the SAP notes system yourself, enter the following search strings:
    "COMPUTE_BCD_OVERFLOW"
    "BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
    point)

    Hi Ganapati,
    Check this thread COMPUTE_BCD_OVERFLOW in Database Performance collector.
    Note 543749 - ABAP runtime error COMPUTE_BCD_OVERFLOW
    It may helps you.

  • What is the runtime error compute_bcd_overflow.

    Hi guys,
    pls let me know that when the runtime error compute_bcd_overflow occurs.what will be the causes for this program.

    You usually get that, if a number you calculate i getting bigger than the field it is stored in allows.
    Take a look at your short dump, in the details it should give you more information and also the place in the coding where the error happens.
    Hope that helps,
    Michael

  • Runtime Error COMPUTE_BCD_OVERFLOW in co02

    Hi guys.
    I am getting the runtime error Overflow during the arithmetical operation (type P) in program "SAPLCK21" when saving via co02.
    This error occurs in the Production system but not in the test system for the same Production Order.
    Thanks in advance.

    I have gone through the specified notes.They are not applicable to our system release 605.
    (For added information: we have recently upgraded SAP from 4.7 to ECC 6.0 EHP5)
    The issue is happening only for a specific raw material 159085420000.
    We have a test system QAS which is a copy of Production (live) system.
    In QAS, if this material is added to any production order, it is getting saved without any issues.
    But in PRD, it is causing the run time error when it is added to any Production Order.
    Also the MM master data for the material 159085420000 is exactly the same in both QAS and PRD.
    Also
    The Base Unit of measure for the material is kg.
    I am using the same unit. While saving (via co02), it throws the run time error from the form price_of_purchase_info_record.
    If I change the unit  to MT (alternative unit of measure) in co02, it is getting saved without any issues.
    Edited by: kapmsd on Jan 23, 2012 6:48 AM
    Edited by: kapmsd on Jan 24, 2012 6:29 AM

  • COMPUTE_BCD_OVERFLOW -  CX_SY_ARITHMETIC_OVERFLOW

    Hello all,
    I'm getting the ABAP Dump in CJ13 tcode please find below dump error & my system release info:
    Component version    SAP ECC 6.0
    SAP_ABA      700     0010     SAPKA70010
    SAP_BASIS     700     0010     SAPKB70010
    SAP_APPL     600     0006     SAPKH60006
    Kernel release    700 (Sup.Pkg lvl.      52)
    Begin of Dump -
    Runtime Errors         COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          07.04.2008 11:53:18
    Short text
         Overflow during the arithmetical operation (type P) in program "SAPLKBPR".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLKBPR" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also keep them for a long time.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
         caught in procedure "READ_COSA" "(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:
         An overflow was discovered in an ongoing arithmetical operation with
        operands of type P. Possible causes are:
        1. The result field of type P is too small for the result.
        2. The result or a intermediate result has more than 31 decimal places.
    Regards,

    HI,
    My patch level is below but even i got a dump of "COMPUTE_BCD_OVERFLOW".
    Component       Lvl    
    SAP_ABA     0019
    SAP_BASIS     0019
    Pls. suggest.
    Thanks in advance.

  • ABAP Short Dump - COMPUTE_BCD_OVERFLOW - CX_SY_ARITHMETIC_OVERFLOW

    Runtime errors      COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    I want to move Currency variable with 4 decimals to another currency variable with 2 decimals. Please advice me with a suitable solution without causing short dump.
    Appreciate Your Help in Advance.
    Thanks.
    Kannan.

    SAP catch the exception like this :
    CATCH SYSTEM-EXCEPTIONS conversion_errors = 1
                                        arithmetic_errors = 5.
                  xkwert = xkomv-kwert * 1000 * xkomv-kpein / komp-mgame.
                  xkomv-kbetr = xkwert.
                ENDCATCH.
                IF sy-subrc = 1 OR sy-subrc = 5.
                  xkomv-kbetr = 0.
                  xkomv-fxmsg = '802'.
                  komp-fxmsg  = '802'.
                ENDIF.

  • Old Report giving the COMPUTE_BCD_OVERFLOW - CX_SY_ARITHMETIC_OVERFLOW

    Hi Guys,
    Can you please help, im not exactly an ABAP Developer but need to resolve the dump with this custom report. its an old productive report  - i guess its just  due to the volume of data being pulled since this report has been in operation years since golive
    Do i need to increase field values or make some sort of adjustment for it to handle the larger volume of results?
    your help much appreciated
    DUMP BELOW*******
    Runtime Error          COMPUTE_BCD_OVERFLOW
    Except.                CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          11/20/2010 01:43:30
    Information on where terminated
    The termination occurred in the ABAP program "ZAPR004" in "SUB_ORD_NOT_DEL".
    The main program was "ZAPR004 ".
    The termination occurred in line 2192 of the source code of the (Include)
    program "ZAPR004"
    of the source code of program "ZAPR004" (when calling the editor 21920).
    The program "ZAPR004" was started as a background job.
    Job name........ "ZAPR004"
    Job initiator... "ME"
    Job number...... 01354700
    Processing was terminated because the exception "CX_SY_ARITHMETIC_OVERFLOW"
    occurred in the
    procedure "SUB_ORD_NOT_DEL" "(FORM)" but was not handled locally, not declared
    in the
    RAISING clause of the procedure.
    The procedure is in the program "ZAPR004 ". Its source code starts in line 1858
    of the (Include) program "ZAPR004 ".
    Source Code Extract
    Line
    SourceCde
    2162
    BINARY SEARCH.
    2163
    IF sy-subrc = 0.
    2164
                begin of change(2) -NSHAH 01/23/2008 CR#3394
    2165
                 Process of Converiosn shuld occur only if r_ekko-WAERS is not USD.
    2166
    IF r_ekko-waers <> 'USD'.
    2167
    PERFORM convert_to_usd_currency USING r_ekko-waers
    2168
    r_ekko-wkurs
    2169
    r_ekpo-netpr
    2170
    CHANGING lv_usd_netpr.
    2171
    ELSE.
    2172
    lv_usd_netpr = r_ekpo-netpr.
    2173
    ENDIF.
    2174
                end   of change(2) -NSHAH 01/23/2008 CR#3394
    2175
    2176
    IF r_ekpo-knttp = c_f. " Account asgnmnt = order
    2177
    r_po_nodel-account = r_po-aufnr.
    2178
    r_po_nodel-price   = lv_usd_netpr / r_ekpo-peinh. "r_ekpo-netpr. CR#3394
    2179
                  begin of insert(2) -NSHAH 01/26/2009 CR#3394
    2180
                  Calculating the total cost, which is Price/Unit(as above) * menge
    2181
    r_po_nodel-netwr = r_po_nodel-price * r_ekpo-menge.
    2182
                  end of insert(2) -NSHAH 01/26/2009  CR#3394
    2183
    r_po_nodel-knttp   = r_ekpo-knttp.  "++padelli.
    2184
    w_tot_io2 = r_ekpo-netpr + w_tot_io2.
    2185
    ENDIF.
    2186
    2187
    IF r_ekpo-knttp = c_k.  " Account asgnmnt = cost center
    2188
    r_po_nodel-account = r_po-kostl.
    2189
    r_po_nodel-price   = lv_usd_netpr / r_ekpo-peinh. "r_ekpo-netpr. CR#3394
    2190
                  begin of insert(3) -NSHAH 01/26/2009 CR#3394
    2191
                  Calculating the total cost, which is Price/Unit(as above) * menge
    >>>>>
    r_po_nodel-netwr = r_po_nodel-price * r_ekpo-menge.
    2193
                  end of insert(3) -NSHAH 01/26/2009  CR#3394
    2194
    r_po_nodel-knttp  = r_ekpo-knttp.  "++padelli.
    2195
    w_tot_rm2 = r_ekpo-netpr  + w_tot_rm2.
    2196
    ENDIF.
    2197
    2198
    IF r_ekpo-knttp = c_p.  " Account asgnmnt = WBS element
    2199
    2200
    CALL FUNCTION 'CONVERSION_EXIT_ABPSP_OUTPUT'
    2201
    EXPORTING
    2202
    input  = r_po-ps_psp_pnr
    2203
    IMPORTING
    2204
    output = r_po_nodel-account.
    2205
    2206
    IF r_po-vproz IS  NOT INITIAL.
    2207
    r_po_nodel-price = r_po-vproz / ( lv_usd_netpr / r_ekpo-peinh ). "r_ekpo-n
    2208
    ELSE.
    2209
    r_po_nodel-price =  lv_usd_netpr / r_ekpo-peinh. "r_ekpo-netpr. CR#3394
    2210
    ENDIF.
    2211
                  begin of insert(4) -NSHAH 01/26/2009 CR#3394
    Edited by: Joe Whitty on Nov 21, 2010 7:21 AM

    Hi Joe,
    if you format it as code, it might be readable
    |>>>>>| r_po_nodel-netwr = r_po_nodel-price * r_ekpo-menge. | |
    is where the overflow occurs.
    I guess, this is a data problem, does not look like release-dependent.
    Try to catch the error and output the data:
    TRY.
      r_po_nodel-netwr = r_po_nodel-price * r_ekpo-menge.
    catch cx_root.
      message E(nnn) 'error with'  r_po_nodel-price   r_ekpo-menge.
    ENDTRY.
    You can also check the dump for global data values when error occurred, this may give you a hint.
    Regards,
    Clemens

  • Catching a runtime error

    Hi,
    A runtime error for overflow (type p) occurs with the following details:
    Runtime Errors         COMPUTE_BCD_OVERFLOW    
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          06/12/2007 11:33:13     
    Instead of displaying the dump screen, i'd like to catch the runtime error and display a message instead. The following is the code that causes the error (onhand is too large):
          REQRMENT = FORECAST - ONHAND - OPENQTY.
    Please help,
    Points will be rewarded and all help will be greatly appreciated.
    Thanks,
    John

    According to help, these are the catchable exceptions for a form call:
    Catchable Exceptions
    CX_SY_PROGRAM_NOT_FOUND
    Cause: The specified program was not found.
    Runtime Error: LOAD_PROGRAM_NOT_FOUND
    Cause: The specified program cannot exist because the program name is longer than 40 characters.
    Runtime Error: PERFORM_PROGRAM_NAME_TOO_LONG
    CX_SY_DYN_CALL_ILLEGAL_FORM
    Cause: The specified subroutine was not found.
    Runtime Error: PERFORM_NOT_FOUND
    Cause: The specified index was too small.
    Runtime Error: PERFORM_INDEX_0
    Cause: The specified index was negative.
    Runtime Error: PERFORM_INDEX_NEGATIVE
    Cause: The specified index was too large.
    Runtime Error: PERFORM_INDEX_TOO_LARGE
    CX_SY_DYN_CALL_PARAM_MISSING
    Cause: The called FORM expects more parameters than were specified.
    Runtime Error: PERFORM_PARAMETER_MISSING
    CX_SY_DYN_CALL_PARAM_NOT_FOUND
    Cause: More parameters were specified than expected by FORM.
    Runtime Error: PERFORM_TOO_MANY_PARAMETERS
    CX_SY_DYN_CALL_ILLEGAL_TYPE
    Cause: In the parameter transfer using the addition STRUCTURE, the addressing offsets/> do not match in the current and target structures.
    Runtime Error: PERFORM_BASE_WRONG_ALIGNMENT
    Cause: The deep components contained in the current and target structures cannot be passed to each other. This error can only occur in parameter transfer using STRUCTURE.
    Runtime Error: PERFORM_CAST_DEEP_MISMATCH
    Cause: During the transfer of a generically defined type to the form, a type conflict occurred.
    Runtime Error: PERFORM_CONFLICT_GENERIC_TYPE
    Cause: The table type of the current parameter does not match the table type of the parameter defined in the form.
    Runtime Error: PERFORM_CONFLICT_TAB_TYPE
    Cause: The type of current parameter does not match the type of parameter defined in the form.
    Runtime Error: PERFORM_CONFLICT_TYPE
    Cause: The current parameter occupies less storage space than the target parameter defined in the form. This error occurs only with parameter specification using STRUCTURE.
    Runtime Error: PERFORM_PARAMETER_TOO_SHORT
    Cause: During parameter transfer with the addition STRUCTURE, the fragment views of the current and target parameters do not match. This error only occurs in Unicode programs in
    Runtime Error: PERFORM_CONFLICT_UC_STRUCT
    Cause:When the form is called, an internal table is expected as current parameter.
    Runtime Error: PERFORM_TABLE_REQUIRED
    Cause: A hash table was passed to a parameter defined using TABLES.
    Runtime Error: PERFORM_STD_TAB_REQUIRED

  • Runtime Error Purchasing BI Content initial setup

    Hi all,
    I'm trying to setup Purchasing BI Content and i have the dump error during the initial setup in T-Code "OLI3BW" Statistical setup of info structures from purchasing documents.
    "Runtime Errors COMPUTE_BCD_OVERFLOW
    Except. CX_SY_ARITHMETIC_OVERFLOW
    Short text
    Overflow during the arithmetical operation (type P) in program "SAPLMCEX02"."
    Thanks.

    Hi,
    Check
    SAP notes: 1165576 and  1176819
    Thanks
    Reddy

  • MRN9 runtime error

    Hi,
       kindly suggest me a OSS  NOTE  on this runtime error.  Points will be rewarded for the appropriate suggestion.
    Runtime Errors         COMPUTE_BCD_OVERFLOW                                                         Except.                CX_SY_ARITHMETIC_OVERFLOW                                                    Date and Time          21.12.2007 12:31:23                                                                               
    Short text                                                                               
    Overflow during the arithmetical operation (type P) in program "RMNIWE90_01".                
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "RMNIWE90_01" had to be terminated because it has                   
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                       
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                     
        The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not               
         caught in                                                                               
    procedure "WERTE_BERECHNEN" "(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:                                                             
        An overflow was discovered in an ongoing arithmetical operation with                         
        operands of type P. Possible causes are:                                                                               
    1. The result field of type P is too small for the result.                                                                               
    2. The result or a intermediate result has more than 31 decimal places.                      
    How to correct the error                                                                               
    The result field must be enlarged, if this is still possible. It may                         
        also be possible to break up the current process into subprocesses so                        
        that only smaller values occur.                                                                               
    If the error occurred in your own ABAP program or in an SAP                                  
        program you modified, try to remove the error.                                                                               
    There may already be a solution to the error in the SAP notes system.                        
        If you have access to the SAP notes system first try searching with the                      
        following keywords:                                                                               
    "COMPUTE_BCD_OVERFLOW"                                                                               
    "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this               
         position)                                                                               
    "RMNIWE90_01" or "RMNIWE90_01"                                                              
         "WERTE_BERECHNEN"                                                                               
    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                               
        "WERTE_BERECHNEN" "(FORM)", or its possible occurrence must be declared in the               
        RAISING clause of the procedure.                                                             
        To prevent the exception, note the following:                                      
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "RMNIWE90_01" - in "WERTE_BERECHNEN".               
        The main program was "RMNIWE90_01 ".                                                                               
    In the source code you have the termination point in line 805                                
        of the (Include) program "RMNIWE90_01".                                                      
        The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"                      
         occurred in                                                                               
    procedure "WERTE_BERECHNEN" "(FORM)", but it was neither handled locally nor                 
         declared                                                                               
    in the RAISING clause of its signature.                                                                               
    The procedure is in program "RMNIWE90_01 "; its source code begins in line                   
        797 of the (Include program "RMNIWE90_01 ".                                                  
    Source Code Extract                                                                               
    Line
    SourceCde                                                                               
    775
       niwe_preis_p = niwe_preis.                                                               
      776
       max_preis_p = max_preis.                                                                 
      777
       IF niwe_preis_p >= max_preis_p.                                                          
      778
         no_price = x.                                                                               
    779
       ENDIF.                                                                               
    780
                                                                                    781
    *------- Fortschreiben Materialpreise -
      782
       PERFORM mryf_material_price_update USING s_mry_mt08y      "note865204                    
      783
                                                space            "note865204                    
      784
                                                no_price                                        
      785
                                                space.                                          
      786
                                                                                    787
    *------- Commit Work -
      788
       IF com_work = x.                                                                               
    789
         PERFORM mryf_commit_work USING comstamp.                                               
      790
       ENDIF.                                                                               
    791
                                                                                    792
    ENDFORM.                    "update_mbew                                                   
      793
    *eject                                                                               
    794
      795
      FORM WERTE_BERECHNEN                                              *                    
      796
      797
    FORM werte_berechnen.                                                                      
      798
                                                                                    799
    *------- Preis aus Matstamm ermitteln -
      800
       lbkum = s_mry_mt08y-stlbk.                                                               
      801
       salk3 = s_mry_mt08y-stsal.                                                               
      802
       IF s_mry_mt08y-stvpr = 'S'.                                                              
      803
         preis = s_mry_mt08y-ststp * bwpei / s_mry_mt08y-stpei.                                 
      804
       ELSE.                                                                               
    >>>>>
         preis = s_mry_mt08y-stver * bwpei / s_mry_mt08y-stpei.                                 
      806
       ENDIF.                                                                               
    807
                                                                                    808
    *------- Negative Bestände ignorieren -
      809
       IF sniwe9-noneg = x.                                                                     
      810
         IF lbkum < 0.                                                                               
    811
           lbkum = 0.                                                                               
    812
           salk3 = 0.                                                                               
    813
         ENDIF.                                                                               
    814
       ENDIF.                                                                               
    815
                                                                                    816
    *------- Bilanzwerte initialisieren -
      817
       CLEAR: wert1, wert2, wert3, wert4, wert5, wert6.                                         
      818
       CLEAR: preis1, preis2, preis3, preis4, preis5, preis6.                                   
      819
       noval1 = noval2 = noval3 = noval4 = noval5 = noval6 = x.                                 
      820
       bwert = max_wert.                                                                        
      821
       bpreis = max_preis.                                                                      
      822
       LOOP AT seq.                                                                               
    823
         CASE seq-step.                                                                               
    824
           WHEN '1'.                                                                        
    Thanks and Regards,
    SKUMAR.

    There should not any need of SAP Note for this.
    This could be because of the wrong value passing to the field which is of type P.
    Check the value of the field and correct it and execute it again. This is surely work.
    Reward if it is useful.
    Thanks,
    Srinivas

  • Getting Runtime error while executing Query on Multiprovider

    Hi ALL,
    When i m executing a query on multiprovider it is giving me runtime error as:
    *Error Reading the data of the infoprovider
    An Exception with the type CX_SY_ARITHMATIC_OVERFLOW occured
    overflow in the operation.*
    I ran this query today morning also it ran successfully, now it is giving this error.
    Please help me.
    Thank you.
    REDDY

    Hi check
    http://sap.ittoolbox.com/groups/technical-functional/sap-basis/sapsys-000-compute_int_times_overflow-cx_sy_arithmetic_overflow-1704462
    Thanks
    Reddy

  • Runtime Errors: COMPUTE_INT_MINUS_OVERFLOW

    Dear experts:
        When I execute a program which was developed by ours ABAPer, the runtime error will happen.
    The detail error information as follows (error happens in program "LSTXBCTB3" at 010730):
    Runtime Errors         COMPUTE_INT_MINUS_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    010640       endloop.
    010650       if sy-subrc = 0.
    010660         append l_otfline to l_lastinfo.
    010670       endif.
    010680   * get corrected value for l_blockpos: should be the position
    010690   * set by the command of 'positioning' (last in the block).
    010700
    010710   * look for 'last' ST command
    010720       l_index = l_blockend.
    010730       while l_flag eq c_true.
         >         l_index = l_index - 1.
    010750         read table p_cell_otf into l_otfline index l_index.
    010760         if l_otfline-tdprintcom <> pc_id_codepage    and
    010770            l_otfline-tdprintcom <> pc_id_call_font   and
    010780            l_otfline-tdprintcom <> pc_id_space_width and
    010790            l_otfline-tdprintcom <> pc_id_uline       and
    010800            l_otfline-tdprintcom <> pc_id_color_text  and
    010810            l_otfline-tdprintcom <> pc_id_move_to     and
    010820            l_otfline-tdprintcom <> pc_id_md_after_par.
    010830
    010840            l_flag = c_false.
    010850          endif.
    010860       endwhile.
    Anyone who can help me to solve the problem? Thanks a million!
    Edited by: Guo Qing Wu on Dec 17, 2007 8:49 AM
    Edited by: Guo Qing Wu on Dec 17, 2007 8:54 AM
    Edited by: Guo Qing Wu on Dec 17, 2007 8:55 AM
    Edited by: Guo Qing Wu on Dec 17, 2007 8:57 AM

    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
    was neither
    caught nor passed along using a RAISING clause, in the procedure
    "TAB_SPLIT_CELL" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    In the current program "SAPLSTXBC ", subtracting the number 1 from
    the number "-2147483648" (using the operation - or 'SUBTRACT') resulted
    in a value either greater than 2147483647 or smaller than
    -2147483648. This results in a whole number overflow.
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "TAB_SPLIT_CELL"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    You may be able to split the process into separate components, so that
    the values generated are smaller.
    If the error occurred in one of your own programs or in an SAP program
    that you modified, try to correct it yourself.
    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.............. "620"
    Application server....... "yihai-appl1"
    Network address.......... "10.10.10.161"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 80686"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 4
    Short dump setting....... "full"
    Database server.......... "DB-YIHAI"
    Database type............ "MSSQL"
    Database name............ "PRD"
    Database owner........... "prd"
    Character set............ "Chinese_CHN.936"
    SAP kernel............... "620"
    Created on............... "Dec 19 2004 22:59:44"
    Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
    Database version......... "SQL_Server_7.00 "
    Patch level.............. "1773"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "620"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    User, transaction...
    Client.............. 888
    User................ "ZHANGLUWEI"
    Language key........ 1
    Transaction......... "ZSD136 "
    Program............. "SAPLSTXBC "
    Screen.............. "ZDIA_SD_KERRY_DO 0601"
    Screen line......... 25
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLSTXBC " in "TAB_SPLIT_CELL".
    The main program was "ZDIA_SD_KERRY_DO ".
    The termination occurred in line 1074 of the source code of the (Include)
    program "LSTXBCTB3 "
    of the source code of program "LSTXBCTB3 " (when calling the editor 10740).
    Processing was terminated because the exception "CX_SY_ARITHMETIC_OVERFLOW"
    occurred in the
    procedure "TAB_SPLIT_CELL" "(FORM)" but was not handled locally, not declared
    in the
    RAISING clause of the procedure.
    The procedure is in the program "SAPLSTXBC ". Its source code starts in line
    897
    of the (Include) program "LSTXBCTB3 ".
    Source code extract
    010440             append l_otfline to l_lastinfo.
    010450             exit.
    010460           endif.
    010470           if l_otfline-tdprintcom = pc_id_call_font.
    010480             exit.
    010490           endif.
    010500         endloop.
    010510       endif.
    010520   *   find last UL command
    010530       loop at p_cell_otf into  l_otfline
    010540                          to    l_blockend
    010550                          where tdprintcom = pc_id_uline.
    010560       endloop.
    010570       if sy-subrc = 0.
    010580         append l_otfline to l_lastinfo.
    010590       endif.
    010600   *   find last CT command
    010610       loop at p_cell_otf into  l_otfline
    010620                          to    l_blockend
    010630                          where tdprintcom = pc_id_color_text.
    010640       endloop.
    010650       if sy-subrc = 0.
    010660         append l_otfline to l_lastinfo.
    010670       endif.
    010680   * get corrected value for l_blockpos: should be the position
    010690   * set by the command of 'positioning' (last in the block).
    010700
    010710   * look for 'last' ST command
    010720       l_index = l_blockend.
    010730       while l_flag eq c_true.
         >         l_index = l_index - 1.
    010750         read table p_cell_otf into l_otfline index l_index.
    010760         if l_otfline-tdprintcom <> pc_id_codepage    and
    010770            l_otfline-tdprintcom <> pc_id_call_font   and
    010780            l_otfline-tdprintcom <> pc_id_space_width and
    010790            l_otfline-tdprintcom <> pc_id_uline       and
    010800            l_otfline-tdprintcom <> pc_id_color_text  and
    010810            l_otfline-tdprintcom <> pc_id_move_to     and
    010820            l_otfline-tdprintcom <> pc_id_md_after_par.
    010830
    010840            l_flag = c_false.
    010850          endif.
    010860       endwhile.
    010870
    010880       if l_otfline-tdprintcom = pc_id_string.
    010890   *   find last MT or MB command
    010900         loop at p_cell_otf into l_otfline
    010910                            to l_index
    010920                            where tdprintcom = pc_id_move_to or
    010930                                  tdprintcom = pc_id_md_after_par.
    Contents of system fields
    SY field contents..................... SY field contents.................
    SY-SUBRC 4                             SY-INDEX -2147483641
    SY-TABIX 0                             SY-DBCNT 0
    SY-FDPOS 3                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY MAIN2000
    SY-UCOMM PREV                          SY-TITLE KerryÒÔ¶Ô·½Îª×¼·½°¸ÊµÏÖ
    SY-MSGTY                               SY-MSGID
    SY-MSGNO 000                           SY-MSGV1
    SY-MSGV2                               SY-MSGV3
    SY-MSGV4
    Active calls / events
    No.... Type........ Name..........................
           Program
           Include                                  Line
           Class
        17 FORM         TAB_SPLIT_CELL
           SAPLSTXBC
           LSTXBCTB3                                 1074
        16 FORM         TAB_SPLIT_LINE_OTF
           SAPLSTXBC
           LSTXBCTB3                                  681
        15 FORM         TAB_END_ROW
           SAPLSTXBC
           LSTXBCTB2                                  510
        14 FORM         TAB_ROW_END
           SAPLSTXBC
           LSTXBCTB2                                  109
        13 FUNCTION     SSFCOMP_TABLE_ROW_END
           SAPLSTXBC
           LSTXBCU44                                    9
    12 FORM         %EV2
        /1BCDWB/SAPLSF00000039
        /1BCDWB/LSF00000039F01                    1133
    11 FORM         %WI3_BODY
        /1BCDWB/SAPLSF00000039
        /1BCDWB/LSF00000039F01                     688
    10 FORM         %WI3
        /1BCDWB/SAPLSF00000039
        /1BCDWB/LSF00000039F01                     645
      9 FORM         CALLBACK
        SAPLSTXBC
        LSTXBCFDC                                  258
      8 FORM         PROCESS_PAGES
        SAPLSTXBC
        LSTXBCFDC                                  220
      7 FUNCTION     SSFCOMP_PROCESS_DOCUMENT
        SAPLSTXBC
        LSTXBCU03                                  106
      6 FUNCTION     /1BCDWB/SF00000039
        /1BCDWB/SAPLSF00000039
        /1BCDWB/LSF00000039U01                     375
      5 FORM         SMART_PRINT
        ZDIA_SD_KERRY_DO
        ZINC_SD_KERRY_DO_0601                      168
      4 MODULE (PAI) TC_0601_USER_COMMAND
        ZDIA_SD_KERRY_DO
        ZINC_SD_KERRY_DO_0601                       87
      3 FORM         LOAD_DO_NO61
        ZDIA_SD_KERRY_DO
        ZINC_SD_KERRY_DO_0601                       51
      2 MODULE (PAI) PAI_2000
        ZDIA_SD_KERRY_DO
        ZINC_SD_KERRY_DO_MAIN                      533
      1 EVENT        END-OF-SELECTION
        ZDIA_SD_KERRY_DO
        ZINC_SD_KERRY_DO_MAIN                       34
    sen variables
    17 FORM         TAB_SPLIT_CELL
    Is it enough? Thanks a lot for your great help.

  • Runtime error : COMPUTE_INT_PLUS_OVERFLOW

    Hi sap experts .
    when i run md01(mrp run), i have this error:
    Runtime Errors         COMPUTE_INT_PLUS_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
      caught in
    procedure "DATE_TIME_CONVERT" "(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:
    In the current program "SAPLCXTP",
    using '+' or 'ADD' to add the values 2147472000 and 30041 resulted in a
    value greater than 2147483647 or smaller than -2147483648. This
    leads to a whole number overflow.
    CAN YOU HELP ME TO SOLVE IT PLEASE.
    THANKS.

    Hi
    you have got this error because of the system limit of data types, you may have probably used any data type in which , it crosses the maximum of the system alloted limit for that data type.
    Please rectify your data type you have used in your program for calculating date and time.
    Alternatively you have to apply suitable note to rectify this, i hope SAP Note 689242 and  1106062 will serve your purpose.
    If not then find any suitable SAP Note and apply it.

  • Runtime Errors : COMPUTE_INT_TIMES_OVERFLOW

    Hi All,
    While loading Query Runtime Stat delta I am geting
    Runtime Errors: COMPUTE_INT_TIMES_OVERFLOW
    Exception: CX_SY_ARITHMETIC_OVERFLOW
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
         caught in
        procedure "DETERMINE_RUNTIME_CATEGORY" "(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:
        *In the current program "CLRSTCT_BIRS_EXTRACTION======CP", multiplying the*_
         numbers 4 and
        1000000000 (using the operation '' or 'MULTIPLY') resulted in a value*
        greater than 2147483647 or smaller than -2147483648. This
        results in a whole number overflow.
    Can you please help me out.
    Best Regards,
    Pratap Sone

    ...and adding more above my comments...
    Check your query definition might be cause below one of issue:
    1) After calculation the result might be more than SAP permitted. for example:  INT[EGER]: This data type is the same as FIXED(10.0). Its permitted values are between -  2147483648 and 2147483647.
    2) If an overflow occurs in an arithmetic operation or a division by 0 at another point.
    Cheers
    Sree

  • Conversion of planned order to production order resulting into Runtime error

    Hello Gurus
         I am trying to convert Planned order into production order in MD04,  but I am getting ABAP Runtime error; for details please see image here posted.
    Please help me to resolve the issue.
    Thanks in advance!
    # If anybody wants remote access of my system through Team viewer I am ready to share my desktop for same.
    Regards!
    AKSHAY

    Hi Akshay,
    Overflow during arithmetical operation type P COMPUTE_BCD_OVERFLOW comes when the maximum of the internal ABAP field that is 99,999,999,999.99 many be quantity, cost value UoM conversion etc.
    Please check how this UOM (unit of measure) is defined in transaction CUNI. In this transaction, you may have set the Value-based commitment indicator. This indicator controls whether commitments for the chosen unit of measure are recorded on a quantity basis or a value basis.
    Please search OSS note for this dump and also raise this to OSS.
    Regards,
    R.Brahmankar

Maybe you are looking for