How To Fix 5Z536 - New record of infotype 0008 ends on &1. Check future records

SAP Error Message - Details

• Message type: E = Error

• Message class: 5Z - IS-HR/PSG Public Sector Payroll - Germany

• Message number: 536

• Message text: New record of infotype 0008 ends on &1. Check future records

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5Z536 - New record of infotype 0008 ends on &1. Check future records ?

  The SAP error message 5Z536, which states "New record of infotype 0008 ends on &1. Check future records," typically occurs in the context of personnel administration when there is an issue with the validity dates of infotype records, specifically infotype 0008 (Basic Pay).
  Cause:
  This error usually arises due to one of the following reasons:
  
  
  Overlapping Validity Periods: There may be existing records in infotype 0008 that have overlapping validity periods with the new record you are trying to create or modify. SAP requires that there be no overlaps in the validity periods of infotype records.
  
  
  Future Records: The error message suggests that there may be future records that are affecting the validity of the new record. If there are records with a start date that overlaps with the end date of the new record, it will trigger this error.
  
  
  Incorrect End Date: The end date of the new record may be set incorrectly, either being too far in the future or conflicting with existing records.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Records: Use transaction code PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data) to review the existing records for infotype 0008 for the employee in question. Look for any records that have overlapping validity periods.
  
  
  Adjust Validity Dates: If you find overlapping records, you may need to adjust the validity dates of the existing records or the new record you are trying to create. Ensure that the new record's end date does not conflict with any existing records.
  
  
  Delete or Change Future Records: If there are future records that are causing the conflict, you may need to delete or change those records to allow for the new record to be created successfully.
  
  
  Consult with HR or SAP Support: If you are unsure about making changes to the records, it may be best to consult with your HR department or SAP support team to ensure that the changes comply with your organization's policies and procedures.
  
  
  Related Information:
  
  Infotype 0008: This infotype is used to maintain basic pay information for employees, including salary, wage type, and other compensation-related data.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA20, PA30, and PA40 (for personnel actions) to manage HR data effectively.
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error message, as there may be known issues or fixes provided by SAP.
  
  By following these steps, you should be able to resolve the error and successfully manage the infotype records in SAP.