SAP MDS_CMPT_UPDATE_DATASET Function Module for Update the datasets for a particular user
MDS_CMPT_UPDATE_DATASET is a standard mds cmpt update dataset SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update the datasets for a particular user 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 mds cmpt update dataset FM, simply by entering the name MDS_CMPT_UPDATE_DATASET into the relevant SAP transaction such as SE37 or SE38.
Function Group: MDS_CMPT_COMPARISON
Program Name: SAPLMDS_CMPT_COMPARISON
Main Program: SAPLMDS_CMPT_COMPARISON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MDS_CMPT_UPDATE_DATASET 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 'MDS_CMPT_UPDATE_DATASET'"Update the datasets for a particular user.
EXPORTING
IT_DATASET_VALUES = "User Datasets
EXCEPTIONS
INSERTION_ERROR = 1 UPDATION_ERROR = 2
IMPORTING Parameters details for MDS_CMPT_UPDATE_DATASET
IT_DATASET_VALUES - User Datasets
Data type: MDS_CMPT_USER_DATASET_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
INSERTION_ERROR -
Data type:Optional: No
Call by Reference: Yes
UPDATION_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MDS_CMPT_UPDATE_DATASET 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_insertion_error | TYPE STRING, " | |||
| lv_it_dataset_values | TYPE MDS_CMPT_USER_DATASET_T, " | |||
| lv_updation_error | TYPE MDS_CMPT_USER_DATASET_T. " |
|   CALL FUNCTION 'MDS_CMPT_UPDATE_DATASET' "Update the datasets for a particular user |
| EXPORTING | ||
| IT_DATASET_VALUES | = lv_it_dataset_values | |
| EXCEPTIONS | ||
| INSERTION_ERROR = 1 | ||
| UPDATION_ERROR = 2 | ||
| . " MDS_CMPT_UPDATE_DATASET | ||
ABAP code using 7.40 inline data declarations to call FM MDS_CMPT_UPDATE_DATASET
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