How To Fix HRPAY99RU_RMS_DB129 - ABAP OS transaction rolled back at &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAY99RU_RMS_DB - RMS DB: Messages for RMS persistence layer

• Message number: 129

• Message text: ABAP OS transaction rolled back at &1 &2

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 HRPAY99RU_RMS_DB129 - ABAP OS transaction rolled back at &1 &2 ?

  The SAP error message HRPAY99RU_RMS_DB129 with the description "ABAP OS transaction rolled back at &1 &2" typically indicates that there was an issue during the execution of a payroll process or a related transaction in the SAP HR module. This error can occur due to various reasons, including database issues, configuration problems, or data inconsistencies.
  Possible Causes:
  
  Database Locking Issues: The transaction may have encountered a lock on the database that prevented it from completing successfully.
  Data Inconsistencies: There may be inconsistencies in the payroll data or master data that are causing the transaction to fail.
  Configuration Errors: Incorrect configuration in the payroll schema or related settings can lead to this error.
  Memory Issues: Insufficient memory or resources on the application server can cause transactions to fail.
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to perform the action.
  
  Solutions:
  
  Check Database Locks: Use transaction SM12 to check for any locks on the database that may be preventing the transaction from completing. If locks are found, they may need to be released.
  Review Payroll Data: Check for any inconsistencies in the payroll data. This can include reviewing employee master data, infotypes, and payroll results.
  Configuration Review: Verify the configuration settings in the payroll schema and ensure that they are set up correctly. This may involve checking the payroll area, wage types, and other related settings.
  Monitor System Resources: Check the system's memory and resource usage. If the system is low on resources, consider increasing the available memory or optimizing the workload.
  Authorization Check: Ensure that the user has the necessary authorizations to execute the payroll transaction. This can be checked in transaction SU53 after the error occurs.
  Review Application Logs: Use transaction SLG1 to check the application logs for any additional error messages or details that can provide more context about the failure.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA03 (Maintain Payroll Area), PC00_MXX_CALC (Payroll Calculation), and PC00_MXX_CEDT (Payroll Results) for further investigation.
  System Logs: Review system logs in transaction SM21 for any related errors or warnings that occurred around the same time as the transaction failure.
  
  If the issue persists after following these steps, it may be necessary to engage SAP support for further assistance.