SAP Function Modules
STU3_GET_LOCKING_CONFLICTS SAP Function module
STU3_GET_LOCKING_CONFLICTS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name STU3_GET_LOCKING_CONFLICTS into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
STU3
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM STU3_GET_LOCKING_CONFLICTS - STU3 GET LOCKING CONFLICTS
CALL FUNCTION 'STU3_GET_LOCKING_CONFLICTS' "
EXPORTING
fb_my_user = " sy-subrc
fb_datatype = " sy-subrc
fb_db2threads = " db2threads
* get_old_data = " int4 Get new data from RFCOSCOL?
* ds_member_spec = " db2dsmem-memb_name Name of the data sharing group member
IMPORTING
fb_dsecprocd = " db2qclreq-dsecprocd number of data sections processed
fb_dsecnprocd = " db2qclreq-dsecnprocd number of data sections not processed
TABLES
fb_thrds_tab = " db2threads
fb_lock_tab = " db2locksh Resources locked by a thread
EXCEPTIONS
RS_AUTH_FAILURE = 1 "
RS_START_TRACE = 2 "
RS_INTERNAL_ERROR = 3 "
RS_NO_LOCKCONFS_SYSWIDE = 4 "
RS_NO_SQLSTMT_THREAD = 5 "
RS_NO_LOCKS_HELD_THREAD = 6 "
RS_INVALID_ACE_THREAD = 7 "
RS_NO_LOCKCONFS_THREAD = 8 "
RS_NO_BUFFERS_THREAD = 9 "
RS_NO_LOCKING_THREAD = 10 "
RS_NO_SQLCOUNTER_THREAD = 11 "
REQUEST_TO_OLD = 12 "
NO_BUFFER_SPACE_IN_SHM = 13 "
UNVALID_REQUEST_ID = 14 "
ANSWER_IS_NOT_YET_AVAILABLE = 15 "
COMMUNICATION_ERROR = 16 "
ANSWER_NOT_POSSIBLE = 17 "
COMMUNICATION_BUFFER_TO_SMALL = 18 "
UNKNOWN_ERROR = 19 "
ILLEGAL_PARAMETER = 20 "
IFI_ERROR = 21 "
. " STU3_GET_LOCKING_CONFLICTS
ABAP code example for Function Module STU3_GET_LOCKING_CONFLICTS
The ABAP code below is a full code listing to execute function module STU3_GET_LOCKING_CONFLICTS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_fb_dsecprocd | TYPE DB2QCLREQ-DSECPROCD , |
| ld_fb_dsecnprocd | TYPE DB2QCLREQ-DSECNPROCD , |
| it_fb_thrds_tab | TYPE STANDARD TABLE OF DB2THREADS,"TABLES PARAM |
| wa_fb_thrds_tab | LIKE LINE OF it_fb_thrds_tab , |
| it_fb_lock_tab | TYPE STANDARD TABLE OF DB2LOCKSH,"TABLES PARAM |
| wa_fb_lock_tab | LIKE LINE OF it_fb_lock_tab . |
DATA(ld_fb_my_user) = '20210129'.
DATA(ld_fb_datatype) = '20210129'.
DATA(ld_fb_db2threads) = '20210129'.
DATA(ld_get_old_data) = '20210129'.
DATA(ld_ds_member_spec) = some text here
"populate fields of struture and append to itab
append wa_fb_thrds_tab to it_fb_thrds_tab.
"populate fields of struture and append to itab
append wa_fb_lock_tab to it_fb_lock_tab. . CALL FUNCTION 'STU3_GET_LOCKING_CONFLICTS' EXPORTING fb_my_user = ld_fb_my_user fb_datatype = ld_fb_datatype fb_db2threads = ld_fb_db2threads * get_old_data = ld_get_old_data * ds_member_spec = ld_ds_member_spec IMPORTING fb_dsecprocd = ld_fb_dsecprocd fb_dsecnprocd = ld_fb_dsecnprocd TABLES fb_thrds_tab = it_fb_thrds_tab fb_lock_tab = it_fb_lock_tab EXCEPTIONS RS_AUTH_FAILURE = 1 RS_START_TRACE = 2 RS_INTERNAL_ERROR = 3 RS_NO_LOCKCONFS_SYSWIDE = 4 RS_NO_SQLSTMT_THREAD = 5 RS_NO_LOCKS_HELD_THREAD = 6 RS_INVALID_ACE_THREAD = 7 RS_NO_LOCKCONFS_THREAD = 8 RS_NO_BUFFERS_THREAD = 9 RS_NO_LOCKING_THREAD = 10 RS_NO_SQLCOUNTER_THREAD = 11 REQUEST_TO_OLD = 12 NO_BUFFER_SPACE_IN_SHM = 13 UNVALID_REQUEST_ID = 14 ANSWER_IS_NOT_YET_AVAILABLE = 15 COMMUNICATION_ERROR = 16 ANSWER_NOT_POSSIBLE = 17 COMMUNICATION_BUFFER_TO_SMALL = 18 UNKNOWN_ERROR = 19 ILLEGAL_PARAMETER = 20 IFI_ERROR = 21 . " STU3_GET_LOCKING_CONFLICTS
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 8. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 9. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 10. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 11. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 12. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 13. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 14. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 15. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 16. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 17. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 18. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 19. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 20. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 21. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_fb_dsecprocd | TYPE DB2QCLREQ-DSECPROCD , |
| ld_fb_my_user | TYPE SY-SUBRC , |
| it_fb_thrds_tab | TYPE STANDARD TABLE OF DB2THREADS , |
| wa_fb_thrds_tab | LIKE LINE OF it_fb_thrds_tab, |
| ld_fb_dsecnprocd | TYPE DB2QCLREQ-DSECNPROCD , |
| ld_fb_datatype | TYPE SY-SUBRC , |
| it_fb_lock_tab | TYPE STANDARD TABLE OF DB2LOCKSH , |
| wa_fb_lock_tab | LIKE LINE OF it_fb_lock_tab, |
| ld_fb_db2threads | TYPE DB2THREADS , |
| ld_get_old_data | TYPE INT4 , |
| ld_ds_member_spec | TYPE DB2DSMEM-MEMB_NAME . |
ld_fb_my_user = '20210129'.
"populate fields of struture and append to itab
append wa_fb_thrds_tab to it_fb_thrds_tab.
ld_fb_datatype = '20210129'.
"populate fields of struture and append to itab
append wa_fb_lock_tab to it_fb_lock_tab.
ld_fb_db2threads = '20210129'.
ld_get_old_data = '20210129'.
ld_ds_member_spec = some text here
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name STU3_GET_LOCKING_CONFLICTS or its description.