How To Fix /SRMSMC/INTEGRATION035 - Compare settings in tables mdsc_ctrl_opt_a and /srmsmc/d_syschr

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/INTEGRATION -

• Message number: 035

• Message text: Compare settings in tables mdsc_ctrl_opt_a and /srmsmc/d_syschr

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 /SRMSMC/INTEGRATION035 - Compare settings in tables mdsc_ctrl_opt_a and /srmsmc/d_syschr ?

  The SAP error message /SRMSMC/INTEGRATION035 indicates that there is a mismatch in the settings between two tables: mdsc_ctrl_opt_a and /srmsmc/d_syschr. This error typically arises in the context of SAP Supplier Relationship Management (SRM) or similar integration scenarios where configuration settings need to be consistent across different components.
  Cause:
  The error is caused by discrepancies in the configuration settings stored in the two tables mentioned. This can happen due to various reasons, such as:
  
  Manual changes made to one of the tables without corresponding updates to the other.
  Incomplete or incorrect configuration during system setup or upgrades.
  Data inconsistencies due to system migrations or updates.
  
  Solution:
  To resolve this error, you should follow these steps:
  
  
  Compare the Tables:
  
  Use transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to view the contents of both tables: mdsc_ctrl_opt_a and /srmsmc/d_syschr.
  Identify the specific settings that are inconsistent between the two tables.
  
  
  
  Identify Required Settings:
  
  Determine which settings are required for your specific business process or integration scenario. This may involve consulting documentation or configuration guides.
  
  
  
  Update the Tables:
  
  Based on your findings, update the necessary settings in either mdsc_ctrl_opt_a or /srmsmc/d_syschr to ensure they match.
  Ensure that any changes made are in line with your organization's configuration standards and practices.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform tests to ensure that the integration or functionality is working as expected.
  Monitor for any further error messages or issues.
  
  
  
  Documentation:
  
  Document the changes made for future reference and to assist in troubleshooting if similar issues arise.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11, SE16, and SE37 (for function modules) that may help in analyzing and resolving the issue.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Consulting SAP Documentation: Review the official SAP documentation for SRM and integration scenarios to understand the expected configurations and settings.
  
  If the issue persists after following these steps, consider reaching out to SAP support or consulting with a technical expert who specializes in SAP SRM and integration issues.