How To Fix ARC_DAS_CON124 - No WebDAV archive store is maintained for the rule for BOR type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: ARC_DAS_CON - XML DAS Connector: Messages

• Message number: 124

• Message text: No WebDAV archive store is maintained for the rule for BOR type &1

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 ARC_DAS_CON124 - No WebDAV archive store is maintained for the rule for BOR type &1 ?

  The SAP error message ARC_DAS_CON124 indicates that there is no WebDAV archive store maintained for the specified Business Object Repository (BOR) type. This error typically occurs in the context of archiving and document management within SAP systems, particularly when trying to access or store documents using WebDAV.
  Cause:
  The error is caused by the absence of a configured WebDAV archive store for the specific BOR type that is being referenced. This means that the system does not know where to store or retrieve archived documents for that particular object type.
  Solution:
  To resolve this error, you need to ensure that a WebDAV archive store is properly configured for the BOR type in question. Here are the steps to do this:
  
  
  Access the Archive Administration:
  
  Go to transaction code SARA in the SAP GUI.
  
  
  
  Check Archive Object:
  
  Identify the archive object related to the BOR type that is causing the error. You can find this in the archive object settings.
  
  
  
  Maintain WebDAV Archive Store:
  
  Navigate to the configuration settings for the archive object.
  Look for the section where you can maintain the WebDAV archive store.
  Ensure that a valid WebDAV URL is configured and that the connection settings (such as authentication) are correct.
  
  
  
  Test the Configuration:
  
  After configuring the WebDAV archive store, test the connection to ensure that it is working correctly.
  You can do this by trying to archive a document or access an archived document related to the BOR type.
  
  
  
  Check Authorization:
  
  Ensure that the user has the necessary authorizations to access the WebDAV store and perform archiving operations.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration steps, refer to the SAP documentation or consult with your SAP Basis or Archive Management team for assistance.
  
  
  
  Related Information:
  
  WebDAV (Web Distributed Authoring and Versioning): A protocol that allows users to collaboratively edit and manage files on remote web servers. In SAP, it is often used for document management and archiving.
  Business Object Repository (BOR): A framework in SAP that allows for the definition and management of business objects, which can be used in various applications and processes.
  Archiving in SAP: A process that allows for the removal of data from the database to improve performance and manage data growth. Archived data is stored in a way that it can be retrieved when needed.
  
  If the issue persists after following these steps, consider reaching out to SAP support or your internal SAP team for further assistance.