Application Development 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: 

How to ENQUEUE to prevent using SE16 to change data?

Former Member

‎05-09-2008 11:37 AM

0 Kudos

Hi All,

When we use SE16 to modify a database table record, a lock entry would be created in the SAP system (can be seen from SM12).

From the Lock Entry List, we know that SE16 makes use of the enqueue function module ENQUEUE_E_TABLEE to lock the record. However, when I try to use the same function module (ENQUEUE_E_TABLEE) in my codes to lock a particular record in the database, I am still able to use SE16 to modify that record.

Why is that so? Thanks.

2 REPLIES 2

Former Member

‎05-09-2008 11:41 AM

0 Kudos

If you run the report with your login id i hoep you can able to modify the record.

at the same time with another login if you can't able to change the same record.

I hope that is the reason.

Please check it out.

REgards,

Madan.

Former Member
In response to Former Member

‎05-09-2008 11:45 AM

0 Kudos

I use the same user (but different SAP session) to (1) run the report program (containing the function module) and (2) run SE16.

Expected Result:

After I run my report program to ENQUEUE that particular record, I SHOULD NOT be able to edit that record using SE16.

Actual Result:

After I run my report program to ENQUEUE that particular record, I AM STILL able to edit that record using SE16.