How To Fix TRQ0074 - Ordering mismatch for position outflows &3 vs &4 (security ID &2, cc &1)

TRQ0074 - Overview

• Message type: E = Error

• Message class: TRQ0 - Messages for TR Quantity Ledger

• Message number: 074

• Message text: Ordering mismatch for position outflows &3 vs &4 (security ID &2, cc &1)

What causes this issue?

Single position management (lot accounting)) is used for security ID
&v2&. The quantity ledger is processing transaction by calculation date.
There are transactions which have a different order when sorted by
position date compared to a sorting by calculation date.
position date/calculation date of current transaction: &v3&
position date/calculation date of transaction: &v4&
Due to the different ordering it is recommended the review the lot
assignment (for example in case pure FIFO or LIFO based on trade date is
expected).

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?

Verify the lot assignment for security ID &v2& in company code &v1&.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

TRQ0074 - Details

• The SAP error message TRQ0074 indicates an "Ordering mismatch for position outflows," which typically occurs in the context of Treasury and Risk Management (TRM) or Financial Supply Chain Management (FSCM) modules. This error arises when there is a discrepancy between the expected order of position outflows for a specific security or cash component.
  
  Cause:
  The error message TRQ0074 can be caused by several factors, including:
  
  
  Inconsistent Data: There may be inconsistencies in the data related to the security ID or cash component. This could be due to incorrect entries or missing information in the system.
  
  
  Incorrect Configuration: The configuration settings for the security or cash component may not align with the expected outflow order, leading to mismatches.
  
  
  Transaction Errors: Errors during transaction processing, such as incorrect posting of outflows or inflows, can lead to this mismatch.
  
  
  Timing Issues: If transactions are processed out of the expected sequence, it can result in an ordering mismatch.
  
  
  
  Solution:
  To resolve the