How To Fix MIGRATE_PRICING_MSG093 - Data in deprecated field KONV-&1 no longer exists in PRCD_ELEMENTS

SAP Error Message - Details

• Message type: E = Error

• Message class: MIGRATE_PRICING_MSG - Pricing Migration Messages

• Message number: 093

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

What causes this issue?

Data has been found in the deprecated 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, data in the 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. 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.
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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

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

  The SAP error message MIGRATE_PRICING_MSG093 indicates that there is an issue with the migration of pricing data, specifically related to the KONV table, which is used for storing condition records in SAP. The message states that data in a deprecated field (KONV-&1) no longer exists in the PRCD_ELEMENTS table, which is part of the new pricing structure introduced in SAP S/4HANA.
  
  Cause:
  
  Data Migration: The error typically occurs during the migration process from an older version of SAP (like SAP ECC) to SAP S/4HANA. The KONV table is part of the old pricing structure, and the migration process is trying to access data that has been deprecated or is no longer valid in the new pricing model.
  Inconsistent Data: There may be inconsistencies in the data that are being migrated, such as missing or incorrectly mapped condition records.
  
  Configuration Issues: The configuration settings for pricing in the new system may not be aligned with