SAP RELM_GUI_LREM_CHG_PBO Function Module for
RELM_GUI_LREM_CHG_PBO is a standard relm gui lrem chg pbo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for relm gui lrem chg pbo FM, simply by entering the name RELM_GUI_LREM_CHG_PBO into the relevant SAP transaction such as SE37 or SE38.
Function Group: RELM_GUI_LREM_CHG
Program Name: SAPLRELM_GUI_LREM_CHG
Main Program: SAPLRELM_GUI_LREM_CHG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RELM_GUI_LREM_CHG_PBO pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'RELM_GUI_LREM_CHG_PBO'".
EXPORTING
IO_LR_EM_CHANGE_MNGR = "Rights and Easements: Changes
ID_SECTYPE = "Type of Section in Land Register
ID_CHGNO = "Changes: Change Number
* IF_READONLY = ABAP_FALSE "
* IO_NAVIGATION_DATA = "Possible Navigation Data
* IO_CURRENT_NAV_DATA = "
IMPORTING
ES_SUBSCREEN = "Screen
IMPORTING Parameters details for RELM_GUI_LREM_CHG_PBO
IO_LR_EM_CHANGE_MNGR - Rights and Easements: Changes
Data type: IF_RELM_LR_EM_CHANGE_MNGROptional: No
Call by Reference: Yes
ID_SECTYPE - Type of Section in Land Register
Data type: RELM_LR_EM_CHANGE-SECTYPEOptional: No
Call by Reference: Yes
ID_CHGNO - Changes: Change Number
Data type: RELM_LR_EM_CHANGE-CHGNOOptional: No
Call by Reference: Yes
IF_READONLY -
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IO_NAVIGATION_DATA - Possible Navigation Data
Data type: CL_RECA_DATA_CONTAINEROptional: Yes
Call by Reference: Yes
IO_CURRENT_NAV_DATA -
Data type: CL_RECA_DATA_CONTAINEROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RELM_GUI_LREM_CHG_PBO
ES_SUBSCREEN - Screen
Data type: RECASCREENOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RELM_GUI_LREM_CHG_PBO Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_es_subscreen | TYPE RECASCREEN, " | |||
| lv_io_lr_em_change_mngr | TYPE IF_RELM_LR_EM_CHANGE_MNGR, " | |||
| lv_id_sectype | TYPE RELM_LR_EM_CHANGE-SECTYPE, " | |||
| lv_id_chgno | TYPE RELM_LR_EM_CHANGE-CHGNO, " | |||
| lv_if_readonly | TYPE ABAP_BOOL, " ABAP_FALSE | |||
| lv_io_navigation_data | TYPE CL_RECA_DATA_CONTAINER, " | |||
| lv_io_current_nav_data | TYPE CL_RECA_DATA_CONTAINER. " |
|   CALL FUNCTION 'RELM_GUI_LREM_CHG_PBO' " |
| EXPORTING | ||
| IO_LR_EM_CHANGE_MNGR | = lv_io_lr_em_change_mngr | |
| ID_SECTYPE | = lv_id_sectype | |
| ID_CHGNO | = lv_id_chgno | |
| IF_READONLY | = lv_if_readonly | |
| IO_NAVIGATION_DATA | = lv_io_navigation_data | |
| IO_CURRENT_NAV_DATA | = lv_io_current_nav_data | |
| IMPORTING | ||
| ES_SUBSCREEN | = lv_es_subscreen | |
| . " RELM_GUI_LREM_CHG_PBO | ||
ABAP code using 7.40 inline data declarations to call FM RELM_GUI_LREM_CHG_PBO
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single SECTYPE FROM RELM_LR_EM_CHANGE INTO @DATA(ld_id_sectype). | ||||
| "SELECT single CHGNO FROM RELM_LR_EM_CHANGE INTO @DATA(ld_id_chgno). | ||||
| DATA(ld_if_readonly) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects