SAP SHP_SE_WRITE_LOG Function Module for Write Application Log
SHP_SE_WRITE_LOG is a standard shp se write log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write Application Log 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 shp se write log FM, simply by entering the name SHP_SE_WRITE_LOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SHP_SE_LOG
Program Name: SAPLSHP_SE_LOG
Main Program: SAPLSHP_SE_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SHP_SE_WRITE_LOG 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 'SHP_SE_WRITE_LOG'"Write Application Log.
EXPORTING
IS_LOG = "Application Log: Log header data
IT_MESSAGES = "Table with BAPI Return Information
* IF_IN_NEW_TASK = ' ' "Checkbox
EXCEPTIONS
CX_SHP_ERROR_MESSAGE = 1
IMPORTING Parameters details for SHP_SE_WRITE_LOG
IS_LOG - Application Log: Log header data
Data type: BAL_S_LOGOptional: No
Call by Reference: Yes
IT_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
IF_IN_NEW_TASK - Checkbox
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
CX_SHP_ERROR_MESSAGE - Error message occured
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SHP_SE_WRITE_LOG 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_is_log | TYPE BAL_S_LOG, " | |||
| lv_cx_shp_error_message | TYPE BAL_S_LOG, " | |||
| lv_it_messages | TYPE BAPIRETTAB, " | |||
| lv_if_in_new_task | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'SHP_SE_WRITE_LOG' "Write Application Log |
| EXPORTING | ||
| IS_LOG | = lv_is_log | |
| IT_MESSAGES | = lv_it_messages | |
| IF_IN_NEW_TASK | = lv_if_in_new_task | |
| EXCEPTIONS | ||
| CX_SHP_ERROR_MESSAGE = 1 | ||
| . " SHP_SE_WRITE_LOG | ||
ABAP code using 7.40 inline data declarations to call FM SHP_SE_WRITE_LOG
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_if_in_new_task) | = ' '. | |||
Search for further information about these or an SAP related objects