How To Fix HRPAYDEPF507 - Principle of origin is locked as table DGIT is not filled.

HRPAYDEPF507 - Overview

• Message type: E = Error

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

• Message number: 507

• Message text: Principle of origin is locked as table DGIT is not filled.

What causes this issue?

Table DGIT is not filled in a retroactive accounting period/for-period.

System Response

It is not possible to carry out a payroll run according to the principle
of origin as the state of the retroactive accounting period/for-period
cannot be reached. The inflow principle is used instead.
As of the period to which retroactive accounting is first carried out,
table DGIT is available for this period and all subsequent periods so
that the system does not have to switch to the inflow principle again.

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYDEPF507 - Principle of origin is locked as table DGIT is not filled. ?

  The SAP error message HRPAYDEPF507 indicates that the "Principle of origin is locked as table DGIT is not filled." This error typically occurs in the context of payroll processing in SAP HR (Human Resources) when the system is unable to determine the principle of origin for a specific employee or payroll area due to missing or incomplete data in the DGIT table.
  
  Cause:
  
  Incomplete Configuration: The DGIT table, which is used to store data related to the principle of origin, may not be populated correctly. This can happen if the necessary configuration steps have not been completed.
  Missing Entries: There may be missing entries in the DGIT table for the relevant payroll area or employee group.
  Locked Entries: The principle of origin may be locked due to previous processing or configuration issues, preventing the system from accessing the required data.
  
  
  Solution:
  
  Check DGIT Table: Verify that the DGIT table is populated correctly. You can do this