SAP Knowledge Base Article - Preview

2096169 - Automatic Matching on OriginalvalueDate fails to match - LMS 6.2

Symptom

  • Defined matching rules on a list of variables for which OriginalValueDate is part of, causes matching engine not to match when two transactions have different value dates.
  • matching rule :

# # match on OriginalValuedate, Currency, Amount, ChannelId and ExternalReference.

# match { ID: 1017 tolerance: 0.00001 match: OriginalValueDate = match: Currency = match: OriginalAmount = match: ChannelId = match: ExternalReference = matchtype: regular } 

matching on OriginalValue Date doesn't work.

Changing the Value Date of the AR/UC to 17 Nov 2014, then the two transactions do match. They take the matchrule: # # If the incoming transaction has the same ValueDate, Currency and ChannelId as an existing transaction, and # their Remaining Amounts are within a tolerance of 1, consider them a match. # match { ID: 1007 tolerance: 1 match: W_ValueDate = match: Currency = match: OriginalAmount = match: ChannelId = matchtype: regular }


Read more...

Environment

  • LMS version v6.2
  • RHEL

Product

SAP Event Stream Processor 5.1 ; SAP Liquidity Management for Banking 6.2

Keywords

KBA , FS-LMS , Liquidity Management Suite , Product Enhancement

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.