How To Fix GU672 - Condition in SUBACT & SEQNR cannot be converted

GU672 - Overview

• Message type: E = Error

• Message class: GU - FI-SL utilities

• Message number: 672

• Message text: Condition in SUBACT & SEQNR cannot be converted

What causes this issue?

During conversion of the previously mentioned condition, no rule name
could be determined. The automatically created rule name is put
together as follows:
X y (y = 1-9) substitution process number
Unfortunately, all of these rule names are already taken.

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?

If possible, delete a rule from this naming area and restart the
conversion.

Error message extract from SAP system. Copyright SAP SE.

GU672 - Details

• The SAP error message GU672, which states "Condition in SUBACT & SEQNR cannot be converted," typically occurs in the context of pricing and condition records in SAP. This error indicates that there is an issue with the conversion of a condition record, specifically related to the sub-activity (SUBACT) and sequence number (SEQNR) of a condition.
  Causes:
  
  Data Inconsistency: There may be inconsistencies in the condition records, such as missing or incorrect data in the fields related to SUBACT and SEQNR.
  Incorrect Configuration: The pricing procedure or condition types may not be configured correctly, leading to issues during the conversion process.
  Custom Code Issues: If there are custom enhancements or modifications in the pricing logic, they may not handle certain conditions properly.
  Transport Issues: If the condition records were transported from one system to another, there may be issues with the transport that led to data corruption or missing entries.
  
  Solutions:
  
  Check Condition Records: Review the condition records