Skipping TasksYou can skip tasks and task bundles that you either cannot start or do not want to perform. There are three types of skips that can be performed by resources :
Forced skip
Performed when the resource cannot start a task or task bundle, such as when the source bin is inaccessible
Voluntary skip
Performed when the resource receives a task that it currently does not want to perform
Permanent voluntary skip
Performed when the resource receives a task that it does not want to perform at all
You can only force skip those tasks that have been accepted but not yet started (tasks with the status
of 03 Accepted
).
In the case of task bundles, you can only perform a permanent voluntary or voluntary skip on the whole bundle and not specific tasks within the bundle.
From the
Source
screen of a task, choose
Skip
. Th
e Skip
screen appears.
In the case of a task bundle, choose
Bndl
if you want to skip the whole bundle. The
Skip bundle
indicator is set.
Choose
List
to view the list of reasons for skipping the task.
Choose a reason corresponding to the type of skip that you want to perform.
Choose
Ent
. The reason code and description appear in the
Reason
field.
Choose
Cnfr
to skip the task.
The skipped task is given the status of
02 Hold
and appears under Problematic Tasks in the
TRM Alert Monitor
, awaiting managerial action.
In addition:
A force skipped task will not be assigned to any resources.
A voluntary skipped task can be assigned to the original resource after it has completed another task, or any other suitably qualified resource.
A permanent voluntary skipped task cannot be assigned to the original resource while the resource is still active but can be assigned to any other suitably qualified resource.
Note
For more information on how warehouse managers can handle skipped tasks, see:
See Also: