Work process restarted session terminated error

[former_member222759]

Hi All,

Iam trying to execute a code

LOOP AT <fs_outtab> INTO <fs_line>.

          DO .

            ASSIGN COMPONENT sy-index OF STRUCTURE <fs_line>  TO <fs>.

            IF sy-subrc <> 0.

              EXIT.

            ELSE.

              lv_data = <fs>.

              CONCATENATE lv_string lv_data  INTO lv_string SEPARATED BY ','.

            ENDIF.

          ENDDO.

*          CONCATENATE lv_string lv_text INTO lv_text  IN CHARACTER MODE SEPARATED BY ','. .

          TRANSFER lv_string TO lv_filepath.

          Clear: lv_string ,lv_data.

           ENDLOOP.

After the TRANSFER statement i get an message .

SAP system message.

Work process restarted session terminated

Is the issue is with the code ?????

[Ashg1402]

Hi Pri,

Why did you use transfer? It's mostly used in file interface. In-spite of transfer use move.  or do a direct copy.

What is the data type for lv_filepath?

[former_member222759]

Hi Ashish,

Thanks for your reply...  lv_filepath is of type string.

I need to transfer data to a dir. in .CSV format.

This is the dump i get in ST22.

Category               Resource Shortage

Runtime Errors         DATASET_WRITE_ERROR

Except.                CX_SY_FILE_IO

Date and Time          22.04.2016 22:11:18

Short text

     Error when writing to the file "/interface/GEC/HKG_IL_ORDER_20160422121118197.c

What happened?

     Resource bottleneck

     The current program "ZSD0002" had to be terminated because

     a capacity limit has been reached.

What can you do?

     Note which actions and input led to the error.

     For further help in handling the problem, contact your SAP administrator

     .

     You can use the ABAP dump analysis transaction ST22 to view and manage

     termination messages, in particular for long term reference.

Error analysis

     An exception occurred that is explained in detail below.

     The exception, which is assigned to class 'CX_SY_FILE_IO', was not caught in

     procedure "DISPLAY_OUTPUT" "(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:

     An error occurred when writing to the file

      "/interface/GEC/HKG_IL_ORDER_20160422121118197.csv".

Error text: "No space left on device"

Error code: 28

[Former Member]

The dump tells you exactly what the problem is!!

"No space left on device".

Rob

[Juwin]

You read/need to provide the information in the Short dump to get help.

Thanks,

Juwin

[former_member222759]

Hi Juwin,

Thanks for your reply.

This is the dump i get in ST22.

Category               Resource Shortage

Runtime Errors         DATASET_WRITE_ERROR

Except.                CX_SY_FILE_IO

Date and Time          22.04.2016 22:11:18

Short text

     Error when writing to the file "/interface/GEC/HKG_IL_ORDER_20160422121118197.c

What happened?

     Resource bottleneck

     The current program "ZSD0002" had to be terminated because

     a capacity limit has been reached.

What can you do?

     Note which actions and input led to the error.

     For further help in handling the problem, contact your SAP administrator

     .

     You can use the ABAP dump analysis transaction ST22 to view and manage

     termination messages, in particular for long term reference.

Error analysis

     An exception occurred that is explained in detail below.

     The exception, which is assigned to class 'CX_SY_FILE_IO', was not caught in

     procedure "DISPLAY_OUTPUT" "(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:

     An error occurred when writing to the file

      "/interface/GEC/HKG_IL_ORDER_20160422121118197.csv".

Error text: "No space left on device"

Error code: 28

[Juwin]

It is clear from the dump that this is not an ABAP issue. Error text says : "No space left on device", mostly meaning, the drive were you are trying to write the file is full.

Thanks,

Juwin

[deependra_shekhawat3]

Hi,

where did you open the dataset before writing into file ?

Could you please provide all code ?

[former_member222759]

Hi Deependra,

This is the code ,

OPEN DATASET lv_filepath  FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.

      IF sy-subrc EQ 0.

        LOOP AT <fs_outtab> INTO <fs_line>.

          DO .

            ASSIGN COMPONENT sy-index OF STRUCTURE <fs_line>  TO <fs>.

            IF sy-subrc <> 0.

              EXIT.

            ELSE.

              lv_data = <fs>.

              CONCATENATE lv_string lv_data  INTO lv_string IN CHARACTER MODE SEPARATED BY SPACE.

            ENDIF.

          ENDDO.

*          CONCATENATE lv_string lv_text INTO lv_text  IN CHARACTER MODE SEPARATED BY ','. .

          TRANSFER lv_string TO lv_filepath.

          CLEAR: lv_string ,lv_data.

        ENDLOOP.

        CLOSE DATASET lv_filepath.

[deependra_shekhawat3]

Code looks okay .

I think it may be   TRANSFER lv_text TO lv_filepath.

Have you checked ST11 to trace the dump ?

You can find the actual reason there. May be some Authorization issue.

[former_member222759]

Hi All,

I solved this...

There were many files created in AL11 in the specified directory. I deleted all the files and then it created .

Thanks for all your help.

Thanks,

Priya