1. Contents
  2. Reference
  3. Channels and tasks
  4. CAO-Faktura
  5. Categories Erase

Categories Erase

The action reports that a category is no longer kept in the ERP system. TRADElube then deletes the category assigned to that identifier. It keeps the tree the same in both systems where CAO-Faktura maintains the categories.

What gets transferred

The ERP system sends nothing but the identifier. What happens afterwards is the same as deleting by hand: the subcategories go along, the products stay and merely lose their assignment to this category, and TRADElube marks them as changed so the connected systems learn about it. In full under categories.

Where no category is found for the identifier, the report is fine all the same. The ERP system gets the answer that there was nothing to delete, and traces carry an entry noting that it was skipped. That is the regular case where a category is deleted that never existed in TRADElube.

How the transfer plan is built

This action has no transfer plan. There is nothing to map, because all that arrives is the identifier of the record meant to disappear. So the channel's Transfer Plans section carries no Erase tab under Categories.

Special features and limits

The Root Category from the channel's configuration cannot be deleted. A call hitting it is answered with an error and carried in traces as Failed. It is the bracket around the transferred subtree, and the whole subtree would disappear with it at once.

There is no way back. A deleted category returns through Categories Update as a new category, not as the same one: it then has a new channel mapping, and the connected shops create it anew as well. So whoever maintains the tree in TRADElube rather than in the ERP system had better not set this action up at all.

Further reading