This posting describes some of the enhancements of the WMS functionality that were added in Microsoft Dynamics AX 2012.
The WMSShipment table now stores the latest date where the shipment must be delivered in order to meet the requested ship date. This information is displayed in the Requested ship date (RequestedShipDate) field and the date corresponds to the earliest date that occurs on the lines of the shipment.
Based on this new field, batch processing of shipments can be set up with a level of detail that allows you to prioritize shipments that are soon to be shipped. The requested ship date is displayed in the Shipments form and records can be filter by this date.
You can now activate shipments when you run shipment reservation in batch. Select the Activate shipments parameter in the Shipment reservation form in Inventory and warehouse management under Periodic > Shipments > Shipment reservation.
With the Joint shipping parameter in the Shipment templates form you can now specify if a shipment should be split when output orders are added. With this parameter you do not need a separate template per customer to define what orders can be added to a shipment.
The enhanced shipment template can help improve the process to automatically assign orders to shipments. Orders are added according to the value of the Joint shipping field and shipments are automatically created for unique values.
In earlier versions only the numbers of pallets were tracked on locations.
In Microsoft Dynamics AX 2012, weight and volume of items and pallets are also tracked together with the pallet count. The load for a location can be seen in the Inventory locations (WMSLocation) form.
The tracking is based on records in a new table named WMSLocationLoad. Records are always created and they are never updated. This is to allow for better scaling. The load on a location can be determined from the sum of the records.
Transports now also store the total weight and the total volume of the transport. The values are stored in the TotalVolume and TotalWeight fields.
In order to reduce the number of records in the WMSLocationLoad table it is recommended to run the Summation of load adjustments job in Inventory and warehouse management under Periodic > Clean up on a regular basis.
By Bibi Christensen, Per Lykke Lynnerup and Lennart Conrad
All the information about AX 2012 posted here is a pre-release. Any feature is a subject to be changed before the release without notice. This disclaimer is applicable to all posts about AX 2012 in this blog.
Thank you for this posting Bibi, Per and Lennart, and we look forward to the final release of AX 2012.
thanks for sharing
<a href="http://geboon.com/"> post free classified </a>
Thanks for the very useful posting!
Could you please confirm that the "Joint shipping" parameter on the Shipment template works as expected:
It will allocate output orders to different shipments (by order or customer) when shipments are created automatically. When user creates a new shipment manually using the wizard, the user specifies a shipment template but the "joing shipping" parameter is ignored and all output orders are always allocated to the same shipment.
Thanks for sharing I have a question regarding this...... when I use the wizard shipment to create a new shipment how I can select from the inventory order page the Output Orders that I want to send with that shipment? cause right now is posting me all the output orders in the shipment and doesnt allow me to select the ones that I want. Thanks in advance!
What exactly is the Summation of load adjustments Clean up job doing? When running a consistency check, I get a few warnings saying that some locations have inconsistent registered vs (actual?) weight. I'm thinking running this clean up will fix, but what will adjusting the weight do? Create/remove inventory? How does it determine what it is adjusting?
Thanks for any insight!
@AAndy: Dynamics AX keeps track of the load on locations by tracking weight, volume and pallets. This is done by inserting records in the table called WMSLocationLoad.
The Summation of load adjustment job will aggregate all these records into one per location. This is done to keep the number of records down, since it improves the performance. So it has nothing to do with the consistency check.
The consistency check it self, should be capable of adjusting the inconsistent values.
It will do this by calculating how much the weight/volume should be, by determining how much inventory is at a location and determine the weight/volume of this inventory using the on-hand tables (InventSum) and the items base data .
If this is different than the load that is tracked on a location, it will create a new WHSLocationLoad record that will adjust the difference. So it will not create or remove any inventory.
I wish all Warehouse Management consultants knew this.
I just ran it on a customers pre-prod system, and one of the WMSLocationId's went down from 1.25 mill. rows to 3 rows.
With 1.25 mill. rows it was virtual impossible to do pallet movements, and when that location was the "entry" location to the warehouse their pallet movement became worse every day.
Thank you, I will never forget this, even I am not functional consultant but infrastructure system architect.
When Ax searches for a free location for inbound, is it only number of pallets that can be a constraint? Or can also height, weight and volume.be used ?