11 Replies Latest reply: Aug 27, 2010 12:21 PM by Harsh Saxena RSS

High execution time for running report s_alr_87013558,CJI3

sanjiv sinha
Currently Being Moderated

Dear experts,

 

when I am trying to generate the report through T code s_alr_87013558 it is either taking too much time or showing dump error.

 

even if we are trying to generate the report after checking the required fields in DB profile , it is taking too much time.

 

please any body can help us in generating the report faster.

 

Thanks and Regards

sanjiv

  • Re: High execution time for running report s_alr_87013558,CJI3
    Venu V
    Currently Being Moderated

    Hi,

     

    Can you post error log here.

     

     

    Vemula

  • Re: High execution time for running report s_alr_87013558,CJI3
    Harsh Saxena
    Currently Being Moderated

    Hi,

     

    Is the dump showing you arithmetic overflow or is dump due to time exceed?

     

    Regards,

    Harsh.

     

    Edited by: Harsh Saxena on Aug 27, 2010 11:32 AM

  • Re: High execution time for running report s_alr_87013558,CJI3
    Gokulkrishnan Pillai
    Currently Being Moderated

    Hi,

     

    Try using dynamic selections and status selection profile and revert.

     

    Regards,

    Gokul

  • Re: High execution time for running report s_alr_87013558,CJI3
    sanjiv sinha
    Currently Being Moderated

    Hi,

     

    As desired following is the error , some time it takes around 3-4 hrs for getting the report generated

     

    Runtime Errors         TIME_OUT                                                                    

    Date and Time          25.08.2010 11:31:57                                                                               

    Short text                                                                               

    Time limit exceeded.                                                                          

     

    What happened?                                                                               

    The program "SAPLXCN1" has exceeded the maximum permitted runtime without                     

        interruption and has therefore been terminated.                                                                               

    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                                                                               

    After a specific time, the program is terminated to make the work area                        

        available to other users who may be waiting.                                                  

        This is to prevent a work area being blocked unnecessarily long by, for                       

        example:                                                                               

    - Endless loops (DO, WHILE, ...),                                                             

        - Database accesses with a large result set                                                   

        - Database accesses without a suitable index (full table scan)                                                                               

    The maximum runtime of a program is limited by the system profile                             

        parameter "rdisp/max_wprun_time". The current setting is 1800 seconds. If this                

         time limit is                                                                               

    exceeded, the system attempts to cancel any running SQL statement or                          

        signals the ABAP processor to stop the running program. Then the system                       

        waits another 60 seconds maximum. If the program is then still active,                        

        the work process is restarted.                                                                

     

    How to correct the error                                                                               

    Programs with long runtime should generally be started as background                          

        jobs. If this is not possible, you can increase the system profile                            

        parameter "rdisp/max_wprun_time".                                                                               

    Depending on the cause of the error, you may have to take one of the                          

        following measures:                                                                               

    - Endless loop: Correct program;                                                              

        - Dataset resulting from database access is too large:                                        

          Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table                      

          (for example);                                                                               

    - Database has unsuitable index: Check index generation.                                                                               

    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:                                                                               

    "TIME_OUT" " "                                                                               

    "SAPLXCN1" or "ZXCN1U07"                                                                      

        "EXIT_SAPLCNAU_003"                                                                               

    exceeding 15000 length characters                                                                               

    thanks and best of regards

    sanjiv sinha

  • Re: High execution time for running report s_alr_87013558,CJI3
    sanjiv sinha
    Currently Being Moderated

    Hi Gokul,

     

    Tried using dynamic selection and changing the db profile still taking too much time or dump error

     

    Thanks and regards

    sanjiv

  • Re: High execution time for running report s_alr_87013558,CJI3
    sanjiv sinha
    Currently Being Moderated

    Hi Harsh,

     

    This is coming for single project and it has around 500 wbs in it.

     

    Thanks and Regards

    sanjiv

  • Re: High execution time for running report s_alr_87013558,CJI3
    Venu V
    Currently Being Moderated

    Hi,

     

     

    Why don't you consult your technical consultant (ABAP) regarding this performance issue, he can debug the programe and might advise you the sort of solution.

     

    And also you can try relevent OSS notes in Service market Place where you can get any help full inormation on note corrections.

     

     

    Vemula

  • Re: High execution time for running report s_alr_87013558,CJI3
    sanjiv sinha
    Currently Being Moderated

    Hi Harsh,

     

    it is showing last authorization was successful , with a tick before that

     

    Thanks and regards

    sanjiv sinha

Actions