Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Order processing

The Mobile WMS application can be used to handle Receive / PutAway / Pick / Count / Move orders.

Each order type is basically handled in the same way and the flow of messages between the mobile device and the ERP system is seen below.

Image Removed

 

 

When the mobile device sends a request for order data it expects the following data per order:

...

The data above is the only order information needed by the Mobile WMS application.

Displaying Order Information

The standard ”Order List” screens are configured to show three lines of text for each order. Here you present the information that the user will use to identify the correct order. The values on the 3 lines are controlled by the content of DisplayLine1+2+3.

 

When an order is selected the user is transferred to the ”Order Lines” screen. In the top of the ”Order Lines” screen there are two lines to display information about the selected order. These values are controlled by the values in the HeaderLabel/Value elements.

 

Example XML

Code Block
languagexml
<?xml version="1.0" encoding="utf-16"?>
<response messageid="4d932552-7394-45a6-89f0-011532c65912" status="Completed" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Response">
  <description />
  <responseData>
    <BaseOrder xmlns="http://schemas.taskletfactory.com/MobileWMS/BaseDataModel">
      <BackendID>WM000001</BackendID>
      <Status>1</Status>
      <Sorting>0</Sorting>
      <DisplayLine1>WM000001</DisplayLine1>
      <DisplayLine2>No. of lines:4</DisplayLine2>
      <DisplayLine3>WHITE</DisplayLine3>
      <HeaderLabel1>Order No.</HeaderLabel1>
      <HeaderLabel2 />
      <HeaderValue1>WM000001</HeaderValue1>
      <HeaderValue2 />
    </BaseOrder>
  </responseData>
</response>

 

...

Example

Code Block
languagexml
<page id="Receive" type="OrderList" icon="mainmenureceive">
  ...
  <orderListConfiguration automaticOrderSelectionAfterFilter="true">
    <service id="Receive" />
    <filter configurationKey="ReceiveOrderFilters" />
    <list listId="Orders" />
    <onOrderSelected navigateTo="ReceiveLines" />
    <unlockOrder title="Release {BackendId}"/>
  </orderListConfiguration>
</page> 

Sections

orderListConfiguration

Configuration for the OrderList page type

  • automaticOrderSelectionAfterFilter

    • Automatically selects the order if only one exists.


service

Defines which service to use.

  •  id

    • Reference to a service defined in the services section.


filter

Defines which filter to use.
  • configurationKey

    • The key used to locate the filter configuration in the reference data

  • enabled

    • Toggles the enabled state of the filter

  • automaticAcceptOnOpen

    Define if values in the header should be accepted on page open 
    • True: Header is applied and disappears automatically (Default)
    • False: Header stays open

Use this property to force users to validate filters before fetching Orders.

Legacy names: automaticAcceptOnStartup, updateOnActivate
 

  • automaticAcceptAfterLastScan

    • Accept the header when a scan causes the last mandatory field to be filled out


list

Defines which list to use for displaying data. 

  • listId

    • Reference to a list defined in the lists section.


registerOrder

Enabling this, allows the user to register an entire order with the default values provided by the order lines

Register all order lines in one action (registerOrder postAllOrders)


postAllOrders

If enabled the post all orders option will appear in the menu. The default text for the menu item is 'Post Orders'.

Register all order lines in one action (registerOrder postAllOrders)


onOrderSelected

Defines which action to take when an order is selected in the list.

  • navigateTo

    • Reference to a page used to display order lines


unlockOrder

Unlock an order locked by an other user. 

  • enabled

    • Toggles the enabled state

  • title

    • The title used in the action menu.