RELM_GUI_LR_EASEMENT_PBO SAP Function module

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

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

Pattern for FM RELM_GUI_LR_EASEMENT_PBO - RELM GUI LR EASEMENT PBO

CALL FUNCTION 'RELM_GUI_LR_EASEMENT_PBO' "
  EXPORTING
    id_sectype =                " relm_lr_easement-sectype  Type of Section in Land Register
    io_lr_easement_mngr =       " if_relm_lr_easement_mngr  Land Register - Rights and Easements: Manager
    id_secno =                  " relm_lr_easement-secno  Section 1/2/3: Sequence Number of Entry
    id_secsubno =               " relm_lr_easement-secsubno  Section 1/2/3: Subentry
*   if_readonly = ABAP_FALSE    " abap_bool
*   io_navigation_data =        " cl_reca_data_container  Possible Navigation Data
*   io_current_nav_data =       " cl_reca_data_container
  IMPORTING
    es_subscreen =              " recascreen    Screen
    .  "  RELM_GUI_LR_EASEMENT_PBO

ABAP code example for Function Module RELM_GUI_LR_EASEMENT_PBO

The ABAP code below is a full code listing to execute function module RELM_GUI_LR_EASEMENT_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_id_sectype) = some text here

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


DATA(ld_id_secno) = some text here


DATA(ld_id_secsubno) = Check type of data required

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

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

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

CALL FUNCTION 'RELM_GUI_LR_EASEMENT_PBO'
  EXPORTING
    id_sectype =                 ld_id_sectype
    io_lr_easement_mngr =        ld_io_lr_easement_mngr
    id_secno =                   ld_id_secno
    id_secsubno =                ld_id_secsubno
*   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
    .  "  RELM_GUI_LR_EASEMENT_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_id_sectype
 
 TYPE RELM_LR_EASEMENT-SECTYPE ,
ld_io_lr_easement_mngr
 
 TYPE IF_RELM_LR_EASEMENT_MNGR ,
ld_id_secno
 
 TYPE RELM_LR_EASEMENT-SECNO ,
ld_id_secsubno
 
 TYPE RELM_LR_EASEMENT-SECSUBNO ,
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_id_sectype = some text here
ld_io_lr_easement_mngr = 'Check type of data required'.

ld_id_secno = some text here

ld_id_secsubno = Check type of data required
ld_if_readonly = 'Check type of data required'.
ld_io_navigation_data = 'Check type of data required'.
ld_io_current_nav_data = 'Check type of data required'.