How To Fix HRPADIT_DECLARATION152 - No suspended SP values for arrears' generation

HRPADIT_DECLARATION152 - Overview

• Message type: E = Error

• Message class: HRPADIT_DECLARATION - Messages for statements (CUD, 770, DM10...)

• Message number: 152

• Message text: No suspended SP values for arrears' generation

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 HRPADIT_DECLARATION152 - No suspended SP values for arrears' generation ?

  The SAP error message HRPADIT_DECLARATION152 indicates that there are no suspended social security (SP) values available for the generation of arrears in the payroll process. This error typically arises in the context of payroll processing in the SAP HR module, particularly in Italy, where specific regulations and calculations for social security contributions are applied.
  
  Cause:
  
  
  Missing Data: The error often occurs when there are no records of suspended social security values for the employee in question. This could be due to:
  
  The employee not having any previous payroll runs that would have generated such values.
  Incorrect or incomplete data in the employee's master data or payroll results.
  The employee not being eligible for certain social security contributions.
  
  
  
  
  Configuration Issues: There may be issues with the configuration of the payroll schema or the specific rules governing the calculation of social security contributions.
  
  
  Timing of Payroll Runs: If the payroll run is being executed at a time when there