How To Fix PRC_MIG_TRANSL_MSG091 - Data found in field KONV-&1 that is not in PRCD_ELEMENTS. See long text.

PRC_MIG_TRANSL_MSG091 - Overview

• Message type: E = Error

• Message class: PRC_MIG_TRANSL_MSG - KONV migration translatable messages

• Message number: 091

• Message text: Data found in field KONV-&1 that is not in PRCD_ELEMENTS. See long text.

What causes this issue?

Data found in the field KONV-&V1& but the field does not exist in
PRCD_ELEMENTS.

System Response

Data processing continued without migrating KONV-&V1& to PRCD_ELEMENTS.

How to fix this error?

If you want to keep the data in the field KONV-&V1&, do the following:
1. Create an SAP ticket to add field KONV-&V1& to the new pricing table
PRCD_ELEMENTS (Note: use component SD-BF-PR).
2. SAP will need to implement this change in order to proceed.
3. Create a report to migrate field KONV-&V1& to PRCD_ELEMENTS.
4. Run the report above.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

If the data in KONV-&V1& is not needed and you don't want to migrate it,
no action is required. The data in field &V1& remained in KONV but was
not migrated to PRCD_ELEMENTS.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

PRC_MIG_TRANSL_MSG091 - Details

• The SAP error message PRC_MIG_TRANSL_MSG091 indicates that there is a discrepancy between the data found in the KONV table (which stores condition records for pricing) and the PRCD_ELEMENTS table (which is used in the context of the new pricing structure in SAP S/4HANA). This error typically arises during data migration or when trying to execute pricing-related transactions.
  
  Cause:
  The error occurs when there are entries in the KONV table that do not have corresponding entries in the PRCD_ELEMENTS table. This can happen due to several reasons, including:
  
  Data Migration Issues: During the migration from an older SAP system to S/4HANA, some condition records may not have been properly migrated or mapped to the new structure.
  Inconsistent Data: There may be inconsistencies in the pricing data, such as orphaned records or records that were not properly maintained.
  Custom Developments: If there are custom developments or modifications in the pricing logic, they may lead to discrepancies between