SAP CO_MES_GET_MESS_TYPE Function Module for Determination of Message Type from Table T160M

Search SAP Function Modules

CO_MES_GET_MESS_TYPE is a standard co mes get mess type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determination of Message Type from Table T160M 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 co mes get mess type FM, simply by entering the name CO_MES_GET_MESS_TYPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: COMES
Program Name: SAPLCOMES
Main Program: SAPLCOMES
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CO_MES_GET_MESS_TYPE 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 'CO_MES_GET_MESS_TYPE'"Determination of Message Type from Table T160M
  EXPORTING
   I_MSGID =  "
   I_MSGNO =  "Message Number
*  SEND_MESSAGE =  "
*  I_MSGV1 =  "Message variable 1
*  I_MSGV2 =  "Message variable 2
*  I_MSGV3 =  "Message variable 3
*  I_MSGV4 =  "Message variable 4
*  I_MSGVS = ' ' "Message control version: Purchasing/Sales

 IMPORTING
   E_MSGTY =  "

EXCEPTIONS
   NO_ENTRY = 1 

.

IMPORTING Parameters details for CO_MES_GET_MESS_TYPE

I_MSGID -

Data type: SY-MSGID
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGNO - Message Number

Data type: SY-MSGNO
Optional: No
Call by Reference: No ( called with pass by value option)

SEND_MESSAGE -

Data type: RC27S-FLG_DARK
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV1 - Message variable 1

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV2 - Message variable 2

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV3 - Message variable 3

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV4 - Message variable 4

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGVS - Message control version: Purchasing/Sales

Data type: T160M-MSGVS
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CO_MES_GET_MESS_TYPE

E_MSGTY -

Data type: SY-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_ENTRY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CO_MES_GET_MESS_TYPE 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.

ABAP code using 7.40 inline data declarations to call FM CO_MES_GET_MESS_TYPE

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