How To Fix ARC_DAS_CON130 - No BOR type selected


SAP Error Message - Details

  • Message type: E = Error

  • Message class: ARC_DAS_CON - XML DAS Connector: Messages

  • Message number: 130

  • Message text: No BOR type selected

  • Show details Hide details


  • 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_CON130 - No BOR type selected ?

    The SAP error message ARC_DAS_CON130: No BOR type selected typically occurs in the context of the Archive Development Kit (ADK) or when working with archiving objects in SAP. This error indicates that the system is unable to find a valid Business Object Repository (BOR) type for the operation you are trying to perform.

    Cause:

    1. Missing BOR Type: The most common cause of this error is that no BOR type has been defined or selected for the archiving object you are working with.
    2. Configuration Issues: There may be configuration issues in the archiving object settings or in the related BOR settings.
    3. Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the BOR types.
    4. System Errors: There could be a temporary system error or inconsistency in the configuration.

    Solution:

    1. Check BOR Configuration:

      • Go to transaction SWE2 (Workflow Event Linkages) and check if the BOR type is correctly defined for the archiving object you are using.
      • Ensure that the BOR type is active and properly configured.
    2. Define BOR Type:

      • If no BOR type is defined, you may need to create one. This can be done in transaction SWO1 (Business Object Builder).
      • Create or modify the BOR type to ensure it is linked to the appropriate archiving object.
    3. Review Archiving Object Settings:

      • Check the settings for the archiving object in transaction SARA (Archive Administration) to ensure that the BOR type is correctly assigned.
    4. User Authorizations:

      • Verify that the user has the necessary authorizations to access the BOR types. This can be checked in transaction SU53 after the error occurs.
    5. Consult Documentation:

      • Review SAP documentation or notes related to the specific archiving object you are working with for any additional configuration steps or requirements.
    6. System Check:

      • If the issue persists, consider checking for any system inconsistencies or errors. You may need to consult with your SAP Basis team or check system logs for further insights.

    Related Information:

    • Transaction Codes:

      • SARA: Archive Administration
      • SWO1: Business Object Builder
      • SWE2: Workflow Event Linkages
      • SU53: Authorization Check
    • SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.

    • SAP Community: Consider checking the SAP Community forums for discussions related to this error, as other users may have encountered and resolved similar issues.

    By following these steps, you should be able to identify and resolve the cause of the ARC_DAS_CON130 error in your SAP system.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author