How To Fix HRPBSDERECL036 - It was not possible to determine the date of pay scale level start.


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 036

  • Message text: It was not possible to determine the date of pay scale level start.

  • Show details Hide details
  • What causes this issue?

    When destroying an absence, it is necessary to first of all check if
    this absence is still required for the automatic pay level increase. It
    is required if it does not lie completely before the last level start.
    During the check, it was not possible to determine the start of the
    current level.

    System Response

    As it is not possible to check if the data will still be required, it is
    not destroyed.

    How to fix this error?

    Please analyze the cause of the problem in the HR master data and store
    it.

    Procedure for System Administrators

    The level start is determined in method EXT_GET_STBEGL of class
    CL_HRPBSDE_RECLASS. This routine does not run error-free until the end,
    which means that a further analysis should be made here if the error in
    the HR master data cannot be found.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message HRPBSDERECL036 - It was not possible to determine the date of pay scale level start. ?

    The SAP error message HRPBSDERECL036, which states "It was not possible to determine the date of pay scale level start," typically occurs in the context of payroll processing or when trying to determine the pay scale level for an employee. This error can arise due to several reasons related to the configuration of pay scale data or employee master data.

    Causes:

    1. Missing Pay Scale Data: The pay scale data for the employee may not be maintained correctly in the system. This includes missing entries for the employee's pay scale group or level.

    2. Incorrect Validity Dates: The validity dates for the pay scale level may not be set correctly. If the date range for the pay scale level does not cover the date being processed, the system will not be able to determine the start date.

    3. Employee Master Data Issues: The employee's master data may not be complete or may have inconsistencies, such as missing infotypes related to pay scale or organizational assignment.

    4. Configuration Issues: There may be issues in the configuration of the pay scale structure in the system, such as missing or incorrect entries in the relevant tables.

    5. Collective Agreement Changes: If there have been recent changes to collective agreements or pay scale structures, the system may not have been updated accordingly.

    Solutions:

    1. Check Pay Scale Data: Verify that the pay scale data for the employee is correctly maintained. This includes checking the employee's pay scale group and level in the infotype 0008 (Basic Pay).

    2. Review Validity Dates: Ensure that the validity dates for the pay scale level are correctly set and that they encompass the date for which the payroll is being processed.

    3. Update Employee Master Data: Check the employee's master data for completeness. Ensure that all relevant infotypes (such as 0001, 0008, etc.) are filled out correctly.

    4. Configuration Review: Review the configuration of the pay scale structure in the system. Ensure that all necessary entries are present and correct in the relevant tables (e.g., T510, T511).

    5. Consult Documentation: If there have been recent changes to collective agreements or pay scales, consult the relevant documentation to ensure that the system reflects these changes.

    6. Testing: After making any changes, perform a test run of the payroll to see if the error persists.

    Related Information:

    • Infotypes: Familiarize yourself with the relevant infotypes, especially 0008 (Basic Pay) and 0001 (Organizational Assignment), as they are crucial for determining pay scale levels.
    • Transaction Codes: Use transaction codes like PA30 (Maintain HR Master Data) to check and update employee records, and PE03 (Maintain Payroll Schema) to review payroll configurations.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.

    If the issue persists after following these steps, it may be beneficial to consult with your SAP HR module support team or reach out to SAP support for further assistance.

    • 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