Do you have any question about this error?
Message type: E = Error
Message class: 5Z - IS-HR/PSG Public Sector Payroll - Germany
Message number: 123
Message text: Infotype is not evaluated for January
The pension recipient statistics are created every year in January and
also evaluate the infotype for this month.
Since the infotype record is not valid in January, it is not evaluated
by the statistics.
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.
5Z123
- Infotype is not evaluated for January ?The SAP error message 5Z123, which states "Infotype is not evaluated for January," typically occurs in the context of personnel administration or payroll processing when the system is unable to evaluate a specific infotype for the month of January. This can happen for various reasons, and understanding the cause and solution can help resolve the issue.
Causes:
Missing Infotype Records: The infotype in question may not have any records for the employee for the month of January. This could be due to the employee not having any relevant data entered for that period.
Incorrect Validity Dates: The validity dates of the infotype records may not cover the month of January. If the records are valid only for other months, the system will not evaluate them for January.
Payroll Control Record Settings: The payroll control record may not be set up correctly for the January payroll run, which can affect the evaluation of infotypes.
Data Entry Errors: There may be data entry errors or inconsistencies in the employee's master data that prevent the infotype from being evaluated.
Configuration Issues: There could be configuration issues in the system related to the infotype or payroll processing that need to be addressed.
Solutions:
Check Infotype Records: Verify that the relevant infotype records exist for the employee in question. You can do this by using transaction codes like PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data).
Review Validity Dates: Ensure that the validity dates of the infotype records include January. If they do not, you may need to create or adjust the records accordingly.
Examine Payroll Control Record: Check the payroll control record settings to ensure that they are correctly configured for the January payroll run. You can use transaction code PC00_MXX_CEDT (where XX is your country code) to access the payroll control record.
Correct Data Entry: If there are any data entry errors, correct them in the employee's master data.
Consult Configuration: If the issue persists, consult with your SAP HR configuration team to review the settings related to the infotype and payroll processing.
Run Consistency Checks: Use transaction code PE03 to run consistency checks on the infotype data to identify any discrepancies.
Related Information:
If the problem continues after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP HR and payroll.
Get instant SAP help. Start your 7-day free trial now.
5Z122
Validity period of infotype is not valid
What causes this issue? The validity period of the infotype covers a period of more than one calendar year. This is only possible if the "Headco...
5Z121
Invalid period
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5Z124
Time unit & is not permitted
What causes this issue? You can only use special time units to specify the period after which the premium rate can be set for the leave and sick pay ...
5Z125
Conversion in client & for table name & is not possible
What causes this issue? The MOTAB field in Customizing table T5D7G cannot be converted since custom fixed values have been added to the field (custom...
Click on this link to search all SAP messages.