Versions Compared

Key

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

...

Description

Excerpt

With this feature, registration data is continuously sent to the back-end, every time the user performs registration (no posting needed)


Normally, registrations are stored on the mobile device until posting timethe user posts.

With LiveUpdate the quanity is continiously sent , real-time data can become available to the back-end, before data is posted. (Or when Networks access is re-established)

 

Supported functional areas

  • Pick
  • Put-away

 

Supported data

  • Quantity

 

     

...

Using Android Image Removed

TODO

 

 

 

Using  Windows Image Removed

 

 Modify the app.config file

 

Code Block
languagexml
<liveUpdate>
  <orderLineRegistrations enabled="true" requestDocumentName="RegisterRealtimeQuantity"/>
</liveUpdate>

 

This will send a request to NAV to register realtime-quantities while picking / putting-away putting a record in table 6181373 TF Mobile Realtime Reg. Qty.
This will in turn enable you to do unplanned counts on bins while taking unposted picks/put-aways into account by modifying the code in the "TF Mobile WMS Adhoc Registr.".PostUnplannedCountRegistration function so it takes the Realtime Reg. Qty. into account.

Image Removed

 

 


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.
  • 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



Order is posted

After the request for "Post all registrations" is issued

An additional request is issued to "Delete all registrations" for the entire order

Registrations are continuously cleared from the back-end this way.


How to enable

Step 1

Modify the Mobile Configuration Files

Note the the following:

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


Code Block
languagexml
<!-- 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


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)
showLabelsfalse
showSpacefalse
sorttitle
reversetrue
titleExamples
excerptTypesimple
cqllabel in ("example","integrationevent") and label = "liveupdate"