You can use transaction RSAUDITC_BCE to check application start locks. This displays the complete lock status of the selected application.
When locking the application start, there is a difference between the standard lock and the customer-specific lock.
- Standard locks are set by the application developer and are transported as part of the corresponding workbench object.
- Customer-specific application start locks are part of Customizing and can be set to be client-specific or cross-client.
An application is considered to be locked when a standard lock or a suitable customer-specific lock has been set for it.
Maintenance of Standard Application Locks (SM01_DEV)
You can maintain standard application locks by using transaction SM01_DEV.
In addition to the administrative authorization for maintaining application locks (S_ADMI_FCD Wert TLCK), you need the corresponding workbench change authorization to maintain the selected applications. Only the application developer should use this maintenance environment (for example, for obsolete applications that have not yet been removed).
Maintenance of Customer-Specific Application Start Locks
You use transaction SM01_CUS to maintain customer-specific application start locks. This is intended for typical customer lock reasons (business-critical transactions, locking for maintenance purposes, and so on).
Use the selection screen to delimit your application area. To lock or unlock an application, use the pushbuttons in the application list after you have selected the lines to be processed.
You maintain the lock status customer-specifically for your own logon
client. You can also set the lock status for all clients in the system by logging on in system client 000. For cross-client maintenance, you require the corresponding authorization for object S_TABU_CLI.
Note
- Transaction SM01 is obsolete and will no longer be available for background processing either in a later release. For more information, see SAP Note 2234192.
