Do you have any question about this error?
Message type: E = Error
Message class: 5G - HR: Messages for Britain
Message number: 622
Message text: Infotype not found in feature SSPLP; no check for change of per.calendar
When infotype Absences (2001) is updated, the employee#s personal
calendar is also amended accordingly. The feature <ZK>SSP/SMP Infotype
- PIW Linking Decision </>(SSPLP) checks whether any such changes to
the personal calendar are relevant to linked Periods of Incapacity for
Work (PIWs) for calculation of Statutory Sick Pay (SSP).
Feature SSPLP is currently missing an entry for the relevant infotype
and consequently, no check can be made to determine whether changes to
the employee#s personal calendar involve linked PIWs.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Maintain feature SSPLP to enable correct updating of the employee
personal calendar. This can be performed using transaction PE03 in the
SAP R/3 System.
Error message extract from SAP system. Copyright SAP SE.
5G622
- Infotype not found in feature SSPLP; no check for change of per.calendar ?The SAP error message 5G622 indicates that the system could not find the specified infotype in the feature SSPLP. This typically occurs in the context of personnel administration, particularly when dealing with personnel calendars or related data.
Cause:
- Missing Infotype: The infotype that the system is trying to access may not be defined in the system or may not be correctly configured.
- Feature Configuration: The feature SSPLP may not be properly set up to include the necessary infotypes for the personnel calendar.
- Customizations: If there have been customizations or modifications to the standard SAP configuration, it may lead to this error if the custom infotypes are not properly linked or defined.
- Data Issues: There may be issues with the data in the infotype, such as missing entries or incorrect configurations.
Solution:
Check Infotype Configuration:
- Go to transaction SPRO (SAP Reference IMG).
- Navigate to Personnel Management -> Personnel Administration -> Infotypes.
- Ensure that the required infotype is defined and active.
Review Feature SSPLP:
- Use transaction PE03 to check the feature SSPLP.
- Ensure that the infotype you are trying to access is included in the feature logic.
- If necessary, modify the feature to include the correct infotype.
Check for Customizations:
- If your organization has made customizations, review those changes to ensure they are not causing the issue.
- Consult with your SAP technical team or ABAP developers if custom code is involved.
Data Validation:
- Check the data in the infotype for any inconsistencies or missing entries.
- Use transaction PA20 or PA30 to view the infotype records and ensure they are correctly populated.
Testing:
- After making the necessary changes, test the functionality again to see if the error persists.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
5G621
Feature SSPLP missing; no check made for change of personal calendar
What causes this issue? When infotype Absences (2001) is updated, the employee#s personal calendar is also amended accordingly. The feature <ZK>...
5G620
Personal calendar date in payroll status set to &
What causes this issue? By changing this absence record, the system has set the personal calendar date and the retroactive date back to the start of ...
5G623
Error in feature SSPLP; no check for change of personal calendar
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5G624
Absence is not SSP/SMP relevant; no check for change of personal calendar
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.