How To Fix 1G070 - Condition is assigned to another condition group

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 070

• Message text: Condition is assigned to another condition group

What causes this issue?

You want to delete a condition that is not yet assigned to a condition
group.

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?

Check the where-used list to see to which condition group the condition
is assigned. Cancel the assignment. Then repeat the deletion.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1G070 - Condition is assigned to another condition group ?

  The SAP error message 1G070 ("Condition is assigned to another condition group") typically occurs in the context of pricing conditions in SAP, particularly when dealing with condition records in the pricing procedure. This error indicates that the condition you are trying to assign or modify is already linked to a different condition group, which prevents you from making the desired changes.
  Cause:
  
  Existing Assignment: The condition record you are trying to work with is already assigned to a different condition group. This can happen if the same condition type is used in multiple pricing procedures or if there are overlapping configurations.
  Configuration Issues: There may be issues in the configuration of the pricing procedure or condition types that lead to conflicts.
  Data Integrity: The system may have integrity checks that prevent the same condition from being assigned to multiple groups simultaneously.
  
  Solution:
  
  
  Check Condition Assignment:
  
  Use transaction code VK13 (Display Condition) to check the existing assignments of the condition record. Identify which condition group it is currently assigned to.
  If you need to change the assignment, you may need to delete the existing assignment first (if appropriate) using VK12 (Change Condition).
  
  
  
  Review Configuration:
  
  Go to transaction SPRO and navigate to the pricing procedure configuration. Check the condition types and their assignments to ensure there are no conflicts.
  Ensure that the condition types are correctly configured and that they are not inadvertently linked to multiple condition groups.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for specific details on the condition types and their intended use within your pricing procedures.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists and you cannot resolve it through the above steps, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK13: Display Condition Records
  VK12: Change Condition Records
  SPRO: Customizing Implementation Guide
  
  
  Condition Types: Understand the specific condition types involved and their roles in the pricing procedure.
  Pricing Procedure: Familiarize yourself with the pricing procedure configuration and how condition groups are structured within it.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.