How To Fix CR358 - Object type & is not permitted as requirement

CR358 - Overview

• Message type: E = Error

• Message class: CR - (1,099) Work Center; (100,200) Capacity

• Message number: 358

• Message text: Object type & is not permitted as requirement

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 CR358 - Object type & is not permitted as requirement ?

  The SAP error message CR358 ("Object type & is not permitted as requirement") 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 use as a requirement is not allowed in the current configuration or context.
  
  Cause:
  
  Invalid Object Type: The object type you are trying to add as a requirement is not recognized or permitted in the current system configuration.
  
  Configuration Issues: The system may not be configured to allow certain object types as requirements due to settings in the transport management system or ChaRM configuration.
  Authorization Issues: The user may not have the necessary authorizations to work with the specified object type.
  
  
  Solution:
  
  Check Object Type: Verify that the object type you are trying to use is valid and supported in the context you are working in. You can check the documentation or configuration settings for