SAP DPVMSUI02_MODIFY_FUNCTN Function Module for VMS DP : Modify Functions in table DPVMSC_FUNCTN
DPVMSUI02_MODIFY_FUNCTN is a standard dpvmsui02 modify functn SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for VMS DP : Modify Functions in table DPVMSC_FUNCTN 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 dpvmsui02 modify functn FM, simply by entering the name DPVMSUI02_MODIFY_FUNCTN into the relevant SAP transaction such as SE37 or SE38.
Function Group: DPVMSUI02
Program Name: SAPLDPVMSUI02
Main Program: SAPLDPVMSUI02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DPVMSUI02_MODIFY_FUNCTN 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 'DPVMSUI02_MODIFY_FUNCTN'"VMS DP : Modify Functions in table DPVMSC_FUNCTN.
EXPORTING
IT_FUNCTION = "Table of Functions
EXCEPTIONS
ENTRY_NOT_EXIST = 1
IMPORTING Parameters details for DPVMSUI02_MODIFY_FUNCTN
IT_FUNCTION - Table of Functions
Data type: DPVMSC_FUNCTN_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
ENTRY_NOT_EXIST - Table entry doens't exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DPVMSUI02_MODIFY_FUNCTN 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_it_function | TYPE DPVMSC_FUNCTN_T, " | |||
| lv_entry_not_exist | TYPE DPVMSC_FUNCTN_T. " |
|   CALL FUNCTION 'DPVMSUI02_MODIFY_FUNCTN' "VMS DP : Modify Functions in table DPVMSC_FUNCTN |
| EXPORTING | ||
| IT_FUNCTION | = lv_it_function | |
| EXCEPTIONS | ||
| ENTRY_NOT_EXIST = 1 | ||
| . " DPVMSUI02_MODIFY_FUNCTN | ||
ABAP code using 7.40 inline data declarations to call FM DPVMSUI02_MODIFY_FUNCTN
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