Do you have any question about this error?
Message type: E = Error
Message class: HRPA_ARCH -
Message number: 112
Message text: There is still dependent data in infotype 2006
The system checks whether entries for the automatic generation of
absence quotas (infotype <LS>absence quotas</> 2006) exist in
Customizing for <LS>Time Management</> under <LS>Automatic Accrual of
Absence Quotas</>. The rules are defined for each <DS:DE.ABWKO>Absence
Quota Type</>. In this way, the data records of infotype 0004 are also
linked to the data records of infotype 2006.
In the time period selected for data destruction, these types of
dependent data records of the infotype 2006 still exist for infotype
0004.
The data is not destroyed.
Check whether something can be deducted from the existing absence
quotas. Execute archiving object HRTIM_QUOT to destroy data records
belonging to infotype 2006. Then, execute another data destruction run
for HRPA_CHLLN to delete the challenge data.
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 HRPA_ARCH112 indicates that there is dependent data in infotype 2006 (Absences) that prevents the archiving of personnel records. This typically occurs when there are still active or relevant records associated with the personnel number that need to be addressed before archiving can proceed.
Cause:
The error arises because:
- There are still active absence records in infotype 2006 for the employee.
- The system requires that all dependent data related to the personnel record be cleared or archived before the main record can be archived.
- There may be other infotypes that are linked to infotype 2006 that also need to be addressed.
Solution:
To resolve this error, you can follow these steps:
Check Infotype 2006 Records:
- Use transaction code PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data) to check the infotype 2006 records for the employee in question.
- Identify any active absence records that need to be processed.
Process Absence Records:
- If there are active absence records, you may need to either delete them or change their status to inactive, depending on your organization's data retention policies.
- If the absence records are historical and should not be deleted, consider whether they can be archived separately.
Check Related Infotypes:
- Review other related infotypes that may have dependencies on infotype 2006. For example, check infotypes like 2001 (Absences) or 2002 (Leave Entitlements) to ensure there are no active records that could be causing the issue.
Archiving Configuration:
- Ensure that your archiving configuration is set up correctly. This includes checking the archiving object and the selection criteria used for archiving personnel records.
Run Archiving Program:
- After addressing the dependent data, you can run the archiving program again to see if the error persists.
Consult Documentation:
- Refer to SAP documentation or your organization's SAP support team for specific guidelines on handling archiving processes and related infotypes.
Related Information:
By following these steps, you should be able to resolve the HRPA_ARCH112 error and successfully archive the personnel records.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
HRPA_ARCH111 Data is still need for payroll (infotype 0003)
What causes this issue? In the time period selected for data destruction, data ...
HRPA_ARCH110 Configuration from table ADMI_RUN could not be read
Self-Explanatory Message Since SAP believes that this specific error message is ...
HRPA_ARCH113 There is still dependent data in infotype &2
What causes this issue? In the time period selected for data destruction, depen...
HRPA_ARCH114 Criteria for data destruction fulfilled for &1
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.