Do you have any question about this error?
Message type: E = Error
Message class: ESH_OM_OBJ_MODEL_REP - Object Model Repository
Message number: 735
Message text: SAVE is not possible when switch settings are specified
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.
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.
ESH_OM_OBJ_MODEL_REP735
- SAVE is not possible when switch settings are specified ?The SAP error message ESH_OM_OBJ_MODEL_REP735 typically indicates that there is an issue with saving an object model representation in the Enterprise Search (ESH) framework when certain switch settings are specified. This error can occur due to various reasons, including configuration issues, missing authorizations, or inconsistencies in the data model.
Cause
- Switch Settings: The error often arises when specific switch settings are enabled that conflict with the current configuration or data model.
- Inconsistent Data: There may be inconsistencies in the data that the object model is trying to save, such as missing mandatory fields or incorrect data types.
- Authorization Issues: The user may not have the necessary authorizations to perform the save operation.
- Technical Issues: There could be underlying technical issues, such as database locks or system performance problems.
Solution
- Check Switch Settings: Review the switch settings that are currently enabled. If they are not required, consider disabling them to see if the error persists.
- Validate Data Model: Ensure that the data model being saved is complete and consistent. Check for any missing mandatory fields or incorrect data types.
- User Authorizations: Verify that the user has the necessary authorizations to perform the save operation. This may involve checking roles and permissions in the SAP system.
- System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
- Technical Support: If the issue persists, consider reaching out to SAP support or your internal technical team for further investigation. They may need to analyze the system configuration or perform debugging to identify the root cause.
Related Information
SE11
(Data Dictionary), SE80
(Object Navigator), or SLG1
(Application Log) to investigate the issue further.By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
ESH_OM_OBJ_MODEL_REP734
No connector has been created: Select a back-end connection
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_OM_OBJ_MODEL_REP733
Virtual model must have a root node
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_OM_OBJ_MODEL_REP736
RFC failure &1 when trying to connect to &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_OM_OBJ_MODEL_REP737
Classification pattern (object type &1) is inconsistent (error &2)
What causes this issue? The classification pattern with starting template &v1& is inconsistent. The pattern consists of three templates for: ...
Click on this link to search all SAP messages.