How To Fix PPH_MRP211 - MRP Live on HANA does not support VC change of BOM item field: &1

PPH_MRP211 - Overview

• Message type: E = Error

• Message class: PPH_MRP -

• Message number: 211

• Message text: MRP Live on HANA does not support VC change of BOM item field: &1

What causes this issue?

You tried to change one of the following fields using variant
configuration:
IDNRK - BOM Component
ITSOB - Special procurement key of planned order component
SCHGT - Bulk material indicator
DSPST - BOM explosion type
LGORT - Storage location
PRVBE - Production supply area

System Response

The material is planned in classic MRP (ABAP).

How to fix this error?

If you want to include the material in the MRP Live on HANA run, avoid
changing these fields using variant configuration.

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 PPH_MRP211 - MRP Live on HANA does not support VC change of BOM item field: &1 ?

  The SAP error message PPH_MRP211 indicates that there is an issue with the MRP Live functionality in SAP S/4HANA when it comes to handling variant configuration (VC) changes for a Bill of Materials (BOM) item. Specifically, this error arises when there is an attempt to change a field in a BOM item that is not supported by the MRP Live process.
  
  Cause:
  The error typically occurs due to the following reasons:
  
  Unsupported Changes: MRP Live on HANA does not support certain changes to BOM items that are related to variant configuration. This could include changes to fields that are critical for MRP processing.
  
  Configuration Issues: There may be issues with how the BOM is configured, especially if it involves variant configuration settings that are not compatible with MRP Live.
  Data Integrity: The data being processed may not meet the requirements for MRP Live, leading to this error when attempting to execute MRP runs.
  
  
  Solution:
  To resolve the