Deleting Location in Location or Inventory Location Control Files May Cause Referential Integrity Error

Deleting Location in Location or Inventory Location Control Files May Cause Referential Integrity Error

Release Date: 03/14/2025
Version: 7.x & Up

Q - We no longer have our warehouse in Tulsa, OK (TL), and I would like to delete the location “TL” in Elliott.  The Stock Status Report shows there is no inventory on hand in the TL location.  Is it as simple as going to Location Control File Maintenance – Create – then “D” for delete and all items for Location TL?  Or is there anything else that needs to be verified before proceeding with this action?

Any other file cleanup you would recommend?


A - Deleting a location in Elliott could be risky and potentially create database referential integrity.  That is to say we can’t predict what may happen when there’s an open or history records reference to a location that is deleted. For this reason, we recommend you simply mark the “TL” location description as “Do Not Use” to avoid this issue.

Deleting unused Inventory Location Control records has lesser risk, but the risk still exists, it depends on if there are any order (including COP, PO, and BOMP) references to the location control record. I have seen errors happen with reset allocations on a work order with components where the Location Control record no longer exists. Also, there’s no mass delete utility and it would be tedious for you to delete these records one by one.  If you really want to delete these records.  We can save these records first and use the backend to mass delete them.  If the mass delete causes a problem, we can restore these records back.  You will not be able to handle this on your own so please coordinate with our support.


EMK

    • Related Articles

    • Avalara Setup Procedures - Integrity Check

      Release Date: 4/28/23 Date Revised: 6/10/24 Version: 8.6 and Above You should run Avalara integrity check on daily, weekly or monthly basis. The frequency depends on if you can commit resources for someone to look at the output of this report and ...

    • Avalara - Log Files

      Release Date: 4/28/23 Version: 8.6 & Above Log files can be very important when investigating why taxes may not be calculated as expected. In particular, the AvalaraAPICalls.xml file is important when you speak with Avalara reps for support. This ...

    • Btrieve Error Codes 001 - 199

      MicroKernel (Btrieve) Database Engine Status Codes This section describes status codes that the MicroKernel returns. All status codes are provided in 3-digit formats since the search on this website cannot search 1 or 2-digit words correctly. That is ...

    • Can I Delete a Ship-To Location in COP?

      Release Date: 05/08/2024 Version: 7.x & Up Q - Does it cause an integrity issue if we delete a ship-to and go back to using the customer file address only? They have some customers who never needed a ship-to but one had been added when they first ...

    • Common Issues with Importing CSV Files Into Elliott

      Release Date: 12/18/2020 Version: 7.0 & Up Elliott Business Software has extensive features with CSV file export and import. It provides a gateway to view Elliott's data in Excel spreadsheets and optionally allow users to edit the data in ...