My Oracle Support Banner

In BWC Document Builder Currency Of Contract Purchase Agreement Not Being Defaulted To Create PO (Doc ID 2758656.1)

Last updated on MARCH 08, 2021

Applies to:

Oracle Purchasing - Version 12.2.9 and later
Information in this document applies to any platform.

Symptoms

The Supplier and the CPA is in GBP but the Requisition is in USD. The PO created in BWC doc builder should be in GBP and this is defaulted from the CPA.

The Purchasing User Guide states the following:
If you source to a foreign currency blanket purchase agreement, contract purchase agreement, or catalog quotation, Oracle Purchasing retrieves the foreign currency information for the document.

Your user-defined preferences for currency are overridden by the currency information on the source document.

This is also true even if the source document currency is blank (the same as the base currency).

By using a single currency, the spend on the Contract Purchase Agreement can be calculated.

Steps:

1. Using Purchasing Responsibility - CPA created with GBP currency
2. Using Iprocurement Responsibility - source and create req in iproc in USD
3. Using Purchasing Responsibility - Demand Workbench - choose req (USD) to add to doc builder
4. USD  currency is populated in doc builder and it is expected to be defaulted as GBP from the CPA.

 

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.