How To Fix MH357 - Cannot determine config. class for generic article &1; correct manually

SAP Error Message - Details

• Message type: E = Error

• Message class: MH - Maintain Material Master Data (Retail)

• Message number: 357

• Message text: Cannot determine config. class for generic article &1; correct manually

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 MH357 - Cannot determine config. class for generic article &1; correct manually ?

  The SAP error message MH357, which states "Cannot determine config. class for generic article &1; correct manually," typically occurs in the context of handling configurable materials or generic articles in SAP. This error indicates that the system is unable to automatically determine the configuration class for a specific generic article, which is necessary for processing configuration-related tasks.
  Causes:
  
  Missing Configuration Class: The configuration class for the generic article may not be defined in the system.
  Incorrect Material Master Data: The material master data for the generic article may be incomplete or incorrectly maintained.
  Customizing Issues: There may be issues in the customizing settings related to configurable materials or generic articles.
  Data Inconsistencies: There could be inconsistencies in the data that prevent the system from determining the configuration class.
  
  Solutions:
  
  
  Check Material Master Data:
  
  Go to the material master record for the generic article (transaction code MM03).
  Ensure that the configuration class is correctly assigned in the relevant views (e.g., Basic Data, Sales, or Plant Data).
  
  
  
  Define Configuration Class:
  
  If the configuration class is missing, you may need to create or assign a configuration class to the generic article.
  Use transaction code CL02 to check existing classes and CL01 to create a new class if necessary.
  
  
  
  Review Customizing Settings:
  
  Check the customizing settings for configurable materials in the SAP IMG (Implementation Guide).
  Ensure that the settings for the configuration profile and class determination are correctly configured.
  
  
  
  Manual Correction:
  
  If the system cannot determine the configuration class automatically, you may need to manually enter the configuration class in the relevant transaction or screen where the error occurs.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for additional guidance on handling configurable materials and generic articles.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  MM03: Display Material
  CL02: Change Class
  CL01: Create Class
  
  
  Configuration Profiles: Ensure that the configuration profiles are set up correctly for the materials in question.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.