4.2 Default Order Settings and Site-Specific Order Settings
Key Takeaways
- Default order settings govern procurement, internal inventory movements, and sales distribution across three dedicated tabs: Purchase order, Inventory, and Sales order.
- Default site and warehouse automatically populate transaction lines; marking Mandatory site or Mandatory warehouse strictly prevents users and master planning from overriding those dimensions.
- Order quantity boundaries (Minimum, Maximum, Multiple, and Standard order quantities) enforce order lot sizes, carton increments, master planning order splits, and BOM cost calculation lot sizes.
- Lead time parameters can be calculated using elapsed calendar days or constrained by an active Working days calendar assigned to the vendor, warehouse, or coverage group.
- Site-specific order settings override the global fallback (blank site) order settings, allowing organizations to tailor order multiples, lead times, warehouses, and Stopped statuses per operational facility.
4.2 Default Order Settings and Site-Specific Order Settings
Quick Answer: Default Order Settings (
InventItemOrderSetup) define operational and commercial guardrails for released products in D365 SCM. Structured across three functional contexts—Purchase order, Inventory, and Sales order—they control default and mandatory sites/warehouses, order quantity boundaries (Minimum, Maximum, Multiple, Standard), lead times, and transaction blocking via Stopped flags. D365 SCM evaluates order settings through a two-tiered resolution hierarchy: the system first searches for a Site-specific order setting matching the transaction site; if none exists, it falls back to the Global default order setting (where Site is blank).
Default Order Settings Architecture: The Three Functional Tabs
Every released product requires defined ordering parameters to control document creation and guide Master Planning (Planning Optimization). Navigate to Product information management > Products > Released products > Manage inventory tab > Order settings > Default order settings.
The form is organized into three distinct transaction tabs:
- Purchase order tab (
InventItemPurchSetup): Governs external procurement, purchase requisition line defaulting, purchase order generation, planned purchase orders generated by master planning, and vendor confirmation lead times. - Inventory tab (
InventItemInventSetup): Governs internal warehouse movements, transfer orders, inventory adjustment/movement journals, BOM/formula component flushing, production order batch sizing, and planned transfer/production orders. - Sales order tab (
InventItemSalesSetup): Governs commercial distribution, customer sales quotation and sales order line defaulting, customer return orders, Available-to-Promise (ATP) shipping lead times, and sales quantity restrictions.
Default Site and Warehouse vs. Mandatory Flags
Within each of the three tabs, consultants configure the physical fulfillment topology:
- Default Site and Warehouse: When an order line (PO, SO, Transfer) is initialized, D365 SCM automatically populates the Site and Warehouse fields using these default values. If a user changes the customer delivery address or selects a different site, the default warehouse tied to that site is re-evaluated.
- Mandatory Site: When checked, users cannot modify the Site dimension on the transaction line. It is strictly locked to the configured default site. If an automated import or EDI message attempts to pass a different site, the transaction fails validation.
- Mandatory Warehouse: When checked, users cannot modify the Warehouse dimension. Master planning is strictly prohibited from generating planned orders for any other warehouse under that site.
[!WARNING] Exam Trap — Master Planning Impact: If Mandatory warehouse is enabled on the Purchase order tab for Warehouse 11, Master Planning (Planning Optimization) will never create a planned purchase order for Warehouse 12, even if Warehouse 12 faces a catastrophic stockout and possesses an active item coverage record. Mandatory flags strictly override dynamic planning logic.
Order Quantity Parameters and Lot Sizing
Order quantity controls prevent erratic ordering patterns, enforce full-carton or pallet-layer purchasing, and protect against catastrophic entry mistakes:
| Parameter | Field Name | Master Planning & Operational Impact |
|---|---|---|
| Multiple | MultipleQty | Forces transactions in discrete numerical increments (e.g., Multiple = 12 enforces full dozens). Master planning rounds net requirements up to the nearest multiple. |
| Minimum order quantity | MinQty | Smallest permissible order quantity. If master planning calculates net demand for 3 units, but the Minimum is 50, the planned order is generated for 50 units. |
| Maximum order quantity | MaxQty | Upper capacity ceiling for a single order line. When master planning encounters demand exceeding this limit (e.g., net demand of 300 where Maximum is 100), it splits the requirement into multiple planned orders (100 + 100 + 100). |
| Standard order quantity | StandardQty | Populates the initial default line quantity upon manual entry. On the Inventory tab, it dictates the Costing lot size for BOM cost roll-ups, amortizing fixed setup costs across this exact quantity. |
Lead Time Management: Working Days vs. Calendar Days
Each tab provides dedicated lead time fields:
- Purchase lead time: Days required from PO confirmation to dock receiving.
- Inventory lead time: Production cycle duration or inter-warehouse transit window.
- Sales lead time: Order dispatch window used for Available-to-Promise (ATP) delivery date calculations.
The Working Days Toggle
Beside each lead time field sits the Working days checkbox:
- Working days unchecked: Lead time represents elapsed calendar days (24/7 continuous progression), including weekends, holidays, and facility shutdown periods.
- Working days checked: D365 SCM iterates through the assigned Working time calendar (configured on the vendor, warehouse, coverage group, or legal entity). Saturdays, Sundays, and non-working holiday dates are skipped. If an order with a 5-day purchase lead time is confirmed on a Thursday, the engine skips Saturday and Sunday, establishing delivery for the following Thursday.
Site-Specific Order Settings: Resolution Hierarchy
In multi-facility enterprises, operational parameters vary by location. An item procured at Site 1 (near a local supplier) may have a 2-day lead time and purchase multiple of 10. That same item transacted at Site 2 (supplied via overseas freight) may require a 45-day lead time and a minimum order quantity of 1,000.
Modern D365 SCM manages this through Site-specific order settings within the unified Default order settings form:
- Rank 0 / Fallback Record (Blank Site): Every released product has a baseline default record where the Site field is empty. This serves as the universal fallback configuration.
- Site-Specific Record: When a record is created with a specific Site selected (e.g., Site 1, Site 2), all settings on that row override the baseline fallback whenever a transaction is initiated for that specific site.
- Granular Overrides: You can configure a site-specific record that overrides only the Sales order tab while inheriting purchasing rules from the fallback record.
The "Stopped" Flag Architecture
The Stopped checkbox is an administrative control available independently on the Purchase order, Inventory, and Sales order tabs:
- Purchase order tab: Blocks purchase requisitions, purchase order lines, vendor confirmation, PO product receipts, and planned purchase orders.
- Inventory tab: Blocks transfer orders, inventory journals (adjustments, movements, counting), BOM consumption, and production report-as-finished.
- Sales order tab: Blocks sales quotation confirmations, sales order line creation, packing slips, and invoicing.
Global vs. Site-Specific Stopping
- Global Discontinuation: Marking Stopped on the blank-site fallback record prevents transactions across the entire legal entity.
- Site-Specific Stopping: Marking Stopped on the Site 2 record halts transactions exclusively at Site 2 (e.g., closing sales from a damaged regional warehouse while Site 1 continues normal order fulfillment).
Implementation Scenarios and Exam Traps
[!IMPORTANT] Exam Tip — Stopped vs. Product Lifecycle State: The Stopped flag on default order settings blocks transactions immediately at the document entry level without altering the product master's lifecycle state. Conversely, Product lifecycle state (
Product information management > Setup > Product lifecycle state) provides broader, policy-driven governance across all legal entities.
[!WARNING] Exam Trap — Minimum vs. Standard Quantity: On the exam, do not confuse Minimum Order Quantity with Standard Order Quantity. Minimum order quantity strictly restricts the smallest transaction size permitted on orders. Standard order quantity simply populates the initial default line quantity and dictates the costing lot size for BOM roll-ups.
A multinational manufacturer operates two production facilities: Site 1 and Site 2. The procurement department purchases raw material chemical RM-40 in standard full-truckload multiples of 100 drums for Site 1. However, Site 2 is a pilot facility with severe space constraints and must procure RM-40 in small pallet increments of 10 drums, with a minimum order quantity of 10 drums and a maximum limit of 30 drums per purchase order. When purchasers create purchase orders for Site 2, the system must enforce the 10-drum multiple and prevent orders exceeding 30 drums. How should the functional consultant configure the order settings?
A distribution enterprise discovers a severe packaging defect in a finished consumer product stocked in Warehouse 21 (located at Site 2). The quality director mandates that customer service representatives must immediately be blocked from creating, quoting, or confirming sales orders for this item when fulfilling from Site 2. However, order fulfillment for the same item from Warehouse 11 (located at Site 1) must continue uninterrupted. How should the functional consultant configure this restriction?
A purchasing agent creates a purchase order line for an imported component on a Wednesday. The vendor's standard purchase lead time is 5 days. The vendor operates Monday through Friday and is completely closed on Saturdays and Sundays. The purchasing director requires that the system calculate the confirmed delivery date by accounting strictly for the vendor's operational business days, automatically skipping non-working weekend days. What configuration is required on the released product's Default Order Settings?