departure PhysObj come back

[petrus-v]

Thanks a lot making this useful library !

I'm not sure if those cases are already coverd. I can split in different issue but would give the big picture first.

We are selling pallet with goods (followed with serial number). Goods stay at the customer place once delivered and pallet came back to the warehouse and are reused.

As first implementation I've used the pallet as a container and I do use Move operation to move PhysObj on it. (at the moment I do not use the pack assembly operation to pack all goods together on the pallet).

I'm wondering what's the best approach:

I've first try to use a departure operation on the pallet, unfortunately:

• side note: PhysObj avatars locate on the pallet are still present in the system (so I loop as well on those PhysObj to make departure Operation on goods as well)
• As departure operation on the pallet the pallet has no present avatar. As far I understand I can't use Arrival/Apparition operation in AWB which create new PhysObj and do not test physobj code exists in the system.

What's would be the best approach ?

• create two new dedicated deposit operations (leave/back) ?
• Improve current operations (Arrival/Apparition) to test if physObj code already exist in the database and let developer/user to define (through behaviour on PhysObj.Type ?) if it should create a new physobj, reuse the same, or raise an exception
• create a customer location where pallet are moved until they came back while pannel use departure operation. So in that case when a pallet came back it would be a Move operation to a Stock location.

Regards,