How To Fix HRPAYDEKUG402 - Sick before RHC is only possible if the illness started in the prev. mth.


SAP Error Message - Details

  • Message type: E = Error

  • Message class: HRPAYDEKUG - Notification class for reduced hours compensation

  • Message number: 402

  • Message text: Sick before RHC is only possible if the illness started in the prev. mth.

  • Show details Hide details
  • What causes this issue?

    The allowance period for reduced hours compensation generally begins on
    the first day of a month even if the non-productive time is not until
    later in the month.
    The reduced hours compensation sick pay to be reimbursed by the health
    insurance fund may only be granted if the illness starts in the previous
    month.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?

    Change the start date of the allowance period in Customizing under
    <DS:SIMG.OHADKU210>Reduced Hours Compensation/Seasonal RHC: Approval
    Periods (T5D3E)</>.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message HRPAYDEKUG402 - Sick before RHC is only possible if the illness started in the prev. mth. ?

    The SAP error message HRPAYDEKUG402 indicates that there is an issue with processing a sick leave (illness) record in the payroll system. Specifically, it states that a sick leave record cannot be created if the illness started in the previous month unless certain conditions are met.

    Cause:

    This error typically arises in the context of payroll processing when:

    1. An employee is trying to report sick leave that began in the previous month, but the payroll period for that month has already been closed.
    2. The system is configured to only allow sick leave entries for the current month or for specific conditions that are not met in this case.

    Solution:

    To resolve this error, consider the following steps:

    1. Check the Dates: Verify the start date of the illness. If it indeed started in the previous month, ensure that the payroll period for that month is still open for adjustments.

    2. Adjust Payroll Period: If the payroll period for the previous month is closed, you may need to reopen it (if your organization's policy allows) to enter the sick leave record.

    3. Use Correct Infotype: Ensure that you are using the correct infotype (e.g., Infotype 2001 for Absences) to record the sick leave.

    4. Consult with HR/Payroll Team: If you are unsure about the policies regarding sick leave and payroll processing, consult with your HR or payroll department for guidance on how to proceed.

    5. System Configuration: If this is a recurring issue, it may be worth reviewing the configuration settings in SAP related to sick leave processing to ensure they align with your organization's policies.

    Related Information:

    • Infotypes: Familiarize yourself with relevant infotypes in SAP HR, particularly Infotype 2001 (Absences) and Infotype 2002 (Attendance).
    • Payroll Processing: Understand the payroll processing cycle in your organization, including how and when sick leave is recorded and processed.
    • SAP Notes: Check for any SAP Notes or documentation that may provide additional insights or updates related to this error message.

    If the issue persists after following these steps, it may be necessary to involve your SAP support team or a consultant who specializes in SAP HR to further investigate the problem.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant