How To Fix HRPAYRU_LNOC004 - Infotype 3273 does not exist for personnel assignment &1

HRPAYRU_LNOC004 - Overview

• Message type: E = Error

• Message class: HRPAYRU_LNOC - Messages for FSSCS and LN in Off-cycle

• Message number: 004

• Message text: Infotype 3273 does not exist for personnel assignment &1

What causes this issue?

Switch AP4LN was activated. According to the description for Customizing
activity
<DS:SIMG.OHARUBP_SC_MGT_007>Generate Applications for Sickness
Compensation</>, the process for sickness compensation payment requires
a corresponding FSS application record in infotype 3273 for personnel
assignment &V1&.

System Response

The payroll calculation stops.

How to fix this error?

Create an FSS application (records in infotype 3273) with the
appropriate subtype for personnel assignment &V1&. Use Customizing
activity
<DS:SIMG.OHARUBP_FSSIT3273_01>Assign Application Types to IT3273
Subtypes</> to select the appropriate subtype.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

HRPAYRU_LNOC004 - Details

• The SAP error message HRPAYRU_LNOC004 indicates that the system is unable to find the specified infotype (in this case, Infotype 3273) for the given personnel assignment. This error typically occurs in the context of HR (Human Resources) and payroll processing, particularly in the Russian payroll module.
  
  Cause:
  
  Infotype Not Created: The infotype 3273 may not have been created for the personnel assignment in question. This could happen if the employee has not been assigned the necessary data or if the infotype was never maintained.
  Incorrect Personnel Number: The personnel number provided may be incorrect or does not exist in the system.
  Data Deletion: The infotype might have been deleted or not yet populated for the specific employee.
  
  Configuration Issues: There may be configuration issues in the system that prevent the infotype from being recognized or accessed.
  
  
  Solution:
  
  Check Infotype Existence: Verify if Infotype 3273 exists for the personnel number in question. You can do this by using