User Tools

Site Tools


implementation:releasenotes:316

Differences

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

Link to this comparison view

implementation:releasenotes:316 [2015/08/12 12:36] (current)
Line 1: Line 1:
 +=====Version 3.16=====
  
 +====3.16.1.10====
 +
 +  * Reception: Added new batch number format generator.
 +  * Reception: Best before date calculation.
 +  * Picking for production flow: Sort items to pick based on sotring in the production order.
 +  * Reception flow: Skipping of certain screens is possible: Identical logistic units / Question to add more items to the logistic unit. The configuration is done on the business partner.
 +  * Reception flow: Proceed with reception after all data has been scanned from the GS1 label. Now the system takes in account whether the item has a batch number or best before date.
 +  * Print item labels: ​ Added possibility to enter batch number 2. The default item label report has been adjusted to pass the new data. The parameter is: @batchNumber2. **Custom made item labels and stored procedures need to be changed! ​ The stored procedure should have these parameters:​**
 +<​code>​
 +@itemCode nvarchar(20) = '',​
 + @batchNumber nvarchar(32) = '',​
 + @batchNumber2 nvarchar(32) = '',​
 + @serialNumber nvarchar(32) = '',​
 + @bestBeforeDate datetime = null,
 + @docType nvarchar(20) = null,
 + @docEntry int = null,
 + @lineNum int = null
 +</​code>​
 +  * A bulk shipping flow has been added. This allows to directly create a delivery from a silo/tank.
 +  * Sbo notification listener: Add possibility on the NewSalesCreatePickListProposal action to set whether to allow the creation of the proposal even if the doc total = 0.
 +To do this, on the config file you need to add a parameter ‘AllowZeroPrice’:​
 +<​code><​action senderType="​SboToPmx"​ objectType="​17"​ transactionType="​A"​ logic="​Produmex.Sbo.Logex.SboNotification.Actions.NewSalesCreatePickListProposal,​ Produmex.Sbo.Logex.SboNotification.Actions">​
 +<​parameter name="​AllowGrouping"​ value="​Y"/>​
 + <​parameter name="​AllowZeroPrice"​ value="​Y"/>​
 +</​action></​code>​
 +  * Added possibility to register time linked to a production order.
 +  * Picking: Showing the message ‘Items picked’ is now configurable on the PickListController:​
 +    - Negative value: Message is not shown
 +    - Zero: Message is shown, and user needs to click ‘OK’ to proceed.
 +    - Positive value: Message is shown that number of seconds. User can still click ‘OK’ to proceed
 +  * Packing: Showing pick/pack remarks in dedicated screen is configurable on the PickListController:​
 +    - Negative value: Message is not shown
 +    - Zero: Message is shown, and user needs to click ‘OK’ to proceed.
 +    - Positive value: Message is shown that number of seconds. User can still click ‘OK’ to proceed
 +  * Move to production line: It is possible to hide the ‘Move all’ buttons, forcing the user to move each item. This option can be set on the ProductionController.
 +  * Changing the internal batch number using the inventory screen. The original internal batch number is stored on the table. The changed internal batch number is for the complete batch (BatchID), and not only the selected line.
 +  * Print item labels: ​ Added possibility to enter a quantity and uom. The default item label report has been adjusted to pass the new data. The parameters are: @quantity and @uom. **Custom made item labels and stored procedures need to be changed! ​ The stored procedure should have these parameters:​**
 +<​code>​
 +@itemCode nvarchar(20) = '',​
 +@batchNumber nvarchar(32) = '',​
 +@batchNumber2 nvarchar(32) = '',​
 +@serialNumber nvarchar(32) = '',​
 +@bestBeforeDate datetime = null,
 +@docType nvarchar(20) = null,
 +@docEntry int = null,
 +@lineNum int = null,
 +@quantity numeric(19,​6) = null,
 +@uom nvarchar(20) = null
 +</​code>​
 +  * Sales return: Added batch number generator.
 +  * Shipping: Possibility to ship part of LUID. This option can be enabled on the SalesDeliveryNoteGenerator.\\
 +**IMPORTANT:​\\
 +To do this, the table PMX_DLPL has been extended to store a quantity that has been loaded. If there are custom queries made on this table (For instance for a report) the quantity should come from the PMX_DLPL.Quantity instead of PMX_MVLI.Quantity. For partially loaded LUID’s this will result in more than 1 row in the table PMX_DLPL.**
 +  * Enter LUID Data (Weight, length, width, height) when an LUID is full during picking/​packing. The configuration is done on the PickListType.
 +  * Open sales orders screen: Select the dock for the proposals to create.
 +  * Open sales order screen: Show orders that have no or partially created proposals.
 +  * Bugfixing
 +
 +====3.16.1.20====
 +
 +  * Supporting GS1 datamatrix barcode
 +  * Bugfixing
 +
 +====3.16.1.32====
 +
 +  * Bugfixing
 +
 +====3.16.1.36====
 +
 +  * Bugfixing
implementation/releasenotes/316.txt · Last modified: 2015/08/12 12:36 (external edit)