My Oracle Support Banner

ReIM Automatch Not Respecting DELAY_LN_MTCH_UNTL_ROUTE_DATE Setting (Doc ID 3038132.1)

Last updated on JULY 30, 2024

Applies to:

Oracle Retail Invoice Matching - Version 16.0.3 and later
Information in this document applies to any platform.

Symptoms

On : 16.0.3 version, Document Matching


Line level matching is not working as expected when IM_SYSTEM_OPTION.DELAY_LN_MTCH_UNTL_ROUTE_DATE is set to N
Setting DELAY_LN_MTCH_UNTL_ROUTE_DATE to N, means the invoice should be eligible for detail match as we have receipt available.


The issue can be reproduced at will with the following steps:
  Set IM_SYSTEM_OPTION.DELAY_LN_MTCH_UNTL_ROUTE_DATE to N

  1) Create a PO , ship and receive it.
  2) Create an invoice with some discrepancy i.e. within tolerance.
  3) Make sure Invoice due date and doc date are not meeting routing days criteria.
  5) Run automatch batch, you will notice in im_match_invc_ws table invoice is showing as not eligible for detail match.
  6) Move vdate further to meet routing days criteria.
  7) Run automatch batch you will notice, in im_match_invc_ws table invoice is showing as eligible for detail match and im_doc_head status moving to MTCH.



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.