FRML770_CALL_PTREE_EXAMPLE SAP Function module

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

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

Pattern for FM FRML770_CALL_PTREE_EXAMPLE - FRML770 CALL PTREE EXAMPLE

CALL FUNCTION 'FRML770_CALL_PTREE_EXAMPLE' "
  EXPORTING
*   i_flg_compare = ''          " rmste_compare
*   i_flg_display_tablecreate = ''  " rmste_display_tablecreate
*   i_tabname =                 " ddobjname
    i_repid = SY-REPID          " sy-repid
  IMPORTING
    e_flg_otpt_display =        " boolean
  CHANGING
*   xs_layout =                 " rmsts_otpt_rmsdx
    xs_appl_param =             " rmsts_appl_param
    xt_ddic_def =               " rmstty_ddic_definition
    .  "  FRML770_CALL_PTREE_EXAMPLE

ABAP code example for Function Module FRML770_CALL_PTREE_EXAMPLE

The ABAP code below is a full code listing to execute function module FRML770_CALL_PTREE_EXAMPLE 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_flg_otpt_display  
 
 TYPE BOOLEAN
.


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

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

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

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

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

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

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

CALL FUNCTION 'FRML770_CALL_PTREE_EXAMPLE'
  EXPORTING
*   i_flg_compare =              ld_i_flg_compare
*   i_flg_display_tablecreate =    ld_i_flg_display_tablecreate
*   i_tabname =                  ld_i_tabname
    i_repid =                    ld_i_repid
  IMPORTING
    e_flg_otpt_display =         ld_e_flg_otpt_display
  CHANGING
*   xs_layout =                  ld_xs_layout
    xs_appl_param =              ld_xs_appl_param
    xt_ddic_def =                ld_xt_ddic_def
    .  "  FRML770_CALL_PTREE_EXAMPLE

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_xs_layout
 
 TYPE RMSTS_OTPT_RMSDX ,
ld_e_flg_otpt_display
 
 TYPE BOOLEAN ,
ld_i_flg_compare
 
 TYPE RMSTE_COMPARE ,
ld_xs_appl_param
 
 TYPE RMSTS_APPL_PARAM ,
ld_i_flg_display_tablecreate
 
 TYPE RMSTE_DISPLAY_TABLECREATE ,
ld_xt_ddic_def
 
 TYPE RMSTTY_DDIC_DEFINITION ,
ld_i_tabname
 
 TYPE DDOBJNAME ,
ld_i_repid
 
 TYPE SY-REPID .


ld_xs_layout = 'some text here'.
ld_i_flg_compare = 'some text here'.
ld_xs_appl_param = 'some text here'.
ld_i_flg_display_tablecreate = 'some text here'.
ld_xt_ddic_def = 'some text here'.
ld_i_tabname = 'some text here'.
ld_i_repid = 'Check type of data required'.