CONVT_OVERFLOW in SM66

Hello,
at use of SM66 we get a runtime error "CONVT_OVERFLOW" after some refreshes.
We implement Note 1560251, but the error is still there.
Has someone a suggestion?
OS: AIX 6.1 6100-05-01-1016
SAP: NW 7.02 ERP 605
Kernel: 720.90
regards
Ch.Fischer

Hi Christian,
we got exactly the same error:
OS: AIX 6100-02-02-0849
SAP: NW 7.02 ERP 605 Basis SP 07
Kernel: 720.96
There is another note, we had to implement both: 1560251 + 1554744
Then the issue was solved.
Best regards
Thomas

Similar Messages

  • Runtime Errors: CONVT_OVERFLOW while executing transaction sm66

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

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

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

  • Unable to kill a session in SM50 or SM66

    One of our developer was working on a program and there was a network failure.  When we got the network back the system shows the process is till running since 3 days. Tried to kill it from SM50 and SM66. 
    While logging in it is giving 3 options and even after selecting "Continue with this logon and end any other logons in system" its not ending that session.
    After we logon the program is running good.
    How to kill this session??
    Details of the session is given below
    No Ty. PID      Status  Reasn Start Err Sem CPU      Time   Cl. User
    3  DIA 6584     Running       No            296:36   168191 130 BYARLAGADDA
    Report / Spool action
    CL_ABAP_TABLEDESCR============CP
    Main Program
    SAPLCV110
    Action                    Table
    Waiting f.                                                                   since
    Database                         Number              Time (usec)         Recs.
    Direct Read                    14,681             519,103                 524
    Sequential Read                18,146            595171                    83
    Insert                              0                   0                   0
    Update                              0                   0                   0
    Delete                              0                   0                   0

    Why does no-one understand SAP Architecture well enough anymore, I blame bad trainers.
    Its like seeing a car driving badly all over the road and blowing up the car rather than shooting the driver.
    The WP is not the problem, it is the task in the WP that is.
    Killing a user in SM04 or a job in SM37 often works. Then I would try cancelling the program in SM50, not the work process.
    If that fails then normally it is waiting on something - often RFC. If RFC a simple removal of the connection in SMGW removes the task from the WP. In this case it looks like a rogue DB process, in this case the WP is just waiting for a response from the DB... killing the WP just gets rid of the visibility in SM50, it does not remove the problem... in fact it then would make my job of identifying why the system is running slow a lot worse.

  • 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

  • Related to SM66

    Hi experts,
                  I have executed SM66 tcode. I have observed some work process details. Npw i would like to see those details in my report. I sthere any SAP Standard Function module for displaying that  information.
    Thanks
    Sasi

    Hi Gautham
               Thank you for the reply .  Can you please tell me for the FM " GWY_READ_WORKPROCESSES "  what input we should provide. The other FM which you have given is with out giving any input throughing results. But GWY_READ_WORKPROCESSES is not throghing any values. Please suggest me what input we should provide here.
    Thank you
    G.S.Naidu

  • Function module to display process overview log from SM66 Transaction

    Hi,
    I want to display process overview log from SM66 Transaction in a report.
    Is there a function module which will help me in achieving that or is there any other method.
    Thanks in advance,
    Sandeep.

    Did you try finding out how SM66 creates the list? You could set break-points e.g. at statement "call function" and see which ones are being called. Look at those starting with TH... especially.
    Thomas

  • Sequential read in sm66 - Database size 550GB - system slow for users

    Hello,
    Currently when we use any standard transactions  or custom program, it is going to sequential read in sm66.
    We are getting slowness in system due to this issue for users.
    Sm66 log:
    sapXX01_XXX_00  0  DIA     12873 Running            Yes                  6 XIRFC    ZCL_WM_S Sequential Read MARD
    sapXX01_XXX_00 20  BTC     16155 Running            Yes                 15 Zuser1  ZCL_SD_D Sequential Read LTAP
    sapXX01_XXX_00 29  SPO     12018 Running            Yes                 12 Zuser1   print 35
    sapXX01_XXX_00 30  SPO     12037 Running            Yes                 12 Zuser1   print 35
    sapXX01_XXX_00 31  SPO     12041 Running            Yes                 12 SAPSYS   querying
    sapXX02_XXX_02  3  DIA     15098 Running            Yes                714 Zuser2  ZCL_IM_B
    sapXX02_XXX_02  4  DIA      8158 Running            Yes                 38 Zuser2  RWRPLPRO Sequential Read WRPL
    sapXX02_XXX_02  6  DIA      8160 Running            Yes                555 Zuser3  ZCL_IM_B
    sapXX03_XXX_03  0  DIA      1969 Running            Yes               2390 Zuser5 SAPLFAGL Sequential Read BSIS
    sapXX03_XXX_04  0  BTC     10811 Running            Yes                209 Zuser6   ZCL_SD_D Sequential Read LTA
    Database: Maxdb
    OS: Linux
    I understand that if you create Index on these table ( whichever it shows as sequential read ), it will improve the report performance.
    Most of the time, system process shows that sequential read on VBAP, VKPA (sales tables), purchase tables, Finance tables and etc.
    If sm66 shows as sequential read for few table, that means that corresponding user will get slowness on getting report/transaction output. I agree on that.
    Is there any reason other user will get slowness ie if i run Va03 transaction, WE02 transaction which is not relevant to sm66 process over view.
    I appreciate, if you give some recommendations reg. this performance improvement and to avoid this kind of sequential read.
    I posted the Same question in DB forum also.
    I want to get some more idea from this forum also. That is reason, i posted here again.
    Thanks
    Praba

    Hi Volker,
    Thanks for your reply.
    We have three application server instance ie 00, 02, 03,   -
    04 (enque server)
    1) This parameter value on 00 instance ie : rdisp/wp_no_spo -  Number of spool work processes
    Dflt value - 0
    ProfileVa - 1
    Current value - 1
    Minimum - Nothing
    Maximum - 100
    2) his parameter value on 02 instance ie : rdisp/wp_no_spo -  Number of spool work processes
    Dflt value - 0
    ProfileVa - 1
    Current value - 1
    Minimum - Nothing
    Maximum - 100
    3) his parameter value on 03 instance ie : rdisp/wp_no_spo -  Number of spool work processes
    Dflt value - 0
    ProfileVa - 1
    Current value - 1
    Minimum - Nothing
    Maximum - 100

  • Process in SM66

    Hi,
    I see BW process chain showing a process node in Yellow, SM37 for the same says job is finished.
    I want to see corresponding job in R/3.
    How to find the corresponding job in tcode SM66.

    go to sm37, double click on your job and then choose job details; the next popup will give you all the info to find the corresponding process in sm66. however, if the job has finished you will not find any corresponding process. you might want to check SM58. maybe you have LUW stuck. if this is the case execute them manually. you can also check BD87 to see if any idoc is still in status 64. these idocs are hanging and need to be reprocessed.
    M.

  • 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

  • Debugging not possible in SM66 t-code

    Dear All,
    I created infinite loop in the program.
    I executed the program in 2 ways:
    1. Direct execute the program (SE38).
       I can see the process in SM66.
       I choose that record and click the debugging button, ABAP Debugger is come out and i can debug my code.
    2. I call that program in background or from other system using RFC.
        I Can see the process in SM66.
        I choose that record and click the debugging button, it said ABAP debugger started.. but nothing come out and i can't debug my program.
    Pls suggest why the 2nd way can't debug.
    Best Regards,
    Victor.

    okay.
    But is it possible to debug the program if the program is executed from other systems?
    i'm not sure about this.but we may debug by just putting endless loop(i tried this only when prg ran by my system only)

  • Convt_overflow error..

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

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

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

  • This is urgent please help!  long running job in sm37 but not in sm66

    Hi,
    Can someone please help for an explanation as to why if you call sm37, you can see that the job is long running (example about 70,000 sec), but when you look at the PID where the job is running in sm66 it does not show 70,000 sec but only around 6,000 sec.
    Can someone please explain why?  Thank you very much

    For background processes, additional information is available for the background job that is currently running. You can only display this information, if you are logged onto the instance where the job is running, or if you choose Settings and deselect Display only abbreviated information, avoid RFC. In any case, the job must still be running.
    Regards
    Anilsai

Maybe you are looking for

  • HELP: failed to setup and run WL performance monitor, console extension on WL 8.1

    Hi All i downloaded and installed the WL performance monitor, console extension package at http://commerce.bea.com/products/weblogicserverconsoleextension/wlsext_home.jsp As i tried to deploy "performance monitor" web app to the WL server at "Perform

  • Disable delete button in PO Modify transaction

    Hi I am new to SAP. I want certain user to prevent deleting PO line item in ME22N transaction (either by disabling delete button). Please let me know how go about it. thanks

  • Can open cr2 files but no thumbnails in Bridge

    I got no response in Bridge forum so I am trying here. I am trying to help a friend with Mac Snow Leopard OS but i am a Windows person so maybe I did something wrong. I downloaded and installed ACR 8.3. His 6D RAW files open fine in Photoshop CS6 but

  • How I can Talk to TOSHIBA Online

    How I can Talk to TOSHIBA Online Chat ! to Serve Me. I don't want to serve me in phone because some times I'm may not be in USA Solved! Go to Solution.

  • Where's the doc for MSI mode?

    Edit: I don't need an answer to this, I found the problem. Where can I find the doc to enable/disable it? it says it is "enabled by default", but my managed servers fail to start if the Admin Server is not running (the problem is in the ODSI AppListe