SAP CM_F_CUSTOMER_MSGTYP_CHECK Function Module for NOTRANSL: Prüft den vom Kunden angegebenen MSGTYP,gegen den vonder Anw. mi
CM_F_CUSTOMER_MSGTYP_CHECK is a standard cm f customer msgtyp check 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: Prüft den vom Kunden angegebenen MSGTYP,gegen den vonder Anw. mi 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 cm f customer msgtyp check FM, simply by entering the name CM_F_CUSTOMER_MSGTYP_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMFE
Program Name: SAPLCMFE
Main Program: SAPLCMFE
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CM_F_CUSTOMER_MSGTYP_CHECK 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 'CM_F_CUSTOMER_MSGTYP_CHECK'"NOTRANSL: Prüft den vom Kunden angegebenen MSGTYP,gegen den vonder Anw. mi.
EXPORTING
APLID = "Application ID
ARBGB = "Work area of message (= MSG ID)
MSGNR = "Message
* MSGTY = ' ' "Message type desired by customer
EXCEPTIONS
INVALID_MSGTYP = 1 NO_CUSTOMER_CONTROL = 2 UNKNOWN_APLID = 3 UNKNOWN_MSGTYP = 4
IMPORTING Parameters details for CM_F_CUSTOMER_MSGTYP_CHECK
APLID - Application ID
Data type: TCMFA-APLIDOptional: No
Call by Reference: No ( called with pass by value option)
ARBGB - Work area of message (= MSG ID)
Data type: TCMFA-ARBGBOptional: No
Call by Reference: No ( called with pass by value option)
MSGNR - Message
Data type: TCMFA-MSGNROptional: No
Call by Reference: No ( called with pass by value option)
MSGTY - Message type desired by customer
Data type: TCMFA-MSGTYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_MSGTYP - Message severity is less than minimum severity
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CUSTOMER_CONTROL - No variable control using msg type for this msg
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_APLID - Unknown application ID
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_MSGTYP - Unknown Message Type
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CM_F_CUSTOMER_MSGTYP_CHECK 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_aplid | TYPE TCMFA-APLID, " | |||
| lv_invalid_msgtyp | TYPE TCMFA, " | |||
| lv_arbgb | TYPE TCMFA-ARBGB, " | |||
| lv_no_customer_control | TYPE TCMFA, " | |||
| lv_msgnr | TYPE TCMFA-MSGNR, " | |||
| lv_unknown_aplid | TYPE TCMFA, " | |||
| lv_msgty | TYPE TCMFA-MSGTY, " SPACE | |||
| lv_unknown_msgtyp | TYPE TCMFA. " |
|   CALL FUNCTION 'CM_F_CUSTOMER_MSGTYP_CHECK' "NOTRANSL: Prüft den vom Kunden angegebenen MSGTYP,gegen den vonder Anw. mi |
| EXPORTING | ||
| APLID | = lv_aplid | |
| ARBGB | = lv_arbgb | |
| MSGNR | = lv_msgnr | |
| MSGTY | = lv_msgty | |
| EXCEPTIONS | ||
| INVALID_MSGTYP = 1 | ||
| NO_CUSTOMER_CONTROL = 2 | ||
| UNKNOWN_APLID = 3 | ||
| UNKNOWN_MSGTYP = 4 | ||
| . " CM_F_CUSTOMER_MSGTYP_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CM_F_CUSTOMER_MSGTYP_CHECK
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 APLID FROM TCMFA INTO @DATA(ld_aplid). | ||||
| "SELECT single ARBGB FROM TCMFA INTO @DATA(ld_arbgb). | ||||
| "SELECT single MSGNR FROM TCMFA INTO @DATA(ld_msgnr). | ||||
| "SELECT single MSGTY FROM TCMFA INTO @DATA(ld_msgty). | ||||
| DATA(ld_msgty) | = ' '. | |||
Search for further information about these or an SAP related objects