topic Re: Why We Create Lock Objects ?? in Application Development and Automation Discussions

Why We Create Lock Objects ??

Former Member — Thu, 02 Jan 2014 14:05:42 GMT

Hi,

I want to know that why we create lock objects? Because in SAP when somebody is editing or working on any object then it is automatically locked.

Re: Why We Create Lock Objects ??

RaymondGiuseppi — Thu, 02 Jan 2014 14:11:17 GMT


it is automatically locked.

is a false assertion, it is locked because in standard transaction/program the SAP developper used a lock object, start reading The SAP Lock Concept (BC-CST-EQ) and Data Consistency.

Regards,

Raymond

Re: Why We Create Lock Objects ??

Former Member — Fri, 03 Jan 2014 09:09:50 GMT

Hi Raymond,

Thanks for your quick response. One doubt is still in my mind that if SAP system is equipped with a special lock mechanism then when we will create a LOCK OBJECT from SE11.

Thanks in Advance.

Re: Why We Create Lock Objects ??

Former Member — Fri, 03 Jan 2014 09:38:34 GMT

Hi,

Lock object in se11 is for custom development.

Suppose you got an object development in which you are suppose to access the same data from a table at the same time from a report/FM. To help you here you need a lock and unlock object to avoid the user getting wrong data, when one is to change data and another wants to read data for processing.

Regards

Re: Why We Create Lock Objects ??

Former Member — Fri, 03 Jan 2014 09:42:17 GMT

Hi Amit,

It's depends on the business applications. Some time the customized transactions/tables are very much important for the business. To control the data inconsistency need to create the locks based on the tables/fields to avoid the issues and keep the data integrity.

Rg, Kiran

Re: Why We Create Lock Objects ??

kiran_k8 — Fri, 03 Jan 2014 11:06:06 GMT

To add to Amit's query.

Can anyone here share their knowledge on what are the scenarios when a Standard Lock object can't be used compelling us to Create a Custom Lock Object.How Enqueue_E_table will differ from the custom lock object with Secondary tables.

K.Kiran