SAP /CLMDV/CLUSTER_DATA Function Module for For cluster Data Fetching
/CLMDV/CLUSTER_DATA is a standard /clmdv/cluster data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for For cluster Data Fetching 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 /clmdv/cluster data FM, simply by entering the name /CLMDV/CLUSTER_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: /CLMDV/EXT_DVF
Program Name: /CLMDV/SAPLEXT_DVF
Main Program: /CLMDV/SAPLEXT_DVF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /CLMDV/CLUSTER_DATA 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 '/CLMDV/CLUSTER_DATA'"For cluster Data Fetching.
EXPORTING
* IV_PROJECT_UUID = "Global Unique ID for table
* IV_PROJECT_ID = "DVF Project ID
* IV_SIMULATION = "Boolean Variable (X = True, - = False, Space = Unknown)
* IV_EXTRACTION = "Boolean Variable (X = True, - = False, Space = Unknown)
* IV_EVALUATION = "Boolean Variable (X = True, - = False, Space = Unknown)
IMPORTING
ET_CLUSTER_SML = "For Cluster data - Simulation
ET_TEST_SPEC = "Test Spec Details
ET_CLUSTER_EXT = "For Cluster data - Extraction
ET_CLUSTER_EVL = "For Cluster data - Evaluation
IMPORTING Parameters details for /CLMDV/CLUSTER_DATA
IV_PROJECT_UUID - Global Unique ID for table
Data type: UUIDOptional: Yes
Call by Reference: Yes
IV_PROJECT_ID - DVF Project ID
Data type: /CLMDV/EXT_PROJ_IDOptional: Yes
Call by Reference: Yes
IV_SIMULATION - Boolean Variable (X = True, - = False, Space = Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
IV_EXTRACTION - Boolean Variable (X = True, - = False, Space = Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
IV_EVALUATION - Boolean Variable (X = True, - = False, Space = Unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for /CLMDV/CLUSTER_DATA
ET_CLUSTER_SML - For Cluster data - Simulation
Data type: /CLMDV/TT_CLUSTEROptional: No
Call by Reference: Yes
ET_TEST_SPEC - Test Spec Details
Data type: /CLMDV/TT_TEST_SPECOptional: No
Call by Reference: Yes
ET_CLUSTER_EXT - For Cluster data - Extraction
Data type: /CLMDV/TT_CLUSTEROptional: No
Call by Reference: Yes
ET_CLUSTER_EVL - For Cluster data - Evaluation
Data type: /CLMDV/TT_CLUSTEROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /CLMDV/CLUSTER_DATA 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_et_cluster_sml | TYPE /CLMDV/TT_CLUSTER, " | |||
| lv_iv_project_uuid | TYPE UUID, " | |||
| lv_et_test_spec | TYPE /CLMDV/TT_TEST_SPEC, " | |||
| lv_iv_project_id | TYPE /CLMDV/EXT_PROJ_ID, " | |||
| lv_iv_simulation | TYPE BOOLEAN, " | |||
| lv_et_cluster_ext | TYPE /CLMDV/TT_CLUSTER, " | |||
| lv_iv_extraction | TYPE BOOLEAN, " | |||
| lv_et_cluster_evl | TYPE /CLMDV/TT_CLUSTER, " | |||
| lv_iv_evaluation | TYPE BOOLEAN. " |
|   CALL FUNCTION '/CLMDV/CLUSTER_DATA' "For cluster Data Fetching |
| EXPORTING | ||
| IV_PROJECT_UUID | = lv_iv_project_uuid | |
| IV_PROJECT_ID | = lv_iv_project_id | |
| IV_SIMULATION | = lv_iv_simulation | |
| IV_EXTRACTION | = lv_iv_extraction | |
| IV_EVALUATION | = lv_iv_evaluation | |
| IMPORTING | ||
| ET_CLUSTER_SML | = lv_et_cluster_sml | |
| ET_TEST_SPEC | = lv_et_test_spec | |
| ET_CLUSTER_EXT | = lv_et_cluster_ext | |
| ET_CLUSTER_EVL | = lv_et_cluster_evl | |
| . " /CLMDV/CLUSTER_DATA | ||
ABAP code using 7.40 inline data declarations to call FM /CLMDV/CLUSTER_DATA
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