Purge Receiving Interface
Use the Purge Receiving Interface scheduled process to purge records that are in error, or in error and pending statuses, from the RCV_TRANSACTIONS_INTERFACE and RCV_HEADERS_INTERFACE tables.
These tables store information about receiving transactions that are waiting to be processed by the Receiving Transaction Manager or were rejected due to an error when the transaction manager tried to process the transaction. When the Receiving Transaction Manager successfully processes a transaction, it deletes the transaction from this table.
When to Use
When processing a receiving transaction, the header information is stored in the RCV_HEADERS_INTERFACE table and the line information is stored in the RCV_TRANSACTIONS_INTERFACE table. After successful processing, the data is removed from the RCV_TRANSACTIONS_INTERFACE, but the data in RCV_HEADERS_INTERFACE is retained. However, if any processing errors occur, the data remains in all interface tables. When the number of rows in the RCV_TRANSACTIONS_INTERFACE table exceeds 10,000, it slows down the Receiving pages, and the processing performance of the Receiving RESTs and SOAP services deteriorates. Therefore, you should run the process manually to purge data from the interface tables if there are more than 10,000 lines in the Receiving Transactions Interface.
Privileges Required
- Purge Receiving Interface Transactions (RCV_PURGE_RECEIVING_INTERFACE_TRANSACTIONS_PRIV)
Specifications
| Specification | Description |
|---|---|
| Job Type | Scheduled or as needed. |
| Frequency | If you use Receiving REST APIs, SOAP services, or file-based
data import (FBDI) to interface receipts, we recommend
scheduling this process to run at least once or twice a day. If
you use the UI for receiving transactions, then you can schedule
the process to run once a week to ensure that no error or
pending records are present in the interface tables. This helps
speed up the transactional processing. Run the process manually if there are more than 10,000 lines in the Receiving Transactions Interface. |
| Time of Day | Schedule the process to run when the receiving activities aren’t taking place. For example, you can schedule the process to run at 7 PM or 12 AM. |
| Duration | This process depends on the volume of the data in the interface tables. |
| Compatibility | There should be only one instance of the process at any one time. |
Parameters
| Parameter | Optional or Required | Description | Parameter Values | Special Combinations Required | Notes |
|---|---|---|---|---|---|
| Purge Data Before | Optional | Purges all the records before the date selected. | Date | None | N/A |
| Status | Optional | The default status is Error. You can select to purge records that are in either in Error or Error and pending statuses. | Error Error and pending |
None | N/A |
Troubleshooting Information
- You can view the status of the process in the Scheduled Processes work area. Select the row and click the log and output attachment on the Process Details tab. Download the log and output file. Share the files with support to log a service request.
- The Purge Receiving Interface request log file shows the information on the number of rows deleted in the RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE tables.
- You can use the Receiving Document Activity diagnostic report. The Receiving Document Activity report provides diagnostic information about your application. Review the Error section of the diagnostic report and find any error text.