SAP CX_MLST_SCHEDULE Function Module for NOTRANSL: Meilenstein terminieren
CX_MLST_SCHEDULE is a standard cx mlst schedule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Meilenstein terminieren 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 cx mlst schedule FM, simply by entering the name CX_MLST_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CXTK
Program Name: SAPLCXTK
Main Program: SAPLCXTK
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CX_MLST_SCHEDULE 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 'CX_MLST_SCHEDULE'"NOTRANSL: Meilenstein terminieren.
EXPORTING
MLSTD_IMP = "Milestone I/O Table
AFVGD_OPR = "Order: Dialog table for Table AFVG (order operation)
* CXZEIT_OPR = "Times and time segments of an operation
* I_TMBAS = '1' "Set of dates for network
* I_FLG_PSP = ' ' "
* I_FLG_MSG_ON_SCREEN = ' ' "
* I_FLG_NO_CALENDAR = ' ' "
* I_FLG_PROTOCOL = 'X' "
IMPORTING
MLSTD_EXP = "Milestone I/O Table
IMPORTING Parameters details for CX_MLST_SCHEDULE
MLSTD_IMP - Milestone I/O Table
Data type: MLSTDOptional: No
Call by Reference: Yes
AFVGD_OPR - Order: Dialog table for Table AFVG (order operation)
Data type: AFVGDOptional: No
Call by Reference: Yes
CXZEIT_OPR - Times and time segments of an operation
Data type: CXZEITOptional: Yes
Call by Reference: Yes
I_TMBAS - Set of dates for network
Data type: CAUFVD-TMBASDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_PSP -
Data type: CX_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_MSG_ON_SCREEN -
Data type: CX_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_NO_CALENDAR -
Data type: CX_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_PROTOCOL -
Data type: CX_BOOLDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CX_MLST_SCHEDULE
MLSTD_EXP - Milestone I/O Table
Data type: MLSTDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CX_MLST_SCHEDULE 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_mlstd_exp | TYPE MLSTD, " | |||
| lv_mlstd_imp | TYPE MLSTD, " | |||
| lv_afvgd_opr | TYPE AFVGD, " | |||
| lv_cxzeit_opr | TYPE CXZEIT, " | |||
| lv_i_tmbas | TYPE CAUFVD-TMBAS, " '1' | |||
| lv_i_flg_psp | TYPE CX_BOOL, " SPACE | |||
| lv_i_flg_msg_on_screen | TYPE CX_BOOL, " SPACE | |||
| lv_i_flg_no_calendar | TYPE CX_BOOL, " SPACE | |||
| lv_i_flg_protocol | TYPE CX_BOOL. " 'X' |
|   CALL FUNCTION 'CX_MLST_SCHEDULE' "NOTRANSL: Meilenstein terminieren |
| EXPORTING | ||
| MLSTD_IMP | = lv_mlstd_imp | |
| AFVGD_OPR | = lv_afvgd_opr | |
| CXZEIT_OPR | = lv_cxzeit_opr | |
| I_TMBAS | = lv_i_tmbas | |
| I_FLG_PSP | = lv_i_flg_psp | |
| I_FLG_MSG_ON_SCREEN | = lv_i_flg_msg_on_screen | |
| I_FLG_NO_CALENDAR | = lv_i_flg_no_calendar | |
| I_FLG_PROTOCOL | = lv_i_flg_protocol | |
| IMPORTING | ||
| MLSTD_EXP | = lv_mlstd_exp | |
| . " CX_MLST_SCHEDULE | ||
ABAP code using 7.40 inline data declarations to call FM CX_MLST_SCHEDULE
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 TMBAS FROM CAUFVD INTO @DATA(ld_i_tmbas). | ||||
| DATA(ld_i_tmbas) | = '1'. | |||
| DATA(ld_i_flg_psp) | = ' '. | |||
| DATA(ld_i_flg_msg_on_screen) | = ' '. | |||
| DATA(ld_i_flg_no_calendar) | = ' '. | |||
| DATA(ld_i_flg_protocol) | = 'X'. | |||
Search for further information about these or an SAP related objects