How To Fix 28130 - Net complete - constraint/rule cannot be entered in net

SAP Error Message - Details

• Message type: E = Error

• Message class: 28 - Configuration

• Message number: 130

• Message text: Net complete - constraint/rule cannot be entered in net

What causes this issue?

There is a maximum number of rules (value assignment alternatives for
constraints) which can be stored in a constraint net. This limit has
now been reached. For this reason, you can no longer enter the
constraint in the constraint net (active).

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?

Assign the constraint to another constraint net, possibly a new one.
You can work with more than one constraint net at one time.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 28130 - Net complete - constraint/rule cannot be entered in net ?

  The SAP error message 28130, which states "Net complete - constraint/rule cannot be entered in net," typically occurs in the context of pricing and conditions in SAP, particularly when dealing with condition records in pricing procedures. This error indicates that there is a conflict or issue with the constraints or rules defined for the pricing conditions.
  Cause:
  
  Incompatible Condition Types: The error may arise if there are incompatible condition types or rules defined in the pricing procedure that cannot coexist.
  Incorrect Configuration: There may be a misconfiguration in the pricing procedure or condition records that leads to this error.
  Missing or Incorrect Condition Records: If the necessary condition records are missing or incorrectly set up, it can trigger this error.
  Hierarchy Issues: If the pricing hierarchy is not correctly defined or if there are issues with the sequence of conditions, it can lead to this error.
  
  Solution:
  
  Review Pricing Procedure: Check the pricing procedure assigned to the sales document. Ensure that the condition types and their sequence are correctly defined and compatible.
  Check Condition Records: Verify that all necessary condition records are created and active. Ensure that there are no missing records that are required for the pricing calculation.
  Analyze Constraints: Look into the constraints or rules defined for the condition types. Make sure that they are logically consistent and do not conflict with each other.
  Debugging: If the issue persists, consider using the debugging tools in SAP to trace the pricing calculation and identify where the error is occurring.
  Consult Documentation: Refer to SAP documentation or notes related to pricing procedures and condition types for any specific guidance or known issues.
  SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, providing them with the details of the error and the context in which it occurs.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to manage condition records.
  Pricing Procedure Configuration: The configuration can be accessed via transaction SPRO under Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional insights.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message 28130 in SAP.