ARCHIVE_REMOTE_TRANSFER_FILE SAP Function module

ARCHIVE_REMOTE_TRANSFER_FILE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ARCHIVE_REMOTE_TRANSFER_FILE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: AADM
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ARCHIVE_REMOTE_TRANSFER_FILE - ARCHIVE REMOTE TRANSFER FILE

CALL FUNCTION 'ARCHIVE_REMOTE_TRANSFER_FILE' "
  EXPORTING
    iv_archiving_object =       " arch_obj-object
    iv_archive_key =            " admi_files-archiv_key
*   iv_offset =                 " arch_idx-offset
*   iv_length =                 " admi_files-obj_count
  IMPORTING
    ev_data_length =            " admi_files-obj_count
  TABLES
    et_data =                   " tbl1024
  EXCEPTIONS
    OPEN_ERROR = 1              "
    .  "  ARCHIVE_REMOTE_TRANSFER_FILE

ABAP code example for Function Module ARCHIVE_REMOTE_TRANSFER_FILE

The ABAP code below is a full code listing to execute function module ARCHIVE_REMOTE_TRANSFER_FILE including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_ev_data_length  
 
 TYPE ADMI_FILES-OBJ_COUNT
,
it_et_data  
 
 TYPE STANDARD TABLE OF TBL1024,"TABLES PARAM
wa_et_data
 
 LIKE LINE OF it_et_data
.

 

SELECT single OBJECT 
  FROM ARCH_OBJ 
  INTO @DATA(ld_iv_archiving_object).

 

SELECT single ARCHIV_KEY 
  FROM ADMI_FILES 
  INTO @DATA(ld_iv_archive_key).

 

SELECT single OFFSET 
  FROM ARCH_IDX 
  INTO @DATA(ld_iv_offset).

 

SELECT single OBJ_COUNT 
  FROM ADMI_FILES 
  INTO @DATA(ld_iv_length).

 

"populate fields of struture and append to itab
append wa_et_data to it_et_data.
.

CALL FUNCTION 'ARCHIVE_REMOTE_TRANSFER_FILE'
  EXPORTING
    iv_archiving_object =        ld_iv_archiving_object
    iv_archive_key =             ld_iv_archive_key
*   iv_offset =                  ld_iv_offset
*   iv_length =                  ld_iv_length
  IMPORTING
    ev_data_length =             ld_ev_data_length
  TABLES
    et_data =                    it_et_data
  EXCEPTIONS
    OPEN_ERROR =                 1
    .  "  ARCHIVE_REMOTE_TRANSFER_FILE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ev_data_length
 
 TYPE ADMI_FILES-OBJ_COUNT ,
ld_iv_archiving_object
 
 TYPE ARCH_OBJ-OBJECT ,
it_et_data
 
 TYPE STANDARD TABLE OF TBL1024 ,
wa_et_data
 
 LIKE LINE OF it_et_data,
ld_iv_archive_key
 
 TYPE ADMI_FILES-ARCHIV_KEY ,
ld_iv_offset
 
 TYPE ARCH_IDX-OFFSET ,
ld_iv_length
 
 TYPE ADMI_FILES-OBJ_COUNT .



SELECT single OBJECT 
  FROM ARCH_OBJ 
  INTO ld_iv_archiving_object.
 

"populate fields of struture and append to itab
append wa_et_data to it_et_data.

SELECT single ARCHIV_KEY 
  FROM ADMI_FILES 
  INTO ld_iv_archive_key.


SELECT single OFFSET 
  FROM ARCH_IDX 
  INTO ld_iv_offset.


SELECT single OBJ_COUNT 
  FROM ADMI_FILES 
  INTO ld_iv_length.