Do you have any question about this error?
Message type: E = Error
Message class: 70 - HR: Messages in Master Data Reporting
Message number: 013
Message text: No personnel numbers exist for country grouping &1
The personnel numbers that are to be converted are selected from
infotype table PA0001 <LS>Personnel Master Record Infotype 0001
(Organizational Assignment)</>.
At the moment, no entry exists in infotype table PA0001 for the
relevant employee group/subgroup combinations from table T5032
<LS>Employee Group/Subgroup Country Assignment</>.
The customizing tables have been converted. The infotype tables have
not yet been edited because no personnel number is affected by the
currency conversion.
You will find further information about pay scale currency conversion
in the documentation of report <DS:RE.RPUEMU00>RPUEMU00</>.
Error message extract from SAP system. Copyright SAP SE.
70013
- No personnel numbers exist for country grouping &1 ?The SAP error message "70013 No personnel numbers exist for country grouping &1" typically occurs when the system is unable to find any personnel numbers associated with the specified country grouping in the Human Resources (HR) module. This can happen for various reasons, and understanding the cause and solution can help resolve the issue.
Cause:
- Missing Personnel Numbers: There are no personnel numbers created for the specified country grouping in the system.
- Incorrect Country Grouping: The country grouping specified in the error message may not be correctly configured or may not correspond to any existing personnel numbers.
- Data Migration Issues: If data has been migrated from another system, there may be inconsistencies or missing data related to personnel numbers.
- Configuration Issues: The configuration settings for the country grouping in the SAP system may not be set up correctly.
Solution:
Check Personnel Numbers: Verify if there are any personnel numbers created for the specified country grouping. You can do this by navigating to the relevant HR infotypes or using transaction codes like PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data).
Verify Country Grouping: Ensure that the country grouping specified in the error message is correct. You can check the country grouping settings in the configuration (transaction code SPRO) under:
- Personnel Management > Administration > Customizing Procedures > Country Grouping.
Create Personnel Numbers: If no personnel numbers exist for the country grouping, you may need to create them. This can be done by creating new employee records in the system.
Check Data Migration: If the issue arose after a data migration, review the migration process to ensure that all personnel numbers were correctly transferred and mapped to the appropriate country groupings.
Consult Documentation: Review SAP documentation or consult with your SAP support team for any specific configurations or settings that may need to be adjusted.
Debugging: If the issue persists, consider debugging the program or transaction that triggered the error to identify any underlying issues.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the problem continues, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
70012
No employee groups or subgroups exist for personnel country grouping &1
What causes this issue? In order to determine the personnel numbers that are to be converted, all employee group/subgroup combinations that are avail...
70011
No entries found in T510 or T710 for the selections specified
What causes this issue? You have selected a combination of type and area that is not available in table T510 <LS>Pay Scale Groups</> nor ...
70014
Table &1 has already been converted for &2 for &3
What causes this issue? Table &1 has already been converted for key conversion date &3. It is therefore not possible to convert it again. Pl...
70015
Table &1 processed again for &2 for &3 (resume)
What causes this issue? Table &1 was already processed, but the processing was terminated. Now, the processing has restarted. Please note the fol...
Click on this link to search all SAP messages.