Adhoc Transfers/Movements allow for devices to initiate Transfers/Movements from the mobile devices, without any pre-existing instruction existing. The rules for ad-hoc instructions also extend to Hybrid/Blind Instructions, which allow for ad-hoc instructions within the context of an instructed header.
Adhoc Transfers can only be initiated by a device.
To learn more about what makes up a Transfer, please look at Transfers
When an Adhoc instruction of any type is generated by the operator using the device, the inputs and values provided are validated and governed by basic rules, these may be extended by applying advanced customer-specific rules where required.
Before an ad-hoc instruction can be initiated, the operator/user requires the necessary user rights as configured for the Role they are assigned to. Without the necessary rights, the operator will not have access to the ADHOC function within TRANSFERS.
The allowed transfers are a finite set of Location/Bin combinations (FROM→TO), for which ad-hoc transfers are allowed. If the specific FROM/TO combination is not found in the Allowe Transfers List as configured by the Administrators, then the operator will not be able to continue/complete the ad-hoc transfer.
When the item is scanned/confirmed, and the user enters the required QTY, the validations will check stock availability to ensure that the movement can take place. The exception to this is for bins where the “allow negative” flag has been enabled.
In some cases where the Customer requires it, custom validation can be performed for ad-hoc transfers. These customisations will be documented and approved in the specification addendums, or change controls, and implemented as customisations in the database.