Description

Unplanned function

Examples of unplanned operations 

It could be items gets damaged and the inventory needs to be updated. It could also be moving an item from one shelf to another.

The Mobile WMS application supports unplanned registrations through the ”Unplanned Item Registration” screen. This screen can be configured to handle many types of registrations. The typical work flow using the ”Unplanned Item Registration” screen is:

1. Activate the feature
2. Show the header values (configuration downloaded during login) [populate combo boxes with reference data]
3. The user enters / selects the values and accepts them
4. The values are sent to Dynamics NAV and it returns the additional registration steps that must be performed for the selected header values (e.g. if an item is lot tracked then the lot number must be registered)
5. The user goes through the registrations steps and scans / enters the values
6. The user posts the registration
7. The registration is sent to Dynamics NAV where it is posted
8. The screen is now ready for a new registration

GetRegistrationConfiguration

This message is sent to the Dynamics NAV when the user presses the button to accept the header values. adjusted. 

How unplanned functions operate

• Unplanned functions always use a Header
• Optionally follwed by one or more Steps

The logic is to ask for one of more information in the header and use that to generate the steps.

Standard Unplanned functions

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

Key points

• Often used for custom functions. See How-to: Create custom Unplanned function in Main Menu
• A Header is always used
• Based on the header input, steps can be used to collect additonal information (optional)
• Can be combined with the result from Lookup Functions to create a powerful customized function. See Page Navigation

Mobile document flow 

Image Added

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

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 registration steps to perform collect before the registration can be posted.

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

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

XML schema explanation

In the <steps> element you can add the steps you need to complete the registration. The step attributes are explained here.

• id [int]
  The id must be unique. It controls the order in which the steps are handled.
• header [string]
  The text displayed in the
• label [string]
  The text displayed before the input field
• helpLabel [string]
  Optional help text displayed below the input field
• inputType [string]
  The inputType determines the type of the input. At the moment there are four input types allowed:
  - Date
  - Integer
  - List

- Text

• length [int]
  This attribute is only relevant for text inputs. The maximum length of the text is limited to this value.

• listValues [string]

This attribute is only relevant for list inputs. The values which will populate the list. Separated by the separator character or string as described below.

• listSeparator [string]

This attribute is only relevant for list inputs. The character or string that separates the list values. Defaults to ‘;’

• minValue [int]
  This attribute is only relevant for integer inputs. The entered value cannot be lower than this value.
• maxValue [int]
  This attribute is only relevant for integer inputs. The entered value cannot be higher than this value.
• minDate [date]
  This attribute is only relevant for date inputs. The entered date cannot be before this date.
  The date must have this format: yyyy-MM-dd
• maxDate [date]
  This attribute is only relevant for date inputs. The entered date cannot be after this date.
  The date must have this format: yyyy-MM-dd
• name [string]
  This attribute sets the name of the element that will hold the registered value when the user posts the registration.

PostAdhocRegistration

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

<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

<?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>