| Home • Tips • Tutorials • Forums • Certification Q's • Interview Q's • Jobs • Testimonials • Contact Us | ||
Document Categories:
What's New?
Contribute?Sample SpecsWhat's Hot? |
Row level locking of database table6.
Just one more change in table maintenance screen.
Now open table maintenance function
group(ZTEST_SHUKS3) in
SE80.We know for table maintenance SAP automatically creates code in the
function group. Now we will make some modification in that existing code to
change the behavior. Open the screen you created through table maintenance and
add one module.
Open the screen 0001 and add one module in PBO of the screen
as shown in figure below.
Check the code below to be added in the module
m_change_locking. MODULE m_change_locking OUTPUT. 7.
Now we are ready for testing. Call the transaction once and make some
entries in table. In below screenshot I have entered some random values. Since
we have not maintained any check tables etc, so values may be invalid. That can
be taken care in real scenario.
Save
data. Let’s
call two sessions of the transaction ZTEST_SHUKS3. Session
1
In
first session we will call the transaction ZTEST_SHUKS3 and try to open some
existing values for table maintenance.
Let’s
open an existing value material = MAT1 and Plant = 0678.
So
the entry opens in change mode. Now
open a second session of the transaction and see. Now the same material and
plant combination can not be changed by any other user or session. Session
2
Open transaction ZTEST_SHUKS3
|
|
|
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM Home • Contribute • About Us • Privacy • Terms Of Use • Disclaimer • Safe • Companies: Advertise on SAPTechnical.COM | Post Job • Contact Us ©2006-2007 SAPTechnical.COM. All rights reserved. All
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG. Graphic Design by Round the Bend Wizards |
||