REYC_GUI_MAJORTENANT_PBO SAP Function module - PBO des Parent-Screens (initialisiert Subscreen)

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

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

Pattern for FM REYC_GUI_MAJORTENANT_PBO - REYC GUI MAJORTENANT PBO

CALL FUNCTION 'REYC_GUI_MAJORTENANT_PBO' "PBO des Parent-Screens (initialisiert Subscreen)
  EXPORTING
    io_term_mngr =              " if_retm_term_mngr
    id_termtype =               " retm_term-termtype
    id_termno =                 " retm_term-termno
    id_validfrom =              " retmtermvalidfrom
*   id_tab_index = 1            " sytabix
*   if_readonly =               " abap_bool
*   io_navigation_data =        " cl_reca_data_container
*   io_current_nav_data =       " cl_reca_data_container
  IMPORTING
    es_subscreen =              " recascreen
    .  "  REYC_GUI_MAJORTENANT_PBO

ABAP code example for Function Module REYC_GUI_MAJORTENANT_PBO

The ABAP code below is a full code listing to execute function module REYC_GUI_MAJORTENANT_PBO 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_es_subscreen  
 
 TYPE RECASCREEN
.


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


DATA(ld_id_termtype) = some text here


DATA(ld_id_termno) = some text here

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

DATA(ld_id_tab_index) = '123 '.

DATA(ld_if_readonly) = '123 '.

DATA(ld_io_navigation_data) = '123 '.

DATA(ld_io_current_nav_data) = '123 '.
.

CALL FUNCTION 'REYC_GUI_MAJORTENANT_PBO'
  EXPORTING
    io_term_mngr =               ld_io_term_mngr
    id_termtype =                ld_id_termtype
    id_termno =                  ld_id_termno
    id_validfrom =               ld_id_validfrom
*   id_tab_index =               ld_id_tab_index
*   if_readonly =                ld_if_readonly
*   io_navigation_data =         ld_io_navigation_data
*   io_current_nav_data =        ld_io_current_nav_data
  IMPORTING
    es_subscreen =               ld_es_subscreen
    .  "  REYC_GUI_MAJORTENANT_PBO

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_es_subscreen
 
 TYPE RECASCREEN ,
ld_io_term_mngr
 
 TYPE IF_RETM_TERM_MNGR ,
ld_id_termtype
 
 TYPE RETM_TERM-TERMTYPE ,
ld_id_termno
 
 TYPE RETM_TERM-TERMNO ,
ld_id_validfrom
 
 TYPE RETMTERMVALIDFROM ,
ld_id_tab_index
 
 TYPE SYTABIX ,
ld_if_readonly
 
 TYPE ABAP_BOOL ,
ld_io_navigation_data
 
 TYPE CL_RECA_DATA_CONTAINER ,
ld_io_current_nav_data
 
 TYPE CL_RECA_DATA_CONTAINER .


ld_io_term_mngr = '123 '.

ld_id_termtype = some text here

ld_id_termno = some text here
ld_id_validfrom = '123 '.
ld_id_tab_index = '123 '.
ld_if_readonly = '123 '.
ld_io_navigation_data = '123 '.
ld_io_current_nav_data = '123 '.