HRPA_ARCH104 - Personnel numbers not processed successfully; restart the delete program

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPA_ARCH -

• Message number: 104

• Message text: Personnel numbers not processed successfully; restart the delete program

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 HRPA_ARCH104 - Personnel numbers not processed successfully; restart the delete program ?

  The SAP error message HRPA_ARCH104 indicates that there was an issue during the deletion of personnel numbers in the archiving process. This error typically occurs when the archiving program encounters problems while trying to delete or archive personnel records, which can be due to various reasons.
  Causes:
  
  Database Locking Issues: The personnel records may be locked by another process, preventing the archiving program from accessing them.
  Data Integrity Issues: There may be inconsistencies or integrity issues in the data that prevent successful deletion.
  Authorization Problems: The user executing the archiving process may not have the necessary authorizations to delete the personnel records.
  Technical Errors: There could be technical issues such as memory problems, timeouts, or other system-related errors during the execution of the archiving program.
  Configuration Issues: Incorrect configuration settings in the archiving object or related settings may lead to this error.
  
  Solutions:
  
  Check for Locks: Use transaction SM12 to check for any locks on the personnel records. If locks are found, you may need to wait for the other processes to complete or resolve the locks.
  Review Logs: Check the application log for more detailed error messages. You can do this using transaction SLG1 and looking for logs related to the archiving process.
  Run in Background: If the process is timing out, consider running the archiving program in the background to allow it more time to complete.
  Check Authorizations: Ensure that the user executing the archiving process has the necessary authorizations to delete personnel records.
  Data Consistency Check: Perform a consistency check on the personnel data to identify and resolve any integrity issues.
  Restart the Program: As suggested by the error message, you can restart the delete program. Make sure to address any underlying issues before doing so.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Archiving Process: Understand the archiving process in SAP HR, including the configuration of archiving objects and the necessary prerequisites for successful execution.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration) for managing archiving processes.
  SAP Documentation: Refer to SAP Help documentation for detailed information on archiving in HR and troubleshooting common issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.