cancel
Showing results for 
Search instead for 
Did you mean: 

Unlocked Transaction still showing the same status "Locked by SM01"

former_member524429
Active Contributor
0 Kudos

Hello Friends,

I am facing one silly problem ,but it is considerable.

I locked the transaction iw20 , then after some time i Unlocked that transaction.

but, When i m executing this iw20 transaction in same server, it is giving the status "Transaction iw20 is locked by SM01 transaction" (something like that) , and the transaction is not executing.

Though , i Unlocked the same transaction using SM01 on that server, its executing the unexpected behavior.

Wht's going wrong with this ?

Thanks in Advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

when you locked the tranasaction using SM01

if is only locked/unlocked by pressing button lock/unlock

it is not locked/unlocked by check/uncheck box under locked.

to lock/unlock tranasaction enter tcode in input box then place cursor on tcode under tcode column then click lock/unlock button vice versa

regards,

kaushal

former_member524429
Active Contributor
0 Kudos

Thanks for your quick responses.

I do it in all the way...

But, still the problem remains same....even for other transactions also.

Wts going wrong ?

former_member524429
Active Contributor
0 Kudos

The Transaction iw20 depends on the SAPMSNUM program. I am thinking that this program is giving the problem, as the same transaction FBN1 and other dependent transactions (which also depend on the same SAPMSNUM program) give the same unexpected response.

:

(Transaction * is locked by SM01)

I have the doubt on S_NUMBER Authorization Object...which stays common for the related transactions....may be..

what u say...?

Still the problem remains same...

Former Member
0 Kudos

HI,

I did not think so,

when you lock the tranasaction through SM01 it's lock the tcode only not the report/program

so when you lock IW20 through SM01 then FBN1 is definitely execute

one more question did you used any application server ( dialog instance)

regards,

kaushal

former_member524429
Active Contributor
0 Kudos

Ok...Anyway....

The Problem is solved.

Actually the SAPMSNUM program was accessing the SNRO Transaction. and the SNRO itself was locked.

Just Unlocked the SNRO, and the Problem solved.

Now, the other dependent transactions are also working fine, after unlocking SNRO.

Thanks to all of you.....

Former Member
0 Kudos

Hi,

i already told you if you lock SNRO usning SM01 it's did not lock IW20 , you can execute IW20 still if SNRO is locked through SM01

regards,

kaushal

ImtiazKaredia
Active Contributor
0 Kudos

Hi,

After deselecting checkbox in SM01, make sure you click enter key.

Thanks