How To Fix MIGRATE_PRICING_MSG094 - Data in custom field KONV-&1 no longer exists in PRCD_ELEMENTS

MIGRATE_PRICING_MSG094 - Overview

• Message type: E = Error

• Message class: MIGRATE_PRICING_MSG - Pricing Migration Messages

• Message number: 094

• Message text: Data in custom field KONV-&1 no longer exists in PRCD_ELEMENTS

What causes this issue?

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

System Response

Data processing will continue without migrating KONV-&V1& to
PRCD_ELEMENTS. However, the data in field KONV-&V1& will be lost.

How to fix this error?

If you want to keep data in the field KONV-&V1&, you will first need to
restore the data from your backups, then:
1. Add a customer append field named &V1& to table PRCD_ELEMENTS that
exactly matches the field of the same name in table KONV. For example,
with the same data element, data type, length, decimal places and short
description.
2. Create a report to migrate field KONV-&V1& to PRCD_ELEMENTS.
3. Run the report above.
If the data in KONV-&V1& is not needed and you don't want to migrate it,
no action is required.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MIGRATE_PRICING_MSG094 - Data in custom field KONV-&1 no longer exists in PRCD_ELEMENTS ?

  The SAP error message MIGRATE_PRICING_MSG094 indicates that there is an issue with the data migration process related to pricing conditions. Specifically, it states that data in a custom field in the KONV table (which stores condition records for pricing) no longer exists in the PRCD_ELEMENTS table (which is used in the new pricing structure in S/4HANA).
  
  Cause:
  
  Data Migration Issues: This error typically arises during the migration from an older SAP system (like ECC) to S/4HANA. The migration process may not have correctly transferred all relevant data from the KONV table to the new PRCD_ELEMENTS structure.
  Custom Fields: If you have custom fields in the KONV table that are not properly mapped or do not have corresponding entries in the PRCD_ELEMENTS table, this error can occur.
  Inconsistent Data: There may be inconsistencies in the data between the two tables, especially if the migration process was interrupted or if there were manual changes made to