Application Development and Automation 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: 
Read only

Tcode

Former Member
0 Likes
935

Hi,

I have a requirement where user should not directly execute tcode VL01, but in a program I have used BDC and made 'Call transaction ' to VL01 and this should work.

How would I restrict users to directly use the tcode. Any user-exits in VL01 by which I can stop if the tcode is directly called and enable call transaction to carry on.I have list of user-exits for VL01, pls suggest which one is appropriate or any alternative that serves this requirement. Is there any special authorization for this kind of requirement?

Thanks in advance.

Vishnu Priya

9 REPLIES 9
Read only

FredericGirod
Active Contributor
0 Likes
905

Lock transaction code with the transaction SM01

Fred

Read only

0 Likes
905

Hi Frederic,

I have tried by locking the tcode using SM01. But then, ' Call transaction' also didn't work.

Regards,

Vishnu Priya

Message was edited by: Vishnu priya

Read only

0 Likes
905

if I use transaction SM01 to lock a transaction and soon I add to a user SAP_ALL profile this user could use the transaction previously locked?

Read only

Former Member
0 Likes
905

Sorry the below wont work...forgot that the ABAP is using the particular transaction. In that case you need to check the user_exit and if the calling program is you zprogram than allow the posting else error message.

---XXX-

There are few ways to tackle the issue

1. Lock the transaction as suggested in the forum.

2. Remove the entry from TSTC table which would mean the users cannot use the transaction.

3. Use authorization profile to achieve the result assign it in a way where the particular transaction is not available to the user.

Message was edited by: Anurag Bankley

Message was edited by: Anurag Bankley

Read only

Former Member
0 Likes
905

Hi,

I think this is a BASIS issue.

Necessary changes need to be made in user roles so that he/she cannot execute VL01 directly.

Read only

Former Member
0 Likes
905

Hi,

This is a basis issue and for restricting this pl ask your basis person to inactivate the object <b>V_LIKP_VST</b>

in the authorization role for the said user.Try this and pl let me know.

Read only

0 Likes
905

Hi

Is your prob solved?

Pl let me know

Read only

0 Likes
905

Hi everybody,

Thanks for your responses. The problem is solved by checking the system variable 'sy-calld' which distinguishes whether a transaction is called in dialogue mode or non-dialogue mode(BDC call transaction stmt)

Thanks & Regards,

Vishnu Priya

Read only

Former Member
0 Likes
905

Hi,

use authorization object to reset profile

for user to execute VL01 transaction

or use sm01 transaction to lock tcode for user

also check

AUTHORITY-CHECK OBJECT 'S_TCODE'

ID 'TCD' FIELD 'VL01'.

IF SY-SUBRC NE 0.

MESSAGE E000 WITH TEXT-152.

endif.

Regards

amole