Time Out error : Its urgent

Hi ,
The scenario is that I am running a Process chain in which there is a loading process . In that process if data loading takes more than 1 hour it gives time out error . in ST22 , but in Sm37 it is active. Moreover in scheduler , the time is set to 2 hrs.
What is happening ? can any one please explain . what should I do to get rid of time out error ? can we set time in update rule as in scheduler ?
Please help me ...

Hi Rajib,
In your case even if you set the time out time in scheduler it takes the default work process settings. Which you can see in the Parameter rdisp/max_wprun_time
at RZ10 transaction and select Instance profile. Even if the job is in active in sm37 it doesn't progress further when there is a timeout recorded. Try to get intouch with you BASIS guys and get the parameter settings to 2 hours. which may require server reboot.
Hope it helps.
Regards,
Srikanth.

Similar Messages

Time out error in report - Urgent

Hi Gurus,
   Am developing the report for GL Account summary from tables bkpf, bseg. Due to lot of records in production server it is coming time out error. Please help me regarding this here am attaching my code.
REPORT ZFBLREPORT.
*TABLES : zgltax.
TYPE-POOLS : SLIS.
TYPES : BEGIN OF TY_ZGLTAX,
        ZGL TYPE BSEG-HKONT,
        ZTAX1 TYPE P DECIMALS 2,
        ZTAX2 TYPE P DECIMALS 2,
        CAMOUNT TYPE RF42B-SALDO,
        PAMOUNT TYPE RF42B-SALDO,
        TCAMOUNT TYPE RF42B-SALDO,
        TPAMOUNT TYPE RF42B-SALDO,
        END OF TY_ZGLTAX.
TYPES : BEGIN OF TY_BKPF,
        BELNR TYPE BKPF-BELNR,
        BUDAT TYPE BKPF-BUDAT,
        END OF TY_BKPF.
TYPES : BEGIN OF TY_BSEG,
        BELNR TYPE BSIS-BELNR,
        DMBTR TYPE BSIS-DMBTR,
        SHKZG TYPE BSIS-SHKZG,
        HKONT TYPE BSIS-HKONT,
        BUDAT TYPE BSIS-BUDAT,
        BUZEI TYPE BSIS-BUZEI,
        END OF TY_BSEG.
DATA : IT_FINAL TYPE STANDARD TABLE OF TY_ZGLTAX,
       WA_FINAL TYPE TY_ZGLTAX.
DATA : IT_BKPF TYPE STANDARD TABLE OF TY_BKPF,
       WA_BKPF TYPE TY_BKPF.
DATA : IT_BSEG TYPE STANDARD TABLE OF TY_BSEG,
       WA_BSEG TYPE TY_BSEG.
DATA: CAMOUNT TYPE RF42B-SALDO,
      PAMOUNT TYPE RF42B-SALDO.
DATA : INDEX TYPE SY-INDEX.
DATA : ID TYPE SY-TABIX.
DATA : START_DATE TYPE SY-DATUM.
DATA : END_DATE TYPE SY-DATUM.
DATA : START_QUATER TYPE SY-DATUM.
DATA : YEAR1(4) TYPE C.
DATA       : T_FIELDALV     TYPE SLIS_T_FIELDCAT_ALV.
DATA       : IMPORT_VARIANT LIKE DISVARIANT.
DATA       : XREPID         LIKE SY-REPID.
DATA       : LAYOUT         TYPE SLIS_LAYOUT_ALV.
SELECTION-SCREEN BEGIN OF BLOCK BK1 WITH FRAME TITLE TEXT-001.
PARAMETER : P_PERIOD(1) TYPE C OBLIGATORY,
            P_YEAR(4) TYPE C OBLIGATORY.
SELECTION-SCREEN END OF BLOCK BK1.
AT SELECTION-SCREEN ON P_PERIOD.
IF P_PERIOD > '4' OR P_PERIOD < '1'.
    P_PERIOD = ''.
    MESSAGE 'Enter Correct Quater Period' TYPE 'E'.
ENDIF.
START-OF-SELECTION.
PERFORM CALC_DATE.
PERFORM BUILD_LOGIC.
PERFORM INITIAL_ALV_FIELDCAT CHANGING T_FIELDALV[].
PERFORM LAYOUT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM     = SY-REPID
      I_GRID_TITLE           = 'FBT Report'
     i_callback_top_of_page = 'FORM_TOP_PAGE'
     it_sort                = p_sort
      IS_LAYOUT              = LAYOUT
      IT_FIELDCAT            = T_FIELDALV[]
      I_SAVE                 = 'A'
    TABLES
      T_OUTTAB               = IT_FINAL.
*&      Form calc_date
      text
--> p1        text
<-- p2        text
FORM CALC_DATE .
IF P_PERIOD = '1'.
    CONCATENATE P_YEAR '04' '01' INTO START_DATE.
    CONCATENATE P_YEAR '04' '01' INTO START_QUATER.
    CONCATENATE P_YEAR '06' '30' INTO END_DATE.
ELSEIF P_PERIOD = '2'.
    CONCATENATE P_YEAR '04' '01' INTO START_DATE.
    CONCATENATE P_YEAR '07' '01' INTO START_QUATER.
    CONCATENATE P_YEAR '09' '30' INTO END_DATE.
ELSEIF P_PERIOD = '3'.
    CONCATENATE P_YEAR '04' '01' INTO START_DATE.
    CONCATENATE P_YEAR '10' '01' INTO START_QUATER.
    CONCATENATE P_YEAR '12' '31' INTO END_DATE.
ELSEIF P_PERIOD = '4'.
    CONCATENATE P_YEAR '04' '01' INTO START_DATE.
    YEAR1 = P_YEAR + 1.
    CONCATENATE YEAR1 '01' '01' INTO START_QUATER.
    CONCATENATE YEAR1 '03' '31' INTO END_DATE.
ENDIF.
ENDFORM.                    " calc_date
*&      Form build_logic
      text
--> p1        text
<-- p2        text
FORM BUILD_LOGIC .
SELECT * FROM ZGLTAX INTO CORRESPONDING FIELDS OF TABLE IT_FINAL.
IF IT_FINAL[] IS NOT INITIAL.
    LOOP AT IT_FINAL INTO WA_FINAL.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          INPUT = WA_FINAL-ZGL
        IMPORTING
          OUTPUT = WA_FINAL-ZGL.
      INDEX = SY-TABIX.
       SELECT belnr dmbtr shkzg hkont budat buzei
      SELECT *
      FROM BSIS
      INTO CORRESPONDING FIELDS OF TABLE IT_BSEG
      WHERE
      BUKRS = '3599' AND
         HKONT = WA_FINAL-ZGL
        AND GJAHR = P_YEAR.
Uses primary index (4.7)
      SELECT *
      FROM BSAS
      APPENDING CORRESPONDING FIELDS OF TABLE IT_BSEG
      WHERE
      BUKRS = '3599' AND
        HKONT = WA_FINAL-ZGL
        AND GJAHR = P_YEAR.
      LOOP AT IT_BSEG INTO WA_BSEG .
        IF WA_BSEG-BUDAT >= START_DATE AND WA_BSEG-BUDAT <= END_DATE.
          IF WA_BSEG-SHKZG = 'S'.
            CAMOUNT = CAMOUNT - WA_BSEG-DMBTR.
          ELSEIF WA_BSEG-SHKZG = 'H'.
            CAMOUNT = CAMOUNT + WA_BSEG-DMBTR.
          ENDIF.
        ENDIF.
        IF WA_BSEG-BUDAT >= START_QUATER AND WA_BSEG-BUDAT <= END_DATE.
          IF WA_BSEG-SHKZG = 'S'.
            PAMOUNT = PAMOUNT - WA_BSEG-DMBTR.
          ELSEIF WA_BSEG-SHKZG = 'H'.
            PAMOUNT = PAMOUNT + WA_BSEG-DMBTR.
          ENDIF.
        ENDIF.
      ENDLOOP.
      WA_FINAL-CAMOUNT = CAMOUNT.
      WA_FINAL-PAMOUNT = PAMOUNT.
      WA_FINAL-TCAMOUNT = CAMOUNT * WA_FINAL-ZTAX1 * WA_FINAL-ZTAX2 / (
100 * 100 ).
      WA_FINAL-TPAMOUNT = PAMOUNT * WA_FINAL-ZTAX1 * WA_FINAL-ZTAX2 / (
100 * 100 ).
      MODIFY IT_FINAL FROM WA_FINAL INDEX INDEX.
      REFRESH IT_BSEG.
    ENDLOOP.
ENDIF.
ENDFORM.                    " build_logic
*&      Form layout
      text
FORM LAYOUT .
LAYOUT-NO_SUBTOTALS = ' '.
ENDFORM.                    " LAYOUT
*&      Form initial_alv_fieldcat
      text
     -->FIELDCAT   text
FORM INITIAL_ALV_FIELDCAT CHANGING FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA : LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
DATA : CNTR TYPE I VALUE 1.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'ZGL'.
LS_FIELDCAT-SELTEXT_L = 'GL A/C NO'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO FIELDCAT.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'ZTAX1'.
LS_FIELDCAT-SELTEXT_L = 'BASE TAX PERCENTAGE'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO FIELDCAT.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'ZTAX2'.
LS_FIELDCAT-SELTEXT_L = 'TAX PERCENTAGE'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO FIELDCAT.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'CAMOUNT'.
LS_FIELDCAT-SELTEXT_L = 'CUMULATIVE AMOUNT'.
LS_FIELDCAT-OUTPUTLEN = 20.
APPEND LS_FIELDCAT TO FIELDCAT.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'TCAMOUNT'.
LS_FIELDCAT-SELTEXT_L = 'Cumulative Tax % Amount'.
LS_FIELDCAT-OUTPUTLEN = 20.
APPEND LS_FIELDCAT TO FIELDCAT.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'PAMOUNT'.
LS_FIELDCAT-SELTEXT_L = 'AMOUNT FOR PERIOD'.
LS_FIELDCAT-OUTPUTLEN = 20.
APPEND LS_FIELDCAT TO FIELDCAT.
CLEAR LS_FIELDCAT.
CNTR = CNTR + 1.
LS_FIELDCAT-COL_POS = CNTR.
LS_FIELDCAT-FIELDNAME = 'TPAMOUNT'.
LS_FIELDCAT-SELTEXT_L = 'Tax AMOUNT FOR PERIOD'.
LS_FIELDCAT-OUTPUTLEN = 20.
APPEND LS_FIELDCAT TO FIELDCAT.
ENDFORM.                    "initial_alv_fieldcat
Points will be awarded
Regards
Ravi

Hi Ravi kanth,
You are using select * statement which is very time consuming and low performance. Dont use select * instead use select field1 field2.... into table itab where field1 = s_field. Use corresponding field names in the select statement.
Follow the below rules.
1) Dont use nested select statements
2) If possible use for all entries in addition
3) In the where addition make sure you give all the primary key
4) Use Index for the selection criteria.
5) You can also use inner joins
6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.
7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly
<b>reward if useful</b>.
Regards,
sunil kairam.

Time out error in production server for alv grid report

hi. i have developed alv grid report using nested select statments. when i testing in development server it is giving the output but in production server if i give 4 months then it is showing time out error.please help me out..its urgent.
Thanks in advance.

Hi Manu,
Don't use Nested selected statements.
Use the Following Performance Tuning Options that i have given below so that your problem can be solved.
1) Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
2) Avoid for all entries in JOINS
3) Try to avoid joins and use FOR ALL ENTRIES.
4)   Try to restrict the joins to 1 level only ie only for tables
5)   Avoid using Select *.
6)   Avoid having multiple Selects from the same table in the same object.
7) Try to minimize the number of variables to save memory.
8)   The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
9)   Avoid creation of index as far as possible
10) Avoid operators like <>, > , < & like % in where clause conditions
11) Avoid select/select single statements in loops.
12) Try to use 'binary search' in READ internal table. Ensure table is sorted before using   BINARY SEARCH.
13) Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
14) Avoid using ORDER BY in selects
15) Avoid Nested Selects
16) Avoid Nested Loops of Internal Tables
17) Try to use FIELD SYMBOLS.
18) Try to avoid into Corresponding Fields of
19) Avoid using Select Distinct, Use DELETE ADJACENT
<b>
Reward Points for sure if you find it useful. </b>
Regards
Babu

Performance issue in Report (getting time out error)

Hi experts,
I am doing Performance for a Report (getting time out error)
Please see the code below and .
while looping internal table IVBAP after 25 minutes its showing time out error at this poit ->
SELECT MAX( ERDAT ) .
please send alternate code for this .
Advance thanks
from
Nagendra
Get Sales Order Details
CLEAR IVBAP.
REFRESH IVBAP.
SELECT VBELN POSNR MATNR NETWR KWMENG WERKS FROM VBAP
   INTO CORRESPONDING FIELDS OF TABLE IVBAP
     FOR ALL ENTRIES IN IVBAK
       WHERE VBELN = IVBAK-VBELN
       AND   MATNR IN Z_MATNR
       AND   WERKS IN Z_WERKS
       AND   ABGRU = ' '.
Check for Obsolete Materials - Get Product Hierarhy/Mat'l Description
SORT IVBAP BY MATNR WERKS.
CLEAR: WK_MATNR, WK_WERKS, WK_PRDHA, WK_MAKTX,
         WK_BLOCK, WK_MMSTA, WK_MSTAE.
LOOP AT IVBAP.
      CLEAR WK_INVDATE.                                   "I6677.sn
      SELECT MAX( ERDAT ) FROM VBRP INTO WK_INVDATE WHERE
      AUBEL EQ IVBAP-VBELN AND
      AUPOS EQ IVBAP-POSNR.
      IF SY-SUBRC = 0.
          MOVE WK_INVDATE TO IVBAP-INVDT.
          MODIFY IVBAP.
      ENDIF.                                               "I6677.e n
      SELECT SINGLE * FROM MBEW WHERE             "I6759.sn
      MATNR EQ IVBAP-MATNR AND
      BWKEY EQ IVBAP-WERKS AND
      BWTAR EQ SPACE.
      IF SY-SUBRC = 0.
         MOVE MBEW-STPRS TO IVBAP-STPRS.
         IVBAP-TOT = MBEW-STPRS * IVBAP-KWMENG.
         MODIFY IVBAP.
      ENDIF.                                      "I6759.en
    IF IVBAP-MATNR NE WK_MATNR OR IVBAP-WERKS NE WK_WERKS.
      CLEAR: WK_BLOCK, WK_MMSTA, WK_MSTAE, WK_PRDHA, WK_MAKTX.
      MOVE IVBAP-MATNR TO WK_MATNR.
      MOVE IVBAP-WERKS TO WK_WERKS.
      SELECT SINGLE MMSTA FROM MARC INTO MARC-MMSTA
        WHERE MATNR = WK_MATNR
        AND   WERKS = WK_WERKS.
      IF NOT MARC-MMSTA IS INITIAL.
        MOVE '*' TO WK_MMSTA.
      ENDIF.
      SELECT SINGLE LVORM PRDHA MSTAE MSTAV FROM MARA
        INTO (MARA-LVORM, MARA-PRDHA, MARA-MSTAE, MARA-MSTAV)
        WHERE MATNR = WK_MATNR.
      IF ( NOT MARA-MSTAE IS INITIAL ) OR
         ( NOT MARA-MSTAV IS INITIAL ) OR
         ( NOT MARA-LVORM IS INITIAL ).
         MOVE '*' TO WK_MSTAE.
      ENDIF.
      MOVE MARA-PRDHA TO WK_PRDHA.
      SELECT SINGLE MAKTX FROM MAKT INTO WK_MAKTX
        WHERE MATNR = WK_MATNR
          AND SPRAS = SY-LANGU.
    ENDIF.
    IF Z_BLOCK EQ 'B'.
      IF WK_MMSTA EQ ' ' AND WK_MSTAE EQ ' '.
        DELETE IVBAP.
        CONTINUE.
      ENDIF.
    ELSEIF Z_BLOCK EQ 'U'.
      IF WK_MMSTA EQ '' OR WK_MSTAE EQ ''.
        DELETE IVBAP.
        CONTINUE.
      ENDIF.
    ELSE.
      IF WK_MMSTA EQ '' OR WK_MSTAE EQ ''.
        MOVE '*' TO WK_BLOCK.
      ENDIF.
    ENDIF.
    IF WK_PRDHA IN Z_PRDHA.                                    "I4792
      MOVE WK_BLOCK TO IVBAP-BLOCK.
      MOVE WK_PRDHA TO IVBAP-PRDHA.
      MOVE WK_MAKTX TO IVBAP-MAKTX.
      MODIFY IVBAP.
    ELSE.                                                     "I4792
      DELETE IVBAP.                                           "I4792
    ENDIF.                                                    "I4792
    IF NOT Z_ALNUM[] IS INITIAL.                              "I9076
      SELECT SINGLE * FROM MAEX                               "I9076
        WHERE MATNR = IVBAP-MATNR                             "I9076
          AND ALNUM IN Z_ALNUM.                               "I9076
      IF SY-SUBRC <> 0.                                       "I9076
        DELETE IVBAP.                                         "I9076
      ENDIF.                                                  "I9076
    ENDIF.                                                    "I9076
ENDLOOP.

Hi Nagendra!
Get Sales Order Details
CLEAR IVBAP.
REFRESH IVBAP.
check ivbak is not initial
SELECT VBELN POSNR MATNR NETWR KWMENG WERKS FROM VBAP
INTO CORRESPONDING FIELDS OF TABLE IVBAP
FOR ALL ENTRIES IN IVBAK
WHERE VBELN = IVBAK-VBELN
AND MATNR IN Z_MATNR
AND WERKS IN Z_WERKS
AND ABGRU = ' '.
Check for Obsolete Materials - Get Product Hierarhy/Mat'l Description
SORT IVBAP BY MATNR WERKS.
CLEAR: WK_MATNR, WK_WERKS, WK_PRDHA, WK_MAKTX,
WK_BLOCK, WK_MMSTA, WK_MSTAE.
avoid select widin loop. instead do selection outside loop.u can use read statement......and then loop if required.
LOOP AT IVBAP.
CLEAR WK_INVDATE. "I6677.sn
SELECT MAX( ERDAT ) FROM VBRP INTO WK_INVDATE WHERE
AUBEL EQ IVBAP-VBELN AND
AUPOS EQ IVBAP-POSNR.
IF SY-SUBRC = 0.
MOVE WK_INVDATE TO IVBAP-INVDT.
MODIFY IVBAP.
ENDIF. "I6677.e n
SELECT SINGLE * FROM MBEW WHERE "I6759.sn
MATNR EQ IVBAP-MATNR AND
BWKEY EQ IVBAP-WERKS AND
BWTAR EQ SPACE.
IF SY-SUBRC = 0.
MOVE MBEW-STPRS TO IVBAP-STPRS.
IVBAP-TOT = MBEW-STPRS * IVBAP-KWMENG.
MODIFY IVBAP.
ENDIF. "I6759.en
IF IVBAP-MATNR NE WK_MATNR OR IVBAP-WERKS NE WK_WERKS.
CLEAR: WK_BLOCK, WK_MMSTA, WK_MSTAE, WK_PRDHA, WK_MAKTX.
MOVE IVBAP-MATNR TO WK_MATNR.
MOVE IVBAP-WERKS TO WK_WERKS.
SELECT SINGLE MMSTA FROM MARC INTO MARC-MMSTA
WHERE MATNR = WK_MATNR
AND WERKS = WK_WERKS.
IF NOT MARC-MMSTA IS INITIAL.
MOVE '*' TO WK_MMSTA.
ENDIF.
SELECT SINGLE LVORM PRDHA MSTAE MSTAV FROM MARA
INTO (MARA-LVORM, MARA-PRDHA, MARA-MSTAE, MARA-MSTAV)
WHERE MATNR = WK_MATNR.
IF ( NOT MARA-MSTAE IS INITIAL ) OR
( NOT MARA-MSTAV IS INITIAL ) OR
( NOT MARA-LVORM IS INITIAL ).
MOVE '*' TO WK_MSTAE.
ENDIF.
MOVE MARA-PRDHA TO WK_PRDHA.
SELECT SINGLE MAKTX FROM MAKT INTO WK_MAKTX
WHERE MATNR = WK_MATNR
AND SPRAS = SY-LANGU.
ENDIF.
IF Z_BLOCK EQ 'B'.
IF WK_MMSTA EQ ' ' AND WK_MSTAE EQ ' '.
DELETE IVBAP.
CONTINUE.
ENDIF.
ELSEIF Z_BLOCK EQ 'U'.
IF WK_MMSTA EQ '' OR WK_MSTAE EQ ''.
DELETE IVBAP.
CONTINUE.
ENDIF.
ELSE.
IF WK_MMSTA EQ '' OR WK_MSTAE EQ ''.
MOVE '*' TO WK_BLOCK.
ENDIF.
ENDIF.
IF WK_PRDHA IN Z_PRDHA. "I4792
MOVE WK_BLOCK TO IVBAP-BLOCK.
MOVE WK_PRDHA TO IVBAP-PRDHA.
MOVE WK_MAKTX TO IVBAP-MAKTX.
MODIFY IVBAP.
ELSE. "I4792
DELETE IVBAP. "I4792
ENDIF. "I4792
IF NOT Z_ALNUM[] IS INITIAL. "I9076
SELECT SINGLE * FROM MAEX "I9076
WHERE MATNR = IVBAP-MATNR "I9076
AND ALNUM IN Z_ALNUM. "I9076
IF SY-SUBRC 0. "I9076
DELETE IVBAP. "I9076
ENDIF. "I9076
ENDIF. "I9076
endloop.
U have used many select queries widin loop-endloop which is a big hindrance as far as performance is concerned.Avoid such practice.
Thanks
Deepika

Time Out Error in BPEL

Hi,
We are trying to invoke a Web Service from BPEL Process (10.1.3.3.0) and we received below time out error message in em console.
</part></Invoke_1_setJobPostingXML_InputVariable></input><fault><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Read timed out</summary>
Problem here is this error is not coming for all the invocation. For ex. We have posted the input payload at 3:15:34PM today and it thrown an error at 3:45:12 PM with above message. Also its not huge load hitting their server as we are calling the webservice once in 4-5 mins and if we repost the same message, its posting without any issue. This time out error comes 4-5 times daily and want to understand why it occurs everyday.
1. Will BPEL receive an error if we post huge payload to web service?
2. Do we need to set some waiting time to receive the response after posting the data to Web service?
3. Other possible scneario's for timeout error?
Thanks,
Saravana

Hi Saravana,
It's likely to be a problem at the remote side or a network latency/communication problem...
How can you affirm "its not huge load hitting their server"? Your service may not be the only source of load...
Cheers,
Vlad

HTTP time out Error in BPM.....

Hi
Error Description:
We have created a Sync-Async Bridge BPM scenario in XI.
In the BPM scenario we are calling the web service, and if the response from the web service is an error message then we have retry in a loop up to 24 times after wait for every 1 min.
We are sending the data to the web service using a proxy created in the R/3 system.
We are getting the time out error in the R/3 system.
We have changed the following parameters in XI.
In SXMB_ADM of XI we have set the value for the following parameter.
Category                      parameter                                                                    current value
SA_COMM                    CHECK_FOR_ASYNC_RESPONSE_TIMEOUT                120
In SXMB_ADM of R/3 we have set the value for the following parameter.
Category                      parameter                                                                    current value
RUNTIME                      HTTP_TIMEOUT                                                            120
When we put the value as 120 for the above parameters and we try for 2 times in the BPM process, then it is sending the response back to the R/3 system after completing the whole BPM process.
But when we increase the no of retries in the BPM process then it is not sending the response back to the R/3 system in the same way, at that time we are getting the error in SXMB_MONI of R/3 system as given below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
-   
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="500" p2="Timeout" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
<SAP:Text language="EN">HTTP status code 500 : Timeout</SAP:Text>
</SAP:ErrorHeader>
Please provide the solution for the same.
Many Thanks
Rinku Gangwani

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

How to avoid time out error in abap program

How to avoid time out error in abap program
based on performance wise i want please help

Timeout occurs when a statement exceeds its time limit.To avoid this we need to tune the statements.
I can give give you few tips for tune a select stament.
1.The order of the feilds in the select statement should be same as the order of fields in the database table.
2.It is always advisible to use the key fields when you are using the where clause.
3. Sort the internal table while using the for all entreis statements.
4.Use index in where clause if necessary.
5.When you have a read statement user binary search but before this a sort statement should be there.
6. Check your program with the Tcode ST05 and check which statement takes much time based on that tune that.

Time out error in receiver soap adapter

Hi,
My scenario is file to soap file with out BPM.I am using a currency converter wsdl.
I am getting a time out error in soap receiver channel.
Do i need to change the time out parameter?Where do i change that?Please help me to solve it out.
Following are the errors in the soap communication channel.
SOAP: call failed: java.net.ConnectException: Connection timed out
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out. Setting message to status failed.
Regards
Divia

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

Time out error in POWL query

Hello Experts,
The user selected Purchase Order ALL and ran the query with wild search, it contains around 40K POs showing in Active query list. When he wants to access these POs by cliking on hyper link ALL (40451). Its going to Time out error, because requestor number is missing.
Kindly throgh some light how to clear this filter.
Highly appreciated for prompt responses.
Regards,
Suneel Kumar

Hi Poonam Patil,
Try to provide BELNR and GJAHR in where condition...
BKPF-DBBLG ==> BSAK-BELNR
Also check
BKPF-BLDAT ==> BSAK-AUGDT
Check out above relation...
If data is there in these fields of the table and both are matching then you can pass it and as they are in primary key of BSAK it will improve the performance...
Hope it will solve your problem..
Thanks & Regards
ilesh 24x7
ilesh Nandaniya

TIME out error in MIRO

Hi Guys,
My FICO is running MIRO but is getting time out error.
The total no of line items in the PO are 2900.
He runs MIRO with set of 400 Line items everytime.I have increased the runtime for the WP but sometimes still it gives timeout.
I have checked the note no 1333601 but its for india specfic version & i m in UAE.
Is there a way to schedule this background.
thanks

Hi,
Thanks for the reply.
I have already asked them to reduce the line items to 200.
In SM50 there is no such information available. only the report name is available doesnt provide any information on the table that is being accessed.. I checked in SM66 also.
Since the data is availalble in PRD only so this occurs in this env only.
Could we schedule this MIRO process in background..?

Time out error in MIRO in prd , but takes times to Quality server

Hi all,
In the sap standard transaction MIRO, in Production while executive , time out error is coming in dump, while when i execute the same tranaction in Quality server, It takes 1 hrs time , but transaction is suceesful.
What would be the problem.
Thanks .
Lolo.

Amit Gujargoud wrote:>
> >
sekhar manda wrote:
> > Try after some time i think it won't goes to dump
>
> My motor bike is not giving good mileage. Okay I'll go inside my house and come back in few minutes. May be it will give me amazing mileage!
No need to go inside and come, just RESTART the bike, its just a typical software engineer's solution

Time out error in J1INQEFILE while generation ETDS file

hi,
when ever i am executing transaction J1INQEFILE. it giving Time out error. in dump folloeing message is coming.
Termination occurred in the ABAP program "J_1I_QER_EFILE" - in "MOVE_VENDOR".
The main program was "J_1I_QER_EFILE ".
In the source code you have the termination point in line 1410
of the (Include) program "J_1I_QER_EFILE_FETCH_DATA".
i checked in program. can you people tell me how to optimize this query after making this program as a Y program.so that this error can be avoided.
Thanks
SP

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

PERFORMANCE -TIME OUT ERROR (430) IN ESTABLISHING A DIALOGUE ASYNCHRONOUS

Hi all,
I have created a flow(program) and while executing the same program in the development server i am getting the desired output.
But when i execute the same program in the background mode (it fails in the foreground after 9 or 10 hrs giving the same error message) in the quality server, its giving time-out error 430 ( 00-430 TIME OUT IN ESTABLISHING A DIALOGUE ASYNCHRONOUS ).
Can someone explain me, what this error is all about.
It will be helpful,if you also teach me how to correct the same error.
NOTE : The DataBase tables being used in this program has fewer entries in the Development Server (in between 100 and 200 entries in each of the tables) whereas in the Quality server its much more (almost 3crore entries in each of the tables).
Regards,
YOGESH BABU K
Edited by: YogeshKS on Jun 13, 2011 11:37 AM
Edited by: YogeshKS on Jun 13, 2011 11:39 AM

Hi all,
I have created a flow(program) and while executing the same program in the development server i am getting the desired output.
But when i execute the same program in the background mode (it fails in the foreground after 9 or 10 hrs giving the same error message) in the quality server, its giving time-out error 430 ( 00-430 TIME OUT IN ESTABLISHING A DIALOGUE ASYNCHRONOUS ).
Can someone explain me, what this error is all about.
It will be helpful,if you also teach me how to correct the same error.
NOTE : The DataBase tables being used in this program has fewer entries in the Development Server (in between 100 and 200 entries in each of the tables) whereas in the Quality server its much more (almost 3crore entries in each of the tables).
Regards,
YOGESH BABU K
Edited by: YogeshKS on Jun 13, 2011 11:37 AM
Edited by: YogeshKS on Jun 13, 2011 11:39 AM

RSTXSCRP - Time out error

Hello ,
I am using the RSTXSCRP program to download and upload script.
I am able to download(EXPORT).
But during upload(IMPORT) to another system its giving a TIME OUT error.
Do we need tot create the script in the upload syatem before using the RSTXSCRP program for upload!

Hi,
Create the Script and try to upload it will work fine. Even I was in the same situation . So I have created the script in SE71 and I have uploaded it . It came all those codes and windows.

Select count(*) cause time out error

I invoke the following statement:
select count(*) as total from table1
where table1 is large(30000 rows), total size of the database is more than 20GB.
The above statement will cause time out error. How to solve the problem?

Hallo chcw,
a timeout in a table with 30.000 records is very unusual (for a simple SELECT COUNT). From my point of view Dan is on the right way and you will have a typical blocking scenario.
1. if you have LOBs they won't be part of a SELECT COUNT (either its a heap of a clustered index)
2. Microosft SQL Server will ALWAYS use the smallest index for such a simple SELECT
3. if it is a heap you will run into a blocking scenario if someone is updating records and transaction has not committed.
4. Check the isolation level of the transactions - but I expect the standard which is "read committed".
Just a demonstration of "SELECT COUNT" will work whether it is a clustered index or a heap. The next script will create a heap with a LOB and additional attributes:
CREATE TABLE dbo.foo
Id INT NOT NULL IDENTITY(1,1),
n1 INT NOT NULL,
n2 SMALLINT NULL,
c1 CHAR(250) NOT NULL,
c2 CHAR(250) NULL,
c3 VARCHAR(MAX) NOT NULL DEFAULT (REPLICATE('A', 15000))
GO
Now we enter 30,000 records into the table
SET NOCOUNT ON;
DECLARE @i INT = 1;
WHILE @i <= 30000
BEGIN
INSERT INTO dbo.foo (n1, c1) VALUES (@i, 'Just a filler');
SET @i += 1;
END
GO
Keep in mind that we have a HEAP and NO indexes! To check the IO i use the following command befor any of the following examples:
SET STATISTICS IO ON;
GO
Let's start with a first try and you will check as a result the produced IO depending on the affected table partitions:
-- USE SELECT in a HEAP
SELECT COUNT(*) FROM dbo.foo;
GO
Output:
Table 'foo'. Scan count 1, logical reads 2508, ..., lob logical reads 0,
As you can see from the result the LOB-data won't be attached only the "in-row-data" are affected (which are stored in 2508 pages. The reason is a quite simple one: Microsoft SQL Server uses different allocation units for in-row-data and LOB
SELECT p.object_id, p.index_id, p.rows, au.total_pages
FROM sys.partitions AS P INNER JOIN sys.allocation_units AS AU
ON(p.partition_id = au.container_id)
WHERE object_id = OBJECT_ID('dbo.foo');
Now I create a simple index on the column n1 which is an INT-datatype
SELECT p.object_id, p.index_id, p.rows, au.total_pages
FROM sys.partitions AS P INNER JOIN sys.allocation_units AS AU
ON(p.partition_id = au.container_id)
WHERE object_id = OBJECT_ID('dbo.foo');
and run the SELECT COUNT again with the following IO-output:
Table 'foo'. Scan count 1, logical reads 69, ...
WOW - only 69 pages have to be read. The explanation is a quite simple one - now we have an index which is quite small. Microsoft SQL Server WILL use the smallest index of a table to scan the number of records. Let's try it again with n2 which is a smallint
(2 bytes)
CREATE NONCLUSTERED INDEX ix_foo_n2 ON dbo.foo (n2);
GO
The IO will be 62 (or less) because MORE index records a fitting to one data page!
Conclusion is that either you have small record size or long record size - The query optimizer will always use the smallest index for the execution (that's maybe why Visahk has asked for the execution plan).
I don't believe it is because of the "huge amount of data" but - as Dan has pointed out - it HAS TO BE a blocking scenario which can have multiple reasons. For demonstration of a blocking scenario open SSMS and start in the query windows with the following
command(s):
BEGIN TRANSACTION
UPDATE dbo.foo
SET c1 = 'This is my name'
WHERE Id = 10000;
-- What locks do we have now in the database
SELECT resource_description,
resource_associated_entity_id,
request_mode,
request_type
FROM sys.dm_tran_locks AS DTL
WHERE resource_database_id = DB_ID() AND
resource_type != 'DATABASE';
Your result should look like that (with differences in the entity_id and resource descriptions :)
The above pic demonstrates the "locking chain". As you can see the slot 7 on PAGE 82400 has an exclusive lock. This means that NO OTHER request can currently obtain another lock to it!
Now open a second query window and run a SELECT COUNT... - it will not finish!
The reason is that the second requests has to wait for the release of the locked resources by the first transaction! Leave the statement and change back to the first transaction and finish the transaction by cancellation of the query. In the moment the locks
have been released the second query will finish immediate.
So - from my point of view - Dan has given the correct answer. Against wide spreaded statements a heap won't block the whole table exclusivly but - as in a cluster, too - only the row itself (see the 7 which is the slot where the record exists).
MCM - SQL Server 2008
MCSE - SQL Server 2012
db Berater GmbH
SQL Server Blog (german only)

Time Out error : Its urgent

Similar Messages

Maybe you are looking for