AR_RECEIPT_API_PUB.APPLY: Functional Currency Remains Unchanged After The Org Context Is Changed
(Doc ID 1377905.1)
Last updated on JULY 13, 2020
Applies to:Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.
Attempting to apply a Receipt using AR_RECEIPT_API_PUB.APPLY and the ORG Context is changed, but the Functional Currency Remains Unchanged.
ARP_PROCESS_APPLICATION PROCEDURE RECEIPT_APPLICATION calls
which calls this to get the functional currency:
lc_currency_code := NVL(p_currency, arpcurr.FunctionalCurrency);
arpcurr.FunctionalCurrency is set by an initial call to arpcurr.init
But arpcurr.init does not get re-initialized when there is an org context change.
If the receipt is loaded using Operating unit 1, which has a functional currency of CURR1 then arpcurr.FunctionalCurrency is set to CURR1
If another receipt is loaded in Operating unit 2, which has functional currency CURR2, after doing as many possible ways to change the org context, arpcurr.FunctionalCurrency remains at CURR1.
When the receipt is called after the ORG context change, the functional currency remains at CURR1.
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