SAP REYC_GUI_EXPPOOL_PBO Function Module for PBO Expense Pool Details Screen
REYC_GUI_EXPPOOL_PBO is a standard reyc gui exppool 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 Expense Pool Details 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 reyc gui exppool pbo FM, simply by entering the name REYC_GUI_EXPPOOL_PBO into the relevant SAP transaction such as SE37 or SE38.
Function Group: REYC_GUI_EXPPOOL
Program Name: SAPLREYC_GUI_EXPPOOL
Main Program: SAPLREYC_GUI_EXPPOOL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REYC_GUI_EXPPOOL_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 'REYC_GUI_EXPPOOL_PBO'"PBO Expense Pool Details Screen.
EXPORTING
IO_OBJ_ASSIGN_MNGR = "Expense Pool
ID_OBJASSKEY = "Internal Key of Real Estate CAM Expense Pool
* IF_READONLY = ABAP_FALSE "
* IF_FIRST_TAB = ABAP_FALSE "
* IO_NAVIGATION_DATA = "
* IO_CURRENT_NAV_DATA = "
IMPORTING
ES_SUBSCREEN = "
IMPORTING Parameters details for REYC_GUI_EXPPOOL_PBO
IO_OBJ_ASSIGN_MNGR - Expense Pool
Data type: IF_REYC_EXPPOOL_ASSIGN_MNGROptional: No
Call by Reference: Yes
ID_OBJASSKEY - Internal Key of Real Estate CAM Expense Pool
Data type: REYC_EXPPOOL-KEYOptional: No
Call by Reference: Yes
IF_READONLY -
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IF_FIRST_TAB -
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IO_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 REYC_GUI_EXPPOOL_PBO
ES_SUBSCREEN -
Data type: RECASCREENOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for REYC_GUI_EXPPOOL_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_obj_assign_mngr | TYPE IF_REYC_EXPPOOL_ASSIGN_MNGR, " | |||
| lv_id_objasskey | TYPE REYC_EXPPOOL-KEY, " | |||
| lv_if_readonly | TYPE ABAP_BOOL, " ABAP_FALSE | |||
| lv_if_first_tab | 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 'REYC_GUI_EXPPOOL_PBO' "PBO Expense Pool Details Screen |
| EXPORTING | ||
| IO_OBJ_ASSIGN_MNGR | = lv_io_obj_assign_mngr | |
| ID_OBJASSKEY | = lv_id_objasskey | |
| IF_READONLY | = lv_if_readonly | |
| IF_FIRST_TAB | = lv_if_first_tab | |
| IO_NAVIGATION_DATA | = lv_io_navigation_data | |
| IO_CURRENT_NAV_DATA | = lv_io_current_nav_data | |
| IMPORTING | ||
| ES_SUBSCREEN | = lv_es_subscreen | |
| . " REYC_GUI_EXPPOOL_PBO | ||
ABAP code using 7.40 inline data declarations to call FM REYC_GUI_EXPPOOL_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 KEY FROM REYC_EXPPOOL INTO @DATA(ld_id_objasskey). | ||||
| DATA(ld_if_readonly) | = ABAP_FALSE. | |||
| DATA(ld_if_first_tab) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects