How To Fix HRPADUN_GEN802 - PT: Multiple contracts valid at &2 (last is taken)

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPADUN_GEN - Messages for UN Developement

• Message number: 802

• Message text: PT: Multiple contracts valid at &2 (last is taken)

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 HRPADUN_GEN802 - PT: Multiple contracts valid at &2 (last is taken) ?

  The SAP error message HRPADUN_GEN802 with the description "PT: Multiple contracts valid at &2 (last is taken)" typically occurs in the context of the SAP Human Capital Management (HCM) module, particularly when dealing with personnel time management and payroll processing.
  Cause:
  This error indicates that there are multiple employment contracts (or personnel assignments) for an employee that are valid at the same time for the specified date (represented by &2). The system is designed to handle only one active contract for payroll processing at a given time, and when it finds multiple contracts valid for the same date, it defaults to the last one in the sequence, which may not be the intended contract.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check Employee Contracts:
  
  Go to the employee's master data in the SAP system (Transaction code: PA20 or PA30).
  Review the employee's contracts and check for any overlapping validity periods.
  
  
  
  Adjust Validity Periods:
  
  If you find multiple contracts that overlap, you may need to adjust the validity periods of these contracts. Ensure that only one contract is active for the specific date in question.
  
  
  
  Review Contract Types:
  
  Ensure that the contracts are correctly categorized and that there are no unintended entries. Sometimes, contracts may be created incorrectly or not updated properly.
  
  
  
  Consult with HR:
  
  If you are unsure about which contract should be active, consult with the HR department or the personnel administration team to clarify which contract should be valid for the employee.
  
  
  
  Run Consistency Checks:
  
  Use SAP reports or transaction codes (like RPCLST00) to run consistency checks on the employee's data to identify any discrepancies.
  
  
  
  Update Payroll Control Record:
  
  If necessary, ensure that the payroll control record is set up correctly to reflect the intended contract for payroll processing.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA20 (Display HR Master Data), PA30 (Maintain HR Master Data), and PC00_MXX_CEDT (Payroll processing).
  Documentation: Review SAP documentation or notes related to personnel administration and payroll processing for additional insights.
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to ensure that only one contract is valid for the specified date, thus preventing the error from occurring in the future.