Why It Is a Bad Idea to Delete a Customer or an Item Record

Why It Is a Bad Idea to Delete a Customer or an Item Record

Release Date: 04/16/2024
Version: 7.x & Up

Q - If a customer is deleted after a price code file entry is made, how do we remove it? There are errors in the manual interface and the import file if the customer is Not On File. We can’t manually delete the entry and our understanding is that we cannot process import files if there are errors.

We should be able to delete any entries whether or not they pass validation. Should this work?

In this case, we took the entries for the bad customer out to continue working. A hack would be to create that customer again, but I don’t want to do that.

See screenshot below of what we are seeing.


A - When you try to delete a customer, Elliott is making some limited checks of foreign key references. The check is not exhaustive. Hence you can delete a customer even though that customer is still being referenced in other tables. For this reason, we do not recommend deleting a customer unless you know for sure there is no foreign key reference. For example, if you just added a customer and you know there's no activity for this customer. Then it is safe to delete this customer.  Otherwise, a safer way is to obsolete the customer by changing the name to “** DO NOT USED **” and put the customer credit hold to “Y”…etc.

Since you did delete the customer and we are in the predicament now, I can think of a few ways to proceed:

  1. Add the customer back temporarily and delete the price code records. You can delete the customer afterwards.  But there’s no guarantee you won’t run into problems elsewhere.
  2. We can use PSQL Control Center to delete these price code records.
  3. We can come up with a change in the “Import Price Code Future Price” application so that when you try to “Delete,” we don’t check the customer foreign key and it won’t error out. You can post an idea on the Elliott Support Portal and we can see if this idea gains supports from other Elliott users.  
A similar issue applies to Item Master. We do not recommend that you delete an item record if that item has activities including history.  You should simply obsolete that item instead.

EMK


    • Related Articles

    • 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 ...

    • Feature - Allow Mass Delete of Attribute Records

      Release date: 1/9/2019 Revised Date: 02/14/2024 Version: 8.5 & Up This feature will allow mass deletion of attribute records. It is called from Util-Setup-> System File Maintenance-> Import-> Mass Delete Attribute. This application will delete the ...

    • Feature - Prevent Item Record Deletion if BOMP Cost Master Record Exists

      Release date: 12/19/2018 When deleting an item in I/M--> Maintenance --> Item file and using BOMP, if the item is on file in the BOMP Cost Master File, the user is presented with an error message and deletion of the item is prevented. Also, in I/M ...

    • How Do I Write off Bad Debts in Accounts Receivable?

      Release Date: 05/17/2024 Version: 7.x & Up Q - How do I write off bad accounts receivable? A - The easiest way is to use a process from AR Cash Receipts Processing. In the example below, you are writing off invoice # 500310, The invoice amount is ...

    • CPCUSITM Customer Order Processing Customer Item File Maintenance

      Customer Item File Maintenance Application Overview Some customers place orders using their item numbers rather than yours. Without a proper cross-referencing system, it may not be easy to understand which item the customer is referring to and could ...