How To Fix HRPSGB_ME062 - Employee has an SSP/SMP absence, but has NO Primary contract for &1

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPSGB_ME - Multiple Employment Errors & Warnings

• Message number: 062

• Message text: Employee has an SSP/SMP absence, but has NO Primary contract for &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPSGB_ME062 - Employee has an SSP/SMP absence, but has NO Primary contract for &1 ?

  The SAP error message HRPSGB_ME062 indicates that an employee has a Statutory Sick Pay (SSP) or Statutory Maternity Pay (SMP) absence, but there is no primary contract associated with that employee for the specified date. This can occur in the context of payroll processing or absence management in the SAP Human Capital Management (HCM) module.
  Cause:
  
  Missing Primary Contract: The employee does not have a primary employment contract defined in the system. This is essential for processing SSP/SMP as the system needs to know which contract to reference for payment calculations.
  Incorrect Contract Configuration: The employee may have multiple contracts, but none are marked as primary, or the primary contract may not be active during the period of the absence.
  Data Entry Errors: There may be errors in the employee's master data, such as incorrect dates or missing information that prevents the system from recognizing the primary contract.
  
  Solution:
  
  
  Check Employee Master Data:
  
  Navigate to the employee's master data in the SAP system (Transaction PA30).
  Verify that there is a primary contract assigned to the employee. If not, you may need to create or update the contract.
  
  
  
  Assign a Primary Contract:
  
  If the employee has multiple contracts, ensure that one is designated as the primary contract. This can typically be done in the contract details section of the employee's master data.
  
  
  
  Review Absence Records:
  
  Check the absence records for the employee to ensure they are correctly entered and that the absence type is appropriate for SSP/SMP.
  
  
  
  Consult with HR/Payroll Team:
  
  If you are unsure about how to make these changes or if the issue persists, consult with your HR or payroll team for assistance. They may have additional insights or access to tools that can help resolve the issue.
  
  
  
  Testing:
  
  After making the necessary changes, run a test payroll or absence calculation to ensure that the error no longer appears and that the employee's SSP/SMP is processed correctly.
  
  
  
  Related Information:
  
  SSP/SMP Regulations: Familiarize yourself with the regulations surrounding SSP and SMP in your region, as these can affect how the system processes absences.
  SAP Notes: Check for any relevant SAP Notes or documentation that may provide additional guidance or updates related to this error message.
  Training: Ensure that HR personnel are trained on how to manage employee contracts and absences in SAP to prevent similar issues in the future.
  
  By addressing the underlying cause of the error and ensuring that the employee's master data is correctly configured, you should be able to resolve the HRPSGB_ME062 error effectively.