This article should clarify a few things about how locking works. There is no actual check on database objects or table entries when locking an entry. MESSAGE A100 WITH 'Claims in use by user' L_LOCK_USER. * -> SWITCH Flag indicating action: "ON" or "OFF"įORM LOCK_ALL USING TRADER LIKE YF023-YTRDNO SWITCH. * -> TRADER The trader number that should be locked * Locks all claims for the current trader. If you want to use the SY-MSGV1 variable above, copy its contents to your own variable first and then do the MESSAGE A100. If the system returns a SY-SUBRC = 1 ( FOREIGN_LOCK) the system variable SY-MSGV1 contains the SAP user name of the person who is locking it. Of course it would be very nice to show who is locking the entry. Note: there is a function module DEQUEUE_ALL as well, it will "dequeue" whatever your program has set using "enqueue". The ABAP can call ENQUEUE_NNNN to lock the object and DEQUEUE_NNNN to release it again. When creating a Lock-object SAP creates two function building blocks: ENQUEUE_NNNN and DEQUEUE_NNNN, ( NNNN is the name of the created Lock-object). See "Data dictionary maintenance", SAP menu => Tools => ABAP Workbench => Development SE11), select radio-button "Lock object". A Lock-object has to be created to claim records from a table. The SAP R/3 Lock-server reserves and releases data for all using processes. As soon as a transparent table record has to be created or modified (or removed), you have to consider the fact that R/3 is a multi-user system.Thus before changing any data we must claim it for the changes.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |