SAP EDESK_MONITOR_WRITE Function Module for EDESK: Write Entry in Database edesk_monitor
EDESK_MONITOR_WRITE is a standard edesk monitor write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EDESK: Write Entry in Database edesk_monitor 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 edesk monitor write FM, simply by entering the name EDESK_MONITOR_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDESK_MONITOR
Program Name: SAPLEDESK_MONITOR
Main Program: SAPLEDESK_MONITOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EDESK_MONITOR_WRITE 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 'EDESK_MONITOR_WRITE'"EDESK: Write Entry in Database edesk_monitor.
EXPORTING
IS_OBJECT = "CDESK: Tabelle zum Monitoren der Datenbanktabelle DRAW
* IN_UPDATE = ' ' "in Update Verarbeitung
EXCEPTIONS
SAVING_FAILED = 1
IMPORTING Parameters details for EDESK_MONITOR_WRITE
IS_OBJECT - CDESK: Tabelle zum Monitoren der Datenbanktabelle DRAW
Data type: EDESK_MONITOROptional: No
Call by Reference: No ( called with pass by value option)
IN_UPDATE - in Update Verarbeitung
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SAVING_FAILED - Speichern nicht möglich
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EDESK_MONITOR_WRITE 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_object | TYPE EDESK_MONITOR, " | |||
| lv_saving_failed | TYPE EDESK_MONITOR, " | |||
| lv_in_update | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'EDESK_MONITOR_WRITE' "EDESK: Write Entry in Database edesk_monitor |
| EXPORTING | ||
| IS_OBJECT | = lv_is_object | |
| IN_UPDATE | = lv_in_update | |
| EXCEPTIONS | ||
| SAVING_FAILED = 1 | ||
| . " EDESK_MONITOR_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM EDESK_MONITOR_WRITE
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_in_update) | = ' '. | |||
Search for further information about these or an SAP related objects