How To Fix HRPA_ARCH035 - Data object has been written to the archive file successfully

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPA_ARCH -

• Message number: 035

• Message text: Data object has been written to the archive file successfully

What causes this issue?

The system performed the write run for the archiving object and
generated the data objects.

System Response

The system writes each data record to be destroyed to a
<DS:GLOS.F2484B01DD71D411A4950060B03C3B0E>data object</>. The data
objects for an archiving object are written to an archive file
sequentially. All data objects in the archive file are structured in the
same way, meaning as described in the archiving object.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPA_ARCH035 - Data object has been written to the archive file successfully ?

  The SAP error message HRPA_ARCH035 indicates that a data object has been successfully written to the archive file. This message is not actually an error but rather an informational message that confirms the successful archiving of data. 
  
  Cause:
  
  The message is triggered during the archiving process when the system successfully writes a specified data object (such as employee records, payroll data, etc.) to an archive file. This is part of the data management process in SAP, particularly in the Human Resources (HR) module.
  
  
  Solution:
  Since this message is informational and not an error, no specific action is required to resolve it. However, if you are looking to ensure that the archiving process is functioning correctly, you can take the following steps:
  
  
  Verify Archive Files: Check the archive files to ensure that the data has been written correctly. You can use transaction codes like SARA (Archive Administration) to manage and review archived data.
  
  
  Check Archive Logs: