How To Fix HRPAYRU_SZVR_DAQ006 - Infotype 2002 or 2003 on date &1 contains unexpected object type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYRU_SZVR_DAQ - Data acquisition messages for PF report SZVR

• Message number: 006

• Message text: Infotype 2002 or 2003 on date &1 contains unexpected object type &2

What causes this issue?

During processing of seniority results, the system detected that a
record of infotype <LS>Attendances</> (2002) or infotype <LS>
Substitutions</> (2003) specifies an unexpected Organization Management
object type on the specified date.
The only allowed object types are:
S - Position
A - Work center

System Response

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

How to fix this error?

Correct infotype entries on the specified date and use only the allowed
object types.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYRU_SZVR_DAQ006 - Infotype 2002 or 2003 on date &1 contains unexpected object type &2 ?

  The SAP error message HRPAYRU_SZVR_DAQ006 typically occurs in the context of the Russian payroll module when there is an issue with the infotypes 2002 (Employment Information) or 2003 (Additional Payments). The error indicates that there is an unexpected object type associated with the specified date.
  
  Cause:
  
  Incorrect Object Type: The error suggests that the system encountered an object type that it did not expect for the specified date. This could be due to incorrect configuration or data entry in the infotype records.
  Data Inconsistency: There may be inconsistencies in the data related to the employee's infotypes, such as overlapping records or incorrect validity periods.
  Custom Development: If there are custom enhancements or modifications in the payroll process, they might be causing the system to misinterpret the data.
  
  
  Solution:
  
  Check Infotype Records: Review the infotype records (2002 and 2003) for the employee in question. Ensure that the object types are correctly defined and that there are no