How To Fix TPM_TRD1030 - OTC transactions &2 and &3 excluded in company code &1 not consistent

TPM_TRD1030 - Overview

• Message type: E = Error

• Message class: TPM_TRD1 - Treasury: Messages regarding the Distributor

• Message number: 030

• Message text: OTC transactions &2 and &3 excluded in company code &1 not consistent

What causes this issue?

The two OTC transactions &V2& and &V3& are linked by a business
transaction (for example, exercising an option). One of the transactions
is inactive. Therefore the linked business transaction cannot be
included in position management.

System Response

The initialization cannot be carried out.

How to fix this error?

Correct the status of both transactions using report
RFTR_MIGRATION_EXCLUDE_OTC. Make sure that both transactions are either
excluded or are relevant for position management.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message TPM_TRD1030 - OTC transactions &2 and &3 excluded in company code &1 not consistent ?

  The SAP error message TPM_TRD1030 indicates that there is an inconsistency in the OTC (Order to Cash) transactions for the specified company code. This error typically arises in the context of Treasury and Risk Management (TRM) when there are discrepancies in the transaction data that prevent the system from processing them correctly.
  
  Cause:
  
  Inconsistent Data: The transactions specified (&2 and &3) may have inconsistent or missing data that does not align with the company code (&1) settings or configurations.
  
  Configuration Issues: There may be configuration issues in the Treasury module or the company code settings that lead to the exclusion of these transactions.
  Master Data Issues: Problems with master data related to customers, vendors, or financial instruments can also lead to inconsistencies.
  Transaction Status: The status of the transactions may not be appropriate for processing, such as being in a locked state or not fully posted.
  
  
  Solution:
  
  Check Transaction Data: Review the details of the transactions (&2