How To Fix /ACCGO/SCP_MSG135 - Purchasing document item category not defined for category &1/&2

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/SCP_MSG -

• Message number: 135

• Message text: Purchasing document item category not defined for category &1/&2

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 /ACCGO/SCP_MSG135 - Purchasing document item category not defined for category &1/&2 ?

  The SAP error message /ACCGO/SCP_MSG135 indicates that there is an issue with the purchasing document item category not being defined for the specified category in the system. This error typically arises in the context of the SAP S/4HANA system, particularly when dealing with the Advanced Compliance Reporting (ACCR) or similar modules.
  Cause:
  The error is caused by one of the following reasons:
  
  Missing Configuration: The item category for the purchasing document is not defined in the system for the specified category (e.g., material type, document type).
  Incorrect Document Type: The document type being used does not have a corresponding item category defined in the configuration.
  Custom Development: If there are custom developments or enhancements, they may not be correctly configured to handle the specified item category.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the SPRO transaction (SAP Reference IMG).
  Navigate to Materials Management > Purchasing > Define Item Categories.
  Ensure that the item category for the specified purchasing document type is defined correctly.
  
  
  
  Define Item Category:
  
  If the item category is missing, you may need to create it. Ensure that you have the necessary authorizations to make changes in the configuration.
  Make sure to assign the correct settings for the item category, including account assignment, procurement type, and any other relevant parameters.
  
  
  
  Review Document Type:
  
  Check the document type being used in the purchasing document. Ensure that it is correctly configured to use the appropriate item categories.
  
  
  
  Check Material Type:
  
  Ensure that the material type associated with the purchasing document is correctly set up to allow the use of the specified item category.
  
  
  
  Testing:
  
  After making the necessary changes, test the purchasing document creation again to see if the error persists.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration, refer to SAP documentation or consult with your SAP Basis or MM consultant for guidance.
  
  
  
  Related Information:
  
  Transaction Codes: SPRO (for configuration), ME21N (for creating purchase orders), ME22N (for changing purchase orders).
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  User Authorizations: Ensure that you have the necessary authorizations to view and modify the configuration settings.
  
  If the issue persists after following these steps, it may be beneficial to engage with SAP support or your internal SAP team for further investigation.