I have an issue I've never seen before and I think I can solve it pretty cleanly using DFD&M, but would like a sanity check.
We have a Sales Order tethered to a Work Ticket that was never truly completed (It was just wrong, and then abandoned). A second Work Ticket was created using the same Sales Order Number, but was completed properly this time. After the ticket was completed by our production team, a raw material originally assigned to the ticket, that was not used in during the making of the product, was subsequently removed and reissued into inventory. That completely hosed up the ticket and the Sales Order. We cannot close the ticket using Make to Stock Closing, which means the ticket stays open and the Sales Order cannot be invoiced. We have abandoned the ticket and the Sales Order and started fresh, and we reissued all of the raw materials used in the ticket into inventory. The problem remains that I cannot close or delete the ticket, nor can I delete the SO. The error I get refers to the fact that there is still an Active Status on each the SO and the WT.
Here's where Data File Display & Maintenance comes into play. I can delete the WT from the appropriate table. I made a backup of the live company and used the backup to test my method. Deleting the Work Ticket and its steps then allows me to delete the SO. Problem solved. But when I run the Data Verification Report in the Manufacturing Module, I see errors for the transactions that still exist for the WT and SO that I deleted.
My question: Is all of this deleting in DFD&M safe? Can I delete the transactions from the JT_Transaction.M4T table, the WT from the JT_WorkTicket.M4T table, and the SO from the UI without borking the whole shebang? I have done all of this is the backup company, leaving the live data untouched, and it seems to have worked, but am I causing a larger issue that will come back to haunt me?