SAP MSGD_LOG_SET Function Module for
MSGD_LOG_SET is a standard msgd log set 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 msgd log set FM, simply by entering the name MSGD_LOG_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SMSGD
Program Name: SAPLSMSGD
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MSGD_LOG_SET 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 'MSGD_LOG_SET'".
EXPORTING
I_MH_ID = "
I_LOG_HANDLE = "
* I_LOG_TYPE = 'M' "
IMPORTING
E_MD_LOG_HANDLE = "
E_RESULT = "
E_CONFIGURATION = "
E_CONTEXT_NAME = "
CHANGING
* C_TRANSFER_TYPE = 'M' "
EXCEPTIONS
WRONG_INPUT = 1 PROGRAM_ERROR = 2
IMPORTING Parameters details for MSGD_LOG_SET
I_MH_ID -
Data type: RS38L_AREAOptional: No
Call by Reference: Yes
I_LOG_HANDLE -
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
I_LOG_TYPE -
Data type: CDefault: 'M'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for MSGD_LOG_SET
E_MD_LOG_HANDLE -
Data type: MHMDHNDLOptional: No
Call by Reference: Yes
E_RESULT -
Data type: COptional: No
Call by Reference: Yes
E_CONFIGURATION -
Data type: MHCONFOptional: No
Call by Reference: Yes
E_CONTEXT_NAME -
Data type: TABNAMEOptional: No
Call by Reference: Yes
CHANGING Parameters details for MSGD_LOG_SET
C_TRANSFER_TYPE -
Data type:Default: 'M'
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MSGD_LOG_SET 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_mh_id | TYPE RS38L_AREA, " | |||
| lv_wrong_input | TYPE RS38L_AREA, " | |||
| lv_c_transfer_type | TYPE RS38L_AREA, " 'M' | |||
| lv_e_md_log_handle | TYPE MHMDHNDL, " | |||
| lv_e_result | TYPE C, " | |||
| lv_i_log_handle | TYPE BALLOGHNDL, " | |||
| lv_program_error | TYPE BALLOGHNDL, " | |||
| lv_i_log_type | TYPE C, " 'M' | |||
| lv_e_configuration | TYPE MHCONF, " | |||
| lv_e_context_name | TYPE TABNAME. " |
|   CALL FUNCTION 'MSGD_LOG_SET' " |
| EXPORTING | ||
| I_MH_ID | = lv_i_mh_id | |
| I_LOG_HANDLE | = lv_i_log_handle | |
| I_LOG_TYPE | = lv_i_log_type | |
| IMPORTING | ||
| E_MD_LOG_HANDLE | = lv_e_md_log_handle | |
| E_RESULT | = lv_e_result | |
| E_CONFIGURATION | = lv_e_configuration | |
| E_CONTEXT_NAME | = lv_e_context_name | |
| CHANGING | ||
| C_TRANSFER_TYPE | = lv_c_transfer_type | |
| EXCEPTIONS | ||
| WRONG_INPUT = 1 | ||
| PROGRAM_ERROR = 2 | ||
| . " MSGD_LOG_SET | ||
ABAP code using 7.40 inline data declarations to call FM MSGD_LOG_SET
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_c_transfer_type) | = 'M'. | |||
| DATA(ld_i_log_type) | = 'M'. | |||
Search for further information about these or an SAP related objects