Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Clarification

Description

Excerpt

Processes performed on Ad-hoc-basis, as opposed to Planned Functions.


Sometimes items gets damaged and the inventory needs to be adjusted. These operations are in other words "unplanned".

Standard Unplanned functions

  • Unplanned Count
  • Unplanned Move

  • Attach Image
  • Add Count Line
  • Adjust Quantity
  • Bulk Move
  • Item Cross Reference
  • Item Dimensions
  • Post Shipment
  • Substitute Items
  • Tote Shipping

Key points

Mobile document flow 


  1. User fills in header and Accepts or Scans

  2. Backend responds with Steps to collect (if any)
    Document Type GetRegistrationConfiguration

  3. User posts the registration (header and steps)
    Document Type
    PostAdhocRegistration




Image Modified

Image Modified

Image Modified

Empty header

Three steps was returned after header was been filled in and accepted


A success message is shown



Document Types

GetRegistrationConfiguration

This request is sent to back-end when header values are accepted.

The backend must return an XML that contains the additional steps to collect before the registration can be posted.

Code Block
languagexml
titleXML Example: Request
<request name="GetRegistrationConfiguration" created="2021-08-06T11:21:30+02:00" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Request">
  <requestData name="GetRegistrationConfiguration">
    <Location>WHITE</Location>
    <Item>1000</Item>
    <RegistrationType>UnplannedCount</RegistrationType>
  </requestData>
</request>


Code Block
languagexml
titleXML Example: Response
<registrationCollectorConfiguration xmlns="http://schemas.taskletfactory.com/MDMF/Platform/Controls/RegistrationCollectorConfiguration.xsd">
    <steps>
        <add id="1"
             header="Enter LOT number"
             helpLabel=""
             inputType="Text"
             label="LOT No."
             length="20"
             name="LotNumber"/>
        <add id="2"
             header="Enter exp. date"
             helpLabel=""
             inputType="Date"
             label="Exp. date"
             name="ExpirationDate"
             minDate="2009-01-01"
             maxDate="2012-12-31"/>
        <add id="3"
             header="Enter quantity"
             helpLabel=""
             label ="Quantity"
             inputType="Integer"
             minValue="0"
             maxValue="150"
             name="QUantity" />
        <add id="4"
             header="Select Location"
             helpLabel=""
             label ="Location"
             inputType="List"
             listValues="Warehouse 1@Warehouse 2@Warehouse 3"
             listSeparator="@"
             name="Location" />
    </steps>
</registrationCollectorConfiguration>

 

PostAdhocRegistration

This request is sent to back-end when header is accepter or, if used, steps are completed.

The backend must return an XML with status=Completed and optionally a success message (description).

Code Block
languagexml
titleXML Example: Request
<request name="PostAdhocRegistration" created="2021-08-06T11:21:43+02:00" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Request">
  <requestData name="PostAdhocRegistration">
    <Location>WHITE</Location>
    <Item>1000</Item>
    <Bin>w-01-0001</Bin>
    <UoM>PCS</UoM>
    <Quantity>1</Quantity>
    <RegistrationType>UnplannedCount</RegistrationType>
  </requestData>
</request>


The response contains:

  • status
    • Completed
    • Error
  • description (optional)
    • A dialog message the user must accept with the "OK" button
    • "Blank" value will result in no dialog at all


Code Block
languagexml
titleXML Example: Response
<?xml version="1.0" encoding="UTF-8"?>
<response xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Response" messageid="A6248127-EB60-4002-81F3-77A8A5D8D25C" status="Completed">
  <description>Unplanned Count for 1000 completed.</description>
</response>


Explore the Mobile WMS App

Page Tree
rootMobile WMS App