How To Fix HRPBSDERECL027 - Absence category &1 follows directly on &2 from absence category &3

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPBSDERECL - Messages for Pay Scale Level Increase

• Message number: 027

• Message text: Absence category &1 follows directly on &2 from absence category &3

What causes this issue?

If two different absences are directly adjacent to each other, then the
two periods are to be considered together with regard to the rounding
down to full months. This is the case here.
However, since non-adjacent periods with the same absence category are
also considered together, this can result in combinations that cannot be
determined automatically. Therefore a manual check of the constellation
is required.

System Response

No automatic reclassification occurs.

How to fix this error?

Check the reclassification time and enter the desired reclassification
date in the <LS>"Next Increase"</> field (Next Incr.) of the <LS>Basic
Pay</> infotype (0008). Note that as the automatic determination of the
reclassification date for the period is then deactivated by the manual
override, you must recheck and correct the date again if necessary in
the case of a later addition (or discontinuation) of relevant absences
during the pay scale runtime.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPBSDERECL027 - Absence category &1 follows directly on &2 from absence category &3 ?

  The SAP error message HRPBSDERECL027 typically occurs in the context of absence management within the SAP Human Capital Management (HCM) module. This error indicates that there is a violation of the absence management rules regarding the sequence of absence categories. Specifically, it means that an absence of a certain category (represented by &1) cannot directly follow another absence category (represented by &2) that is preceded by a third absence category (represented by &3).
  Cause:
  The error is caused by the configuration of absence types and their relationships in the system. In many organizations, certain absence types are defined to have specific rules about how they can be used in relation to one another. For example, an employee may not be allowed to take a sick leave immediately after a vacation leave without a certain period in between.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review Absence Configuration: Check the configuration of the absence types in the SAP system. This can be done in the following way:
  
  Go to the transaction code SPRO.
  Navigate to Personnel Management > Time Management > Absences > Define Absence Types.
  Review the settings for the absence categories involved in the error message.
  
  
  
  Check Absence Quotas: Ensure that the employee has the necessary quotas for the absence types being used. If an absence type is not allowed to follow another, it may be due to quota restrictions.
  
  
  Adjust Absence Entries: If the absence entries are incorrect, you may need to adjust them. This could involve changing the order of the absence entries or adding a different absence type in between.
  
  
  Consult with HR or Payroll: If you are unsure about the rules governing absence types, consult with your HR or payroll department. They may have specific policies that dictate how absences should be recorded.
  
  
  Testing: After making any changes, test the absence entry again to ensure that the error no longer occurs.
  
  
  Related Information:
  
  Documentation: Refer to SAP documentation or help files for more detailed information on absence management and configuration.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  User Forums: Consider visiting SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.