Warehouse policies
Warehouse policies is a hierarchical system for applying policies to warehouse operations.
Policy kind
Warehouse policies have diferent kinds/types which specify what the actual action of the policy is.
The list of the policy kinds is system predifined.
| Type | Description |
|---|---|
| AllowProductChange | Allows execution with а different product than the ordered. If ApplicablePolicy = null or ApplicablePolicy.Value == false and WarehouseOrderLine.Product != null, then when executing in Orders, it’s not possible to define Product != WarehouseOrderLine.Product. If another value is defined, an error sound will play, along with the appearance of a popup message: “Product change is not allowed. Please select the suggested product.” • Stored as 'APC'. • Database Value: 'APC' • Model Value: 0 • Domain API Value: 'AllowProductChange' |
| AllowLotChange | Allows execution with a different lot than the ordered. If Value == false and WarehouseOrderLine.Lot != null, then when executing in Orders, it’s not possible to define product Lot !=WarehouseOrderLine.Lot. <If another value is defined, an error sound is played, along with the appearance of a popup message: “Lot change is not allowed. Please select the suggested lot.” • Stored as 'ATC'. • Database Value: 'ATC' • Model Value: 1 • Domain API Value: 'AllowLotChange' |
| AllowLocationChange | Allows execution from a different location than the ordered. If Value == false and WarehouseOrderLine.Location != null, then when executing in Orders, it’s not possible to define product Location != WarehouseOrderLine.Location. If another value is defined, an error sound is played, along with the appearance of a popup message: "Location change is not allowed. Please select the suggested location." • Stored as 'ALC'. • Database Value: 'ALC' • Model Value: 2 • Domain API Value: 'AllowLocationChange' |
| AllowUnitChange | Allows execution of a quantity in a different measurement unit than the ordered. If Value == false and WarehouseOrderLine.QuantityUnit != null, then when executing in Orders, it’s not possible to define product QuantityUnit != WarehouseOrderLine.QuantityUnit. If another value is defined, an error sound is played, along with the appearance of a popup message: "Quantity Unit change is not allowed. Please select the suggested quantity unit." • Stored as 'AUC'. • Database Value: 'AUC' • Model Value: 3 • Domain API Value: 'AllowUnitChange' |
| RequireSourceScan | Requires scanning of the source location when moving or dispatching. If Value == true, then when executing in Orders, the USE button in the Location screen will be hidden, while the Availability table will be inaccessible. • Stored as 'RSS'. • Database Value: 'RSS' • Model Value: 4 • Domain API Value: 'RequireSourceScan' |
| RequireDestinationScan | Requires scanning of the destination location when moving or receiving. If Value == true, then when executing in Orders, the USE button in the Destination screen will be hidden. • Stored as 'RDS'. • Database Value: 'RDS' • Model Value: 5 • Domain API Value: 'RequireDestinationScan' |
| AllowLineSkip | Allows skipping of an order line when executing (allow quantity = 0). Not planned for release at the moment. • Stored as 'ALS'. • Database Value: 'ALS' • Model Value: 6 • Domain API Value: 'AllowLineSkip' |
| ZoneType | Specifies the type of zone for receiving, shipping, packing, etc. It can have the following values: picking, packing, receiving, shipping, and storage. According to the Zone Policies rule, the policy has a "Zone" and there are no “Product”, “Product group” or “Product type” fields. • Stored as 'ZTY'. • Database Value: 'ZTY' • Model Value: 7 • Domain API Value: 'ZoneType' |
Applicability
You set up each warehouse policy by defining the conditions where it applies, to which products and for how long. Each warehouse policy can apply to:
Warehouse
Zone and its sub-zones
Product group and its sub-groups
Product type
Specific product
From date
To date
NOTE: Some policies can be applied only at the warehouse or zone level.
Importance
Policies have importance. When evaluating a policy, the setting with the highest importance is applied.
For example, if a policy is applied to a root zone and to a sub-zone, the importance of the sub-zone setting determines which setting will be applied:
- If the sub-zone setting has higher priority, it will be applied.
This can be used for hierarchical application of policies for zones.
- If the root zone setting has higher priority, it will be applied.
This can be used for root zone (or even warehouse level) setting, which overrides the setting for specific zones.
Importance is an integer value, allowing even negative numbers (for very low importance).