How To Fix HRPAYSE_MTS019 - Record has the same ID, specification number was replaced by PERNR

HRPAYSE_MTS019 - Overview

• Message type: E = Error

• Message class: HRPAYSE_MTS - Monthly tax statement

• Message number: 019

• Message text: Record has the same ID, specification number was replaced by PERNR

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.

HRPAYSE_MTS019 - Details

• The SAP error message HRPAYSE_MTS019 indicates that there is a conflict in the payroll data where a record has the same ID, and the specification number has been replaced by the personnel number (PERNR). This typically occurs in the context of payroll processing, particularly when dealing with infotypes or records that are expected to be unique.
  
  Cause:
  
  Duplicate Records: The error usually arises when there are duplicate entries for a specific ID in the payroll data. This can happen if the same personnel number is being used for multiple records that should be unique.
  Data Migration Issues: If data has been migrated from another system or if there have been manual entries that were not properly validated, it can lead to duplicates.
  
  Configuration Issues: Incorrect configuration in the payroll schema or infotype settings can also lead to this error.
  
  
  Solution:
  
  
  Check for Duplicates: 
  
  Use transaction codes like PA20 or PA30 to check the infotype records for