SAP REXC_GUI_IMU_PBO Function Module for PBO for IMU detail-screen









REXC_GUI_IMU_PBO is a standard rexc gui imu pbo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PBO for IMU detail-screen 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 rexc gui imu pbo FM, simply by entering the name REXC_GUI_IMU_PBO into the relevant SAP transaction such as SE37 or SE38.

Function Group: REXC_GUI_IMU
Program Name: SAPLREXC_GUI_IMU
Main Program: SAPLREXC_GUI_IMU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function REXC_GUI_IMU_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 'REXC_GUI_IMU_PBO'"PBO for IMU detail-screen
EXPORTING
IO_IMU_MNGR = "IMU class
ID_DATEFROM = "Internal Key of Real Estate Object
* IF_READONLY = ABAP_FALSE "
* IO_NAVIGATION_DATA = "
* IO_CURRENT_NAV_DATA = "

IMPORTING
ES_SUBSCREEN = "
.



IMPORTING Parameters details for REXC_GUI_IMU_PBO

IO_IMU_MNGR - IMU class

Data type: CL_REXC_IT_IMU_DATA
Optional: No
Call by Reference: Yes

ID_DATEFROM - Internal Key of Real Estate Object

Data type: REXCITIMU_S-DATEFROM
Optional: No
Call by Reference: Yes

IF_READONLY -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

IO_NAVIGATION_DATA -

Data type: CL_RECA_DATA_CONTAINER
Optional: Yes
Call by Reference: Yes

IO_CURRENT_NAV_DATA -

Data type: CL_RECA_DATA_CONTAINER
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for REXC_GUI_IMU_PBO

ES_SUBSCREEN -

Data type: RECASCREEN
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for REXC_GUI_IMU_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_io_imu_mngr  TYPE CL_REXC_IT_IMU_DATA, "   
lv_es_subscreen  TYPE RECASCREEN, "   
lv_id_datefrom  TYPE REXCITIMU_S-DATEFROM, "   
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 'REXC_GUI_IMU_PBO'  "PBO for IMU detail-screen
    EXPORTING
         IO_IMU_MNGR = lv_io_imu_mngr
         ID_DATEFROM = lv_id_datefrom
         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
. " REXC_GUI_IMU_PBO




ABAP code using 7.40 inline data declarations to call FM REXC_GUI_IMU_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 DATEFROM FROM REXCITIMU_S INTO @DATA(ld_id_datefrom).
 
DATA(ld_if_readonly) = ABAP_FALSE.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!