‎2009 Apr 28 10:52 AM
Hi everyone,
I have created two maintenance view for a single table with some selection conditions. Now if i open a view to maintain the table, i am not able to maintain the other view because it says the table is locked by the other one. So, is there any possibility to maintain the same table with two different views with different selection conditions.
‎2009 Apr 28 11:16 AM
I think the SAP default is that if you start a standard, system generated maintenance view you lock the whole table. Maintenance views are just system generated dynpro screens and you can change these , so you might be able to change these to use a different table lock object of your own creation. Personally, I'd just create a dynpro of my own to do the maintenance instead so that I would be in complete command of who can maintain what when - I''m assuming that you're talking about a custom table and not a SAP standard table here.
‎2009 Apr 28 12:48 PM
No you can't.
System will lock the table entries once you try to maintain using a view.
‎2009 Apr 29 9:05 AM
Hi mevin,
check this link it will help you.
[http://help.sap.com/saphelp_nw04s/helpdata/en/1f/464941db42f423e10000000a155106/frameset.htm]
Regards,
Pavan.
‎2009 Apr 29 10:36 AM
Hi Mevin,
I would suggest to avoid such situation as this may require lot of checks for inconsistent data.
Table Maintenance will create lock on table and hence it will not allow parallel updating of data. (Although, you can update data using insert, update, modify from the code. This is not exclusive lock on data).
If you cannot convince your client to do so, you may create your custom Z program which will update the table. You may copy same code generated by TMG removing FM to lock the table.
If your requirement is modifying different set of data, you may put exclusive lock on data you display for 1 user and display it as locked for another.
Regards,
Mohaiyuddin
‎2009 Apr 29 12:04 PM
If any user opens the table for modification, all the entries of the table is available for modification. This is the default behaviour of SM30. Inthis case, table needs to be locked. You cannot enter in change mode by more than one user at a time.
However there is event no 14. which is after Lock/Unlock of table, you unlock the table after locking. But if you unlock the table, there can be inconsistency of data. (if it suits, you can program to unlock in the event no. 14 of table maintenance)
‎2009 May 15 6:27 AM
Hi mevin,
check this link it will help you.
[http://help.sap.com/saphelp_nw04s/helpdata/en/1f/464941db42f423e10000000a155106/frameset.htm]
Regards,
Pavan.