How To Fix EL106 - Dev. &1, MR date &2: Deviation fr. previous MR > perm. deviat. fixed val.

SAP Error Message - Details

• Message type: E = Error

• Message class: EL - IS-U meter reading data processing

• Message number: 106

• Message text: Dev. &1, MR date &2: Deviation fr. previous MR > perm. deviat. fixed val.

What causes this issue?

Validation 96 (automatic validation) recognized that the value exceeded
or fell below the permissible deviation. This check is only valid for
registers that relate to a nonactive or disconnected installation, or
for registers that are not yet allocated to an installation.

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

Devices with installation allocation:
----------------------------
The deviation fixed value is stored in table TE409. It specifies the
permissible deviation in the the last register decimal place.
Example:
Deviation fixed value: 5
Previous meter reading: 100.001 kWh
Current meter reading: 100.009 kWh
The deviation in the last register decimal place is 8. This value is
greater than 5 and therefore the meter reading is implausible.
Devices without installation allocation:
-----------------------------
The deviation fixed value for devices without an installation
allocation is stored in table TE437 in accordance with the unit of
measurement for meter reading.
Example:
Deviation fixed value:
5 Previous meter reading: 100.001
kWh Current meter reading: 100.003 kWh
The deviation in the last register decimal place is 2. This value is
less than 5 and therefore the meter reading is plausible.

System Response

How to fix this error?

The meter reading can be released or reset for later processing.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EL106 - Dev. &1, MR date &2: Deviation fr. previous MR > perm. deviat. fixed val. ?

  The SAP error message EL106 indicates that there is a deviation in the material requirements (MR) date that exceeds the permitted deviation fixed value. This error typically occurs in the context of production planning or material management when the system detects that the planned dates for materials or production orders deviate from previously established parameters.
  Cause:
  
  Deviation Exceeds Permitted Limits: The error arises when the new material requirement date (MR date) deviates from the previous MR date by more than the allowed limit set in the system.
  Configuration Settings: The fixed value for permitted deviation may be set too low in the configuration, leading to frequent errors when there are legitimate changes in the production schedule or material availability.
  Changes in Production Schedule: Changes in the production schedule, such as delays or rescheduling, can lead to deviations that exceed the allowed limits.
  Incorrect Data Entry: Manual entry errors or incorrect data in the material master or production order can also trigger this error.
  
  Solution:
  
  Review Configuration Settings: Check the configuration settings for the permitted deviation fixed value in the relevant customizing settings (transaction code SPRO). Adjust the limits if necessary to accommodate realistic deviations.
  Analyze the MR Dates: Review the material requirement dates and the reasons for the deviation. Ensure that the changes are justified and necessary.
  Adjust Production Schedule: If the deviation is due to changes in the production schedule, consider adjusting the schedule to bring the MR dates within the permitted limits.
  Correct Data Entry: Verify and correct any data entry errors in the material master or production order that may have led to the deviation.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling this error in your version of SAP.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like MD04 (Stock/Requirements List) or COHV (Mass Processing of Production Orders) to analyze the situation further.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Exits and BAdIs: If the error is frequent and affects business processes, consider implementing user exits or BAdIs to customize the behavior of the system regarding material requirements.
  
  By following these steps, you should be able to identify the cause of the EL106 error and implement a suitable solution.