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

WorthKnowing: Where to add new fields on Item master

When customizing the item master in Dynamics 365 Finance and Operations (D365FO), one common question is:
Should I extend InventTable or EcoResProduct?

Here’s a WorthKnowing guide to help you decide:

1. InventTable

• Purpose: Holds inventory-specific data for released products.
• Scope: Company-specific (per legal entity).
• Use When:
  You need to add fields related to:
• Inventory management
• Warehousing
• Sales or purchasing
• Any data that varies by company
• Examples:
  Item group, inventory dimensions, default warehouse, sales price.

2. EcoResProduct

• Purpose: Stores the core product definition (product master).
• Scope: Shared across all companies (global).
• Use When:
  You need to add fields related to:
• Product identity
• Technical specifications
• Data that should be consistent across all legal entities
• Examples:
  Product name, product type, product number, technical specs.

Knowing the difference between these two tables can save you time and ensure your customizations align with D365FO’s architecture. Choose wisely based on the scope and nature of your data.

New post series 'WorthKnowing'

Hello Everyone,

I'm excited to kick off a brand-new blog series where I’ll be sharing bite-sized insights and interesting facts about Dynamics 365 Finance and Operations (D365FO).

This series will highlight:

• Hidden gems that have been around for a while but often go unnoticed
• New features and their best use cases
• Common functionalities you might be using differently than intended
• Similar looking things with their core differences

Each post will be short, sharp, and packed with useful takeaways to help you get the most out of D365FO.

Stay tuned — and let’s explore these insights together!

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