How To Fix WER173 - Saving cannot be performed in display mode

SAP Error Message - Details

• Message type: E = Error

• Message class: WER - Messages for the package WER

• Message number: 173

• Message text: Saving cannot be performed in display mode

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 WER173 - Saving cannot be performed in display mode ?

  Certainly! Here's detailed information about the SAP error message WER173 - "Saving cannot be performed in display mode":
  
  Error Message
  WER173: Saving cannot be performed in display mode
  
  Cause
  This error occurs when a user attempts to save changes to a document or transaction while the system is in display mode. Display mode is intended only for viewing data, not for editing or saving changes. The system prevents saving to maintain data integrity and avoid unintended modifications.
  
  Explanation
  
  In SAP, transactions or screens can be opened in different modes:
  
  Display mode: View-only, no changes allowed.
  Change mode: Allows editing and saving.
  Create mode: For creating new entries.
  
  
  If you try to save while the screen is in display mode, SAP throws this error because saving is logically not allowed.
  
  
  Solution
  To resolve this error, you need to:
  
  
  Switch to Change Mode:
  
  Instead of opening the document in display mode, open it in change mode.
  For example, if you are working with a sales order, use the transaction or menu option that allows you to change the order (e.g., VA02 for sales order change instead of VA03 for display).
  
  
  
  Check How You Open the Document:
  
  Ensure you are not using a transaction or function code that opens the document in display mode.
  Use the appropriate transaction or screen variant that allows editing.
  
  
  
  If Using a Custom Program or Screen:
  
  Verify that the program logic sets the screen mode correctly.
  The screen should be set to change mode ('E' for edit) rather than display mode ('D').
  
  
  
  Authorization Check:
  
  Sometimes, users may only have display authorization but not change authorization.
  Verify user roles and authorizations to ensure the user has permission to change and save the document.
  
  
  
  
  Related Information
  
  Transaction Codes:
  
  Display mode transactions usually end with 03 (e.g., VA03 for sales order display).
  Change mode transactions usually end with 02 (e.g., VA02 for sales order change).
  
  
  SAP Notes:
  
  Check SAP Notes related to the specific module or transaction if the error persists.
  
  
  Debugging:
  
  If you are a developer, check the program or screen flow logic to ensure the mode is set correctly.
  
  
  User Training:
  
  Educate users on the difference between display and change modes to avoid this error.
  
  
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Attempt to save data while in display mode (view-only).
  
  
  Solution
  Open the document in change mode and then save. Check user authorizations.
  
  
  Related
  Use correct transaction codes (e.g., VA02 vs VA03). Verify program logic if custom.
  
  
  
  
  If you provide the specific transaction or context where this error occurs, I can give more tailored advice.