Community
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.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

search help, lock objects.

Former Member

‎2007 Jul 16 5:03 PM

0 Likes
1,303

what is a search help?how can we create it?what is purpose of this?

what is lock objects?how can we create it?what is purpose of this?

5 REPLIES 5
Read only

former_member196299
Active Contributor

‎2007 Jul 17 5:36 AM

0 Likes
885

hi Spart ,

Here are few documents I am pasting for your knowledge n reference for creation of search helps and Lock objects :

Introduction :

There is a standard way of providing input values to any screen field in ABAP reporting. This way of providing input values can be defined by creating the search helps in ABAP dictionary and using them in reports .

Search helps: Search helps are used to assign an input help ( F4 help ) to screen fields. You can do this by creating a search help for that screen field. And these search helps has only to be assigned to the corresponding screen fields.

There are 2 types of search helps according to their use are available in SAP.

They are : 1) Elementary search helps ( ESH )

2) Collective search helps ( CSH )

1) Elementary search helps ( ESH 😞 These kind of search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).

An ESH defines the standard flow of an input search. The following components of this flow can be defined in the search helps.

• Where does the data displayed in the list come from( selection method ).

• What information should be displayed in the dialog box for value selection and the in hit list ( search help parameters ) .

• What field contents can be taken into account for hit list selection and which values in the hit list can be returned to the screen fields (import and export parameters).

• What dialog step should be executed in the input help ( Dialog behavior ) .

Selection Method: The possible input values of fields displayed in the hit list are determined at runtime by a database selection. In Selection method we provide the

Table name from where the data is being selected. If data retrieval is from more than

two tables then we can create a view ( database view or help view ) and then use it in Selection method . If the tables are client specific then the client field must be copied to the view or else the selection will be for all the clients.

Sear help parameters: A search help has an interface consists of parameters. These parameters defines the fields of the selection method that should be used in the input field. The parameters are copied from the corresponding selection method, that is they always have the same name as the corresponding field of the selection method.

If the search is restricted with a parameter of the search help, this is used in the data selection for formulating a WHERE condition for the field of the selection method with the same name. A data element should be assigned to each search help parameter in other words you define a type for the search help parameter.

Import and Export parameters: The interface of a search help defines the context data that can be used in the input help (import) and the data that can be returned in the input template (export) .

When an input help is called, the entries that the user already made in the input template are taken into consideration. For example, if a user calls the input help for the flight number and already specified the carrier, of course only the numbers of flights of this carrier should be offered. On the other hand if the user selects one row of the hit list, more than one field of the input template might have to be filled with data from the selected row of the hit list. For example, if the flight number is obtained from the hit list, the city of departure and the destination should also be returned in the screen template.

The sample screen is provided for better understanding of screen description of search helps.

• Import parameters: Parameters with which context information from the processed input template (screen) may be copied to the help process.

• Export parameters: Parameters with which values from the hit list may be returned to the input template.

How does the value gets transferred to the input helps ? The values already entered on the screen are used as restrictions for a selection from the hit list. Only those hits that are consistent with the values already entered are displayed. When the input help is called, the system tries to find a field with the same name on the screen for each import parameter of the search help that is attached to a table or structure field. If such a field is found, the contents of the screen field are copied to the search help parameter.

There are at most four steps when searching for the screen field with the same name:

• If the input help is called in a step loop, a field with the same name is searched for in this step loop.

• If the step loop does not contain a field with the same name, the corresponding sub-screen is searched.

• If the sub-screen does not have a field with the same name, the main screen is searched.

• If the main screen does not contain a field with the same name either, the module pool of the corresponding screen is searched.

Values are only returned at the level where the input help was called. The values are only returned to the export parameters.

Collective Search helps ( CSH 😞 These kind of search helps are the combination of various elementary search paths, so they can provide a some alternative search paths.

While defining the CHS we need to provide all the ESH we want to include in that

CSH .A collective search help also has an associated interface for transporting the values they use both the ESH parameter and the input template.

A CSH is a collection of single or multiple elementary search helps and it combines all the meaningful search paths. While linking the elementary search helps with the collective search help there must be at-least one parameter assignment done for linking both of them. This parameter assignment should be done between the interface parameters of the collective search help with that of the included search helps.

Creation of Elementary Search Help:

The creation of an elementary search help is described below with example.

1. Open TCode – SE11 for DDIC objects -> select the radio button for Search helps -> give the name of the search help you want to create, ex – ZSH004.Click on Create .

2. In the next screen select the option “ Elementary search help “ .

3. Now you need to provide the short text for your search help.

4. In the selection method provide the table or view name you want to use for data retrieval. Ex. ZMARA_01.

5. Select the dialog type according to your scope, ex. “ display values immediately’.

6. Then provide the search help parameters i.e. the interface parameters for the search help .

7. The ZMARA_01 table fields MATNR, ERSDA,MHDHB,MHDHT,MHDRZ are provided by selecting the table fields , by doing this the data elements for these fields are automatically copied to the interface from the selection method.

8. Now define the type of parameter ( import or export ) here for the selection and return of values in runtime.

9. Provide the positions to these parameters to specify how they will be arranged in the hit list display.

10. Now save the object in the respective development class and check the same for errors and then activate .Finally the creation of a ESH ( ex: ZSH004 ) is complete and can be used for providing the input help.

Creation of Collective Search Helps:

The creation of an elementary search help is described below with example.

1. Open TCode – SE11 for DDIC objects -> select the radio button for Search helps -> give the name of the search help you want to create, ex – ZSH005.Click on Create .

2. In the next screen select the option “ Collective search help “ .

3. Now you need to provide the short text for your search help.

4. Select the dialog type according to your scope, ex. “ display values immediately’.

5. Then provide the search help parameters i.e. the interface parameters for the search help .

6. The ZMARA_01 table fields MATNR, ERSDA,MHDHB are provided by selecting the table fields . Define the types for the parameters of a collective search help by assigning a data element. Enter the name of the data element that describes the contents of the search help parameter in the Data element field.

7. In the Definition tab page enter the parameters of the collective search help.

Select the Imp flag if it is an import parameter. Select the Exp flag if it is an export parameter. Optional-You can assign the parameter a default value in the Default value field.

8.

Next, Select the tab “ Included Search help “ and provide the elementary search helps you want to include here . In the current example 2 elementary search helps ZSH004 and ZSH003 are being included.

9. Create a parameter assignment between all the included search helps and the collective search help here ( Note that at-least one of the parameter assignment must be done for linking the includes ) .This can be done by clicking on the tab

10. “Parameter assignment “ .ex. we have done the parameter assignment here by using the MATNR field for both the includes i.e. the selection paths should be based on the provided material number.

11. After performing the steps save the search help and activate for use in the later stage.

Additions to the Search helps :

There are few additional functionalities which can be achieved by providing the following :

• Hot Key: The hot key is used to select the elementary search help from the collective search help and to enter the restrictions in the dialog box for restricting values directly from the entry field. If the user often searches for values using the same search help, this procedure can save time. The hot key is available only if for the relevant screen field there is an entry in the Screen Painter in the Search help attribute, that is, if this attribute is not initial.

• Search Help Exits: In exceptions, you might have to change the standard flow defined by the search help with a search help exit. In this case enter the name of the search help exit in the corresponding field. In the later part of the document one example has been provided for describing and understanding Search Help Exits.

Search Help Exits: A search help describes the standard input help process. In exceptions it could be necessary to deviate in some points from this standard. Such a deviation from the standard can also be implemented using a search help exit. The search helps should look as much same as possible through out the entire system so all the exceptions only should be put in the search help exits.

The search help exit is a function module that has a predefined interface. A search help exit is called at certain times by the help processor and the administrative data of the help processors are passed to the search help exit using the interface.

There are some of the search help exits provided by the SAP system and they are used when needed. All the search help exits are stored under the function group SDHI.

A list of function modules provided by SAP for reference are :

F4UT_OPTIMIZE_COLWIDTH – this search help exit adjusts the column width in the hit list to the contents of the column. It makes sense to use this search help exit when the columns of the hit list have to be made very wide.

Any search help exit created should have the same interface as the F4IF_SHLP_EXIT_EXAMPLE. The module is well documented with all the conditions and should be considered as a sample example for understanding the logics involved.

The various parameters involved here are:

TABLE parameters:

• SHLP_TAB - contains information about the search help fields and structures.

• RECORD_TAB – contains the hit list.

CHANGING parameters:

• SHLP – additional information about the parameters. (Deep structure)

• CALLCONTROL – instructions for controlling the search help process.

There are several logics involved in using the CALLCONTROL-STEP.

CALLCONTROL-STEP: This field can be set by your system and can be changed by your code. The function module will be called for each step of the process for each conditional exceptions noted below.

LOCK OBJECTS:

The SAP system synchronizes simultaneous users to the same records via a lock mechanism. This lock mechanism is nothing but you can synchronize access by several programs to the same data with a logical lock mechanism. This lock mechanism fulfills two main functions:

• A program can tell other programs which data records it is just reading or changing.

• A program can prevent itself from reading data that is just being changed by another program.

The data records of a table to be locked are defined by a logical condition. When a lock is set, this logical condition is entered in a lock table. This entry is retained until it is removed by the program or the program comes to an end. All the locks set by a program are thus removed at the end of the program.

To set a lock a lock object must be defined in the ABAP Dictionary. When this lock object is activated two function modules are generated with the names ENQUEUE_< lockobj name > and DEQUEUE_<Lock object name >.You must call these function modules for locking and unlocking your data records. The values of the key fields that specify the records to be locked are passed to the tables contained in the lock object when the function module is called or else there will be a generic lock if values are not passed for all the key fields.

Structure of the Lock Objects:

The tables in which data records should be locked with lock requests along with their key fields are defined in the Lock objects. When tables are selected, one table i.e. the primary table is first selected. Further tables can also be added by using the foreign key relationship.

Lock Argument:

The lock argument of a table in the lock object consists of the key fields of the table. The lock argument fields of a lock object are used as input parameters in the function modules for setting and removing locks generated from the lock object definition. When these function modules are called, the table rows to be locked or unlocked are specified by defining certain values in these fields.

A lock mode can be assigned for each table in the lock object. This mode defines how other users can access a locked record of the table.

Creating Lock Objects:

1. Select object type Lock Object in the initial screen of ABAP Dictionary, enter the name of the object you want to create and choose [ Create ].Note : the name of the lock object should start with E.

EX: We created a lock object with the name EZ_FLIGHT_01 and provided the short text .

2. The maintenance screen then appears for this lock object, write the short text in the space provided for this .

3. Enter the name of the primary table of the lock object. All other tables in the lock object must be provided here who are linked with each other through foreign keys. [ Note : There are other conditional notes also available for the foreign key relationships which could be referred from the sap library .

Provided the name of the primary table SFLIGHT .

4. Select the lock mode of the primary table. This is used as a default value for the parameters of the generated function module.

Selected the lock mode as Exclusive, Cumulative .

[ Lock Modes : The lock mode controls whether several users can access data records at the same time. The lock mode can be assigned separately for each table in the lock object. When the lock is set, the corresponding lock entry is stored in the Lock table of the system for each table. Basically the lock mode describes what kind of lock is it.Below is a list of the lock modes available:

Shared Lock [ Lock Mode S ] : Several transactions can access the data in same time in display mode .Request from further shared locks are accepted, even if they are from different users .An Exclusive lock set on an object that already have a shared lock is rejected.

Exclusive Lock [ Lock Mode E ] : An exclusive lock protects the locked object against all types of locks from other transactions. Only the same lock owner can reset the lock (accumulate).

Exclusive but not cumulative lock [ Lock Mode X ] : Whereas exclusive locks can be requested several times by the same transaction and released one by one, an exclusive, non-cumulative lock can only be requested once by the same transaction. Each further lock request will be rejected.

Optimistic lock [ Lock Code O ]: Optimistic locks initially behave like shared locks and can be converted into exclusive locks. ]

Hope these documents will be of help !!There are even more documents available in SDN , may be you can refer them as well ..

Regards,

Ranjita

Read only

Former Member

‎2007 Jul 17 5:41 AM

0 Likes
885

Hi Spart,

<b>Search Helps</b>

The input help (F4 help) is a standard function of the SAP System. The user can display the list of all possible input values for a screen field with the input help. The possible input values can be enhanced with further information. This is meaningful especially when the field requires the input of a formal key.

<b>Standard Input Help Process</b>

A user calls an input help with the following steps (some steps can be omitted, depending on the definition of the input help):

1. The user starts the input help to display the possible input values for a field (search field) in a screen template.

2. The system offers the user a number of possible search paths. The user selects one of these search paths. Each search path offers a number of restrictions to limit the number of possible input values. These values are offered in a Dialog box for value restriction when the search path is selected.

3. The user enters restrictions if required and then starts the search.

4. The system determines the values that satisfy the entered restrictions (hits) and displays them as a list (hit list).

5. The user selects the most suitable line from the hit list by double-clicking.

6. The value of the search field is returned to the screen template (possibly together with other values).

Steps 2 and 3 are omitted if there is only a single search path available. In this case the dialog box for the value selection is offered immediately. You can also output the hit list directly after starting the input help. Steps 2 to 4 are omitted in this case.

<b>Function of a Search Help</b>

This standard process can be completely defined by creating a search help in the ABAP Dictionary. This search help only has to be assigned to the screen fields in which they should be available (see Attaching Search Helps to Screen Fields).

There are two types of search help:

&#9679; <b>Elementary search helps</b> describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).

&#9679; <b>Collective search helps</b> combine several elementary search helps. A collective search help thus can offer several alternative search paths.

Type and Uses of Lock Objects in SAP

<b>How many types of lock objects?

How to create Lock objects?

What is the main use of it in real time?</b>

<b>Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.</b>

SAP Provide three type of Lock objects.

- Read Lock(Shared Locked)

protects read access to an object. The read lock allows other transactions read access but not write access to

the locked area of the table

- Write Lock(exclusive lock)

protects write access to an object. The write lock allows other transactions neither read nor write access to

the locked area of the table.

- Enhanced write lock (exclusive lock without cumulating)

works like a write lock except that the enhanced write lock also protects from further accesses from the

same transaction.

You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.

Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.

Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.

Technicaly:

When you create a lock object System automatically creat two function module.

1. ENQUEUE_<Lockobject name>. to insert the object in a queue.

2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.

You have to use these function module in your program.

Hope this will give a basic idea.

Create a lock object for table MSEG called EZTESTLOCK.

When you has created the lock object, the two function modules

ENQUEUE_EZTESTLOCK

DEQUEUE_EZTESTLOCK

Will automatically be created


REPORT lockentries.


PARAMETERS:
p_mbelnr LIKE mseg-mblnr DEFAULT '4900008001',
p_mjahr LIKE mseg-mjahr DEFAULT '2001',

p_zeile LIKE mseg-zeile DEFAULT 1,
p_lock RADIOBUTTON GROUP lock,
p_unlock RADIOBUTTON GROUP lock.


START-OF-SELECTION.

IF p_lock = 'X'.
* Lock item
CALL FUNCTION 'ENQUEUE_EZTESTLOCK'
EXPORTING
* MODE_MSEG = 'E'
* MANDT = SY-MANDT
mblnr = p_mbelnr
mjahr = p_mjahr
zeile = p_zeile
* X_MBLNR = ' '
* X_MJAHR = ' '
* X_ZEILE = ' '
* _SCOPE = '2'
* _WAIT = ' '

* _COLLECT = ' '
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3
.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

ELSEIF p_unlock = 'X'.
* Unlock item
CALL FUNCTION 'DEQUEUE_EZTESTLOCK'
EXPORTING
* MODE_MSEG = 'E'
* MANDT = SY-MANDT
mblnr = p_mbelnr
mjahr = p_mjahr
zeile = p_zeile

* X_MBLNR = ' '
* X_MJAHR = ' '
* X_ZEILE = ' '
* _SCOPE = '3'
* _SYNCHRON = ' '
* _COLLECT = ' '
.
ENDIF.

<i><b>Hope this will give u the picture of search help and lock object :)</b></i>

<u>Reward pts if found usefull :)</u>

Regards

Sathish

Read only

Former Member

‎2007 Jul 17 5:47 AM

0 Likes
885

Hi,

Search Help:

The input help (F4 help) is a standard function of the SAP System. The user can display the list of all possible input values for a screen field with the input help. The possible input values can be enhanced with further information. This is meaningful especially when the field requires the input of a formal key.

Link for creating search help:

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ea31446011d189700000e8322d00/frameset.htm">Search Help</a>

Lock Objects:

The SAP System synchronizes simultaneous access of several users to the same data records with a lock mechanism. When interactive transactions are programmed, locks are set and released by calling function modules (see Function Modules for Lock Requests). These function modules are automatically generated from the definition of lock objects in the ABAP Dictionary.

Link for creating Lock object:

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ea31446011d189700000e8322d00/frameset.htm">Lock Object</a>

Creating Lock Objects:

Procedure:

1. Select object type Lock object in the initial screen of the ABAP Dictionary, enter an object name and choose Create. The name of a lock object should begin with an E (Enqueue).

The maintenance screen for lock objects is displayed.

2. Enter an explanatory short text in the field Short text.

You can then use the short text to find the lock object at a later time, for example with the SAP Repository Information System.

3. Enter the name of the primary table of the lock object.

All other tables in the lock object must be linked with the primary table using foreign keys. There are also some restrictions on the valid foreign key relationships.

4. Select the lock mode of the primary table in the field below it.

The lock mode is used as the default value for the corresponding parameters of the function modules generated from the lock object.

5. Choose Add if you want to lock records in more than one table with the lock object.

A list of all the tables linked with the primary table using valid foreign keys is displayed. Select the appropriate table. The lock mode of the primary table is copied as lock mode. You can change this setting as required, for example you can assign the lock mode separately for each table.

Similarly, you can add a table linked with the secondary table just added with foreign keys. To do this, place the cursor on the name of the secondary table and choose Add.

If no lock mode is assigned to a table, no lock is set for the entries in this table when the generated function modules are called. You should not assign a lock mode if a secondary table was only used to define a path between the primary table and another secondary table with foreign keys.

6. Save your entries.

A dialog box appears in which you have to assign the lock object a development class.

7. You can (optionally) exclude lock parameters (see lock objects) from the function module generation on the Lock parameter tab page. This makes sense for example if you always want to lock a parameter generically.

To do this, simply deselect the Weight flag for the parameter. The parameter is not taken into consideration in the generated function modules. This parameter is then always locked generically.

The name of a lock parameter is usually the name of the corresponding table field. If two fields with the same name are used as lock parameters in the lock object from different tables, you must choose a new name for one of the fields in field Lock parameter.

8. You can define whether the function modules generated from the lock object should be RFC-enabled on the Attributes tab page.

If you set the Allow RFC flag, the generated function modules can be called from within another system with Remote Function Call.

If you permit Remote Function Calls for an existing lock object, you must ensure that the generated function modules are called from within an ABAP program with parameters appropriate for the type. You should therefore check all programs that use the associated function modules before activating the lock object with the new option.

9. Choose .

<b>Please do reward points for my effort.</b>

Regards,

Ameet

Read only

Former Member

‎2007 Jul 17 5:48 AM

0 Likes
885

Hi

Search help

1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).

2) Collective search helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.

3)An elementary search help defines the standard flow of an input help.

4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.

5)A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.

6)Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in a collective search help, they are expanded to the level of the elementary search helps when the input help is called.

CREATION:

Go to SE11 Tcode

select search help

give the 'z' search help name and create

select the selection method ur table name eg : 'mara'

dialog module 'display value immediately'.

add the field whatever u want and lpos = 1 and spos = 1 and check import and export parameter.

where left position when displaying and spos = search position

and then save and activate ..

See the links:

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee45446011d189700000e8322d00/content.htm

https://forums.sdn.sap.com/click.jspa?searchID=3173469&messageID=2176485

https://forums.sdn.sap.com/click.jspa?searchID=3173469&messageID=3601619

pls go through this for search help creation

http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm

Search Help Exits:

LOCK Objects

Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.

SAP Provide three type of Lock objects.

- Read Lock(Shared Locked)

protects read access to an object. The read lock allows other transactions read access but not write access to

the locked area of the table

- Write Lock(exclusive lock)

protects write access to an object. The write lock allows other transactions neither read nor write access to

the locked area of the table.

- Enhanced write lock (exclusive lock without cumulating)

works like a write lock except that the enhanced write lock also protects from further accesses from the

same transaction.

You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.

Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.

Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.

Technicaly:

When you create a lock object System automatically creat two function module.

1. ENQUEUE_<Lockobject name>. to insert the object in a queue.

2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.

You have to use these function module in your program.

check this link for example.

http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm

tables:vbak.

call function 'ENQUEUE_EZLOCK3'

exporting

mode_vbak = 'E'

mandt = sy-mandt

vbeln = vbak-vbeln

  • X_VBELN = ' '

  • _SCOPE = '2'

  • _WAIT = ' '

  • _COLLECT = ' '

  • EXCEPTIONS

  • FOREIGN_LOCK = 1

  • SYSTEM_FAILURE = 2

  • OTHERS = 3

.

if sy-subrc <> 0.

  • MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

  • WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

endif.

Normally ABAPers will create the Lock objects, because we know when to lock and how to lock and where to lock the Object then after completing our updations we unlock the Objects in the Tables

http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm

purpose: If multiple user try to access a database object, inconsistency may occer. To avoid that inconsistency and to let multiple user give the accessibility of the database objects the locking mechanism is used.

Steps: first we create a loc object in se11 . Suppose for a table mara. It will create two functional module.:

1. enque_lockobject

1. deque_lockobject

before updating any table first we lock the table by calling enque_lockobject fm and then after updating we release the lock by deque_lockobject.

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm

GO TO SE11

Select the radio button "Lock object"..

Give the name starts with EZ or EY..

Example: EYTEST

Press Create button..

Give the short description..

Example: Lock object for table ZTABLE..

In the tables tab..Give the table name..

Example: ZTABLE

Save and generate..

Your lock object is now created..You can see the LOCK MODULES..

In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function

Lock objects:

http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm

Match Code Objects:

http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm

http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html

See this link:

http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm

Check these links -

<b>Reward points for useful Answers</b>

Regards

Anji