SAP FVD_REPAY_UI_PROCESS_UCOMM Function Module for Payoff: Function Code Handling









FVD_REPAY_UI_PROCESS_UCOMM is a standard fvd repay 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 Payoff: Function Code Handling 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 repay ui process ucomm FM, simply by entering the name FVD_REPAY_UI_PROCESS_UCOMM into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVD_REPAY_UI
Program Name: SAPLFVD_REPAY_UI
Main Program: SAPLFVD_REPAY_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FVD_REPAY_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_REPAY_UI_PROCESS_UCOMM'"Payoff: Function Code Handling
EXPORTING
I_OKCODE = "Screens, Function Code That Triggered PAI
I_BOCAT = "Business Operation Category
* I_WAIT = ' ' "Single-Character Flag

IMPORTING
E_FLG_UCOMM_USED = "Boolean Variable (X=true, -=false, space=unknown)
E_OKCODE = "Screens, Function Code That Triggered PAI
E_CHANGES = "Single-Character Flag
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFVD_REPAY_UI_001 Transfer User Data to Subscreen (Administration Data)
EXIT_SAPLFVD_REPAY_UI_002 Transfer User Data from Subscreen (Administration Data)
EXIT_SAPLFVD_REPAY_UI_003 Activate and Name Customer Tabs
EXIT_SAPLFVD_REPAY_UI_004 Transfer User Data to Subscreen (Customer Tab 1)
EXIT_SAPLFVD_REPAY_UI_005 Transfer User Data From Subscreen (Customer Tab 1)
EXIT_SAPLFVD_REPAY_UI_006 Transfer User Data to Subscreen (Customer Tab 2)
EXIT_SAPLFVD_REPAY_UI_007 Transfer User Data from Subscreen (Customer Tab 2)
EXIT_SAPLFVD_REPAY_UI_008 Transfer User Data to Subscreen (Customer Tab 3)
EXIT_SAPLFVD_REPAY_UI_009 Transfer User Data from Subscreen (Customer Tab 3)
EXIT_SAPLFVD_REPAY_UI_010 User Exit for Additional Data in the Item Overview

IMPORTING Parameters details for FVD_REPAY_UI_PROCESS_UCOMM

I_OKCODE - Screens, Function Code That Triggered PAI

Data type: SYUCOMM
Optional: No
Call by Reference: Yes

I_BOCAT - Business Operation Category

Data type: SBO_CAT
Optional: No
Call by Reference: Yes

I_WAIT - Single-Character Flag

Data type: CHAR1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FVD_REPAY_UI_PROCESS_UCOMM

E_FLG_UCOMM_USED - Boolean Variable (X=true, -=false, space=unknown)

Data type: BOOLEAN
Optional: No
Call by Reference: Yes

E_OKCODE - Screens, Function Code That Triggered PAI

Data type: SYUCOMM
Optional: No
Call by Reference: Yes

E_CHANGES - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_REPAY_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_flg_ucomm_used  TYPE BOOLEAN, "   
lv_i_bocat  TYPE SBO_CAT, "   
lv_e_okcode  TYPE SYUCOMM, "   
lv_i_wait  TYPE CHAR1, "   SPACE
lv_e_changes  TYPE CHAR1. "   

  CALL FUNCTION 'FVD_REPAY_UI_PROCESS_UCOMM'  "Payoff: Function Code Handling
    EXPORTING
         I_OKCODE = lv_i_okcode
         I_BOCAT = lv_i_bocat
         I_WAIT = lv_i_wait
    IMPORTING
         E_FLG_UCOMM_USED = lv_e_flg_ucomm_used
         E_OKCODE = lv_e_okcode
         E_CHANGES = lv_e_changes
. " FVD_REPAY_UI_PROCESS_UCOMM




ABAP code using 7.40 inline data declarations to call FM FVD_REPAY_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.

 
 
 
 
DATA(ld_i_wait) = ' '.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!