Message type: E = Error
Message class:  HRPAYDEPF - Error messages for German infotype module pools: garnishment 
Message number: 311
Message text: In case of cleanup, PFEP must not be locked in the period
In the current in-period of the payroll, the garnishment results for the
personnel number should be cleaned up. In this case, the principle of
origin cannot be locked for this period.
If the system determines the error via the program used to clean up the
garnishment results (<LS>Garnishment Principle of Origin - Check and
Cleanup of Shadow Cluster</> (<LS>RPCPCAD0_EP_CHECK_UPDATE</>)), it does
not save the cleanup results. If cleanup results already exist and
locking of the principle of origin only takes place afterwards, the
procedure within payroll is terminated.
Delete the wage type for the specification of the lock of the principle
of origin for the current in-period in the master data of the personnel
number and save the cleanup results or start the payoll again.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message HRPAYDEPF311 typically occurs in the context of payroll processing, particularly when dealing with the Personnel File (PFEP) in the Human Resources module. This error indicates that there is an issue with the locking of the Personnel File for a specific period during a cleanup operation.
Cause: The error message HRPAYDEPF311 is triggered when the system attempts to perform a cleanup operation on the Personnel File (PFEP) while the file is locked for the specified period. This can happen due to several reasons: Ongoing Payroll Processing: The PFEP might be locked because payroll processing is currently active for that period. Previous Locking: There may be a previous operation that has locked the PFEP, preventing any cleanup actions.
Configuration Issues: Incorrect configuration settings in the payroll or personnel administration module may lead to locking issues.
Solution: To resolve the HRPAYDEPF311 error, you can take the following steps: Check Lock Status: Verify if the PFEP is indeed
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
HRPAYDEPF310 Error category &1 not relevant for cleaning up the cluster
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDEPF309 Garnishment &1/&2: Difference seizable amt &3 > amount limit in period &4
What causes this issue?  The repaid amount of the garnishment (&v1&/&v2&) changes in the period &v4& during the cleanup. At th...
HRPAYDEPF312 Garnishment &1/&2: Neg. amt for repayt or rem. debt in period &3 (DP)
What causes this issue?  A negative amount in field <LS>GTBTR </>(Repaid amount for current period) or <LS>GTALT </>(Garnishme...
HRPAYDEPF313 Additional options cannot be used without debugger authorization
What causes this issue?  You have attempted to use additional parameters of the report using the function code <LS>SAP</> or using the mai...
Click on this link to search all SAP messages.