How To Fix CNV_PE328 - No split defined on KB STR level for parameter &1

CNV_PE328 - Overview

• Message type: E = Error

• Message class: CNV_PE - General messages for posting engine

• Message number: 328

• Message text: No split defined on KB STR level for parameter &1

What causes this issue?

In order to assign a condition rule on relevance identifier level, a
split must be defined on structure level in the knowledge base. This is
not the case.
A split is defined in the following cases
<ZK>Split Max.</> is set.
<ZK>Split Flexible</> and a split rule is defined.
If a split is defined on structure level (STR), condition rules must be
defined for each relevance identifier on relevance identifier level
(REL_ID).
A split can also be defined on relevance identifier level. This depends
on the following requirements:
No split is defined on structure level.
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_PE328 - Details

• The SAP error message CNV_PE328 indicates that there is no split defined at the Knowledge Base (KB) structure level for the specified parameter. This error typically arises during data migration or conversion processes, particularly when using SAP's Conversion Tools or during the execution of specific programs that rely on Knowledge Base structures.
  
  Cause:
  
  Missing Configuration: The error usually occurs when the system expects a split configuration for a specific parameter at the KB structure level, but it has not been defined.
  Incorrect Parameter: The parameter specified in the error message may not be correctly set up in the system or may not exist in the expected format.
  Data Migration Issues: If you are performing data migration, it could be that the mapping or transformation rules are not correctly defined for the data being processed.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the relevant configuration settings in the SAP system and verify if the split for the specified parameter