SAP SD_MONITOR_PROTOCOL_EXPORT Function Module for NOTRANSL: SD-Monitor: Sichern des Protokolls auf die Datenbank









SD_MONITOR_PROTOCOL_EXPORT is a standard sd monitor protocol export SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: SD-Monitor: Sichern des Protokolls auf die Datenbank 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 sd monitor protocol export FM, simply by entering the name SD_MONITOR_PROTOCOL_EXPORT into the relevant SAP transaction such as SE37 or SE38.

Function Group: V01A
Program Name: SAPLV01A
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SD_MONITOR_PROTOCOL_EXPORT 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 'SD_MONITOR_PROTOCOL_EXPORT'"NOTRANSL: SD-Monitor: Sichern des Protokolls auf die Datenbank
EXPORTING
FVBELN = "
FPAPPL = "
.



IMPORTING Parameters details for SD_MONITOR_PROTOCOL_EXPORT

FVBELN -

Data type: VBUK-VBELN
Optional: No
Call by Reference: No ( called with pass by value option)

FPAPPL -

Data type: SDPROTHEAD-PAPPL
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SD_MONITOR_PROTOCOL_EXPORT 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_fvbeln  TYPE VBUK-VBELN, "   
lv_fpappl  TYPE SDPROTHEAD-PAPPL. "   

  CALL FUNCTION 'SD_MONITOR_PROTOCOL_EXPORT'  "NOTRANSL: SD-Monitor: Sichern des Protokolls auf die Datenbank
    EXPORTING
         FVBELN = lv_fvbeln
         FPAPPL = lv_fpappl
. " SD_MONITOR_PROTOCOL_EXPORT




ABAP code using 7.40 inline data declarations to call FM SD_MONITOR_PROTOCOL_EXPORT

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 VBELN FROM VBUK INTO @DATA(ld_fvbeln).
 
"SELECT single PAPPL FROM SDPROTHEAD INTO @DATA(ld_fpappl).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!