How To Fix CRD_CUST520 - Requirement type &2 of requirement &1 does now allow comb.requirements

SAP Error Message - Details

• Message type: E = Error

• Message class: CRD_CUST - Credentialing: Messages for Editing Customizing

• Message number: 520

• Message text: Requirement type &2 of requirement &1 does now allow comb.requirements

What causes this issue?

Requirement &v1& references requirement type &v2&. However this
requirement type is <ZH>not</> suitable for combined requirements.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Change the requirement type for requirement &v1& in Customizing for
<ZK>Credentialing</> under<ZK> Configure Requirements -> Define and
Configure Requirements -> Define Requirements</> or change requirement
type &v2& in Customizing under <ZK>Configuration of Requirements ->
Basic Settings -> Configure Requirement Types.</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRD_CUST520 - Requirement type &2 of requirement &1 does now allow comb.requirements ?

  The SAP error message CRD_CUST520 indicates that there is an issue with the configuration of requirement types in the context of combining requirements in a sales order or similar document. Specifically, it suggests that the requirement type specified does not allow for combined requirements, which can occur in various scenarios, such as when dealing with sales order processing, delivery, or production planning.
  Cause:
  
  
  Requirement Type Configuration: The requirement type (identified as &2 in the error message) associated with the requirement (identified as &1) is configured in such a way that it does not permit the combination of requirements. This could be due to settings in the configuration of the requirement types in the SAP system.
  
  
  Custom Settings: If the requirement types have been customized, it is possible that the settings were altered to restrict the combination of requirements.
  
  
  Business Rules: There may be specific business rules or logic that dictate that certain requirement types cannot be combined, which could be part of the overall business process design.
  
  
  Solution:
  
  
  Check Requirement Type Configuration:
  
  Go to the configuration settings for requirement types in the SAP system (Transaction code: SPRO).
  Navigate to the relevant area (e.g., Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Requirement Types).
  Review the settings for the requirement type in question and ensure that it is configured to allow combined requirements if that is the desired behavior.
  
  
  
  Adjust Custom Settings:
  
  If the requirement type has been customized, review the custom settings to see if they can be modified to allow for combined requirements.
  Consult with your SAP functional consultant or technical team if necessary.
  
  
  
  Review Business Processes:
  
  Ensure that the business processes align with the requirement type settings. If combining requirements is necessary for your business process, consider whether a different requirement type should be used.
  
  
  
  Testing:
  
  After making any changes, conduct thorough testing to ensure that the changes resolve the issue and do not introduce new problems.
  
  
  
  Related Information:
  
  Documentation: Refer to SAP documentation for detailed information on requirement types and their configurations.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after checking the configuration and making necessary adjustments, it may be beneficial to involve SAP support for further assistance.