How To Fix FITVPS350 - Date of absence does not lie within the separation allowance period

SAP Error Message - Details

• Message type: E = Error

• Message class: FITVPS -

• Message number: 350

• Message text: Date of absence does not lie within the separation allowance period

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FITVPS350 - Date of absence does not lie within the separation allowance period ?

  The SAP error message FITVPS350 indicates that there is an issue with the date of absence specified in a separation allowance process. Specifically, it means that the date of absence does not fall within the defined separation allowance period. This can occur in various HR processes, particularly when dealing with employee separations, terminations, or leave of absence.
  Cause:
  
  Incorrect Date Entry: The date of absence entered may be outside the range of the separation allowance period defined in the system.
  Configuration Issues: The separation allowance period may not be correctly configured in the system, leading to discrepancies between the defined period and the absence date.
  Employee Status: The employee's status may not be correctly set, or the separation allowance may not be applicable to the employee's current status.
  Time Evaluation: The time evaluation settings may not be aligned with the separation allowance rules, causing the system to reject valid dates.
  
  Solution:
  
  Verify Dates: Check the date of absence entered and ensure it falls within the separation allowance period. Adjust the date if necessary.
  Review Configuration: Consult with your SAP HR configuration team to ensure that the separation allowance period is correctly set up in the system. This includes checking the start and end dates for the separation allowance.
  Employee Status Check: Ensure that the employee's status is appropriate for the separation allowance being processed. If the employee is not eligible, the absence date will not be valid.
  Consult Documentation: Review SAP documentation or help files related to separation allowances to understand the specific requirements and configurations needed.
  Testing: If changes are made to the configuration, conduct tests to ensure that the error does not reoccur and that the system behaves as expected.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as PA30 (Maintain HR Master Data) or PA20 (Display HR Master Data) to check employee records and absence types.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on separation allowances.
  HR Module: This error is typically related to the SAP HR module, so ensure that you have the necessary permissions and access to make changes or view configurations.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP HR expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.