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

Function FVD_REPAY_API_DELETE 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_API_DELETE'"Delete Payoffs.
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
I_RBO = "Business operation number (loans)
* I_LOGHANDLE = "Application Log: Log Handle
* I_SIM = "
* I_NO_ENQUEUE = ' ' "Transfer Enqueue
* I_CALLN_APPLN = 'INT' "Calling Application
IMPORTING
E_LOGHANDLE = "Application Log: Log Handle
E_LOG_DATA = "Data of Application Log
E_RBO = "Business operation number (loans)
E_TAB_VDBEKI = "Table Type for Table VDBEKI
E_TAB_VDBEPI = "Table Type for Table VDBEPI
EXCEPTIONS
NOT_DELETED = 1 FAILED = 2
IMPORTING Parameters details for FVD_REPAY_API_DELETE
I_BUKRS - Company Code
Data type: VDARL-BUKRSOptional: No
Call by Reference: Yes
I_RANL - Contract Number
Data type: VDARL-RANLOptional: No
Call by Reference: Yes
I_RBO - Business operation number (loans)
Data type: VDBOHEAD-RBOOptional: No
Call by Reference: Yes
I_LOGHANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
I_SIM -
Data type: COptional: Yes
Call by Reference: Yes
I_NO_ENQUEUE - Transfer Enqueue
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_CALLN_APPLN - Calling Application
Data type: TB_CALLNG_APPLNDefault: 'INT'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_REPAY_API_DELETE
E_LOGHANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
E_LOG_DATA - Data of Application Log
Data type: FVD_TYP_LOG_DATAOptional: No
Call by Reference: Yes
E_RBO - Business operation number (loans)
Data type: VDBOHEAD-RBOOptional: No
Call by Reference: Yes
E_TAB_VDBEKI - Table Type for Table VDBEKI
Data type: TRTY_VDBEKIOptional: No
Call by Reference: Yes
E_TAB_VDBEPI - Table Type for Table VDBEPI
Data type: TRTY_VDBEPIOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_DELETED - Payoff Not Posted
Data type:Optional: No
Call by Reference: Yes
FAILED - Authority Check Failed for Structured Finance
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_REPAY_API_DELETE 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_bukrs | TYPE VDARL-BUKRS, " | |||
| lv_e_loghandle | TYPE BALLOGHNDL, " | |||
| lv_not_deleted | TYPE BALLOGHNDL, " | |||
| lv_failed | TYPE BALLOGHNDL, " | |||
| lv_i_ranl | TYPE VDARL-RANL, " | |||
| lv_e_log_data | TYPE FVD_TYP_LOG_DATA, " | |||
| lv_e_rbo | TYPE VDBOHEAD-RBO, " | |||
| lv_i_rbo | TYPE VDBOHEAD-RBO, " | |||
| lv_i_loghandle | TYPE BALLOGHNDL, " | |||
| lv_e_tab_vdbeki | TYPE TRTY_VDBEKI, " | |||
| lv_i_sim | TYPE C, " | |||
| lv_e_tab_vdbepi | TYPE TRTY_VDBEPI, " | |||
| lv_i_no_enqueue | TYPE FLAG, " SPACE | |||
| lv_i_calln_appln | TYPE TB_CALLNG_APPLN. " 'INT' |
|   CALL FUNCTION 'FVD_REPAY_API_DELETE' "Delete Payoffs |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_RBO | = lv_i_rbo | |
| I_LOGHANDLE | = lv_i_loghandle | |
| I_SIM | = lv_i_sim | |
| I_NO_ENQUEUE | = lv_i_no_enqueue | |
| I_CALLN_APPLN | = lv_i_calln_appln | |
| IMPORTING | ||
| E_LOGHANDLE | = lv_e_loghandle | |
| E_LOG_DATA | = lv_e_log_data | |
| E_RBO | = lv_e_rbo | |
| E_TAB_VDBEKI | = lv_e_tab_vdbeki | |
| E_TAB_VDBEPI | = lv_e_tab_vdbepi | |
| EXCEPTIONS | ||
| NOT_DELETED = 1 | ||
| FAILED = 2 | ||
| . " FVD_REPAY_API_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_REPAY_API_DELETE
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 BUKRS FROM VDARL INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RANL FROM VDARL INTO @DATA(ld_i_ranl). | ||||
| "SELECT single RBO FROM VDBOHEAD INTO @DATA(ld_e_rbo). | ||||
| "SELECT single RBO FROM VDBOHEAD INTO @DATA(ld_i_rbo). | ||||
| DATA(ld_i_no_enqueue) | = ' '. | |||
| DATA(ld_i_calln_appln) | = 'INT'. | |||
Search for further information about these or an SAP related objects