Manufacturers Erase
The action reports that a manufacturer is no longer kept in the ERP system. TRADElube then deletes the manufacturer assigned to that identifier.
What gets transferred
The ERP system sends nothing but the identifier. What happens afterwards is the same as deleting by hand: the articles are kept in full, their Manufacturer field is emptied, and TRADElube marks them as changed so that the old manufacturer name does not stay behind in the connected systems. In full under manufacturers.
Where no manufacturer 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.
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 Manufacturers.
Special features and limits
A returning manufacturer is a new one. Where the ERP system later reports the same manufacturer again through Manufacturers Update, a record with a new channel mapping is created, and the articles that referred to it before stay without a manufacturer: their link fell when it was deleted and is not restored.
Further reading
- CAO-Faktura: login details, configuration, mappings and the other eighteen actions
- Manufacturers Update: the route by which a manufacturer is created
- Manufacturers (reference): the detail view of a manufacturer, and what deleting takes along there
- Mappings and channel mappings (concepts): how TRADElube recognizes the record behind the reported identifier