LCM: How to Associate Receipt Lines with an Invoice if the Invoice Currency is Different from the Purchase Order Currency

LCM: How to Associate Receipt Lines with an Invoice if the Invoice Currency is Different from the Purchase Order Currency

In this Document
Goal
Solution
APPLIES TO:

Oracle Landed Cost Management - Version 12.1.1 and later
Information in this document applies to any platform.
GOAL

Ability to associate Receipt lines with an Invoice if the Invoice Currency is different from the Purchase Order Currency and when Matching Type is 'Freight' or 'Miscellaneous'or 'Tax'

This functionality is required when Freight Charges (or other Miscellaneous Charges) are incurred in a Currency that is different from the Purchase Order Currency and when the Invoice needs to be settled using a Currency that is different from Purchase Order Currency.

SOLUTION



ONLY FOR CUSTOMERS USING : Oracle Landed Cost Management


Customize 'Find Receipts for Matching' Payables form ($AU_TOP/forms/US/ APXRMTCH.fmb) using following steps :

Comment out or remove following code from

OTHR_CHRG_MATCH_EVENT.CONSTRUCT_WHERE_CLAUSE program unit

==
-- and this clause by default
app_query.append ('OTHR_CHRG_MATCH',
'CURRENCY_CODE = :INVOICE.INV_CURR_CODE');
==
Replace 'poh.currency_code = :invoice.inv_curr_code' with '((:match_qf.match_type = 'ITEM' AND poh.currency_code = :invoice.inv_curr_code) OR (:match_qf.match_type <> 'ITEM'))' in PO_NUMBER record group
Replace 'RTXN.currency_code = :invoice.inv_curr_code' with '((:match_qf.match_type = 'ITEM' AND RTXN.currency_code = :invoice.inv_curr_code) OR (:match_qf.match_type <> 'ITEM'))' in RECEIPT_NUMBER record group (at 4 places)
Save the changes and Compile the form to generate APXRMTCH.fmx.
Go to $AP_TOP/forms/US and take a backup of APXRMTCH.fmx (i.e copy APXRMTCH.fmx to APXRMTCH.fmx.bak)
Copy APXRMTCH.fmx (from step b) to $AP_TOP/forms/US
Test the changes


1. As the case with any other Customization, this Customization also needs to be thoroughly tested for all possible business cases before using in Production.

2. As the case with any other Customization, this Customization will also be overridden when a higher version of the form is applied (via a patch). Hence, the Customization needs to be done whenever a patch with higher version of the form (in this case APXRMTCH.fmb ) is applied.


DO NOT provide this codefix to customers under any circumstance if it has not been previously approved by development team. This is due to dependencies.