My Oracle Support Banner

Purchase Order not Autocreated Automatically from CTO Requisition (Doc ID 2682628.1)

Last updated on MARCH 15, 2022

Applies to:

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


Using Purchasing, Version 12.
 PO is not getting created from the Requisition after Configure to Order (CTO) flow
  Requisition does not have reference to the source document ( GBPA in this case)



Steps to reproduce:

1. Create an ATO Model.
2. Create a buy type sourcing rule for this model. Attach it to a sourcing
assignment set. Set the value of the profile MRP: Default Sourcing Assignment
Set to this assignment set.
3. Create an ASL for the model with the same supplier and site as the
sourcing rule.
4. Set the profile PO: Automatic Document Sourcing to Yes.
5. Create a GBPA for the model with the same supplier and supplier site as
the sourcing rule and ASL.
6. Enter a price break for the model line. Enter the Start and End Dates of
this price break (ex. 01-MAY-2020 to 31-MAY-2020)
7. Set the expiration date value for the model line (ex. 30-JUN-2020).
8. Create, configure and book a SO for this configuration. Run ACC for this
9. Once ACC completes, the new config item will get inserted in the blanket
from step 5. with expiration date 31-May-2020 value in Agreement tab  

10. Requisition gets created , however there is no source document reference,
no PO is automatically created


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.