SAP MH_MESSAGE_CONTEXT_GET Function Module for









MH_MESSAGE_CONTEXT_GET is a standard mh message context get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 mh message context get FM, simply by entering the name MH_MESSAGE_CONTEXT_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SMSG1
Program Name: SAPLSMSG1
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MH_MESSAGE_CONTEXT_GET 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 'MH_MESSAGE_CONTEXT_GET'"
EXPORTING
* I_LOG_TYPE = 'M' "

IMPORTING
E_CONTEXT_NAME = "
E_CONTEXT_VALUE = "
E_MH_ID = "
E_RESULT = "

EXCEPTIONS
PROGRAM_ERROR = 1 WRONG_INPUT = 2
.



IMPORTING Parameters details for MH_MESSAGE_CONTEXT_GET

I_LOG_TYPE -

Data type: C
Default: 'M'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MH_MESSAGE_CONTEXT_GET

E_CONTEXT_NAME -

Data type: BALTABNAME
Optional: No
Call by Reference: Yes

E_CONTEXT_VALUE -

Data type: BALCVAL
Optional: No
Call by Reference: Yes

E_MH_ID -

Data type: RS38L_AREA
Optional: No
Call by Reference: Yes

E_RESULT -

Data type: C
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PROGRAM_ERROR -

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

WRONG_INPUT -

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

Copy and paste ABAP code example for MH_MESSAGE_CONTEXT_GET 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_log_type  TYPE C, "   'M'
lv_program_error  TYPE C, "   
lv_e_context_name  TYPE BALTABNAME, "   
lv_wrong_input  TYPE BALTABNAME, "   
lv_e_context_value  TYPE BALCVAL, "   
lv_e_mh_id  TYPE RS38L_AREA, "   
lv_e_result  TYPE C. "   

  CALL FUNCTION 'MH_MESSAGE_CONTEXT_GET'  "
    EXPORTING
         I_LOG_TYPE = lv_i_log_type
    IMPORTING
         E_CONTEXT_NAME = lv_e_context_name
         E_CONTEXT_VALUE = lv_e_context_value
         E_MH_ID = lv_e_mh_id
         E_RESULT = lv_e_result
    EXCEPTIONS
        PROGRAM_ERROR = 1
        WRONG_INPUT = 2
. " MH_MESSAGE_CONTEXT_GET




ABAP code using 7.40 inline data declarations to call FM MH_MESSAGE_CONTEXT_GET

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.

DATA(ld_i_log_type) = 'M'.
 
 
 
 
 
 
 


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!