Do you have any question about this error?
Message type: E = Error
Message class: PBAS_SERVICE - HR Master Data: Service Functions
Message number: 060
Message text: Central person for &1 not found
The RPUFIXDS report (<DS:RE.RPUFIXDS>Repairing Data Sharing
Inconsistencies</>) requires access to the central person. The system
was, however, unable to determine the central person (CP) for the
personnel number (P) &V1&.
This may be due to the fact that no central person has been created for
this personnel number. It may also be because the corresponding
relationship to the central person contains errors.
The system display an error message.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You can determine and delete if necessary relationships that contain
errors using the <DS:RE.RHCHECKRELATIONS>RHCHECKRELATIONS</> report.
You can create missing central persons (CP) using the
<DS:RE.RPU46CX_CENTRAL_PERSON_ONLINE>RPU46CX_CENTRAL_PERSON_ONLINE</>
report.
Error message extract from SAP system. Copyright SAP SE.
PBAS_SERVICE060
- Central person for &1 not found ?The SAP error message PBAS_SERVICE060 indicates that the system could not find a central person record for the specified identifier (represented by
&1
). This error typically occurs in the context of personnel administration or when dealing with employee master data in SAP systems.Cause:
- Missing Central Person Record: The most common cause is that the central person record for the specified employee or individual does not exist in the system.
- Incorrect Identifier: The identifier (such as personnel number or employee ID) provided may be incorrect or not formatted properly.
- Data Synchronization Issues: If your SAP system is integrated with other systems (like an HR system), there may be synchronization issues leading to missing records.
- Authorization Issues: The user may not have the necessary authorizations to view or access the central person data.
Solution:
- Check Central Person Data: Verify if the central person record exists for the specified identifier. You can do this by using transaction codes like PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data) to check if the employee's data is present.
- Correct Identifier: Ensure that the identifier you are using is correct. Double-check for any typos or formatting issues.
- Create Missing Records: If the central person record is indeed missing, you may need to create it. This can typically be done through the HR master data maintenance transactions.
- Data Synchronization: If your system is integrated with other systems, check the integration points to ensure that data is being synchronized correctly. You may need to run data synchronization jobs or check for errors in the integration process.
- Authorization Check: Ensure that the user has the necessary authorizations to access the central person data. You may need to consult with your SAP security team to verify and adjust authorizations if necessary.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution.
Get instant SAP help. Start your 7-day free trial now.
PBAS_SERVICE059
Drag&Drop only possible with suitable person/infotype
What causes this issue? You attempted to move an entry of one person to another person or from one infotype to another using drag and drop. The drag ...
PBAS_SERVICE058
No data available for &1 &2 &3
What causes this issue? No data was stored for the number &V2& in infotype &V3& for the transaction class &V1& (A = employee,...
PBAS_SERVICE061
Successful repair for person number &1
What causes this issue? The system was able to repair the grouped data for personnel number &V1&.System Response As long as the report was n...
PBAS_SERVICE062
&2 is not a permitted value for feature for &1
What causes this issue? The evaluation of feature &1 returns the value &2. However, this value is not a permitted return value for this featu...
Click on this link to search all SAP messages.