Get Started with Redwood: Oracle Cloud SCM and Purchasing
Lack of traceability between Requisition and Purchase Order after contract creation
We are working with the following procurement flow:
Requisition → Negotiation → Contract Creation → Purchase Order (via Fulfill Orders)
After the Purchase Orders are generated, when reviewing the PO lifecycle, we are unable to identify or trace back the original internal requisition that initiated the process.
Is there any standard functionality, configuration, or recommended best practice that allows maintaining end-to-end traceability between the Purchase Order and the originating requisition in this scenario?
0