How To Fix HRGB_LGPS005 - LGPS: Dates BADI has forced no re-assessment

SAP Error Message - Details

• Message type: E = Error

• Message class: HRGB_LGPS - HR: Messages for LGPS

• Message number: 005

• Message text: LGPS: Dates BADI has forced no re-assessment

What causes this issue?

The LGPS Dates BADI has been implemented and it has forced that this
employee will not be re-assessed during this payroll period, even though
the SAP standard solution would re-assess the employee in this payroll
period.

System Response

This is not an error.

How to fix this error?

Though this is not an error, you should perhaps consider whether this is
actually sensible.
Your implementation of the LGPS Dates BADI is contradicting the LGPS
Scheme Rules, so firstly this has to be a <ZH>very</> exceptional case
and secondly this should really be controlled in a more transparent
manner by entering the "Employee Specific Record Indicator", "EEs" and
"ERs" percentage rates on the employee's Pension Details infotype
(0071).

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRGB_LGPS005 - LGPS: Dates BADI has forced no re-assessment ?

  The SAP error message HRGB_LGPS005 with the description "LGPS: Dates BADI has forced no re-assessment" typically occurs in the context of the Local Government Pension Scheme (LGPS) in the UK. This error is related to the processing of pension data, particularly when the system is trying to re-assess pension contributions or benefits based on certain date criteria.
  Cause:
  The error is triggered when a Business Add-In (BADI) related to the LGPS has been implemented in such a way that it prevents the system from re-assessing pension data for specific dates. This could be due to:
  
  BADI Implementation: The BADI implementation may have logic that explicitly prevents re-assessment for certain conditions or dates.
  Configuration Issues: There may be configuration settings in the pension module that are not aligned with the expected behavior of the BADI.
  Data Issues: There could be issues with the underlying data that the BADI is processing, such as missing or incorrect date entries.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review BADI Implementation: Check the implementation of the BADI related to LGPS. Look for any conditions that might be causing the re-assessment to be skipped. You may need to modify the logic if it is too restrictive.
  
  
  Check Configuration: Ensure that the configuration settings for the LGPS module are correct. This includes checking the settings for pension schemes, contribution rates, and any other relevant parameters.
  
  
  Data Validation: Validate the data being processed. Ensure that all necessary dates and other relevant information are correctly entered in the system. Look for any anomalies or missing data that could be causing the issue.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the LGPS and the specific BADI in question. There may be known issues or additional guidance available.
  
  
  Testing: After making any changes, conduct thorough testing to ensure that the re-assessment process works as expected without triggering the error.
  
  
  Seek Support: If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who specializes in HR and pension modules.
  
  
  Related Information:
  
  BADI (Business Add-In): A BADI is a type of enhancement in SAP that allows developers to add custom functionality to standard SAP applications without modifying the original code.
  LGPS (Local Government Pension Scheme): This is a pension scheme for employees of local authorities in the UK, and it has specific rules and regulations that must be adhered to.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.