Relationship Between SAP Locks and Database Locks

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/47/d9967bf6e74ac5e10000000a42189d/content.htm
Created on August 22, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 3

Table of content
1 Relationship Between SAP Locks and Database Locks

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 3

1 Relationship Between SAP Locks and Database Locks

The following graphic shows the relationship between SAP locks and database locks.

SAP Locks and Database Locks

The components include:

The dialog work process that executes a transaction
The update work process that inherits the locks
The database
The Enqueue Server that manages the locks in the Lock Table. To simplify the graphic, the enqueue server is not shown.
The duration of the SAP LUW and of the SAP lock is shown on the left.
The dialog work process executes an SAP dialog transaction that comprises three screens (input windows). Each screen corresponds to one database LUW.
Once the user has made an entry, the database LUW ends.
Processing is then resumed by a dialog work process. After the second user input, processing is completed and the dialog part of the SAP LUW ends.

Note
The transaction does not have to be processed by the one dialog work process only. For each screen, the dispatcher simply searches for a free work
process to handle the processing.
In this example, an SAP lock is requested on the first screen of the transaction. This exists until the application data has been changed in the database, that
is, in most cases, until the SAP update is completed. There is no loss of performance since it does not involve a database lock.
The database lock exists only for the duration of the database LUW, in which the changes made in the SAP system are actually updated.

More Information
Lock Owners
_SCOPE Parameters
Features of the Update

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 3