Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from SAPAUSSEC on Nov 6 at 7:32 PM Transaction codes beginning with / can be
A command e.g. /o opens a new session
an IMG transaction
can refer to a component which may be a plug in e.g. GRC
are more common in some new components such as SRM,
https://www.google.com.au/url?sa=t&rct=j&q =&esrc=s&source=web&cd=7&cad=rja&a mp;uact=8&ved
hUKEwikkfLmn5XQAhUCFJQKHYt6Bj4QFghDMAY&url=htt p%3A%2F%2Fpavelgk.pbworks.com%2Ff%2FSAP.ECC6%2BAll%2BTX%2Bcodes. xls&usg=AFQjCNFZScnY-gFdYhYyMealFKrimbqSZg&bvm=bv.137904068,d.dGo
download the file
| | | ---------------Original Message---------------
From: James Johnson
Sent: Sunday, November 06, 2016 4:19 PM
Subject: Tcodes Beginning With Slash
Hi,
We have a diluted form of SAP_ALL which has tcode omissions such as copying clients, user creation and other "significant" activities but leaving other things open for developers and consultants in our Dev / Test environments.
One of the omissions set before my time is any tcode beginning with /SAP.
We are now implementing SAP TMS and there are business tcodes that are required that start with /SAP. I've had a look and there are hundreds of tcodes that begin with /SAP, many have no description and give no clues to their function.
Does anyone have any knowledge of what tcodes beginning with /SAP are considered "dangerous" and need to be restricted or what approach has been taken in this area? Of course when the functionality is implemented - business roles will list allowed tcodes - this is a question of access to implementers.
Thanks,
James. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
