SAP BBPU_F4_HELP_SYSTEM Function Module for
BBPU_F4_HELP_SYSTEM is a standard bbpu f4 help system 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 bbpu f4 help system FM, simply by entering the name BBPU_F4_HELP_SYSTEM into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_UTILITIES_1
Program Name: SAPLBBP_UTILITIES_1
Main Program: SAPLBBP_UTILITIES_1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBPU_F4_HELP_SYSTEM 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 'BBPU_F4_HELP_SYSTEM'".
IMPORTING
SELECTED_VALUE = "
EXCEPTIONS
NO_SYSTEM_VALUE_SELECTED = 1 NO_SYSTEMS_AVAILABLE = 2
EXPORTING Parameters details for BBPU_F4_HELP_SYSTEM
SELECTED_VALUE -
Data type: RFCDES-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SYSTEM_VALUE_SELECTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SYSTEMS_AVAILABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBPU_F4_HELP_SYSTEM 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_selected_value | TYPE RFCDES-RFCDEST, " | |||
| lv_no_system_value_selected | TYPE RFCDES, " | |||
| lv_no_systems_available | TYPE RFCDES. " |
|   CALL FUNCTION 'BBPU_F4_HELP_SYSTEM' " |
| IMPORTING | ||
| SELECTED_VALUE | = lv_selected_value | |
| EXCEPTIONS | ||
| NO_SYSTEM_VALUE_SELECTED = 1 | ||
| NO_SYSTEMS_AVAILABLE = 2 | ||
| . " BBPU_F4_HELP_SYSTEM | ||
ABAP code using 7.40 inline data declarations to call FM BBPU_F4_HELP_SYSTEM
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 RFCDEST FROM RFCDES INTO @DATA(ld_selected_value). | ||||
Search for further information about these or an SAP related objects