User Tools

Site Tools


implementation:wms:cashregister_packing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

implementation:wms:cashregister_packing [2018/06/29 09:00] (current)
csuhaa created -18.2
Line 1: Line 1:
 +======9.5. Cash Register Packing======
 +The //Cash register packing// flow uses a pick list as an input. In this flow users can perform picking and packing in one step, therefore the input pick list does not have to be picked.
  
 +{{map> :​implementation:​wms:​functional:​cr_packing:​flowchart.png |}}
 +  * [[implementation:​wms:​cashregister_packing#​select_a_packing_location|Select packing line @162,​99,​314,​155]]
 +  * [[implementation:​wms:​cashregister_packing#​select_pick_list|Select pick list @162,​192,​314,​250]]
 +  * [[implementation:​wms:​cashregister_packing#​scan_barcode |Scan barcode @68,​287,​314,​683]]
 +  * [[implementation:​wms:​cashregister_packing#​add_items| @162,​683,​314,​777]]
 +  * [[implementation:​wms:​cashregister_packing#​finish_logistic_unit| @162,​777,​314,​870 ]]
 +{{<map}}
 +
 +=====9.5.1. Select a packing location=====
 +Select a packing line from the list. Every active packing line from the warehouses assigned to the [[implementation:​wms:​thinclient|thin client]] are listed.
 +
 +{{ :​implementation:​wms:​functional:​cr_packing:​packing_line.png?​500 |}}
 +
 +If there are already started logistic units on the packing line, the ‘Select a logistic unit to pack on’ screen is displayed. On this screen every packed logistic unit, which is not yet shipped, is listed. The customer name and address is displayed for each logistic unit. To continue packing onto a logistic unit, select the logistic unit and press the right key button. To start a new logistic unit, press the ‘Start new logistic unit’ button. ​
 +
 +=====9.5.2. Select pick list=====
 +On the next screen select a pick list. Every pick list that meets the following conditions is displayed:
 +  * The ‘Use for Cash register packing?’ option enabled for the [[implementation:​wms:​plty|pick list type]].
 +  * The status is ‘Not Ready’, ‘Partially Ready’, ‘Ready’,​ ‘Partially Picked’, ‘Picked’ or ‘Partially Packed’.
 +  * The pick list is assigned to the warehouse of the selected packing line.
 +
 +{{ :​implementation:​wms:​functional:​cr_packing:​pick_list.png?​500 |}}
 +
 +=====9.5.3. Scan barcode=====
 +On the next screen the items to pack are listed.
 +  * Product: The barcode, item code and description of the item to pack.
 +  * Batch number, Best before date: The batch number, the second batch number and the best before date of the allocated stock. The stock to be packed is allocated from pick locations based on the stock details available on the pick list and based on the FEFO rule. Only stock details that are available on the sales order are enforced.
 +  * Total: The open quantity on the pick list. Items with no open quantity are not listed.
 +  * Quantity to pack: The quantity to pack. If the //‘Force user to only scan items?’// option is enabled on the Packing controller, then the quantity to pack can only be added by scanning the barcode, otherwise the quantity can be adjusted with the + - buttons. ​
 +
 +{{ :​implementation:​wms:​functional:​cr_packing:​add_item.png?​500 |}}
 +
 +The following barcodes can be scanned on this screen:
 +  * EAN number of the item. 
 +  * GS1 128 barcode. It is possible to pack stock with different details than the allocated stock, except if the stock detail was set on the sales order. ​
 +  * Batch number. If the batch number belongs to multiple items, select the item to pack on the opening screen. (Batch with multiple BBD on stock?)
 +  * Serial number. If the serial number belongs to multiple items, select the item to pack on the opening screen. ​
 +  * SSCC number. In the case of a mixed pallet, select the item to pack on the opening screen.
 +
 +{{ :​implementation:​wms:​functional:​cr_packing:​product.png?​500 |}}
 +
 +Each scanned barcode increases the quantity by one if valid stock can be found. Over picking is not allowed.
 +
 +=====9.5.4. Add items=====
 +If there is at least one item where the ‘Quantity to pack’ is not zero, the ‘Add items’ button becomes active. Press this button to pack the ‘Quantity to pack’ amount of the selected items.
 +
 +If there is a stated logistic unit for the pick list, the system adds the packed items to that logistic unit. \\
 +If there is no stated logistic unit for the pick list, then the system checks whether there are started logistic units for the customer. If there are, then the user can continue the packing onto one of those logistic units or create a new one. If there are no started logistic units for the customer, the system automatically creates a new one. \\
 +The started logistic unit is displayed on the top right corner of the screen.
 +
 +If the item to add is managed by serial numbers and not all serial number were scanned, then the serial numbers has to be scanned before packing the item.  On the next screen indicate whether you would like to scan the serial numbers one by one or you would like to scan the starting and ending serial number only. For more information about adding the quantity by scanning the serial numbers please see: [[implementation:​wms:​typicalscreens#​screens_for_entering_additional_information|Screens for entering additional information]]
 +
 +=====9.5.5. Finish logistic unit=====
 +If there is at least one product packed onto the logistic unit, the ‘Finish logistic unit’ button becomes active. Press this button to finish the logistic unit. \\
 +If configured, the //Packing: finished logistic unit event (500)// print event is triggered and the SSCC label is printed. After finishing a logistic unit, the system displays the shipping dock where the logistic unit has to be moved.
 +
 +====9.5.5.1. Capture weight====
 +{{page>​implementation:​wms:​packing#​capture_weight&​noheader&​noeditbtn}}
 +
 +=====9.5.6. Skip items=====
 +{{page>​implementation:​wms:​packing#​skip_items&​noheader&​noeditbtn}}
implementation/wms/cashregister_packing.txt · Last modified: 2018/06/29 09:00 by csuhaa