How To Fix MS015 - Transaction Variants and Screen Variants Were Saved

SAP Error Message - Details

• Message type: E = Error

• Message class: MS - SAP customer enhancement project messages

• Message number: 015

• Message text: Transaction Variants and Screen Variants Were Saved

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MS015 - Transaction Variants and Screen Variants Were Saved ?

  The SAP error message MS015, which states "Transaction Variants and Screen Variants Were Saved," typically indicates that a transaction variant or screen variant has been successfully created or modified. This message is not an error in the traditional sense; rather, it is an informational message confirming that the changes you made to transaction or screen variants have been saved successfully.
  Cause:
  
  The message appears when you are working with transaction variants (which allow you to customize the behavior of standard SAP transactions) or screen variants (which allow you to customize the layout of screens in SAP).
  It is triggered after you save your changes in the relevant transaction (e.g., using transaction codes like SHD0 for transaction variants or SE93 for screen variants).
  
  Solution:
  Since this message is informational and not an error, no specific action is required to resolve it. However, if you are looking to ensure that your transaction or screen variants are functioning as intended, you can follow these steps:
  
  
  Verify Changes: After receiving the message, you can verify that the transaction or screen variant has been saved correctly by navigating back to the relevant transaction or screen and checking the settings.
  
  
  Test the Variant: Execute the transaction or screen using the variant you just created or modified to ensure that it behaves as expected.
  
  
  Documentation: If necessary, document the changes made for future reference or for other users who may need to understand the modifications.
  
  
  User Training: If the variants are intended for use by other users, consider providing training or documentation to help them understand how to use the new or modified variants.
  
  
  Related Information:
  
  Transaction Variants: These are used to simplify the user interface of standard transactions by hiding fields, setting default values, or changing the layout.
  Screen Variants: These allow users to customize the appearance of screens by changing field visibility, order, and default values.
  Transaction Codes: Common transaction codes related to variants include:
  
  SHD0: Create and manage transaction variants.
  SE93: Manage transaction codes and their variants.
  
  
  
  If you encounter any issues with the functionality of the variants after saving, you may need to check for authorization issues, user settings, or other configuration settings that could affect how the variants operate.