How To Fix /SMB/SC_MAIN035 - Cannot write data to table /SMB/SC_SLSCNS. Selection was not saved

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/SC_MAIN -

• Message number: 035

• Message text: Cannot write data to table /SMB/SC_SLSCNS. Selection was not 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 /SMB/SC_MAIN035 - Cannot write data to table /SMB/SC_SLSCNS. Selection was not saved ?

  The SAP error message /SMB/SC_MAIN035 Cannot write data to table /SMB/SC_SLSCNS. Selection was not saved typically indicates that there is an issue with writing data to a specific table in the SAP system. This can occur for several reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Authorization Issues: The user may not have the necessary permissions to write data to the specified table.
  Table Locking: The table may be locked by another process or user, preventing any write operations.
  Data Consistency: There may be issues with the data being written, such as violating constraints or data types.
  Technical Issues: There could be underlying technical issues, such as database connectivity problems or system performance issues.
  Custom Code: If there is custom code involved in the process, it may contain errors that prevent data from being saved.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to write to the table. This can be done by checking the user's roles and authorizations in the SAP system.
  Check for Locks: Use transaction codes like SM12 to check for any locks on the table. If there are locks, you may need to wait for them to be released or contact the user who has locked the table.
  Validate Data: Ensure that the data being written to the table meets all the required constraints and data types. Check for any validation rules that may be causing the issue.
  Review Custom Code: If there is custom code involved, review it for any errors or issues that may be causing the write operation to fail.
  Check System Logs: Use transaction codes like SM21 to check the system logs for any related error messages that may provide more context on the issue.
  Database Connectivity: Ensure that the database is up and running and that there are no connectivity issues between the SAP application server and the database.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), and SE37 (Function Module) to investigate the table and related objects.
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.