How To Fix HRPSGB_LG017 - Record Not Found In Infotype &1 Between Dates &2 - &3

HRPSGB_LG017 - Overview

• Message type: E = Error

• Message class: HRPSGB_LG - HR GB PS Messages for Local Government

• Message number: 017

• Message text: Record Not Found In Infotype &1 Between Dates &2 - &3

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

HRPSGB_LG017 - Details

• The SAP error message HRPSGB_LG017 indicates that a record was not found in a specific infotype for the given date range. This error typically occurs in the Human Resources (HR) module when trying to access or process employee data that is expected to be present in a specific infotype but is missing for the specified dates.
  
  Cause:
  
  Missing Data: The most common cause is that there is no record in the specified infotype for the employee within the date range provided.
  Incorrect Date Range: The date range specified may not align with the actual records in the infotype.
  Infotype Not Maintained: The infotype may not have been maintained for the employee, either due to oversight or because the infotype is not applicable to that employee.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the records, leading to the perception that they do not exist.
  
  
  Solution:
  
  Check Infotype Records: Use transaction code PA20