Configuring WMS Dimensions for Multi-Company Dynamics 365

MB-330 By islever Editorial Last updated

Create and manage products Configure warehouse management

Short answer

BD Create a product master and leave the storage group blank, assigning it specifically during release to each company.

Question

A company with two legal entities uses Dynamics 365 Supply Chain Management. You are creating new products and learn that CompanyA plans to use Warehouse management (WMS) but CompanyB will not. Each storage, tracking, and production dimension name and configuration must be identical in each company. You need to set up the dimensions that affect the WMS for the new products. Which two actions should you perform? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
  1. Assign a tracking group to the product and release it to both companies, changing one tracking group after release.
  2. Leave storage group blank on the product and assign after release to both companies. Correct Answer
  3. Assign storage group to the product and release to both companies, changing one after release.
  4. Create a product master and assign configuration technology. Correct Answer

Key Takeaways

This question tests the prerequisite of establishing a global product structure before assigning company-specific warehouse configurations, avoiding common errors in tracking group management.

Learn how to configure identical warehouse dimensions across legal entities in Dynamics 365 SCM by using a product master and configuring storage groups during release.

Common mistake: Many users incorrectly select options involving modifying tracking groups after release or leaving storage groups blank without proper configuration, failing to realize that storage groups must be explicitly assigned per company if they differ from the master.

Expert Analysis

Why the Answer Is Correct

The correct actions are to create a product master (Option D) and leave the storage group blank on the product while assigning it upon release to each company (Option B). In Dynamics 365 Supply Chain Management, when multiple legal entities share a product but have different warehouse requirements (like WMS vs. non-WMS), you must first define the product at the global level (Product Master). Since CompanyA uses WMS and CompanyB does not, their storage dimension requirements likely differ. You cannot assign a single storage group to the Product Master that satisfies both if they are fundamentally different. Therefore, you leave the storage group blank at the global level and specify the appropriate storage group for each legal entity when releasing the product.

Why the Other Options Are Wrong

Option A is incorrect because changing a tracking group after release is not a standard supported practice for ensuring consistency; tracking groups should be defined correctly during the release process. Option C is incorrect because assigning a storage group to the product (at the master level) and then changing it after release is redundant and potentially problematic; the storage group is a company-specific attribute in this context, so it should be set during the release step, not modified afterwards. Modifying core attributes post-release can lead to data integrity issues.

Community Comment Notes

The community heavily favored the combination of creating a product master and handling storage groups during release. As user IlseKH noted, interpreting production dimension groups as part of the product setup makes sense, and leaving the storage group blank initially ensures the right assignment. User globeearth confirmed that technically, one can create a product master without a global storage dimension group, allowing for specific assignments to legal entities upon release. This validates the strategy of decoupling the global product definition from specific warehouse configurations.

Exam Strategy

When dealing with multi-company scenarios in Dynamics 365, always check if the configuration differs between companies. If it does, use the Product Master for shared attributes and handle differing attributes (like Storage Groups) specifically during the 'Release to Companies' step rather than trying to force a global setting.

Frequently Asked Questions

Why can't I assign a storage group to the product master?

If companies have different WMS requirements, a single global storage group may not fit both. Assigning it per company during release allows for necessary differences.

Is it safe to change tracking groups after release?

It is generally not recommended. Tracking groups should be defined correctly during the initial release to ensure data consistency and avoid potential system errors.

More MB-330 FAQ →

Community Votes

BD
80%
BC
20%

80% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors, not of islever. The comments shown first are the most substantive of the thread — ranked by depth, community endorsement and relevance; expand the list below to read the rest.

From public community threads 3

  1. IlseKH 👍 3
    if production dimension group can be interpreted as "product" dimension group, D as an answer makes sense, B would also be the best way to be sure to assign the right group, and not forget it to change after the release thanks copilot (it seems to use the same MS language :) )
  2. globeearth 👍 1
    it is technically possible to create a product master without assigning a storage dimension group at the global (shared) level, leaving it blank initially and assign it while releasing ito legal entity.
  3. Markus0877 👍 1
    b and c?

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Configure Asset Management for Fuel and Maintenance in Dynamics 365

S-grade

Configuring ABC Model Codes in Dynamics 365 SCM

S-grade

Dynamics 365 SCM Maintenance Round vs Plan

S-grade

Configuring Exporter Reporting for Shipments in D365 SCM

S-grade

← Back to MB-330 Study Guide