REBD_GUI_CORP_USE_ARCH SAP Function module - Internal Usage of Architecture

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

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

Pattern for FM REBD_GUI_CORP_USE_ARCH - REBD GUI CORP USE ARCH

CALL FUNCTION 'REBD_GUI_CORP_USE_ARCH' "Internal Usage of Architecture
  EXPORTING
    it_intreno =                " re_t_intreno  INTRENO
    id_spec_date =              " sy-datum      Date and Time, Current (Application Server) Date
    id_date_to =                " sy-datum      Date and Time, Current (Application Server) Date
    id_bukrs =                  " bukrs         Company Code
    id_meas_1 =                 " rebdmeas      Measurement Type
    id_meas_2 =                 " rebdmeas      Measurement Type
    id_arch_use =               " c
*   if_full = ' '               " c
*   if_rental_unit = ' '        " c             Do Not Display Rental Units
    .  "  REBD_GUI_CORP_USE_ARCH

ABAP code example for Function Module REBD_GUI_CORP_USE_ARCH

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

DATA(ld_id_spec_date) = '20210129'.

DATA(ld_id_date_to) = '20210129'.

DATA(ld_id_bukrs) = '20210129'.

DATA(ld_id_meas_1) = '20210129'.

DATA(ld_id_meas_2) = '20210129'.

DATA(ld_id_arch_use) = '20210129'.

DATA(ld_if_full) = '20210129'.

DATA(ld_if_rental_unit) = '20210129'.
.

CALL FUNCTION 'REBD_GUI_CORP_USE_ARCH'
  EXPORTING
    it_intreno =                 ld_it_intreno
    id_spec_date =               ld_id_spec_date
    id_date_to =                 ld_id_date_to
    id_bukrs =                   ld_id_bukrs
    id_meas_1 =                  ld_id_meas_1
    id_meas_2 =                  ld_id_meas_2
    id_arch_use =                ld_id_arch_use
*   if_full =                    ld_if_full
*   if_rental_unit =             ld_if_rental_unit
    .  "  REBD_GUI_CORP_USE_ARCH

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_it_intreno
 
 TYPE RE_T_INTRENO ,
ld_id_spec_date
 
 TYPE SY-DATUM ,
ld_id_date_to
 
 TYPE SY-DATUM ,
ld_id_bukrs
 
 TYPE BUKRS ,
ld_id_meas_1
 
 TYPE REBDMEAS ,
ld_id_meas_2
 
 TYPE REBDMEAS ,
ld_id_arch_use
 
 TYPE C ,
ld_if_full
 
 TYPE C ,
ld_if_rental_unit
 
 TYPE C .


ld_it_intreno = '20210129'.
ld_id_spec_date = '20210129'.
ld_id_date_to = '20210129'.
ld_id_bukrs = '20210129'.
ld_id_meas_1 = '20210129'.
ld_id_meas_2 = '20210129'.
ld_id_arch_use = '20210129'.
ld_if_full = '20210129'.
ld_if_rental_unit = '20210129'.