Deleting a Batch (ICL)

When the Transaction Server receives a delete batch (ICL) request, it ensures the request is valid and uses a return code value to indicate any problems. If problems exist, error messages are logged and the delete operation is not started. A delete request will not start if:

• The requested inbound batch (ICL) was not found in the database
• The requested inbound batch (ICL) has not completed its initial load
• The requested inbound batch (ICL) did not originate from an electronic file
• The requested inbound batch (ICL) has already been deleted
• A delete operation for the specified inbound batch (ICL) is already in progress

Once the request is determined to be valid, the inbound batch (ICL) is deleted as follows:

1. The condition flag in the outbound batch (ICL) is set to deleted
2. For each batch (ICL) that belongs to the batch (ICL) group, the condition flag is set to deleted and the loaded state is turned off
3. The transactions that are attached to the batch (ICL) are all marked as deleted
4. Transaction Server notifies other applications by issuing an BatchDelete event and waits for each to complete. Refer to Configure the BatchDelete Event Handler in Transaction Server for more information. The application can log data during the delete. Refer to Delete Batch (ICL) Processing and Error Reporting for more information about how the applications process and log data for the delete event.
5. Transaction Server determines if the batch (ICL) was successfully deleted by examining the return codes from all of the other applications:
   • The delete fails when any of the applications returns an error. The delete is aborted.
   • The delete succeeds when none of the applications returns an error. The batch (ICL) loaded state indicator is cleared.

The delete can be restarted to force completion of a previously run delete operation.