SAP UPB_PARAM_OK_CODE Function Module for
UPB_PARAM_OK_CODE is a standard upb param ok code 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 upb param ok code FM, simply by entering the name UPB_PARAM_OK_CODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPBE
Program Name: SAPLUPBE
Main Program: SAPLUPBE
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPB_PARAM_OK_CODE 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 'UPB_PARAM_OK_CODE'".
EXPORTING
I_OK_CODE = "
IMPORTING
E_REPID = "
E_DYNNR = "
EXCEPTIONS
NO_PARAM_OK_CODE = 1
IMPORTING Parameters details for UPB_PARAM_OK_CODE
I_OK_CODE -
Data type: SY-UCOMMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UPB_PARAM_OK_CODE
E_REPID -
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
E_DYNNR -
Data type: SY-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_PARAM_OK_CODE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPB_PARAM_OK_CODE 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_e_repid | TYPE SY-REPID, " | |||
| lv_i_ok_code | TYPE SY-UCOMM, " | |||
| lv_no_param_ok_code | TYPE SY, " | |||
| lv_e_dynnr | TYPE SY-DYNNR. " |
|   CALL FUNCTION 'UPB_PARAM_OK_CODE' " |
| EXPORTING | ||
| I_OK_CODE | = lv_i_ok_code | |
| IMPORTING | ||
| E_REPID | = lv_e_repid | |
| E_DYNNR | = lv_e_dynnr | |
| EXCEPTIONS | ||
| NO_PARAM_OK_CODE = 1 | ||
| . " UPB_PARAM_OK_CODE | ||
ABAP code using 7.40 inline data declarations to call FM UPB_PARAM_OK_CODE
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 REPID FROM SY INTO @DATA(ld_e_repid). | ||||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_i_ok_code). | ||||
| "SELECT single DYNNR FROM SY INTO @DATA(ld_e_dynnr). | ||||
Search for further information about these or an SAP related objects