SAP FVD_REPAY_MAIN Function Module for Loans: New Repayment
FVD_REPAY_MAIN is a standard fvd repay main SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Loans: New Repayment 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 main FM, simply by entering the name FVD_REPAY_MAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVN_BUS_OPERATION
Program Name: SAPLFVN_BUS_OPERATION
Main Program: SAPLFVN_BUS_OPERATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_REPAY_MAIN 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_MAIN'"Loans: New Repayment.
EXPORTING
I_VDARL_KEY = "VDARL Schlussel-Struktur
* I_RBO = "Business operation number (loans)
* I_MODUS = 'D' "Mode for Payoff Data
* I_TEMPLATE = "Template Key
* I_FLG_CONFIRMATION = ' ' "Aufruf aus der Freigabe
* I_FLG_FOREIGN_CALL = 'X' "Single-Character Flag
I_BO_CAT = "Geschäftsvorfalltyp
* I_ROLLOVER_CALL = "Aufruf aus Prolongation
* I_COPY = "Bestehenden GV kopieren
EXCEPTIONS
LOAN_INVALID = 1 BO_INVALID = 2 LOG_HEADER_INCONSISTENT = 3 OTHERS = 4
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_SAPLFVN_BUS_OPERATION_001 Customer Functions for SAPLFvn_bus_operation
EXIT_SAPLFVN_BUS_OPERATION_101 Additional Data for FN8D
EXIT_SAPLFVN_BUS_OPERATION_102 User Exit for ZUONR and RSOLL
EXIT_SAPLFVN_BUS_OPERATION_500 Customer Function for Determining Country
IMPORTING Parameters details for FVD_REPAY_MAIN
I_VDARL_KEY - VDARL Schlussel-Struktur
Data type: VDARL_KEYOptional: No
Call by Reference: Yes
I_RBO - Business operation number (loans)
Data type: RBOOptional: Yes
Call by Reference: Yes
I_MODUS - Mode for Payoff Data
Data type: TB_REPAY_MODUSDefault: 'D'
Optional: Yes
Call by Reference: Yes
I_TEMPLATE - Template Key
Data type: TDREPAY_TEMPL-RTEMPLATEOptional: Yes
Call by Reference: Yes
I_FLG_CONFIRMATION - Aufruf aus der Freigabe
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
I_FLG_FOREIGN_CALL - Single-Character Flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: Yes
I_BO_CAT - Geschäftsvorfalltyp
Data type: SBO_CATOptional: No
Call by Reference: Yes
I_ROLLOVER_CALL - Aufruf aus Prolongation
Data type: FLAGOptional: Yes
Call by Reference: Yes
I_COPY - Bestehenden GV kopieren
Data type: FLAGOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
LOAN_INVALID - Darlehen nicht vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BO_INVALID - Geschäftsvorfallnummer nicht vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOG_HEADER_INCONSISTENT -
Data type:Optional: No
Call by Reference: Yes
OTHERS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_REPAY_MAIN 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_vdarl_key | TYPE VDARL_KEY, " | |||
| lv_loan_invalid | TYPE VDARL_KEY, " | |||
| lv_i_rbo | TYPE RBO, " | |||
| lv_bo_invalid | TYPE RBO, " | |||
| lv_i_modus | TYPE TB_REPAY_MODUS, " 'D' | |||
| lv_log_header_inconsistent | TYPE TB_REPAY_MODUS, " | |||
| lv_others | TYPE TB_REPAY_MODUS, " | |||
| lv_i_template | TYPE TDREPAY_TEMPL-RTEMPLATE, " | |||
| lv_i_flg_confirmation | TYPE CHAR1, " SPACE | |||
| lv_i_flg_foreign_call | TYPE CHAR1, " 'X' | |||
| lv_i_bo_cat | TYPE SBO_CAT, " | |||
| lv_i_rollover_call | TYPE FLAG, " | |||
| lv_i_copy | TYPE FLAG. " |
|   CALL FUNCTION 'FVD_REPAY_MAIN' "Loans: New Repayment |
| EXPORTING | ||
| I_VDARL_KEY | = lv_i_vdarl_key | |
| I_RBO | = lv_i_rbo | |
| I_MODUS | = lv_i_modus | |
| I_TEMPLATE | = lv_i_template | |
| I_FLG_CONFIRMATION | = lv_i_flg_confirmation | |
| I_FLG_FOREIGN_CALL | = lv_i_flg_foreign_call | |
| I_BO_CAT | = lv_i_bo_cat | |
| I_ROLLOVER_CALL | = lv_i_rollover_call | |
| I_COPY | = lv_i_copy | |
| EXCEPTIONS | ||
| LOAN_INVALID = 1 | ||
| BO_INVALID = 2 | ||
| LOG_HEADER_INCONSISTENT = 3 | ||
| OTHERS = 4 | ||
| . " FVD_REPAY_MAIN | ||
ABAP code using 7.40 inline data declarations to call FM FVD_REPAY_MAIN
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_modus) | = 'D'. | |||
| "SELECT single RTEMPLATE FROM TDREPAY_TEMPL INTO @DATA(ld_i_template). | ||||
| DATA(ld_i_flg_confirmation) | = ' '. | |||
| DATA(ld_i_flg_foreign_call) | = 'X'. | |||
Search for further information about these or an SAP related objects