Do you have any question about this error?
Message type: E = Error
Message class: ARC_DAS_CON - XML DAS Connector: Messages
Message number: 132
Message text: No BOR types or reports selected
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.
ARC_DAS_CON132
- No BOR types or reports selected ?The SAP error message ARC_DAS_CON132 with the description "No BOR types or reports 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 could not find any Business Object Repository (BOR) types or reports that match the criteria specified in the archiving process.
Causes:
- No BOR Types Defined: There may be no BOR types defined for the archiving object you are trying to use.
- Selection Criteria: The selection criteria you have set may not match any existing BOR types or reports.
- Configuration Issues: There may be configuration issues in the archiving object or the related BOR types.
- Authorization Issues: Lack of proper authorizations to access the BOR types or reports.
Solutions:
Check BOR Types:
- Go to transaction SWO1 (Business Object Builder) and check if the required BOR types are defined for the archiving object you are working with.
- Ensure that the BOR types are active and correctly configured.
Review Selection Criteria:
- Review the selection criteria you are using in the archiving process. Make sure they are correctly set to include the relevant BOR types or reports.
Configuration Review:
- Check the configuration of the archiving object in transaction SARA. Ensure that all necessary settings are correctly defined.
- Verify that the archiving object is properly linked to the relevant BOR types.
Authorization Check:
- Ensure that you have the necessary authorizations to access the BOR types and reports. You may need to consult with your SAP security team to verify your permissions.
Consult Documentation:
- Refer to the SAP documentation or help files related to the specific archiving object you are working with for any additional configuration steps or requirements.
SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
ARC_DAS_CON131
No (further) data was found with this selection
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ARC_DAS_CON130
No BOR type selected
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ARC_DAS_CON140
Attachment &1 exists, but could not found in WebDAV store
What causes this issue? According to the index, the attachment is available, but it is not found in the WebDAV archive store.System Response There i...
ARC_DAS_CON141
ArchiveLink references created; for details see job log
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.