How To Fix ED353 - &1: &2 broken in table SMODISRC/I; reset the object

SAP Error Message - Details

• Message type: E = Error

• Message class: ED - ABAP/4 Editor messages

• Message number: 353

• Message text: &1: &2 broken in table SMODISRC/I; reset the object

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 ED353 - &1: &2 broken in table SMODISRC/I; reset the object ?

  The SAP error message ED353 typically indicates that there is a problem with a specific object in the system, often related to the modification or enhancement of standard SAP objects. The message suggests that the object is "broken" in the specified table (in this case, SMODISRC/I), which is related to the enhancement framework in SAP.
  Cause:
  
  Modification Issues: The object may have been modified or enhanced incorrectly, leading to inconsistencies in the system.
  Transport Issues: If the object was transported from one system to another (e.g., from development to production), there may have been issues during the transport process.
  Missing or Incomplete Enhancements: The enhancement might not have been fully implemented or activated.
  Version Conflicts: There may be version conflicts between the enhancement and the standard SAP object.
  
  Solution:
  
  Reset the Object: The error message suggests resetting the object. This can typically be done through transaction SE80 or SE11, where you can find the object and reset it to its original state.
  Check Enhancements: Review the enhancements related to the object in question. Ensure that they are correctly implemented and activated.
  Transport Check: If the object was transported, check the transport logs for any errors or warnings that might indicate what went wrong during the transport.
  Re-implement the Enhancement: If the enhancement is broken, you may need to re-implement it. This involves deleting the existing enhancement and creating it again.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide guidance on how to resolve it.
  System Consistency Check: Run a consistency check on the system to identify any other potential issues that might be related to this error.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SE80 (Object Navigator), SE11 (Data Dictionary), or SE37 (Function Module) to investigate the object further.
  SAP Notes: Search for SAP Notes related to ED353 for specific guidance or patches that may resolve the issue.
  Documentation: Review SAP documentation on enhancements and modifications to understand best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or development team for further assistance.