How To Fix 5Z735 - No pension case found but infotype 0326 (&3) is available. Check case.

5Z735 - Overview

• Message type: E = Error

• Message class: 5Z - IS-HR/PSG Public Sector Payroll - Germany

• Message number: 735

• Message text: No pension case found but infotype 0326 (&3) is available. Check case.

What causes this issue?

INCLUDE PAY_AT_PCALZ_AD OBJECT DOKU ID TX
INCLUDE HRPAYDE_RZB_RUECKMELDUNG_PR OBJECT DOKU ID TX

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?

INCLUDE HRPAYDE_RZB_WHAT_TO_DO_FNG_1 OBJECT DOKU ID TX
Infotype <LS>Imputation to Pension</> (0326) is checked using the
payroll number &V3& that is contained in the confirmation of the pension
service.
INCLUDE HRPAYDE_RZB_WHAT_TO_DO_FNG_2 OBJECT DOKU ID TX

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 5Z735 - No pension case found but infotype 0326 (&3) is available. Check case. ?

  The SAP error message 5Z735, which states "No pension case found but infotype 0326 (&3) is available. Check case," typically occurs in the context of managing employee benefits, specifically related to pension cases in the SAP Human Capital Management (HCM) module. This error indicates that while there is data present in Infotype 0326 (which is used for pension-related information), the system cannot find a corresponding pension case.
  
  Cause:
  
  Missing Pension Case: The primary cause of this error is that there is no pension case created for the employee in the system, even though there is data in Infotype 0326.
  Incorrect Configuration: There may be configuration issues in the system that prevent the pension case from being recognized or created.
  Data Inconsistency: There could be inconsistencies or errors in the data entered in Infotype 0326 or related infotypes.
  Timing Issues: The pension case may not have been created yet due to timing issues in the data