Punchout Requisitions Are Not Defaulting The Negotiated Flag From The Smart Form
(Doc ID 2218975.1)
Last updated on JANUARY 06, 2017
Applies to:Oracle Fusion Purchasing Cloud Service - Version 188.8.131.52.0 and later
Oracle Fusion Purchasing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Generate Purchase Documents From Requisition
Punchout Requisitions are Not Defaulting the Negotiated flag from the Smart form
We have created a smart form which has the negotiated flag ticked by default.
This allows any requisition created using the smart form to utilise the touchless PO feature. I.e. a PO is automatically created once the requisition is approved.
This works fine, and has been working perfectly since go live
We have enabled a Punchout to an Office Supplier. We have assigned the same above smart form to the Punchout content zone.
An example of a Requisition which was created via a Punchout that does not have the negotiated flag defaulted is Requisition: 2115
This is causing massive issues as the customer site as they have to manually create a PO for EVERY punchout order.
Customer expects the negotiation flag to be checked for the even from punchout
The issue has the following business impact:
Due to this issue, users cannot perform automatic PO';s for Punch out requisition
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