BSPWD_RT_REP_GET_INTVIEW_4_DEF SAP Function module - Dialog popup for requesting an Component Interface view for definition

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

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

Pattern for FM BSPWD_RT_REP_GET_INTVIEW_4_DEF - BSPWD RT REP GET INTVIEW 4 DEF

CALL FUNCTION 'BSPWD_RT_REP_GET_INTVIEW_4_DEF' "Dialog popup for requesting an Component  Interface view for definition
  EXPORTING
    iv_persistence =            " cl_bsp_wd_rt_rep_persist  Runtime Repository Persistence Handler
    iv_start_row = '5'          "
    iv_start_col = '5'          "
  IMPORTING
    ev_interface_view =         " string
    ev_mapped_window =          " string
    ev_switch_id =              " sfw_switchid  ID of Switch in Switch Framework
    ev_switch_reaction =        " sfw_showhide  Reaction to Switch
  EXCEPTIONS
    CANCELED = 1                "               Dialog canceled by user
    .  "  BSPWD_RT_REP_GET_INTVIEW_4_DEF

ABAP code example for Function Module BSPWD_RT_REP_GET_INTVIEW_4_DEF

The ABAP code below is a full code listing to execute function module BSPWD_RT_REP_GET_INTVIEW_4_DEF 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_ev_interface_view  
 
 TYPE STRING
,
ld_ev_mapped_window  
 
 TYPE STRING
,
ld_ev_switch_id  
 
 TYPE SFW_SWITCHID
,
ld_ev_switch_reaction  
 
 TYPE SFW_SHOWHIDE
.


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

DATA(ld_iv_start_row) = 'some text here'.

DATA(ld_iv_start_col) = 'some text here'.
.

CALL FUNCTION 'BSPWD_RT_REP_GET_INTVIEW_4_DEF'
  EXPORTING
    iv_persistence =             ld_iv_persistence
    iv_start_row =               ld_iv_start_row
    iv_start_col =               ld_iv_start_col
  IMPORTING
    ev_interface_view =          ld_ev_interface_view
    ev_mapped_window =           ld_ev_mapped_window
    ev_switch_id =               ld_ev_switch_id
    ev_switch_reaction =         ld_ev_switch_reaction
  EXCEPTIONS
    CANCELED =                   1
    .  "  BSPWD_RT_REP_GET_INTVIEW_4_DEF

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_ev_interface_view
 
 TYPE STRING ,
ld_iv_persistence
 
 TYPE CL_BSP_WD_RT_REP_PERSIST ,
ld_ev_mapped_window
 
 TYPE STRING ,
ld_iv_start_row
 
 TYPE STRING ,
ld_ev_switch_id
 
 TYPE SFW_SWITCHID ,
ld_iv_start_col
 
 TYPE STRING ,
ld_ev_switch_reaction
 
 TYPE SFW_SHOWHIDE .


ld_iv_persistence = 'Check type of data required'.
ld_iv_start_row = 'some text here'.
ld_iv_start_col = 'some text here'.