Purge Interface Table

Use the Purge Receiving Interface process to maintain the receiving interface.

Receipts that are successfully imported are usually purged automatically. However, some receipt rows may remain in the interface and accumulate over time. The Purge Receiving Interface process purges records that are in error, or in error and pending statuses.

Navigate with the Cloud UI and schedule the process “Purge Receiving Interface.”

Name	Description	Optional/Required
Purge before date	Purges all the records before the date selected.	Optional
Status	The default status is error. You can also select and purge records that are in both error and pending statuses.	The default status is error. You can also select and purge records that are in both error and pending statuses.

Name

Description

Optional/Required

Purge before date

Purges all the records before the date selected.

Optional

Status

The default status is error. You can also select and purge records that are in both error and pending statuses.

Before initiating the purge process, confirm that the Refresh Import process has been executed. Failure to do so will result in successful receipts and errors not being returned to the Integrator worksheet.

Oracle recommendation

To optimize transactional processing, we recommend scheduling this process to run at least once or twice daily. This is particularly important when using Receiving REST APIs for interfacing receipts. Performance of the Receiving pages and REST services can significantly deteriorate when the transaction interface table exceeds 10,000 rows.