Branch Transfer Send and Receive

Branch Transfer (aka internal deliveries, warehouse runs, stocking deliveries) is a TrackAbout Delivery with Integrated Order Sync feature that lets you track assets being moved between internal locations using a branch transfer order and a handheld mobile device running TrackAbout Mobile 6 and TrackAbout Mobile 7.

The Branch Transfer Send and Branch Transfer Receive actions break the combined loading / delivery action in Branch Transfer into two distinct and separate actions – loading (sending) and delivery (receiving) – which can be run independently at the load point and the delivery point, independent of a truck or a particular driver.

With Branch Transfer Send, assets (scanned and non-scanned alike) are registered to a branch transfer order using TrackAbout Mobile 6 or 7, transported, then registered as delivered when they arrive at their destination.

Branch Transfer Send and Branch Transfer Receive give you flexibility Branch Transfer does not. Since all scans happen at the docks on either end, drivers no longer need a handheld or company vehicle for branch transfers. Using Branch Transfer Send and Branch Transfer Receive also cuts down on the number of scan points throughout the transfer process, increasing efficiency – even more if you’re using Automatic Receiving.

What is Automatic Receiving?

Normally, each asset and hard good included in a branch transfer to a location must be scanned during a Branch Transfer Receive. Automatic Receiving lets you designate a location as trusted, meaning branch transfers to that location do not require each asset or hard good be scanned during Branch Transfer Receive. Automatic Receiving can be enabled by TrackAbout Support.

Options

Several configuration options are available with Branch Transfer Send and Branch Transfer Receive. These options can be configured by TrackAbout support.

Allow Sorting more items than are on the trip: EnableLoadingMoreThanOrderedOnSortTrip; When enabled, users will be able to sort more items onto a Sort Trip or Branch Transfer Send action than are on the orders making up the trip. When disabled, the device will limit the user to just what is on the orders for the trip. Users can always sort containers onto a trip, regardless of the setting.
Billing Code required for Line Items?: IsOwnerFlagRequiredForLineItems; If set to True, a Billing Code must be associated with each Line Item of an Order.
Use Billing Code for Matching Delivered Assets: UseOwnerFlagForMatchingDeliveredAssets; When set to True, the Billing Code of the delivered assets will be taken into account while matching assets to Line Items during paperless delivery. If set to False, the Billing Code will be used only for matching returned assets.
Enable Difference Reason Codes: EnableDifferenceReasonCodes; When enabled, this feature will require users of paperless delivery on TrackAbout Mobile 6 and TrackAbout Mobile 7 (iOS and Android) to specify a "reason code" for each mismatched line item during a delivery. The list of available reason codes will be pre-defined and maintained on a page on the AWS.
Order Item with 0 Deliver Quantity Considered Matching: OrderItemWithNoDeliverQuantityConsideredMat; If set to True, an Order Item with a Deliver Quantity of 0 will be considered as matching for Deliver Quantities in TrackAbout Mobile even when the actual Delivered Quantity is greater than 0. This also applies to cases where an Order Item entered in TrackAbout Mobile is not present in the original Order imported from the Accounting system.