Editor lock

[Former Member]

Hi

I have following problem. Two months ago one user created report and set editor

lock. Then that user was expired and now nobody can remove that lock.

How to remove editor lock without direct updating TRDIR table?

[Former Member]

no other way than directly updating TRDIR.

[Former Member]

sorry ignore.

Edited by: Amit Gujargoud on Oct 21, 2008 2:54 PM

[Former Member]

Hi Marat,

There is a solution to open the lock i have seen this program in some website. I have never used it as i have not got the requirement to test this please do try the code that i have shown and revert back the result have you succeed or not.

REPORT sy-repid.

TABLES: TRDIR.

PARAMETERS: P_PROG LIKE TRDIR-NAME OBLIGATORY.

START-OF-SELECTION.

SELECT SINGLE * FROM TRDIR WHERE NAME = P_PROG.

IF SY-SUBRC = 0.

IF TRDIR-EDTX = 'X'.

MOVE ' ' TO TRDIR-EDTX.

MODIFY TRDIR.

WRITE: /'Editor Lock was removed from', P_PROG.

ELSE.

WRITE: /'Program', P_PROG, 'does not have an Editor Lock'.

ENDIF.

ELSE.

WRITE: /'No match found for program', P_PROG.

ENDIF.

Cheers!!

Balu

Edited by: Balu CH on Oct 21, 2008 6:26 PM

[Former Member]

Ask your security to re-create the user ID or for a special moment let you logon with that other locked user ID to unlock the editor.

Cheers,

Julius

[Former Member]

If not yet transported you may just copy the programme...

[matt]

This is one case where you can update the table directly. You should use the code supplied with note 37900, or create a user with the id that was used to lock the program.

I suggest you also develop a program that checks of editor locks. Anyone who sets one get's one warning to never do it again. After that, they're simply removed from site.

matt.

[Former Member]

Hi Marat,

I am waiting for the result whether you have opened your program lock or not so that we can estimate the code importance.

Cheers!!

Balu

[Former Member]

It looks as if Marat is too busy cross-posting ducplicate IDOC questions to follow-up on this one.

Oh well, I guess I should not have rushed in to answer either...