How To Fix TPM_THX1378 - Test plan cat. in profile &1 inconsistent with scenario &2 definition.

TPM_THX1378 - Overview

• Message type: E = Error

• Message class: TPM_THX1 - Treasury: Message Class for P-HA

• Message number: 378

• Message text: Test plan cat. in profile &1 inconsistent with scenario &2 definition.

What causes this issue?

The test plan category is not set to <LS>Effectiveness Testing is
disabled (e.g. shortcut-method)</> even if the <LS>No Effectiveness Test
</> indicator in the underlying hedging relationship scenario is set to
<LS>TRUE</>.

System Response

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

How to fix this error?

Set the test plan category of the relevant hedging profile to
<LS>Effectiveness Testing is disabled (e.g. shortcut-method)</> in
Customizing under <LS>Financial Supply Chain Management -> Treasury and
Risk Management -> Transaction Manager -> General Settings -> Hedge
Accounting for Positions -> </>
<DS:SIMG.THXV_HR_PROFILE>Define Hedging Profiles</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TPM_THX1378 - Test plan cat. in profile &1 inconsistent with scenario &2 definition. ?

  The SAP error message TPM_THX1378 indicates that there is an inconsistency between the test plan category defined in a profile and the scenario definition in the context of SAP Treasury and Risk Management (TRM) or similar modules. This error typically arises when the configuration settings for a test plan do not align with the expected parameters for a specific scenario.
  
  Cause:
  
  Inconsistent Configuration: The test plan category defined in the profile does not match the scenario definition. This could be due to changes made in the configuration that were not reflected in the test plan or vice versa.
  Missing or Incorrect Assignments: The test plan category may not be correctly assigned to the scenario, or the scenario may not be properly defined in the system.
  Data Migration Issues: If data was migrated from another system or if there were recent updates, inconsistencies may arise due to improper mapping or configuration.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the