How To Fix RSDHA073 - Name of InfoProvider '&1' does not contain prefix '@3'

RSDHA073 - Overview

• Message type: E = Error

• Message class: RSDHA - HANA Analysis in BW

• Message number: 073

• Message text: Name of InfoProvider '&1' does not contain prefix '@3'

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 RSDHA073 - Name of InfoProvider '&1' does not contain prefix '@3' ?

  The SAP error message RSDHA073 indicates that there is an issue with the naming convention of an InfoProvider in the SAP BW (Business Warehouse) system. Specifically, the error states that the name of the InfoProvider does not contain the required prefix, which is typically used to identify the type or category of the InfoProvider.
  
  Cause:
  
  Naming Convention Violation: The InfoProvider name does not adhere to the expected naming conventions set by the system. For example, certain types of InfoProviders (like InfoCubes, DataStore Objects, etc.) may require specific prefixes (like 'CUBE', 'DSO', etc.) to be recognized correctly by the system.
  
  Configuration Issues: There may be a misconfiguration in the system that is causing it to expect a certain prefix that is not present in the InfoProvider name.
  Transport Issues: If the InfoProvider was transported from another system, it may not have been set up correctly in the target system, leading to this error.
  
  
  Solution:
  
  Check Naming Conventions: