Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
If you ensure that this only used by one program then you can ignore this ENQUEUE and DEQUEUE process. But ideally tables are used in more than places.(Different program). Better to use ENQUEUE and DEQUEUE process.
If you ensure that this only used by one program then you can ignore this ENQUEUE and DEQUEUE process. But ideally tables are used in more than places.(Different program). Better to use ENQUEUE and DEQUEUE process.
enqueue locks the table which u r modifying. we use enqueue to maintain consistency in the table. in that period of time nobody else can modify the table
> Even when we use insert new entries in the database table. Coz how come the enqueue will lock entries that does not exist in the Zxxx database table?
Hello,
The SAP Lock Objects are not Database Locks. They don't lock the DB entries, but create a lock argument in the Lock Table ( which resides in the Enqueue Server ).
What you are talking about is DB Locks. How do you handle the scenario when 2 users are trying to insert records with the same key field values in the same DB table ?
Please read this SAP documentation on the [Lock Mechanism|http://help.sap.com/saphelp_nw04/Helpdata/EN/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.htm] which will clear you doubts.
Bluesky
