How To Fix THMHR_EVENT101 - Hedge strategy & cannot be found in the Customizing table

THMHR_EVENT101 - Overview

• Message type: E = Error

• Message class: THMHR_EVENT - Messages for events occuring at valuation

• Message number: 101

• Message text: Hedge strategy & cannot be found in the Customizing table

What causes this issue?

The hedge strategy cannot be found in the customizing table.

System Response

Processing cannot continue.

How to fix this error?

Verify that the configuration for the hedge strategy has been completed
properly in the Customizing, and assign a valid hedge strategy to the
hedging relationship in the <LS>Hedge Accounting for Exposures</>
(transaction <NP>THMEX</>).
<DS:SIMG.THMHRV_HR_STR>Customizing Hedge Strategy</>

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

THMHR_EVENT101 - Details

• The SAP error message THMHR_EVENT101 typically indicates that a hedge strategy cannot be found in the customizing table. This error is often encountered in the context of Treasury and Risk Management (TRM) within SAP, particularly when dealing with hedging transactions.
  
  Cause:
  
  Missing Customizing Entries: The hedge strategy you are trying to use has not been defined in the customizing tables. This could be due to a lack of configuration or an oversight during the setup process.
  Incorrect Configuration: The hedge strategy may have been incorrectly configured or deleted, leading to the system being unable to locate it.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the hedge strategy, which can lead to the appearance of this error.
  Data Inconsistencies: There may be inconsistencies in the data or a mismatch between the hedge strategy and the transaction being processed.
  
  
  Solution:
  
  
  Check Customizing Settings:
  
  Navigate to the relevant customizing transaction (usually in SPRO) and verify