如何在SAP Logon中为锁定用户替换提示消息？

Got it, let's fix this flood of unnecessary support tickets right away. When you lock users during system copy or upgrade, the default SAP lock message doesn't clearly state the reason, leading users to reach out for unlocks when they shouldn't. Here's a straightforward way to swap that generic prompt for your custom text:

Step 1: Locate the Standard Lock Message #

The default "user locked" notification comes from message class 00 (SAP's core system messages) with message number 012. The original text typically reads something like: "User &1 is locked".

Step 2: Modify the Message via SE91 #

1. Launch transaction SE91 (the go-to tool for maintaining SAP system messages).
2. Enter message class 00 and message number 012, then click the Change button.
3. In the Short text field, replace the default text with your custom message:
   Your user is locked because of copy/upgrade works
4. Save your changes. If you're working in a development system, you'll need to assign a transport request to push this change to the systems undergoing copy/upgrade.

Critical Considerations #

• Make this a temporary change: Don't leave the custom message in place permanently! Once the maintenance is done, revert the message back to its original text. Otherwise, users will see this maintenance-specific prompt every time their account is locked for other reasons (like failed login attempts).
• Test before going live: Lock a test user account after modifying the message and try logging in to confirm your custom text appears correctly.
• Alternative for non-permanent edits: If you don't want to alter the standard message directly, use an implicit enhancement in the ABAP login validation code. Add a check for your maintenance window and dynamically overwrite the message text. This requires ABAP development skills but avoids modifying the standard message long-term.

Once your copy/upgrade wraps up, be sure to switch the message back to the original—this will prevent confusion for users down the line.

内容的提问来源于stack exchange，提问作者Skalozub