SAP SDOK_LOG_MESSAGE Function Module for
SDOK_LOG_MESSAGE is a standard sdok log message 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 sdok log message FM, simply by entering the name SDOK_LOG_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDCI
Program Name: SAPLSDCI
Main Program: SAPLSDCI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SDOK_LOG_MESSAGE 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 'SDOK_LOG_MESSAGE'".
EXPORTING
* SUBOBJECT = "
* MSG_ALTEXT = "
* MSG_USEREXITF = "
MSG_PROBCLASS = "
* LOG_SYMSG = ' ' "
* COUNTER = -1 "
* EXTNUMBER = "
* MSGTY = 'I' "
* MSGID = "
MSGNO = "
* MSGV1 = "
* MSGV2 = "
* MSGV3 = "
* MSGV4 = "
TABLES
* MSG_TEXT_LIST = "
IMPORTING Parameters details for SDOK_LOG_MESSAGE
SUBOBJECT -
Data type: BALHDRI-SUBOBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
MSG_ALTEXT -
Data type: BALMI-ALTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
MSG_USEREXITF -
Data type: BALMI-USEREXITFOptional: Yes
Call by Reference: No ( called with pass by value option)
MSG_PROBCLASS -
Data type: BALMI-PROBCLASSOptional: No
Call by Reference: No ( called with pass by value option)
LOG_SYMSG -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
COUNTER -
Data type: IDefault: -1
Optional: Yes
Call by Reference: Yes
EXTNUMBER -
Data type: BALHDRI-EXTNUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
MSGTY -
Data type: BALMI-MSGTYDefault: 'I'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGID -
Data type: BALMI-MSGIDOptional: Yes
Call by Reference: No ( called with pass by value option)
MSGNO -
Data type: BALMI-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
MSGV1 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV2 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV3 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGV4 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SDOK_LOG_MESSAGE
MSG_TEXT_LIST -
Data type: SPAROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SDOK_LOG_MESSAGE 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_subobject | TYPE BALHDRI-SUBOBJECT, " | |||
lt_msg_text_list | TYPE STANDARD TABLE OF SPAR, " | |||
lv_msg_altext | TYPE BALMI-ALTEXT, " | |||
lv_msg_userexitf | TYPE BALMI-USEREXITF, " | |||
lv_msg_probclass | TYPE BALMI-PROBCLASS, " | |||
lv_log_symsg | TYPE C, " ' ' | |||
lv_counter | TYPE I, " -1 | |||
lv_extnumber | TYPE BALHDRI-EXTNUMBER, " | |||
lv_msgty | TYPE BALMI-MSGTY, " 'I' | |||
lv_msgid | TYPE BALMI-MSGID, " | |||
lv_msgno | TYPE BALMI-MSGNO, " | |||
lv_msgv1 | TYPE BALMI, " | |||
lv_msgv2 | TYPE BALMI, " | |||
lv_msgv3 | TYPE BALMI, " | |||
lv_msgv4 | TYPE BALMI. " |
  CALL FUNCTION 'SDOK_LOG_MESSAGE' " |
EXPORTING | ||
SUBOBJECT | = lv_subobject | |
MSG_ALTEXT | = lv_msg_altext | |
MSG_USEREXITF | = lv_msg_userexitf | |
MSG_PROBCLASS | = lv_msg_probclass | |
LOG_SYMSG | = lv_log_symsg | |
COUNTER | = lv_counter | |
EXTNUMBER | = lv_extnumber | |
MSGTY | = lv_msgty | |
MSGID | = lv_msgid | |
MSGNO | = lv_msgno | |
MSGV1 | = lv_msgv1 | |
MSGV2 | = lv_msgv2 | |
MSGV3 | = lv_msgv3 | |
MSGV4 | = lv_msgv4 | |
TABLES | ||
MSG_TEXT_LIST | = lt_msg_text_list | |
. " SDOK_LOG_MESSAGE |
ABAP code using 7.40 inline data declarations to call FM SDOK_LOG_MESSAGE
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 SUBOBJECT FROM BALHDRI INTO @DATA(ld_subobject). | ||||
"SELECT single ALTEXT FROM BALMI INTO @DATA(ld_msg_altext). | ||||
"SELECT single USEREXITF FROM BALMI INTO @DATA(ld_msg_userexitf). | ||||
"SELECT single PROBCLASS FROM BALMI INTO @DATA(ld_msg_probclass). | ||||
DATA(ld_log_symsg) | = ' '. | |||
DATA(ld_counter) | = -1. | |||
"SELECT single EXTNUMBER FROM BALHDRI INTO @DATA(ld_extnumber). | ||||
"SELECT single MSGTY FROM BALMI INTO @DATA(ld_msgty). | ||||
DATA(ld_msgty) | = 'I'. | |||
"SELECT single MSGID FROM BALMI INTO @DATA(ld_msgid). | ||||
"SELECT single MSGNO FROM BALMI INTO @DATA(ld_msgno). | ||||
Search for further information about these or an SAP related objects