Do you have any question about this error?
Message type: E = Error
Message class: HRPAYDEE2 - Message Class ELStAM Procedure
Message number: 338
Message text: No Per. No. found for ID No. &1 and ER Tax No. &3 on &2 (VR)
When using distributed reporting, there is no personnel number available
in the decentralized systems for the data transferred (identification
number, employer tax number, and key date).
The error may occur for two different reasons as soon as ELStAM
notifications are available in the central system for the data trans
ferred:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
First case:Use the identification number to determine possible infotype records of
infotype Tax Data D (0012) in the decentralized systems, and check the
specifications for the ELStAM procedure in these systems.
Check if the employer tax number has changed.
After correcting the data, make the assignment using report
<DS:RE.RPCE2ZD0>ELStAM: Transfer XML Data to ELStAM Table - Distributed
Reporting</> (RPCE2ZD0). Mark the corresponding line with the status
"not assigned" and choose "assignment". You may then continue to process
the data using report <DS:RE.RPCE2VD0_IN>ELStAM Procedure: Update Master
Data Using ELStAM Procedure</> (RPCE2VD0_IN).
Error message extract from SAP system. Copyright SAP SE.
HRPAYDEE2338
- No Per. No. found for ID No. &1 and ER Tax No. &3 on &2 (VR) ?The SAP error message HRPAYDEE2338 indicates that the system could not find a personnel number (Per. No.) for a given ID number and employee tax number on a specific date. This error typically occurs in the context of payroll processing or when generating reports related to employee data.
Cause:
- Missing Personnel Data: The personnel number may not exist in the system for the specified ID number and tax number.
- Incorrect ID or Tax Number: The ID number or tax number provided may be incorrect or not properly linked to the personnel number.
- Data Migration Issues: If data was recently migrated or imported, there may be inconsistencies or missing records.
- Time Period Issues: The date specified may fall outside the range of valid employment or payroll records for the employee.
- Configuration Issues: There may be configuration issues in the payroll or personnel administration modules.
Solution:
- Verify Data: Check the ID number and tax number against the personnel records in the system to ensure they are correct.
- Check Personnel Records: Use transaction codes like PA20 or PA30 to look up the employee's personnel number and verify that it exists and is active.
- Review Payroll Data: Ensure that the employee has been properly set up in the payroll system and that all necessary data has been entered.
- Check Time Period: Confirm that the date specified in the error message is within the valid employment period for the employee.
- Consult with HR/Payroll Team: If the issue persists, consult with your HR or payroll team to investigate any potential data migration issues or configuration problems.
- Debugging: If you have access to technical resources, debugging the payroll process may help identify the root cause of the issue.
Related Information:
If the problem continues after following these steps, it may be necessary to escalate the issue to your SAP support team or consult with SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
HRPAYDEE2337
AGSTNR not filled
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDEE2336
IDNR not filled
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDEE2339
Notifications with NDTIC &1 were already processed (VH999999999).
What causes this issue? If a processing data ticket has already been indicated as processed through earlier processing of a change list and the new c...
HRPAYDEE2340
Notifications with NDTIC &1 were already processed (VH551001001).
What causes this issue? If a processing data ticket has already been indicated as processed through earlier processing of a change list and the new c...
Click on this link to search all SAP messages.