Is there an alternative to prevent access to a transaction?

Question

Hello Everyone!
Is there an alternative to prevent access to a standard transaction when a user has the S_TCODE value already? A custom program was created through batch input recording and there are transaction calls made to the standard transaction. I had to give the S_TCODE value for the program to run for the user, but one requirement was to force the user to use the custom t-code and not use the standard one. Unfortunately, I have provided the user access to the standard t-code as demanded by the program. Is there a way around this? I assume this has to be manipulated in the program.
Thanks!

Answer 1

If no further intervention is needed, then you can execute the processing as a batch job with the SYSTEM type jobsstep user?
If the dialog user is processing the session in SM35 themselves or the job is executed in their name, then must also have been able to process the data manually.
In the stead of Batch Input, you should also consider redesigning the process to call a BAPI locally or via a group to process the data. This way they typically need the application authorizations but do not need an entry point to them such as S_TCODE or S_RFC.
Or reconsider the transaction code used in the Batch Input call?
Or reconsider the person (job function) who executes this processing?
Or give the originator of the data a webservice to process the data real time?
Lots of options...
Cheers,
Julius