How To Fix /SMB/MD_AS_CUST058 - If you cannot solve the error, open an incident on component &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/MD_AS_CUST -

• Message number: 058

• Message text: If you cannot solve the error, open an incident on component &1

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/MD_AS_CUST058 - If you cannot solve the error, open an incident on component &1 ?

  The SAP error message /SMB/MD_AS_CUST058 typically relates to issues in the SAP Business One or SAP S/4HANA systems, particularly in the context of master data or configuration settings. While the exact cause can vary based on the specific implementation and configuration of your SAP system, here are some common causes and potential solutions:
  Cause:
  
  Missing Configuration: The error may arise due to missing or incorrect configuration settings in the system.
  Data Inconsistencies: There may be inconsistencies in the master data that are preventing the system from processing a request.
  Authorization Issues: The user may not have the necessary permissions to perform the action that triggered the error.
  Integration Issues: If the system is integrated with other applications, there may be issues with data transfer or synchronization.
  
  Solution:
  
  Check Configuration Settings: Review the configuration settings related to the specific module or functionality you are working with. Ensure that all required settings are correctly configured.
  Validate Master Data: Check the master data for any inconsistencies or missing entries. Correct any issues found.
  Review User Permissions: Ensure that the user has the necessary authorizations to perform the action. If not, adjust the user roles and permissions accordingly.
  Consult Logs: Check the system logs for more detailed error messages that can provide additional context about the issue.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message. SAP Notes often contain patches or workarounds for known issues.
  Testing: If changes are made, conduct thorough testing to ensure that the issue is resolved and that no new issues are introduced.
  
  Related Information:
  
  SAP Support: If the issue persists after trying the above solutions, it is advisable to open an incident with SAP Support. When doing so, provide detailed information about the error, including the steps that led to the error, any relevant configuration settings, and the context in which the error occurred.
  Component Information: The error message suggests opening an incident on a specific component. Make sure to identify the correct component related to your SAP system (e.g., S/4HANA, Business One) when submitting the incident.
  
  Conclusion:
  Resolving SAP error messages often requires a systematic approach to identify the root cause. If internal troubleshooting does not resolve the issue, engaging with SAP Support is a recommended next step.