Using the mobile client to change location or status WHS AX 2012 R3.

You can create work to instruct a warehouse worker to move inventory from one location in the warehouse to another – but you can also create a mobile client menu item that allows a worker to perform an un-planned move (or to change the inventory status on some on-hand inventory).

Create yourself a Mobile device menu item. Warehouse management > Setup > Mobile device > Mobile device menu items:


You need a mobile device menu item Mode = Work; don’t tick ‘Use existing work’; set the ‘Work creation process’ = Movement.

Add the menu item to a Mobile device menu. Warehouse management > Setup > Mobile device > Mobile device menu:

I’ve logged on to the mobile client, and here’s my menu:

Movement gives:

Enter Location and item or LP. OK gives:

Enter from batch number, Quantity, Unit and Inventory status. OK gives:

Confirm unit. OK gives:

Enter inventory status. OK gives:

Confirm. OK gives:

Careful – up until now we were confirming the ‘From’ information’, Here we’re entering the ‘To’ status and location. OK gives:

And we’re done.

WHS product receipt data capture with a Work audit template in AX 2012 R3.

So I guess you’re familiar with the product receipt and put-away workflow in Microsoft Dynamics AX 2012 R3 Advanced warehousing (WHS). But I never like to take things for granted, so let’s create a purchase order for a WHS warehouse. Procurement and sourcing > Common > Purchase orders > All purchase orders:


For reasons that I’ll explain later, we need to use the two stage product receipt process. First we perform a warehouse product receipt using a mobile device menu item like this. Warehouse management > Mobile device > Mobile device menu item:


And then we perform the put-away work using a mobile device menu item like this:


So let’s do the product receipt:






The system’s generated a licence plate and registered our purchase order line into the default purchase order receipt location for the warehouse:


And of course we now have put-away work to perform in the warehouse. Warehouse management > Common > Work > Open purchase work:


 

So let’s perform that work:






And our work is done:


Now let’s create a work audit template that will capture the vendor’s delivery note number. Warehouse management > Setup > Work > Work audit template:


That setup is pretty self-explanatory. I’m triggering this event before I do any work on a new WorkId, and I’m capturing one data field. Notice that I have the option of entering a custom method to process the data I capture, but that’s way beyond my level of competence.

Now add that to the Purchase order put-away Mobile menu item. Warehouse management > Mobile device > Mobile device menu item:


Now let’s perform the purchase order item receiving as before and generate our put-away work, and again perform the put-away work:



And the work audit template triggers a data capture form:


OK, and we’re back to our pick/put flow:


The data’s written to a table found at Warehouse management > Inquires > Work audit data capture:


And as you can see I experimented with a multi-line data capture (three fields in the same workflow) and that worked just fine.

The only issues I’ve had setting this up were that I’d really like to perform this data capture at the Purchase order item receiving step – but there’s no option to add the work audit template to that menu option. And I tried adding the Work audit template to the Mobile menu item that does the combined purchase order item receiving and put-away work, and got a stack trace error. However those are minor issues, and I guess easy to fix.

So why did I choose to capture the vendor delivery note number? Well in an earlier post

https://timsaxblog.wordpress.com/2015/07/15/automatic-product-receipt-in-whs-ax-2012-r3/ I setup automatic product receipt job in WHS and found that I’d lost the option to capture the vendor delivery note, but that which was lost is now found.

Confirm the outbound shipment automatically in WHS (AX 2012 R3)

I needed help with this – and I’d like to acknowledge John Foster of Blue Horseshoe who very kindly sent me a very detailed e-mail after I to a posted a question on the AXUG forum; and Nataliia Sukhanova of Intergen who noticed the subtle difference between two Mobile menu items.

So, let’s try and do a really simple sales order pick, pack and despatch workflow in a WHS (Advanced warehouse processes) warehouse.

First we’re going to set a couple of parameters so that we automatically reserve inventory at sales order entry when we run the batch job to release sales orders. We need a ‘Fulfilment rate’. Accounts receivable > Setup > Accounts receivable parameters > Warehouse management:


And we need to set a parameter on the warehouse so that the inventory’s reserved to the sales order line when we run the ‘Automatic release of sales orders’ batch job in Warehouse management. Warehouse management > Setup > Warehouse setup > Warehouses:


So, here’s my sales order. Sales and marketing > Common > Sales orders > All sales orders:


Now run the job to release the sales order work to the warehouse (and create the load and shipment). Warehouse management > Periodic > Automatic release of sales orders:


And we get work. Warehouse management > Common > Work > Open sales work:


Do the work, and now we can go to the shipment and print the packing slip. Warehouse management > Common > Shipments > Active shipments:


Except that, of course we can’t post the sales order packing slip from the shipment, because we haven’t confirmed the outbound shipment.

Now I can imagine an environment where you would want to put in an additional process step at this point (because for instance, in New Zealand when you transport plant or animal products they must often be accompanied by the appropriate certification issued by the Ministry for Primary Industries – and you’d want to check that this certification was in place before completing the sales order delivery). But there are also implementations where you’d consider that this additional step didn’t add any value – and you’d want to automate it.

To do that, we’re going to use the scary sounding ‘Work audit template’. Go to Warehouse management > Setup > Work > Work audit template and create a new one like this:


In case the screen-shot isn’t clear, the settings I’ve used are:

Audit template ID:    AutoConfShipment
Description:        Automatically confirm outbound shipment
Audit trigger field:    WorkId
Audit trigger event:    Status change
Break status:        Loaded
Line > Function:        Event
Line > Event:        Shipping confirmed

We need to link this to the mobile client menu item that’s used to perform the pick, If you want to test this yourself – and if you don’t why are you still with me – make sure you use ‘User directed’ sales picking, Warehouse management > Setup > Mobile device > Mobile device menu items:


 

Now let’s run through the sales order pick cycle shown above again, after completing the Pick work this is what we see on the Shipment. Warehouse management > Common > Shipments > Active shipments:


And the reason for this, is of course that the Shipment has been automatically confirmed and it’s now ready for posting the packing slip:


We’re not quite done with this – because I haven’t figured out how to display a list of shipments which are ready for packing slip posting; and also I found that you have to use a ‘User directed’ sales picking step. If you use a Mobile menu item which is ‘System directed’, the automatic shipment confirmation doesn’t happen (at least not in the demo AX 2012 R3 CU8 hyper-v image).

Incidentally, I’ve also tried this with the slightly simpler Work audit template setup like this:


And that also works.

The Work audit template also provides the mechanism for customising warehouse management workflows (you set Function = Custom, and define the ‘Custom method), but I’m afraid that’s outside the scope of this blog.