Do you have any question about this error?
Message type: E = Error
Message class: 5H - Garnishment Messages (Austria)
Message number: 172
Message text: Error reading Family/Related Person infotype with key &1 &2
No entry was found for a maintenance creditor of garnishment in
infotype 21 (Family/Related Persons).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Compare the entry for maintenance creditor in infotype 134 (garnishable
amount) with the entry in infotype 21.
Error message extract from SAP system. Copyright SAP SE.
5H172
- Error reading Family/Related Person infotype with key &1 &2 ?The SAP error message 5H172, which states "Error reading Family/Related Person infotype with key &1 &2," typically occurs when there is an issue accessing the Family/Related Person infotype (IT0021) in the SAP system. This infotype is used to store information about an employee's family members or related persons.
Causes:
- Missing Data: The specified key (usually the employee number and the sequence number) does not exist in the database. This could be due to data not being maintained or deleted.
- Authorization Issues: The user may not have the necessary authorizations to access the infotype data.
- Database Issues: There could be a problem with the database, such as corruption or connectivity issues.
- Incorrect Key: The key provided in the error message may be incorrect or formatted improperly.
- Configuration Issues: There may be configuration issues in the system that prevent the infotype from being accessed correctly.
Solutions:
- Check Data Existence: Verify that the data for the specified employee and sequence number exists in the Family/Related Person infotype (IT0021). You can do this by using transaction code PA20 or PA30 to view the infotype records.
- Verify Key: Ensure that the key being used to access the infotype is correct. Check for any typos or formatting issues.
- Authorization Check: Ensure that the user has the necessary authorizations to access the infotype. This can be checked with the help of a security administrator.
- Database Check: If there are indications of database issues, consult with your database administrator to check for any problems or inconsistencies.
- System Logs: Check the system logs (transaction code SLG1) for any additional error messages or information that might provide more context about the issue.
- Consult Documentation: Review SAP notes or documentation related to this error message for any specific patches or updates that may address the issue.
Related Information:
If the issue persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
5H171
Error occurred when reading table &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5H170
170-189 reserved for RPCPFAA0
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5I000
Select an employee
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5I001
&
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.