How To Fix HRPAYBR94054 - Third-party aliquot missing for company &1 and branch &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYBR94 - Reports log

• Message number: 054

• Message text: Third-party aliquot missing for company &1 and branch &2

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 HRPAYBR94054 - Third-party aliquot missing for company &1 and branch &2 ?

  The SAP error message HRPAYBR94054 indicates that there is a missing third-party aliquot for a specific company and branch in the Brazilian payroll system. This error typically arises in the context of payroll processing when the system is unable to find the necessary data related to third-party payments, which are often required for social security, health insurance, or other deductions.
  Cause:
  
  Missing Configuration: The third-party aliquot may not be configured correctly in the system for the specified company and branch.
  Data Entry Errors: There may be errors in the master data or payroll data entries that prevent the system from locating the required aliquot.
  Inconsistent Data: The data in the payroll infotypes may not be consistent with the expected values for the third-party aliquot.
  Updates or Changes: Recent changes in legislation or updates to the payroll system may have affected the configuration or data.
  
  Solution:
  
  
  Check Configuration: 
  
  Verify the configuration of third-party aliquots in the SAP system. Ensure that the necessary settings for the company and branch are correctly defined in the relevant infotypes (e.g., infotype 0014 for recurring payments and deductions).
  Use transaction codes like SPRO to access the configuration settings and check the payroll settings for Brazil.
  
  
  
  Review Master Data:
  
  Check the employee master data for the affected employees to ensure that all necessary information is correctly entered.
  Look for any missing or incorrect entries in infotypes related to payroll deductions.
  
  
  
  Validate Payroll Data:
  
  Run a payroll simulation for the affected employees to identify any discrepancies or missing data that could lead to this error.
  Use transaction code PC00_M01_CEDT to simulate payroll and check for errors.
  
  
  
  Consult Documentation:
  
  Review SAP notes and documentation related to Brazilian payroll to ensure compliance with current regulations and to find any specific notes addressing this error.
  
  
  
  Contact Support:
  
  If the issue persists after checking the configuration and data, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  
  Related Information:
  
  SAP Notes: Look for specific SAP notes related to HRPAYBR94054 for any patches or updates that may address this issue.
  Documentation: Refer to the SAP Help Portal for detailed documentation on Brazilian payroll processing and third-party payments.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.