Features of Advance warehouse in MS Dynamics AX R3 -
The
devices we see deployed with the advanced warehousing solution are often rugged
industrial equipment, designed to work within the hostile environment of the
warehouse. These often support integrated barcode scanning and can survive the
occasional accidental drop. With an often significant investment in these
devices we wanted to ensure the Microsoft Dynamics warehouse solution works
across the widest possible distribution of devices. We also wanted to ensure
the workflows and capabilities exposed by the mobile device interface were flexible
enough to match the business processes of your warehouse. Thus the entire
interface that is built and rendered on the mobile device is extremely flexible
– with the entire menu system and workflow exposed and extensible both from
within core AX and through partner code.
This blog
post is the first in a two part series that will cover customizing the mobile
device portal. This post will cover the options exposed in Microsoft Dynamics
AX 2012 R3 to build custom mobile workflows for your workforce and how to build
different mobile experiences depending on user and device criteria. The next
blog post will cover the deeper code underpinnings of the mobile device portal
and how it can be extended to expose additional workflow options.
Menu
At the
heart of the mobile device portal interface lies the concept of Menus and
MenuItems. These are configured in AX by navigating to Warehouse Management
-> Setup -> Mobile device. The high level concept of a Menu is simply a
flexible container that can contain both MenuItems as well as other Menus (i.e.
it is a nestable structure). Thus it is possible to construct an interface for
your users that provides exactly the capabilities required for the role they
are assigned. For example, it is possible to build a Menu that only exposes the
outbound picking operations for a certain segment of warehouse workers, and
have a separate menu structure used by the forklift operators for replenishment
operations.
The menu
item interface can be seen below. Menus can be defined in the top section, and
MenuItems can be added to the selected Menu in the lower section from the list
of all available MenuItems in the bottom right list.
MenuItem
Defining
a MenuItem is done in the Mobile device menu item screen – and there are a lot
of options available for configuring the workflow exposed to the end user.
MenuItem – Mode
When
creating a new MenuItem, you first must decide the Mode that this activity will
be operating under. This can be “Indirect” or “Work.” This defines if the
MenuItem will interact and operate on Work in the warehouse (i.e. Work mode),
or if it will support some sort of ancillary process in the warehouse not
directly related to a Work line (i.e. Indirect mode). Selecting the Indirect
mode will cause the UI to display the list of “Activity codes.” This allows the
user to select the non-work related workflow that will execute when this
MenuItem is selected on the mobile device.
Again –
the complete list of activities can be found in the TechNet article, but the
following are a sampling of the possible workflows:
Change warehouse
|
Change the warehouse that a worker is logged on to.
|
Location enquiry
|
View information about all items and quantities for a location.
|
License plate enquiry
|
View the quantity of items on a license plate, and the location of the
license plate.
|
Start production order
|
Start a production order.
|
Changing
the Mode to “Work” will change the UI significantly. It will now be possible to
select the checkbox “Use existing work.” This will configure the MenuItem
workflow to either consume an existing Workline (checked) or to generate a new
set of Work (unchecked). By leaving the checkbox unchecked (i.e. not to use
existing work) the user will be able to define the exact work creation process
required to generate new work through this MenuItem. This is often used when
receiving items and/or starting putaway work.
There are
various options available when defining the work creation process that will get
initiated by this MenuItem. These will differ depending on the exact work
creation process workflow selected – all of the various options are described
in detail in the TechNet article referenced above. All of them are available to
allow you to customize the exact business process that is enabled by the mobile
device user.
Changing
the selection to “Use existing work” will indicate that this MenuItem will
process existing Work lines – and thus must be configured define exactly how
that work should be processed. Again there are a multitude of options available
to configure exactly how the workflow should proceed. In addition, two very important
settings must be configured: how this work is directed, and the work classes
available to process. The Work classes section defines the valid work
that this MenuItem can process; this can be used to restrict access to certain
user roles or to separate processing logic for different types of operations.
The
“Directed by” setting defines exactly how the work will be selected for the
mobile device user. This is a very important setting – as this is how the
system will know what work to assign to a particular user. All of the options
are defined in the TechNet article – these are copied here for convenience:
Option
|
Description
|
None
|
This default value does not process work.
|
System directed
|
Microsoft Dynamics AX controls the type of work that is assigned to a
worker and the sequence in which to perform it.
When you select this option, you can click System-directed
work to open the System-directed sorting order form,
where you can set up sorting criteria for the work. The sorting criteria
control the order in which the worker will perform the work. You can add as
many criteria as needed.
|
User directed
|
The worker selects the work to perform and the sequence in which to
perform it.
|
User grouping
|
The worker manually groups work. For example, this is useful when a
worker can pick multiple items at the same time in a location. After the
worker has finished picking all of the required items, he or she can put the
items away.
|
System grouping
|
Microsoft Dynamics AX groups work for the worker based on a specified
field. For example, picking work is grouped when a worker scans a shipment
ID, load ID, or any value that can link each work unit.
If you select this option, the following fields are required:
|
Validated user directed
|
The worker selects the work to perform when work is associated with a
larger entity, such as a load or shipment. The worker determines the order in
which to pick the items.
If you select this option, you must select the following:
For example, this is useful when multiple pallets are staged for a
load. If you select the LoadId field, the worker can pick
any pallet that is associated with the load. An error message is displayed if
a worker scans an item that is not associated with the load.
|
Cluster picking
|
The worker groups work into clusters. Clusters enable workers to pick
items from a single location for multiple work orders at the same time.
|
Cycle count grouping
|
The worker selects a zone, work pool, or location, and Microsoft
Dynamics AX will assign work based on the selection.
If you select this option, you can also click Cycle counting to
specify additional information to display, and specify the number of times
that the worker must repeat the count if a difference is found.
|
Work Users
In order to access the WMDP one needs to create at least one warehouse
work user, which has a user name, password, default warehouse, and
available mobile menu. In order to create a warehouse work user, a worker
will first need to be defined within the HRM module. The HRM worker is
typically associated with an AX user mapped to an active directory identity
(through user associations defined in the administration module).
After creating the HRM worker, one can assign a number of warehouse
work users to it through the “Worker” form accessed under Warehouse
management -> Setup -> Work users -> Worker. You can think of the
warehouse work users as a number of logins for the selected HRM worker – each
one which can provide a default warehouse and targeted workflow exposed by the
menu. Obviously it is also possible to simple define all your warehouse work
users under a single HRM worker, but this is not the recommended pattern.
A warehouse work user is
defined very simply with a user ID, user name, default warehouse, and a menu.
This menu is loaded when the user logins into the portal, and is how different
experiences can be tailored to different logins. For example, in the screenshot
below we have created separate menus for the UPS drivers, the Forklift
operators, and the primary warehouse workers. Each have a different set of
MenuItems available, specifically only the ones required for them to perform
their jobs effectively.
Mobile Site Customization
CSS Customization
The site
that is created by the configured Menu and MenuItems can be further customized
through a variety of options exposed through Microsoft Dynamics AX. These
options are available through the work user mobile device display settings form
– seen below. This screen allows a CSS file, display settings view, and
keyboard shortcut settings to be defined for a set of criteria. This allows
different displays to be rendered for different types of devices or browsers.
The most
obvious way to customize the mobile site is through CSS customization. The
default css file shipped with the mobile device portal (defaultrf.css) can be
found at <AX Installation directory> \6.3\Warehouse Mobile Devices
Portal\<WMDP Instance folder>\Content\CSS\RFCSS. This file defines the
basic look and feel of the UI and includes things like the background color,
text font and size, and the width and behavior of the rendered buttons. The
default login screen is rendered in the following manner:
The
overall look of the interface is defined by the default css file, which
includes the following settings:
Note the
background color and button colors have been customized, as well as the layout
(100%) of the button and the hover behavior of the buttons. By removing all of
the default css and replacing it with the following simple css, we can
dramatically change the look of the UI:
This is
achieved with the following css file:
body
{
background: #777777;
text-align: center;
}
{
background: #777777;
text-align: center;
}
.whsLabel
{
font-size: 15pt;
color: #FFFFFF!important;
}
{
font-size: 15pt;
color: #FFFFFF!important;
}
.whsTextLabel
{
color: #FFFFFF;
}
{
color: #FFFFFF;
}
.whsPasswordLabel
{
color: #FFFFFF;
}
{
color: #FFFFFF;
}
Note the
requirement for the important keyword in the .whsLabel class definition.
This is because all whsLabels are generated with an embedded color component
defined in the “mobile device text colors” form (or defaulting to black). This
form can be found at Warehouse management -> Setup -> Mobile device ->
Mobile device text colors. Unfortunately this form does not allow criteria
based filtering or customizing on the generated colors, so utilizing the css
styling is the recommended way for updating the text colors.
The
ability to change the look and feel of the generated HTML is more important
than simply wanting a different background color or text color may initially
appear. Different devices used in the warehouse may impose strict limits on
what can or should be displayed for optimal visibility and usability. The need
to specify a specific width or a specific format for buttons may be a
requirement for the specific device utilized in the warehouse, in which case
the css styling is a must for enabling the workflow.
Keyboard shortcuts
Another facility
exposed in the “Work user mobile device display settings” form are keyboard
shortcut definitions. These allow you to customize what hardware keys trigger
different MenuItems. It is possible to map specific buttons to MenuItems such
that when the MenuItem is visible users can press the hardware button to
trigger the functionality on the device. This is often useful for warehouses
when devices are used that have obvious keyboard mappings to specific
functionality in the portal.
The
format for setting up keyboard shortcuts is very specific, and the entered
string must match the required format exactly so as to be registered into the
client-side JavaScript correctly. The required format string for each shortcut
is (note they can be appended together with a semi-colon):
<control
name>(<key name>)=<javascript key code>;
The
control name is the value of the “id” attribute in the generated HTML. This can
be easily found by examining the generated HTML in a browser or developer tool.
The key name is a string value displayed to the user in the button text – this
is designed to help the user understand the available hardware button options.
The JavaScript keycode is the value exposed from the JavaScript
onKeyDown/onKeyUp methods.
An
example keyboard shortcut string is:
Login(L)=76;
Full(F2)=113
This
would cause the “L” hardware button to execute the Login button automatically,
and the “F2″ hardware button execute the Full button. The generated HTML would
inject the key name values into the button text, so the above string would
result in the following pages:
Display Settings View
The last
option available on this form is the “Mobile device display settings view.”
This describes the name of the ASP.NET view file used to render the mobile site
in the server-side ASP.NET application. This file controls how the overall
structure of the HTML is laid out and customizing this functionality is only
recommended if you have serious structural issues with the HTML and JavaScript
that need to be changed for your specific devices. Note that, like the CSS
files, there is a specific directory where these files need to be located so
the IIS application can load them – <AX Installation
directory>\6.3\Warehouse Mobile Devices Portal\<WMDP instance folder>\Views\Execute.
Criteria
All of
the above settings (CSS file, Keyboard shortcuts, and Mobile device display
settings view) can be customized in order to render a different mobile
experience to different devices and/or users. The system uses the criteria
column to determine exactly which settings to load. The criteria column allows
the following attributes of the incoming request to be used to qualify the
different settings rows:
- Requestor IP address
- Requestor Host name
- Request User Agent string
Each of
these values can be examined using a regular expression – any successful match
will cause the specific display settings row to be loaded for that particular
user session. The criteria string must match a specific format, and must
include all three of the criteria options, even if you are only examining one
of these values (wildcards must be specified for the others). The format of the
criteria string must be:
Request.UserHostAddress=<user
host address>|HostName=<user host name>|Request.UserAgent=<user
agent>
Here is
an example of the criteria used to differentiate between two browsers (Opera
and Internet Explorer) based on the UserAgent field. Note the wildcard settings
for the other two criteria options.
The above
settings will enable us to display a different css file to different browsers –
perhaps we are operating with two different classes of machines in the
warehouse each with a different browser and different capabilities. We want to
be able to target a different UI experience to each to ensure our users can be
productive with their specific devices.
Mobile Device Portal Tools
There are
two tools included with the mobile device portal that aim to make the processes
describe above easier to configure. These tools can be found in the initial
screen for the portal (i.e. go to the root URL of the portal).
The “View
codes for keyboard shortcuts” will take you to a simple page that will display
the JavaScript keycode for the hardware key pressed. This would allow you to
test the specific hardware buttons for your devices in order to configure the
keyboard shortcuts described above.
The “View
server configuration for display settings” will show you the current display
settings view selected, as well as the IP address, Host name of the requestor,
and the full User agent string. As described above, these three fields are what
is available to be queried against in the criteria string – so this page can be
used to see exactly what the different values might be for the different
devices in use in your warehouse.
Configure mobile devices for warehouse work [AX 2012]
This topic applies to features in the Warehouse management
module. It does not apply to features in the Inventory
management module. |
·
Process an inquiry or perform an activity, such
as print a label, generate license plate numbers, start a production order, or
quickly look up information about items in a location.
·
Create work that will be performed through
another process. For example, receiving an item for a purchase order can create
put away work for another worker.
·
Perform work that was created by another
process. This is called existing work. For
example, performing put away work that was created when an item was received
for a purchase order.
The procedures in this topic describe how to configure a menu item for each
of these activities.
|
Depending on the mode that you select for the menu item, and if the menu
item is used to perform existing work, additional fields are available for the
menu item. These include required and optional fields for the menu item. For
information about the additional field selections, see the section titled
“Additional menu item options” in this topic. |
Enter the menu item text that is displayed in the
mobile device menu
For all menu items, you must enter the text that is displayed in the mobile
device menu to indicate what the menu item is used for. For example, if the menu
item starts a cycle count, the name and title could be “Cycle Count.” To enter the text that is displayed in the menu, follow these steps:
1. Click
Warehouse management > Setup > Mobile
device > Mobile device menu items.
2. Click
New to create a new menu item.
3. In
the Menu item name and Title fields, enter a
name for the menu item, and the title to display on the mobile device.
Set up a menu item for activities and inquiries
You can configure a menu item to perform general activities or inquiries
that do not create work. For example, these include activities such as
reprinting license plate labels, and inquiries about the items in a location. To set up a menu item to perform general activities or inquiries, follow these steps:
1. Click
Warehouse management > Setup > Mobile
device > Mobile device menu items.
2. Enter
a name and a title for the menu item.
3. In
the Mode field, select Indirect.
4. On
the General FastTab, in the Activity code
field, select the activity or inquiry that the menu item will perform. The
following table describes the activities and inquiries that are available.
Options
|
Description
|
||
None |
This default value does not enable an activity or inquiry. |
||
About |
View information about the system, such as the version number, warehouse
ID, and the worker who is currently logged in. |
||
Change warehouse |
Change the warehouse that a worker is logged on to. |
||
Location enquiry |
View information about all items and quantities for a location. |
||
License plate enquiry |
View the quantity of items on a license plate, and the location of the
license plate. |
||
Start production order |
Start a production order. |
||
Production scrap |
Enter the quantity of scrap that was created during production for each
bill of materials line. |
||
Production last pallet |
Indicate that the last pallet of items has been produced for a production
order, and that the status of the production order must be updated to
reported as finished by using the Microsoft Dynamics AX 2012 R3 client. The status of the raw materials that were not consumed during production is reverted from Picked to On order, and the items can be returned to inventory. |
||
Item inquiry |
Scan an item to determine where it is in the warehouse. The inquiry
returns all locations and quantities for the scanned item. |
||
Reprint label |
Reprint a license plate label. |
||
License plate build |
Create a parent license plate by combining multiple license plates in the
same location. This is useful if you move multiple license plates at the same
time. After the parent license plate is moved, you must perform a license
plate break before you can pick items from each license plate.
|
||
License plate break |
Break up a license plate build so that you can pick items from the license
plates that were in the build. |
||
Driver check in |
If you’re using Transportation management, register that
a driver has arrived by scanning the outbound load ID, appointment ID, or
shipment ID. This requires that a load is assigned to the appointment, and
that the status of the load is Loaded. |
||
Driver check out |
N/A |
||
Flush number sequence cache |
Delete number sequence numbers from the number sequence cache. This
activity is typically performed by a system administrator to resolve caching
problems when accessed from mobile devices. |
||
Change batch disposition |
Select this check box to allow a worker to specify a batch disposition
code for an item and batch. This selection will update the disposition code
that is specified for the batch. |
||
Display open work list |
This option is only available in Microsoft Dynamics AX 2012 R3 Cumulative
Update 9. It enables you to show a list of work available to a particular
user, and the user can select the work to perform and will be directed to it.
This display is expected to be viewed on tablet devices with screen sizes of
7 inches or more. When you select this option, the Edit query and Field list menu items are enabled. The Edit query form enables you to set up criteria for what work to show on the list. The Field list form is used to select what fields to show in the work list. For example, you may want to reduce the number of fields that are visible to make it quicker for the user to select the most appropriate work item. You can also select how many work records per page should be shown in the Records per page field on the General FastTab. If the Allow users to filter work by transaction type checkbox is selected, the user will see an additional Filter work control on the work list which allows them to filter by transaction type.
|
Set up a menu item to create work for another
worker or process
You can set up a menu item that will create work for another worker after an
initial action is performed on the mobile device. For example, when one worker
uses a mobile device to receive an item, put away work is created for another
worker. To set up a menu item that will create work, follow these steps:
1. Click
Warehouse management > Setup > Mobile
device > Mobile device menu items.
2. Enter
a name and a title for the menu item.
3. In
the Mode field, select Work.
4. On
the General FastTab, in the Work creation process
field, select the process that will generate work. In the following table, the
options are arranged by work order type.
|
||||
Depending on your selection in the Work creation process
field, additional fields are available on the General
FastTab. For a description of each field, see the section titled “Additional
menu item options” in this topic. |
||||
Work order type
|
Option
|
Description
|
||
Purchase order |
Purchase order line receiving |
Register the receipt of a quantity of an item by using the purchase order
number and purchase order line number. Create put away work for another
worker. |
||
Purchase order line receiving and put away |
Register the receipt of a quantity of an item by using the purchase order
number and purchase order line number, and put the items away. The same
worker will perform both actions. |
|||
Purchase order item receiving |
Register the receipt of a quantity of an item for a purchase order by
registering the purchase order number and item number. Create put away work
for another worker. |
|||
Purchase order item receiving and put away |
Register the receipt of a quantity of an item for a purchase order by
registering the purchase order number, and put the item away. The same worker
will perform both actions. |
|||
License plate receiving |
Receive an inbound load by using the license plate ID. |
|||
Load item receiving |
Register the receipt of a quantity for a load by using the load ID. The
item number and product dimensions match the receipt to the purchase order
lines. Create put away work for another worker. |
|||
Load item receiving and put away |
Register the receipt of a load by using the load ID, and put the items
away. The item number and product dimensions match the receipt to the
purchase order lines. The same worker will perform both actions. |
|||
Return order |
Return order receiving |
Register the receipt of a quantity of an item by registering the RMA
number, and create put away work for another worker. |
||
Return order receiving and put away |
Register the receipt of a quantity of an item by registering the RMA
number, and put the items away. The same worker will perform both actions. |
|||
Transfer order |
Transfer order item receiving |
Register the receipt of a quantity of an item, and create put away work
for another worker.
|
||
Transfer order item receiving and put away |
Register the receipt of a quantity of an item, and put the items away. The
same worker will perform both actions.
|
|||
Transfer order line receiving |
Register the receipt of a quantity of an item, and create put away work
for another worker. |
|||
Transfer order line receiving and put away |
Register the receipt of a quantity of an item, and put the items away. The
same worker will perform both actions. |
|||
Production |
Report as finished |
Register a quantity of a finished item that has been finished for a
production. The quantity can be some or all of the quantity that was planned
for production. Create put away work for another worker. |
||
Report as finished and put away |
Register a quantity of a finished item that has been finished for a
production, and put the items away. The quantity can be some or all of the
quantity that was planned for production. The same worker will perform all
actions. |
|||
Kanban |
Indicate that a Kanban is completed, and create put away work for another
worker. |
|||
Kanban put away |
Indicate that a Kanban is completed, and put away the items. The same worker
will perform all actions. |
|||
Inventory |
Movement |
Register that items have been moved from one location to another. The
worker specifies the location that the items are moved from and where they
are moved to. |
||
Quarantine |
Change the status of the on-hand inventory for a license plate or location
to make damaged or missing inventory items unavailable. |
|||
Movement by template |
Move items from one location to another in a semi-automated manner. The
worker selects the location to move items from, and Microsoft Dynamics AX
uses the location directive to determine where to move it to. |
|||
Warehouse transfer |
Register that items have been transferred from one warehouse to another.
This requires that the worker is allowed to perform work in both warehouses.
|
|||
License plate loading |
Use this option when you are setting up your warehouse for the first time.
Scan all of the license plates in all locations in the warehouse. The locations must be license plate controlled. You cannot use this option if Serial number or Batch number are listed above Location in the Inventory reservation hierarchy. |
|||
Cycle count |
Adjustment in |
Increase the quantity of items in inventory. Specify the location, license
plate, item, quantity, unit of measure, and status. |
||
Adjustment out |
Reduce the quantity of items in inventory. Specify the location, license
plate, item, quantity, unit of measure, and status of the inventory. |
|||
Spot cycle counting |
Start a count for a location. The worker must count all items in the
location. When the result of a count is less than the expected quantity, the
missing quantity is considered a loss. |
Set up a menu item to process existing work
To set up a menu item that will process existing work, follow these steps:
1. Click
Warehouse management > Setup > Mobile
device > Mobile device menu items.
2. Enter
a name and a title for the menu item.
3. In
the Mode field, select Work.
4. Select
the Use existing work check box.
5. On
the General FastTab, in the Directed by
field, select the method to use to direct work to the mobile device. The
following table describes the options.
|
|
Depending on your selection in the Directed by field,
additional fields are available on the General FastTab. For
a description of each field, see the section titled “Additional menu item
options” in this topic. |
|
Option
|
Description
|
None |
This default value does not process work. |
System directed |
Microsoft Dynamics AX controls the type of work that is assigned to a
worker and the sequence in which to perform it. When you select this option, you can click System-directed work to open the System-directed sorting order form, where you can set up sorting criteria for the work. The sorting criteria control the order in which the worker will perform the work. You can add as many criteria as needed. |
User directed |
The worker selects the work to perform and the sequence in which to
perform it. |
User grouping |
The worker manually groups work. For example, this is useful when a worker
can pick multiple items at the same time in a location. After the worker has
finished picking all of the required items, he or she can put the items away.
|
System grouping |
Microsoft Dynamics AX groups work for the worker based on a specified
field. For example, picking work is grouped when a worker scans a shipment
ID, load ID, or any value that can link each work unit. If you select this option, the following fields are required:
o
System grouping field –
Select the field that the worker will scan to group the work.
o
System grouping label - Enter
text to inform the worker about what to scan to group the work.
|
Validated user directed |
The worker selects the work to perform when work is associated with a
larger entity, such as a load or shipment. The worker determines the order in
which to pick the items. If you select this option, you must select the following:
o
Validated User Directed Field
– Select the field that the worker will scan to group the work.
o
Validated User Directed Label
- Enter the text that will inform the worker about what to scan when picking
work is grouped by the system.
For example, this is useful when multiple pallets are staged for a load.
If you select the LoadId field, the worker can pick
any pallet that is associated with the load. An error message is displayed if
a worker scans an item that is not associated with the load. |
Cluster picking |
The worker groups work into clusters. Clusters enable workers to pick
items from a single location for multiple work orders at the same time. |
Cycle count grouping |
The worker selects a zone, work pool, or location, and Microsoft Dynamics
AX will assign work based on the selection If you select this option, you can also click Cycle counting to specify additional information to display, and specify the number of times that the worker must repeat the count if a difference is found. |
6. On
the Work classes FastTab, click New.
7. In
the Work class ID field, select the work class to control
access to this task. You can add as many work classes as needed.
Additional menu item options
Additional menu items options are available in the Mobile device
menu items form, depending on the process that you’re configuring the
menu item for. The following table describes these options.
Field
|
Description
|
||
Allow over pick |
This option is only available in Microsoft Dynamics AX 2012 R3 Cumulative
Update 10 or from KB 3107010. Select this option to allow users to over pick sales and transfer orders. The work user also needs to be set up to allow over picking. |
||
Allow splitting of work |
Select this check box to let users put items for a work order into more
than one target license plate. This is useful, for example, when a target
license plate is full and the worker must add the remaining items to another
license plate. The worker can click Full to indicate
that the license plate is full and stop receiving picking work for it. The
put location for the picked items is then displayed, and the picking work
that has already been completed is moved to a new work order. The remaining
picking work for the target license plate stays on the original work order. |
||
Anchoring |
Select this check box to allow workers to specify a location that will
override the suggested staging or loading location. All of the remaining put
away work is directed to the new location. For example, this is useful when a worker is to put items for order 1 in a staging location by Dock 1, but can’t because a previous load hasn’t cleared the location. Rather than waiting for the Dock 1 staging location to become available, the worker decides to use the staging location for Dock 2 instead, and overrides the suggested staging location. The put location for all remaining items for the work order is updated to the Dock 2 staging location. If you select this check box, you must specify whether to anchor by shipment or by load in the Anchor by field. |
||
Anchor by |
If you are using anchoring, you must specify whether you want to anchor by
shipment or by load. |
||
Audit template ID |
Select the work audit template that will interrupt the work process for
this menu item so that another operation can be performed. For example, if
this menu item is for inbound work, the audit template might require that the
worker checks the temperature in the delivery container. The point at which the process is interrupted is specified on the audit template and can be, for example, when work is started or completed, or when its status changes. |
||
Cluster profile ID |
Select the cluster profile to use for cluster picking. The cluster profile
includes settings such as whether to create clusters automatically, the names
of positions and the number of work units they can be assigned, when to break
clusters into individual units, and whether verification is required. This option is available only if Cluster picking is selected in the Directed by field. |
||
Count total item quantity first |
Select this check box to require a worker to count the total quantity
first during a count. If a difference is found, the worker must provide
additional information, such as the license plate number, batch number,
serial numbers, and so on. |
||
Create movement |
Select this check box to enable a worker to create work for a movement
without requiring the worker to perform the work immediately. For example,
this is useful if a quality inspection has been completed, and the inspector
wants the item to be moved from the quality inspection area. |
||
Directive code |
To use a specific location directive, select the directive code that is
associated the location directive. This option is available when you create
work and the work creation process is Movement by template. |
||
Disable cycle count thresholds |
Select this check box to ignore the cycle count thresholds. If you select
this check box, cycle count work is not created when threshold values are
exceeded. |
||
Display batch disposition code |
Select this check box to display batch disposition codes. For example, you
can display batch disposition codes when you receive a returned batch. This
will enable workers to evaluate the status or quality of a batch, and select
the appropriate code. The rules on the batch disposition code determine
whether the batch will be available to other warehouse processes. If you do not select this check box, one of the following is used:
·
If you receive a new batch number, the default
batch disposition code that is specified on the item model group is used.
·
The batch disposition code that is already
assigned to the batch is used.
|
||
Display disposition code |
Select this check box to display disposition codes. For example, display
disposition codes when receiving return items. This will enable workers to
evaluate the status or quality of the items, and select the appropriate code.
The rules on the disposition code determine whether the items will be
available to other warehouse processes. |
||
Display inventory status |
Select this check box to display the status of items in inventory. This option is available for all menu items that use
existing work, except cycle counting. |
||
Display summary of pick screen |
Select this check box to display a summary of picking work for the
selected work order. The summary is displayed until the first work line is
processed for the work order. |
||
Generate license plate |
Select this check box to generate a unique license plate number based on
the number sequence selection. For example, you can generate a license plate
number for items received for purchase orders. |
||
Group put away |
Select this check box to group the put away work. This option is available
when the work was grouped either by the worker or by Microsoft Dynamics AX.
When the worker finishes all of the picking work in the group, put away work
is created for the same group. |
||
Inventory adjustment types |
Select the inventory adjustment type that determines the inventory
counting journal that is used to post the adjustment, and whether to remove
reservations. This option is available only for the Adjustment in
or Adjustment out work creation processes. |
||
Override batch number |
Select this check box to allow workers who are reporting a quantity as
finished for a production order to enter a batch number that differs from the
batch number that is assigned to the production order. |
||
Override license plate during put: |
This option is only available in Microsoft Dynamics AX 2012 R3 Cumulative
Update 10 or from KB 3107010. Select this option to allow the warehouse worker to override the target license plate from the work order, when performing a put operation. For example, this is useful when the warehouse worker wants to place some items on an existing pallet instead of using the target license plate from the work order. The warehouse worker can create a new target license plate or place the items on a license plate that already exists for the location. |
||
Override target license plate |
Select this check box to allow workers to specify a target license plate
number that differs from the suggested target license plate. Use this option when the first pick for a work order is for the entire quantity of an item on a license plate. For example, this is useful when reusing a pallet. |
||
Pick and pack |
Select this check box to allow workers to combine work for a sales order
or load into a single work unit. The worker can perform work only for the
sales order or load. For example, this is useful when you must increase a
quantity for a sales order after the load, shipment, and work has been
created for the sales order. This option is available when the menu item uses existing work, and the work is directed by the user or system. |
||
None |
Indicate if the worker must pick the oldest batch in a location first. The
following options are available:
·
None – The worker can pick
any batch in the location. No message is displayed.
·
Warn – The worker can pick
any batch in the location, but a warning message is displayed if a batch is
not the oldest.
·
Force – The worker must pick
the oldest batch in the location. An error message is displayed if a batch is
not the oldest.
|
||
Print label |
Select this check box to allow workers to print license plate labels. |
||
System grouping field |
Select the field that will determine how Microsoft Dynamics AX will group
picking work for worker. For example, if you select the ShipmentId
field, the worker will scan the shipment ID to group the picking work. All
work for the shipment is then assigned to the worker. This requires that you create a menu item to use existing work that is grouped by the system. You must also enter text in the System grouping label field to show the worker what to scan. |
||
System grouping label |
Enter the text that will inform the worker about what to scan when picking
work is grouped by Microsoft Dynamics AX. For example, if you are using the ShipmentId field to group picking work by shipment, you
might enter Shipment ID in the field. This requires that you create a menu item to use existing work that is grouped by the system. You must also select the field to group by in the System grouping field field. |
||
Use default data |
Select this check box to enable the Default data button,
where you can select fields to display data that a worker typically needs in
their daily work. For example, this is useful if a worker often picks items
from the same location. You can select the From location
field to display the location by default. |
||
Validated User Directed Field |
Select the field that the worker will scan to group the work. For example,
if you select LoadId, a worker can pick any work
that is associated with a selected load. You must also enter text in the Validated User Directed Label field to show the worker what to scan. |
||
Validated User Directed Label |
Enter the text that will inform the worker about what to scan when picking
work is grouped by a validated user directed field. For example, if you’re
using the LoadId field to group picking work for a
load, you might enter Load ID in the field. |
||
Work template code |
Select the work template that will create the work for a process. For
example, if you are receive an item for a purchase order, the put away work
will be generated based on the work template. If you do not select a work template, Microsoft Dynamics AX will assign a template based on query criteria. |
Require workers to confirm the product, location
or quantity when picking items
You can set up work confirmations that require a worker to use a mobile
device to register the location or quantity when performing work in the
warehouse. This helps to ensure that the worker is at the correct location, or
is handling the correct quantity of items. You can also enable Microsoft
Dynamics AX to automatically confirm the worker’s registration. If you enable
auto-confirmation, you cannot also require confirmations for location or
quantity.
|
If you’ve installed AX 2012 R3 CU8, work confirmations also include
products and product variants. Additionally, you can register confirmations
by scanning a bar code. Work confirmations in earlier versions do not include
products, product variants, or bar code scanning. To confirm products and
product variants, you must enter an ID for the product or product variant.
This can be a product ID, product search ID, external ID, GTIN, or bar code.
After you enter the ID or scan the bar code, the dimensions for the product
variant are displayed on the mobile device. |
1. Click
Warehouse management > Setup > Mobile
device > Mobile device menu items.
2. Select
the menu item, and then click Work confirmation setup.
3. In
the Work type field, select the work process that will use the
confirmation.
Option
|
Description
|
Pick |
Require confirmation when picking items. |
Put |
Require confirmation when putting items in a location. |
Counting |
Require confirmation during cycle counting. |
Adjustments |
Require confirmation when adjusting inventory quantities. |
Custom |
Require confirmation for custom work. |
Quarantine |
Require confirmation when moving items to quarantine. |
License plate building |
Require confirmation when consolidating the items to build a license
plate. |
Print |
Require confirmation when printing license plate labels. |
Status change |
Require confirmation when changing the status of inventory. |
4. Select
the confirmation that you want to require.
|
You can only require product confirmation for pick and put work types. |
Thank you For sharing the Best Blog.
ReplyDeleteMicrosoft Dynamics AX Online Training
Thanks for your informative blog!!! Keep on updating your with such awesome information.
ReplyDeleteD365 Finance and Operations Online Training
Thanks for delivering a good stuff related to SharePoint, Explanation is good, Nice Article.
ReplyDeleteMS Dynamics Trade and Logistics Online Training
Microsoft Dynamics Operations Trade and logistics Training
Microsoft Dynamics operations Trade and Logistics
MS Dynamics Trade and Logistics Training
MS Dynamics Operation Trade and Logistics Training
Thank you for sharing wonderful information with us to get some idea about that content. Thank you for sharing wonderful information with us to get some idea about it. Thank you for sharing any good knowledge and thanks for fantastic efforts.
ReplyDeleteoracle training in chennai
oracle training institute in chennai
oracle training in bangalore
oracle training in hyderabad
oracle training
oracle online training
hadoop training in chennai
hadoop training in bangalore