2021 Oct 12 2:40 PM
Hello,
I am trying to check and control a file on application server, at some point, I have to read the content of the xml file in a string then call a transformation.
DO.
CLEAR lv_line.
TRY.
READ DATASET lv_filepath INTO lv_line.
CATCH cx_sy_conversion_codepage.
"Erreur lecture du fichier
MESSAGE e008(zisu_charg_sf) INTO gs_return-msg .
MOVE-CORRESPONDING sy TO gs_return.
EXIT.
ENDTRY.
IF sy-subrc NE 0.
EXIT.
ENDIF.
y_xml_string = |{ y_xml_string } { lv_line }|.
CONDENSE y_xml_string.
ENDDO.
The file is large(about 12 Mo), the MF exceeds the maximum permitted runtime without interruption( the system profile parameter "rdisp/max_wprun_time"), SAP considers it as an endless loop and then a TIME OUT dump is triggered and has therefore been terminated.
From my point of view, there's nothing to do in ABAP level, the production team refuse to increase the value of "rdisp/max_wprun_time".
I would be grateful if you could provide some help and suggest a solution.
Best regards,
Achraf
Hello,
I am trying to check and control a file on application server, at some point, I have to read the content of the xml file in a string then call a transformation.
DO.
CLEAR lv_line.
TRY.
READ DATASET lv_filepath INTO lv_line.
CATCH cx_sy_conversion_codepage.
"Erreur lecture du fichier
MESSAGE e008(zisu_charg_sf) INTO gs_return-msg .
MOVE-CORRESPONDING sy TO gs_return.
EXIT.
ENDTRY.
IF sy-subrc NE 0.
EXIT.
ENDIF.
y_xml_string = |{ y_xml_string } { lv_line }|.
CONDENSE y_xml_string.
ENDDO.
The file is large(about 12 Mo), the MF exceeds the maximum permitted runtime without interruption( the system profile parameter "rdisp/max_wprun_time"), SAP considers it as an endless loop and then a TIME OUT dump is triggered and has therefore been terminated.
From my point of view, there's nothing to do in ABAP level, the production team refuse to increase the value of "rdisp/max_wprun_time".
I would be grateful if you could provide some help and suggest a solution.
Best regards,
Achraf
2021 Oct 12 2:53 PM
2021 Oct 12 2:55 PM
2021 Oct 12 3:09 PM
No, SAP doesn't consider it's an endless loop, it considers it's a time out.
See Matthew solution. Background execution is not subject to time out.