How To Fix RSDAS_PERSIST013 - Data Access Service ID & not found in version &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDAS_PERSIST - Persistence Layer for ER Data Access Services

• Message number: 013

• Message text: Data Access Service ID & not found in version &2

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 RSDAS_PERSIST013 - Data Access Service ID & not found in version &2 ?

  The SAP error message RSDAS_PERSIST013 indicates that a specific Data Access Service (DAS) ID is not found in the specified version. This error typically occurs in the context of SAP BW (Business Warehouse) or SAP HANA when there is an issue with accessing or retrieving data from a data source.
  Cause:
  
  Missing Data Access Service ID: The specified Data Access Service ID does not exist in the system. This could be due to a deletion, incorrect configuration, or a typo in the ID.
  Version Mismatch: The version specified in the error message may not correspond to the version where the Data Access Service ID is defined.
  Transport Issues: If the Data Access Service was recently transported from another system, it may not have been properly imported or activated.
  Authorization Issues: The user may not have the necessary authorizations to access the specified Data Access Service.
  
  Solution:
  
  Verify Data Access Service ID: Check if the Data Access Service ID exists in the system. You can do this by navigating to the relevant transaction or using the appropriate SAP BW or HANA tools.
  Check Version: Ensure that you are using the correct version of the Data Access Service. If necessary, update the version in your request or configuration.
  Re-import Transport Requests: If the Data Access Service was transported, ensure that the transport request was successfully imported and activated in the target system.
  Check Authorizations: Verify that the user has the necessary authorizations to access the Data Access Service. You may need to consult with your SAP security team to ensure proper roles and permissions are assigned.
  Consult Documentation: Review SAP documentation or notes related to the specific Data Access Service to ensure that it is set up correctly.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench) or other tools used for managing data access services.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.