====== Ad Hoc Moves ======

=====Overview=====
Ad-hoc moves are used to move stock without a move order. The movement can be performed both in the office environment and on the shopfloor. 

===== Configuration =====

**Set the default warehouses** \\
Set default warehouses for the thin client. For more information about thin client settings click [[implementation:wms:thinclient|here]].

**Set the move controller** \\
Adjust the settings for the ad hoc moves in the move controller. For more information about the move controller click [[implementation:wms:movecontr|here]].

===== Ad-hoc movements in the office ===== 

Select stock line(s) from the [[implementation:wms:inventoryreport|Inventory Report]]. Click on the ’Move’ button and select the ’Perform move’ option from the dropdown menu.
 
{{ :implementation:functionalguide:moves:ah_office1.png |}}

{{ :implementation:functionalguide:moves:ah_office2.png |}}
 
On the ‘Perform Move’ window, select a destination location from the dropdown menu. Every active location of the company can be selected./ Both local moves and warehouse transfers can be performed. Add the quantity. By default the quantity is the quantity of the stock line. The entered quantity cannot exceed the quantity of the stock in the line. Press the ‘Execute’ button to perform the move.

Note: Only authorized users can perform ad-hoc moves in the office. For more information please see: [[implementation:wms:authorizations|Authorizations]]

For more information about moving beas reserved stock please see: [[implementation:addonmove|Performing Move with the Add-On with included WMS/Beas reservations]]

===== Ad-hoc movements on the shopfloor =====

====Workflow====

{{map> :implementation:functionalguide:moves:ah_flow.png |}}
  * [[implementation:wms:adhoc_moves#select_move_type| Select move type @336.5,88,383,116.5,336.5,145,290,116.5]]
  * [[implementation:wms:adhoc_moves#select_warehouse| Select warehouse @460,132,552,187]]
  * [[implementation:wms:adhoc_moves#select_move_task| Select move task @336.5,173,383,201.5,336.5,230,290,201.5]]
  * [[implementation:wms:adhoc_moves#full_logistic_unit| Full logistic unit @6,270,100,290]]
  * [[implementation:wms:adhoc_moves#scan_an_sscc| Scan an SSCC @6,305,101,360]]
  * [[implementation:wms:adhoc_moves#identify_destination_location| Identify destination location @6,380,101,435]]
  * [[implementation:wms:adhoc_moves#partial_logistic_unit| Partial logistic unit @195,270,290,290]]
  * [[implementation:wms:adhoc_moves#identify_source_location| Identify source location @195,305,290,360]]
  * [[implementation:wms:adhoc_moves#scan_an_sscc2| Scan an SSCC @195,380,290,435]]
  * [[implementation:wms:adhoc_moves#identify_product| Identify product @195,455,290,510]]
  * [[implementation:wms:adhoc_moves#enter_quantity| Enter quantity @195,530,290,585]]
  * [[implementation:wms:adhoc_moves#identify_destination_location_SSCC| Identify destination location/SSCC @195,607,290,662]]
  * [[implementation:wms:adhoc_moves#multiple_logistic_unit| Multiple logistic units @363,270,460,290]]
  * [[implementation:wms:adhoc_moves#scan_the_SSCC_s| Scan the SSCC’s@363,305,460,360]]
  * [[implementation:wms:adhoc_moves#scan_the_destination_location_or_GS1_label| Scan the destination location or GS1 label @363,380,460,435]]
  * [[implementation:wms:adhoc_moves#bulk_move| Bulk move @555,270,647,290]]
  * [[implementation:wms:adhoc_moves#identify_pick_location| Identify pick location @555,305,647,360]]
  * [[implementation:wms:adhoc_moves#identify_destination_location| Identify destination location @555,380,647,435]]
  * [[implementation:wms:adhoc_moves#enter_quantity| Enter quantity @555,455,647,510]]
{{<map}}

When there is only one or no default warehouse set for the thin client, only local moves are allowed. When there are more than one default warehouses set for the thin client, warehouse transfers can be executed as well between the default warehouses.

<WRAP round tip>In order to be able perform ad hoc moves into a non-Produmex managed warehouse, set up the warehouse in the following way:
  - On the Warehouse – Setup window set the ’Is managed by Produmex?’ user defined field to ’False’. 
  - On the Organizational Structure create a Warehouse type location for the given warehouse and select the SBO warehouse as the ’Warehouse’. 
  - Create a Dock type location under the warehouse and enable the ’Active’, ’Loading’ and ’Unloading’ checkboxes.

{{ :implementation:wms:functional:nonpmx_adhoc.png |}}

</WRAP>

====1. Initiate the flow====

To initiate the flow, follow the next path: Logistic > Move > Ad hoc movement

====2. Select move type====
  
Select the move type. To move stock within the warehouse, press ‘Local move’. To move stock between warehouses, press ‘Warehouse transfer’. 

====3. Select warehouse====

When executing a warehouse transfer, select the destination warehouse. //Only the default warehouses set for the thin client can be selected. //

{{ :implementation:functionalguide:moves:ah01.png |}}

====4. Select move task====

Select a move task. The following tasks can be selected:
  * [[implementation:wms:adhoc_moves#full_logistic_unit|‘Full logistic unit’]]: to move a full logistic unit
  * [[implementation:wms:adhoc_moves#partial_logistic_unit|‘Partial logistic unit’]]: to move a partial logistic unit
  * [[implementation:wms:adhoc_moves#multiple_logistic_units|‘Multiple logistic unit’]]: to move more than one logistic units
  * [[implementation:wms:adhoc_moves#bulk_move|‘Bulk move’]]: to move from a silo or a tank 
//Note: Bulk moves are only allowed during local moves. //

{{ :implementation:functionalguide:moves:ah02.png |}}

==== 5. Full logistic unit ====

===5.1. Scan an SSCC===

Scan the SSCC on the logistic unit to move. 

===5.2. Identify destination location===
Scan the destination location or select it from a list after pressing the ‘Select other location’ button. In case of a warehouse transfer, only locations from the selected warehouse can be scanned or selected. 

{{page>implementation:wms:defaultloc_calc&noheader}}

When the location suggestion is not enabled, an additional ‘Select empty location’ button will be displayed. To execute the move to an empty location, press this button and select a location from the list.

In case of a warehouse transfer, the //‘Warehouse: move has been added (701)’// print event will be triggered after the destination location had been selected, if the print event is defined.

Note: Assigning a logistic carrier to a Master SSCC is not supported. 

When moving Beas reserved stock, confirmation is required. See: [[implementation:wms:beas_integration#moving_stock_reserved_for_beas|Moving stock reserved for Beas]]

{{ :implementation:functionalguide:moves:ah_destloc.png |}}

===5.3. Logistic unit/ items are moved===
After scanning or selecting the new destination location, the ad-hoc movement is registered and the system displays the message: Logistic unit/Items are moved. The movement is booked as a ‘Move’ in case of local moves, or as a ‘Warehouse transfer’ in case of warehouse transfers.

==== 6. Partial logistic unit ====

To move a partial logistic unit, press the ’Partial logistic unit’ button.

===6.1. Identify source location===
Identify the pick location or select it from a list after pressing the ’Select location’ button.

{{ :implementation:functionalguide:moves:ah03.png |}}

===6.2. Scan an SSCC===
Scan the SSCC to move. Only SSCC’s linked to the selected location can be scanned.

{{ :implementation:functionalguide:moves:ahp_prod.png |}}

===6.3. Identify product===

If the ''No SSCC'' button is tapped, the system can move all the stock of the product regardless of whether or not the stock has an SSCC. If it has one or more SSCCs, the system chooses the SSCC to move. 

When there are more than one item on the logistic unit/SSCC, or the //Always scan product?// option is enabled on the [[implementation:wms:movecontr|Move controller]], the system will display a list of those items. Identify the item by scanning or selecting it from the list. When there is only one item on the logistic unit/pick location, the system will automatically proceed with that item.

When the item has more than one batch on that location, a list of batches will be displayed. Identify the product by selecting the batch. When there is only one batch, the system will automatically proceed with that batch.

When the selected stock is reserved in Beas, extra steps are required. See: [[implementation:wms:beas_integration#moving_stock_reserved_for_beas|Moving stock reserved for Beas]]

===6.4. Enter quantity===
Enter the quantity to move. For more information about adding the quantity in Produmex see: [[implementation:wms:infoscreen| 4.3.4. Screens for entering additional information ]]

===6.5. Identify destination location/SSCC===
To move the selected products to an existing SSCC, scan the SSCC. If the scanned SSCC is not in stock, identify the destination location on the next screen. The products will be moved to that logistic unit and location. Then the system will go back to the ‘Scan source location or GS1 label’ screen.

To create a new logistic unit, press the ‘New SSCC’ button then identify the destination location.

To move the selected products without changing the logistic unit, scan or select a location from a list. 

//When moving a partial pallet and the SSCC was not defined in this step (either by scanning an existing one or by creating a new one), then the products will be moved without a linked SSCC. //

Scan the destination location or select it from a list after pressing the ‘Select other location’ button. When the location suggestion option is not enabled to the warehouse, the system will display an additional ‘Select empty location’ button. To execute the move to an empty location, press this button and select a location from the list.

{{page>implementation:wms:defaultloc_calc&noheader}}

In case of a warehouse transfer, the //‘Warehouse: move has been added (701)’// print event will be triggered after the destination location had been selected, if the print event is defined.

In case of a new SSCC has been created, the //‘Warehouse: a new LU has been created (700)’// print event will be triggered after the destination location had been selected, if the print event is defined.

{{ :implementation:functionalguide:moves:ahp_dest.png |}}

===6.6. Logistic unit/ items are moved===
After scanning or selecting the destination location, the ad-hoc movement is registered and the system displays the message: Logistic unit/Items are moved. 

The movement is booked as ‘Move’ in case of local moves or as a ‘Warehouse transfer’ in case of warehouse transfers.

==== 7. Multiple logistic units ==== 
To move multiple logistic units at once, press the ’Multiple logistic units’ button.

===7.1. Scan the SSCC’s===
Scan the SSCC’s to move. The already scanned SSCC’s will be displayed in a list. After having all the SSCC’s to move scanned, proceed with the right arrow button.

{{ :implementation:functionalguide:moves:ahm_01.png?450 |}}

===7.2. Scan the destination location or GS1 label===
Scan the destination location or select it from a list after pressing the ’Select other location’ button.

To group the scanned SSCC into a master SSCC, press the ’Move to new master SSCC’ button then select the destination location.

{{page>implementation:wms:defaultloc_calc&noheader}}

When the location suggestion is not enabled, an additional ‘Select empty location’ button will be displayed. To execute the move to an empty location, press this button and select a location from the list.

In case of a warehouse transfer, the //Warehouse: move has been added (701)’// print event will be triggered after the destination location had been selected, if the print event is defined.

In case of a new master SSCC has been created, the //‘Warehouse: a new master LU has been created (702)’// print event will be triggered after the destination location had been selected, if the print event is defined.

When moving beas reserved stock, confirmation is required. See: [[implementation:wms:beas_integration#moving_stock_reserved_for_beas|Moving stock reserved for Beas]]

{{ :implementation:functionalguide:moves:ahm_dest.png?450 |}}

===7.3. Logistic unit/ items are moved===
After identifying the destination location, the ad-hoc movement is registered and the system displays the message: Logistic unit/Items are moved.

The movement is booked as ‘Move’ in case of local moves or as a ‘Warehouse transfer’ in case of warehouse transfers.

==== 8. Bulk move ==== 
The bulk move will take stock from a silo/tank and move it to another silo/tank. The stock to move will be calculated by the consumption algorithm defined on the silo/tank. 

{{ :implementation:functionalguide:moves:ahb.png?220 |}}

===8.1. Identify pick location===
Identify the source silo/tank by scanning or selecting it from a list after pressing the ’Select location’ button. 

{{ :implementation:functionalguide:moves:ahb_loc.png |}}

===8.2. Identify destination location===
Then identify the destination location. This location also should be a silo or a tank. Scan or select the location from a list after pressing the ’Select location’ button.

===8.3. Enter quantity===
After selecting the destination location, add the quantity to move. For more information about adding the quantity in Produmex see: [[implementation:wms:infoscreen| 4.3.4. Screens for entering additional information ]]

===8.4. Items are moved===
After pressing the right arrow button, the move will be booked.