SAP CN_CL_S_MST_CHANGE Function Module for NOTRANSL: Ändern eines Ereignispunktes
CN_CL_S_MST_CHANGE is a standard cn cl s mst change 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: Ändern eines Ereignispunktes 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 cn cl s mst change FM, simply by entering the name CN_CL_S_MST_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNCL
Program Name: SAPLCNCL
Main Program: SAPLCNCL
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CN_CL_S_MST_CHANGE 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 'CN_CL_S_MST_CHANGE'"NOTRANSL: Ändern eines Ereignispunktes.
EXPORTING
* I_ECN_S = ' ' "Change Number
I_KEY_DATE_S = "
* I_FLG_MST_CHECK = 'X' "
I_MST_CLASS_DATA = "
* I_MARK_TXT_UPDATE = "
IMPORTING
E_ECM_DATA_ERROR_TYPE = "
EXCEPTIONS
MST_NOT_CONSISTENT = 1 NO_AUTHORITY = 2 NO_VALID_MST = 3 OPERATION_NOT_LOCKED = 4 WRONG_MST_NUMBER = 5 ECM_DATA_NOT_SUITABLE = 6 LINK_TO_REF_SET_OF_OPR = 7 LINK_TO_WC_REF_SET_OF_OPR = 8 NO_VALID_OPERATION = 9
IMPORTING Parameters details for CN_CL_S_MST_CHANGE
I_ECN_S - Change Number
Data type: MST_CLASS_DATA-AENNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KEY_DATE_S -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_MST_CHECK -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MST_CLASS_DATA -
Data type: MST_CLASS_DATAOptional: No
Call by Reference: No ( called with pass by value option)
I_MARK_TXT_UPDATE -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CN_CL_S_MST_CHANGE
E_ECM_DATA_ERROR_TYPE -
Data type: CPCC_MESSAGE_TYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
MST_NOT_CONSISTENT -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_MST -
Data type:Optional: No
Call by Reference: Yes
OPERATION_NOT_LOCKED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_MST_NUMBER -
Data type:Optional: No
Call by Reference: Yes
ECM_DATA_NOT_SUITABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LINK_TO_REF_SET_OF_OPR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LINK_TO_WC_REF_SET_OF_OPR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_OPERATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CN_CL_S_MST_CHANGE 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_i_ecn_s | TYPE MST_CLASS_DATA-AENNR, " SPACE | |||
lv_mst_not_consistent | TYPE MST_CLASS_DATA, " | |||
lv_e_ecm_data_error_type | TYPE CPCC_MESSAGE_TYPE, " | |||
lv_i_key_date_s | TYPE SY-DATUM, " | |||
lv_no_authority | TYPE SY, " | |||
lv_no_valid_mst | TYPE SY, " | |||
lv_i_flg_mst_check | TYPE SY, " 'X' | |||
lv_i_mst_class_data | TYPE MST_CLASS_DATA, " | |||
lv_operation_not_locked | TYPE MST_CLASS_DATA, " | |||
lv_wrong_mst_number | TYPE MST_CLASS_DATA, " | |||
lv_i_mark_txt_update | TYPE CHAR1, " | |||
lv_ecm_data_not_suitable | TYPE CHAR1, " | |||
lv_link_to_ref_set_of_opr | TYPE CHAR1, " | |||
lv_link_to_wc_ref_set_of_opr | TYPE CHAR1, " | |||
lv_no_valid_operation | TYPE CHAR1. " |
  CALL FUNCTION 'CN_CL_S_MST_CHANGE' "NOTRANSL: Ändern eines Ereignispunktes |
EXPORTING | ||
I_ECN_S | = lv_i_ecn_s | |
I_KEY_DATE_S | = lv_i_key_date_s | |
I_FLG_MST_CHECK | = lv_i_flg_mst_check | |
I_MST_CLASS_DATA | = lv_i_mst_class_data | |
I_MARK_TXT_UPDATE | = lv_i_mark_txt_update | |
IMPORTING | ||
E_ECM_DATA_ERROR_TYPE | = lv_e_ecm_data_error_type | |
EXCEPTIONS | ||
MST_NOT_CONSISTENT = 1 | ||
NO_AUTHORITY = 2 | ||
NO_VALID_MST = 3 | ||
OPERATION_NOT_LOCKED = 4 | ||
WRONG_MST_NUMBER = 5 | ||
ECM_DATA_NOT_SUITABLE = 6 | ||
LINK_TO_REF_SET_OF_OPR = 7 | ||
LINK_TO_WC_REF_SET_OF_OPR = 8 | ||
NO_VALID_OPERATION = 9 | ||
. " CN_CL_S_MST_CHANGE |
ABAP code using 7.40 inline data declarations to call FM CN_CL_S_MST_CHANGE
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 AENNR FROM MST_CLASS_DATA INTO @DATA(ld_i_ecn_s). | ||||
DATA(ld_i_ecn_s) | = ' '. | |||
"SELECT single DATUM FROM SY INTO @DATA(ld_i_key_date_s). | ||||
DATA(ld_i_flg_mst_check) | = 'X'. | |||
Search for further information about these or an SAP related objects