How To Fix PBAS_SERVICE060 - Central person for &1 not found

PBAS_SERVICE060 - Overview

• Message type: E = Error

• Message class: PBAS_SERVICE - HR Master Data: Service Functions

• Message number: 060

• Message text: Central person for &1 not found

What causes this issue?

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.

System Response

The system display an error message.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

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 - Details

• 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