Do you have any question about this error?
Message type: E = Error
Message class: HRPAYFI00 - Messages for Finnish payroll handling
Message number: 003
Message text: Maximal distance between sequences absences not specified (const FISDY).
The maximum time between sequences absence to be regarded as one
absence hasn't been specified in the payroll constants table - constant
FISDY.
Payroll was stopped since absence handling cannot be processed
properly.
Check your payroll constant customizing in table "Payroll
Constants"(T511K)
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.
HRPAYFI00003
- Maximal distance between sequences absences not specified (const FISDY). ?The SAP error message HRPAYFI00003 with the description "Maximal distance between sequences absences not specified (const FISDY)" typically occurs in the context of payroll processing, particularly when dealing with absence management in the Human Resources (HR) module. This error indicates that there is a configuration issue related to the maximum allowable distance between absence sequences, which is defined by the constant FISDY.
Cause:
- Configuration Issue: The constant FISDY (which stands for "Maximum Distance Between Absences in Days") has not been defined in the system. This constant is used to determine the maximum number of days that can exist between two absence records for an employee.
- Absence Records: There may be absence records that are not properly configured or that exceed the defined limits, leading to inconsistencies in payroll calculations.
- Customizations: If there are custom developments or modifications in the payroll process, they may not align with the standard configurations, causing this error.
Solution:
Define the Constant:
- Go to the SAP Customizing Implementation Guide (SPRO).
- Navigate to Personnel Management > Payroll > Payroll: General Settings > Define Constants.
- Look for the constant FISDY and ensure it is defined with an appropriate value that reflects the maximum distance allowed between absence sequences.
Check Absence Records:
- Review the absence records for the employee(s) in question to ensure that they are correctly entered and do not exceed the defined limits.
- Make sure that there are no gaps in the absence records that would violate the defined maximum distance.
Testing:
- After making the necessary changes, run a test payroll to ensure that the error does not reoccur and that the payroll calculations are correct.
Consult Documentation:
- Refer to SAP documentation or notes related to payroll processing and absence management for additional guidance on configuring constants and handling absence records.
Seek Support:
- If the issue persists after checking the configuration and absence records, consider reaching out to SAP support or consulting with an SAP HR expert for further assistance.
Related Information:
By addressing the configuration of the constant FISDY and ensuring that absence records are properly maintained, you should be able to resolve the HRPAYFI00003 error.
Get instant SAP help. Start your 7-day free trial now.
HRPAYFI00002
Total maximal time for sequenced absences not specified (constant FISDT).
What causes this issue? Constant FISDT in T511K is not specified. So the total time interval for sequenced absences cannot be determined.System Respo...
HRPAYFI00001
No evaluation rule (T7FISL) found to &1 &2 &3 with &4 days.
What causes this issue? It ws tried to access a Finnish absence evaluation rule that does not exist in table "Lenth of sickpay periods (XNAB)&qu...
HRPAYFI00004
Please check whether the entry & & & in V_T7FI549Q is correct
What causes this issue? Table entry in T7FI549Q possibly incomplete or missing.System Response The system issues an error message and will not allow...
HRPAYFI00005
Please check whether the entry & & & in V_T549Q is correct
What causes this issue? The key to read T549Q is taken from another related table for Finland T7FI549Q. Hence, if the table key specified in the mess...
Click on this link to search all SAP messages.