Pro Tip: Bypass Security Restrictions in SAP and Getting Things Done

Caution: Please use common sense. I do not advocate going into areas of SAP that are sensitive in nature. The purpose of this article is to allow the studious worker to complete his/her task in environments where security is a mess.

Task: I need to document a process that correct listens to an event. (Event triggering should be an all-too-familiar topic for those who have worked with BW 3.0B.)

Problem: To raise an event, I had access to transaction SM64 in the Development environment, but not in the Quality Assurance environment.

Solution: Find the underlying program (or function module) associated with this transaction code.

1. Go to SE16
2. Enter “TSTC” for the field “Table Name”
3. Click on the “Execute button
4. Enter the “SM64” in the field “Transaction Code”
5. Click on the “Execute” button

Here are some screen shots for the visually inclined:

1. Go to SE16
2. Enter “TSTC” for the field “Table Name”
3. Click on the “Execute button
   

   Enter Transaction Code

4. Enter the “SM64” in the field “Transaction Code”
5. Click on the “Execute” button
   

   Program Name for Transaction Code

There you have it! The transaction “SM64” is associated with the program “RSEVTHIST”.

This procedure can be applied to any transaction code or program combination. Please use it carefully. If this tip has helped you to get your work done, then please leave a small comment at the bottom of this post. Thanks!

Bonus: For those who are interested in what the SM64 screen looks like, here are some additional shots:

1. Go to SE38
   

   Enter Program Name

2. Enter “RSEVTHIST” in the “Program” field
3. Click on the Execute Button
   

   Find Event Trigger

4. Find the event trigger that you’re looking for

Related posts:

1. SAP Security Tip: How To Quickly Find Existing Roles
2. How To Group Records in a Data Package (DTP) in SAP Netweaver BW (BI)
3. Handy BW trick: Generated Programs for Transformations and Update Rules