PeopleSoft FSCM 9.2 – Capturing Existing PO Number on Change Order Requisitions

Hello,

We are reviewing our PeopleSoft process for requisitions intended to add to or change an existing PO.

Currently, requesters create a new requisition with Origin = CO and enter the existing PO number in the requisition name or comments. Sometimes the PO number is omitted, requiring Purchasing to research which PO the request belongs to.

We are considering using the delivered Purchasing User-Definable/Custom Fields to capture an Existing PO Number.

Ideally, we would like to:

• Require the PO number when Origin = CO.
• Provide a lookup/validation against existing POs.
• Make the PO reference easily visible to buyers during sourcing.