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 11.1.11.1.0 and later
Oracle Fusion Purchasing - Version 11.1.9.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.11.1.0 version, Generate Purchase Documents From Requisition

ACTUAL BEHAVIOR
---------------
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

EXPECTED BEHAVIOR
-----------------------
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

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot perform automatic PO';s for Punch out requisition

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms