How To Fix /MOC/OBJECT355 - Reference object type &1 not allowed for change request type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /MOC/OBJECT -

• Message number: 355

• Message text: Reference object type &1 not allowed for change request type &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 /MOC/OBJECT355 - Reference object type &1 not allowed for change request type &2 ?

  The SAP error message /MOC/OBJECT355 Reference object type &1 not allowed for change request type &2 typically occurs in the context of SAP Change Request Management (ChaRM) or when working with transport requests. This error indicates that the object type you are trying to reference is not permitted for the specified change request type.
  Cause:
  
  
  Object Type Restrictions: The object type (represented by &1) you are trying to include in the change request (represented by &2) is not configured to be allowed for that specific change request type. This can happen if the object type is not part of the allowed object types for the change request type in the system configuration.
  
  
  Configuration Issues: The configuration settings in the SAP system for the change request management may not include the object type you are trying to use. This could be due to a misconfiguration or oversight during the setup of the ChaRM process.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the transaction SPRO and navigate to the relevant configuration settings for Change Request Management.
  Look for the settings related to "Change Request Types" and "Object Types". Ensure that the object type you are trying to use is included in the allowed object types for the specified change request type.
  
  
  
  Modify Change Request Type:
  
  If the object type is not allowed, you may need to modify the change request type configuration to include the object type. This typically involves adding the object type to the list of allowed object types for that change request type.
  
  
  
  Consult Documentation: 
  
  Review the SAP documentation or help resources related to Change Request Management to understand the specific configurations and requirements for object types and change request types.
  
  
  
  Authorization Check: 
  
  Ensure that you have the necessary authorizations to work with the specified object type and change request type. Sometimes, authorization issues can also lead to similar error messages.
  
  
  
  Contact SAP Support: 
  
  If you are unable to resolve the issue through configuration changes, consider reaching out to SAP support for assistance. They can provide guidance based on the specific details of your system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE01 (Transport Organizer), SE09 (Workbench Organizer), and SPRO (Customizing).
  Change Request Management: Understanding the overall process of Change Request Management in SAP can help in troubleshooting related issues.
  SAP Notes: Check for any SAP Notes that might address this specific error or provide additional insights into configuration best practices.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.