Description: |
Background Tasks are backed up due to accidental submission of wide-open Order Invoicing/Credit Memo or Consolidated Invoicing print How can I cancel large numbers of invoices or credit memos that were printed? User accidentally ran Order Invoicing/Credit Memo with no parameters and 1000's of invoices are printing and cannot be stopped. |
Work Around: |
1. Go to Utility Server and select Start>Administrative Tools>Services>Infor Framework Task Man service 3b. Update the reports to 'Waiting' status through an update statement similar to this: update ActiveBGTasks_mst set TaskStatusCode = 'WAITING' where TaskNumber like '%<TN>%' and TaskName = '<TaskName>' Delete ActiveBGTasks_mst where TaskStatusCode = 'Waiting' and TaskName = '<TaskName>' Here are some other example queries which can let you target a specific task and/or user. This is useful for example when you know the username of the user that submitted the task or for accidentally printed invoices where you know the Task Name you wish to delete. select * from ActiveBGTasks_mst where TaskName = 'ConsolidatedInvoicingLaser' and RequestingUser = 'bob' The above would display only tasks for Consolidated Invoicing that were submitted by the Syteline user 'bob'. Once you confirm that you are seeing the records that you want to delete, you can then replace the select with a delete, and it would look something like this: delete ActiveBGTasks_mst where TaskName = 'ConsolidatedInvoicingLaser' and RequestingUser = 'bob' An example for standard invoicing would be: delete ActiveBGTasks_mst where Taskname = 'OrderInvoicingCreditMemoReportLaser' and RequestingUser = 'bob' The above queries can be updated to substitute in any Task and/or RequestingUser as necessary. As with any query, it is strongly recommended that you first run a Select of the records to be sure you're seeing only the records you wish to delete and then change the query to a Delete only after that has been confirmed. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article