Redwood: Purge Completed PAR Requests

Periodic Automatic Replenishment (PAR) ensures that supplies are consistently restocked in forward locations, so essential goods are always available when needed. Over time, the data generated from PAR requests can assist with optimizing PAR levels and identifying trends in high or low usage items. However, as this data ages, it may lose relevance and can negatively impact calculations, reporting clarity, and system performance. Now you can remove completed PAR request data that's no longer needed.

This feature introduces a new Purge Replenishments Requests scheduled process that enables users to delete completed PAR request records based on configurable parameters, including organization, subinventory, processing status, and purge date criteria. By removing obsolete PAR request records, organizations can better manage data growth and maintain optimal application performance.

Use this feature to:

• Remove success, error, or both (success and error) PAR request records to ensure timely redundant data cleanup.
• Improve system performance by reducing unnecessary data buildup.
• Ensure active and in-progress PAR requests remain unaffected.

Using this scheduled process, you can now select multiple parameters to remove existing replenishment request records.

The Purge Replenishment Requests scheduled process includes these parameters:

• Organization: (Mandatory) You must select the operating organization.
• Subinventory: (Optional) The list of values displays all PAR-enabled subinventories for the selected organization.
• Purge Before Date: (Mandatory) The system purges all requests created before the given date, with a default blank value.
• Status: (Mandatory) Supported values include:
  • Success
  • Error
  • Both

This scheduled process purges only replenishment request records that match the selected organization, subinventory, status, and date criteria.

Here's the job execution behavior:

• Runs as a standard scheduled process. 
• Deletes records based on the input criteria.
• Generates a summary log with record counts and purge completion status.

Purge Replenishment Requests

This feature helps maintain accurate reporting and optimal system efficiency by providing you the ability to clear PAR request data that's no longer relevant to your operations.

Steps to enable and configure

You don't need to do anything to enable this feature.

Tips and considerations

• Review and confirm the purge parameters carefully, such as organization and date criteria, to avoid deleting records unintentionally.
• This feature only applies to completed PAR requests and doesn’t affect active or in-progress replenishment transactions.
• Access to the purge job is controlled through role-based security. Only users with the appropriate privileges can run the purge process.

Key resources

• Oracle Fusion Cloud SCM: Using Inventory Management guide, available on the Oracle Help Center.
• Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Materials Management guide, available on the Oracle Help Center.
• Oracle Fusion Cloud SCM: Redwood: PAR Location Replenishment guide, available on the Oracle Help Center.

Access requirements

You have a couple of options for giving users access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
  • Inventory Manager (ORA_INV_INVENTORY_MANAGER)

These job roles were available prior to this update.

• Users who are assigned configured job roles that contain the following duty role and privilege are able to access this feature:

  • Review PAR Counts Using Responsive Inventory Duty (ORA_INV_REVIEW_PAR_COUNTS_PWA_DUTY)

This duty role was available prior to this update.

This duty role includes the privilege:

• Purge Replenishment Record Requests for existing records (INV_Purge_Replenishment_Requests_PRIV)

This privilege is new in this update.