How To Fix HRPAYBR_EFD170 - Payroll wage types &1 for EE &2 not relevant f/previous paym.info.record

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYBR_EFD - Message class EFD-Social

• Message number: 170

• Message text: Payroll wage types &1 for EE &2 not relevant f/previous paym.info.record

What causes this issue?

To inform the payments previous to the start of the eSocial compulsory
periodic events, the payrolls relevant for the event are the ones
retrocalculated and run after the eSocial start date for the periodic
events. However, the differences of previous generated payrolls are not
relevant for the record <ZK>prevPaymInfo</>.

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 NA_SYSADMIN1 OBJECT DOKU ID TX LANGUAGE EN

Procedure for System Administrators

If you want, review your customizations of wage types relevant for the
event in the customizing activity <DS:SIMG.PAY_BR_EFD08>Check wage type
table entries</>, activity <LS>Customize wage type nature</>. This
activity refers to the <LS>Wage type assignment to cumulation wage types
(customer table)</> (V_T596J) view, subapplication
<DS:HRDS.DSYSLO_ECDAPPL_SOCNAAAAAAAAAAAAAAAA37_1VVV>SOCN</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYBR_EFD170 - Payroll wage types &1 for EE &2 not relevant f/previous paym.info.record ?

  The SAP error message HRPAYBR_EFD170 typically occurs in the context of Brazilian payroll processing. This error indicates that certain payroll wage types for an employee (EE) are not relevant for a previous payment information record. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Wage Type Configuration: The wage types in question may not be configured correctly in the system. They might not be set up to be relevant for the specific payroll period or payment information record.
  Payroll Period Issues: The error can occur if there are discrepancies in the payroll periods being processed. For example, if the wage types were not applicable in the previous payroll period but are being referenced.
  Employee Master Data: There may be issues with the employee's master data, such as missing or incorrect information that affects the payroll processing.
  Data Consistency: There might be inconsistencies in the payroll data, such as missing entries or incorrect wage type assignments.
  
  Solution:
  
  Check Wage Type Configuration: Review the configuration of the wage types in the SAP system. Ensure that they are set up correctly for the relevant payroll periods and that they are marked as relevant for the employee's payment information.
  Review Payroll Periods: Verify the payroll periods for the employee and ensure that the wage types are applicable for the periods being processed. If necessary, adjust the payroll periods or the wage type settings.
  Validate Employee Master Data: Check the employee's master data for any inconsistencies or missing information. Ensure that all relevant fields are filled out correctly.
  Run Payroll Simulation: Perform a payroll simulation to identify any other potential issues that may not be immediately apparent. This can help in diagnosing the root cause of the error.
  Consult Documentation: Refer to SAP documentation or notes related to Brazilian payroll processing for any specific guidelines or updates that may address this issue.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or fixes related to this error message.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA30 (Maintain HR Master Data), PC00_M01_CEDT (Payroll for Brazil), and others that may help in troubleshooting.
  Support Forums: Consider reaching out to SAP support or community forums for additional assistance, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.