How To Fix HRPBSDEDNEUG015 - Simultaneous step increase and fictitious transfer on &1

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPBSDEDNEUG - Dienstrechtsneuordnungsgesetz - DneuG

• Message number: 015

• Message text: Simultaneous step increase and fictitious transfer on &1

What causes this issue?

If the next level in the previous basic pay system would have been
reached on the key date of the transfer (July 1, 2009) and an assignment
to the transfer level would have occurred, the subsequent level is
reached on July 1, 2009 at the same time as the transfer to the
subsequent level.
If the next level in the previous basic pay system would have been
reached on the key date of the transfer (July 1, 200) and an assignment
to level 5 in the pay seniority groups A7 to A12 would have occurred,
level 5+ is reached on July 1, 2009 at the same time as the transfer.

How to fix this error?

Check or correct the level or the transfer level in the data record of
the infotype <LS>Basic Pay</> (IT0008) starting from the point in time
of the promotion.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPBSDEDNEUG015 - Simultaneous step increase and fictitious transfer on &1 ?

  The SAP error message HRPBSDEDNEUG015, which states "Simultaneous step increase and fictitious transfer on &1," typically occurs in the context of personnel administration and payroll processing within the SAP Human Capital Management (HCM) module. This error indicates that there is a conflict between a step increase (a salary increase based on the employee's performance or tenure) and a fictitious transfer (a transfer that does not involve a physical move but may affect the employee's pay or position).
  Cause:
  The error is usually caused by the following scenarios:
  
  Simultaneous Actions: The system is trying to process both a step increase and a fictitious transfer for the same employee at the same time, which is not allowed.
  Configuration Issues: There may be configuration settings in the system that do not allow for these two actions to occur simultaneously.
  Data Entry Errors: Incorrect or conflicting data entries in the employee's master data or infotypes can lead to this error.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review the Employee's Data: Check the employee's infotypes (such as infotype 0000 for actions, infotype 0001 for organizational assignment, and infotype 0008 for basic pay) to ensure that there are no conflicting entries for the step increase and fictitious transfer.
  
  
  Separate the Actions: If both a step increase and a fictitious transfer are necessary, consider processing them in separate payroll runs or actions. For example, first process the step increase, and once that is completed, then process the fictitious transfer.
  
  
  Check Configuration Settings: Review the configuration settings in the SAP system related to personnel actions and pay increases. Ensure that the system is set up to handle these actions appropriately without conflicts.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version of SAP you are using.
  
  
  Related Information:
  
  Infotypes: Familiarize yourself with relevant infotypes in SAP HCM, especially those related to employee actions, pay, and organizational assignments.
  SAP Notes: Search for SAP Notes related to HRPBSDEDNEUG015 for any updates or known issues that may provide additional context or solutions.
  Testing: If changes are made to the configuration or data, ensure to test in a development or quality assurance environment before applying changes to the production system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.