How To Fix CNV20305059 - BT &1 must be included in CoAr &2

CNV20305059 - Overview

• Message type: E = Error

• Message class: CNV20305 - Messages for conversion packages in CO

• Message number: 059

• Message text: BT &1 must be included in CoAr &2

What causes this issue?

For business transaction (BT) &V1&, no number range interval is defined
in reference controlling area &V2&.
However this BT is used in the controlling areas which are to be
merged.
If the BT is used with the same number range interval in all
controlling areas which are to be merged, there is no problem, because
during the conversion this number range interval is transferred to the
reference controlling area.
In the given case, however, the controlling areas which are to be
merged have different number range intervals, so that an automatic
transfer is not possible. Consequently, an entry for this BT in the
reference controlling area is required.

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?

Maintain the BT in the reference controlling area and re-start the
programs for number ranges in this phase.

Error message extract from SAP system. Copyright SAP SE.

CNV20305059 - Details

• The SAP error message CNV20305059 typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that a specific business transaction (BT) must be included in a corresponding configuration area (CoAr).
  
  Cause:
  The error message CNV20305059 arises when there is a mismatch or missing configuration in the data migration process. Specifically, it suggests that a required business transaction (denoted as &1) is not included in the specified configuration area (denoted as &2). This can happen due to:
  
  Incomplete Configuration: The configuration for the business transaction may not have been set up correctly in the target system.
  Data Mapping Issues: The mapping of data from the source system to the target system may not include the necessary business transaction.
  Missing Customization: If the business transaction is custom or specific to your organization, it may not have been included in the standard migration templates.
  
  
  Solution:
  To resolve this