SAP K_MONITOR_RECORD_OPEN Function Module for
K_MONITOR_RECORD_OPEN is a standard k monitor record open 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 record open FM, simply by entering the name K_MONITOR_RECORD_OPEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: PFM3
Program Name: SAPLPFM3
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function K_MONITOR_RECORD_OPEN 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_RECORD_OPEN'".
EXPORTING
I_SELID = "
* I_PFSWP = "
I_FUNCTION = "
* I_ACTIVITY = "
* I_REPID = "
* I_VARIANT = "
* I_TCODE = "
I_TEST = "
* I_PFFLD_ORG = "
* I_PFFLD_HIERARCHY = "
IMPORTING
E_PFLID = "
TABLES
* T_PFSEL = "
* T_PFPAR = "
EXCEPTIONS
NO_POSTING_DATE = 1
IMPORTING Parameters details for K_MONITOR_RECORD_OPEN
I_SELID -
Data type: PFLOG-SELARTOptional: No
Call by Reference: No ( called with pass by value option)
I_PFSWP -
Data type: PFSWP_FIELDSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FUNCTION -
Data type: PFLOG-FUNCTIONOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTIVITY -
Data type: PFLOG-ACTIVITYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REPID -
Data type: PFLOG-REPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VARIANT -
Data type: PFLOG-VARIANTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TCODE -
Data type: PFLOG-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TEST -
Data type: PFLOG-TESTOptional: No
Call by Reference: No ( called with pass by value option)
I_PFFLD_ORG -
Data type: PFFLD_ORGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PFFLD_HIERARCHY -
Data type: PFFLD_HIERARCHYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for K_MONITOR_RECORD_OPEN
E_PFLID -
Data type: PFLOG-TIMESTMPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for K_MONITOR_RECORD_OPEN
T_PFSEL -
Data type: PFSELOptional: Yes
Call by Reference: No ( called with pass by value option)
T_PFPAR -
Data type: PFPAROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_POSTING_DATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for K_MONITOR_RECORD_OPEN 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_e_pflid | TYPE PFLOG-TIMESTMP, " | |||
| lv_i_selid | TYPE PFLOG-SELART, " | |||
| lt_t_pfsel | TYPE STANDARD TABLE OF PFSEL, " | |||
| lv_no_posting_date | TYPE PFSEL, " | |||
| lv_i_pfswp | TYPE PFSWP_FIELDS, " | |||
| lt_t_pfpar | TYPE STANDARD TABLE OF PFPAR, " | |||
| lv_i_function | TYPE PFLOG-FUNCTION, " | |||
| lv_i_activity | TYPE PFLOG-ACTIVITY, " | |||
| lv_i_repid | TYPE PFLOG-REPID, " | |||
| lv_i_variant | TYPE PFLOG-VARIANT, " | |||
| lv_i_tcode | TYPE PFLOG-TCODE, " | |||
| lv_i_test | TYPE PFLOG-TEST, " | |||
| lv_i_pffld_org | TYPE PFFLD_ORG, " | |||
| lv_i_pffld_hierarchy | TYPE PFFLD_HIERARCHY. " |
|   CALL FUNCTION 'K_MONITOR_RECORD_OPEN' " |
| EXPORTING | ||
| I_SELID | = lv_i_selid | |
| I_PFSWP | = lv_i_pfswp | |
| I_FUNCTION | = lv_i_function | |
| I_ACTIVITY | = lv_i_activity | |
| I_REPID | = lv_i_repid | |
| I_VARIANT | = lv_i_variant | |
| I_TCODE | = lv_i_tcode | |
| I_TEST | = lv_i_test | |
| I_PFFLD_ORG | = lv_i_pffld_org | |
| I_PFFLD_HIERARCHY | = lv_i_pffld_hierarchy | |
| IMPORTING | ||
| E_PFLID | = lv_e_pflid | |
| TABLES | ||
| T_PFSEL | = lt_t_pfsel | |
| T_PFPAR | = lt_t_pfpar | |
| EXCEPTIONS | ||
| NO_POSTING_DATE = 1 | ||
| . " K_MONITOR_RECORD_OPEN | ||
ABAP code using 7.40 inline data declarations to call FM K_MONITOR_RECORD_OPEN
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 TIMESTMP FROM PFLOG INTO @DATA(ld_e_pflid). | ||||
| "SELECT single SELART FROM PFLOG INTO @DATA(ld_i_selid). | ||||
| "SELECT single FUNCTION FROM PFLOG INTO @DATA(ld_i_function). | ||||
| "SELECT single ACTIVITY FROM PFLOG INTO @DATA(ld_i_activity). | ||||
| "SELECT single REPID FROM PFLOG INTO @DATA(ld_i_repid). | ||||
| "SELECT single VARIANT FROM PFLOG INTO @DATA(ld_i_variant). | ||||
| "SELECT single TCODE FROM PFLOG INTO @DATA(ld_i_tcode). | ||||
| "SELECT single TEST FROM PFLOG INTO @DATA(ld_i_test). | ||||
Search for further information about these or an SAP related objects