Confirmation for serial numbers is now supported in 10.0.37 Microsoft Dynamics 365 SCM

In this blogpost I am going to walk through the new feature released in 10.0.37 Microsoft Dynamics 365 Supply Chain Management.

Before this feature is introduced, it was possible to confirm only batch numbers for the products where batch number is above the locations in the reservation hierarchy. This functionality was not available for serial numbers.

Batch and license plate confirmation - Supply Chain Management | Dynamics 365 | Microsoft Learn

For many organizations, especially for the manufacturing processes, it is highly important that picker picks the right product. Without this feature picker might take a different serial number then the one specified in the work line and he didn't have a way to confirm the serial number that was reserved for the picking work.

In 10.0.37 a new configuration was introduced: 

• Go to Warehouse management > Setup > Mobile device > Mobile device menu items 
• Select Sales picking mobile device menu item
• Select Work confirmation button
• Serial confirmation parameter is displayed.

Limitations and considerations:

• Serial confirmation is supported only for serial above items
• It is not supported for piece by piece picking

Now let's walk through the example. 

First of all, we need to created Serial above reservation hierarchy. 

• Go to Warehouse management > Setup > Inventory > Reservation hierarchy
• Create a new one and select serial number above the location.

Then let's create a product with enabled serial number tracking dimension and serial above reservation hierarchy. 

We also will need on-hand for this product. I am going to add 3 ea for 3 different serial numbers S1, S2 and S3

It is time to create a sales order. 

Create sales order with product.

Reserve inventory and release to warehouse.

You will notice that work is created

As you can see, the system is reserving S1 serial number, so worker will be guided to pick up this specific serial number.

Let's now log in to the mobile device and do the picking.

I will start by navigation to Work list to see all open works.

Select the work with the serialized product created previously. 

System will ask to scan the License plate. 

Now the system asks to confirm serial number. This step is displayed because we activated new configuration - Serial confirmation on the mobile device menu item. 

If you scan a serial number that doesn't match to the serial number on the work line - you will get an error message. 

If it matches, the next step to scan target LP will be displayed. 

And the rest steps are typical for the picking process and not related to the new feature. 

Confirm the put step.

Once you confirm - work completed message will be displayed

That's it!

Automatic re-waving process has been introduced in 10.0.37 SCM

In this blogpost I am going to walk through new feature that has been introduced in 10.0.37. This feature allows users  to configure automatic re-waving process that will process shipment lines that did not complete during processing of waves. It eventually will be removing any manual human involvement.

Why it is important? 

It is very common situation when wave lines fail due to multiple reasons. It can be because of lack of on-hand inventory in picking locations, some item attributes issues and many other. There are might be other reasons of why shipments lines do not complete waving. They are:

• Production is delayed and did not report inventory as finished, waves cannot allocate inventory.
• Goods are in quarantine and not available
• Goods are still on inbound bay and not available on picking locations

When this happens, users typically need to manually handle such situations. They have to manually add lines to the new wave and process it. 

With this feature, this process is now automated. There is a new batch job has been introduced that will make your life easier meaning that if the lines didn't complete wave process then the failed line will be automatically assigned to the same wave template and re-waved without human involvement. 

Now let's deep dive into the feature.

We will start with simulating failure of waving process:

I am going to create sales order for the product for which I have on-hand inventory in RECV location, but not in the Picking location. Let's assume customer ordered 2 ea, and I have 10 ea available on-hand in RECV location.

Reservation will be done successfully, but wave allocation will fail. 

As soon as I release this order, the following will be done:

• Load will be created
• Shipment will be created
• Wave will be created
• Shipment will be added to wave
• Wave allocation will fail
• Shipment will be removed from wave

The result of the release:

And here a new logic kicks in. 

When wave fails, a record will be created in the new table WHSWaveProcessingRemovedShipment with the RewaveCount

You can review the data using table browser:

/?mi=SysTableBrowser&tablename=WHSWaveProcessingRemovedShipment&cmp=USMF

Now, you can run new batch job introduced to pick up failed shipments and create new waves and try to process wave with included failed shipments again. 

Go to Warehouse management > Outbound waves > Auto add shipments to wave

Here you see how many times process the failed shipment will be repeated. In our case it is set to 5 times. Batch job will pick up all shipments where Rewave counter is less or equal to the Rewave counter set in the batch job parameters, 

Since for our scenario, we have not changed anything, wave processing will fail again. Rewave counter in this scenario will be increased. It means that we tried to process that shipment via batch job 1 time.

Let's add on-hand to the bulk location and run Auto add shipments to wave again. 

Now the new wave will be created, shipments are added and wave is successfully process. Data related to that shipment will be removed from the WHSWaveProcessingRemovedShipment table. 

Some additional details:

If The failed Shipment is removed, it will be removed from this WHSWaveProcessingRemovedShipment log table. 

That's it!

Synchronize updates of the Requested ship and receipt dates on intercompany sales and purchase order lines.

In this blog post, I would like to talk through the intercompany feature that has been introduced in 10.0.37 release. 

Feature name: Synchronize updates of the Requested ship and receipt dates on intercompany sales and purchase order lines
Feature summary: This feature lets you control whether the requested ship and receipt dates are synchronized across intercompany sales and purchase order lines.
It adds new settings to both the "Purchase order policies" and "Sales order policies" tabs of the "Intercompany" setup page for customers and vendors.

I am going to use a few abbreviations throw-out the article. It means the following:  

IC PO - Intercompany Purchase order

IC SO - Intercompany Sales order

When this feature is disabled, then requested dates are synchronized in the intercompany flow.

For instance, you create IC PO and IC SO will be created automatically. When you update Requested receipt date on the IC PO, Requested ship date will be updated on the IC SO. The same happens in opposite scenario: you create IC SO and IC PO will be created automatically. When you update Requested ship date on the IC SO, Requested receipt date will be updated on the IC PO. 

When this feature is enabled, a new parameters will be displayed:

• Go to Accounts payable > Vendors > All vendors
• Select General tab on the Action pane
• Select Intercompany in the Set p section

On the Purchase order policies and Sales order policies, you will notice new parameter.

Name: Disable requested ship and receipt dates synchronization
Help text (Sales policy): Select the option to disable line-level synchronization of updates on Intercompany Sales order requested ship and receipt dates with Intercompany Purchase order requested ship and receipt dates.
Help text (Purchase policy): Select the option to disable line-level synchronization of updates on Intercompany Purchase order requested ship and receipt dates with Intercompany Sales order requested ship and receipt dates.

When parameters are disabled, nothing is changed. Requested dates synchronization will happen upon date changes on the line. 

When Disable requested ship and receipt dates synchronization is enabled only for purchase order policies, then when you update Requested receipt date on the IC PO, requested ship dates will not be updated on the IC SO. But IC PO dates will still be updated if you change requested ship dates on the IC SO, since Sales order policy parameter was not enabled. 

When you enable this parameter for both policies (Sales, Purchase) then no matter where you update the dates, it will not be synchronized. 

That's it!