Purge Interface Tables

The Purge Interface Tables scheduled process deletes records from import interface tables. This helps maintain system performance by preventing excessive data accumulation that can slow down queries and impact import operations.

When to Use

To remove records from import interface tables, regardless of whether they were successfully processed, failed, or unprocessed.
To free up database space and improve query performance.
To maintain system performance and avoid import failures due to excessive records.

Privileges Required

Load Interface File for Import (FUN_FSCM_LOAD_INTERFACES_PRIV)

Specifications

Review these specifications before setting up this scheduled process:

Specification	Description
Job Type	Ad hoc job. Run at any time.
Frequency	No constraints.
Time of Day	Run it when your system isn't processing a lot of transactions.
Duration	Typically, less than a minute.
Compatibility	NA. You can run more than one instance of this process at the same time.

Parameters

Parameter	Optional or Required	Description
Purge Process Intent	Required	There are three options: File-based data import (FBDI) – Purge the records that were loaded using FBDI. You can purge based on the specified load request ID or a range of load request IDs. Maintenance – Purge the interface table entries and the extracted files in the file location that are older than 30 days or a user-defined age. Other – Purge the records that were loaded using methods other than FBDI. You can purge based on the specified request ID or a range of request IDs.
Import Process	Required	Select the applicable import process name.
Load Request ID	Required	Enter the load request ID or enable an ID range. Load Request ID – Specify the load request ID based on the purge that must be performed. Enable load request ID ranges – Select this option and specify the range of the load request IDs in the Start Load Request ID and End Load Request ID fields. Caution: Load Request ID range should be chosen wisely. Keep it as narrow as possible so that there are no performance issues. For purging multiple load request ID data at once, use the maintenance intent.
Extract Data	Optional	Yes/No. The default value is No. If the value is Yes, the process will extract all the data being selected for purge and upload the data to Oracle WebCenter Content for future audit reference.
Allow Context Purge of Data	Optional	Yes/No. Select Yes if the purge predicate must be considered while purging the FBDI entries.
Number of Days	Optional	If Maintenance is selected as the purge process intent, specify a number greater than 30. The interface table entries and extracted files exceeding this value for a given import process are purged.
Request ID	Optional	If you've selected Other as the purge process intent mode, specify one of the following: Enable request ID - Select this option and specify the Start Request ID and Start Request ID. Request ID – Specify the request ID. Caution: Load Request ID range should be chosen wisely. Keep it as narrow as possible so that there are no performance issues. For purging multiple load request-ID data at once, use the maintenance intent.
Advanced Scheduling	Optional	Lets you schedule the purge process to run later. This is available only when Maintenance is selected as the purge process intent mode.

Troubleshooting Information

Slow system performance - Run the purge job regularly to prevent query slowdowns.
Unable to purge specific data - Ensure that you've selected the correct parameter (for example, the correct Load Request ID, Request ID, or date range).
Scheduled job fails - Check the process logs for errors, ensure that you've configured the job correctly, and verify database integrity.