Abdul,
If you’re asking if it is okay to have access in their everyday support role the answer is NO.
If it is a one-time thing as you say to troubleshoot issues that cannot be
duplicated in production than you should implement a change control process
where this type of request is approved by people at the top of the food chain
for accountability and also make sure to provide documentation on misuse of
access will lead to corrective actions. Usually when ABAPers see this they seem
to find other routes in resolving issues without needing such critical access.
At the end of the day the goal is protecting the integrity of the data in production and not having ABAPers go in make changes in production purposely or inadvertently which is the
big RISK.
Lastly, SE16 is okay to give in production so as long as you make sure the right table groups
are assigned in S_TABU_DIS with display access and no create/change for S_DEVELOP.
-Wes