Retire the SE16 in Production server

[SAPSupport]

There is issue with Tx. SE16. Our management want to disable the use of Tx SE16 in Production environment.

We already restricted through authorization but remove the possibilities for accidental assignment . Please share the possibilities how should we proceed.

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

Especially in a standard setup, where roles are maintained in the DEV system and then transported to QAS and PRD, it can happen, that roles, which contain the authorization to access SE16 could be transported to PRD by accident.

Therefore an additional way to avoid the access to se16 has to be used.

The easiest way is to lock the application in the PRD system.

There are 2 ways of an application lock:

1. a global lock - to be set with transaction SM01_DEV
2. a local lock - to be set with transaction SM01_CUS

For this scenario, where SE16 should be locked in PRD only, the local lock is applicable. It can be set directly in PRD, as it is a customizing setting and can be used directly as it is a 'current setting'.

SAP note #2234192 provides more information, as well as the documentation available within the SM01_*-t-codes. The former SM01 is not available anymore.

b.rgds, Bernhard