How To Fix MH365 - Only displays (ATTYP = 12) can be used to create procurement articles.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 365

• Message text: Only displays (ATTYP = 12) can be used to create procurement articles.

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 MH365 - Only displays (ATTYP = 12) can be used to create procurement articles. ?

  The SAP error message MH365 indicates that only articles with a specific attribute type (ATTYP = 12) can be used to create procurement articles. This typically relates to the configuration of material types and their associated attributes in the SAP system.
  Cause:
  
  Attribute Type Restriction: The error arises because the system is configured to allow only certain attribute types for procurement articles. In this case, ATTYP = 12 is likely associated with a specific category of materials that can be procured.
  Material Master Configuration: The material master record may not be set up correctly, or the material type being used does not meet the criteria for procurement.
  Custom Configuration: There may be custom settings in the SAP system that restrict the creation of procurement articles to only those with the specified attribute type.
  
  Solution:
  
  
  Check Material Type Configuration:
  
  Go to the configuration settings for material types in SAP (Transaction Code: OMS2).
  Verify that the material type you are trying to use is configured to allow procurement and that it is associated with the correct attribute type.
  
  
  
  Review Material Master Data:
  
  Check the material master record for the article you are trying to create (Transaction Code: MM03).
  Ensure that the material type and attributes are correctly assigned. If the material type does not support procurement, you may need to change it to a type that does.
  
  
  
  Use Correct Attribute Type:
  
  If you are trying to create a procurement article, ensure that you are using a material that has ATTYP = 12. If necessary, create a new material with the correct attributes.
  
  
  
  Consult with SAP Basis or Functional Consultant:
  
  If you are unsure about the configuration or if the issue persists, consult with your SAP Basis or functional consultant. They can provide insights into the specific configuration and help resolve the issue.
  
  
  
  Check for Custom Development:
  
  If your organization has custom developments or enhancements, check if any of these are affecting the material creation process. Custom code may impose additional restrictions.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on material types and procurement processes.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MM01 (Create Material), MM02 (Change Material), and MM03 (Display Material) for managing material master data.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.