WorthKnowing: WHS vs WMS Prefixes in D365FO Warehouse Management

Hi folks,

If you've worked with Warehouse Management in Dynamics 365 Finance and Operations (D365FO), you might have come across two different prefixes in the system: WHS and WMS. Ever wondered why both exist and what they signify? Let’s break it down.

The Basics: WHS vs WMS

Both WHS and WMS stand for Warehouse Management System, but they refer to different generations of warehouse management solutions within Microsoft Dynamics.

WMS – The Legacy System

Objects prefixed with WMS belong to the legacy warehouse management system, which was part of earlier AX versions. This system supports basic warehouse operations, such as:

• Inventory location tracking
• Simple picking and receiving
• Basic location control

Examples of WMS objects:

• WMSLocation – Stores warehouse locations
• WMSOrderTrans, WMSJournalTable, etc.

While functional, the legacy WMS lacks the flexibility and scalability required for complex warehouse scenarios. It’s generally not recommended for new implementations.

WHS – The Advanced System

With the release of AX 2012 R3, Microsoft introduced a more robust and feature-rich warehouse management solution, which continues to evolve in D365FO. Objects prefixed with WHS are part of this advanced warehouse management system, designed to handle complex warehouse processes, including:

• Mobile device integration
• Work creation and execution (e.g., picking, putaway)
• Location directives, work templates, and wave processing

Examples of WHS objects:

• WHSWorkTable – Stores work headers
• WHSWorkLine – Stores work lines
• WHSInventEnabled, WHSParameters, etc.

This system is highly configurable and supports modern warehouse operations across industries.

Summary

• Use WHS objects for advanced, scalable warehouse management in D365FO.
• WMS objects are legacy and suitable only for basic scenarios or backward compatibility.

Understanding the distinction between WHS and WMS helps ensure you're building solutions on the right foundation, especially when designing or extending warehouse functionality in D365FO.

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

[Solved]The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory.

Hello,

This is happening again, when applying an update on development box, its failed with similar error on LCS

But when checking logs its says some strange error message, 

The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory.

I could not find a permanent solution for this but below worked for me. Firstly you can try to resume it once if its still throwing errors try below steps, 

1. Do a get latest on your dev box
2. Clear any of your pending changes, if feasible. Or at least make them error free. 
3. Do a full build and synch, make sure there are no errors. 
4. Close the VS and any other application running on your machine. 
5. Close the RDP.
6. Try to update your VM now. 

Also check for similar issues while updating your development boxes, 

Update script for service model: DevToolsService on machine

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta