Do you have any question about this error?
Message type: E = Error
Message class: 1S - Messages for SSF ("Secure Store & Forward")
Message number: 400
Message text: Transaction PSEMAINT is no longer supported
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Use transaction <DS:TRAN.STRUST>STRUST</>.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message "1S400 Transaction PSEMAINT is no longer supported" indicates that the transaction code PSEMAINT, which was used for managing the SAP system's PSE (Personal Security Environment), is deprecated and no longer supported in the current version of SAP.
Cause:
- Deprecation of Transaction: SAP periodically updates its software and may deprecate certain transactions as part of its efforts to streamline functionality and improve security. PSEMAINT has been replaced by newer methods or transactions for managing security settings.
- Version Upgrade: If you have recently upgraded your SAP system, certain transactions may have been removed or replaced with new functionality.
Solution:
Use Alternative Transactions: Instead of PSEMAINT, you should use the recommended alternative transactions for managing PSE. Common alternatives include:
- STRUST: This transaction is used for managing the PSE and SSL settings in SAP systems.
- STRUSTSSO2: This transaction is specifically for managing Single Sign-On (SSO) settings.
- STRUSTSEC: This transaction is used for managing security settings related to the PSE.
Check SAP Notes: Look for relevant SAP Notes that provide guidance on the transition from PSEMAINT to the new transactions. SAP Notes often contain important information about changes, including how to migrate settings or configurations.
Consult Documentation: Review the official SAP documentation for your version to understand the new processes and transactions that have replaced PSEMAINT.
Contact SAP Support: If you are unsure about how to proceed or if you encounter issues with the new transactions, consider reaching out to SAP Support for assistance.
Related Information:
By following these steps, you should be able to resolve the issue related to the deprecation of the PSEMAINT transaction and effectively manage your SAP system's security settings.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
1S361 A unique extended parameter was used more than once
Self-Explanatory Message Since SAP believes that this specific error message is ...
1S360 An extended parameter has an invalid value
What causes this issue? One of the extended parameters is invalid. In certifica...
1S401 New password and password confirmation do not match
Self-Explanatory Message Since SAP believes that this specific error message is ...
1S402 Choose server
What causes this issue? You did not select an application server to execute the...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.