MH_LOG_CREATE SAP Function module

MH_LOG_CREATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MH_LOG_CREATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SMSG1
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM MH_LOG_CREATE - MH LOG CREATE

CALL FUNCTION 'MH_LOG_CREATE' "
* EXPORTING
*   i_object = SPACE            " balobj_d
*   i_subobject = SPACE         " balsubobj
*   i_log_type = 'M'            " c
*   i_use_context = ' '         " c
  IMPORTING
    e_log_handle =              " balloghndl
    e_config =                  " mhconf
    e_result =                  " c
* CHANGING
*   c_mess_transfer_type = 'M'  " c
  EXCEPTIONS
    WRONG_INPUT = 1             "
    PROGRAM_ERROR = 2           "
    .  "  MH_LOG_CREATE

ABAP code example for Function Module MH_LOG_CREATE

The ABAP code below is a full code listing to execute function module MH_LOG_CREATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_log_handle  
 
 TYPE BALLOGHNDL
,
ld_e_config  
 
 TYPE MHCONF
,
ld_e_result  
 
 TYPE C
.


DATA(ld_c_mess_transfer_type) = 'Check type of data required'.

DATA(ld_i_object) = 'Check type of data required'.

DATA(ld_i_subobject) = 'Check type of data required'.

DATA(ld_i_log_type) = 'Check type of data required'.

DATA(ld_i_use_context) = 'Check type of data required'.
.

CALL FUNCTION 'MH_LOG_CREATE'
* EXPORTING
*   i_object =                   ld_i_object
*   i_subobject =                ld_i_subobject
*   i_log_type =                 ld_i_log_type
*   i_use_context =              ld_i_use_context
  IMPORTING
    e_log_handle =               ld_e_log_handle
    e_config =                   ld_e_config
    e_result =                   ld_e_result
* CHANGING
*   c_mess_transfer_type =       ld_c_mess_transfer_type
  EXCEPTIONS
    WRONG_INPUT =                1
    PROGRAM_ERROR =              2
    .  "  MH_LOG_CREATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_c_mess_transfer_type
 
 TYPE C ,
ld_e_log_handle
 
 TYPE BALLOGHNDL ,
ld_i_object
 
 TYPE BALOBJ_D ,
ld_e_config
 
 TYPE MHCONF ,
ld_i_subobject
 
 TYPE BALSUBOBJ ,
ld_e_result
 
 TYPE C ,
ld_i_log_type
 
 TYPE C ,
ld_i_use_context
 
 TYPE C .


ld_c_mess_transfer_type = 'Check type of data required'.
ld_i_object = 'Check type of data required'.
ld_i_subobject = 'Check type of data required'.
ld_i_log_type = 'Check type of data required'.
ld_i_use_context = 'Check type of data required'.