SAP COMH_CHECK_MESSAGE_HEADER Function Module for NOTRANSL: Prüfen, ob ein Meldungskopf vollständig ist.









COMH_CHECK_MESSAGE_HEADER is a standard comh check message header 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üfen, ob ein Meldungskopf vollständig ist. 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 check message header FM, simply by entering the name COMH_CHECK_MESSAGE_HEADER 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_CHECK_MESSAGE_HEADER 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_CHECK_MESSAGE_HEADER'"NOTRANSL: Prüfen, ob ein Meldungskopf vollständig ist.
EXPORTING
MS_HEADER = "Message header to be checked

EXCEPTIONS
MESSAGE_CLASS = 1 MESSAGE_ID = 2 SEND_DATE = 3 SEND_TIME = 4 SOURCE = 5 WERK = 6
.



IMPORTING Parameters details for COMH_CHECK_MESSAGE_HEADER

MS_HEADER - Message header to be checked

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

EXCEPTIONS details

MESSAGE_CLASS -

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

MESSAGE_ID - No message number

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

SEND_DATE - No send date

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

SEND_TIME - No send time

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

SOURCE - No message source

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

WERK - Wrong plant

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

Copy and paste ABAP code example for COMH_CHECK_MESSAGE_HEADER 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_ms_header  TYPE RCOMH, "   
lv_message_class  TYPE RCOMH, "   
lv_message_id  TYPE RCOMH, "   
lv_send_date  TYPE RCOMH, "   
lv_send_time  TYPE RCOMH, "   
lv_source  TYPE RCOMH, "   
lv_werk  TYPE RCOMH. "   

  CALL FUNCTION 'COMH_CHECK_MESSAGE_HEADER'  "NOTRANSL: Prüfen, ob ein Meldungskopf vollständig ist.
    EXPORTING
         MS_HEADER = lv_ms_header
    EXCEPTIONS
        MESSAGE_CLASS = 1
        MESSAGE_ID = 2
        SEND_DATE = 3
        SEND_TIME = 4
        SOURCE = 5
        WERK = 6
. " COMH_CHECK_MESSAGE_HEADER




ABAP code using 7.40 inline data declarations to call FM COMH_CHECK_MESSAGE_HEADER

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!