Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

locked T-codes

Former Member
0 Kudos

Hello experts,

how can i find the locked tcodes.

if we know the Tcode it can be checked with SM01,

but if i want to know all the Tcodes in the system which are

locked, How can i find out.

regards,

kavitha

1 ACCEPTED SOLUTION

Former Member
0 Kudos

I hadn't looked into this in so long, that I cannot remember whether I had infact looked into it

21 = locked area menu

22 = locked parameter transaction

24 = locked dialog transaction

A0-9 = locked report transaction

B0-9 = locked variant transactions

Not sure whether I missed anything there...

Just for the record and to clear my own conscience: I don't believe in locking transactions... you can cause some serious problems in the system by doing that in certain places and a skilled person (or even an unskilled person with a simple set of instructions) could most likely start the functionality anyway...

It is a much safer option to restrict their authority to start the transaction and their authority to use the transaction to completion - which is different from just starting it.

Cheers,

Julius

8 REPLIES 8

Former Member
0 Kudos

You can see this in table TSTC, field is CINFO. Value 2 = locked

Edited to add, you need to enter 21 & 22 for CINFO in your search

Edited by: Alex Ayers on Aug 20, 2008 9:51 AM

0 Kudos

Alex,

I was looking into TSTC as well as I find this a good question. But I have no problems starting transactions where the TSTC record CINFO holds the value '02'. I am on ECC 6.0. Any clues?

Jurjen

Clues were in your edit Got it! Add to sticky please!

Edited by: Jurjen Heeck on Aug 20, 2008 10:56 AM

0 Kudos

Hi Jurjen,

I think there are more codes but those are ones I've used in the past.

There is a post on ITToolbox which lists codes for custom tx which are locked but I haven't tested that. ( use range is A0 - A9 )

Cheers

Alex

Former Member
0 Kudos

I hadn't looked into this in so long, that I cannot remember whether I had infact looked into it

21 = locked area menu

22 = locked parameter transaction

24 = locked dialog transaction

A0-9 = locked report transaction

B0-9 = locked variant transactions

Not sure whether I missed anything there...

Just for the record and to clear my own conscience: I don't believe in locking transactions... you can cause some serious problems in the system by doing that in certain places and a skilled person (or even an unskilled person with a simple set of instructions) could most likely start the functionality anyway...

It is a much safer option to restrict their authority to start the transaction and their authority to use the transaction to completion - which is different from just starting it.

Cheers,

Julius

0 Kudos

Hi,

Thank you for the response

I completely agree with Julius, we can restrict a tcode with authoization concept.

still want to know if there is any possibility.

I had tested with both the options .

21 - 22 and A0 - A9.

I locked SM02 and when i go with 21 - 22 and A0 - A9 options it is not showing.

but when i enter SM02 in tcode field, the CINFO value is 2.

regards,

kavitha

0 Kudos

> but when i enter SM02 in tcode field, the CINFO value is 2.

That sounds like SE16 which is just showing you '2 ' => double-click on the record, it will be '24'...

Cheers,

Julius

0 Kudos

Hi julius,

gr8, now it works. before i had given values from 21 -22.

we should give it from 20 .

thank you very much,

got required info.

regards,

kavitha

0 Kudos

> we should give it from 20 .

Yes, you are correct. It is 20 not 24.

Difference between 20 and 24 is...

20 = locked dialog transaction without additional authorization object checked at tcode start.

24 = locked dialog transaction with additional authorization object checked at tcode start.

You can see this additional object (and field values) checked at tcode start in transaction SE93.

Cheers,

Julius