Warehouse Aisle Digital Solutions - New Arc

D365 SCM – Release to Warehouse and Shipment Issues 

by D365 SCM

In warehouse operations, understanding system behaviors and troubleshooting common issues with Releasing orders to the warehouse and the created Shipments is key to maintaining efficiency. Below are frequently asked questions (FAQs) related to these topics within the Warehouse Management Module in Microsoft Dynamics 365 Supply Chain Management (D365 SCM). 

Why Won’t My Order Released to the Warehouse? 

There are several reasons why orders may not have properly released to the Warehouse and created a Shipment, here are the most common: 

  • Inventory is not reserved for the line being released. Ensure that inventory is Reserved physical, not Ordered reserved. 
  • The order requires 100% fulfillment, and something on the order is not fully reserved.
    The order requires 100% fulfillment, and something on the order is not fully reserved
  • The order is on hold for any of the following:  
    • Customer Hold – this could be at the account OR invoice account level. Check the Confirmation, delivery and invoicing on hold field on both the Customer and Invoice Account.
      A screenshot of a computer AI-generated content may be incorrect.
    • Order Holds
      A screenshot of a computer AI-generated content may be incorrect.
      • Manual hold from a user
      • Credit Hold 
  • If using Commerce, the order was not marked as “Completed.” 

Why are Shipments consolidating when there are different Shipping Carriers and/or Services? 

The Mode of delivery field on the Shipment consolidation policy is not linked to the Mode of delivery form, but instead just the Mode form. This means that, as long as the Mode for two orders is the same, Consolidation could occur when using default Shipment consolidation setups.

Screenshot of the Shipment Consolidation Policies in Microsoft Dynamics 365, displaying fields such as Address, Shipping Carrier, and Mode of Delivery.

To tell the system to correctly NOT consolidate orders, remove the Mode of delivery setting and Add Shipping carrier AND Carrier service.

A screenshot showing the Shipment Consolidation Policies in Microsoft Dynamics 365 Supply Chain Management, detailing policy settings, general information, and consolidation fields.

Note: the Mode of delivery on the Shipment is also really just the Mode. Use the Shipping carrier and Carrier service fields to do any filtering on the Shipment list pages.  

What Fields Will Update the Shipment if Updated on the Sales Order? 

Thanks to the Auto Update Shipment configuration within the Warehouse, some information that is changed on a Sales Order will flow directly to the Shipment without needing to delete the Shipment and Re-Release the order to the Warehouse.

A screenshot of the Warehouse Management settings in Microsoft Dynamics 365, highlighting the 'Auto update shipment' dropdown menu with options for updating shipments based on quantity changes.

 

As long as the Shipment has NOT been processed on a Wave (Work created), the following will update based on the setting of the Auto update shipment configuration.  

  • On quantity decrease 
    • The quantity for an existing line decreases 
  • Always 
    • The quantity for an existing line decreases 
    • The quantity for an exiting line increases  

Regardless of whether Work has been created, the following will also update on the Shipment when changed on the Sales order: 

  • Delivery recipient 
  • Address 

The following fields will NOT update on the Shipment if updated on the Sales order and must be manually updated either at the Shipment or Load level within the Warehouse: 

  • Mode of delivery 
  • Shipping carrier 
  • Carrier service 

Why aren’t shipments waving or why do they fall off the wave? 

If no work can be created for the shipment (review common Work creation issues here), it drops from the wave so the wave can continue for other shipments. 

If some work can be created, the shipment stays on the wave and creates work for what is available. 

Why do we get shipments with some work created but not all? 

If partial work can be created during the wave process, the shipment remains on the wave with the work that is possible. Items that cannot generate work will remain on the shipment with zero work quantity. 

  • Items with zero Work quantity need to be re-waved on a new wave or removed from the Shipment in order to complete the Shipment and see it in a Loaded status. 

Conclusion  

Understanding the nuances in how the system behaves when Releasing orders to the Warehouse and generating Shipments is a key step in efficiently running a warehousing using the D365 Warehouse Management module.   

For further insights on how to tailor D365 SCM to your specific needs reach out to a New Arc Solutions expert to Get Started! 

Warehouse and computer

D365 SCM – Containerization with Replenishment

by D365 SCM

In warehouse operations, Replenishment is commonly used to ensure picking can be condensed into specific areas and zones. When necessary, replenishment can occur on demand, Wave demand replenishment.  

However, when Containerization is introduced, Wave demand replenishment causes containers to break incorrectly, outside of the Containerization configurations. This happens since lines break when Wave demand replenishment is involved. 

What is Immediate Replenishment 

Immediate replenishment tells the system to replenish inventory as soon as the Pick line from a Location directive fails. This ensures that the replenished quantity is in the same unit that the outbound Pick is configured, instead of combining all the necessary replenishment needed for an entire wave, and replenishing in whatever the highest unit that is a perfect divisor for the quantity needed.  

When immediate replenishment is used, the Work created for the outbound pick does not split lines for a given item as does happen when Wave demand replenishment comes into play.  

Immediate Replenishment Configuration 

Immediate replenishment is configured through the same process as Wave demand replenishment, with the difference being when it is called. Where Wave demand replenishment is called using a Wave step code, Immediate replenishment is called on the Pick Location directives for outbound work (Sales orders, transfer issue, Raw material picking).  

Replenishment Template 

Just like Wave demand replenishment, a Replenishment Template is needed for Immediate replenishment where the Replenishment type is Wave demand.

Screenshot of a replenishment template management interface in a warehouse management system showing demand replenishment settings and options.

Note: a Replenishment Template created for Wave Demand can also be used for Immediate Replenishment.  

Replenishment Work Template 

The necessary Work templates for Replenishment are still needed for Immediate replenishment so that the necessary Work will get created. If multiple Pick/Put pairs are desired, a Directive unit is needed on all but the last Put.

Screenshot of a user interface displaying work templates for replenishment in a warehouse management system.

Replenishment Location Directives 

Just like Wave demand replenishment, a Pick Replenishment Location Directive is necessary to tell the system where to pick inventory when needed for Immediate replenishment as well as a Put in case the inventory needs a location not already determined by the Sales order Pick.

Screenshot of the Demand Replenishment Location Directives configuration, showcasing fields for directive sequence number, name, warehouse selection, and location directive actions.

Outbound Order Pick Location Directives 

Immediate replenishment can be added to any Pick Location directive line for all different Outbound orders types: 

  • Sales orders 
  • Transfer issues 
  • Raw material picking 

On the Pick line, add the Replenishment template of a type Demand in the immediate replenishment field. Note: only Replenishment templates of type Demand will be available in the dropdown. 

Screenshot of a warehouse management system interface displaying location directives for outbound picking, highlighting the field for immediate replenishment with the option 'Demand Replenish'.

Conclusion 

Understanding the nuances in how different functionality within the D365 Warehouse management module relate and work with each other key to effectively running a warehouse on the system. 

For further insights on how to tailor D365 SCM to your specific needs reach out to a New Arc Solutions expert to Get Started! 

Industrial warehouse showcasing organized shelves with illuminated storage boxes

D365 SCM – Work Creation issues 

by D365 SCM

In warehouse operations, understanding why Work isn’t created, either how it was desired or at all, can be painful to determine. Below are some of the common issues with work creation and how to solve and get past those issues.  

Understanding the Relationship Between Location Directives and Work Templates 

The first step to understanding why Work is not creating properly is to fully understand the relationship between Location Directives and Work Templates. This relationship is different depending on the Work order types.  

Outbound Order Picking: 

For Outbound Work order types, the following processes occurs to run through and select Location Directives and Work Templates.  

  • Wave is processed. 
  • Pick Location Directive is found. 
  • Temporary work lines are created. 
  • Work Template is identified. 
  • Based on the Work Template Directive Code, the Put Location Directive is found. 

Inbound Work: 

For Inbound Work order types, the following processes occurs to run through and select Location Directives and Work Templates.  

  • Receipt occurs on a mobile device. 
  • Temporary work lines are created. 
  • Work Template is identified. 
  • Put Location Directive is found based on directive codes. 

Replenishment Work: 

For the Replenishment Work order type, the following processes occurs to run through and select Location Directives and Work Templates.  

  • Pick Location Directive is found. 
  • Temporary work lines are created. 
  • Work Template is identified. 
  • Put Location Directive is found unless already determined by the Replenishment Template 
  • For Min/Max replenishment, a final Put cannot (generally) have a directive code. 

My Order is fully reserved, but no work has been created for certain items. 

In D365, there is no such thing as an unpickable location when it comes to reservation –only for work creation through Location directive. This means that an outbound order can reserve against any inventory within the warehouse if it has the same Inventory status and Variants, And is not already reserved against another outbound order.  

Only inventory reserved against an Outbound order and/or Outbound work is considered Reserved when a new order is evaluating inventory. This means, inventory sitting in a location that has Putaway work, movement work, or replenishment work tied to it may still be available for Outbound order reservation. 

Work Creating with Blank Locations when Location Directive Failures are Configured 

If you have Location directive failures configured, but are getting work with a blank Put, it may be due to the Work order type only reviewing the Location directive failures during the Pick process. 

For Outbound Work order types, the Location directive failure is only reviewed for the initial Pick when multiple Pick/Put pairs are being used. This can lead to a blank Put and subsequent second Pick to end up blank on created work instead of the work failing to create completely if no location can be found

Screenshot showing 'Location directive failures' settings with a focus on the 'Sales orders' work order type and an option to stop work on location directive failure.

Work Created for Locations with Cycle Count Work 

When cycle count work is created, the location and all the inventory in the location is still available for reservation and pick work. The system is smart enough to know if something is removed or added to the location, even if the Cycle count work is in process or Pending review.   

  • Picking: If the system expects 100 but a user counts 90, and 10 units are picked, the pending count updates to 90 system count and 80 user count. 
  • Putaway: If the system expects 100 but a user counts 90, and 10 units are put away, the pending count updates to 110 system count and 100 user count. 

If an item is short picked and Cycle count work is created, the system assumes the inventory is still there until the cycle count is completed and accepted. This means that something that is counted to zero but not yet approved (still in Pending review), work will continue to get created to pick from that location.  

Both of these issues can be mitigated by keeping up with Cycle count work and any Pending reviews that are necessary. 

Conclusion 

Understanding the nuances in how the system behaves to create work is a key step in efficiently running a warehouse using the D365 Warehouse Management module.  

For further insights on how to tailor D365 SCM to your specific needs reach out to a New Arc Solutions expert to Get Started!