How To Fix ARC_DAS_CON118 - BOR type &1 does not have any of the selected document types

SAP Error Message - Details

• Message type: E = Error

• Message class: ARC_DAS_CON - XML DAS Connector: Messages

• Message number: 118

• Message text: BOR type &1 does not have any of the selected document types

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_CON118 - BOR type &1 does not have any of the selected document types ?

  The SAP error message ARC_DAS_CON118 indicates that a specific business object (BOR type) does not have any of the selected document types associated with it. This error typically arises in the context of document management or archiving processes within SAP.
  Cause:
  
  Missing Document Types: The BOR type you are trying to work with does not have any document types assigned to it. This could be due to configuration issues or missing entries in the relevant tables.
  Incorrect Configuration: The configuration settings for the document types or the BOR type may not be set up correctly.
  Data Inconsistency: There may be inconsistencies in the data that prevent the system from recognizing the relationship between the BOR type and the document types.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the BOR type in the SAP system. Ensure that the document types you are trying to use are correctly assigned to the BOR type.
  You can check this in transaction SWO1 (Business Object Builder) or SWE2 (Event Linkage) to see if the BOR type is correctly configured.
  
  
  
  Assign Document Types:
  
  If the document types are not assigned, you will need to assign the appropriate document types to the BOR type. This can usually be done in the customizing settings for document management or archiving.
  
  
  
  Review Authorization:
  
  Ensure that you have the necessary authorizations to access the document types and BOR types. Sometimes, authorization issues can lead to such errors.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest support packages and notes, as there may be fixes or enhancements related to this issue.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to document management and BOR types for any specific instructions or guidelines.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the configuration and assignments, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version and configuration of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SWO1, SWE2, and SARA (for archiving).
  SAP Notes: Search for SAP Notes related to ARC_DAS_CON118 for any known issues or patches.
  Documentation: Review the SAP Help Portal for documentation on Business Object Repository (BOR) and document management.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.