SAP FVD_MD_TOOLS_NORISKMS Function Module for Risk-Increasing Measures in Contract
FVD_MD_TOOLS_NORISKMS is a standard fvd md tools noriskms SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Risk-Increasing Measures in Contract 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 md tools noriskms FM, simply by entering the name FVD_MD_TOOLS_NORISKMS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_MD_TOOLS
Program Name: SAPLFVD_MD_TOOLS
Main Program: SAPLFVD_MD_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_MD_TOOLS_NORISKMS 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_MD_TOOLS_NORISKMS'"Risk-Increasing Measures in Contract.
EXPORTING
* I_BUKRS = "Company Code
* I_SARCHIV = "Archiving Category Indicator
* I_RANL = "Contract Number
* I_WRK_VDARL = "Loan
* I_TAB_VVZZKOPO = "Table Type for Table VVZZKOPO
* I_TAB_DATE_RANGE_4_CREATION = "Range for Date Values
* I_TAB_DATE_RANGE_4_DISPLAY = "Range for Date Values
* I_PERIOD_4_RISK_COUNT_CREA = "Period in Months for Allowed Number of Risk-Increasing Measures
IMPORTING
E_STR_NO_OF_RISK_INCREASES = "Number of Risk-Increasing Measures
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FVD_MD_TOOLS_NORISKMS
I_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: Yes
I_SARCHIV - Archiving Category Indicator
Data type: SARCHIVOptional: Yes
Call by Reference: Yes
I_RANL - Contract Number
Data type: RANLOptional: Yes
Call by Reference: Yes
I_WRK_VDARL - Loan
Data type: VDARLOptional: Yes
Call by Reference: Yes
I_TAB_VVZZKOPO - Table Type for Table VVZZKOPO
Data type: TRTY_VVZZKOPOOptional: Yes
Call by Reference: Yes
I_TAB_DATE_RANGE_4_CREATION - Range for Date Values
Data type: TRTY_RDATE_RANGEOptional: Yes
Call by Reference: Yes
I_TAB_DATE_RANGE_4_DISPLAY - Range for Date Values
Data type: TRTY_RDATE_RANGEOptional: Yes
Call by Reference: Yes
I_PERIOD_4_RISK_COUNT_CREA - Period in Months for Allowed Number of Risk-Increasing Measures
Data type: TB_PERIOD_4_RISKINCREASE_CREAOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FVD_MD_TOOLS_NORISKMS
E_STR_NO_OF_RISK_INCREASES - Number of Risk-Increasing Measures
Data type: RDAT_NO_OF_RISK_ADV_MEASURESOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_MD_TOOLS_NORISKMS 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_error | TYPE STRING, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_e_str_no_of_risk_increases | TYPE RDAT_NO_OF_RISK_ADV_MEASURES, " | |||
| lv_i_sarchiv | TYPE SARCHIV, " | |||
| lv_i_ranl | TYPE RANL, " | |||
| lv_i_wrk_vdarl | TYPE VDARL, " | |||
| lv_i_tab_vvzzkopo | TYPE TRTY_VVZZKOPO, " | |||
| lv_i_tab_date_range_4_creation | TYPE TRTY_RDATE_RANGE, " | |||
| lv_i_tab_date_range_4_display | TYPE TRTY_RDATE_RANGE, " | |||
| lv_i_period_4_risk_count_crea | TYPE TB_PERIOD_4_RISKINCREASE_CREA. " |
|   CALL FUNCTION 'FVD_MD_TOOLS_NORISKMS' "Risk-Increasing Measures in Contract |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_SARCHIV | = lv_i_sarchiv | |
| I_RANL | = lv_i_ranl | |
| I_WRK_VDARL | = lv_i_wrk_vdarl | |
| I_TAB_VVZZKOPO | = lv_i_tab_vvzzkopo | |
| I_TAB_DATE_RANGE_4_CREATION | = lv_i_tab_date_range_4_creation | |
| I_TAB_DATE_RANGE_4_DISPLAY | = lv_i_tab_date_range_4_display | |
| I_PERIOD_4_RISK_COUNT_CREA | = lv_i_period_4_risk_count_crea | |
| IMPORTING | ||
| E_STR_NO_OF_RISK_INCREASES | = lv_e_str_no_of_risk_increases | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FVD_MD_TOOLS_NORISKMS | ||
ABAP code using 7.40 inline data declarations to call FM FVD_MD_TOOLS_NORISKMS
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