The three tables that you mentioned in the first post do not appear to have any FK relations to each other, so I would say the order should not matter.
items (stockmaster)
customers (debtorsmaster)
vendors (suppliers)
If you are getting FK complaints, then those are likely to other tables, and would need to know what the error message(s) say.
=====
Also, know that all but three tables in webERP use INNODB (the three that do not use INNODB do not have any FK relations), and this is what MySQL says about the INNODB engine type in the MySQL 5.7 TRUNCATE docs:
MySQL 5.7 docs Wrote:Logically, TRUNCATE TABLE is similar to a DELETE statement that deletes all rows, or a sequence of DROP TABLE and CREATE TABLE statements. To achieve high performance, it bypasses the DML method of deleting data. Thus, it cannot be rolled back, it does not cause ON DELETE triggers to fire, and it cannot be performed for InnoDB tables with parent-child foreign key relationships.
The 5.7 doc was
found here.
However, the TRUNCATE behavior in older MySQL docs differ, so if you have, say, MySQL 5.1:
MySQL 5.1 docs Wrote:For an InnoDB table, InnoDB processes TRUNCATE TABLE by deleting rows one by one if there are any FOREIGN KEY constraints that reference the table. If there are no FOREIGN KEY constraints, InnoDB performs fast truncation by dropping the original table and creating an empty one with the same definition, which is much faster than deleting rows one by one...
The 5.1 doc was
found here.
So, as Tim implied, YMMV as to how/what you'd like to accomplish. Based on the information differences here, what might have been possible in an "older version" may no longer be possible in a "newer version".