When A PO Is Copied, the Field PAY_ON_CODE Is Not Used From the Supplier Site Current Setup
(Doc ID 2323232.1)
Last updated on MARCH 15, 2022
Applies to:
Oracle Purchasing - Version 12.2.6 and laterInformation in this document applies to any platform.
Symptoms
When copying an existing PO, the field "PAY ON CODE - PAY ON RECEIPT" value is copied to another Blanket PO from the terms info on the existing PO even though the pay on code has been removed from the supplier site.
The message box LOV "Pay On" will pop up with displayed_field <NULL> when a release is created from this Blanket
STEPS TO REPRODUCE THE ISSUE
-----------------------
The issue can be reproduced at will with the following steps:
- Enter "pay on receipt" on a supplier site
- Create a Blanket PO with this supplier and site
- Approve the PO
- Copy the PO using the COPY functionality and approve the new Blanket PO
- Go to ENTER RELEASES form and enter a Release using the newly created Blanket PO that was created by copying
Changes
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 |
Changes |
Cause |
Solution |
References |