=====25.2. Shipping flow=====
{{map> :implementation:wms:functional:shipping:00shipping_flow.png |}}
  * [[implementation:wms:shipping#select_dock|Select dock @205,80,295,115]]
  * [[implementation:wms:shipping#select_the_input_type|Select input type @5,145,495,270]]
  * [[implementation:wms:shipping#identify_and_load_the_logistic_units|Identify logistic unit @200,305,300,505]]
  * [[implementation:wms:shipping#shipping1|Shipping @77,850,300,890]]
  * [[implementation:wms:shipping#extra_steps|Extra steps @200,550,300,815]]
{{<map}}
====25.2.1. Initiate flow====
To start the process, press the ‘Shipping’ button from the Sales menu on the handheld terminal. 

====25.2.2. Select dock====
On the next screen select the dock where the loading will take place. Every [[implementation:wms:docksettings|dock]] that can be used for loading is listed.

====25.2.3. Select the input type====
After the selection of the loading dock, select the input of the loading and shipping:
  - **Route**: Loading and shipping based on a route. Multiple pick lists for various customers and addresses can be consolidated into a route. The loading order is defined by the route sequence.
  - **Pick list**: Loading and shipping based on a single pick list. A pick list can be generated for one or more sales order for the same customer. 
  - **Wave**: Loading and shipping based on a wave of pick lists. A pick list wave can contain multiple pick lists for various customers. 
  - **Customer**: Loading and shipping multiple pick lists for a single customer. 

====25.2.4. Identify and load the logistic units====
===25.2.4.1. Shipping based on a route===
**Select a route** \\
Select the route from the list. Routes that verify the following criteria are listed:
  * The status of the route is ‘Released’
  * The status of the pick lists on the route is ‘Packed’
  * If the //‘Allow loading of ready logistic units on not fully packed pick lists?’// option is set to true on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], a route is listed if there is at least one logistic unit packed for a pick list on the route.
  * The route is assigned to the selected dock

The following information is displayed on the screen:
  - Route date
  - Route number
  - Route description (Template code)

{{ :implementation:wms:functional:shipping:01selectroute.png?200 |}}

**Scan SSCC** \\
On the next screen every logistic unit that has been packed for the route, but is not yet loaded, is listed. Produmex WMS orders the logistic units in the reverse order of delivery. The SSCC’s are sorted by the following:
  * Route sequence number of the pick list (descending)
  * LUID (descending)

{{ :implementation:wms:functional:shipping:02routesequence.png |}}

It is possible to load the logistic units in a different order, but a warning will appear on the screen. Press the ‘Yes’ button to load the scanned logistic unit anyway. 
{{ :implementation:wms:functional:shipping:03scanssccroute.png?400 |}}

When shipping based on a route, it is not possible to skip logistic units from the shipping. It is also not possible to ship a partial LUID regardless of the //‘Allow shipping of partial LUID? (Y/N)’// setting on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]].

<WRAP round box>If the ‘Allow to load all SSCC’s in one time? (Y/N)’ option is enabled on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], an additional ‘Load all SSCC’s’ button is displayed on the screen as long as no SSCC is loaded for the selected route. Press this button to load every SSCC that is listed on the screen without scanning the barcodes. After the user acknowledges the ‘The sscc has been loaded.’ message, the system proceeds to the [[implementation:wms:shippingflow#shipping|Shipping step]].</WRAP>

===25.2.4.2. Shipping based on a pick list===
**Select pick list** \\
Select the pick list from the list. Pick lists verifying the following criteria are listed:
  * The pick list is not on a route. 
  * The pick list is on the selected dock.
  * The pick list status is ‘Packed’ or ‘Partially Delivered’ 
  * If the //‘Allow loading of ready logistic units on not fully packed picklists?’// option is set to true on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], a pick list will be listed if there is at least one logistic unit packed for it. 

<WRAP round box>The pick list status will not be ‘Packed’ or ‘Partially Delivered’ in the following scenarios:
  * The ‘Automatic shipping’ option is enabled for the shipping type
  * The ‘Customer collect’ option is enabled for the shipping type
  * The ‘Use for Production?’ option is enabled for the Produmex Pick list type of the pick list
</WRAP>
  
On the screen the following information is displayed:
  - [Shipping ID] 
  - Pick list number 
  - Customer name - address

{{ :implementation:wms:functional:shipping:04selectpl.png?200 |}}

**Scan the SSCC** \\
On the next screen logistic units that verify the following criteria are listed:
  * was picked for the selected pick list
  * are ready for shipping
  * not yet loaded

If the //‘Group similar picklists? (Y/N)’// option is enabled on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], the system will also list the logistic units packed for other pick lists that were generated for the same customer and delivery address. All those SSCC’s can be loaded as well.

Scan the SSCC to load the logistic unit. When shipping based on a pick list, the loading sequence is not determined. Acknowledge the “The sscc has been loaded” message by pressing the ‘OK’ button.

<WRAP round box>If the //‘Allow to load all SSCC’s in one time? (Y/N)’// option is enabled on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], an additional ‘Load all SSCC’s’ button is displayed on the screen as long as no SSCC is loaded for the selected pick list, customer address or wave.

Press this button to load every SSCC that is listed on the screen without scanning the barcodes. After the user acknowledges the ‘The sscc has been loaded.’ message, the system proceeds to the [[implementation:wms:shippingflow#shipping|Shipping step]].</WRAP>

{{ :implementation:wms:functional:shipping:pl_scan_sscc.png?600 |}}

Then scan the next SSCC on the list until every logistic unit is loaded.

When there are SSCC’s that cannot be loaded, press the ‘Ship loaded SSCC’s’ button. After the button has been pressed, the loaded logistic units will be shipped while the remaining SSCC’s will be skipped. On the next screen the user must select a reason why the full quantity has not been shipped. Every [[implementation:wms:reasons|reason]] that can be used for shipping can be selected.
{{ :implementation:wms:functional:shipping:06scannext.png?400 |}}

If the //‘Allow loading of ready logistic units on not fully packed picklists?’// option is enabled on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], an additional ‘Load partial SSCC’ button is displayed on the screen.
{{ :implementation:wms:functional:shipping:07loadpartial.png?400 |}}

Press this button to load an SSCC partially. On the next screen scan the SSCC. 

Every SSCC that was picked for the selected pick list, are ready for the shipping but not yet loaded are listed on the screen and can be scanned.
{{ :implementation:wms:functional:shipping:08scanloadpartial.png?200 |}}

On the next screen select the item to load. Every item on the scanned SSCC is listed. Products with different batch number or best before date will be listed on separate lines.

Displayed information:
  - Loading dock
  - Available quantity
  - Item description
  - SSCC number
  - Batch number
  - Best before date

{{ :implementation:wms:functional:shipping:09selectitemload.png?200 |}}

Then enter the number of items to load. The quantity to load cannot exceed the quantity on the logistic unit. For more information about entering the quantity in Produmex WMS please see: [[implementation:wms:infoscreen|Screens for entering additional information]].

After the quantity is added the partial SSCC is loaded. Press the ‘OK’ button to acknowledge the message.

{{ :implementation:wms:functional:shipping:10partialloaded.png?200 |}}

===25.2.4.3. Shipping based on a wave===
**Select the wave** \\
Scan the wave or select it from the list.

Every wave that contains at least one pick list that verifies the following criteria are listed:
  * the status of the pick lists in the wave is ‘Packed’ or ‘Partially Delivered’
  * there is at least one pick list that is not on a route
  * there is at least one pick list that is on the selected dock

If the wave contains pick lists for various customers:\\
<wrap indent>1. Wave number</wrap> \\
<wrap indent>2. [Shipping ID] Pick list number, for each pick list in the wave</wrap>

If the wave contains only pick lists for the same customer and ship to address: \\
<wrap indent>3. Card code- Customer name – Shipping address</wrap>

{{ :implementation:wms:functional:shipping:11selectwave.png?200 |}}

**Scan SSCC** \\
On the next screen logistic units that verify the following criteria are listed:
  * was packed for a pick list from the wave
  * are ready for shipping
  * not yet loaded
For more information about the loading process please see: [[implementation:wms:shippingflow#shipping_based_on_a_pick_list|Shipping based on a pick list]]

===25.2.4.4. Shipping based on a Customer===
**Select a customer** \\
Select a customer from the list. Only customers that have a packed SSCC that is not on a route is listed. Customers with different shipping address are listed on a separate line.

Displayed information on the screen:
  - Customer code - Customer name 
  - Shipping address

{{ :implementation:wms:functional:shipping:12selectcustomer.png?200 |}}

**Scan SSCC** \\
On the next screen logistic units that verify the following criteria are listed:
  * was packed for the selected customer and address
  * are ready for shipping
  * not yet loaded
For more information about the loading process please see: [[implementation:wms:shippingflow#shipping_based_on_a_pick_list|Shipping based on a pick list]]

====25.2.5. Shipping====

After every SSCC is loaded or the user pressed the ''Ship loaded SSCCs'' button, the logistic units are shipped and the delivery document is created.

Note: 
  * Items with different description on the sales order, even if using the same itemcode, are not consolidated on the delivery document.
  * When the invoices are generated automatically via the Mobile Client, the down payment request information is not being pulled through.
  * When shipping multiple SSCCs of a customer with different shipping addresses, the system changes the address to the default address of the customer in the delivery note.

<WRAP round box>
Multiple sales deliveries can be created for a single sales order in the following scenarios:
  * Multiple pick lists have been generated and the //‘Group similar picklists?’// option is not set to true on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]]. Otherwise pick list for the same customer and delivery address will be grouped during the shipping.
  * Multiple pick lists have been generated and the picklists are picked/packed/shipped separately on different times.
Multiple sales deliveries can be created for a single pick list in the following scenario:
  * There are multiple sales orders on the pick list and the //‘Group sales orders for the same customer to 1 delivery?’// option is not enabled on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]].
A single sales delivery can be created for multiple sales orders with the same customer and delivery address in the following scenarios:
  * The //‘Group sales orders for the same customer to 1 delivery?’// option is enabled on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]] and the sales orders are shipped at the same time.
  * During the picking the pick lists were picked onto the same SSCC.
</WRAP>

{{ :implementation:wms:functional:shipping:13adddelivery.png?200 |}}

If the //‘Use Pmx sales shipping?’// option is set to true on the [[implementation:wms:salesdeliverynotegen|Sales delivery note generator]], instead of an SBO sales delivery note, a PMX sales shipping note will be created. The pick list(s) will remain open and the stock will remain on the dock until the SBO delivery note is created.

<WRAP round info>
In order to create an SBO delivery note from a PMX sales shipping note, go to the Open Documents Report from the Produmex module in SAP Business One and select ‘PMX Sales Shipping’ as the document type. Select the document(s) then click on the ‘Create sales delivery’ button to create the SBO delivery note.
</WRAP>


If the //’Fill packing info in delivery? (Y/N)’// option is enabled on the [[implementation:wms:salesdeliverynotegen|Sales Delivery Note Generator]], the master SSCC and the SSCC number is added to the Packing Slip when the delivery note is created. 
The Package No. is  the LUID of the (sub)logistic unit. 

{{ :implementation:wms:functional:shipping:packingslip.png |}}
====25.2.6. Print document====
When an SBO delivery note is created, the //‘Shipping: Sales delivery note created event (300)’// print event is triggered. \\
When a PMX sales shipping note is created, the //‘Shipping: PMX sales shipping created event (303)’// print event is triggered. \\
The default reports for both print events are:
  * DefaultSalesDeliveryBySSCC.rpt
  * DefaultSalesDeliveryBySalesOrder.rpt

When shipping based on a pick list/wave/customer, the //‘Shipping: Picklist shipped event (302)’// print event is also triggered and the pick list is printed. 

When shipping based on a route, the //‘Shipping: Route shipped event (301)’// print event is also triggered and the Route Document is printed. The default report for the print event is the DefaultRouteDocument.rpt.

====25.2.7. Extra steps====
Based on the shipping type and the General settings configurations, the user might have to take the following steps before creating the delivery document: **Shipping configurations**

===25.2.7.1. Select a license plate===
Select the license plate from the list. Every license plate defined in the [[implementation:wms:lipl|License plate (PMX_LIPL)]] user table can be selected. It is also possible to enter a license plate that is not defined in the user table. \\
{{ :implementation:wms:functional:shipping:14licensepfc.png?200 |}}

The license plate will be added to the ’The license plate’ UDF on the sales delivery document and the A/R invoice.
{{ :implementation:wms:functional:shipping:14licensepd.png?500 |}}

===25.2.7.2. Select a driver===
Select the driver from the list. Every driver defined in the [[implementation:wms:driv|Drivers (PMX_DRIV)]] user table can be selected. It is also possible to enter a driver who is not defined in the user table. \\
{{ :implementation:wms:functional:shipping:15driverfc.png?200 |}}

The driver name will be added to the ’The name of the driver’ UDF on the sales delivery document and the A/R invoice.
{{ :implementation:wms:functional:shipping:15driverd.png?500 |}}

===25.2.7.3. Select a trailer number===
Select the trailer number from the list. Every trailer number defined in the [[implementation:wms:trnr|List of selectable trailer numbers (PMX_TRNR)]] user table can be selected. It is also possible to enter a trailer number that is not defined in the user table.
{{ :implementation:wms:functional:shipping:16trailernfc.png?200 |}}

The trailer number will be added to the ’The trailer number’ UDF on the sales delivery document and the A/R invoice.
{{ :implementation:wms:functional:shipping:16trailerd.png?500 |}}

===25.2.7.4. Enter a tracking number===
Enter the tracking number. 
{{ :implementation:wms:functional:shipping:17trackingnbr.png?200 |}}