SAP K_MONITOR_PROTOCOL_STATUS_SET Function Module for









K_MONITOR_PROTOCOL_STATUS_SET is a standard k monitor protocol status set 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 k monitor protocol status set FM, simply by entering the name K_MONITOR_PROTOCOL_STATUS_SET into the relevant SAP transaction such as SE37 or SE38.

Function Group: PFM1
Program Name: SAPLPFM1
Main Program: SAPLPFM1
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function K_MONITOR_PROTOCOL_STATUS_SET 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 'K_MONITOR_PROTOCOL_STATUS_SET'"
EXPORTING
I_USSTAT = "

CHANGING
C_PFLOG_ALL = "

EXCEPTIONS
LOGICAL_SYSTEM_NOT_VALID = 1 TIMESTAMP_NOT_VALID = 2 STATUS_UNDEFINED = 3 ENTRY_NOT_FOUND = 4
.



IMPORTING Parameters details for K_MONITOR_PROTOCOL_STATUS_SET

I_USSTAT -

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

CHANGING Parameters details for K_MONITOR_PROTOCOL_STATUS_SET

C_PFLOG_ALL -

Data type: PFLOG_ALL
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

LOGICAL_SYSTEM_NOT_VALID -

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

TIMESTAMP_NOT_VALID -

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

STATUS_UNDEFINED -

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

ENTRY_NOT_FOUND -

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

Copy and paste ABAP code example for K_MONITOR_PROTOCOL_STATUS_SET 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_i_usstat  TYPE PFLOG_ALL-USSTAT, "   
lv_c_pflog_all  TYPE PFLOG_ALL, "   
lv_logical_system_not_valid  TYPE PFLOG_ALL, "   
lv_timestamp_not_valid  TYPE PFLOG_ALL, "   
lv_status_undefined  TYPE PFLOG_ALL, "   
lv_entry_not_found  TYPE PFLOG_ALL. "   

  CALL FUNCTION 'K_MONITOR_PROTOCOL_STATUS_SET'  "
    EXPORTING
         I_USSTAT = lv_i_usstat
    CHANGING
         C_PFLOG_ALL = lv_c_pflog_all
    EXCEPTIONS
        LOGICAL_SYSTEM_NOT_VALID = 1
        TIMESTAMP_NOT_VALID = 2
        STATUS_UNDEFINED = 3
        ENTRY_NOT_FOUND = 4
. " K_MONITOR_PROTOCOL_STATUS_SET




ABAP code using 7.40 inline data declarations to call FM K_MONITOR_PROTOCOL_STATUS_SET

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 USSTAT FROM PFLOG_ALL INTO @DATA(ld_i_usstat).
 
 
 
 
 
 


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!