SAP RSENQ_PROTOCOL_DISPLAY_INT Function Module for Lock protocol (internal)
RSENQ_PROTOCOL_DISPLAY_INT is a standard rsenq protocol display int SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lock protocol (internal) 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 rsenq protocol display int FM, simply by entering the name RSENQ_PROTOCOL_DISPLAY_INT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSENQ
Program Name: SAPLRSENQ
Main Program: SAPLRSENQ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSENQ_PROTOCOL_DISPLAY_INT 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 'RSENQ_PROTOCOL_DISPLAY_INT'"Lock protocol (internal).
EXPORTING
I_ACTION = "Range of lock actions (table)
I_UNM_ENQ = "Range of user names (table)
I_TSP_ENQ = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
I_UNM_DEQ = "Range of user names (table)
I_TSP_DEQ = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
I_ERROR = "Boolean
EXCEPTIONS
ERROR_SELECTION = 1
IMPORTING Parameters details for RSENQ_PROTOCOL_DISPLAY_INT
I_ACTION - Range of lock actions (table)
Data type: RSENQ_T_ACTION_RANGEOptional: No
Call by Reference: Yes
I_UNM_ENQ - Range of user names (table)
Data type: RSENQ_T_UNAME_RANGEOptional: No
Call by Reference: Yes
I_TSP_ENQ - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: RSTIMESTMPOptional: No
Call by Reference: Yes
I_UNM_DEQ - Range of user names (table)
Data type: RSENQ_T_UNAME_RANGEOptional: No
Call by Reference: Yes
I_TSP_DEQ - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: RSTIMESTMPOptional: No
Call by Reference: Yes
I_ERROR - Boolean
Data type: RS_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_SELECTION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSENQ_PROTOCOL_DISPLAY_INT 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_action | TYPE RSENQ_T_ACTION_RANGE, " | |||
| lv_error_selection | TYPE RSENQ_T_ACTION_RANGE, " | |||
| lv_i_unm_enq | TYPE RSENQ_T_UNAME_RANGE, " | |||
| lv_i_tsp_enq | TYPE RSTIMESTMP, " | |||
| lv_i_unm_deq | TYPE RSENQ_T_UNAME_RANGE, " | |||
| lv_i_tsp_deq | TYPE RSTIMESTMP, " | |||
| lv_i_error | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSENQ_PROTOCOL_DISPLAY_INT' "Lock protocol (internal) |
| EXPORTING | ||
| I_ACTION | = lv_i_action | |
| I_UNM_ENQ | = lv_i_unm_enq | |
| I_TSP_ENQ | = lv_i_tsp_enq | |
| I_UNM_DEQ | = lv_i_unm_deq | |
| I_TSP_DEQ | = lv_i_tsp_deq | |
| I_ERROR | = lv_i_error | |
| EXCEPTIONS | ||
| ERROR_SELECTION = 1 | ||
| . " RSENQ_PROTOCOL_DISPLAY_INT | ||
ABAP code using 7.40 inline data declarations to call FM RSENQ_PROTOCOL_DISPLAY_INT
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.Search for further information about these or an SAP related objects