'Price can be Changed on Order' on Procurement Contract Not Working for eProcurement Requisitions
(Doc ID 2347657.1)
Last updated on OCTOBER 29, 2018
Applies to:PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
'Price can be changed on Order' on Contract works differently when using sourcing vs referencing on Purchase Order
Steps to Replicate the Issue:
Scenario# 1 - With a $0 price and the price can change set to Y on Contract Line
1.Created a Contract with $0 max amount(meaning unlimited mount) and one line that is description only. Trying to track the spend for that contract
2.Contract Line Details.
3.Created a PO by copying the contract from the PO header
4.Created a PO by searching for the contract from the PO Line without entering the Vendor ID on the PO header
5.Created a PO by entering the Contract in the contract ID field of the PO Line and before or after entering the vendor ID on the PO header.
The contract does not show up as it is a $0 price contract line.
6.Now try to create a Purchasing requisition and enter the contract using the contract search button on the req line.
(Note - The contract does not show up on the contract ID field on the req line as it is a $0 contract line) Sourced the req to a PO using auto source
7.Now try to create an eProcurement requisition and associate the contract to the req, Click on req line details icon to apply the contract by searching for the contract in the contract ID field.
(Note: The contract ID shows up even though it is a $0 contract line. It does not show up on the PO line.
Contract ID field though. The contract is also available when using the search icon on the req line)
With a $0 price and the price can change set to Y, it works fine with all above scenarios.
Scenario#2 -Tried out the same as above with a non-zero price and price can change set to N
1.Create a contract with a non-zero price and price can be changed set to N
2.Copy contract from PO header ------------------------> works correctly
3.Copy contract from PO Line using contract search ---> work correctly
4.Copy contract from PO Line using contract ID Field --> works correctly
5.Using purchasing requisitions works fine but why is the default quantity of 2 not copied over like it does on the Purchase Order? Sourced the req
6.Create an eProcurement requisition and associate the contract. Sourced the requisition to Purchase Order using Auto Source. Price Field is available for edit. This is incorrect.
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