Description

Normally, registrations are stored on the mobile device until the user posts. This could enable you to perform Unplanned counts while taking unposted picks/put-aways into account 

With LiveUpdate, real-time data can become available to the back-end, before data is posted.

Use cases

• Avoid selling specific Items which are already picked, but not yet posted by the warehouse worker
• Perform unplanned counts while respecting current picks/put-aways

Limitations (Important)

• Unposted data can be changed by the mobile user at any time
• No error is shown on mobile if the request fails ("fire and forget")
  • Any logic that you create for LiveUpdate, must be tolerant of this fact
    
    
• "Variant Code" is not part of Mobile data.
  • However, Order, Line, and Item tracking information is  

Communication with back-end

There are four kinds of mobile requests for LiveUpate. 

A registration is made

Example:

...

• Line quantity is 10 pcs.

• A request is issued after each registration is completed
• When a registration is modified a request with 'clearOrderLines' attribute is issued 

How to enable

• 3 of lot no. A was already picked.
• 7 of lot no. B is now picked.
  
  

All registrations for this one line is sent - including all existing and the one just made.

A registration is deleted

All registrations for this one line is sent - which is information about the line - but empty registrations.

This action is used Image Added

All registrations for entire order are deleted  

A request with the attribute 'clearOrderLines' is sent. 

This action is used Image Added

How to enable

Step 1

Modify the Mobile Configuration File, add Files

Note the the following:

• "operationMode"  = OnlineWithLiveUpdate
• "liveUpdate" = RegisterRealtimeQuantity (Or Choose your own name)

<!-- SERVICES -->


<services>
...
 
<service id="Pick" type="Order" orderType="Pick" operationMode="OnlineWithLiveUpdate">
  <requests>
    <getOrders>GetPickOrders</getOrders>
    <getOrderLines>GetPickOrderLines</getOrderLines>
    <postOrder>PostPickOrder</postOrder>
    <liveUpdate>RegisterRealtimeQuantity</liveUpdate>
  </requests>
</service>

Step 2

...

• Make sure to add a "Mobile Document Type"
  • with the name of your registration type (i.e. 'RegisterRealtimeQuantity' in the example)
  • that is attached to the correct "Mobile Group"'s

Windows Image Removed

 Modify the app.config file

...<!-- Service for managing Pick Orders -->
 
<liveUpdate>
  <orderLineRegistrations enabled="true" requestDocumentName="RegisterRealtimeQuantity"/>
</liveUpdate>

...

Business Central implementation

The “Realtime” registration data is stored in a separate table “MOB Realtime Reg Qty.” as they are received. From here the data for all mobile devices can be accessed from your customization.

These registrations are only stored for validation purposes and never used in the actual posting. The registrations to be posted are still received with the Post-request when posting the document and stored in “MOB WMS Registrations” as usually.

See examples below for more information:

Filter by label (Content by label)
showLabels false showSpace false sort title reverse true title Examples excerptType simple cql label in ("example","integrationevent") and label = "liveupdate"