Dynamics 365 Supply Chain Management

Work audit data capture

The work audit date feature offers warehouse employees the possibility to capture date, or automatically update shipment data or to print documents during the execution of warehouse processes. This can be useful for various purposes, for example to obtain a tracking number of a shipment or packing information with respect to boxes, pallets or containers. Another option is to update the shipment status to ‘shipped’ as soon as the load status has been changed to ‘loaded’.

In this blog I will demonstrate how you can employ the work audit data template feature for the registration of the packing dimensions. You might wonder whether you could also use the container type instead. Indeed, a container type allows you to setup default dimensions such as length, width and height as well. However, the disadvantage is that you cannot update these efficiently during the packing process. In particular situations, the container dimensions differ per order and packing type. In these cases, you might rather consider to register dimensions via the work audit data feature.

What is added value of this feature for the business?

It is a flexible feature which can be applied it in different ways.
The registered information (captured data) can be used in business documents such as a packing slip.

Configuration

1.A work audit template needs to be configured. In the work audit date template, you can configure which data the user has to enter during a warehouse process.

*Path: Warehouse management > Work > Work audit template lines update*

2.A mobile device menu item for the movement of the container from the pack location to the ship location. The work audit data template needs to be linked to the mobile device menu item.

*Path: Warehouse management > Setup > Mobile device > Mobile device menu items*

3.A mobile device menu with the mobile device menu item ‘Packed container picking’.

*Path: Warehouse management > Setup > Mobile device > Mobile device menu*

4.A work template for work order type ‘Packed container picking’. This work template is necessary to enable movement work of the container.

*Path: Warehouse management > Work > Work templates*

5.A location directive for work order type ‘Packed container picking’. The location directive allows you to configure the system in such a way that it instructs users to pick the container from the pack location and deliver it at the ship location.

*Path: Warehouse management > Setup > Location directives*

6.Container types for the packing process. The container types refer to the type of packing, for example a box or pallet. Additionally, you can enter container dimensions like container length, width, and height.

Path: Warehouse management > Setup > Containers > Container types

7.Container packing policy. The container packing policy determines whether Dynamics needs to create movement for the container or whether Dynamics should automatically move the container to the ship location.

Path: Warehouse management > Setup > Containers > Container packing policies

8.Packing profile. Via the container profile you can configure whether the container ID needs to be created automatically or entered manually by the user.

*Path: Warehouse management > Setup > Packing > Packing profiles*

9.A work user with a container packing policy, packing profile and default packing station.

*Path: Warehouse management > Setup > Worker*

Demonstration

1.A sales order with a product.

2.Release of the sales order to the warehouse for picking.

3.Picking from warehouse location A001.

4.Sending to put location for the packing process.

5.The worker can open the packing screen. In the packing screen, settings such as site, warehouse, location and packing profile are pre-filled based on the worker settings.

*Path: Warehouse management > Packing and containerization > Pack*

6.The warehouse worker can scan or enter the shipment ID/license plate to start the packing process.

7.The user has to click the button ‘New container’ and select the relevant container type.

8.The warehouse employee can pack the item into a container (box or pallet) with the ‘Pack’ button.

9.The warehouse employee closes the container with the ‘Close button’ and enters the weight.

10.The worker opens the Warehouse app and clicks on the menu item ‘Packed container picking’ to move the container (box or pallet) from the pack location to the ship location.

11.Pick from the pack location.

12.Move to the ship location.

13.The warehouse app asks the user to enter the ‘Length in mm’. This and following information requests come from the work audit data capture.

14.The warehouse app asks the user to enter the ‘Width in mm’.

15.The warehouse app asks the user to enter the ‘Height in mm’.

16.The warehouse app asks the user to enter the ‘Net weight in kg’.

17.The warehouse app asks the user to enter the ‘Gross weight in kg’.

18.The entered data has been added to the table ‘Work audit data capture’.

19.The warehouse employee can confirm the shipment of the sales order.

20.The packing slip can be posted.

21.The sales order status has been changed into delivered.

Detours

In the Warehouse Management mobile app, users can use the menus and menu items for the execution of warehouse processes such as receiving and picking. It may be necessary for the worker to perform a lookup for specific information during the receiving and picking process. This lookup feature is called ‘Detour’. Let’s explain this using the following scenario: a purchase order may arrive in different lines for the same item due to different delivery days, for example:

Line number 1 | delivery date 17-03-2024 | item A0002 | 1000 pcs
Line number 2 | delivery date 24-03-2024 | item A0002 | 1000 pcs

The supplier was able to deliver both lines (2000 pcs) earlier on 17-03-2024. Hence, the warehouse worker would like to register the 2000 pcs. However, the worker does not know that item A0002 has two purchase order lines. When the worker registers 2000 pcs on line number 1, this could mean that line number 2 remains open until someone discovers the error. In these situations, it would be useful to configure a lookup that shows the purchase order lines.

Configuration

1.A menu item for the purchase order receipt and put away.

2.A menu item called ‘Lookup PO lines’ for the lookup of the purchase order lines. The following settings are important:

Mode > Indirect
Activity code > Data inquiry
Table name > PurchLine

3.A query for the menu item ‘Lookup PO lines’. In the query the field ‘Item number’ needs to be added. In the field line number, a ‘star’ needs to be added. The star is necessary to show all the available purchase order lines for a specific item.

4.The field list needs to be configured. The field list is important for the detour settings of the mobile device step.

5.The menu item ‘PO Receipt and put away’ should to be added to the mobile device step ‘POLineNum’.

*Path: Warehouse management > Setup > Mobile device steps*

6. The detour menu item ‘Lookup PO lines’ has to be selected and added.

7.The fields need to be configured for automatic filling of the values between the main task and the detour.

Purchase order > Purchase order
Line number > Line number
Item number > Item

8.The menu items ‘PO Receipt and put away’ and ‘Lookup PO lines’ should to be added to the mobile device menu.

Demonstration

1.A purchase order with two lines for the same item and different delivery dates.

2.In the mobile device the user can click on ‘Inbound’ menu item.

3.The user then clicks on the menu item ‘PO Receipt and put away’.

4.After this, the user enters the purchase order number and clicks on the ‘Confirm button’.

5.The new button ‘Lookup PO lines’ is visible. The user can click on the button ‘Look PO lines’.

6.The user scans/enters an item number and clicks on the ‘Confirm button’ button.

7.An overview of the purchase order lines becomes available. Subsequently, the user can select the second purchase order line for example. If a purchase order line has already been (partially) received, the received quantity is visible in the field ‘Registered’.

8.After clicking on the purchase order line, the Warehouse app asks the user to confirm the purchase order line number. The selected purchase order line will be copied automatically.

9.The user enters the quantity and clicks on the ‘Confirm button’.

10.The user can confirm the entered values and click on the ‘Confirm button’.

11.The user then confirms the put location.

12.The pick & put work for the second purchase order line has now been completed.

Priority-based planning

Traditional master planning uses the requirement date to calculate when a supply is needed. If there are two demand requirements at the same day, the planner has to decide where it should go to first. Priority based planning helps the planner to determine in which order the inventory has to be allocated to different sources of demand, especially when there is no sufficient on-hand inventory available. The following picture demonstrates a priority based planning scenario.

The picture above shows that the demand cannot be fulfilled entirely through the on-hand inventory available. The question is then to which demand the on-hand inventory has to be allocated. Priority based planning supports the planner answering these questions by assigning priority to the demand based on business rules.

What is the business value of priority based planning?

Increased service levels
Lower inventory levels needed
Optimization of the Supply Chain

Configuration

1.The first parameter to be configured is the priority model. Via the priority calculation method, Dynamics assigns priority to the demand.

*Path: Master planning > Setup > Planning priority models*

Number	Explanation
1.Name	Name of the planning priority model
2.Description	Description of the planning priority model
3.Priority calculation method	Two calculation methods: Priority ranges > total inventory available as the percentage of the maximum inventory quantity that is set for an item.Percentage of maximum inventory ranges > the priority follows the value that are defined in the planning priority ranges grid (6)
4.Planned order creation	Two planned order creation options: Single supply with the most priority > the planning priority for a planned order is based on the most important priority range. Split according to priority ranges > Split the demand into multiple planned orders based on planning priority ranges
5.Consider demand priority	Set to “Yes” to limit the priority of a new planned order that is created for supply. If you set it to “No”, the priority of the demands will be ignored.
6.Planning priority ranges	The priority ranges
7.Planning priority defaults	Default planning priorities for each type of supply or demand.

2.The second parameter is the coverage group. The coverage group has a new coverage code called “Priority”. The coverage group has to be linked to the planning priority model.

3.The third important parameter is the item coverage. In the item coverage, the reorder point and the maximum quantity need to be configured. The reorder quantity should be based on the lead time and average daily usage.

Demo

1.For this demo we use item F0008 with item coverage “%Max”. Coverage group “%Max” has been linked to planning priority model “%Max” with calculation method “Percent of Maximum inventory quantity”. Dynamics uses the following formula to calculate the priority: Percentage of maximum = (Net flow position × 100) / Maximum inventory quantity value from the item coverage.

2.Item F00008 has the following on-hand inventory.

3.We run Planning Optimization via the net requirements form for the creation of the planned orders and the assignment of the priority.

4.Based on the calculation method “Percent of Maximum inventory quantity”, Dynamics has assigned the following priorities to the demand. The sales order gets the highest priority, then the transfer for warehouse 12 and the warehouse 11. The reason why warehouse 12 gets more priority then warehouse 11 is, that the actual on-hand inventory for warehouse 12 is less compared to the on-hand inventory of warehouse 11.

Demand	Requirement quantity	Priority	Actual on-hand inventory
Sales order	100	5
Warehouse 12	880	12	120
Warehouse 11	550	45	450

5.For the second demo we use item F0008 with item coverage “PRSingle”. Coverage group “PRSingle” has been linked to planning priority model SimpleSplit with priority calculation method “priority ranges”. This calculation method is more advanced than the percent of maximum inventory quantity. Via the grid “planning priority ranges”, you can configure the rules for the priority assignment in relation to the reorder points and maximum inventory.

6.Item F00017 has the following on-hand inventory.

7.We run Planning Optimization via the net requirements form for the creation of the planned orders and the assignment of priority.

8.Based on the calculation method “priority ranges”, Dynamics has assigned priorities to the demand below as follows. The purchase order gets the highest priority, then the sales order, and then the transfer orders for warehouse 12 and warehouse 11. The transfer order for warehouse 12 gets more priority, as the requirement quantity is between zero and the minimum inventory quantity (200).

Supply and demand	Requirement quantity	Priority	Actual on-hand inventory
Planned purchase order	880	1
Sales order	100	5	650
Warehouse 12	880	30	120
Warehouse 11	550	50	450

Custom label layouts

The custom label feature is designed to print labels for information such as items or locations etc. Customer label offers companies the possibility to apply label printing to any form in Dynamics. In the previous versions of Dynamics, label printing was limited to the inbound and outbound process of Warehouse Management. During projects, customers often asked whether it is possible to print labels for products or locations. Yet, customer had to perform this by themselves. With this feature, this is no longer necessary. What is the business value of this feature?

The possibility to print labels from almost any form in Dynamics 365 Supply Chain Management. For instance, this allows your company to print a label for a fixed asset or a customer.
Custom labels facilitate warehouse implementations. When a customer does not have any locations labels with bar codes, you can easily print these via custom labels.

Configuration

1.Enable the parameter ‘Display customer label print buttons’

2.Set up a label layout data source. Via this form you can determine from which table and which form you want to print the label. For example, if you want to print a label for a location, then you have to select the WMSLocation table.

3.A layout needs to be available for the label. In the overview below, you can find a short explanation for the label layout fields.

Number	Explanation
1. Label layout ID	Identification of the label layout
2. Description	The description of the label layout
3. Definition type	The code for the label like ZPL
4. Label layout data source ID	The source of the label (step 2)
5. Date, time and number format	Language for the date, time and numbers on the label
6. Fields	The available Dynamics fields for the label. When you select a field and click ‘Insert at end of text’, the value of the field will be included in the label.
7. Layout	ZPL code for the layout of the label. This ZPL code is being sent to the label printer.

4.A label printer needs to be configured to print the labels. For this blog I configured a virtual local ZPL printer from my pc.

Note: You might use the following YouTube video to configure a virtual local ZPL printer: https://www.youtube.com/watch?v=oG6n2PA-Phs

Demo

1.In the locations form, the new print button ‘Print Locations’ is now available.

2.Select one or multiple locations.

3.Click on the button ‘Print Locations’.

4.Select the label layout as well as the printer you are using and then click on the ‘Ok’ button.

5.Two labels have now been printed from the virtual local ZPL printer.

Custom fields

Recently, I got the opportunity to explore and apply the feature custom fields. What does the feature custom fields involve? Custom fields is a feature which enables you to create new fields, add these to a form, and to view these in Dynamics. The feature custom fields is powerful, as it avoids enhancements. Enhancements are sometimes necessary, however it is recommended to avoid these since Dynamics 365 Supply Chain Management is a cloud solution which is being updated regularly. The custom fields can be managed via System administration. Additionally, you can insert custom fields into data entities. The custom fields can be added to any form in Dynamics, and via this blog I would like to explain how you can configure a custom field and how you can apply it.

What are the benefits of custom fields for a company?

Avoid enhancements. Enhancements are a risk for upgrades, because an upgrade may change your custom code. Enhancements also influence the throughput time for testing, e.g., fewer enhancements could make the testing cycles shorter.
Decrease the need for technical support. You can configure new fields yourself, so you will no longer need the support of a developer for the creation of a new field.
Improve throughput time. You can easily customize Dynamics based on the needs of the customer. This will help to decrease the throughput time of the implementation.

Configuration

1.For this blog, I will add a new custom field to a released product. I will also explain how you can use the custom field while searching via the On-hand list.

2.Right-click the menu button ‘Personalize’.

3.Click on ‘Add a field’

4.Click on the ‘Create new field’ button.

5.Enter the following information for the creation of a new field:

Table name > Items
Name prefix > TypeNumber
Type > Text
Label > Label of the new field which appears on the form.
Help text > Additional information about the meaning of the new field.
Length > Maximum number of characters for the new field.

After entering the information, you can click on the ‘Save’ button to create the new field.

6.The new field is visible in the ‘Insert columns’ form. Click on the ‘Update’ button to add the new field to the released products form.

7.The new field is visible in the released products form.

8.The new field ‘Type number’ must be stored in a view. The reason for saving it to a new view is that it needs to remain visible and use the new field after re-opening the form. Another advantage is that you can also share the view with other users.

9.Enter a name for the new view and click the ‘Save’ button to save the new view.

10.Re-open the released products form and select the new view. The new field is visible and editable.

11.The new field ‘Type number’ can also be added to the list view via insert columns. Select the new field and click on the ‘Update’ button.

12.The new field is visible and also needs to be saved in a view. Select the view and click on the ‘Save as’ button.

13.Enter a name and click on the ‘Save’ button to save the new view.

14.The new view is now available.

15.Via the form ‘Custom fields’ you can manage the custom fields. In the form ‘Custom fields’ you can modify existing custom fields, delete them, and also add translations.

Path: System administration > Setup > Custom fields

16.If you want to insert the custom field into a data entity for the import and or export of data, you need to check the checkbox per data entity in the tab ‘Entities’.

17.After enabling the data entities, make sure that you click on the button ‘Apply changes’, otherwise, the changes will be lost.

18.If you want to use a custom field in a data entity, then you also need to generate the mapping of a data entity again. Select a data entity, for example ‘Released products V2’ and click on ‘Modify target mapping’.

19.By clicking ‘Generate mapping’, the new custom field becomes part of the data entity.

Demo

1.Open a released product and select the view ‘Released product with type number’.

2.Enter a Type number, for example ‘TN01072023’.

3.Close the form and open the Released products overview form and select the view ‘Released products overview with type number. As you can see, the value ‘TN01072023’ is also visible in the list overview.

4.Open the on-hand list.

Path: Inventory management > Inquiries and reports > On-hand list

5.Click on the ‘Add’ button in the filter form.

6.Search and select the new field ‘Type number’. After selecting, click on the ‘Update’ button.

7.The new field type number is now visible in the filter form.

8.Enter the value ‘TN01072023’ in the filter field ‘Type number’ and click on the ‘Apply’ button.

9.The released product appears based on the search value ‘TN01072023’ via the new field ‘Type number’.

10.When you run an export via the data entity ‘Released products V2’, the new field including the value is also included in the export.

Warehouse management wizards

When you need to configure the warehouse management parameters for a new warehouse, or when you have to configure the base setup of the warehouse management processes, you have to go through a number of steps. During the configuration process, you might forget certain steps, which could then cause errors during the test process and delays during the implementation process. To simplify the configuration process, Microsoft has introduced two wizards:

Warehouse management initiation wizard
Warehouse initiation wizard

The warehouse management initiation wizard assists the consultant or key-user in configuring the base settings, such as location profiles, location types, location formats, etc. The purpose of the warehouse initiation wizard is to guide the consultant and or key-user with the creation of warehouse management settings for a new warehouse. These wizards can also be useful after a go-live. For instance, when the company starts a new legal entity or a new warehouse, these wizards can facilitate a fast implementation of Warehouse management.

To summarize, what is the added value of the wizards for a company and or implementation partner?

Simplified implementation for consultants and/or key-users. These wizards facilitate simplified and faster implementation, saving (implementation) time.
Avoiding errors during the (test) process. The wizard provides guidance and makes sure that the consultant and or key-user do not overlook any parameter.

Configuration

It is recommended to first configure the Warehouse implementation tasks. Go to the homepage of Dynamics 365 Supply Chain Management and click on the workspace ‘Data management.’

2. Click on the tile ‘Framework parameters’.

3. Click on the tab ‘Entity settings’ and then on ‘Refresh entity list’. Refreshing the entity list is required to import the tasks into the workspace ‘Warehouse implementation tasks’.

4.Go back to the homepage of Dynamics 365 Supply Chain Management and open the workspace ‘Warehouse implementation tasks’.

5. In step 9 and 10, you can see the tasks of the Warehouse management wizards. It is recommended to execute steps 1-8 before using the wizards. Dependent of the situation, you may not need to go through all of the steps, e.g., a reservation hierarchy might already be available when you are changing settings for a new warehouse after go-live.

6. For the Warehouse wizard you also need to have ‘warehouse’. The parameter ‘Use warehouse management process’ should therefore be set as ‘Yes’, otherwise you are not able to select this warehouse in the wizard.

Process

1.The purpose of the Warehouse management initiation wizard is to configure the base setup for Warehouse management within a legal entity, for example location profiles and location types. Go to Warehouse management > Setup > Wizards > Warehouse management initiation wizard.

2. The starting page of the Warehouse management wizard shows what you have to configure in detail. Click ‘Next’ for the next step.

3. The next step is to ‘Initialize base data’, by entering the following information:

Location and profile names
Inventory status
Work user

4.Click on ‘Next’ for the next step.

5.The ‘base data setup complete’ page shows what the wizard will configure. Click on ‘Finish’ to start the configuration process.

6. A message in the action center shows that the configuration process has been completed.

7. When you open the ‘Location profiles’ for example, you can see the new location profiles.

8.Go to Warehouse management > Setup > Wizards > Warehouse initiation wizard. The purpose of this wizard is to guide the consultant and or key-user with the configuration of warehouse management parameters for a new warehouse.

9. The ‘welcome’ page of the wizard shows which settings the wizard can configure. Click on ‘Next’ for the next step.

10. Select the warehouse(s) you want to configure, including locations and other settings. Click ‘Next’ for the next step in the wizard.

11. Enter the names for the new work templates, wave templates and location directives for the new warehouse. If you enter an existing work class, e.g., purchase, then Dynamics will not create a new work class. In the final step, the wizard indicates whether a setting already exists or not. Click on ‘Next’.

12.If relevant, you can also configure a staging area via the wizard. Click on ‘Next’.

13. Enter the information for the shipping area. Click on ‘Next’.

14.The ‘warehouse setup complete’ page shows what the wizard will configure for the new warehouse. The column ‘Existing’ shows which settings already exist. If a setting already exists, the wizard will not configure these this again. Click on the ‘Finish’ button to start the configuration.

15.Let’s check what has been created by the wizard. The wizard has created two new sales order location directives for ‘WH 4’

16.Even the query of the location directive actions has been configured

17.Let’s also check the work templates. A new work template for the sales orders of the new warehouse ‘WH 4’ has been created.

Cross docking

There are several definitions of cross docking. According to Wikipedia, cross docking refers to a practice in logistics of unloading materials from a manufacturer or mode of transportation directly to the customer or another mode of transportation, with little or no storage in between. Cross docking takes place in a distribution docking terminal; usually consisting of trucks and dock doors on two (inbound and outbound) sides with minimal storage space. The picture below shows a simplified example of a cross docking process flow in a warehouse.

The supplier delivers the goods at the inbound area. Instead of the goods being put away to one of the storage locations, the goods go straight from the inbound area to the outbound area. Microsoft Dynamics 365 Supply Chain Management has a helpful function to support cross docking in the module Warehouse Management. What are the benefits of applying crossdocking for a company?

Efficient goods movements because it is no longer necessary to store the goods in storage locations first. This also saves picking time for the warehouse employee.
Faster throughput time of the orders. The goods can be delivered in a more efficient way and as a result, a company can deliver more goods and this way increase the cashflow.

Configuration

1.A cross docking template needs to be configured. In the cross docking template, you can configure the supply source as well as a few other important settings, e.g. the warehouse and location type. Other settings include the time windows for the time between the supply arrival and the demand departure. The supply sources setting is necessary for the system to determine whether the cross docking process concerns a transfer or purchase order.

2. A work class with work order type ‘cross docking’. Work classes are used to direct and/or limit the type of work order lines that a warehouse worker can process from a mobile device.

3. A work template for the creation of the cross docking work. Both the work order type and work class should be set as ‘Cross docking’.

4. A location directive for work order type Cross docking. Via the location directive, the system can determine the outbound location.

5. The purchase put away menu item must contain the work class cross docking.

Scenario

1.A sales order with 10 Jabra speakers.

2. Creation of the purchase order.

Note: the purchase can be generated in several ways, e.g. Planning Optimization.

3. Release to warehouse. When you release the sales order to the warehouse, Dynamics creates a cross docking link between the sales and purchase order.

Note: the release to warehouse can also be enabled by an automatic batch process on the background or via the release-to-warehouse form.

4. A warning message will appear, but this warning message can be ignored.

5. When you click on the Shipment details of the sales order line, you can see the cross docking link.

6. The purchase order is received via the Warehouse management app. By clicking on the inbound menu item, the mobile device shows the purchase receive menu item.

7. The purchase order number, item, and quantity can be scanned and entered via the menu item purchase receive.

8. Entering the purchase order number and clicking on the confirm button for confirmation of the purchase order.

9. Scanning the item number and clicking on the confirm button for the confirmation of the item number.

10. Confirmation of the entered information.

11. The warehouse management app detects the cross docking link and proposes the outbound location instead of a storage location as the ‘put away location’. Clicking on the confirm button to confirm the put action to the ship location.

12. Posting of the purchase order product receipt.

13. From the sales order, it can be seen that the cross docking work has been processed using the work order type cross docking.

14. In the ‘shipments ready to ship’ form the shipment is shown. From this form the shipment can be opened.

15. The shipment is confirmed, and the packing slip is posted.

16. The sales order status has been changed into delivered.

System directed cluster picking

Cluster picking is an efficient way to pick similar (small) items for different orders. Let’s explain this using the following example. Imagine having multiple sales orders with similar items, e.g., AirPods and iPad mini’s. The AirPods are available at location A001 and the iPad mini’s at location B004. The most efficient picking process would be for the picker to pick all items at the same time, first from location A001 and then from location B004, so that everything for the different orders can be picked in one round. In short, what are the benefits for a company?

Efficiency. The picker needs to go only once to a location for multiple orders.
Faster pick process. A picker can pick more orders per day, and this way, a company can process and deliver more orders of their customers.

Cluster picking is supported by Dynamics 365 Supply Chain Management. By configuring a few rules, you can easily make sure items for different orders are being clustered.

Configuration

A cluster profile. In a cluster profile you can configure how the system creates the cluster. Important settings are the sorting and the position settings. The sorting settings determine how systems sort within a cluster. The position settings determine the maximum number of containers or boxes within a cluster.

Path: Warehouse management > Setup > Mobile device > Cluster profile

2. A mobile device menu item for cluster picking. The setting ‘Directed by’ needs to be set as ‘System directed cluster picking’ and in the field ‘cluster profile ID’, the cluster profile has to be selected.

3. Mobile device menu with the menu item ‘SD Cluster’

Scenario

Two sales orders with the same items (iPad mini and AirPods Pro)

2. Both sales orders have been released to the warehouse.

3. From the mobile device menu, select ‘Outbound’.

4. Click on the menu item ‘SD cluster’.

5. The automatically created cluster appears. The picker needs to pick two iPad mini’s for both sales orders. After picking, the picker clicks on the confirm button.

6. The picker then enters the position. The position can be a container, a bin, or a box on a cart.

7. The picker receives the order to pick two AirPods for both sales orders. After picking, the picker clicks on the confirm button.

8. The picker enters the position and clicks on the confirm button again.

9. The picker can bring the picked items to the outbound location. After confirmation, the picking has been finished.

10. Shipments of both sales orders being confirmed.

11. Packing slips of both sales orders being posted.

12. Status of both sales orders have been changed into delivered.

Slotting

Companies can have many orders throughout the day. Multiple orders can contain the same item. The items could be stored in bulk and pick locations. Items from bulk locations have to be used to replenish the items at pick locations, so that the pick locations can be used for order picking effectively. To avoid empty pick locations, it is important to replenish items at pick locations in time. Dynamics 365 SCM has added a new feature called ‘Slotting’. By using Slotting, Dynamics helps to make sure locations are being replenished in time, based on the actual consolidated demand of sales and/or transfer orders. For example, on Monday, there are 100 sales orders for item X. At the beginning of the day you want at least 100 pieces of item X to be available from a pick location. The Slotting feature of Dynamics checks the actual consolidated demand. Additionally, based on the total demand, Dynamics could propose a movement from the bulk location to the pick location. The benefits for a company are:

Efficiency. By using this feature, replenishment is based on actual demand and empty pick locations can be prevented.
Cashflow. With increased efficiency, a company can deliver more orders which may also have a positive effect on the cashflow.

Configuration

A replenishment template of replenishment type ‘wave demand’.

*Path: Warehouse management > Setup > Replenishment > Replenishment templates*

2. A work class of work order type ‘replenishment’.

*Path: Warehouse management > Setup > Work > Work classes*

3. A work template for work order type ‘Replenishment’.

*Path: Warehouse management > Setup > Work > Work templates*

4. A mobile device menu item for replenishment work. This menu item is needed for the execution of the replenishment work via the mobile device.

5. Location directives for work order type ‘Replenishment’ and a directive code. The location directives determine the picking and delivering location for the replenishment work, e.g., the items have to be picked from the bulk location and have to be delivered at the pick location.

6. Slotting unit of measure tiers. The purpose of the slotting unit is the grouping of units for slotting. For instance, ea and box can be grouped in the same area.

*Path: Warehouse management > Setup > Replenishment > Slotting unit of measure tiers*

7. A slotting template of demand type ‘Sales orders’ and Demand strategy ‘Ordered’. The demand strategy determines the definition of demand, or what does the company consider a demand. For instance, a company might consider the demand to be determined by the number of orders, or rather by the number of reservations.

*Path: Warehouse management > Setup > Replenishment > Slotting templates*

Scenario

There are four sales orders from different customers. Each sales order contains the item S211202.

2. Item ‘S21112022’ is only available at the bulk locations.

3. At the Slotting template you first need to click on the button ‘Generate demand’. This way, Dynamics checks the total consolidated demand (sales orders with status ‘ordered’) for items with the unit of measure ea.

4. When the user clicks on ‘Slotting demand’, Dynamics shows the total demand. In this example, the total demand is 50 ea for multiple sales orders.

5. Locate the demand to generate the slotting plan.

6. In the slotting plan, Dynamics shows where the demand is located, as well as the put away location (picking area)

7. Run replenishment for the creation of replenishment work from the bulk to pick location.

8. Replenishment work has been created.

9. Execution of the replenishment work via the mobile device.

10. The items of the requested demand are available at the pick location.

11. After the replenishment work, the sales orders can be released to the warehouse for picking.

12. Execution of the picking work via the mobile device.

13. Confirmation of the shipments.

14. Generate packing slip.

15. The sales orders’ status is changed into ‘delivered’.

Advanced Shipping Notice (ASN)

The Advanced Shipping Notice (ASN) is an electronic notification of upcoming shipments. It contains the list of item(s), but also the packaging type and carrier information. Using ASN’s has two important benefits:

Lower costs > It is no longer necessary for a warehouse worker to break down the packaging of parcels to identify the items inside the parcels, as the ASN includes a barcoded ID license plate) which represents the items and quantity.
Improved accuracy > the warehouse worker of the receiving warehouse is being informed about any differences between expected and shipped quantity immediately.

When the ASN is available in the system, warehouse workers only need to scan the barcoded ID (license plate) to register items for the receipt and put away process. This way, the inbound process becomes more efficient and less complex.

Configuration

The item(s) must be enabled for the warehouse management via the Storage dimension group.

2. At the ‘Warehouse’, the parameter ‘Use warehouse management process’ needs to be set to ‘yes’.

3. The mobile device menu item ‘PO LP Receipt’ and work creation process ‘License plate receiving’ have to be available in the mobile device app.

4. Also, the mobile device menu item ‘PO Overview’ and mode ‘Indirect’ and activity code ‘Display open work list’ have to be available.

Demo

A purchase order with two order lines

2. An Advanced Shipping Notice in XML format

3. ASN can be imported via an import project in Data management workspace. In the Data management workspace, an import project of the type ‘import’ has to be created.

4. The XML message needs to be uploaded via the data entity ‘Inbound ASN V3’ in the data import project. ‘XML-Element’ then has to be selected as the source data format.

5. By clicking the button ‘Import Now’, the import process is being started.

6. The execution status will be changed into ‘Succeeded’.

7. A new load has been created for the purchase order.

8. The load also has a packing structure with ASN structure. The packing structure contains the barcoded ID (License plate), items and quantity.

9. Once the items have been delivered, the warehouse worker can use the mobile device scanner and click on the button ‘Purchase order LP receipt’.

10. Then, the warehouse worker can scan the barcoded ID (license plate) on the packaging and click on the confirm button.

11. The mobile device will show a summary of the barcoded ID (License plate). The warehouse worker can click on the confirm button again.

12. When the warehouse worker has clicked on the confirm button, the system will have registered the items on the receipt location and have started put away work.