How To Fix 5D629 - Personnel area &1/subarea &2 is not liable for contributions

SAP Error Message - Details

• Message type: E = Error

• Message class: 5D - Error Messages for German Infotype Module Pools

• Message number: 629

• Message text: Personnel area &1/subarea &2 is not liable for contributions

What causes this issue?

You entered SI attribute 23 (SI contribution). However, the work center
is not obligated to pay contributions.

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?

Delete SI attribute 23.
<ZH>Procedure up to 2005:
If the work center is supposed to be liable to pay contributions, you
have to enter this work center in view V_T5D1A or V_T5D19, together with
the health insurance fund responsible for the SI contribution and its
contribution percentage rates.</>
<ZH>Procedure from 2006:
If the work center is supposed to be liable for the U1 contribution
(illness), you have to assign the corresponding U1 contribution rate for
payroll periods from 01/2006 in view V_T5D49 of the workplace (personnel
area/subarea or personnel area/subarea/HI fund).</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5D629 - Personnel area &1/subarea &2 is not liable for contributions ?

  The SAP error message 5D629 indicates that the specified personnel area and subarea are not liable for contributions, which typically relates to payroll processing and employee benefits in the SAP Human Capital Management (HCM) module. This error can occur during payroll runs or when processing employee data related to contributions for social security, health insurance, or other benefits.
  Cause:
  
  Configuration Issues: The personnel area and subarea may not be correctly configured in the system to handle contributions. This could be due to missing settings in the payroll schema or the absence of necessary infotypes.
  Employee Master Data: The employee's master data may not be set up correctly, leading to the system not recognizing the personnel area/subarea as liable for contributions.
  Legal Regulations: Changes in legal regulations or company policies may have affected the contribution liability for specific personnel areas or subareas.
  Incorrect Payroll Control Record: The payroll control record may not be set up to allow contributions for the specified personnel area/subarea.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the SAP Customizing Implementation Guide (SPRO) and navigate to the payroll settings for your country.
  Ensure that the personnel area and subarea are configured to be liable for contributions.
  Verify the settings for the relevant wage types and ensure they are correctly assigned to the personnel area/subarea.
  
  
  
  Review Employee Master Data:
  
  Check the employee's master data (infotypes 0001, 0002, 0006, etc.) to ensure that the personnel area and subarea are correctly assigned.
  Make sure that the employee has the necessary infotypes filled out that pertain to contributions.
  
  
  
  Update Payroll Control Record:
  
  Check the payroll control record to ensure that it is set up to process contributions for the relevant personnel area/subarea.
  Make any necessary adjustments to the payroll control record.
  
  
  
  Consult Legal Regulations:
  
  Review any recent changes in legal regulations that may affect contribution liabilities for the specified personnel area/subarea.
  
  
  
  Testing:
  
  After making the necessary changes, run a test payroll to ensure that the error does not occur again.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as PA30 (Maintain HR Master Data), SPRO (Customizing), and PC00_MXX_CALC (Payroll Calculation) to access the relevant settings and data.
  Documentation: Refer to SAP documentation or help files for specific configuration steps related to payroll and contributions for your country.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP HCM expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.