AUTOCREATE PURCHASE REQUISITIONS: ENTER A REQUESTER WHO IS A VALID WORKER
(Doc ID 2676541.1)
Last updated on JUNE 01, 2020
Applies to:Oracle Configure to Order - Version 12.2.6 and later
Information in this document applies to any platform.
On : 12.2.6 version, Transaction Fulfillment
With around 1000 buy items where where the Assemble to Order (Replenish to Order) flag is set to yes. So, when these items end up as shippable sales order lines, they create purchase requisitions via AutoCreate Purchase Requisitions and Requisition Import with an Import Source of CTO. These Sales Orders are often entered months in advance of their ship date. The lead time for most of these ATO buys is just a couple weeks.
Previously, AutoCreate Purchase Requisitions was creating requisitions as soon as the order was progressed. It is difficult for the Purchasing team to separate off the Requisitions for which they did not yet have to create a PO. During the last few years, users started running AutoCreate Purchase Requisitions with Offset Days parameter set to 15. That helped ensure the Requisition was created just in time to get the item to the factory to ship with the rest of the order. That went just fine until late last year when it was found that some reqs were missing. This is when it was determine that some of the Reqs are erroring out for "PREPARER_ID: Preparer is not an active worker" and "DELIVER_TO_REQUESTOR_ID: The requester is not an active worker". The engineer that had entered the sales order line no longer worked for the company and the user record was end-dated.
Order Management Development determined that the code in CTOPROCB.pls already aims to populate the preparer/requestor with OM system parameter "Requestor For Drop Ship Orders Created By External Users" in the case where created_by on SO line is not an EBS user. However, they fail to account for the case where created_by was an EBS user at one time, but is no longer.
"PREPARER_ID: Preparer is not an active worker"
"DELIVER_TO_REQUESTOR_ID: The requester is not an active worker".
The issue can be reproduced at will with the following steps:
1. Order Management Responsibility
2. Create the Sales Order
3. Save and book.
4. Progress the order.
5. Run the Autocreate Purchase Requisition process.
6. Occasionally see messages mentioned above.
The issue has the following business impact:
Due to this issue, users cannot complete the sales order process without some errors.
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