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

Function FVD_REPAY_OL_CHECK_CONDITIONS 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_OL_CHECK_CONDITIONS'"Determine Payoff Conditions.
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
I_SKOGRP = "Condition Group
I_VZZKOPO = "Condition Items Table
IMPORTING
E_FLG_REPAYMENT_CONDITION = "Single-Character Flag
EXCEPTIONS
REPAYMENT_CONDITION = 1 NOT_FOUND = 2 KEY_NOT_FILLED = 3
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_OL_001 User Exit for Flow Data
EXIT_SAPLFVD_REPAY_OL_002 User Exit for Amounts
EXIT_SAPLFVD_REPAY_OL_003 User Exit: Plausiblity Check for Payoff Data
EXIT_SAPLFVD_REPAY_OL_004 User Exit Flow Type Determination
EXIT_SAPLFVD_REPAY_OL_005 User Exit Transfer of all Relevant Data
IMPORTING Parameters details for FVD_REPAY_OL_CHECK_CONDITIONS
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_SKOGRP - Condition Group
Data type: TZPA-SKOGRPOptional: No
Call by Reference: Yes
I_VZZKOPO - Condition Items Table
Data type: VZZKOPOOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FVD_REPAY_OL_CHECK_CONDITIONS
E_FLG_REPAYMENT_CONDITION - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EXCEPTIONS details
REPAYMENT_CONDITION - Payoff Condition
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND - No Payoffs Exist
Data type:Optional: No
Call by Reference: Yes
KEY_NOT_FILLED - Key Parameters Are Incomplete
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_REPAY_OL_CHECK_CONDITIONS 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_repayment_condition | TYPE VDARL, " | |||
| lv_e_flg_repayment_condition | TYPE CHAR1, " | |||
| lv_i_ranl | TYPE VDARL-RANL, " | |||
| lv_not_found | TYPE VDARL, " | |||
| lv_i_skogrp | TYPE TZPA-SKOGRP, " | |||
| lv_key_not_filled | TYPE TZPA, " | |||
| lv_i_vzzkopo | TYPE VZZKOPO. " |
|   CALL FUNCTION 'FVD_REPAY_OL_CHECK_CONDITIONS' "Determine Payoff Conditions |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_SKOGRP | = lv_i_skogrp | |
| I_VZZKOPO | = lv_i_vzzkopo | |
| IMPORTING | ||
| E_FLG_REPAYMENT_CONDITION | = lv_e_flg_repayment_condition | |
| EXCEPTIONS | ||
| REPAYMENT_CONDITION = 1 | ||
| NOT_FOUND = 2 | ||
| KEY_NOT_FILLED = 3 | ||
| . " FVD_REPAY_OL_CHECK_CONDITIONS | ||
ABAP code using 7.40 inline data declarations to call FM FVD_REPAY_OL_CHECK_CONDITIONS
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 SKOGRP FROM TZPA INTO @DATA(ld_i_skogrp). | ||||
Search for further information about these or an SAP related objects