disable locking with SM30

[Clemenss]

Hi,

my customer is not amused that SM30 locks a whole table not selected records. We have a couple of user tables with maintenance views. For the departments (of this small company) it is dificult to maintain their data if another department has data in the same table although completely different records.

I have seen a lecturer using a report to disable and reenable locking for SM30/SM31 10 years ago.

Any Idea?

Regards,

Clemens

P.S. I know that it is dangerous to disable locking, but: Why does SM30 not provide single-record-locking (or even 'optimistic locks').

And the customer wants it.

[Former Member]

I suspect it will lock single records if you maintain the table using the conditions option.

[Clemenss]

Hi Martin,

althought this was not my question, thank you for creativity. You might even have tried before posting. The you might agree that this 'conditions option' is not too useful: You can't use patterns as in select-options.

Next try, please.

Regards,

Clemens

[Former Member]

'You might even have tried before posting'.

I wouldn't of even bothered posting such a stupid question in the first place. You never delete a table lock. SIMPLE AS THAT.

Write a program that can be used to maintain the table instead.

In fact you said it yourself.

'I have seen a lecturer using a report to disable and reenable locking for SM30/SM31 10 years ago.'

Message was edited by:

Martin Shinks

[andreas_mann3]

hi Clemens,

write a forerun to sm30 .

1)in the forerun you lock the entries.

2)after lock call fm VIEW_MAINTENANCE_CALL

with table DBA_SELLIST

A.

[Clemenss]

no help on this - maybe it is better...