SAP UR_EXEC_CHECK_STATUS_NO_LOCK Function Module for









UR_EXEC_CHECK_STATUS_NO_LOCK is a standard ur exec check status no lock 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 ur exec check status no lock FM, simply by entering the name UR_EXEC_CHECK_STATUS_NO_LOCK into the relevant SAP transaction such as SE37 or SE38.

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



Function UR_EXEC_CHECK_STATUS_NO_LOCK 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 'UR_EXEC_CHECK_STATUS_NO_LOCK'"
EXPORTING
IO_REALIGNER = "
I_CHGRUN = "
I_STATUS = "
IO_DB_SERVICE = "

IMPORTING
ET_BAPIRET = "
E_SUBRC = "

EXCEPTIONS
FAILED = 1
.



IMPORTING Parameters details for UR_EXEC_CHECK_STATUS_NO_LOCK

IO_REALIGNER -

Data type: CL_UR_REALIGNER
Optional: No
Call by Reference: Yes

I_CHGRUN -

Data type: UR_CHGRUN
Optional: No
Call by Reference: Yes

I_STATUS -

Data type: UR00_S_STAT
Optional: No
Call by Reference: Yes

IO_DB_SERVICE -

Data type: CL_UR_DB_SERVICE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for UR_EXEC_CHECK_STATUS_NO_LOCK

ET_BAPIRET -

Data type: BAPIRETTAB
Optional: No
Call by Reference: Yes

E_SUBRC -

Data type: SYSUBRC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FAILED -

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

Copy and paste ABAP code example for UR_EXEC_CHECK_STATUS_NO_LOCK 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_failed  TYPE STRING, "   
lv_et_bapiret  TYPE BAPIRETTAB, "   
lv_io_realigner  TYPE CL_UR_REALIGNER, "   
lv_e_subrc  TYPE SYSUBRC, "   
lv_i_chgrun  TYPE UR_CHGRUN, "   
lv_i_status  TYPE UR00_S_STAT, "   
lv_io_db_service  TYPE CL_UR_DB_SERVICE. "   

  CALL FUNCTION 'UR_EXEC_CHECK_STATUS_NO_LOCK'  "
    EXPORTING
         IO_REALIGNER = lv_io_realigner
         I_CHGRUN = lv_i_chgrun
         I_STATUS = lv_i_status
         IO_DB_SERVICE = lv_io_db_service
    IMPORTING
         ET_BAPIRET = lv_et_bapiret
         E_SUBRC = lv_e_subrc
    EXCEPTIONS
        FAILED = 1
. " UR_EXEC_CHECK_STATUS_NO_LOCK




ABAP code using 7.40 inline data declarations to call FM UR_EXEC_CHECK_STATUS_NO_LOCK

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



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!