Do you have any question about this error?
Message type: E = Error
Message class: FG - Program Error Messages
Message number: 650
Message text: Start of document archiving (computer: &)
The document archiving was started.
Information
The document archiving was started by user &v2& on machine &v1&.
The following program control was selected ('X' = on, ' ' off):
Detail log: &v3&
Test run : &v4&
Error message extract from SAP system. Copyright SAP SE.
FG650
- Start of document archiving (computer: &) ?The SAP error message FG650 typically indicates an issue related to the document archiving process in SAP. This error can occur for various reasons, and understanding the cause and potential solutions is essential for resolving it.
Cause:
- Configuration Issues: The archiving object may not be properly configured in the system.
- Authorization Problems: The user may not have the necessary authorizations to start the archiving process.
- System Settings: There may be issues with the settings on the application server or database that prevent archiving from starting.
- Document Status: The documents intended for archiving may not be in a status that allows them to be archived.
- Archiving Process Not Started: The archiving process may not have been initiated correctly or may have been interrupted.
Solution:
- Check Configuration: Ensure that the archiving object is correctly configured in the SAP system. This includes checking the settings in transaction code SARA (Archive Administration).
- Review Authorizations: Verify that the user attempting to start the archiving process has the necessary authorizations. This can be checked in transaction SU53 or by consulting with your security team.
- System Logs: Check the system logs (transaction SM21) for any related error messages that could provide more context on why the archiving process failed.
- Document Status: Ensure that the documents you are trying to archive are in the correct status. You may need to change the status of the documents or check if they are locked.
- Restart the Process: If the archiving process was interrupted, try restarting it. You can do this in transaction SARA by selecting the appropriate archiving object and starting the process again.
- Check Background Jobs: If the archiving process is supposed to run as a background job, check the job status in transaction SM37 to see if it has failed or is still running.
- Consult Documentation: Refer to SAP Notes or the official SAP documentation for any specific guidance related to the archiving object you are working with.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FG621
Simultaneous retrieval not yet implemented
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FG620
Writing the index not possible
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FG651
Number of document headers read/archived: &/&
What causes this issue? &v1& document headers were read during the current program run for archiving documents, of which &v2& meet al...
FG652
SAP archive &: No.of documents read/archived previously: &/&
What causes this issue? &v2& documents were read on the data base during the archiving run, of which &v3& fulfil all the criteria for...
Click on this link to search all SAP messages.