ShipIT 365

Customizing the Tasklet Integration

 

In the Tasklet Integration app the supported flow is that Warehouse Shipments are posted from the Mobile Devices. In this flow the transport order will be created from the unposted warehouse shipment and the license plates from Tasklet will be attached to the new transport order.

However, some customers wanted a customized flow where the Warehouse Shipment is posted from BC, instead of the Mobile Device. This topic gives some suggestions on how this can be accomplished.

Before making any customization's we recommend you to consider to base the transport orders on posted documents. When the “Base Transport Orders on” field in the ShipIT Setup is set to posted documents, then the license plates are automatically transferred to the new transport order.
Since version 22.11.2786.0 this setting is supported in the Tasklet Integration.

If you, for whatever reason, need to work with transport orders that are based on unposted documents, then the following events and procedure calls can be used to support posting warehouse shipments from BC:

Create an event subscriber to OnAfterCreateTransportOrderFromWrkshLine in the "IDYS Document Mgt." Codeunit. In this procedure call the TransferLicensePlatesToTransportOrderPackages() procedure in the “IDYST ShippingProvider” Codeunit to transfer license plates that are scanned on the Mobile Device to the newly created Transport Order.

The CreatedOrders parameter of the event OnAfterCreateTransportOrderFromWrkshLine can be used to find the (single) Transport Order where the license plates should be attached to. In a Mobile WMS scenario there should always be one new created transport order for the warehouse shipment.

The OverrideShippingAgent parameter can be left blank.

The OnAfterCreateTransportOrderFromWrkshLine event also has a parameter that mentions the Warehouse Shipment No. that is being handled.

 

IDYN 2024