How To Fix CNV_PE_CHECK321 - Split is not defined, relevance identifiers cannot be defined

CNV_PE_CHECK321 - Overview

• Message type: E = Error

• Message class: CNV_PE_CHECK - Check Framework messages for posting engine

• Message number: 321

• Message text: Split is not defined, relevance identifiers cannot be defined

What causes this issue?

Split is <ZH>not </>defined on structure level in the knowledge base.
Therefore relevance identifiers cannot be defined.
A split is defined if either <ZK>Split Max. </>or <ZK>Split Flexible</>
is set and a <ZK>Split Rule</> is defined.
If a split is defined on structure (STR) level, then <ZK>Condition Rules
</> must be defined for each relevance identifier on or relevance
identifier level.
A split can also be defined on relevance identifier level. This depends
on the following requirements:
No split is defined on structure level.
<ZK>Sender Parameter</> is unassigned on structure level.
For each relevance identifier entry on relevance identifier level a
sender parameter is assigned.
All sender parameters are different on relevance identifier level.
If <ZK>Split Flexible</> is defined on relevance identifier level a
split rule is required. A mixture of split rules and condition rules is
<ZH>not </>allowed on relevance identifier level.

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?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_PE_CHECK321 - Details

• The SAP error message CNV_PE_CHECK321 with the description "Split is not defined, relevance identifiers cannot be defined" typically occurs in the context of data migration or conversion processes, particularly when using the SAP Landscape Transformation (SLT) or SAP Data Services tools. This error indicates that the system is unable to determine how to split or categorize the data based on the relevance identifiers that are expected to be defined for the operation.
  Causes:
  
  Missing Configuration: The error may arise if the necessary configuration for defining splits or relevance identifiers is missing or incomplete in the migration or transformation settings.
  Data Model Issues: There may be inconsistencies or issues in the data model that prevent the system from determining how to categorize the data.
  Incorrect Mapping: If the mapping of fields or data structures is not correctly defined, it can lead to this error.
  Version Compatibility: Sometimes, the error can occur due to compatibility issues between