Use transaction SE38 with SECATT

[Former Member]

Hello Experts

We have a customer specific programme "/ZEU/YHG_TEST_GET_PICTURE" to export employee's pictures on C:\temp. These pictures were once uploaded into the ArchiveLink (Transaction OAAD) as PREL documents. If I run the programme with SE38 directly, the file is properly saved as jpg with the following message:

--> Message no. FES034

--> 62.858 bytes transferred

During the recording of the SECATT script, it works as well. But if I start the SECATT script afterwards, no file has been created, neither in Testsystem nor in productive System.

In the Log file from the SECATT I don't receive any mistake. The message is the same:

--> Message no. FES034

--> 62.858 bytes transferred

For some reason, in C:\temp no file has been created.

Do you have any idea what the problem could be?

Thanks a lot.

[Wutschi]

Could you please share some more Information:

Aare you using TCD or SAPGUI?

Is it possible to share the detailed Log file?

(To download the log you need to print the log and download the print view.)

Try to run the script with the option to check Application Log Messages.

How do you enter the path on the Program if it opens this window:

This belongs not to the SAP System and could not be recorded.

Regards

Christian

[Former Member]

I use the command TCD REC.

Please find attached the detailed log-file.

The check box "create application log messages" I have always selected.

A popup to save the file never appears. It is programmed in the customer-specific programme which I start in the SECATT. As you can see below, it is fix programmed to export it in C:\Temp:

IF filelength > 0.

  CONCATENATE 'C:\Temp\' filename INTO path.

  CALL FUNCTION 'GUI_DOWNLOAD'

    EXPORTING

      bin_filesize = filelength

      filename     = path

      filetype     = 'BIN'

    TABLES

      data_tab     = binary_tab.

  IF sy-subrc = 0.

    SKIP.

    WRITE: / 'Document saved in', path.

  ENDIF.

ENDIF.

In the debugger I see that the code was executed (filelength = 62858). After the CONCATENATE the variable "path" has the value = C:\Temp\00161652.jpg, what looks perfect.

Best regards,
Diego

[Wutschi]

Hi Diego,

you are using the FB GUI_DOWNLOAD in your program, but you are using the TCD Driver which is not using the SAPGUI and is running in background.

I think you need to use the SAPGUI Driver to record you program as the SAPGUI driver is using the SAPGUI Scripting and then the FB GUI_DOWNLOAD should work.

Regards

Christian

[Former Member]

Hello Christian

I have tried to use SAPGUI instead of TCD in the SECATT script. Then I receive a popup with the field "Start Recording with Transaction" where I wrote SE38. After press the button <Start Recording> I receive the following message:

Scripting Is Not Allowed in Current eCATT System

or on Current Server

Is this SAPGUI-Driver missing? If yes, how can I solve it?

Best regards,

Diego

[Wutschi]

Hi Diego,

you need to go to Transaction RZ11 in the system where SE38 should run and change the Parameter sapgui/user_scripting to TRUE. You should get your basis team to change that parameter in the server profile (RZ10) as well. Otherwise it will be gone after a system reboot.

Regards

Christian