How To Fix RSDAS_PERSIST028 - Error when deleting the function module for the D.A.S. &1

RSDAS_PERSIST028 - Overview

• Message type: E = Error

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

• Message number: 028

• Message text: Error when deleting the function module for the D.A.S. &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 RSDAS_PERSIST028 - Error when deleting the function module for the D.A.S. &1 ?

  The SAP error message RSDAS_PERSIST028 typically occurs when there is an issue related to the deletion of a function module in the Data Warehousing (D.A.S.) environment. This error can arise due to various reasons, including dependencies on the function module, authorization issues, or inconsistencies in the system.
  
  Cause:
  
  Dependencies: The function module you are trying to delete may be in use or referenced by other objects, such as InfoProviders, transformations, or data flows.
  Authorization Issues: The user attempting to delete the function module may not have the necessary authorizations to perform this action.
  System Inconsistencies: There may be inconsistencies in the metadata or the system that prevent the deletion of the function module.
  Active Objects: If the function module is active or has been used in a process that is currently running, it cannot be deleted.
  
  
  Solution:
  
  
  Check Dependencies: 
  
  Use transaction codes like SE80 or SE37 to check if the function module is being used by other