SAP DMC_GENERIC_CLUSTER_EXPORT_JS Function Module for JEST Read write Function Module
DMC_GENERIC_CLUSTER_EXPORT_JS is a standard dmc generic cluster export js SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for JEST Read write Function Module 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 dmc generic cluster export js FM, simply by entering the name DMC_GENERIC_CLUSTER_EXPORT_JS into the relevant SAP transaction such as SE37 or SE38.
Function Group: DMC_GENERIC_READ_WRITE_JS
Program Name: SAPLDMC_GENERIC_READ_WRITE_JS
Main Program: SAPLDMC_GENERIC_READ_WRITE_JS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DMC_GENERIC_CLUSTER_EXPORT_JS 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 'DMC_GENERIC_CLUSTER_EXPORT_JS'"JEST Read write Function Module.
EXPORTING
* I_NO_CLUSTER_FILL = '-' "Boolean
I_CLUID = "DATA LENGTH
TABLES
LT_PRT_S_JESTT = "Individual Object Status
IMPORTING Parameters details for DMC_GENERIC_CLUSTER_EXPORT_JS
I_NO_CLUSTER_FILL - Boolean
Data type: DMC_TYPES-BOOLEANDefault: '-'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CLUID - DATA LENGTH
Data type: BDLBYTESOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DMC_GENERIC_CLUSTER_EXPORT_JS
LT_PRT_S_JESTT - Individual Object Status
Data type: JESTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DMC_GENERIC_CLUSTER_EXPORT_JS 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: | ||||
| lt_lt_prt_s_jestt | TYPE STANDARD TABLE OF JEST, " | |||
| lv_i_no_cluster_fill | TYPE DMC_TYPES-BOOLEAN, " '-' | |||
| lv_i_cluid | TYPE BDLBYTES. " |
|   CALL FUNCTION 'DMC_GENERIC_CLUSTER_EXPORT_JS' "JEST Read write Function Module |
| EXPORTING | ||
| I_NO_CLUSTER_FILL | = lv_i_no_cluster_fill | |
| I_CLUID | = lv_i_cluid | |
| TABLES | ||
| LT_PRT_S_JESTT | = lt_lt_prt_s_jestt | |
| . " DMC_GENERIC_CLUSTER_EXPORT_JS | ||
ABAP code using 7.40 inline data declarations to call FM DMC_GENERIC_CLUSTER_EXPORT_JS
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 BOOLEAN FROM DMC_TYPES INTO @DATA(ld_i_no_cluster_fill). | ||||
| DATA(ld_i_no_cluster_fill) | = '-'. | |||
Search for further information about these or an SAP related objects