How To Fix FXM_CORE072 - B/S hedge request &1 does not exist.

FXM_CORE072 - Overview

• Message type: E = Error

• Message class: FXM_CORE -

• Message number: 072

• Message text: B/S hedge request &1 does not exist.

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 FXM_CORE072 - B/S hedge request &1 does not exist. ?

  The SAP error message FXM_CORE072 indicates that a hedge request does not exist in the system. This error typically occurs in the context of financial transactions, particularly when dealing with hedging instruments in SAP's Financial Supply Chain Management (FSCM) or Treasury modules.
  
  Cause:
  
  
  Non-Existent Hedge Request: The hedge request you are trying to access or process does not exist in the system. This could be due to:
  
  The hedge request was never created.
  The hedge request was deleted or archived.
  A typographical error in the hedge request ID you are trying to use.
  
  
  
  Authorization Issues: The user may not have the necessary permissions to view or access the hedge request.
  
  
  Data Synchronization Issues: If the system is integrated with other systems, there may be a delay or issue in data synchronization that prevents the hedge request from being recognized.
  
  
  
  Solution:
  
  
  Verify Hedge Request ID: Double-check the hedge request ID you are using to ensure it is correct. Look for