How To Fix FITVPS214 - Absence from main destination is not allowed to last longer than & days

SAP Error Message - Details

• Message type: E = Error

• Message class: FITVPS -

• Message number: 214

• Message text: Absence from main destination is not allowed to last longer than & days

What causes this issue?

The reduction of accommodation per diems for the main destination was
terminated due to the length of this destination (the System checks
whether the absence from the main destination lasts more than 10 days,
this means that for 10 day trips this depends on whether the end time
is later than the start time for the stopover)

System Response

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

How to fix this error?

Create the stopover as a separate trip.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FITVPS214 - Absence from main destination is not allowed to last longer than & days ?

  The SAP error message FITVPS214 indicates that an absence from the main destination (such as a work location or a specific area of responsibility) is not allowed to last longer than a specified number of days. This error typically arises in the context of travel management or personnel administration within SAP, particularly when dealing with employee absences or travel requests.
  
  Cause:
  
  Configuration Settings: The error is often due to configuration settings in the SAP system that define the maximum allowable duration for an absence from the main destination. This is typically set to ensure compliance with company policies or legal regulations.
  Data Entry Error: The user may have inadvertently entered an absence duration that exceeds the allowed limit.
  Business Rules: The organization may have specific business rules that restrict the length of time an employee can be absent from their main work location.
  
  
  Solution:
  
  Check Configuration: Review the configuration settings in the SAP system related to