Purchase Order Purge Criteria
If you are purging purchase orders, the Purge program deletes related purchase requisitions, and receipts. You can purge purchase orders that meet the following criteria:
- You have not updated the header, line, shipment, or distribution after the Last Activity Date. Note that Oracle Purchasing automatically updates some of your purchase order information even of you are not in a purchase order window. For example, when you receive items against a purchase order, Purchasing automatically updates your purchase order shipment to reflect the quantity received.
- You have not updated any releases for a blanket agreement that meets the purge criteria after the Last Activity Date
- Purchase order is approved
- Purchase order is cancelled or closed
- Purchase order is billed and received
- Any contract referenced on a standard purchase order meets the purge criteria
- All online requisitions and all receipts referencing the purchase order meet the purge criteria
- All invoices referencing the purchase order meet the Invoice Purge Criteria (this condition applies only when you choose Matched Invoices and POs for the purge category)
- No invoices match the purchase order (this condition must apply only when you choose Simple Purchase Orders for the purge category)
- Purchase order is not referenced in Oracle Inventory or Oracle MRP
- Purchase order is not Oracle Projects related
- If Oracle Supplier Scheduling is installed, the blanket release is not referenced on a supplier schedule
- Purchase order is not referenced on an ASL
Supplier Schedules Criteria
If Oracle Supplier Scheduling is installed, you can purge supplier schedules that meet the following criteria:
- The schedule must be for the organization specified in the Submit Purge window. For multi-org schedules, we purge the schedule line that meets the purge criteria. Once all lines associated with a schedule are purged, the whole schedule is purged.
- The schedule header Last Update Date must be on or before the Last Activity Date
- All releases of blanket purchase orders referenced on the schedule must be either closed or eligible for purging
- For organizations in which CUM Management is enabled, schedules must have a horizon start date before the current defined CUM Period
- The EDI Gateway interface table does not contain the schedule
CUM Period Criteria
If Oracle Supplier Scheduling is installed, you can purge CUM Periods that meet the following criteria:
- CUM Management is enabled for the organization specified in the Submit Purge window. For multi-org schedules, we purge the schedule line that meets the purge criteria. Once all lines associated with a schedule are purged, the whole schedule is purged.
- The Last Activity Date must be after the CUM Period end date for the purge organization. All previous CUM Periods are purged.
- The system date cannot be within the CUM Period
- When a CUM Period is purged, all CUM Period items, all data for supplier planning and shipping schedules, CUM Period high authorizations, and CUM Period adjustments are also purged
