How To Fix SWN073 - Message with message class &1 and number &2 not found

SWN073 - Overview

• Message type: E = Error

• Message class: SWN - WF Notif: Messages

• Message number: 073

• Message text: Message with message class &1 and number &2 not found

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.

SWN073 - Details

• The SAP error message SWN073 indicates that a message with a specific message class and number could not be found in the system. This typically occurs in the context of the SAP Workflow Notification system, where the system is trying to retrieve a message that is either not defined or not available in the message class specified.
  
  Cause:
  
  Missing Message Definition: The message class and number specified in the error do not exist in the SAP system. This could be due to a missing translation or a custom message that has not been created.
  Incorrect Configuration: The configuration for the workflow or notification might be pointing to an incorrect message class or number.
  Transport Issues: If the message class was recently transported from another system, it may not have been included correctly, or the transport might not have been executed properly.
  
  
  Solution:
  
  Check Message Class: Use transaction code SE91 to check if the message class and