SAP ISU_O_ADRCITYMRU_PAI_BEFORE Function Module for INTERNAL: Prepares the CALL SUBSCREEN PAI
ISU_O_ADRCITYMRU_PAI_BEFORE is a standard isu o adrcitymru pai before SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Prepares the CALL SUBSCREEN PAI processing and below is the pattern details for this FM, 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 isu o adrcitymru pai before FM, simply by entering the name ISU_O_ADRCITYMRU_PAI_BEFORE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ER11
Program Name: SAPLER11
Main Program: SAPLER11
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_O_ADRCITYMRU_PAI_BEFORE 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 'ISU_O_ADRCITYMRU_PAI_BEFORE'"INTERNAL: Prepares the CALL SUBSCREEN PAI.
EXPORTING
X_SUB_OBJ = "
X_ADRCITYD = "Screen data
IMPORTING Parameters details for ISU_O_ADRCITYMRU_PAI_BEFORE
X_SUB_OBJ -
Data type: RS001_ADRCITY_SUBOptional: No
Call by Reference: No ( called with pass by value option)
X_ADRCITYD - Screen data
Data type: ADRCITYDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_O_ADRCITYMRU_PAI_BEFORE 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_x_sub_obj | TYPE RS001_ADRCITY_SUB, " | |||
| lv_x_adrcityd | TYPE ADRCITYD. " |
|   CALL FUNCTION 'ISU_O_ADRCITYMRU_PAI_BEFORE' "INTERNAL: Prepares the CALL SUBSCREEN PAI |
| EXPORTING | ||
| X_SUB_OBJ | = lv_x_sub_obj | |
| X_ADRCITYD | = lv_x_adrcityd | |
| . " ISU_O_ADRCITYMRU_PAI_BEFORE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_O_ADRCITYMRU_PAI_BEFORE
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.Search for further information about these or an SAP related objects