Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Landed Cost - How it works in Mobile WMS

Available in Mobile WMS for Dynamics AX/365FO version 3.14 and newer.


Landed cost provides accurate and timely cost estimates for overhead landed costs. At the same time, it provides increased financial and logistical visibility into the extended supply chain. It also helps reduce the administration of costing and costing errors.

Through Mobile WMS you can either receive via goods in transit or directly post product receipts from voyages with purchase orders.

Voyages

Every voyage has at least 1 shipment and 1 purchase order, but you can have multiple purchase orders on the same voyage. Below image illustrates this.



From a processing perspective you can receive the voyage in two ways. Below image illustrates the two paths. 

Goods In Transit Orders

You can generate goods in transit orders, when you have invoiced the purchase orders through a voyage. 

Once the purchase orders are invoiced, the items are received and GIT orders are created to move the on-hand goods to a special warehouse of the type "Goods In Transit".

A standard requirement is the location from the purchase order line has to be present in GIT warehouse. When you receive GIT orders, the items are now available in that specified location they originally were receipt on. 

When GIT orders are created the status is "In transit" and a completed order has status "Finished". 


Below image shows the GIT setup on warehouses. 


Mobile WMS - GIT Orders

Using Mobile WMS to receive GIT orders you will register the required dimensions to ensure posting can be done correctly. 

There are some specialties in Mobile WMS when it comes to some of the dimensions. 

  • Location
  • Batch number
  • Serial number

Location - the location has to exist in both warehouses, so during receipt the user might choose a different location and wants to register it directly to that new location. This is possible in Mobile WMS. What happens is a receipt into the original location and a transfer journal moves the item to the new location. It is an extra transaction due to standard landed cost only offers receipts into the original location. See section afterburner.

Batch number - items with batch numbers must have automatic batch number created for the GIT orders to process. See section afterburner.

Serial number - similar to batch number, the item must have automatic serial numbers created for the GIT orders to process. Mobile WMS empowers the user to register the actual serial numbers when the physical goods arrive. A transfer journal is created to register the transfer of the automatic serial number to the actual registered. See section afterburner.

GIT Created

Standard landed cost creates Goods In Transit Orders when you invoice the voyage. See below image.

During invoicing the goods are received into the receiving warehouse and then automatically moved from here to the GIT warehouse.

GIT Received

At the same time GIT orders are created to cover the transfer back to the original receiving warehouse. When these are eventually posted, the goods are moved back again into the receiving warehouse. See below image.

Afterburner

Mobile WMS provides extra flexibility regarding receipt of goods and their respective dimensions aka. location, batch and serial number.

Location

GIT orders are receipt into the location stated on the purchase order. If you want to register another location you simply do that using Mobile WMS. 

Batch Number

GIT orders are receipt using the automatically created batch numbers. 

To the mobile device user this extra transfer journal does not influence the registration process, and the user can focus on registering and get the job done. 

Serial Number

GIT orders are receipt using the automatically created serial numbers. But with Mobile WMS you are able to register the actual serial number during physical receipt of the goods.

The mobile device user does not see the extra transaction, but only has to register and post. But as you can see on below image, a transfer journal is created and posted with the actual serial numbers. 

Tolerances

When your quantities does not match quantities on GIT orders, an Over/Under Transaction Number is created depending on your tolerances setup. 

The processing of Over/Under Transaction Numbers is typically not a part of the warehouse operations and hence this requires to be processed from the D365FO client.


Post Product Receipt

The biggest difference from a standard purchase order product receipt is the voyage. A voyage can have multiple purchase orders and upon receiving, you can receive on multiple purchase orders. 

Mobile WMS - Post Product Orders

Mobile WMS receives order lines across purchase orders as you would during a normal purchase order. When it comes to posting you must register the product receipt, and here multiple purchase orders could require unique registrations depending on parameter setup. In Mobile WMS you most register a product receipt to keep registrations simplified. If the receipt covers multiple purchase orders, we ensure that the registration gets a postfix to secure unique values regardless of company setup. 

When you receive goods from more than one purchase order, your packing slips must be specified. From Mobile WMS we have simplified the posting process, so instead of asking for a packing slip for each purchase order, we only ask for one. During posting we ensure a unique packing slip, where we use the registered packing slip from the device and add a postfix '_#', where # is an incremental integer. Example given on below image. 


Parameter Setup

In Mobile WMS/Parameters/Documents/Receive Order Handler you find a parameter to suggest batch number. Landed Cost works in a way where you have to setup the batch controlled items to have automatic batch numbering. This is not necessary the way you want to receive your goods, due to registering and labeling items with batch numbers that comes from the vendor. 

When you set the parameter to "Yes", Mobile WMS will receive the items as per usual in Landed Cost, but we have added an afterburner to make a transfer journal in where your just received items will be moved from the autogenerated batch number to the one you have registered during your physical receipt. 


Transfer Orders

Transfer orders is not covered through Mobile WMS.


  • No labels