How To Fix 5M369 - Person rejected: only one accumulator & per export run!

SAP Error Message - Details

• Message type: E = Error

• Message class: 5M - Error Messages for Denmark

• Message number: 369

• Message text: Person rejected: only one accumulator & per export run!

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 5M369 - Person rejected: only one accumulator & per export run! ?

  The SAP error message 5M369 ("Person rejected: only one accumulator & per export run") typically occurs in the context of payroll processing or data export in SAP HR (Human Resources) modules. This error indicates that there is an issue with the configuration of the payroll export process, specifically related to the use of accumulators.
  Cause:
  The error arises when the system detects that there is an attempt to process more than one accumulator for a person during a single export run. Accumulators in SAP HR are used to store cumulative values (like hours worked, wages, etc.) for employees, and the system is designed to allow only one accumulator per person for each export run to avoid data inconsistencies.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Accumulator Configuration: Review the configuration of the accumulators in your payroll schema. Ensure that the accumulators are set up correctly and that there are no conflicting settings that would allow multiple accumulators for the same person in a single run.
  
  
  Review Payroll Results: Check the payroll results for the employee in question. Look for any anomalies or duplicate entries that might be causing the system to attempt to process multiple accumulators.
  
  
  Adjust Export Parameters: If you are using a custom export program or report, ensure that it is designed to handle only one accumulator per person. You may need to modify the logic to filter or aggregate the data correctly.
  
  
  Run Payroll in Batches: If you are processing a large number of employees, consider running the payroll in smaller batches to avoid hitting the limit of accumulators.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to payroll processing and accumulators for any specific guidelines or updates that may apply to your version of SAP.
  
  
  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 specific to your system configuration or version.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to payroll processing (e.g., PC00_MXX_CALC, PC00_MXX_CEDT) to help you navigate the payroll module effectively.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.