Functional Currency Document Is Always Set As Requisition's Source Document Even Though Different Currency Is Specified On Requisition Line
(Doc ID 2873644.1)
Last updated on MAY 30, 2022
Applies to:
Oracle Purchasing - Version 12.2.10 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
On a requisition line, a blanket purchase agreement(BPA) defined with functional currency is always set as a source document even though different currency is specified.
Expected Behavior
When currency information is provided on a requisition line, a blanket purchase agreement defined with the corresponding currency is set as a source document.
Steps to Reproduce
- Navigate to System Administrator > Profiles > System > set Profile Option PO: Automatic Sourcing = Yes.
- Navigate to Purchasing > Purchase Orders > Purchase Orders and create two blanket agreements as below;
- BPA#100, with functional currency (example: USD)
- BPA# 200, with different currency (example: JPY) - Navigate to Purchasing > Requisitions > Requisitions
- Tools menu > Preference > Set Currency: JPY and provide Rate information > Apply.
- On Lines tab, provide item information.
- On Source Details tab, BPA#100 is set as a source document.
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 |