-
Warehouse labels to be printed in normal laser printers
There should be the option to select if you want to printer warehouse labels in ZPL printers or in normal laser printers.
With the current design, only ZPL files are generated.
-
It should be possible to run cost calculation for Co-products
A planning item contains 2 co-products. TCA is used. Items are standard cost. In order to estimate the cost , both co-products must have an activated cost.
Customer would like to run cost calculation in order to get the standard cost automatically created based on the purchase price + surcharges that are set up in the costing sheet. (Since these products are also bought sometimes)
Currently the cost calculation process excludes co-products and it's not possible to use this functionality.
-
Wrong unit taken for CW items for transfer receipt in \Classes\InventCostItemDim\updateModelAverage()
In \Classes\InventCostItemDim\updateModelAverage(), there is a line code where it's set, line 195: pdsCWReceiptScanQty = this.financialOpenQty(transferReceipt); This is wrong as it's refering to the Primary item unit and not of the secondary (CW) item unit. It should be: pdsCWReceiptScanQty = this.pdsCWFinancialOpenQty(transferReceipt); This caused an inventory closing error saying: ‘Product A100800. Available physical Site PWA Impossible to take the PV of 378,535.00 as only 63,539.00 are available in the stock of the variable weight. The update has been cancelled. Closing is suspended because an error occurred. Please fix the problem and resume the close’ Problem was fixed in Customer environment and Partner reported this problem as code defect, but cannot provide repro steps nor a copy of the environment where it happened. Below the If statement where this problem is: // If we are recovering from a hard shutdown, but have no receipts other than the transfer receipt, // then all original receipts must have been settled against the transfer already, and we can just // use the transfer receipt as a single ordinary receipt and settle all (remaining) issues against it. if (transferAlreadyExists && receiptScanCount == 0) { receiptScanQty = this.financialOpenQty (transferReceipt); receiptScanValue = this.financialOpenValue(transferReceipt); if (isCatchWeightItem) { pdsCWReceiptScanQty = this.financialOpenQty(transferReceipt); } receiptScanCount = 1; transferAlreadyExists = false; } -
Purchase order takes Mode of delivery and Delivery terms from Sales order, should be from Vendor
After creating a sales order with a specific mode of delivery and delivery terms, a purchase order is created from the sales order (no direct delivery, just a normal one). The purchase order takes the mode of delivery and delivery terms from the Sales order when it should be filled what has been defined at vendor level. Imagine a situation situation the end-customer has a Truck 3 days delivery mode/terms and this is copied to the purchase order when it makes no sense since the vendor is in a different continent and delivers in ship in 60 days.
-
Load item receiving – cannot input batch number or skip lines
When receiving Variant Items with reservation hierarchy 'BatchAbove' and a manual Batch tracking group number. The batch numbers are specified on the purchase order lines. When receiving 2 batches for the same item, using inbound loads, the mobile device with work process 'load item receiving and put away' does not ask the batch you are receiving, and just registers the receipt on the first match purchase line, so potentially on the wrong batch number. It is also not possible to skip / enter a different line number. -
Cycle count "Retry attempt count" negatively impacts the flow when using counting reason codes
When using new Reason codes functionality with cycle counting together with quantity confirmation, the reason code must currently be specified before counted quantity has been confirmed by the user. This presents a functional issue where the user must specify the reason of wrong count before he/she is sure about the counted amount. FinOps 227593 -
‘Keep reservations on release failure’ during Automatic release of sales orders
Item model group has Reservation to FEFO date-controlled and Pick criteria to Expiration date. Location directive failures exists for Sales orders with Stop work on location directive failure enabled. Warehouse has ‘Reserve when orders are released by a batch job’ set to Yes. An item that is batch controlled has stock for a expired batch and the customer has some sellable days for it. A sales order is created with this item. The order is released through Warehouse management > Release to warehouse > Automatic release of sales orders, with Keep reservations on release failure to No. The release process fails as the batch is expired. When you check the transactions for the sales line, it's reserved when it should not. FinOps 227564 -
Inventory value report does not show any values when the ID contains "\"
When you create an Inventory value report with a "\" in the ID, like: INV\Group for example, the report does not work, no columns with qty and amount are shown. FinOps 180774
-
Load is not updated with the batch/serial numbers from production order when linked to a sales order
1. Batch and serial are above in Reservation hierarchy 2. Production order is created from sales line. Then load is created from sales order. 3. Production order is RAF (Batch and Serial are set with number groups) unit by unit. The batch and serial numbers are correctly updated in the inventory transactions but not in the load lines. 4. Load remains with status Incomplete reservation, and to move forward the only way is to delete the load and create it again. FinOps 230086 -
When removing the qty in an open sales line, the status does not change to Cancelled
When a sales order line is in Open status and you remove the quantity there, the inventory transaction is deleted but the sales line does not change to Cancelled but stays in Open order. It should change to Cancelled.
You’re offline. This is a read only version of the page.
