Today in the Office... (Security)

Problem: Some users were able to maintain several tables using TCODE SE16 in a production system. For example currency exchange rates.

Solution: Take away TCODE SE16, create a custom TCODE that executes a custom coded SE16 version that does not allow modification of data.

Some highlights of the discussion:

• “We will raise a message with SAP because this is a bug. SE16/SE16N is a data browser and should not allow modification of data”
• “Users got activity 02 through some other role”
• "Some tables are maintainable in production. No idea why"
  
• “User needs maintenance permission of another table of the group, so he got it for all tables”