SAP COMH_PROCESS_MESSAGE_CHARS2 Function Module for NOTRANSL: Meldungsmerkmale Anzeigen bzw. Bearbeiten
COMH_PROCESS_MESSAGE_CHARS2 is a standard comh process message chars2 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: Meldungsmerkmale Anzeigen bzw. Bearbeiten 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 comh process message chars2 FM, simply by entering the name COMH_PROCESS_MESSAGE_CHARS2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: COMH
Program Name: SAPLCOMH
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COMH_PROCESS_MESSAGE_CHARS2 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 'COMH_PROCESS_MESSAGE_CHARS2'"NOTRANSL: Meldungsmerkmale Anzeigen bzw. Bearbeiten.
EXPORTING
I_MODUS = "Generic Type
I_SCREEN_TITLE = "Menu Painter: Function code
IMPORTING
E_OK_CODE = "Function Code
TABLES
I_COMH_TAB = "PP-PI: Header Data for Process Messages
I_COME_TAB = "Message Characteristics
LV_MS_ELEMS_TAB = "Process Management: Mess.Elements,Funct.Grp COMH,Screen 400
* X_COMH_TAB = "Process Management: Table COMH with Update Flag
* X_COME_TAB = "Process Management: Table COME with Update Flag
EXCEPTIONS
CHAR_NOT_VALID = 1 DDB_ERROR = 2
IMPORTING Parameters details for COMH_PROCESS_MESSAGE_CHARS2
I_MODUS - Generic Type
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
I_SCREEN_TITLE - Menu Painter: Function code
Data type: RSEU1-TIT_CODEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for COMH_PROCESS_MESSAGE_CHARS2
E_OK_CODE - Function Code
Data type: RSEU1-FUNCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for COMH_PROCESS_MESSAGE_CHARS2
I_COMH_TAB - PP-PI: Header Data for Process Messages
Data type: COMHOptional: No
Call by Reference: No ( called with pass by value option)
I_COME_TAB - Message Characteristics
Data type: COMEOptional: No
Call by Reference: No ( called with pass by value option)
LV_MS_ELEMS_TAB - Process Management: Mess.Elements,Funct.Grp COMH,Screen 400
Data type: RCOMSEOptional: No
Call by Reference: Yes
X_COMH_TAB - Process Management: Table COMH with Update Flag
Data type: RCOMHOptional: Yes
Call by Reference: No ( called with pass by value option)
X_COME_TAB - Process Management: Table COME with Update Flag
Data type: RCOMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CHAR_NOT_VALID - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DDB_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COMH_PROCESS_MESSAGE_CHARS2 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_modus | TYPE C, " | |||
| lv_e_ok_code | TYPE RSEU1-FUNC, " | |||
| lt_i_comh_tab | TYPE STANDARD TABLE OF COMH, " | |||
| lv_char_not_valid | TYPE COMH, " | |||
| lv_ddb_error | TYPE COMH, " | |||
| lt_i_come_tab | TYPE STANDARD TABLE OF COME, " | |||
| lv_i_screen_title | TYPE RSEU1-TIT_CODE, " | |||
| lt_lv_ms_elems_tab | TYPE STANDARD TABLE OF RCOMSE, " | |||
| lt_x_comh_tab | TYPE STANDARD TABLE OF RCOMH, " | |||
| lt_x_come_tab | TYPE STANDARD TABLE OF RCOME. " |
|   CALL FUNCTION 'COMH_PROCESS_MESSAGE_CHARS2' "NOTRANSL: Meldungsmerkmale Anzeigen bzw. Bearbeiten |
| EXPORTING | ||
| I_MODUS | = lv_i_modus | |
| I_SCREEN_TITLE | = lv_i_screen_title | |
| IMPORTING | ||
| E_OK_CODE | = lv_e_ok_code | |
| TABLES | ||
| I_COMH_TAB | = lt_i_comh_tab | |
| I_COME_TAB | = lt_i_come_tab | |
| LV_MS_ELEMS_TAB | = lt_lt_ms_elems_tab | |
| X_COMH_TAB | = lt_x_comh_tab | |
| X_COME_TAB | = lt_x_come_tab | |
| EXCEPTIONS | ||
| CHAR_NOT_VALID = 1 | ||
| DDB_ERROR = 2 | ||
| . " COMH_PROCESS_MESSAGE_CHARS2 | ||
ABAP code using 7.40 inline data declarations to call FM COMH_PROCESS_MESSAGE_CHARS2
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 FUNC FROM RSEU1 INTO @DATA(ld_e_ok_code). | ||||
| "SELECT single TIT_CODE FROM RSEU1 INTO @DATA(ld_i_screen_title). | ||||
Search for further information about these or an SAP related objects