FASU_HANDLE_1_VARIANT_RFC SAP Function module - handel on single variant for one report (RFC)

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

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

Pattern for FM FASU_HANDLE_1_VARIANT_RFC - FASU HANDLE 1 VARIANT RFC

CALL FUNCTION 'FASU_HANDLE_1_VARIANT_RFC' "handel on single variant for one report (RFC)
  EXPORTING
    is_report =                 " tasuvar1      ASU Variants: Fieldinformations for reports with variant
    is_varid =                  " varid         Variant directory
  TABLES
    ct_protocol =               " sprot_u       Log Generation Interface
    it_selc =                   " rselc         Structure of table of selection conditions
    it_sscr =                   " rsscr         Structure of internal table %_SSCR (selection screen,ABAP/4)
    .  "  FASU_HANDLE_1_VARIANT_RFC

ABAP code example for Function Module FASU_HANDLE_1_VARIANT_RFC

The ABAP code below is a full code listing to execute function module FASU_HANDLE_1_VARIANT_RFC 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:
it_ct_protocol  
 
 TYPE STANDARD TABLE OF SPROT_U,"TABLES PARAM
wa_ct_protocol
 
 LIKE LINE OF it_ct_protocol
,
it_it_selc  
 
 TYPE STANDARD TABLE OF RSELC,"TABLES PARAM
wa_it_selc
 
 LIKE LINE OF it_it_selc
,
it_it_sscr  
 
 TYPE STANDARD TABLE OF RSSCR,"TABLES PARAM
wa_it_sscr
 
 LIKE LINE OF it_it_sscr
.


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

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

"populate fields of struture and append to itab
append wa_ct_protocol to it_ct_protocol.
 

"populate fields of struture and append to itab
append wa_it_selc to it_it_selc.
 

"populate fields of struture and append to itab
append wa_it_sscr to it_it_sscr.
.

CALL FUNCTION 'FASU_HANDLE_1_VARIANT_RFC'
  EXPORTING
    is_report =                  ld_is_report
    is_varid =                   ld_is_varid
  TABLES
    ct_protocol =                it_ct_protocol
    it_selc =                    it_it_selc
    it_sscr =                    it_it_sscr
    .  "  FASU_HANDLE_1_VARIANT_RFC

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_is_report
 
 TYPE TASUVAR1 ,
it_ct_protocol
 
 TYPE STANDARD TABLE OF SPROT_U ,
wa_ct_protocol
 
 LIKE LINE OF it_ct_protocol,
ld_is_varid
 
 TYPE VARID ,
it_it_selc
 
 TYPE STANDARD TABLE OF RSELC ,
wa_it_selc
 
 LIKE LINE OF it_it_selc,
it_it_sscr
 
 TYPE STANDARD TABLE OF RSSCR ,
wa_it_sscr
 
 LIKE LINE OF it_it_sscr.


ld_is_report = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_ct_protocol to it_ct_protocol.
ld_is_varid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_selc to it_it_selc. 

"populate fields of struture and append to itab
append wa_it_sscr to it_it_sscr.