SAP DUV_MSEG_EXTRACT_PREPARE Function Module for
DUV_MSEG_EXTRACT_PREPARE is a standard duv mseg extract prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 duv mseg extract prepare FM, simply by entering the name DUV_MSEG_EXTRACT_PREPARE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CKMLDUVMAT
Program Name: SAPLCKMLDUVMAT
Main Program: SAPLCKMLDUVMAT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DUV_MSEG_EXTRACT_PREPARE 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 'DUV_MSEG_EXTRACT_PREPARE'".
EXPORTING
S_MKPF = "
TABLES
T_MSEG = "
T_MSEG_EXTRACT = "
IMPORTING Parameters details for DUV_MSEG_EXTRACT_PREPARE
S_MKPF -
Data type: MKPFOptional: No
Call by Reference: Yes
TABLES Parameters details for DUV_MSEG_EXTRACT_PREPARE
T_MSEG -
Data type: MSEGOptional: No
Call by Reference: Yes
T_MSEG_EXTRACT -
Data type: DUVMSEG_EXTRACTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DUV_MSEG_EXTRACT_PREPARE 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_s_mkpf | TYPE MKPF, " | |||
| lt_t_mseg | TYPE STANDARD TABLE OF MSEG, " | |||
| lt_t_mseg_extract | TYPE STANDARD TABLE OF DUVMSEG_EXTRACT. " |
|   CALL FUNCTION 'DUV_MSEG_EXTRACT_PREPARE' " |
| EXPORTING | ||
| S_MKPF | = lv_s_mkpf | |
| TABLES | ||
| T_MSEG | = lt_t_mseg | |
| T_MSEG_EXTRACT | = lt_t_mseg_extract | |
| . " DUV_MSEG_EXTRACT_PREPARE | ||
ABAP code using 7.40 inline data declarations to call FM DUV_MSEG_EXTRACT_PREPARE
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