======Cross-Docking Flow====== =====Overview===== In the cross-docking process goods are immediately delivered to the customer after the reception based on the sales order linked to the purchase order. If the received stock is insufficient, a pick list will be generated in order to meet the required quantities from the sales order. To have a distinction between pick lists that are created for cross-docking, a cross-docking picklist type can be provided on the [[implementation:wms:purchasedeliverygen|purchase delivery generator]]. =====Configuration===== In order to automatically create the sales delivery note, enable the //Auto reserve stock when purchase order is linked to sales order?// option on the [[implementation:wms:purchasedeliverygen|purchase delivery generator]]. Otherwise the received stock will not be locked and a pick list will be created for the total quantity in the sales order in the end of the reception. =====Workflow===== {{map> :implementation:wms:functional:purchase:cross-dock_flowchart.png |}} * [[implementation:wms:cross_docking#select_a_location|Select location @ 30,90,167,145]] * [[implementation:wms:cross_docking#select_a_po|Select purchase order @ 30,172,167,230]] * [[implementation:wms:cross_docking#select_a_task|Select task @ 30,250,290,400]] * [[implementation:wms:cross_docking#scan_barcodes|Scan barcodes @ 30,450,167,505]] * [[implementation:wms:cross_docking#logistic_carrier|Select logistic carrier @ 30,530,167,590]] * [[implementation:wms:cross_docking#identify_item|Identify item @ 30,615,167,672]] * [[implementation:wms:cross_docking#add_the_number_of_items|Enter quantity @ 30,700,167,757]] * [[implementation:wms:cross_docking#add_more_products|Add more products @ 30,789,167,880]] * [[implementation:wms:cross_docking#continue_reception|Continue reception @ 175,789,225,880]] * [[implementation:wms:cross_docking#finish_reception|Add more products @ 30,890,535,1320]] {{implementation:wms:reception_flow#select_task_identical_no_identical_logistic_units&noheader&noeditbtn}} ====5. Scan barcodes==== {{page>implementation:wms:reception_flow#scan_barcodes_gs1_label&noheader&noeditbtn}} ====6. Logistic carrier ==== {{page>implementation:wms:reception_flow#select_a_logistic_carrier&noheader&noeditbtn}} ====7. Identify item==== If there were no product barcode on the scanned label or no label has been scanned, the operator is asked to scan or select a product. only items matching the following criteria can be scanned or selected: * The purchase order/container contains the item with open quantity. * The item is not registered for reception in the ASN table with the total open quantity for the given purchase order/container. If the //‘Check data in UDF’s from PO line’// option is enabled on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]], purchase order lines are listed separately on the screen. {{ :implementation:wms:functional:purchase:reception_select_product.png?400 |}} If the item has a zone type specified on the [[implementation:wms:imdtab|Inventory tab]] of the Item Master Data, and the receiving dock is not located in a zone matching with the zone type of the item, an error message will open. Acknowledge the message by pressing the ‘Ok’ button. The system will return to the //Scan a product// screen. {{ :implementation:wms:functional:purchase:cross_zone.png?200 |}} ===7.1. Identify batch number=== {{page>implementation:wms:reception_flow#identify_batch_number&noheader&noeditbtn}} ===7.2. Specify the best before date=== {{page>implementation:wms:reception_flow#specify_the_best_before_date&noheader&noeditbtn}} ===7.3. Specify additional information=== {{page>implementation:wms:reception_flow#specify_additional_information&noheader&noeditbtn}} ====8. Add the number of items==== On the next screen add the number of items on the logistic unit. For more information about adding the quantity on the thin client please see: [[implementation:wms:infoscreen|Screens for entering additional information]]. //Please note: On this screen the number of items on a single logistic unit can be added. If there are identical logistic units, do not add the total quantity of all logistic units. // By default the following quantity is displayed: * The //Default quantity on logistical unit// set on the [[implementation:wms:imdtab|Produmex Inventory tab]] of the Item Master Data * If there is no default quantity set, then the quantity on the purchase order line The maximum limit for the quantity to receive is the open quantity in the order unless the //‘Allow to exceed ordered quantity?’// option is enabled on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]]. The ‘Still to receive’ quantity depends on whether there are identical logistic units or not. * If there are no identical logistic units, the ‘Still to receive’ quantity is the open quantity on the purchase order. * If there are identical logistic units, the ‘Still to receive’ quantity is the open quantity on the purchase order divided by the number of identical logistic units (rounded down). If the purchase order is linked to a sales order, an additional info icon is displayed on the screen. Press this icon to see the customer card code, name and the sales order number. To see the customer and the sales order number, press the information icon. The customer name (Card Code) – sales order number will be displayed on the screen. {{ :implementation:wms:functional:purchase:cross_quantity.png?200 |}} ====9. Add more products==== On the next screen verify whether there are remaining products on the logistic unit or not. The system automatically skips this screen if the [[implementation:wms:businesspartner|‘Never deliver mixed logistic unit’ option]] is set to true for the vendor. To add the next item, press the ‘Yes’ button. To finish the logistic unit, press the ‘No’ button. The system will register the logistic unit. If there were no logistic label, the system will create one. The //‘Reception: new logistic unit identified event (101)’// print event will be triggered and the system will print the logistic label. The default report for the print event is: //DefaultGoodsReceiptLabel.rpt//. If the //‘Split received quantity into logistic units of default size’// option is enabled on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]], and the item has a //‘Default quantity on logistical unit’// set on the [[implementation:wms:imdtab|Produmex Inventory tab]] of the Item Master Data, the received quantity will be split to multiple logistic units based on the default quantity. An individual logistic label will be generated for each logistic unit, but only one Goods Receipt PO document will be created for the item. If the //‘Ask user to print labels?’// option is set to true on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]], the system will ask whether to print the logistic label. Press a button accordingly. {{ :implementation:wms:functional:purchase:reception_next_lu.png?600 |}} ===9.1. Continue reception=== If there are more open items on the purchase order, the system will show the ‘Enter the data for the next logistic unit’ message. Acknowledge the message by pressing the ‘Ok’ button. The system will proceed to the [[implementation:wms:cross_docking#scan_barcodes|‘Scan barcodes GS1 label’ screen]]. ===9.2. Finish reception=== If the //‘Receive all items in one purchase delivery?’// option is not enabled on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]], the system automatically generates the Goods Receipt PO document after the logistic unit is completed. Otherwise the Goods Receipt document is only created after the total quantity of the purchase order/container has been received. The //‘Reception: purchase delivery note created event (100)’// print event is triggered and the system prints the document. After the total ordered quantity is received, and the delivery note has been added in SAP B1, a //Processing cross-docking operation…// message is displayed on the screen. {{ :implementation:wms:functional:purchase:cross_process.png?200 |}} * If the ’Allow to exceed ordered quantity? option is enabled on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]], it is possible to receive more than the ordered quantity. The delivered quantity will be equal to the received quantity. * If every item on the sales order has a linked purchase order, the items will be automatically shipped after the reception has been completed. In SAP B1 the purchase and the delivery document is added and the sales and the purchase order is closed. The system will return to the ‘Select a PO’ screen. \\ //Please note: When using the PMX sales delivery, the sales order is only closed after the PMX delivery is processed.// * If not every item on the sales order has a linked purchase order, a pick list proposal and a picklist will be created for the items without a linked purchase order after the reception has been completed. The type of the generated pick list(s) is the pick list type defined as the ‘Cross-docking pick list type’ on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]]. The system will automatically proceed to the [[implementation:wms:picking|Picking flow]]. \\ //Please note: If there is no free stock, the pick list proposal is not created.// * If the //’Auto reserve stock when purchase order is linked to sales order?’// option is not enabled on the [[implementation:wms:purchasedeliverygen|Purchase delivery generator]], the stock is not locked during the reception. After the reception is completed, a cross-docking type picklist will be generated and the system will automatically proceed to the [[implementation:wms:picking|Picking flow]]. ====10. Go back==== ===10.1. Items on the logistic unit=== {{page>implementation:wms:reception_flow#items_on_the_logistic_unit&noheader&noeditbtn}} ===10.2. Goods receipt not booked yet === {{page>implementation:wms:reception_flow#goods_receipt_not_yet_booked&noheader&noeditbtn}}