SAP CMX_MESSAGE_VARIANT_STOP Function Module for Retention of Message Variants (Reset Release)
CMX_MESSAGE_VARIANT_STOP is a standard cmx message variant stop SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retention of Message Variants (Reset Release) 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 cmx message variant stop FM, simply by entering the name CMX_MESSAGE_VARIANT_STOP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMX_PM_MDA
Program Name: SAPLCMX_PM_MDA
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMX_MESSAGE_VARIANT_STOP 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 'CMX_MESSAGE_VARIANT_STOP'"Retention of Message Variants (Reset Release).
EXPORTING
* PLANT = "Plant of the Variants
VARIANTS = "Variant Table
IMPORTING
RESULTS = "Messages
IMPORTING Parameters details for CMX_MESSAGE_VARIANT_STOP
PLANT - Plant of the Variants
Data type: WERKS_DOptional: Yes
Call by Reference: Yes
VARIANTS - Variant Table
Data type: CMX_PM_VAR_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CMX_MESSAGE_VARIANT_STOP
RESULTS - Messages
Data type: CMX_PM_VAR_MSG_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMX_MESSAGE_VARIANT_STOP 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_plant | TYPE WERKS_D, " | |||
| lv_results | TYPE CMX_PM_VAR_MSG_TAB, " | |||
| lv_variants | TYPE CMX_PM_VAR_TAB. " |
|   CALL FUNCTION 'CMX_MESSAGE_VARIANT_STOP' "Retention of Message Variants (Reset Release) |
| EXPORTING | ||
| PLANT | = lv_plant | |
| VARIANTS | = lv_variants | |
| IMPORTING | ||
| RESULTS | = lv_results | |
| . " CMX_MESSAGE_VARIANT_STOP | ||
ABAP code using 7.40 inline data declarations to call FM CMX_MESSAGE_VARIANT_STOP
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