Message type: E = Error
Message class: /BOFU/ARCH -
Message number: 101
Message text: Cannot be archived; '&1'-status is '&2'
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.
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.
The SAP error message
/BOFU/ARCH101 Cannot be archived; '&1'-status is '&2'
typically occurs when you are trying to archive a document or data object in SAP, but the object is in a status that does not allow it to be archived. The placeholders&1
and&2
in the message represent the specific object type and its current status, respectively.Cause:
The error is caused by the fact that the object you are trying to archive is not in a suitable state for archiving. Common reasons include:
To resolve this error, you can take the following steps:
Check the Status: Identify the object type and its current status using the information provided in the error message. You can do this by navigating to the relevant transaction or using the appropriate report.
Change the Status: If the object is in a status that prevents archiving, you may need to change its status to one that allows archiving. This could involve:
Consult Documentation: Refer to the SAP documentation or help files for the specific object type to understand the valid statuses for archiving.
Use Transaction Codes: Depending on the object type, you may need to use specific transaction codes to change the status or to check the details of the document. For example, if it’s a financial document, you might use transaction codes like FB03 (Display Document) or FB02 (Change Document).
Check Custom Logic: If there are custom developments or enhancements in your SAP system, ensure that they are not interfering with the archiving process.
Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP Notes for any known issues related to this error.
By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.
/BOFU/ARCH100 *** 101 - 150 messages which can be used in BO specific implementations *
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOFU/ARCH070 The archived data has been deleted from the database
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOFU/ARCH102 Cannot be archived; '&1' is smaller than retention time '&2'
Self-Explanatory Message Since SAP believes that this specific error message is ...
/BOFU/ARCH110
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.