SAP FVD_CHARGE_UI_PROCESS_UCOMM Function Module for Call OK Code Handling in BAdI
FVD_CHARGE_UI_PROCESS_UCOMM is a standard fvd charge ui process ucomm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call OK Code Handling in BAdI 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 fvd charge ui process ucomm FM, simply by entering the name FVD_CHARGE_UI_PROCESS_UCOMM into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_CHARGE_UI
Program Name: SAPLFVD_CHARGE_UI
Main Program: SAPLFVD_CHARGE_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_CHARGE_UI_PROCESS_UCOMM 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 'FVD_CHARGE_UI_PROCESS_UCOMM'"Call OK Code Handling in BAdI.
EXPORTING
I_OKCODE = "Function Code That Triggered PAI
IMPORTING
E_EXITCODE = "Function Code That Triggered PAI
E_DB_MODE = "Single-Character Flag
IMPORTING Parameters details for FVD_CHARGE_UI_PROCESS_UCOMM
I_OKCODE - Function Code That Triggered PAI
Data type: SYUCOMMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_CHARGE_UI_PROCESS_UCOMM
E_EXITCODE - Function Code That Triggered PAI
Data type: SYUCOMMOptional: No
Call by Reference: No ( called with pass by value option)
E_DB_MODE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_CHARGE_UI_PROCESS_UCOMM 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_i_okcode | TYPE SYUCOMM, " | |||
| lv_e_exitcode | TYPE SYUCOMM, " | |||
| lv_e_db_mode | TYPE CHAR1. " |
|   CALL FUNCTION 'FVD_CHARGE_UI_PROCESS_UCOMM' "Call OK Code Handling in BAdI |
| EXPORTING | ||
| I_OKCODE | = lv_i_okcode | |
| IMPORTING | ||
| E_EXITCODE | = lv_e_exitcode | |
| E_DB_MODE | = lv_e_db_mode | |
| . " FVD_CHARGE_UI_PROCESS_UCOMM | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CHARGE_UI_PROCESS_UCOMM
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