How To Fix EAMS_SP105 - Call horizon has already been defined as &1 &2

EAMS_SP105 - Overview

• Message type: E = Error

• Message class: EAMS_SP - EAMS: Service Provider Layer

• Message number: 105

• Message text: Call horizon has already been defined as &1 &2

What causes this issue?

You want to edit the planning data of a maintenance order on the Web UI
and enter, change, or display the value in the <LS>Call horizon</>
field. This is not possible because the call horizon of the maintenance
order has been defined in days or working days in the SAP ERP system.

System Response

Since the calculation types DAY (days) and FCD (factory calendar days)
are not available on the Web UI, the system cannot display the valid
value for the call horizon and therefore does not allow any changes to
be made to the <LS>Call horizon</> field.

How to fix this error?

You have defined &V1& &V2& for the call horizon of this maintenance
order on the user interface of the SAP ERP system. The system therefore
generates maintenance call objects &V1& days/working days before the
planned date. You can change this value on the user interface of the SAP
ERP system, but not on the WEB UI.

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 EAMS_SP105 - Call horizon has already been defined as &1 &2 ?

  The SAP error message EAMS_SP105, which states "Call horizon has already been defined as &1 &2," typically occurs in the context of SAP's Asset Management or Plant Maintenance modules. This error indicates that there is an attempt to define a call horizon (a time frame for scheduling maintenance or service calls) that has already been set for a particular object or task.
  
  Cause:
  
  Duplicate Definition: The error is primarily caused by trying to define a call horizon that has already been defined for the same object or task. This can happen if the user is attempting to create or modify a maintenance plan, service order, or similar object where the call horizon is already in place.
  
  Configuration Issues: There may be issues in the configuration settings of the maintenance plans or scheduling parameters that lead to conflicts.
  Data Integrity Issues: There could be inconsistencies in the data, such as multiple entries for the same