How To Fix ICL_BRF_PLUS073 - Message type changed from &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ICL_BRF_PLUS - BRFplus - Message Class

• Message number: 073

• Message text: Message type changed from &1 to &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 ICL_BRF_PLUS073 - Message type changed from &1 to &2 ?

  The SAP error message ICL_BRF_PLUS073 indicates that there has been a change in the message type for a specific business rule framework (BRF+) application. This typically occurs when the message type associated with a BRF+ decision table or rule has been modified, which can lead to inconsistencies or issues in processing.
  Cause:
  
  Change in Configuration: The message type for a BRF+ application may have been changed in the configuration settings, either intentionally or accidentally.
  Transport Issues: If the BRF+ application was transported from one system to another (e.g., from development to production), there may have been discrepancies in the message type settings.
  Versioning: Different versions of the BRF+ application may have different message types, leading to conflicts when trying to execute rules.
  
  Solution:
  
  Check Configuration: Review the configuration settings for the BRF+ application to ensure that the message type is set correctly. You can do this by navigating to the BRF+ workbench and checking the relevant decision tables or rules.
  Consistency Check: Perform a consistency check on the BRF+ application to identify any discrepancies or issues that need to be resolved.
  Transport Validation: If the issue arose after a transport, validate that all necessary objects and configurations were included in the transport request. Ensure that the target system has the same configuration as the source system.
  Revert Changes: If the change was made unintentionally, consider reverting to the previous message type or configuration that was working correctly.
  Consult Documentation: Refer to SAP documentation or notes related to BRF+ for any specific guidance on handling message type changes.
  
  Related Information:
  
  BRF+ Documentation: SAP provides extensive documentation on BRF+ that can help you understand how to manage decision tables, rules, and message types.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to BRF+ and message types.
  Community Forums: Engage with the SAP community forums or support channels for additional insights or similar experiences from other users.
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.