Configure products
MB-335 tests how you turn a product portfolio into Dynamics 365 Supply Chain Management master data. Expect questions on product masters, variant dimensions, attribute metadata, category hierarchies, unit conversions, and the settings that travel with a released product.
Core rules
- A distinct product has no variants; a product master carries up to three variant dimensions (commonly Color, Size, Style, Configuration) defined in a product dimension group. Storage and tracking dimension groups decide whether site, warehouse, location, batch, or serial numbers are mandatory.
- Configuration technology matters: predefined variants generate a fixed list; constraint-based rules create valid combinations; dimension-based configuration uses a configuration dimension. Changing technology after transactions exist is not supported.
- Attribute types are metadata: currency, date, decimal, enumeration, integer, reference, string, and boolean. Assign attributes to categories; released products inherit them, and values can be overridden per product.
- Category hierarchies drive procurement and sales category policies; a released product must belong to the hierarchy when the policy requires it.
- Unit conversions use a factor or numerator/denominator, with rounding. Default order settings can be legal-entity or site-specific; site-specific settings override the default.
- Product lifecycle state controls whether a product can be released and used on transactions.
- Product relationships include substitute, cross-sell, up-sell, accessory, and kit.
Worked example
A T-shirt is sold in three colors and four sizes. Create a product master with a dimension group containing Color and Size, assign an enumeration attribute for fabric, place it in the Apparel category, then release it to the legal entity. Releasing creates one released product per variant. Set storage and tracking groups before the first transaction because they cannot be changed afterward.
Traps
- Releasing before assigning a category hierarchy when category policies are active.
- Forgetting that unit conversion rounding affects order quantities, not inventory on-hand.
- Changing the item model group after cost transactions post, which changes costing behavior.