SAP REBD_GUI_OCCUPANCY_PBO Function Module for Calls Maintenance Dialog for Occupancy
REBD_GUI_OCCUPANCY_PBO is a standard rebd gui occupancy 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 Calls Maintenance Dialog for Occupancy 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 rebd gui occupancy pbo FM, simply by entering the name REBD_GUI_OCCUPANCY_PBO into the relevant SAP transaction such as SE37 or SE38.
Function Group: REBD_GUI_OCCUPANCY
Program Name: SAPLREBD_GUI_OCCUPANCY
Main Program: SAPLREBD_GUI_OCCUPANCY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REBD_GUI_OCCUPANCY_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 'REBD_GUI_OCCUPANCY_PBO'"Calls Maintenance Dialog for Occupancy.
EXPORTING
IO_BUSOBJ = "Business Object
IMPORTING
ES_SUBSCREEN = "Screen
IMPORTING Parameters details for REBD_GUI_OCCUPANCY_PBO
IO_BUSOBJ - Business Object
Data type: IF_REBD_HAS_OCCUPANCYOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for REBD_GUI_OCCUPANCY_PBO
ES_SUBSCREEN - Screen
Data type: RECASCREENOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for REBD_GUI_OCCUPANCY_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_busobj | TYPE IF_REBD_HAS_OCCUPANCY, " | |||
| lv_es_subscreen | TYPE RECASCREEN. " |
|   CALL FUNCTION 'REBD_GUI_OCCUPANCY_PBO' "Calls Maintenance Dialog for Occupancy |
| EXPORTING | ||
| IO_BUSOBJ | = lv_io_busobj | |
| IMPORTING | ||
| ES_SUBSCREEN | = lv_es_subscreen | |
| . " REBD_GUI_OCCUPANCY_PBO | ||
ABAP code using 7.40 inline data declarations to call FM REBD_GUI_OCCUPANCY_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.Search for further information about these or an SAP related objects