FM_FMIT_FROM_ARCHIVE_READ SAP Function module

FM_FMIT_FROM_ARCHIVE_READ 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 FM_FMIT_FROM_ARCHIVE_READ into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FMAR_READ
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FM_FMIT_FROM_ARCHIVE_READ - FM FMIT FROM ARCHIVE READ

CALL FUNCTION 'FM_FMIT_FROM_ARCHIVE_READ' "
  EXPORTING
    i_selections =              " rsds_trange
*   i_show_errors =             " boole_d
*   i_show_progess = 'X'        " boole_d
  IMPORTING
    e_log_handle =              " balloghndl
* TABLES
*   e_fmit =                    " fmit
*   i_arch_sel =                " rng_archiv
  EXCEPTIONS
    NO_INFOSTRUC_FOUND = 1      "
    SELECTIONS_ERROR = 2        "
    .  "  FM_FMIT_FROM_ARCHIVE_READ

ABAP code example for Function Module FM_FMIT_FROM_ARCHIVE_READ

The ABAP code below is a full code listing to execute function module FM_FMIT_FROM_ARCHIVE_READ 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_e_log_handle  
 
 TYPE BALLOGHNDL
,
it_e_fmit  
 
 TYPE STANDARD TABLE OF FMIT,"TABLES PARAM
wa_e_fmit
 
 LIKE LINE OF it_e_fmit
,
it_i_arch_sel  
 
 TYPE STANDARD TABLE OF RNG_ARCHIV,"TABLES PARAM
wa_i_arch_sel
 
 LIKE LINE OF it_i_arch_sel
.


DATA(ld_i_selections) = 'Check type of data required'.

DATA(ld_i_show_errors) = 'Check type of data required'.

DATA(ld_i_show_progess) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_e_fmit to it_e_fmit.
 

"populate fields of struture and append to itab
append wa_i_arch_sel to it_i_arch_sel.
.

CALL FUNCTION 'FM_FMIT_FROM_ARCHIVE_READ'
  EXPORTING
    i_selections =               ld_i_selections
*   i_show_errors =              ld_i_show_errors
*   i_show_progess =             ld_i_show_progess
  IMPORTING
    e_log_handle =               ld_e_log_handle
* TABLES
*   e_fmit =                     it_e_fmit
*   i_arch_sel =                 it_i_arch_sel
  EXCEPTIONS
    NO_INFOSTRUC_FOUND =         1
    SELECTIONS_ERROR =           2
    .  "  FM_FMIT_FROM_ARCHIVE_READ

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "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_e_log_handle
 
 TYPE BALLOGHNDL ,
ld_i_selections
 
 TYPE RSDS_TRANGE ,
it_e_fmit
 
 TYPE STANDARD TABLE OF FMIT ,
wa_e_fmit
 
 LIKE LINE OF it_e_fmit,
ld_i_show_errors
 
 TYPE BOOLE_D ,
it_i_arch_sel
 
 TYPE STANDARD TABLE OF RNG_ARCHIV ,
wa_i_arch_sel
 
 LIKE LINE OF it_i_arch_sel,
ld_i_show_progess
 
 TYPE BOOLE_D .


ld_i_selections = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_e_fmit to it_e_fmit.
ld_i_show_errors = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_i_arch_sel to it_i_arch_sel.
ld_i_show_progess = 'Check type of data required'.