How To Fix MD107 - Simulation version is same as the version to be replaced

MD107 - Overview

• Message type: E = Error

• Message class: MD - Material Requirements Planning (MRP)

• Message number: 107

• Message text: Simulation version is same as the version to be replaced

What causes this issue?

The planned independent requirements version for long-term planning is
to be replaced by itself. A version can only be replaced by a version
with a different key.

System Response

The function "Version to be replaced" controls the usage of the
versions, for example, if you have copied an operative version for
long-term planning and at the same time you have maintained simulative
versions for some materials. If you want the system to replace the
operative version if a simulative version has been created for the
material, then you must enter the simulative version number in the
field, <LS>Version to be replaced</>.

How to fix this error?

In field, <LS>Version to be replaced</> enter a different planned
independent requirements version number from the field <LS>Version</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MD107 - Simulation version is same as the version to be replaced ?

  The SAP error message MD107, which states "Simulation version is same as the version to be replaced," typically occurs in the context of Material Requirements Planning (MRP) when you are trying to run a simulation for a planning version that is identical to the version you are attempting to replace. This situation can arise during planning activities where you are trying to simulate changes without affecting the actual planning version.
  
  Cause:
  The error is triggered because the system does not allow you to simulate a planning version that is the same as the version you are trying to replace. This is a safeguard to prevent unintended overwrites or changes to the same version.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Planning Versions: Ensure that you are selecting different planning versions for simulation and replacement. You need to have a distinct simulation version that is not the same as the version