How To Fix HRPAYDEPF270 - Garnishment principle of origin locked in IT&3 in period &1 with WT &2

HRPAYDEPF270 - Overview

• Message type: E = Error

• Message class: HRPAYDEPF - Error messages for German infotype module pools: garnishment

• Message number: 270

• Message text: Garnishment principle of origin locked in IT&3 in period &1 with WT &2

What causes this issue?

The principle of origin is locked for the in-period &v1&. No shadow
clusters are created for this in-period.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

INCLUDE HRPAYDEPF_REBUILD_OK OBJECT DOKU ID TX

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

HRPAYDEPF270 - Details

• The SAP error message HRPAYDEPF270 indicates that there is a problem related to garnishment processing in the payroll system. Specifically, it refers to a situation where the "garnishment principle of origin" is locked in the relevant infotype (IT) for a specific period and wage type (WT). Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  
  Locked Garnishment Principle: The garnishment principle of origin is locked in Infotype 3 (IT003) for the specified period. This can happen if:
  
  The garnishment has been set up incorrectly.
  There are conflicting entries or changes made to the garnishment data.
  The payroll run has already processed the period, and changes cannot be made.
  
  
  
  Incorrect Configuration: There may be issues with the configuration of the garnishment types or wage types in the system.
  
  
  Data Inconsistency: There could be inconsistencies in the employee's payroll data or infotype records.
  
  
  
  Solution:
  
  
  Check Infotype 003: Review the entries in Infotype 003 (Garnishments) for the employee in