-
Setup of feasible warehouses per user
Through authorizations it is -theoretically- possible to restrict users to certain warehouses. However, with a large number of warehouses and users the drawback is: - lot of setup work - slow performance - not possible to grant a user - full access to warehouse A, - read access to warehouse B - no access to warehouse C. In my opinion it would be great to have a setup table "feasible warehouses per user". Preferably with authorization levels: full control, read, none. This should be respected at least in: - sales header - sales line - purchase header - purchase line - quotation header - quotation line - production order - production BOM - wave - load - shipment - work - on hand inventory - IC on hand inventory - transfer order header - warehouses - locations - inventory transactions Should be possible to setup from warehouse, and from user. Data area ID of the warehouse should also be part of the new table.
-
Work line should display product VARIANT name
In the form Work details, and on the Document Shipping pick list for wave, for product variants, the product variant name ("T-shirt Blue Large") should be displayed instead of the product name ("T-shirt"). Proposed solution: adding this.inventDimId in the argument of the display method WHSWorkLine.displayItemName() public display ItemName displayItemName() { return InventTable::find(this.ItemId).itemName(); } -
Packing station should display open lines from mutliple locations
Packing station in AX2012R3 CU13 and D365FO only shows the open lines of a shipment that are on the exact location of the current packing station. However, in practice items to be packed for a single shipment might be put on different locations in a packing area. If there are multiple packing stations, at the time the picker puts the goods on a location on the packing area, the exact station where the goods will be packed is in most cases not known yet. In CU10, the open lines were populated based on all the work lines that were put on the location type packing. There was no restriction wether the goods needed to be on this precise packing station. Pls. restore the CU10 functionality, or make this configurable. -
Auto split work when picking multiple LPs from 1 location with several LPs.
When multiple LPs are stored on one location, upon picking the mobile device worker has to "scan best matching LP". Scan LP1 If LP1 is not sufficient, the worker has to scan another LP, but that LP2 is dissolved into target LP1. Theoretically it is possible to avoid this by scanning LP1, pressing Full (which creates a closed work for LP1) enter the qty on the LP just picked, and continuing with the remainder on the original work. This process is so error-prone that I fail about half of the times. When the LPs have a fixed qty, it is possible to maximize the work template to 1 LP. But with varying qty per LP this is not possible. -
Vendor batch registration mobile device
Vendor batch data entry (vendor batch ID, expiry date, country of origin) on the mobile device should be possible to setup in the item model group, and date format in the warehouse worker. Currently, all data has to be entered on the mobile device in a less efficient way, and date entry is error-prone. It is fine if there are multiple screens, as long as each screen is relevant, and data entry is easy and non-ambiguous. Vendor batch number should always be asked first. A GS1 data matrix or batch barcode with multiple AI's should be interpreted. One scan is sufficient to fill batch date, best before date and expiry date. If the vendor batch is already known, in most cases it is not needed to re-enter the already known dates and country of origins, Proposed extra setting on item model group when Vendor batch registration is switched on: Vendor batch date: 0 = Always; 1 = First time only; 2 = Never Vendor batch best before 0 = Always; 1 = First time only; 2 = Never Vendor batch exp date 0 = Always; 1 = First time only; 2 = Never Country of origin 1 0 = Always; 1 = First time only; 2 = Never Country of origin 2 0 = Always; 1 = First time only; 2 = Never Use vendor batch date as manufacturing date Y/N Use vendor expiry date as expiry date Y/N "First time only" means: if this information is already known for the current vendor batch, do not ask for this information again, so skip the screen. DDMMYY or MMDDYY or YYMMDD should be possible to setup on the warehouse worker. On the mobile screen, display which format is used. No dashes or slashes etc. needed upon entry. -
Production order should not get status Released if raw material release to warehouse fails
If an error occurs in release to warehouse for raw material picking, the message "Could not release the order to warehouse because some materials could not be reserved." (class ProdWHSRelease.whsReleaseSingleOrder) However, the production order status is now Released. The production order setting "Release to warehouse" (ProdTable.ProdWHSReleasePolicy): Allow partial reservation or Require full reservation has no influence on this. Proposed solution: add a third option to ProdWHSReleasePolicy: "Block release until work created" i.e. release production order (or batch order) only when all raw material pick work is created. Note that the production wave is not always processed immediately. Alternative: add a checkmark on the production order "All raw material pick work created". -
Pack station enforce full scanning
In AX2012R3 WHS packing station (CU10), it was not possible to select multiple lines and pack these lines in 1 step. In D365FO, multi select was added. Now you can select all lines, and press Pack. This offers an easy bypass for the lazy packer... It should be possible to enforce full scanning (by disabling multiselect) based on a new flag on the shipment or the packing profile or the packing station worker or the picking worker. -
Store shipment ID on packing slip and invoice
When the packing slip ID is generated from the load or the shipment or the packing station, the table WHSLoadTableCustPackingSlipJour stores the link between the load ID and the packing slip ID. Often it is needed to print the shipment ID on the packing slip and invoice lines. However, this information is difficult to retrieve by the developer, and not always a unique identifier. Proposed solution 1. When posting the packing slip from load, shipment or packing station, store the shipment ID in the packing slip header and / or lines (add fields salesParmTable.WHSShipmentId and salesParmLine.WHSShipmentId). 2. Store the shipment on the packing slip header and lines (CustPackingSlipJour.WHSShipmentId and CustPackingSlipTrans.WHSShipmentId) 3. When posting the sales invoice, copy the shipment ID to invoice lines, and if identified invoice header. Maybe it is needed to store the Shipment ID on the Inventory transaction (InventTrans) as well.
Delivered solution
On the load a new field called Packing slip policy has been added.
If the packing slip policy is Shipment, then the packing slip will be created per shipment on the load.Two new fields are added to the shipment table.
Preallocated packing slip id, which will be used for the packing slip for the shipment since it will be passed to the SalesParmTable
The preallocated packing slip document date will be used as the date for the packing slip creation.
Preallocated packingslip ids can only be assigned to outbound shipments.
The preallocated packing slip Id is copied from the WHSSHipmentTable to the new field on the SalesParmTable called PreallocatedPackingSlipId and if that is set, it will be used as the packing slip id.
The preallocated packing slip Id is not populated for now, it will have to be entered manully or using an extension e.g. in whsshipmenttable.insert() method.
-
Intercompany shared warehouse locations
Purpose: use the same physical warehouse for intercompany. If multiple legal entities use the same physical warehouse, it is possible to create multiple identical warehouse setup. Thanks to the stored configuration settings in the WHS mobile app, the worker can now logon to a different company. However, in company X it is not visible whether location A-01-01 is occupied by inventory, or reserved for put away work in company Y. Therefor the worker in company X should not move inventory to location A-01-01. And the put away in company X should not be directed to location A-01-01 Proposed solution: 1. New checkmark on location profile: Block input for other companies 2. Automatically block a location for input (e.g. in the input block field or a new field Exclusive for company) in other legal entities whenever: - A put away work is created that is heading for such a location - A manual movement towards such a location is created - A worker overrides the put location 3. Automatically unblock a location for input in other legal entities whenever: - Such a location gets empty after a work pick line is executed - The worker has overridden this put location with a different location. - Trigger is the same as the update trigger for the location status. 4. Location directives must take into account the input block field. 5. An intercompany overview of all open work per warehouse (on the PC). -
Create new transfer order from sales line should set marking and group per transfer order
When you create a new production order from a sales order line, the marking and the references between sales line and production order are set automatically. But in the new functionality that allows the creation of a transfer order from a sales order line, no marking is created, and there is no protection against creating a double transfer order. Automatic marking of transfer orders created from sales lines should at least be possible through a parameter setting. For each sales line, a new transfer header and 1 transfer line is created. In the dialog, when you choose the from-warehouse, and there is already one open (not released) transfer order, there should be an option to add the new transfer line to the existing transfer order.
You’re offline. This is a read only version of the page.
