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

SAP Error Message - Details

• 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 call horizon.
  
  Solution:
  
  Check Existing Call Horizons: Review the existing call horizons for the object or task in question. You can do this by navigating to the relevant maintenance plan or order and checking the scheduling details.
  Modify or Delete Duplicate Entries: If you find that a call horizon is already defined, you may need to modify or delete the duplicate entry. Ensure that you only have one active call horizon for the specific object.
  Review Configuration Settings: Check the configuration settings related to maintenance planning and scheduling to ensure that there are no conflicting settings that could lead to this error.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on managing call horizons and maintenance plans.
  Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as IP01 (Create Maintenance Plan), IP02 (Change Maintenance Plan), and IP03 (Display Maintenance Plan) to manage maintenance plans effectively.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that could resolve the issue.
  User Roles and Authorizations: Ensure that the user has the appropriate roles and authorizations to make changes to maintenance plans and call horizons.
  
  By following these steps, you should be able to identify the cause of the EAMS_SP105 error and implement a solution to resolve it.