Modules:Advanced Warehouse Operations/ Deviations
Contents |
Deviations
In the context of AWO (Advanced Warehouse Operations) a Deviation is a process that happens within the generation of a Task to swap the initial Routing assigned to the Task being generated with a different one, based on the Warehouse definition.
The AWO engine generates Tasks based on the Warehouse Definition, the actual stock situation, and optionally a specific Document, like a Sales Order.
In order to generate a Task the engine follows this steps:
- Detect ITT. Based on the user action, the engine has to detect the Inventory Transaction Type (ITT) that needs to be used, e.g., when the user clicks on the Pick button of a Sales Order, the system detects that it has to use the Picking Sales Order ITT
- Search Routing. Based on the ITT detected, the engine reads the Warehouse Definition and looks for the Routing Assignment configuration. With this ITT, it searches for the Routing that is related to it
- Determine Routing. Finally, the engine has found which Routing it has to use and it can continue with the rest of the operations
With the Routing already determined, the engine can continue with the rest of the validations and operations. However, it is possible that at this moment, the engine detects that a Deviation has been defined for the selected Routing.
In this case the engine checks if it is possible to use the new Routing defined in the Deviation and, if so, it swaps the Routing with the one defined in the Deviation.
The rest of the validations and operations are done using the new Routing.
![]() | Note
All the Deviations implemented actually can be used in ITT's that use a Base Task Type of From-To and for which the From is already defined, e.g. a Put-Away of stock, in this case the stock is already selected This means that the actual deviations can only modify the destination Internal Routing Area by changing the Routing |
Deviation To Quality Inspection
The Deviation To Quality Inspection allows to automatically deviate goods to the Quality Inspection Area before placing them in the Storage Area.
This type of deviation is useful in cases in which there are Products that must be always reviewed before storing them, either because the Product itself is quite sensitive or in order to comply with local regulations.
To implement this scenario, it is necessary to define at least three different Internal Routing Areas:
- Reception. The Area to receive the goods and from which a Put-Away to Storage should be done
- Storage. The Area to store the goods
- Inspection. The Quality Inspection Area. This is where the deviation should move the goods instead of Storage in the Put-Away
Restrictions
There are several conditions that must be fulfilled to allow the AWO engine to successfully generate a Deviation To Quality Inspection:
- Put-Away. This Deviation can be defined only for Routings that use a Task Type with a Base Task Type of From-To. Additionally, this Deviation will only work with ITT's of the type Put-Away.
- Product Definition. The Product must be also defined as Deviation To Quality Inspection
- Full Quantity. In a Deviation To Quality Inspection, all the quantity of the Task will be deviated to the Inspection Area
Configuration
As explained above, it is necessary to have three different Internal Routing Areas, and a Routing to do the Put-Away from Reception to Storage Areas
Put-Away Routing Configuration
In the Routing for the Put-Away from Reception To Storage it is necessary to enable the flag for Deviation To quality Inspection
Deviation To Quality Inspection Routing Configuration
It is necessary to define a new Routing for Deviation To Quality Inspection that goes from Reception to Inspection Areas.
Also, a Routing Assignment that links with the new Routing is necessary. And finally the Warehouse Algorithm Assignments related to this ITT should be also defined (this ITT needs to find the destination Bin to place the stock, so only PA type algorithms will be shown)
Product Configuration
Finally, it is necessary to enable the Deviation To Quality Inspection flag for those Products that need to be deviated to Inspection. Only the ones flagged as such will be deviated, the rest will not.
Example
With the configuration in place, when a Put-Away is generated from Reception to Storage Area, if both the Routing and Product are flagged as Deviation To Quality Inspection, the Task generated will not be a Put-Away Task from Reception to Storage, but a Deviation To Quality Inspection Task from Reception To Inspection
Deviation To Cross Docking
![]() | This feature is available starting from 1.5.200. |
The Deviation To Cross Docking is a functionality of AWO that allows to optimize Warehouse Operations by deviating goods directly to the Shipping Area when there is an Order pending to be picked for the same day.
By directly moving the goods to the Shipping area is possible to bypass the operation of Putting-Away the goods into storage and then perform the picking operations, thus maximizing efficiency in the number of movements performed to prepare an Order.
This deviation only takes into account Orders (either Sales Orders or Distribution Orders that have a delivery date for the actual day)
To implement this scenario it is necessary to define at least three different Internal Routing Areas:
- Reception. The Area to receive the goods and from which a Put-Away to Storage should be done
- Storage. The Area to store the goods
- Shipping. The Area from which the goods will be delivered. This is where the deviation should move the goods instead of Storage in the Put-Away
Restrictions
There are several conditions that must be fulfilled to allow the AWO engine to successfully generate a Deviation To Cross Docking:
- Put-Away. This Deviation can be defined only for Routings that use a Task Type with a Base Task Type of From-To. Additionally, this Deviation will only work with ITT's of the type Put-Away.
- No Deviation To Quality Inspection. Deviation To Quality Inspection has priority over Deviation To Cross Docking. This means that if a Deviation To Quality Inspection is detected for a particular stock, the Deviation To Cross Docking will not be executed. However, it is possible to define both deviations for the same Routing, as it is possible to have Products defined to not be deviated to Inspection
- Pending Picking Quantity for Today. There should exist Order lines with quantity pending to be picked and that are scheduled to be delivered for the actual day. If not, no Deviation To Cross Docking will happen.
- Partial Quantity. In a Deviation To Cross Docking only the quantity pending to be picked will be deviated, the rest of the quantity will continue with the flow generated by the original Task
- Picking already done. Since the Deviation To Cross Docking simulates the Picking operation for the Order, the quantities that have been deviated by the Cross Docking Deviation are considered as picked, which means that is not necessary, and not possible, to pick this quantity again. Like with the Picking operations, the stock is reserved for the Order, to ensure that no other Order will take it unintentionally
Configuration
As explained above, it is necessary to have three different Internal Routing Areas, and a Routing to do the Put-Away from Reception to Storage Areas
Put-Away Routing Configuration
In the Routing for the Put-Away from Reception To Storage it is necessary to enable the flag for Deviation To Cross Docking
Deviation To Cross Docking Routing Configuration
It is necessary to define a new Routing for Deviation To Cross Docking that goes from Reception to Shipping Areas.
Also, a Routing Assignment that links with the new Routing is necessary. And finally the Warehouse Algorithm Assignments related to this ITT should be also defined (this ITT needs to find the destination Bin to place the stock, so only PA type algorithms will be shown)
Example
With the configuration in place, in an scenario is which there are 50 units of a particular stock in the Reception Area, and there is a Sales Order with 5 units pending to be picked and a scheduled delivery date for the actual day.
A Put-Away is generated for this stock. 5 Units are Deviated To Cross Docking for the pending Sales Order, 45 Units are Put-Away to Storage.