RM07DOCS_GENERATED Time_out

Dear All,
how about big issue Tcode MB51 with include RM07DOCS_GENERATED. we always attempt time out with big range selection in the field.
does anyone Know?
Regards,
Djeet

Dear,
is there any in english version? cause we're worry about the wrong interpretation
Regards
Djeet

Similar Messages

User WF_BATCH dumps with TIME_OUT for a background task

Hello,
Situation :
While executing a workflow with a task defined as background task, the workflow creates a dump in ST22 after around 40 minutes. dump is because of TIME_OUT exception. And the workflow stays in status InProcess forever.
Question:
In my opinion background tasks do not have a time limit because they are executed as backgound batch jobs with batch user WF_BATCH. Then why do I get a TIME_OUT error ?
Is my assumption that workflow background task are just handled like other background jobs (sm36) is wrong ?
More Details :
I have a workflow with a task defined as background task (Task -> Basic Data -> Execution -> Check box 'Background processing' selected).
This task calls a method defined as 'Synchronous' method.
This method calls a ABAP FM having a select statement which selects large volume of Data.
If I execute this FM in Dialog mode definately I get a TIME_OUT. I understand this.
But what I do not understand is , while executing in background I do not expect TIME_OUT error since background jobs do not have a time limit. They can even run for several days.
Please let me know in what cases does a background job throws a time_out exception.esp wrt workflow.
Thanks in Advance
Shivanand

Check this link.
http://mailman.mit.edu/pipermail/sap-wug/2003-April/008883.html
Thanks
Arghadip

TIME_OUT error while executing an ABAP report

Hi All,
I have an ABAP report in which the code looks like below
LOOP AT pernr_tab . " *Internal table consists of around 25k records*
   IF last_run_date IS INITIAL. " Initial Load
      PERFORM fill_data USING pernr_tab-pernr last_run_date CHANGING lv_flag.
      lv_flag = 'x'.
      initial_count = initial_count + 1.
    ELSE.
      PERFORM fill_data USING pernr_tab-pernr last_run_date CHANGING lv_flag.
      IF pernr_tab-status EQ '3' AND pernr_tab-begda GE today. " Future Hire records during delta load
        lv_flag = 'x'.
      ENDIF.
      IF lv_flag EQ 'x'.
        delta_change_count = delta_change_count + 1.
      ENDIF.
    ENDIF.
    IF lv_flag = 'x'. "initial load or changes in some infotype for delta load
      PERFORM append_data.
      CLEAR: p0000_tab[],p0000,p0001_tab[],p0001,p0002_tab[],p0002,p0006_tab[],p0006,p0006_phone,
p0007_tab[],p0007,p0027_tab[],p0027,p0032_tab[],p0032,p0105_tab_usr[],p0041_tab[],p0041.
      CLEAR: p0105_usr,p0105_tab_ven[],p0105_ven,p0105_tab_mgr[],p0105_mgr,p0709_tab[],p0709,pos_id,
functional_title,p0521_tab[],p0521,p2001_tab[],p2001,corporate_band_code,corporate_title_code,wa_pernr_tab.
    ENDIF.
ENDLOOP.
inside the loop i am fetching data from 10 different infotypes and adding into another internal table.When I execute this program it is giving TIME_OUT error.Is there any way i can resolve this issue(I dont want to run this program in the background)
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on Jul 13, 2010 8:25 AM
Edited by: Thomas Zloch on Jul 13, 2010 4:58 PM - line width reduced

fill_data
reading 10 infotypes
call function 'HR_READ_INFOTYPE'
exporting
*     TCLAS                 = 'A'
    pernr                 = p_pernr_tab_pernr
    infty                 = '0000'
   begda                 = '18000101'
   endda                 = '99991231'
*   bypass_buffer         = 'X'
tables
    infty_tab             = p0000_tab
exceptions
   infty_not_found       = 1
   others                = 2
if sy-subrc <> 0.
endif.
if p0000_tab[] is not initial.
    sort p0000_tab by endda descending.
    read table p0000_tab into p0000 index 1.
    if p0000-aedtm ge last_run_date.
      lv_flag = 'X' ." Infotype 0 has been changed
    endif.
endif.
append_data
assigning 50 different fields from above infotypes to ls_emp_data
ls_emp_data-functional_title = functional_title.
ls_emp_data-last_update = today.
if ( p2001-awart = '5006' and p2001-begda <= today and p2001-endda >= today ) or
( p0521-atzph = 'AB' AND p0521-begda <= today AND p0521-endda >= today ).
    ls_emp_data-absent = text-007.
ELSE.
    ls_emp_data-absent = text-008.
ENDIF.
ls_emp_data-corporate_band_code = corporate_band_code.
ls_emp_data-corporate_title_code = corporate_title_code.
APPEND ls_emp_data TO lt_emp_data.
CLEAR:ls_emp_data,lv_flag.
Thanks
Bala Duvvuri
Edited by: Thomas Zloch on Jul 14, 2010 2:48 PM - code tags added

TIME_OUT in ST22 while loading data

Hello all!
While I load data from ODS-object to an InfoCube, after around 18 minutes I have the first TIME_OUT in ST22. Some seconds later I have the next and then again after 18 minutes and so on. All the time while loading. The loading doesn´t stop.
I found the following statement in ST22:
The program "GP2GCXJX3UPKBEN0B528IGJFPA3 " has exceeded the maximum permitted runtime and has therefore been terminated.
But loading is still running.
This programm is the programm which is generated from the update rules which can be found in the update rules under ->Extras ->Display Activated Programm in the menu there.
I found also the information in ST22 that "rdisp/max_wprun_time" is 1000 seconds (16.66 minutes) which is the max. runtime. I think there is a second chance so the max. runtime should be 2000 seconds.
But I think "rdisp/max_wprun_time" is a parameter for dialog processes and loading over InfoPackage isn´t one as far as I know.
I load as a backround process. I´m loading from ODS and reading in update rules from 2 other ODS-objects. I read around 2 million records. Another IC which is very similar but doesn´t read from the 2nd ODS needs around 1 and a half hour to load.
Can someone please help me?
Thank you,
Peter

Peter,
Update rules are processed in foreground and the time out setting applies to all dialog processes. The processing is done one data packet at a time.
If the load is from ODS to InfoCube and is timing out then there is no option but to tune the update rules. Bring down the records that are being read. If your select statement is reading based on the contents of the data packet, then bring down the size of the data packet. THis can be done in the InfoPack in Scheduler --> DataS. Default Data Transfer. In the Max size field try 10000 or even 5000. Number of data pakckets will increase but processing time per packet should be lower.
Another option is to find the ODS PSA request in the PSA Tree. ODS PSA Request number is the request number right before the REQU number in the ODS requests tab. They begin with ODSR.... Find this in the PSA and update to data target from there. This processing is then done in the background and the time out setting does not apply.
If you do not see the request then turn on display generated object from the menu of the admin workbench Settings --> Display Generated Objects
Cheers
Aneesh

Short Dump due to TIME_OUT Error

Hi,
We have a situation here, where the monthly data from R/3 is extracted to ODS (Full upload) and subsequently getting uploaded to infocube (Delta). Usually the ODS to infocube updation takes long hours of time (say 8 hours), because of complexity of the update rules over the cube and this was working fine for the past months.
But on 1st of this month when I extracted R/3 data went fine upto ODS, but failed in the further process (i.e., ODS to Infocube) resulting in a short dump. Extract is shown below
Short dump in the Warehouse
Diagnosis
The data update was not completed. A short dump has probably been logged in BW providing information about the error.
System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
So I want to try out with another option, Since we know the data coming to ODS on a monthly basis, instead of pushing the data to infocube in delta mode, can I upload the data using full update (but of course weekly wise) to cube ?.
What will be the complications?.
Please guide with your ideas
Thanks in advance,
Arun.

System response
"Caller 70" is missing.
Further analysis:
Search in the BW short dump overview for the short dump belonging to the request. Pay attention to the correct time and date on the selection screen.
You get a short dump list using the Wizard or via the menu path "Environment -> Short dump -> In the Data Warehouse".
Did you follow this recommendation? Did you check the short dump?
If it is really a time_out issue, the short dump will tell you so, but there can also be other causes for caller 70 missing.
It is a time_out you can either increase your time out setting, or decrease the package size in your infopackages;
kr,
Tom

Time_Out when running transaction S_ALR_87100205

All ,
Whenever we are trying to execute the transaction S_ALR_87100205 it is giving us runtime TIME_OUT error.
The error is occuring at SELECT...ENDSELECT statements.
Please provide your valuable feedbacks or SAP notes to resolve this urgent problem.
The dump analysis from TX ST22 is :-
Time limit exceeded.
What happened?
The program "SAPDBBRF " has exceeded the maximum permitted runtime
and has therefore been terminated.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
After a certain time, the program terminates to free the work process
for other users who are waiting.
This is to stop work processes being blocked for too long by
- Endless loops (DO, WHILE, ...),
- Database acceses with large result sets,
- Database accesses without an apporpriate index (full table scan)
- database accesses producing an excessively large result set,
The maximum runtime of a program is set by the profile parameter
"rdisp/max_wprun_time".
The current setting is 2700 seconds. After this, the system gives the
program a second chance. During the first half (>= 2700 seconds), a
call that is blocking the work process (such as a long-running SQL
statement) can occur. While the statement is being processed, the
database layer will not allow it to be interrupted. However, to
stop the program terminating immediately after the statement has been
successfully processed, the system gives it another 2700 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
How to correct the error
Long-running programs should be started as background jobs. If
this is not possible, you can increase the value of the system
profile parameter "rdisp/max_wprun_time".
One or more of the following may also be useful:
following measures:
- Endless loops: Correct in program;
- Database access with large result set:
Use "SELECT * INTO itab" instead of "SELECT ... ENDSELECT";
- Database access without suitable index: Check the index generation.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPDBBRF " in
"PUT_BKPF".
The main program was "RFHABU00N ".
The termination occurred in line 1023
of the source code of program "SAPDBBRF " (when calling the editor 10230).
Source code extract
009930             PERFORM T001_READ.
009940   *         expiring currencies:
009950             GD_WAERS_SAVE = BKPF-WAERS.
009960             IF NOT GD_EXPCUR_FLAG IS INITIAL.
009970               PERFORM ITEM_CURR_CONVERT_BKPF USING    'SAPDBBRF'
009980                                                       SY-DATLO
009990                                              CHANGING BKPF.
010000             ENDIF.
010010
010020             PUT BKPF.
010030           ENDIF.
010040
010050   *------- Belegkoepfe lesen, Positionen einzeln dazu -
010060         ELSE.
010070           SELECT (BKPF_FIELDS) FROM BKPF INTO
010080            CORRESPONDING FIELDS OF BKPF
010090             WHERE BUKRS IN BR_BUKRS
010100             AND   BLART IN BR_BLART
010110             AND   BUDAT IN BR_BUDAT
010120             AND   XBLNR IN BR_XBLNR
010130             AND   BELNR IN BR_BELNR
010140             AND   GJAHR IN BR_GJAHR
010150             AND   BSTAT IN BR_BSTAT
010160             AND   AWTYP IN BR_AWTYP
010170             AND   AWKEY IN BR_AWKEY
010180             AND   AWSYS IN BR_AWSYS
010190             AND   CPUDT IN BR_CPUDT
010200             AND   BLDAT IN BR_BLDAT
010210             AND   USNAM IN BR_USNAM
010220             AND   (BKPF_WHERE)
            ORDER BY PRIMARY KEY.
010240             IF BKPF-BSTAT EQ 'D'.
010250               SELECT SINGLE * FROM BKDF
010260                 WHERE BUKRS EQ BKPF-BUKRS
010270                 AND   BELNR EQ BKPF-BELNR
010280                 AND   GJAHR EQ BKPF-GJAHR.
010290             ENDIF.
010300             SAVE_BUKRS = BKPF-BUKRS.
010310             SAVE_BELNR = BKPF-BELNR.
010320             SAVE_GJAHR = BKPF-GJAHR.
010330             CNT_BKPF = CNT_BKPF + 1.
010340             B0SG-XARBL = SPACE.
010350             PERFORM T001_READ.
010360   *         expiring currencies:
010370             GD_WAERS_SAVE = BKPF-WAERS.
010380             IF NOT GD_EXPCUR_FLAG IS INITIAL.
010390               PERFORM ITEM_CURR_CONVERT_BKPF USING    'SAPDBBRF'
010400                                                       SY-DATLO
010410                                              CHANGING BKPF.
010420             ENDIF.
Active calls / events
No.... Type........ Name..........................
       Programm
       Include                                  Line
     1 FORM         PUT_BKPF
       SAPDBBRF
       SAPDBBRF                                  1023
     2 FORM         PUT_BOSG
       SAPDBBRF
       SAPDBBRF                                   675
     3 FORM         %_ROOT
       SAPDBBRF
       SAPDBBRF                                  3502
     4 EVENT        SYSTEM-EXIT
       RFHABU00N
                                           25
Regards,
AD

Thanks for your valuable inputs Rob, but will the transaction FBL3N solve the purpose of the user .
Can you guys suggest me any transaction which can become a work around for the same.
Regards,
Amitanshu

TIME_OUT error while executing a Z program

Hi,
We are executing a Z report based on the input field "Dispatched on" (Z date type)
which is resulting in a runtime error.We have already created Indexes for the table CRMD_ORDERADM_H and
CRMD_ORDER_INDEX.
Runtime Errors         TIME_OUT
Date and Time          20.07.2010 14:27:20
Short text
Time limit exceeded.
What happened?
The program "SAPLCRMBSVA" has exceeded the maximum permitted runtime without
|    interruption and has therefore been terminated.
Any suggestions?
Regards,
PP

Hi,
timeout time could be changed in a RZ11 profile parameter.
I´m not sure which one it is in your case.
Kind regards
Manfred

TIME_OUT when opening a report

Dear SDN BI Team,
When i am opening workbook it giving error message ***
(1) Error reading the data of info provider xxxxx
(2) system error: time limit excceeded
(3) messages for data source xxxxxx from source system xxxxxxx
(4) errors occurred during parallel processing of query 3,RC: 3
(5) error reading data;navigation is possible
I tried opening the report in RSRT,given variable values but the query is not opening.
In ST22 we have log of TIME_OUT
Runtime Errors         TIME_OUT
Date and Time          01.04.2010 17:11:01
Short text
     Time limit exceeded.
"TIME_OUT" " "
"CL_RSTCT_BIRS_OLAP_AGGR_EX====CP" or "CL_RSTCT_BIRS_OLAP_AGGR_EX====CM00A"
"FILTER_STEPUIDS"
Thanks and Kind Regards,
Lakshman Kumar G

Hi Lakshman,
Do your query alot of data from the infoprovider that is the source of the workbook/query?
If yes this could be the problem, that you try and query too much data, if you try with a
smaller data selection does the problem also happen?
If the problem relates to the Technical content please make sure that the note 1317483
has been applied in your system.
Best Regards,
Des

TIME_OUT error with /sapapo/rtsinput_cube

We are in the process of cutting over to a new
planning area ZPA2 with data from a backup InfoCube
(ZIC21), and the /sapapo/rtsinput_cube program
is failing with a TIME_OUT error.
The overall job finishes with a success message,
although data is only partially loaded in to the
planning area. When you look at the spool, the first
steps are green, then the job times out for the
subsequent steps.
We ran this first with 3 key figures being loaded
from cube to planning area for approx 1/5 of 464000
CVCs for 5 years in monthly buckets only.
This errored with SAPSQL_INVALID_FIELDNAME message as
well as the TIME_OUT error message, and data was
loaded partially in the ZPA2 planning area (only 2
months).
We then reduced the time horizon from 5 years of
months to be only 1 year in months.
This errored with the TIME_OUT error message. Again,
data was partially loaded in to the planning area
(about 7 of the 12 months was loaded).
The prime issue is with the constant time out.
Has anyone any idea how to solve this problem ?

not sure what version you are using but if you are on the latesr versions, its a good idea to use parallel processing - you can find it on the additonal settings tab
you can also set it to copy only the specified period (previously it copied the whole bucket in the planning area to cover the time period)
if you are in versions that dont support this - then you can create parallel jobs that get triggered by an event or use a process chain and run this in parallel. As long as you dont overlap the periods it should be fine
you should also ask your basis team to check the time out set up for the application and get it extended (you can see this in rz11 i think and choosing the correct parameter - would leave it to the basis folks to help in this) Alternately check your processing power and see if you can get it increased

TIME_OUT error while trying to execute a report

Hi all,
When I try to exceute a Z report using a particular variant, it displays the output.
However, when another person tries to run the same Z report using the same variant, it gives a TIME_OUT error.
ABAP runtime errors TIME_OUT
Time limit exceeded.
Please let me know the reason for this.
Thanks and regards,
Anishur

Hi Anishur,
Is the TIME OUT occuring on the same client as you are running the report? And if so, does the user have the same authorisation as you? The TIME OUT will occur if the program is handling more data, if you are seeing different performance it will be down to the amount of data process.
As others have suggested, look at improving the performance of the report.
Regards,
Nick

BI 7.01 BEx report/workbok Time_Out Errors

Hi,
Our BEx reports/workbooks are failing with time_out error's. Below are the time_out error details: BEx workbooks are executed through VB Script.
Some days they run fine and some days they time_out.
The program "CL_RSDRH_HIER_CACHE===========CP" has exceeded the maximum
permitted runtime without
interruption and has therefore been terminated.
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" " "
"CL_RSDRH_HIER_CACHE===========CP" or "CL_RSDRH_HIER_CACHE===========CM00D"
"ADD_MEM"
Other time_out error's as below:
1) The program "SAPLRSDRC_SPLIT" has exceeded the maximum permitted runtime
without
interruption and has therefore been terminated.
Termination occurred in the ABAP program "SAPLRSDRC_SPLIT" - in "SELAGGR_GET2".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 1101
of the (Include) program "LRSDRC_SPLITF01".
2) The program "CL_RSDRH_HIER_CACHE===========CP" has exceeded the maximum
permitted runtime without
interruption and has therefore been terminated.
Termination occurred in the ABAP program "CL_RSDRH_HIER_CACHE===========CP" -
in "CHECK".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 80
of the (Include) program "CL_RSDRH_HIER_CACHE===========CM001".
3) The program "SAPLRSDRC_SPLIT" has exceeded the maximum permitted runtime
without
interruption and has therefore been terminated.
Termination occurred in the ABAP program "SAPLRSDRC_SPLIT" - in
"SELDR_TO_AGGROBJ".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 214
of the (Include) program "LRSDRC_SPLITF01".
4) The program "SAPLSENA" has exceeded the maximum permitted runtime without
interruption and has therefore been terminated.
Termination occurred in the ABAP program "SAPLSENA" - in "FLUSH_PACKAGE".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 229
of the (Include) program "LSENAF01".
Recently we have increased the parameter "rdisp/max_wprun_time" from 5400 to 7200 Seconds.
Pl. advise.

Hello,
I think this is quite easy.
Execute the report SAP_DROP_TMP_TABLES (via SE38 transaction) and the issue should be solved.
For more details, see notes 698280 and 1139396.
Let me know if persist.
Best Regards,
Edward John

Runtime Errors TIME_OUT

guyz,
i am facing the below issue while running DTP to load the master data attr to info object.
previoulsy it was working perfect but from last few days its getting hanged and throwing this error.
also records are very few around 2500.
dont know why its getting hanged.
Runtime Errors         TIME_OUT
Date and Time          10/04/2011 16:35:09
Short text
     Time limit exceeded.
What happened?
     The program "SAPLSENA" 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 600 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" " "
    "SAPLSENA" or "LSENAF01"
    "FLUSH_PACKAGE"
    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.
also sometimes when i try to refresh the requests in the manage option of the info object, it doesnt show the previous requests and throws the message
Refresh of the display terminated because InfoCube/DSO cannot be locked
Message no. RSM854
Diagnosis
InfoProvider 0PROD_CATEG cannot be locked with lock argument RSICCONT.
System Response
The display is not refreshed and contains old or incorrect data, that can come from other InfoProviders.
Procedure
Check why the sm12 lock is not yet released on the table RSICCONT; Where necessary delete the lock.
With reproduction of an unauthorized lock, write a message to SAP.
please guide.
cheerz,
raps.

Dear Raps,
The program SAPLSENA is the lock handler tool. It is doing
enqueue/dequeue operations.
The error should come from the program created running in this dialog
process and calls the SAPLSENA program to create the lock.
The problem actually occurs because an application program commits many
separate calls of DEQUEUE function modules, and thus causes the
dispatcher queue in the enqueue dispatcher to overflow. Such an
application program always causes a performance problem. DEQUEUE calls
are started asynchronously, that is, they normally do not give a
response, and the calling program continues without waiting time.
If an overflow of the ENQ dispatcher queue occurs in this case, locks
are kept forever, and processes that are waiting for an enqueue
response, will keep hanging.
Please kindly refer to some notes for more information.
653996     Analyzing lock situations
142054     Processes in status stopped ENQ
97760      Enqueue: Performance and resource consuption
74141      Resource Management for tRFC and aRFC
39412      How many work processes to configure
Please check as well attached note 74141 for RFC load distribution.
Regards,
arvind

TIME_OUT in VK13 / VK33 on IDES system

We are receiving the following timeout when running VK13 and VK33 on our IDES system. This is standard code, and there is no notes regarding this TIME_OUT.
The Termination occurred in the ABAP program "SAPLV12A" - i
"ACCESS_REPORT_GENERATE".
The main program was "SAPMV13A ".
The whole ST22 dump is as follows:
Runtime Errors         TIME_OUT
Date and Time          18.08.2010 19:35:25
     Short text
          Time limit exceeded.
     What happened?
          Error analysis
          If you have access to SAP Notes, carry out a search with the following
          keywords:
          "TIME_OUT" " "
          "SAPLV12A" or "LV12AU07"
          "ACCESS_REPORT_GENERATE"
     System environment
          SAP-Release 700
          Application server... "sap6ides"
          Network address...... "10.3.3.125"
          Operating system..... "Windows NT"
          Release.............. "5.2"
          Hardware type........ "2x AMD64 Level"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 3
          Shortdump setting.... "full"
          Database server... "sapC10ides"
          Database type..... "ADABAS D"
          Database name..... "C10"
          Database user ID.. "SAPC10"
          Char.set.... "C"
          SAP kernel....... 700
          created (date)... "May 22 2007 00:12:17"
          create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
          Database version. "SQLDBC 7.6.0.035 CL 139084 "
          Patch level. 111
          Patch text.. " "
          Database............. "MaxDB 7.6, MaxDB 7.7"
          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...... 16759360
          Heap.... 0
          Page.... 2342912
          MM Used. 4880016
          MM Free. 3496816
     User and Transaction
          Client.............. 800
          User................ "MEASLE"
          Language key........ "E"
          Transaction......... "VK13 "
          Program............. "SAPLV12A"
          Screen.............. "SAPMV13A 0100"
          Screen line......... 24
     Information on where terminated
          Termination occurred in the ABAP program "SAPLV12A" - in
           "ACCESS_REPORT_GENERATE".
          The main program was "SAPMV13A ".
          In the source code you have the termination point in line 177
          of the (Include) program "LV12AU07".
     Source Code Extract
     Line     SourceCde
       147                   dff_desc_ref_field = dd08v_tab-reffldname
       148                 EXCEPTIONS
       149                   OTHERS             = 1.
       150               IF sy-subrc NE 0.
       151                 CLEAR: dd08v_tab-txttabname,
       152                        dd08v_tab-reffldname,
       153                        dd08v_tab-txtfldname.
       154               ENDIF.
       155     * und aufnehmen
       156               READ TABLE dd08v_tab WITH KEY tabname = dd08v_tab-tabname
       157                                             fieldname = dd08v_tab-fieldname
       158                                             TRANSPORTING NO FIELDS.
       159               IF sy-subrc EQ 0.
       160                 MODIFY dd08v_tab INDEX sy-tabix
       161                        TRANSPORTING txttabname reffldname txtfldname
       162                                     arbgb msgnr.
       163               ELSE.
       164                 APPEND dd08v_tab.
       165               ENDIF.
       166               LOOP AT dd05m_tab WHERE
       167                 tabname = t681-kotab AND fieldname = xt681e_tab-sefeld.
       168
       169                 READ TABLE dd03v_tab INDEX dd05m_tab-primpos.
       170                 IF sy-subrc = 0 AND dd03v_tab-datatype NE 'CLNT'.
       171                   MOVE-CORRESPONDING dd05m_tab TO dd05v_sel.
       172                   dd05v_sel-forfldname = dd03v_tab-fieldname.
       173                   IF dd08v_tab-reffldname IS INITIAL.
       174                     dd05v_sel-reffldname = dd03v_tab-fieldname.
       175                   ELSE.
       176                     TABLES dd05p.
     >>>>>                     SELECT * FROM dd05p
       178                     WHERE tabname = dd08v_tab-txttabname
       179                      AND   fieldname = dd08v_tab-reffldname
       180                      AND   checktable = dd08v_tab-checktable
       181                      AND   checkfield = dd03v_tab-fieldname.
       182                       dd05v_sel-reffldname = dd05p-forkey.
       183                       EXIT.
       184                     ENDSELECT.
       185                     IF sy-subrc = 4.
       186                       dd05v_sel-reffldname = dd08v_tab-reffldname.
       187                     ENDIF.
       188                   ENDIF.
       189                   APPEND dd05v_sel.
       190                 ENDIF.
       191               ENDLOOP.
       192             ENDIF.
       193             IF NOT dd08v_tab-txttabname IS INITIAL AND
       194                NOT dd08v_tab-txtfldname IS INITIAL.
       195     * Fremdtabelle lesen (Text)
       196               CALL FUNCTION 'RV_TABLE_READ'
                       2
             0
             0
             0

>           Database version. "SQLDBC 7.6.0.035 CL 139084 "
You seem to use a VERY OLD MaxDB database software.
I suggest:
- Update your MaxDB to a recent release, the version you use is very old.
- Update your database statistics to make sure the access paths for the data is optimal
- check the database parameters against Note 814704 - MaxDB Version 7.6 parameter settings for OLTP/BW
If you still use the default settings that came with the installation then it's rather obvious why your system is so slow.
Markus

Getting time_out Error in report bcos of SQL Statement!

Hi Experts,
I am getting Time_out error in my big program because of Select statement.I have checked in SQL Trace AND fuond the message
"SQL0104N An unexpected token "vakey" was found following "umh
kschl". Expected tokens may include: ",". SQLSTATE=42601"
I have given the following code and SQL statement where the error is getting occured.Please help.
TYPES: BEGIN OF ty_vakey1,
           vakey TYPE vakey,
         END OF ty_vakey1,
         ty_t_vakey1 TYPE HASHED TABLE OF ty_vakey1 WITH UNIQUE KEY vakey.
DATA: ih_vakey1 TYPE ty_t_vakey1,
        wa_vakey1 TYPE ty_vakey1,
        wa_vakey TYPE ty_vakey.
LOOP AT i_vakey INTO wa_vakey.
    wa_vakey1-vakey = wa_vakey-vakey.
    COLLECT wa_vakey1 INTO ih_vakey1.
    CLEAR wa_vakey1.
ENDLOOP.
IF ih_vakey1 IS NOT INITIAL.
Here it is required to select the Key field and so cannot be used in Where condition
    SELECT knumh                                             "Condition record number
           kschl                                             "Pricing conditions
           vakey                                             "Variable Key
           datab                                             "Valid-From Date
           datbi                                             "Valid To Date
           FROM konh
           INTO TABLE i_konh
           FOR ALL ENTRIES IN ih_vakey1
           WHERE vakey EQ ih_vakey1-vakey .           "#EC CI_NOFIELD
Here #EC CI_NOFIELD is used because the key field of the table konh ( ie knumh)
is to be selected and so is not used in the WHERE condition above
    IF sy-subrc NE c_0.
No data found for specified criteria
      MESSAGE i036.
      LEAVE LIST-PROCESSING.
    ENDIF.
Thanks&Regards,
Sarkar

Check if i_konh definition matches the fields in the SELECT statement.
Also, since you're not using the primary key when selecting from KONH table, such program by design is going to run forever and may time out eventually. Usually KONH is a very large table. Not sure what's the purpose of this program, but I'm pretty sure there must be some other way to program this. There are actually some standard FMs that read the conditions.
A secondary index might help, but only as a last resort.

TIME_OUT runtime error for Zreport in only Production server.

Hi Experts,
                 I have created one new Zreport which is working well in Development & Quality Server for given input. but same report is giving run time error in Production server for same input resulting into error TIME_OUT. Short text of error is Time limit exceeded.
                Please provide me solution for the same.
                Thanks in advance.
Best Regards,
Vinayak

Moderator message - Please see Please Read before Posting in the Performance and Tuning Forum before posting - post locked

RM07DOCS_GENERATED Time_out

Similar Messages

Maybe you are looking for