REXC_FR_SRU_OUTPUT SAP Function module - Handle SRU Tool Output

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

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

Pattern for FM REXC_FR_SRU_OUTPUT - REXC FR SRU OUTPUT

CALL FUNCTION 'REXC_FR_SRU_OUTPUT' "Handle SRU Tool Output
  EXPORTING
*   it_postings_l =             " re_t_fr_sru_tp_l  Log of SRU Postings (VIXCFRSRULOG)
*   it_su =                     " re_t_vixcfreo  Output list of SUs in Status Extraord. Operation
*   it_sostatus =               " re_t_fr_sostatus  Select Options for Status
    id_trans =                  " rexcfrtrans   Transaction ID
*   id_vari =                   " slis_vari     Layout
*   id_logtrans =               " rexcfrtrans   Transaction ID
* CHANGING
*   co_msglist =                " if_reca_message_list  Application Log: Log Handle
    .  "  REXC_FR_SRU_OUTPUT

ABAP code example for Function Module REXC_FR_SRU_OUTPUT

The ABAP code below is a full code listing to execute function module REXC_FR_SRU_OUTPUT 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_co_msglist) = 'Check type of data required'.

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

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

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

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

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

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

CALL FUNCTION 'REXC_FR_SRU_OUTPUT'
  EXPORTING
*   it_postings_l =              ld_it_postings_l
*   it_su =                      ld_it_su
*   it_sostatus =                ld_it_sostatus
    id_trans =                   ld_id_trans
*   id_vari =                    ld_id_vari
*   id_logtrans =                ld_id_logtrans
* CHANGING
*   co_msglist =                 ld_co_msglist
    .  "  REXC_FR_SRU_OUTPUT

IF SY-SUBRC EQ 0.
  "All OK
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_co_msglist
 
 TYPE IF_RECA_MESSAGE_LIST ,
ld_it_postings_l
 
 TYPE RE_T_FR_SRU_TP_L ,
ld_it_su
 
 TYPE RE_T_VIXCFREO ,
ld_it_sostatus
 
 TYPE RE_T_FR_SOSTATUS ,
ld_id_trans
 
 TYPE REXCFRTRANS ,
ld_id_vari
 
 TYPE SLIS_VARI ,
ld_id_logtrans
 
 TYPE REXCFRTRANS .


ld_co_msglist = 'Check type of data required'.
ld_it_postings_l = 'Check type of data required'.
ld_it_su = 'Check type of data required'.
ld_it_sostatus = 'Check type of data required'.
ld_id_trans = 'Check type of data required'.
ld_id_vari = 'Check type of data required'.
ld_id_logtrans = 'Check type of data required'.