How You Purge Work Order Records from Interface

Oracle Manufacturing execution transactions like work order transactions, operation transactions, material and resource transactions, order less transactions and output transactions performed via Rest, FBDI or UI are done through batch and interface records.

Post transaction completion, the batch and interface records may be retained depending on outcome status. Over a period of time, when large volume of such records get accumulated, the Purge Records from interface job can be scheduled to remove them.

Within ADFDI, you mark the header or detail interface records to be deleted, then delete the records. The records are then deleted from the table. To delete the interface batch record from ADFDI, you must run the purge program. When you run the purge program, it checks and deletes any interface batch records that had no interface header and detail records. When the header record gets deleted, all detail records for that header are deleted automatically.

SOAP services can include import material, and operation transactions that were expected to be used by contract manufacturers for milestone reporting, or in cases where the transactions reported in Manufacturing Execution System (MES) need to be imported to Manufacturing. Because, there was no way to correct and resubmit error records, the purge program was introduced to remove such records from the work order, material, resource and operation transaction interface tables.

Here's a table that explains how you can manage transactions with the Purge Records from Interface scheduled process.

Entity	User Interface	REST	FBDI	Error Correction and Submission
Work Orders (For all work order types which include discrete and process and work order actions, such as create and update)	The data is directly inserted into the production tables. There's no interface table. So, there's no possibility of records getting stuck in the interface. Purge action isn't applicable.	The data is directly inserted into the production tables. There's no interface table. So, there's no possibility of records getting stuck in the interface. Purge action isn't applicable.	The interface table is used for processing. During the import process, data is populated in the interface table, and then inserted into the production table. A batch can contain multiple header interface records. Each header interface record can have multiple detail interface records. If the header interface record and it's detail interface records are processed successfully, then they're deleted. If the header interface record and it's detail interface records aren't processed successfully, then all are marked with status completed error and aren't deleted. If all the header interface and detail interface records for the batch are processed successfully, then the batch record is deleted.	The interface table used for processing. ADFdi correction sheet is used to correct the error records, delete the header and child records. When a header is deleted, a cascade delete is done for all detail type records. Batch level deletion isn't supported. The batch records can be deleted using the Purge program, if there are no header and detail records for the batch. Records must not get stuck in the interface tables. If the upload contains a batch and details, but not header, when import runs it updates the batch as an error. The detail records remains at ready status. ADFdi doesn't display the details because the header doesn't exist, so the details can't be deleted. Purge can't be done for the batch because details exist. The user can't do anything with them.
Work Order Operation Transactions	Interface records created from UI in status COMPLETED_ERRORS, COMPLETED_WARNINGS, GENEALOGY_COMPLETED are purged. IN_PROCESS records are purged after time out of 30 minutes.	IN_PROCESS status batch records and interface records with 30 minute time out are purged. COMPLETED_ERRORS, COMPLETED_WARNINGS status batch and interface records are purged. COMPLETED status batch records are purged, Interface records are deleted by Genealogy API. GENEALOGY_COMPLETED, batch and interface records are purged. Orphan batch records are to be purged in any status.	COMPLETED status batch records are purged, Interface records are deleted by Genealogy API. GENEALOGY_COMPLETED status batch and interface records are purged. COMPLETED_WARNINGS status batch and interface records are purged.	COMPLETED_ERRORS from FBDI are left for error correction. ADFdi correction sheet is used to correct the error records, delete the header and child records. When a header is deleted, a cascade delete is done for all detail type records. Batch level deletion isn't supported.
Work Order Material Transactions	Interface records created from UI in status COMPLETED_ERRORS, COMPLETED_WARNINGS, GENEALOGY_COMPLETED are purged. IN_PROCESS records are purged after time out of 30 minutes.	IN_PROCESS status batch records and interface records with 30 minute time out are purged. COMPLETED_ERRORS, COMPLETED_WARNINGS status batch and interface records are purged. COMPLETED status batch records are purged, Interface records are deleted by Genealogy API. GENEALOGY_COMPLETED, batch and interface records are purged. Orphan batch records are to be purged in any status.	COMPLETED status batch records are purged, Interface records are deleted by Genealogy API. GENEALOGY_COMPLETED status batch and interface records are purged. COMPLETED_WARNINGS status batch and interface records are purged.	COMPLETED_ERRORS status batch and interface records aren't purged and left for error correction. ADFdi correction sheet is used to correct the error records, delete the header and child records. When a header is deleted, a cascade delete is done for all detail type records. Batch level deletion isn't supported.
Output Transactions	Interface table is used for processing. Purge deletes the stuck (IN_PROCESS) records after half an hour.	Interface table is used for processing. Purge deletes the stuck (IN_PROCESS) records after half an hour. Purge also deletes the successful records and error records.	The interface table used for processing. During the import process, data populated in the interface table; then inserted into the production table. If header is process successfully, header and detail records are deleted. If all headers are processed successfully, the batch is deleted. If an error is found, all interface records are marked as completed errors and not deleted.	ADFdi correction sheet is used to correct the error records and delete the header and child records. When a header is deleted, a cascade delete is done for all detail type records.
Orderless Transactions	The interface table is used for processing. Purge deletes the stuck (IN_PROCESS) records after half an hour. During orderless transaction, records are inserted in WIE_WORK_ORDERS_B as well. Any stale records in WIE_WORK_ORDERS_B isn't purged by an ESS job.	The interface table is used for processing. Purge deletes the stuck (IN_PROCESS) records after 30 minutes. Purge also deletes the successful records and error records.	The interface table is used for processing. During the import process, data populated in the interface table, and then inserted into the production table. If header is processed successfully, header and detail records are deleted. If all headers are process successfully, the batch is deleted. If an error is found, all interface records are marked as completed errors and not deleted.	ADFdi correction sheet is used to correct the error records and delete the header and child records. When a header is deleted, a cascade delete is done for all detail type records.
Work Order Resource Transactions	Interface records created from UI in status COMPLETED_ERRORS, COMPLETED_WARNINGS, GENEALOGY_COMPLETED are purged. IN_PROCESS records are purged after time out of 30 minutes.	IN_PROCESS status batch records and interface records with 30 minute time out are purged. COMPLETED_ERRORS, COMPLETED_WARNINGS status batch and interface records are purged. COMPLETED status batch records are purged. Orphan batch records are to be purged in any status.	COMPLETED status batch and interface records are purged.	COMPLETED_ERRORS status batch and interface records aren't purged and left for error correction.

Note: Using the Purge Records from Interface scheduled process, you can purge all the interface records and also purge unprocessed interface records. However, interface records that are yet to be interfaced to Genealogy won't be purged.