Do you have any question about this error?
Message type: E = Error
Message class: 5G - HR: Messages for Britain
Message number: 843
Message text: More than one SSP1(L) record for employment period & to &
More than one Infotype 85 SSP1(L) record is present in an employment
period. As SSP1(L) records contain the number of SSP days from a
previous employment, only one should ever appear per employment period.
Conversion will be performed, using the first SSP1(L) found.
Check that the first SSP1(L) record in this employment period matches
the information on the employee's SSP1(L) form.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message 5G843 indicates that there is more than one SSP1(L) record for a specific employment period in the system. This typically occurs in the context of payroll processing, particularly when dealing with statutory sick pay (SSP) in the UK.
Cause:
The error arises when the system finds multiple records for the same employee's SSP1(L) for a given employment period. This can happen due to:
- Duplicate Entries: There may be duplicate SSP records created for the same period, possibly due to incorrect data entry or system processing errors.
- Incorrect Data Migration: If data was migrated from another system, it might have resulted in duplicate records.
- Configuration Issues: There may be issues in the configuration of the payroll system that allow for multiple records to be created.
Solution:
To resolve this error, you can take the following steps:
Check for Duplicate Records:
- Use transaction codes like SE16 or SE11 to access the relevant database tables (e.g., T5UKA for SSP records) and check for duplicate entries for the employee in question.
- Identify the records that are causing the conflict.
Delete or Correct Duplicate Records:
- If duplicates are found, you may need to delete or correct the unnecessary records. This can typically be done through transaction codes like PA30 (Maintain HR Master Data) or by using specific programs designed to clean up duplicate records.
- Ensure that you have the necessary authorizations to make these changes.
Review Payroll Configuration:
- Check the payroll configuration settings to ensure that they are set up correctly to prevent the creation of duplicate records in the future.
Consult Documentation:
- Review SAP notes and documentation related to this error message for any specific guidance or patches that may address the issue.
Testing:
- After making corrections, run a test payroll to ensure that the error does not reoccur and that the payroll processes correctly.
Seek Help from SAP Support:
- If the issue persists or if you are unsure about making changes, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the error message 5G843 in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
5G842 Invalid absence evaluation type for &
What causes this issue? The NCALE table for the Absence Calendar contains absen...
5G841 Missing Infotype Payroll Status (0003)
What causes this issue? The infotype record may have been accidentally deleted....
5G844 Missing Infotype SSP1(L)Form Data GB (0085) record for absence on &
What causes this issue? There is no corresponding Infotype 85 PIW record for an...
5G845 No Infotype Organizational Assignment (0001) record for absence on &
What causes this issue? No <ZH>Organizational Assignment</> (Infoty...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.