...
Excerpt |
---|
The Mobile WMS app can be used to register the receiving of items in many different ways in Business Central. |
Column | ||||
---|---|---|---|---|
| ||||
It is the configuration of the location card that determines how the data is transferred to The Location setup will determine how Receiving orders is handled on the mobile device. Overview
|
Column | ||
---|---|---|
| ||
Purchase Orders
...
Receive by Printing and Scanning
We highly recommend printing new Item Labels when you receive items.
You will get the most out of Mobile WMS because all processes can now be scanned using these labels.
The process is:
- Print the label from Receipt-lines
- Scan the label to perform the receipt
This method ensures your registrations and your labels match exactly
Purchase Orders
For customers with simple warehouse requirements and without using the warehouse module, the Mobile WMS app can integrate directly to purchase orders in Business Central.
Purchase orders will be available for Receiving on the mobile device if:
- The location code on the purchase order header is configured NOT to not use Receipts or Put-aways
- The purchase order is released
- The user logged onto the mobile device, is configured to work on this location
This is done on the warehouse employee page
...
- A customer calls in with a complaint about a received product
- The service person creates a sales return order based on the original sales order
- The service person registers the return reason code on the line(s)
Note: The return reason code is set in Business Central and not on the mobile device - The customer then ships the items back
- The items are received using the mobile device
- A credit memo is issued to the customer
Over-receipt
Over-receipt is supported on the mobile device. The Mobile WMS automatically detects if over-receipt is valid for the document line and validates entered quantities accordingly.
You may over-receive when:
...
When more goods arrive than were ordered, you may want to receive them instead of canceling the receipt. For example, it might be cheaper to keep the excess items in inventory than return them,
or your vendor may offer a discount for keeping them. In this release, in addition to Purchase Orders and Warehouse Receipts, you can also use inventory put-away documents to handle over-receipts.
Overreceipt is supported on the mobile device. The Mobile WMS automatically detects if over-receipt is valid for the document line and validates entered quantities accordingly.
You may over-receive when:
- Over-Receipt Code is populated at the document line being displayed on the mobile device
- Over-Receipt setup exists, either as a default Over-receipt Code, or set up by Item or Vendor
...
Mobile: Receive Order filters
Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Mobile: Receive Order list
Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Selecting the right order
The user can use the scanner of the mobile device to select the right order to work on. In the standard setup, the user can scan the barcode of one of the received items. The mobile device will then filter the list of orders to only show the orders containing this item. This will typically result in a very limited set of orders.
Note: The filter functionality when scanning can be changed to allow filtering on any scanned value. E.g. scanning an order reference number.
The order is opened by touching the order line in the list. Whether this needs to be done once or twice, is defined in the configuration file for the mobile device, and the default is to double touch. When the line is opened the order lines are downloaded to the mobile device.
Order locking
The lock symbol, illustrated on the third order, tells the user if someone else is working on the order. If the user selects a locked order, a warning is displayed, telling the user who is working on the order. The locking function is used to prevent unintentionally selecting an order handled by another user. If the user still wants to work on the order after seeing the warning, the order can be opened in the menu by selecting "Release (order no.)" to unlock the order. The menu is opened either by clicking the round blue menu button or by long-pressing on the line.
Menu options
Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Mobile: Receive Order lines
...
An example is if the mobile device is used in an area without wireless network coverage (e.g. inside a container).
Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The expiration date can be changed by touching the current date, which will show a calendar.
Registering Lot numbers
If the item tracking code for the item on the order line has been set up to register Lot numbers then the mobile device will ask the user to enter a Lot number.
The user can either scan or manually register the Lot number, after which the quantity will be requested.
Register serial numbers
...
- The user can either scan or manually register the serial number. When serial numbers are registered the user is not allowed to enter a quantity since a serial number is equal to a quantity of one
- When a serial number is registered the quantity is automatically incremented by one
Registering the quantity
...
Menu options
Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
If tracking like Lot Number, Expiration Date, or Serial Number is predefined on the Purchase order, it is not displayed on mobile.
This is by design, as we recommend a process where items are labeled and then scannedfirst physically labeled and then ready to be handled by scanning.
How Quantity Is Updated
Which value does mobile display as the "Quantity To Handle"?
The value comes from the "Qty. Outstanding"-field.
What happens on posting a Quantity?
On posting the "Qty. to Receive"-field is either:
- Filled with the Quantity from Mobile
or - Zeroed Out
This is done so Mobile will never post any existing/arbitrary value, but always use what is collected from the mobile user.