1.2 Product Templates, Category Hierarchies, and Product Lifecycle States

1.2 Product Templates, Category Hierarchies, and Product Lifecycle States

Quick Answer: When releasing products in Dynamics 365 Supply Chain Management, over 50 company-specific parameters must be configured. Product Templates (Personal or Shared) eliminate manual entry by defaulting baseline setups. Category Hierarchies organize products for operational roles (Procurement, Sales, Retail, Commodity codes), where only one hierarchy can be assigned to a specific role per scope. Product Lifecycle States govern operational readiness, allowing granular control to block or warn on master planning, purchasing, sales, production, and inventory movements.

---

Product Templates: Personal vs. Shared

Manually populating parameters for every released product introduces errors and delays. Product templates standardize field defaults across items.

1. Template Types

• Personal Templates (Template type = User): Visible only to the user who created them. Stored in personal usage data, suitable for individual product specialists.
• Shared Templates (Template type = Shared): Visible across the legal entity or organization to all authorized users. Centrally administered to enforce corporate data standards.

2. Creating and Applying Templates

• Creating from an Existing Product: Navigate to Product information management > Products > Released products, select a reference item, and click Options > Record info > Company accounts template. Enter a name, select the field groups to include (Inventory, Sales, Purchase, Warehouse management), choose the template type, and click OK.
• Applying Templates:
  • Manual Item Creation: Prompted automatically when clicking New in the Released products list.
  • Product Release Wizard: Selected during the release flow to populate company fields across target entities.
  • Action Pane Application: Applied to an existing record via the Apply template action.

---

Category Hierarchies and Hierarchy Roles

Category hierarchies provide multi-level taxonomies that classify products, services, and transactions (Product information management > Setup > Categories and attributes > Category hierarchies).

1. Structure

Organized as an inverted tree consisting of a Root node, intermediate Parent categories, and terminal Leaf categories. Nodes hold category codes, names, and attribute assignments.

2. Hierarchy Roles

Category hierarchies become operational when linked to roles under Category hierarchy role associations (Product information management > Setup > Categories and attributes > Category hierarchy role associations):

[!IMPORTANT] Single Role Assignment Rule: Only one category hierarchy can be actively assigned to the Procurement role. All procurement departments (IT, Facilities, Office Supplies) must be organized as branches within this single hierarchy.

3. Associating Products with Category Nodes

Open Released products, select an item, and click Product categories on the Action Pane. A product can belong to multiple hierarchies simultaneously (one Procurement node, one Sales node, one Commodity code node), but typically maps to only one leaf node per hierarchy tree.

---

Product Lifecycle States

Product lifecycle states manage the availability of products across their lifecycle from introduction to obsolescence (Product information management > Setup > Product lifecycle state).

1. Configuring Lifecycle States

• State ID and Name: Identifier (e.g., ACTIVE, PHASEOUT, OBSOLETE).
• Is active for planning: If set to No, Master Planning (including Planning Optimization) ignores demand and will not generate planned purchase, production, or transfer orders.

2. Enabled Business Processes (Blocking Matrix)

On the Enabled business processes FastTab, configure policy settings for transactional areas:

Each process supports three policy states:

• Enabled: Transactions process normally without restriction.
• Warning: Displays a non-blocking infolog warning when adding the item.
• Blocked: Throws a hard error and prevents transaction creation.

3. Default States and Automation

• Default State on Release: Configured in Product information management parameters to assign an initial state (e.g., Design or Active) automatically upon product release.
• Automated Obsolescence: A recurring batch job (Product information management > Periodic tasks > Change lifecycle state for obsolete products) evaluates products with zero transactions over a defined lookback period and transitions them to Obsolete.

---

Implementation Scenarios and Common Exam Traps

[!TIP] Exam Tip — Legal Entity Independence: Product lifecycle states exist directly on the Released product record. An item can be marked Obsolete in legal entity USMF (stopping sales and purchasing) while remaining Active in legal entity DEMF, accommodating regional product lifecycles.

[!WARNING] Exam Trap — Planning vs. Sales Mismatch: When phasing out a product, organizations often want to sell remaining inventory without purchasing new stock. If you set Sales order = Blocked, sales orders cannot be entered to clear stock. The correct setup is setting Purchase order = Blocked and Is active for planning = No, while keeping Sales order = Enabled.

[!IMPORTANT] Exam Trap — Category Deletion: A category node cannot be deleted if active released products or procurement policies are assigned to it. Products must be reassigned before node deletion.