===2.3.69. Sales Delivery Note Generator===

__Extension: Sales Delivery Note Generator - Generates Sales Delivery Notes in Separate Transactions__

This means that for instance when delivering a route, all deliveries are created in a separate transaction, instead of 1 transaction. \\
This will lead to less long lasting blocks when creating deliveries.

{{ :implementation:wms:ose:extensions:sales_delivery_note_generator.png |Sales Delivery Note Generator}}

<WRAP>//**General**//</WRAP>
**//Add quantity to non-inventory sales BOM item? (Y/N)//** \\
If enabled, the non-inventory components from a sales BOM are automatically added to the sales delivery when it is created through the Produmex functionality.

**//Copy text lines from order to delivery? (Y/N)//** \\
If set to true, text lines from the base document will be copied to the delivery.

**//Fill packing info in delivery? (Y/N)//** \\
If set to true, the packing info will be entered in the delivery. \\
This will be based on the SSCC/Master SSCC. \\
//(DLN7 & DLN8)//

**//Use Pmx sales shipping? (Y/N)//** \\
If set to true, it will book the delivery into a temporary table. The SAP sales delivery can be created through a tool, or manually in SAP.\\
The advantage of this setting is that the creation of the delivery is much faster. \\
The disadvantage is that the stock remains on the dock, pick list is still open until the SAP delivery is created. \\
Also when invoices need to be created immediately after the creation of the delivery, this setting cannot be enabled.

<WRAP>//**Grouping**//</WRAP>
**//Add grouping columns to header level? (Y/N)//** \\
Defines how data is queried for grouping. For backward compatibility the default value is ’True’.  If you have performance issues during the generation of sales delivery notes, disable this setting. 

If this setting is enabled, the //‘Grouping filter columns’// and the //‘Join clause for grouping filter’// fields are added in the main string:
<code>SELECT Table1.*, <Grouping filter columns> 
FROM (
SELECT …  
FROM …
) AS Table 1 
<Join clause for grouping filter> 
WHERE …
ORDER BY … ,<Order by for grouping filter></code>

If this setting is disabled, the //‘Grouping filter Columns’// and the //‘Join clause for grouping filter’// fields are added in a substring:
<code>SELECT Table1.* 
FROM (
SELECT … , <Grouping filter columns> 
FROM … 
<Join clause for grouping filter>
) AS Table 1 
WHERE …
ORDER BY … ,<Order by for grouping filter></code>

**//Group sales orders for the same customer to 1 delivery? (Y/N)//** \\
When the delivery is made, it is possible according to the type of shipping: wave/route/… that there are goods that come from different sales orders, for the same customer. \\
If the option is set to true, only 1 delivery will be made for those sales orders. \\
If set to false, a delivery by sales order will be made.

**//Grouping filter columns//** \\
Enter columns on which deliveries need to be grouped. \\
When columns are added, the deliveries that will be created will be split when values in these columns are different. \\
Multiple columns can be split by ','\\

**//Join clause for grouping filter//** \\
When the grouping filter columns are in a table that is not available in the standard query, a join clause can be added to join to the missing table(s). \\
This join clause will be fully added to the query, which means that the 'INNER JOIN', 'LEFT JOIN', ... keywords need to be added to this value.

{{:implementation:wms:wms_saldelge_grouping.png|}}

**//Example grouping filter//** \\
When splitting on discount percentage of the sales order: \\
Value for filter: "DiscPrcnt" \\
Value for join clause: INNER JOIN "ORDR" ON "ORDR"."DocEntry" = "GROUPED_TABLE"."SalesDocEntry"

**//Grouping Order by//** \\
Defines the sorting of the sales orders for the grouping. If this field is empty, the value of the //'Grouping filter columns'// is used for sorting.

<WRAP>//**Shipping**//</WRAP>

**//Allow loading of ready logistic units on not fully packed picklists? (Y/N)//** \\
If set to true, the users will be able to already select an unfinished picklist on the shipping client, and already start loading finished SSCC’s.

**//Allow shipping of partial LUID? (Y/N)//** \\
If set to true, on the shipping flow, a button will be available to only ship a part of a picked SSCC. The remainder will still be open on the pick list.

**//Allow to load all SSCC’s in one time? (Y/N)//** \\
If enabled, the user will be able to load all picked SSCC in one step during shipping without scanning the barcodes. 

**//Group similar picklists? (Y/N)//** \\
If set to true, during shipping the system will get all picklists that are available for the same customer, delivery address, … for the selected pick list. \\
All SSCC’s for those pick lists can to be loaded.