HighJumpTM Warehouse

Advantage
Functional Description
Version 13.9
HighJump

(800) 328–3271

5600 W 83rd Street, Suite 600, 8200 Tower, Minneapolis, Minnesota 55437

www.highjump.com

support@highjump.com

© Copyright 2005–2019 HighJump. All Rights Reserved. Reproduction and distribution under license only.

This document and the software it describes are confidential and proprietary information of HighJump and its affiliated
entities and are copyrighted properties of HighJump with all rights reserved. Information contained herein is subject to
change at any time in HighJump’s sole discretion. Neither this information nor the software may be copied in whole or in
part without the prior written consent of HighJump.

This documentation and the related software programs are “commercial computer software” and “commercial computer
software documentation” pursuant to DFAR Section 227.7202 and FAR Section 12.212 (and any successor sections).
Use of this documentation or the related software programs, including reproduction and display of them, by the United
States of America and/or any of its instrumentalities, regardless of form, (collectively, the “Government”), is allowed only
as governed by terms of a valid license agreement with HighJump or one of its affiliated companies. Under no
circumstances shall HighJump be obligated to comply with any Government requirements regarding cost or pricing data
or cost accounting requirements. If any Government requirement might apply, you must notify HighJump of the
Government requirement and obtain a waiver or exemption for the benefit of HighJump before you may use this
documentation or the related software programs.

HighJump® is a trademark of HighJump Software Inc. All other marks are the property of their respective owners.
Table of Contents

Introduction .................................................................................................................................1
Recommended Resources ....................................................................................................................... 1
Contact Information .................................................................................................................................. 1
Documentation Feedback ......................................................................................................................... 1
Third-Party Logistic Providers .................................................................................................................. 1

Interleaving ..................................................................................................................................2
Interleave Groups ..................................................................................................................................... 2
Processes ............................................................................................................................................. 2
Age/Priority Thresholds ........................................................................................................................ 2
Interleave Types ................................................................................................................................... 3

Authentication .............................................................................................................................5
Windows Security Hybrid Authentication .................................................................................................. 5
Pre-requisite ......................................................................................................................................... 5
RF Password Security .............................................................................................................................. 6
Process Details ..................................................................................................................................... 6
Interface Requirements ........................................................................................................................ 6
Reporting/Labeling Requirements ........................................................................................................ 6
Configuration Requirements ................................................................................................................. 6
Equipment Audit ....................................................................................................................................... 7
Process Details ..................................................................................................................................... 7

Universal Quantity Prompting ................................................................................................... 8

Count ........................................................................................................................................................ 8
Default Quantity ........................................................................................................................................ 8
No UOM .................................................................................................................................................... 9
Receipt ...................................................................................................................................................... 9
Request .................................................................................................................................................. 10

Employee Input Log .................................................................................................................. 11

Receiving ...................................................................................................................................12
Unload Inbound Order ............................................................................................................................ 13
Process Details ................................................................................................................................... 13
Interface Requirements ...................................................................................................................... 13
Reporting/Labeling Requirements ...................................................................................................... 14
Configuration Requirements ............................................................................................................... 14
ASN Receipt ........................................................................................................................................... 14
Process Details ................................................................................................................................... 14
Interface Requirements ...................................................................................................................... 16
Reporting/Labeling Requirements ...................................................................................................... 16

HighJump Warehouse Advantage Functional Description i

 Configuration Requirements ............................................................................................................... 16
Receipt of Inbound Order ....................................................................................................................... 17
Process Details ................................................................................................................................... 17
Interface Requirements ...................................................................................................................... 20
Reporting/Labeling Requirements ...................................................................................................... 20
Configuration Requirements ............................................................................................................... 20
Close Inbound Order .............................................................................................................................. 21
Process Details ................................................................................................................................... 21
Interface Requirements ...................................................................................................................... 21
Reporting/Labeling Requirements ...................................................................................................... 21
Configuration Requirements ............................................................................................................... 21
Staged Receipt ....................................................................................................................................... 22
Process Details ................................................................................................................................... 22
Interface Requirements ...................................................................................................................... 25
Reporting/Labeling Requirements ...................................................................................................... 25
Configuration Requirements ............................................................................................................... 25
Receipt of Shipment ............................................................................................................................... 26
Process Details ................................................................................................................................... 26
Interface Requirements ...................................................................................................................... 29
Reporting/Labeling Requirements ...................................................................................................... 29
Configuration Requirements ............................................................................................................... 29
Adjust Receipt of Shipment .................................................................................................................... 30
Process Details ................................................................................................................................... 30
Interface Requirements ...................................................................................................................... 32
Reporting/Labeling Requirements ...................................................................................................... 32
Configuration Requirements ............................................................................................................... 32
Unknown Receipt.................................................................................................................................... 33
Process Details ................................................................................................................................... 33
Interface Requirements ...................................................................................................................... 34
Reporting/Labeling Requirements ...................................................................................................... 34
Configuration Requirements ............................................................................................................... 34
Warehouse Transfer In ........................................................................................................................... 35
Process Details ................................................................................................................................... 35
Interface Requirements ...................................................................................................................... 36
Reporting/Labeling Requirements ...................................................................................................... 37
Configuration Requirements ............................................................................................................... 37
Miscellaneous Return ............................................................................................................................. 38
Process Details ................................................................................................................................... 38
Interface Requirements ...................................................................................................................... 39
Reporting/Labeling Requirements ...................................................................................................... 40
Configuration Requirements ............................................................................................................... 40
Receipt from Production ......................................................................................................................... 41
Process Details ................................................................................................................................... 41
Interface Requirements ...................................................................................................................... 43
Reporting/Labeling Requirements ...................................................................................................... 43
Configuration Requirements ............................................................................................................... 43
Reusable Container Receipt ................................................................................................................... 44
Process Details ................................................................................................................................... 44

ii HighJump Warehouse Advantage Functional Description

 Interface Requirements ...................................................................................................................... 44
Reporting/Labeling Requirements ...................................................................................................... 44
Configuration Requirements ............................................................................................................... 44
Directed Receipt ..................................................................................................................................... 45
Process Details ................................................................................................................................... 45
Interface Requirements ...................................................................................................................... 48
Reporting/Labeling Requirements ...................................................................................................... 48
Configuration Requirements ............................................................................................................... 48
Directed Put-Away .................................................................................................................................. 49
Put-Away Level 1 Process Details ..................................................................................................... 49
Put-Away Level 2 Process Details ..................................................................................................... 53
Put-Away Level 3 Process Details ..................................................................................................... 58
Pick Plan for Put-Away ....................................................................................................................... 61
Interface Requirements ...................................................................................................................... 61
Reporting/Labeling Requirements ...................................................................................................... 61
Configuration Requirements ............................................................................................................... 61
VAS Execute ........................................................................................................................................... 62
Process Details ................................................................................................................................... 62
Interface Requirements ...................................................................................................................... 66
Reporting/Labeling Requirements ...................................................................................................... 66
Configuration Requirements ............................................................................................................... 66

Movement ..................................................................................................................................67
Directed Pickup....................................................................................................................................... 67
Process Details ................................................................................................................................... 67
Interface Requirements ...................................................................................................................... 70
Reporting/Labeling Requirements ...................................................................................................... 70
Configuration Requirements ............................................................................................................... 70
Move ....................................................................................................................................................... 71
Process Details ................................................................................................................................... 71
Interface Requirements ...................................................................................................................... 73
Reporting/Labeling Requirements ...................................................................................................... 73
Configuration Requirements ............................................................................................................... 74
Request an Item ..................................................................................................................................... 74
Process Details ................................................................................................................................... 75
Interface Requirements ...................................................................................................................... 76
Reporting/Labeling Requirements ...................................................................................................... 76
Configuration Requirements ............................................................................................................... 76
Create Pickup ......................................................................................................................................... 77
Process Details ................................................................................................................................... 77
Interface Requirements ...................................................................................................................... 77
Reporting/Labeling Requirements ...................................................................................................... 77
Configuration Requirements ............................................................................................................... 77
Replenishment ........................................................................................................................................ 78
Process Details ................................................................................................................................... 78
Interface Requirements ...................................................................................................................... 79
Reporting/Labeling Requirements ...................................................................................................... 79
Configuration Requirements ............................................................................................................... 79
Directed Move ......................................................................................................................................... 79

HighJump Warehouse Advantage Functional Description iii

 Execute Planned Move ........................................................................................................................... 80
Process Details ................................................................................................................................... 81
Allocation Process to Find a Pick Location ........................................................................................ 88
Troubleshooting .................................................................................................................................. 88
Interface Requirements ...................................................................................................................... 88
Reporting/Labeling Requirements ...................................................................................................... 88
Configuration Requirements ............................................................................................................... 88
Execute Planned Move Pickup ............................................................................................................... 89
Process Details ................................................................................................................................... 89
Interface Requirements ...................................................................................................................... 89
Reporting/Labeling Requirements ...................................................................................................... 89
Configuration Requirements ............................................................................................................... 89

Picking .......................................................................................................................................90
Bulk Pick by Wave .................................................................................................................................. 90
Process Details ................................................................................................................................... 90
Interface Requirements ...................................................................................................................... 99
Reporting/Labeling Requirements .................................................................................................... 100
Configuration Requirements ............................................................................................................. 100
Bulk Pick by Load ................................................................................................................................. 101
Process Details ................................................................................................................................. 101
Interface Requirements .................................................................................................................... 109
Reporting/Labeling Requirements .................................................................................................... 109
Configuration Requirements ............................................................................................................. 109
Order Picking ........................................................................................................................................ 110
Process Details ................................................................................................................................. 110
Interface Requirements .................................................................................................................... 118
Reporting/Labeling Requirements .................................................................................................... 119
Configuration Requirements ............................................................................................................. 119
Batch Picking by Order ......................................................................................................................... 119
Process Details ................................................................................................................................. 119
Interface Requirements .................................................................................................................... 130
Reporting/Labeling Requirements .................................................................................................... 130
Configuration Requirements ............................................................................................................. 130
Batch Picking by Container .................................................................................................................. 131
Process Details ................................................................................................................................. 131
Interface Requirements .................................................................................................................... 140
Reporting/Labeling Requirements .................................................................................................... 140
Configuration Requirements ............................................................................................................. 140
Pick/Pass by Order ............................................................................................................................... 141
Assumption ....................................................................................................................................... 141
Process Details ................................................................................................................................. 141
Interface Requirements .................................................................................................................... 149
Reporting/Labeling Requirements .................................................................................................... 149
Configuration Requirements ............................................................................................................. 149
Label Picking—Confirm by Label ......................................................................................................... 150
Process Details ................................................................................................................................. 150
Interface Requirements .................................................................................................................... 150
Reporting/Labeling Requirements .................................................................................................... 151

iv HighJump Warehouse Advantage Functional Description

 Configuration Requirements ............................................................................................................. 151
Label Picking—Confirm by Batch ......................................................................................................... 151
Process Details ................................................................................................................................. 151
Interface Requirements .................................................................................................................... 152
Reporting/Labeling Requirements .................................................................................................... 152
Configuration Requirements ............................................................................................................. 152
Warehouse Transfer Out ...................................................................................................................... 152
Process Details ................................................................................................................................. 152
Interface Requirements .................................................................................................................... 156
Reporting/Labeling Requirements .................................................................................................... 156
Configuration Requirements ............................................................................................................. 156
Miscellaneous Issue ............................................................................................................................. 157
Process Details ................................................................................................................................. 157
Interface Requirements .................................................................................................................... 161
Reporting/Labeling Requirements .................................................................................................... 161
Configuration Requirements ............................................................................................................. 161
Reprint Packing Slip ............................................................................................................................. 162
Process Details ................................................................................................................................. 162
Interface Requirements .................................................................................................................... 162
Reporting/Labeling Requirements .................................................................................................... 162
Configuration Requirements ............................................................................................................. 162

Shipping...................................................................................................................................163
Packing ................................................................................................................................................. 164
Process Details ................................................................................................................................. 164
Interface Requirements .................................................................................................................... 167
Reporting/Labeling Requirements .................................................................................................... 167
Configuration Requirements ............................................................................................................. 167
Post Manifest Container ....................................................................................................................... 168
Process Details ................................................................................................................................. 168
Interface Requirements .................................................................................................................... 168
Reporting/Labeling Requirements .................................................................................................... 168
Configuration Requirements ............................................................................................................. 168
License Plate Audit Check .................................................................................................................... 169
Process Details ................................................................................................................................. 169
Interface Requirements .................................................................................................................... 169
Reporting/Labeling Requirements .................................................................................................... 169
Configuration Requirements ............................................................................................................. 169
License Plate Audit ............................................................................................................................... 170
Process Details ................................................................................................................................. 170
Interface Requirements .................................................................................................................... 171
Reporting/Labeling Requirements .................................................................................................... 171
Configuration Requirements ............................................................................................................. 171
Loading ................................................................................................................................................. 172
Process Details ................................................................................................................................. 172
Interface Requirements .................................................................................................................... 177
Reporting/Labeling Requirements .................................................................................................... 177
Configuration Requirements ............................................................................................................. 177

HighJump Warehouse Advantage Functional Description v

 Load Audit ............................................................................................................................................. 178
Process Details ................................................................................................................................. 178
Interface Requirements .................................................................................................................... 179
Reporting/Labeling Requirements .................................................................................................... 180
Configuration Requirements ............................................................................................................. 180
Unload/Unpick ...................................................................................................................................... 180
Process Details ................................................................................................................................. 180
Interface Requirements .................................................................................................................... 184
Reporting/Labeling Requirements .................................................................................................... 184
Configuration Requirements ............................................................................................................. 184
Shipping ................................................................................................................................................ 185
Process Details ................................................................................................................................. 185
Interface Requirements .................................................................................................................... 187
Reporting/Labeling Requirements .................................................................................................... 187
Configuration Requirements ............................................................................................................. 187
Shipping by Container .......................................................................................................................... 187
Process Details ................................................................................................................................. 187
Interface Requirements .................................................................................................................... 188
Reporting/Labeling Requirements .................................................................................................... 188
Configuration Requirements ............................................................................................................. 188
Reusable Container Shipping ............................................................................................................... 188
Process Details ................................................................................................................................. 188
Interface Requirements .................................................................................................................... 189
Reporting/Labeling Requirements .................................................................................................... 189
Configuration Requirements ............................................................................................................. 189
Reprint Bill of Lading............................................................................................................................. 189
Process Details ................................................................................................................................. 189
Interface Requirements .................................................................................................................... 189
Reporting/Labeling Requirements .................................................................................................... 189
Configuration Requirements ............................................................................................................. 190

Inventory ..................................................................................................................................191
View Inventory ...................................................................................................................................... 191
Process Details ................................................................................................................................. 191
Interface Requirements .................................................................................................................... 192
Reporting/Labeling Requirements .................................................................................................... 192
Configuration Requirements ............................................................................................................. 192
Build Master LP .................................................................................................................................... 192
Process Details ................................................................................................................................. 192
Interface Requirements .................................................................................................................... 193
Reporting/Labeling Requirements .................................................................................................... 193
Configuration Requirements ............................................................................................................. 193
Inventory Adjustment ............................................................................................................................ 193
Process Details ................................................................................................................................. 194
Interface Requirements .................................................................................................................... 198
Reporting/Labeling Requirements .................................................................................................... 198
Configuration Requirements ............................................................................................................. 198
Scrap..................................................................................................................................................... 198

vi HighJump Warehouse Advantage Functional Description

 Process Details ................................................................................................................................. 198
Interface Requirements .................................................................................................................... 199
Reporting/Labeling Requirements .................................................................................................... 199
Configuration Requirements ............................................................................................................. 199

Kitting.......................................................................................................................................200
Component Kit Request........................................................................................................................ 200
Process Details ................................................................................................................................. 200
Interface Requirements .................................................................................................................... 200
Reporting/Labeling Requirements .................................................................................................... 200
Configuration Requirements ............................................................................................................. 200
Kit Completion ...................................................................................................................................... 201
Process Details ................................................................................................................................. 201
Interface Requirements .................................................................................................................... 202
Reporting/Labeling Requirements .................................................................................................... 202
Configuration Requirements ............................................................................................................. 202
Unkitting ................................................................................................................................................ 202
Process Details ................................................................................................................................. 202
Interface Requirements .................................................................................................................... 203
Reporting/Labeling Requirements .................................................................................................... 203
Configuration Requirements ............................................................................................................. 203

Administrative .........................................................................................................................204
Cycle Count .......................................................................................................................................... 204
Process Details ................................................................................................................................. 204
Interface Requirements .................................................................................................................... 212
Reporting/Labeling Requirements .................................................................................................... 212
Configuration Requirements ............................................................................................................. 212
Cycle Count Check ............................................................................................................................... 212
Process Details ................................................................................................................................. 213
Interface Requirements .................................................................................................................... 219
Reporting/Labeling Requirements .................................................................................................... 219
Configuration Requirements ............................................................................................................. 219
On Demand Cycle Count ...................................................................................................................... 220
Process Details ................................................................................................................................. 220
Cycle Count Scheduling ....................................................................................................................... 220
Before you Begin .............................................................................................................................. 220
Process Details ................................................................................................................................. 222
Manual Scheduling ........................................................................................................................... 223
Opportunistic Cycle Counting ............................................................................................................... 223
Physical ................................................................................................................................................ 224
Process Details ................................................................................................................................. 224
Interface Requirements .................................................................................................................... 226
Reporting/Labeling Requirements .................................................................................................... 226
Configuration Requirements ............................................................................................................. 226
Location Status ..................................................................................................................................... 227
Process Details ................................................................................................................................. 227
Interface Requirements .................................................................................................................... 227

HighJump Warehouse Advantage Functional Description vii

 Reporting/Labeling Requirements .................................................................................................... 227
Configuration Requirements ............................................................................................................. 227
RF Messaging ....................................................................................................................................... 228
Process Details ................................................................................................................................. 228
Interface Requirements .................................................................................................................... 228
Reporting/Labeling Requirements .................................................................................................... 228
Configuration Requirements ............................................................................................................. 228

Quality Control ........................................................................................................................229

Hold and Release ................................................................................................................................. 229
Process Details ................................................................................................................................. 229
Interface Requirements .................................................................................................................... 233
Reporting/Labeling Requirements .................................................................................................... 233
Configuration Requirements ............................................................................................................. 233

Lot and Serial Trace Behavior ............................................................................................... 234

Inbound Trace ....................................................................................................................................... 234
Process Details ................................................................................................................................. 234
Outbound Trace .................................................................................................................................... 235
Process Details ................................................................................................................................. 235

Pick Plan Behavior.................................................................................................................. 236

Waveless..................................................................................................................................237
Overview ............................................................................................................................................... 237
Rules ..................................................................................................................................................... 237
Overview ........................................................................................................................................... 237
Priority Rules .................................................................................................................................... 237
Cutoff Time Rules ............................................................................................................................. 239
Processing Time Rules..................................................................................................................... 240
Researching Processing Time .............................................................................................................. 241

Order Consolidation ............................................................................................................... 242

Overview ............................................................................................................................................... 242
Import .................................................................................................................................................... 242
Process Details ................................................................................................................................. 242
Consolidation Criteria ........................................................................................................................... 243
Warehouse Controls ............................................................................................................................. 243
Shipping ................................................................................................................................................ 243

viii HighJump Warehouse Advantage Functional Description

Introduction
HighJump Warehouse Advantage is a warehouse management system that provides a wide variety
of warehousing functions to help manage your business' demands. This guide provides an overview
of the HighJump Warehouse Advantage system processes and framework.

Recommended Resources
Visit the HighJump documentation website to access the following materials.
• Installation guides
• Functional descriptions
• Administrator and user documentation
• Technical reference materials
• Release notes
• White papers
• Technical notes
• Glossary

Contact Information
If you have any questions about HighJump Warehouse Advantage, send an email to
support@highjump.com or call (800) 328-3271.

Documentation Feedback
Send your comments to HighJump's documentation department at documentation@highjump.com.

Third-Party Logistic Providers

HighJump Advantage Dashboard includes functionality to allow you to display fields conditionally on
search, edit, and report pages. On the device terminals in the warehouse, the system always displays
the values for Display ASN Number, Display Item Number, Display PO Number, and Display Order
Number, regardless of the conditional visibility settings for HighJump Advantage Dashboard.

The system may prompt a user for the client code if the system cannot uniquely identify the ASN
number, item number, order number, or PO number the user entered. Because the system prompts
the user for the ASN number item number, order number, or PO number throughout many processes,
the process details section for all processes does not include this system prompt.

For more information about the Conditional Visibility feature, see “Conditional Visibility on Web
Pages” in the HighJump Advantage Dashboard Functional Description.

HighJump Warehouse Advantage Functional Description 1

Interleaving
Interleaving uses interleave groups to determine how to assign work and the types of work to
interleave for each interleave group. Interleaving is set up at the Work Queue level, so that each
process in the interleave group is completed before the next one begins.

This section describes the components of interleave groups and how to set up the system for
interleaving.

Interleave Groups
Each interleave group has an interleave type and a list of processes, as described in the following
sections.

Processes

An interleave group includes at least one of the following processes.

• Receipt of Inbound Order (IO)

Note
Receipt of Inbound Order is not a Work Queue driven process. It requires additional setup.

• Directed Pickup (06)

• Order Picking (03)
• Bulk Pick by Wave (04)
• Cycle Count (08)
• Planned Move

Note
To ensure Executive Planned Moves is included in an interleave group, you must add all of
the following work types to the interleave group.

− Directed Move (07)

− Replenishment MinMax (71)
− Replenishment TopOff (72)
− Slot Move (17)

Age/Priority Thresholds

For each process, with the exception of Cycle Count a priority and age threshold may be defined.
Regardless of interleave type, if a Work Queue exceeds the defined age or priority threshold, it is
assigned to the user.

For example, within the interleave group, if the interleave type is Proximity for Order Picking but the
priority threshold is set at 60, any Order Pick Work Queue with a priority of 60 or higher is assigned to
the handler, regardless of its proximity to the user.

2 HighJump Warehouse Advantage Functional Description

Interleave Types

Interleave groups must be set up with a specific interleave type, such as the following:

Priority-PickFlow
• Determines the work to be assigned based on Work Queue priority and pickflow. All priorities
greater than or equal to the priority threshold are assigned first and then others, if they exist.

Age-Priority
• Determines work to be assigned based on Work Queue priority (highest to lowest). Where there
are multiple Work Queues with the same priority, the oldest work queue is used.
• There is no work queue or operator directed work, such as Receipt of Inbound Order. So the
“defaults” for priority and age are used.

Strict Revolving
• Each process in the interleave group is assigned a sequence.
• The user is assigned work from the dispatcher based on the sequence of the work processes.
When the last process in the sequence is approached, the process starts over again from the
beginning of the sequence.
• If no work is found for a specific work type the user will be assigned work from the next process
based on sequence.
• If operator directed processes (a process that is not Work Queue based) exist within the
interleave group, the user always is prompted to perform that process in sequence. The user is
never prompted with the “No Work Available” screen. If no work is available for any other
processes in the interleave group, the user is always directed to perform the operator directed
processes in order of how they are defined in the interleave group.

Proximity
• Work is assigned to the user based on available work nearest to the user’s previous location.
• Each location is assigned to a node; a node is a logical group of locations.
• Each node has a distance relationship to every other node in the warehouse.
− Each node relationship must exist in both directions.
− For example, for Node A and Node B, you must define the distance from A to B and from B to
A. These distances may differ due to one-way aisles, for example.
− The “distance” value is relative. Values are used to find the nearest node, and they do not
use units of measure (for example, feet and meters). Values also are not exact. For example,
where Node A is 157 feet of travel from Node B and 569 feet from Node C, you could set the
node distances as follows: A to B=157; A to C=569. Or A to B=1; A to C=2.
− Where distances are equal, priority and age are considered.

HighJump Warehouse Advantage Functional Description 3

 • Work that exists in the previous destination location’s node is assigned first.
• Operator Directed processes (such as Receipt of Inbound Order) require additional setup, as
there is no work queue to which a location can be associated.

To override the assignment behavior for interleave types, thresholds can be set up for priority and/or
age at the work type level.

Example
If a priority threshold of 60 is set for a work type within the interleave group, any work with a
priority higher than that threshold is assigned prior to the find work logic for the Age Priority,
Strict Revolving, or Proximity interleave types.

4 HighJump Warehouse Advantage Functional Description

Authentication
The HighJump Supply Chain Advantage applications support the following policies for handling
authentication of users who access the servers and databases.
• HighJump Security uses the user IDs and passwords defined and managed within HighJump
applications to authenticate users during the logon process, along with vendor authentication for
database access. The User ID and User Domain fields in the HighJump employee record are
blank.
• HighJump One Security uses User IDs and passwords defined and managed within HighJump
One to authenticate users. This is the default. The User ID field in the HighJump employee record
is populated.
• Windows Security allows Windows Active Directory to store user passwords and enforce
authentication rules based on the domain for both application and database access. This solution
provides single sign on access. The User ID and User Domain fields in the HighJump employee
record are set to match the user’s Windows credentials.
• Lightweight Directory Access Protocol (LDAP) Security allows HighJump Advantage Platform to
authenticate user IDs and passwords against an LDAP server for application access, along with
vendor authentication for database access. The User ID field in the HighJump employee record is
set to match the user’s LDAP UID.

All policies allow for prompting users to log on again after a specified period of inactivity. With this
security feature, users in the pharmaceutical industry can be compliant with FDA Part 11. For more
information on how to implement Windows Security or LDAP Security, see Setting up Enhanced
Security for Your HighJump SCA System User’s Guide.

Windows Security Hybrid Authentication

For the Warehouse Advantage device (e.g. RF) logon process, you can use a hybrid authentication
model that allows you to mix Windows Security and HighJump Security. This model allows you to
have the system authenticate some employees using Windows security and other employees using
HighJump Security.
• If the provided Windows credentials are authenticated, the logon process checks for a record in
the HighJump employee table with that User ID and User Domain. If the logon process finds a
corresponding employee record, the system logs on the user using single sign-on and displays
the equipment prompt.
• If the provided Windows credentials are not authenticated, or the system does not find a record in
the HighJump employee table with that User ID and User Domain, the logon process uses
HighJump Security and prompts users for their user ID and password.

Note
The hybrid authentication model is not available for HighJump One Platform.

• The hybrid model uses the system control, MIXEDLOGON. The Next Value field for the control
must be set to 1 for hybrid authentication.

Pre-requisite
• HighJump servers must be configured to use Windows Security as defined in the Setting up
Enhanced Security for Your HighJump SCA System User’s Guide.

HighJump Warehouse Advantage Functional Description 5

RF Password Security
The RF Password Security process allows passwords to be stored in an encrypted format when the
HighJump Security model is enabled. This process provides controls for password expiry, either
administratively or for a configuration number of days. The RF Password Security does not require
passwords to be unique but can be enabled to enforce unique passwords across a configurable
number of recent passwords.

Process Details

The following process details apply.

• Passwords are not required. If no password is set up for a user, then the user is not prompted for
a password.
• If an unexpired password exists for the user, the user is prompted for the password.
• If a password exists for the user but has expired either by administrative action or elapsed days,
the user is prompted to first confirm their old password then establish a new password by
entering it twice.

The process allows the administrator to enable password uniqueness to allow no duplicates for a
configurable number of passwords. If password uniqueness is enabled, the new password is checked
for uniqueness across the configured number of previous passwords.

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

6 HighJump Warehouse Advantage Functional Description

Equipment Audit
The Equipment Audit process is part of the Log-On process and allows warehouses to maintain
compliance as standards change. The users are prompted with a series of questions based on the
type of equipment they are using. Equipment types and rules are maintained in HighJump One
Platform.

Process Details

The following details apply.

• The process determines the type of equipment set up for the warehouse using the
t_equipment_type process object in the t_location table.
• The users are prompted for inputs based on the equipment type they are using.
• The inputs are authenticated using the rules stored in t_equipment_rules.
• The operator responses are logged to the t_equipment_log.

HighJump Warehouse Advantage Functional Description 7

Universal Quantity Prompting
HighJump Warehouse Advantage uses five quantity prompting behavior types.
• Count
• Default Quantity
• No UOM
• Receipt
• Request

Each warehouse process uses the appropriate behavior type based on how the system needs to
prompt the user for quantity and unit of measure (UOM).

Count
The Count Behavior type allows counting of all the UOMs associated with the item being counted.
• A list of the UOMs associated with the item being counted displays on the screen. The number in
parenthesis next to each count type provides the number currently counted.
• Users can enter multiple quantities for the item being counted. When the “COUNT_ALL_UNITS”
Warehouse Control option is set to ON from HighJump Warehouse Advantage System Controls
page, lot prompt and expiration date display ‘ALL’.
• Users cannot enter negative quantities.
• If the “LP_ITEM_UNIT_COUNT_ENABLED” control option is set to ON, the users can count the
number of items, LPs, and MLPs in an Item, License Plate, or Master License Plate-controlled
location. The system does not display the Item number, lot number, serial number, and expiration
date prompts for matching counts. A mismatch triggers prompts for all data.
• The system does not validate standard handling quantity.
• For mismatched inventory in a location, the system prompts the user to recount until the user
either matches the system-expected quantity or counts the same quantity twice in a row.
• The F3: Done function can be used when all the quantities are entered.

Default Quantity
The Default Quantity behavior type is the only behavior type that defaults the expected quantity in the
dialog input.
• Only active UOMs display.
• The conversion factor for the UOM must be less than the expected quantity.
• The system displays the UOM with the smallest conversion factor first.

8 HighJump Warehouse Advantage Functional Description

 • The default UOM is the UOM with the greatest common factor.

Note
The greatest common factor is the UOM with the largest conversion factor that is evenly
divisible into the expected quantity. Since there is always a UOM with a conversion factor of
1, the system uses that UOM as the default if no other UOMs meet the criteria.

• Users cannot enter zero quantities.

• Users cannot enter negative quantities.
• By default, the standard handling quantity check for each process is on.
• The system validates the quantity entered against the UOM’s standard handling quantity.
• The F2 and F8 options function as follows:
− The function buttons display if there is more than one acceptable UOM for the item.
− F2 cycles through the available UOMs in ascending order based on the conversion factor.
− F2 returns to the first UOM in the list if the UOM currently displayed is the last available UOM
in the list.
− F8 lists all available UOMs for the item.

No UOM
The No UOM behavior type prompts the user to enter the quantity.

Note
This behavior type does not list the available UOMs for an item.

• Users cannot enter zero quantities.

• Users cannot enter negative quantities.
• The system does not validate standard handling quantity.

Receipt
The Receipt behavior type expects the user to enter the total quantity of the item being received. The
system converts the quantity entered, regardless of the selected unit of measure, to the item's base
unit of measure.

Note
This behavior type does not cycle through each UOM associated with the item being
received.

• Only active UOMs display.

• The system displays the UOM with the smallest conversion factor first.

Note
PO details or item UOMs may have an override UOM for receiving. The system may display
the override UOM first instead of the smallest conversion factor for processes that generate a
151 Inbound Order Receipt (Rcpt) transaction.

• The system defaults each UOM quantity input to blank.

HighJump Warehouse Advantage Functional Description 9

 • Users cannot enter negative quantities.
• By default, the standard handling quantity check for each process is on.
• The system validates the quantity entered against the UOM’s standard handling quantity.
• The F2 and F8 options function as follows:
− The function buttons display if there is more than one acceptable UOM for the item.
− F2 cycles through the available UOMs in ascending order based on the conversion factor.
− F2 returns to the first UOM in the list if the UOM currently displayed is the last available UOM
in the list.
− F8 lists all available UOMs for the item.

Request
The Request behavior type expects the user to enter the total quantity of the item being requested.
The system converts the quantity entered, regardless of the selected unit of measure, to the item's
base unit of measure.

Note
This behavior type does not cycle through each UOM associated with the item being
requested.

• Only active UOMs display.

• The system displays the UOM with the smallest conversion factor first.
• The system defaults each UOM quantity input to blank.
• Users cannot enter negative quantities.
• By default, the standard handling quantity check for each process is on.
• The system validates the quantity entered against the UOM’s standard handling quantity.
• The F2 and F8 options function as follows:
− The function buttons display if there is more than one acceptable UOM for the item.
− F2 cycles through the available UOMs in ascending order based on the conversion factor.
− F2 returns to the first UOM in the list if the UOM currently displayed is the last available UOM
in the list.
− F8 lists all available UOMs for the item.

10 HighJump Warehouse Advantage Functional Description

Employee Input Log
The Employee Input Log allows recording of every input of a user on the system through the
Universal Dialog process. For more information, see the “Universal Dialog Functionality” section in
HighJump Warehouse Advantage Technical Reference Guide. The input log information includes the
employee name, device identifier, equipment identifier, prompt date, input date, dialog type, user
input, and JSON string data.

The system control EMP_LOG_INPUT determines whether this feature is enabled. If the Next Value
is set to 1, it is enabled and if it is 0, it is disabled.

When this feature is enabled, you can set logging for an employee through the Employee
maintenance pages in HighJump Warehouse Advantage web.

You can view the logging results through the Employee Input Log menu.

HighJump Warehouse Advantage Functional Description 11

Receiving
Receiving includes the following processes:
• Unload Inbound Order
• ASN Receipt
• Receipt of Inbound Order
• Close Inbound Order
• Staged Receipt
• Receipt of Shipment
• Adjust Receipt of Shipment
• Unknown Receipt
• Warehouse Transfer In
• Miscellaneous Return
• Receipt from Production
• Reusable Container Receipt
• Directed Receipt
• Directed Put-Away
• VAS Execute

Notes
Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from
the oldest recall.
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

For information about the Web pages you can use to view shipment information and unknown
receipts information, see “Receipt of Shipments Pages” and “Unknown Receipts Pages” in HighJump
Advantage Dashboard Functional Description.

12 HighJump Warehouse Advantage Functional Description

Unload Inbound Order
The Unload Inbound Order process provides visibility to the arrival of an inbound order into the
warehouse. An inbound order can correspond to a vendor purchase order, transfer order, or return
order. Based on a specific inbound order, the inbound order staging location and container quantity
are entered and captured in the transaction log. The visibility of the unloaded inbound order can be
used to direct users to begin the Receipt of Inbound Order process and to monitor vendor
compliance. The completion of the unloaded inbound order task creates a corresponding work task
and receiver that is used to direct users to receive using the Directed Receipt process.

Process Details

The following process details apply.

• The purchase order is identified by scanning or entering a valid purchase order.
• Purchased orders may be indicated as closed by the host system. If a closed purchase order is
entered, the user must confirm the re-opening of the purchase order. If confirmed, the purchase
order's status is reset to “Open”. The change of status is not communicated back to the host
system.

Note
This feature is enabled with a system control setting. If it is disabled, the user receives an
error message when a closed purchase order is scanned.

• The carrier for the purchase order is identified by entering some or all of the carrier code value. If
multiple matches are found, all matching carrier values display in a list and the user must select
the exact carrier value.
• The user identifies the staging location associated with the unloaded purchase order by scanning
or entering a staging location. The system verifies the location corresponds to a valid staging
location.
• The system prompts for quantity using the Universal Quantity Behavior Type–No UOM.
• To identify the number of containers associated to an unloaded purchase order, the user can
enter any non-zero quantity.
• Entering the number of containers quantity triggers the generation of the purchase order-specific
Pre-Receipt by PO transaction, the Directed Receipt work queue, and the PO/Carrier specific
receiver.

Interface Requirements

The following interface requirements apply.

• The host system provides valid inbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 903 Unload Inbound Order transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated when the number of containers quantity is entered by the user.

HighJump Warehouse Advantage Functional Description 13

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

ASN Receipt
The ASN Receipt process manages the receipt of inventory by scanning only the ASN or LP.
Inventory is created and ASN Receipt transactions are generated at the time of receipt. When the
user's equipment reaches a user-determined capacity, the user is directed to put away the inventory
on the equipment.

Process Details

Items can be received by ASN or LP through the F2: Switch function key.

Receiving by ASN
• If the warehouse control option ASN_RCPT_BY_MLP is enabled, the system prompts the user to
scan or enter an MLP.

Note
If the ASN_RCPT_BY_MLP warehouse control option is enabled, the user cannot proceed
without entering or scanning an MLP.

• The ASN is identified by scanning or entering a valid ASN.

• The ASN must be valid and in an Open status.
• The purchase orders related to the ASN should be in an Open status.
• The system finds all LPs associated with the ASN that are in Open status and receives them one
at a time.

Note
The error message, “Incomplete Data,” may mean the lot number was not specified when the
item was created. When this error occurs, no items are received into inventory. Use ASN
maintenance to address the incomplete data so that you can receive the ASN.

Receiving by LP
• The system prompts the user to scan or enter the MLP if the warehouse control option
ASN_RCPT_BY_MLP is enabled.
• The LP must be valid and in an open status.
• ASN for that LP should exist and be Open. The error message “ASN does not exist” can mean:
− The ASN does not exist.
− The ASN is not open.
• The purchase orders related to the LP should be in an open status.

14 HighJump Warehouse Advantage Functional Description

 • If the system encounters an LP related to two open ASNs, the user is prompted for the ASN.

ASN Processing

Note
For ASN Receipt, the user is not prompted for quantity within the process. Rather, the system
captures quantity from the ASN detail table.

• If the ASN is missing carrier information, the system prompts the user for the carrier. The carrier
is identified by entering some or all of the carrier code value. If multiple matches are found, all
valid matching carrier values are displayed in a list and the user must select the exact carrier
value.
• The system determines if the LP it is receiving exists already in the system. If the LP exists, the
user is prompted to enter a new, unique LP.
• An overage quantity can be received within this process. If an overage quantity is found, the user
must confirm the acceptance of the overage quantity. If accepted, the entered quantity is received
to the user's equipment.

Note
The system does the following to determine when the quantity received is an overage
quantity.
1) Sums the purchase order quantity for the item and warehouse to determine the total
quantity expected for the item. For example, if the purchase order includes two line items with
a quantity of 35 and 15, the purchase order quantity is 50.
2) Calculates the receipt percentage overage. The control type RECPT OVERAGE indicates
the receipt overage percent allowed. For example, if the receipt overage allowed is 10%, the
system calculates the receipt percent overage using this calculation:
(10 + 100) ÷ 100 = 110%.
3) Calculates the receipt maximum quantity by multiplying the purchase order quantity by the
receipt percentage overage. For example, if the purchase order quantity is 50 and the receipt
percentage overage is 110%, the maximum quantity that can be received for an item is 55.
4) During receiving, sums the quantity that has been received to determine the receipt
quantity and compares the receipt quantity to the maximum quantity. If the receipt quantity is
greater than the receipt maximum quantity, the system displays a message to the user.

• If the item for the ASN detail is configured for full, inbound trace, or trace in/out serial control,
additional prompting is required to capture serial numbers.
− The item number associated with the ASN detail must be identified by entering or scanning
the valid item number or a valid alternative item number or UPC number associated to the
item. The user can select the F8: LST option to select a serial-controlled item from the list of
serial-controlled items on the LPs for which serial numbers have not been scanned.
− The user is prompted for a lot number when the item is configured for full, inbound trace, or
trace in/out lot control. When prompted, the lot number is required but not validated. When
configured for full lot control, the specified lot number is maintained permanently within
HighJump Warehouse Advantage inventory. When configured for inbound trace or trace
in/out lot control, the specified lot numbers are maintained only while the inventory is on the
user’s equipment. The specified lot number is discarded when the Directed Put-Away
process is initiated.

HighJump Warehouse Advantage Functional Description 15

 − When prompted, the user scans each serial number in an “X of Y” method for the received
quantity in the base unit of measure for the item. Scanned serial numbers are validated and
must be unique for the item in the warehouse. For receipt records, scanned serial numbers
are randomly assigned and distributed throughout purchase order lines. When configured for
full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out serial
control, the specified serial numbers are maintained only while the inventory is on the user’s
equipment. The specified serial numbers are discarded when the Directed Put-Away process
is initiated.
• ASN Receipt transactions are generated based on the inventory that has been received.

Interface Requirements

The following interface requirements apply.

• The host system provides valid ASN master and detail data through the HighJump Advantage
Link layer. See the relevant Advantage Link application guide for details (for example, HighJump
Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 161 ASN Receipt (Rcpt) transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated when the ASN or LP are received.
• HighJump Warehouse Advantage generates 162 ASN Receipt (Put) transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated after the user scans the destination location and the item/LP quantity to drop off at the
location.
• HighJump Warehouse Advantage generates 163 ASN Receipt (HU ID Change) as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
after the user scans a new HU ID for the ASN if a source HU ID already exists in the system.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

16 HighJump Warehouse Advantage Functional Description

Receipt of Inbound Order
The Receipt of Inbound Order process manages the receipt of a single inbound order's items into the
warehouse. An inbound order can correspond to a vendor purchase order (PO), transfer order, or
return order. Based on a specific inbound order, items are identified to the system in parallel with the
placement of the items on the user's equipment.

When the user's equipment reaches a user-determined capacity, or when there are no more items on
the inbound order to receive, the inbound order-specific Inbound Order Receipt transactions are
generated and the user is directed to put away the items on their equipment.

Process Details

The following process details apply.

• The user is required to identify a receiver to begin the process. The user can select an open
receiver or generate a new receiver. By default, the system assigns a generic, sequential number
as the new receiver. The user can override the generated receiver with any unique, alphanumeric
identifier.

Note
A receiver is a logical grouping of a set of receiving transactions for a specific purchase
order. A receiver could be a truck identifier, a shipment identifier, or any other meaningful
identifier the user chooses to enter. The logical assignment provides a basis to maintain,
view, and report on the receiving transactions. A receiver remains open until the user closes
the receiver. Closing a receiver removes the receiver from the list of open receivers.

• A receiver can only be associated to a single purchase order; however, a purchase order can be
associated to multiple receivers.
• The user can only receive against one receiver at a time; however, multiple users can receive
against the same receiver.
• The purchase order is identified by scanning or entering a valid purchase order or by selecting an
open receiver.
• Purchased orders may be indicated as closed by the host system. Closed purchase orders can
be received against throughout this process. If a closed purchase order is entered, the user must
confirm the re-opening of the purchase order. If confirmed, the purchase order's status is reset to
Open. The change of status is not communicated back to the host system.

Note
This feature is enabled with control value REOPEN_PO. If this control value is disabled, the
user receives an error message when a closed purchase order is scanned.

• The F7: Close function key closes the receiver, but it does not close the purchase order.
• All purchase order detail lines remain available to be received against while the purchase order
master remains in an Open status. The purchase order line is not assumed to be closed when the
total quantity received is equal to or greater than the expected purchase order quantity.
• After scanning the purchase order, if there are any PO comments with the comment type of “R”,
the system displays the comments.
• After scanning the item number, if there are any detail comments for that item with the comment
type of “R”, the system displays the comments.

HighJump Warehouse Advantage Functional Description 17

 • The user is required to identify the carrier when a new receiver is selected. The carrier can be
identified by either entering the carrier name, or by selecting the carrier from a list of carrier
names.
• The system prompts the user to scan or enter the master license plate (MLP) if the warehouse
control option RCP_IO_BY_MLP is enabled.

Note
If the RCP_IO_BY_MLP warehouse control option is enabled, the user cannot proceed
without entering or scanning an MLP.

• Users can receive loose items directly to their equipment, or to an LP (license plate) on their
equipment. The transaction defaults to items or LP-based receiving, based on the warehouse
specific Item/HU Flag setting.

Note
The user cannot receive loose items if the warehouse control option RCP_IO_BY_MLP is
enabled.

• Multiple LPs can be received onto the user's equipment. The user can switch between receiving
loose items and LPs via the F2: Switch function key. However, the mode cannot be switched if at
least one item is received to the user's equipment. After the user's equipment is empty, the mode
can be switched.
• The item number associated with the received product must be identified by entering or scanning
a valid item number or a valid alternative item number, or UPC number associated to the item
number.
• An unknown item (an item that does not exist in the warehouse) cannot be received with this
process.
• An unexpected item (an item that is not associated to the purchase order, but is a valid item in the
warehouse) can be received with this process. If an unexpected item number is entered, the user
must confirm the acceptance of the unexpected item. If accepted, the unexpected item is
received to the user's equipment. However, the item is not automatically added to the purchase
order.

Note
This feature is enabled with control setting RCV_ITEM_NOT_ON_PO. If the
RCV_ITEM_NOT_ON_PO is disabled, the user receives an error message when an
unknown item is scanned.

• The user is prompted for a lot number when the item is configured for full, inbound trace, or trace
in/out lot control. When prompted, the lot number is required but not validated. When configured
for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out, the specified
lot number is maintained only while the inventory is on the user's equipment. The specified lot
number is discarded when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.

18 HighJump Warehouse Advantage Functional Description

 • The user is prompted for serial numbers when the item is configured for full, inbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. When
configured for full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out serial control,
the specified serial numbers are maintained only while the inventory is on the user’s equipment.
The specified serial numbers are discarded when the Directed Put-Away process is initiated.
• The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• The system automatically reconciles the quantity received to the line(s) containing the item on the
specified purchase order. When multiple lines exist for the item on the purchase order, the
quantity is allocated in line number and schedule number sequence.
• An overage quantity can be received with this process. If an overage quantity is entered, the user
must confirm the acceptance of the overage quantity. If accepted, the entered quantity is received
to the user's equipment.

Note
The system uses the following steps to determine when the quantity received is an overage
quantity.
1) Sums the purchase order quantity for the item and warehouse to determine the total
quantity expected for the item. For example, if the purchase order includes two line items with
a quantity of 35 and 15, the purchase order quantity is 50.
2) Calculates the receipt percentage overage. The control type RECPT OVERAGE indicates
the receipt overage percent allowed. For example, if the receipt overage allowed is 10%, the
system calculates the receipt percent overage by using the following calculation.
(10 + 100) ÷ 100 = 110%.
3) Calculates the receipt maximum quantity by multiplying the purchase order quantity by the
receipt percentage overage. For example, if the purchase order quantity is 50 and the receipt
percentage overage is 110%, the maximum quantity that can be received for an item is 55.
4) During receiving, the system sums the quantity that has been received to determine the
receipt quantity and compares the receipt quantity to the maximum quantity. If the receipt
quantity is greater than the receipt maximum quantity, the system displays a message to the
user.

• The user can generate item labels after each item quantity is received to the user's equipment or
enter a zero quantity if no labels are needed.
• The item quantity received to the user's equipment or specific LP can be modified by selecting
the F6: Edit option until the user selects the F3: Done option. The user can modify the item
quantity when entering an item number that already exists on the equipment or specified LP.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED. The damaged inventory is put on hold on the receiver’s
equipment.

Note
Inventory received as damaged is counted as received against the purchase order.

HighJump Warehouse Advantage Functional Description 19

 • Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from the
oldest recall.

Note
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• When the user's equipment has reached a user-determined capacity or when there are no more
items on the purchase order to receive against the receiver, the user selects the F3: Done option.
The F3: Done option triggers the generation of purchase order-specific receipt transactions for
the items on the user's equipment and initiates the Directed Put-Away process.

Interface Requirements

The following interface requirements apply.

• The host system provides valid inbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• Each purchase order detail line item identifier is provided to HighJump Warehouse Advantage
using the item's unique item number.
• Each purchase order detail line item quantity is provided to HighJump Warehouse Advantage in
the item's base unit of measure. No conversion is performed by the HighJump Warehouse
Advantage application.
• The host system provides valid vendor and carrier data through the HighJump Advantage Link
layer. See the relevant Advantage Link application guide for details (for example, HighJump
Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 151 Inbound Order Receipt (Rcpt) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. When the user
selects F3: Done, the transactions are generated.
• HighJump Warehouse Advantage generates 152 Inbound Order Receipt (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated after the user scans the destination location and the item/LP quantity to drop off at
the location.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create Item Labels when each item quantity is received to the
user's equipment. The user can enter zero if no labels are needed.

Configuration Requirements

There are no configuration requirements.

20 HighJump Warehouse Advantage Functional Description

Close Inbound Order
The Close Inbound Order process allows the closing of inbound orders. An inbound order can
correspond to a vendor PO, transfer order, or return order.

Process Details

The following process details apply.

• The purchase order is identified by scanning or entering a valid purchase order or by selecting an
open receiver.
• If the purchase order is already closed, the user is prompted to scan or enter another purchase
order number after displaying a message indicating that the purchase order is already closed.
• If the purchase order does not exist in the warehouse, the user is prompted to reenter the
purchase order.
• The process updates the purchase order status to close on receipt of a valid purchase order.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 157 Close Inbound Order transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. Transactions are generated
when the user changes the status of the purchase order to close.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 21

Staged Receipt
The Staged Receipt process manages the receipt of a single inbound order's items into the
warehouse. An inbound order can correspond to a vendor purchase order, transfer order, or return
order. Based on a specific inbound order, items are identified to the system in parallel with the
placement of the items on the user's equipment.

When the user's equipment reaches a user-determined capacity or when there are no more items on
the inbound order to receive, the inbound order-specific Inbound Order Receipt transactions are
generated and the user is directed to stage the items on their equipment in either a Staging or Pickup
& Delivery location. After staged, a Directed Pickup work request is created.

Process Details

The following process details apply.

• The user is required to identify a receiver to begin the process. The user can select an open
receiver or generate a new receiver. By default, the system assigns a generic, sequential number
as the new receiver. The user can override the generated receiver with any unique, alphanumeric
identifier.

Note
A receiver is a logical grouping of a set of receiving transactions for a specific purchase
order. A receiver could be a truck identifier, a shipment identifier, or any other meaningful
identifier the user chooses to enter. The logical assignment provides a basis to maintain,
view, and report on the receiving transactions. A receiver remains open until the user closes
the receiver. Closing a receiver removes the receiver from the list of open receivers. Closing
a receiver closes the associated purchase order.

• A receiver can only be associated to a single purchase order; however, a purchase order can be
associated to multiple receivers.
• The user can only receive against one receiver at a time; however, multiple users can receive
against the same receiver simultaneously.
• The purchase order is identified by scanning or entering a valid purchase order or by selecting an
open receiver.
• A closed purchase order (a purchase order that is indicated as such by the host system via the
purchase order import process) can be received against within this process. If a closed purchase
order is entered, the user must confirm the re-opening of the purchase order. If confirmed, the
purchase order's status is reset to Open. The status change is not communicated back to the
host system.

Note
The REOPEN_PO system control option enables this feature. If the option is disabled, the
user receives an error message when a closed purchase order is scanned.

• All purchase order detail lines remain available to be received against while the purchase order
remains in an Open status. The purchase order line is not assumed to be closed when the total
quantity received is equal to or greater than the expected purchase order quantity.
• After scanning the purchase order, if there are any PO comments with the comment type of “R”,
the system displays the comments.
• After scanning the item number, if there are any detail comments for that item with the comment
type of “R”, the system displays the comments.

22 HighJump Warehouse Advantage Functional Description

 • If a new receiver is selected, the system prompts the user to identify the carrier by either entering
the carrier name, or by selecting the carrier from a list of carrier names.
• If the warehouse control option STG_RCPT_BY_MLP is enabled, the system prompts the user to
scan or enter an MLP.

Note
If the STG_RCPT_BY_MLP warehouse control option is enabled, the user cannot proceed
without entering or scanning an MLP

• The user can receive multiple loose items directly onto their equipment, to an LP (license plate),
or multiple LPs onto their equipment. The transaction defaults to items or LP-based receiving
based on the warehouse specific Item/HU Flag setting. The user can switch between receiving
loose items and LPs via the F2: Switch function key; however, the mode cannot be switched
unless the user's equipment is empty. After the user's equipment is empty, the mode can be
switched.

Note
The user cannot receive loose items if the warehouse control option STG_RCPT_BY_MLP is
enabled.

• The user must identify the item number associated with the received product by entering or
scanning a valid item number or a valid alternative item number, or UPC number associated to
the item number.
• An unknown item (an item that does not exist in the warehouse) cannot be received with this
process.
• An unexpected item (an item that is not associated to the purchase order, but is a valid item in the
warehouse) can be received with this process. If an unexpected item number is entered, the user
must confirm the acceptance of the unexpected item. If accepted, the unexpected item is
received to the user's equipment. However, the item is not automatically added to the purchase
order.

Note
The RCV ITEM NOT ON PO system control option enables this feature. If the option is
disabled, the user receives an error message when an unknown item is scanned.

• If the item is configured for full, inbound trace, or trace in/out lot control, the system prompts the
user for a lot number. When prompted, the lot number is required but not validated. When
configured for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. If configured for inbound trace or trace in/out, the specified lot
number is maintained only while the inventory is on the user's equipment. The specified serial
number is discarded when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.
• If the item is configured for full, inbound trace, or trace in/out serial control, the system prompts
the user for serial numbers. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. If
configured for full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out serial control,
the specified serial numbers are maintained only while the inventory is on the user’s equipment.
The specified serial numbers are discarded when the Directed Put-Away process is initiated.

HighJump Warehouse Advantage Functional Description 23

 • The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• If any Inbound VAS Tasks are found that apply to current receipt, the user is not allowed to
receive loose items. All Inbound VAS receipts must be received using LPs.

Notes
A pending inbound VAS task is determined if any VAS profile might be applied to item, UOM,
inventory class, inventory category, inventory type, vendor, carrier, inbound order type,
transaction type, or if any VAS profile has been assigned to an inbound order detail.
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• If the user attempts to receive an item to an LP that already contains at least one item for which a
pending inbound VAS Task exists, the user is warned that they will be mixing VAS with Non-VAS
items. At this point, the user may continue with the receipt, or they may back out of the receipt in
order to complete the current LP.
• The system automatically reconciles the quantity received to the line(s) containing the item on the
specified purchase order. When multiple lines exist for the item on the purchase order, the
quantity is allocated in line number and schedule number sequence.
• An overage quantity can be received within this process. If an overage quantity is entered, the
user must confirm the acceptance of the overage quantity. If accepted, the entered quantity is
received to the user's equipment.

Note
The system uses the following steps to determine when the quantity received is an overage
quantity.
1) Sums the purchase order quantity for the item and warehouse to determine the total
quantity expected for the item. For example, if the purchase order includes two line items with
a quantity of 35 and 15, the purchase order quantity is 50.
2) Calculates the receipt percentage overage. The control type RECPT OVERAGE indicates
the receipt overage percent allowed. For example, if the receipt overage allowed is 10%, the
system calculates the receipt percent overage by using the following calculation:
(10 + 100) ÷ 100 = 110%.
3) Calculates the receipt maximum quantity by multiplying the purchase order quantity by the
receipt percentage overage. For example, if the purchase order quantity is 50 and the receipt
percentage overage is 110%, the maximum quantity that can be received for an item is 55.
4) During receiving, the system sums the quantity that has been received to determine the
receipt quantity and compares the receipt quantity to the maximum quantity. If the receipt
quantity is greater than the receipt maximum quantity, the system displays a message to the
user.

• The user can generate item labels after each item quantity is received to the user's equipment or
enter a zero quantity if no labels are needed.
• The user can select the F6: Edit option to modify the item quantity received to their equipment or
specific LP until the user selects the F3: Done option. The user can also modify the item quantity
when entering an item number that already exists on the equipment or specified LP.

24 HighJump Warehouse Advantage Functional Description

 • To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED. The damaged inventory is put on hold on the receiver’s
equipment.

Note
Damaged item quantities are not reconciled against the purchase order.

• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from the
oldest recall.
• After the user's equipment has reached a user-determined capacity or there are no more items
on the purchase order to receive against the receiver, the user selects the F3: Done option. The
F3: Done option triggers the generation of purchase order-specific receipt transactions for the
items on the user's equipment and prompts the user to enter or scan the receipt staging location.
The receipt staging location may either be a Staging or Pickup & Delivery location. After the
location has been entered, a Directed Pickup work request is created.

Interface Requirements

The following interface requirements apply.

• The host system provides valid inbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• Each purchase order detail line item identifier is provided to HighJump Warehouse Advantage
using the item's unique item number.
• Each purchase order detail line item quantity is provided to HighJump Warehouse Advantage in
the item's base unit of measure. No conversion is performed by the HighJump Warehouse
Advantage application.
• The host system provides valid vendor and carrier data through the HighJump Advantage Link
layer. See the relevant Advantage Link application guide for details (for example, HighJump
Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 151 Inbound Order Receipt (Rcpt) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. When the user
selects F3: Done, the transactions are generated.
• HighJump Warehouse Advantage generates 152 Inbound Order Receipt (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated after the user scans the destination location and the item/LP quantity to drop off at
the staging location.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create Item Labels when each item quantity is received to the
user's equipment. The user can enter zero if no labels are needed.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 25

Receipt of Shipment
The Receipt of Shipment process manages the receipt of an expected shipment of items into the
warehouse. An expected shipment consists of a group of purchase order items, which are associated
to a unique, user-assigned shipment number using the HighJump Advantage Dashboard Receipt of
Shipment pages. Based on the specific shipment number, expected items are identified to the system
in parallel with the placement of the items on the user's equipment. Inventory is allocated to the
specific shipment number during the process, and remains allocated until the shipment is reconciled
within the Shipment Reconciliation Dashboard pages. After the user's equipment reaches a user-
determined capacity, or there are no more items on the shipment to receive, the system directs the
user to put away the items on their equipment.

The availability of received inventory is determined by the warehouse control option

SHIP_ALLOCATE_INV.
• If the warehouse control option SHIP_ALLOCATE_INV is disabled, inventory may be allocated to
the specific shipment number during the process, and remains allocated until the shipment is
reconciled within the Shipment Reconciliation Dashboard pages.
• If the warehouse control option SHIP_ALLOCATE_INV is enabled, inventory is received as
immediately available and automatically reconciled during the receiving process.

After the user's equipment reaches a user-determined capacity, or there are no more items on the
shipment to receive, the user is directed to put away the items on their equipment.

For information about the Web pages you can use to view shipment information, see “Receipt of
Shipments Pages” in HighJump Advantage Dashboard Functional Description.

Process Details

The following process details apply.

• The system prompts for a valid shipment number to begin the process. A valid shipment number
must correspond to an existing Open shipment created within the Receipt of Shipment
Dashboard pages.
• If the purchase order has comments with the comment type of “R”, the system displays the
comments.
• The user can only receive against a single shipment number at a time; however, multiple users
can receive against the same shipment number simultaneously.
• If the warehouse control option RCP_SHIP_BY_MLP is enabled, the system prompts the user to
scan or enter an MLP.

Note
The user cannot proceed without entering or scanning an MLP if the warehouse control
option RCP_SHIP_BY_MLP is enabled.

26 HighJump Warehouse Advantage Functional Description

 • The user can receive multiple loose items directly to their equipment, or to an LP (license plate)
on their equipment. The transaction defaults to items or LP-based receiving based on the
warehouse specific Item/HU Flag setting. The user can switch between receiving loose items and
LPs via the F2: Switch function key; however, the mode cannot be switched unless the user's
equipment is empty. After the user's equipment is empty, the mode can be switched.

Note
The user cannot receive loose items if the warehouse control option RCP_SHIP_BY_MLP is
enabled.

• If there are no more items to be received for the shipment, the user can select F5: Complete. The
F5: Complete option is only available when the user's equipment is empty. If no other users are
assigned to the shipment, the shipment is set to Complete; otherwise, the shipment remains set
to Open.
• After marking a shipment as Complete, no further receipts against that shipment are allowed. A
shipment can be reopened in the Receipt of Shipment Dashboard pages to allow additional items
to be received under the shipment number.
• The item number associated with the received product must be identified by entering or scanning
a valid item number or a valid alternative item number, or UPC number associated to the item
number.
• An unknown item (an item that does not exist in the warehouse) cannot be received with this
process.
• An unexpected item (an item which is not associated to the shipment, but is a valid item in the
warehouse) can be received within this process, but only under the following condition: the item is
an item included on the purchase orders associated to the shipment, but the corresponding
purchase order detail lines have not been added to the shipment. All purchase order detail lines
containing the item are automatically added to the shipment for each purchase order already
associated to the shipment.

Note
This feature is enabled with a configuration setting. If it is disabled, the user receives an error
message when an unknown item is scanned.

• If the item entered is not associated to any purchase orders already attached to the shipment, but
is associated to an existing purchase order, a dialog displays the purchase order. The purchase
order must be associated to the shipment in the Receipt from Shipment Dashboard pages.
• If the item entered is not associated to any purchase orders already attached to the shipment,
and is not associated to any existing purchase order, the system displays an "Item is not
expected on shipment" error message.
• If the purchase order detail has comments with the comment type of “R”, the system displays the
comments.
• If the item is configured for full, inbound trace, or trace in/out lot control, the system prompts the
user for a lot number. When prompted, the lot number is required but not validated.
− If configured for full lot control, the specified lot number is maintained permanently within
HighJump Warehouse Advantage inventory.
− If configured for inbound trace or trace in/out, the specified lot number is maintained only
while the inventory is allocated to the shipment, but then discarded when the inventory is
accepted within the HighJump Advantage Dashboard Shipment Reconciliation pages, or
when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.

HighJump Warehouse Advantage Functional Description 27

 • The user is prompted for serial numbers when the item is configured for full, inbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. Serial
numbers are maintained permanently within HighJump Warehouse Advantage inventory when
the item is configured for full serial control. When configured for inbound trace or trace in/out
serial control, the specified serial numbers are maintained only while the inventory is allocated to
the shipment, but then discarded when the inventory is accepted within the HighJump Advantage
Dashboard Shipment Reconciliation pages.
• The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• If any Inbound VAS Tasks are found that apply to the current receipt, the user is unable to receive
loose items. All Inbound VAS receipts must be received using LPs.

Note
A pending inbound VAS task is determined if any VAS profile might be applied to item, UOM,
inventory class, inventory category, inventory type, vendor, carrier, inbound order type,
transaction type, or if any VAS profile has been assigned to an inbound order detail.

• If the user attempts to receive an item to an LP that already contains at least one item for which a
pending inbound VAS Task exists, the user is warned they will be mixing VAS with Non-VAS
items. The user can continue with the receipt, or back out to complete the current LP.
• An overage quantity can be received within this process. If an overage quantity is entered, the
user must confirm the acceptance of the overage quantity. If accepted, the entered quantity is
received to the user's equipment.

Note
The system uses the following steps to determine if the quantity received is an overage
quantity.
1) Sums the purchase order quantity for the item and warehouse to determine the total
quantity expected for the item. For example, if the purchase order includes two line items with
a quantity of 35 and 15, the purchase order quantity is 50.
2) Calculates the receipt percentage overage. The control type RECPT OVERAGE indicates
the receipt overage percent allowed. For example, if the receipt overage allowed is 10%, the
system calculates the receipt percent overage by using the following calculation:
(10 + 100) ÷ 100 = 110%.
3) Calculates the receipt maximum quantity by multiplying the purchase order quantity by the
receipt percentage overage. For example, if the purchase order quantity is 50 and the receipt
percentage overage is 110%, the maximum quantity that can be received for an item is 55.
4) During receiving, the system sums the quantity received to determine the receipt quantity,
and compares the receipt quantity to the maximum quantity. If the receipt quantity is greater
than the receipt maximum quantity, the system displays a message to the user.

• If receiving items directly to their equipment, the user can generate item labels after each item
quantity is received. If no labels are necessary, the user can enter a zero quantity.
• The item quantity received to the user's equipment or specific LP can be modified by selecting
the F6: Edit option until the user selects the F3: Done option. The user can modify the item
quantity when entering an item number that already exists on the equipment or specified LP.

28 HighJump Warehouse Advantage Functional Description

 • To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED. The damaged inventory is put on hold on the receiver’s
equipment.
• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. Where multiple holds are not allowed and multiple recalls exist, the system
uses the hold code from the oldest recall.

Note
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• After the user's equipment has reached a user-determined capacity or when there are no more
items to receive against the shipment, the user selects the F3: Done option. The F3: Done option
initiates the Directed Put-Away process.

Interface Requirements

The following interface requirements apply.

• The host system provides valid inbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• Each purchase order detail line item identifier is provided to HighJump Warehouse Advantage
using the item's unique item number.
• Each purchase order detail line item quantity is provided to HighJump Warehouse Advantage in
the item's base unit of measure. No conversion is performed by the HighJump Warehouse
Advantage application.
• HighJump Warehouse Advantage generates the 153 Shipment Receipt (Rcpt) activity
transactions as detailed in the HighJump Warehouse Advantage Log Transactions specification.
The transactions are generated when the user selects F3: Done.
• HighJump Warehouse Advantage generates the 154 Shipment Receipt (Put) activity transactions
as detailed in the HighJump Warehouse Advantage Log Transactions specification. The
transactions are generated when the user scans the destination location and the item/LP quantity
to drop off at the location.

Note
The 156 Shipment Reconciliation transactions are generated in the HighJump Advantage
Dashboard Shipment Reconciliation pages for inventory allocated to the specific shipment
number.

Reporting/Labeling Requirements

The following reporting or labeling requirements apply.

• The system prompts the user to create Item Labels when each item quantity is received to the
user's equipment. The user can enter zero if no labels are needed.
• Refer to the "Reports and Labels" section of this specification for the detailed Item Label format
requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 29

Adjust Receipt of Shipment
The Adjust Receipt of Shipment process manages the adjustment of inventory received from the
Receipt of Shipment process and subsequently put away into an inventory location. Based on a
specific shipment number and license plate (LP), an item's quantity can be modified to reflect the
actual quantity of the item on the LP. Inventory is allocated to the specific shipment number during
the process, and remains allocated until the shipment is reconciled within the Shipment Reconciliation
Dashboard pages. An LP quantity can only be adjusted if the shipment is in an Open status and the
specific item has not been closed on the shipment.

For information about the Web pages you can use to view shipment information, see “Receipt of
Shipments Pages” in HighJump Advantage Dashboard Functional Description.

Process Details

The following process details apply.

• The user is required to identify a valid shipment number to begin the process. A valid shipment
number must correspond to an existing Open shipment created within the Receipt of Shipment
Dashboard pages.
• The user can only receive against one shipment number at a time; however, multiple users can
receive against the same shipment number.
• The user can edit one LP at a time.
• When there are no more items to be received for the shipment, the user selects the F5: Complete
option. If no other users are assigned to the shipment, the shipment is denoted as Complete;
otherwise, the shipment remains Open.
• After a shipment is denoted as Complete, no further receipts against the shipment are allowed. A
shipment can be reopened in the Receipt of Shipment Dashboard pages to allow additional items
to be received under the shipment number.
• The item number associated with the received product must be identified by entering or scanning
a valid item number or a valid alternative item number, or UPC number associated to the item
number.
• The user is prompted for lot numbers when the item is configured for full, inbound trace, or trace
in /out lot control. When prompted, the lot number is required but not validated. When configured
for full lot-control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out lot control,
the specified lot number is maintained only while the inventory is allocated to the shipment, but
then discarded when the inventory is accepted within the HighJump Advantage Dashboard
Shipment Reconciliation pages.
• A Closed item (an item which is denoted as Closed for the shipment within the Shipment
Reconciliation Dashboard pages) cannot be adjusted within this process.
• An item that does not exist on the specified LP cannot be adjusted within this process.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.

30 HighJump Warehouse Advantage Functional Description

 • The user is prompted for serial numbers when the item is configured for full, inbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the stored quantity in the base unit of measure for the item, with the ability to use the
F3: Done option during scanning to change received quantity to “X”. If the serial number does not
exist anywhere in the warehouse, the system prompts the user to confirm the serial number. The
system allows the user to add the serial number to that location. The system validates the serial
number entered does not exist in a different quantum of inventory. When configured for inbound
trace or trace in/out serial control, the specified serial numbers are maintained only while the
inventory is allocated to the shipment, but then discarded when the inventory is accepted within
the HighJump Advantage Dashboard Shipment Reconciliation pages.
• The quantity entered, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• An overage quantity can be entered within this process. If an overage quantity is entered, the
user must confirm the acceptance of the overage quantity. If accepted, the entered quantity is
received to the user's equipment.

Note
The system uses the following steps to determine when the quantity received is an overage
quantity.
1) Sums the purchase order quantity for the item and warehouse to determine the total
quantity expected for the item. For example, if the purchase order includes two line items with
a quantity of 35 and 15, the purchase order quantity is 50.
2) Calculates the receipt percentage overage. The control type RECPT OVERAGE indicates
the receipt overage percent allowed. For example, if the receipt overage allowed is 10%, the
system calculates the receipt percent overage by using the following calculation:
(10 + 100) ÷ 100 = 110%.
3) Calculates the receipt maximum quantity by multiplying the purchase order quantity by the
receipt percentage overage. For example, if the purchase order quantity is 50 and the receipt
percentage overage is 110%, the maximum quantity that can be received for an item is 55.
4) During receiving, the system sums the quantity that has been received to determine the
receipt quantity and compares the receipt quantity to the maximum quantity. If the receipt
quantity is greater than the receipt maximum quantity, the system displays a message to the
user.

• The reason code "RCPTOFSHIP" must be entered or selected from the reason code list after the
adjusted quantity is entered.
• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from the
oldest recall.

HighJump Warehouse Advantage Functional Description 31

Interface Requirements

The following interface requirements apply.

• The host system provides valid inbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• Each purchase order detail line item identifier is provided to HighJump Warehouse Advantage
using the item's unique item number.
• Each purchase order detail line item quantity is provided to HighJump Warehouse Advantage in
the item's base unit of measure. No conversion is performed by the HighJump Warehouse
Advantage application.
• HighJump Warehouse Advantage generates the 155 Shipment Receipt activity transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated when the user enters the reason code.
• HighJump Warehouse Advantage generates the 156 Adjust Receipt of Shipment activity
transactions as detailed in the HighJump Warehouse Advantage Log Transactions specification.
The transactions are generated when the user enters the reason code.

Note
The 156 Shipment Reconciliation transactions are generated in the Shipment Reconciliation
Dashboard pages for inventory allocated to the specific shipment number.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create Item Labels when each item quantity is received to the
user's equipment. The user can enter zero if no labels are needed.

Configuration Requirements

There are no configuration requirements.

32 HighJump Warehouse Advantage Functional Description

Unknown Receipt
The Unknown Receipt process provides visibility to the receipt of unknown items into the warehouse.
An unknown receipt can represent the receipt of an item with or without a valid item identifier or with
or without a valid purchase order. Unknown receipts do not represent actual inventory and are
maintained in a separate unknown receipt table.

Unknown receipts can be reviewed, edited, resolved, and closed within the HighJump Advantage
Dashboard Unknown Receipt pages. For information about the Web pages you can use to view
unknown receipt information, see “Unknown Receipts Pages” in HighJump Advantage Dashboard
Functional Description.

Process Details

The following process details apply.

• An unknown receipt includes a purchase order number (optional), vendor name, carrier, item
number, quantity, comments, description, and destination location. Each unique purchase order
number/vendor name/carrier/item combination represents a specific unknown receipt.
• A purchase order can be identified by entering a purchase order or other meaningful receipt
identifier. The purchase order is not required and is not validated.
• The vendor name can be identified by entering the vendor name, or by selecting the vendor from
a list of vendor names. The vendor name is required and is validated.
• The carrier name can be identified by entering the carrier name, or by selecting the carrier from a
list of carrier names. The vendor name is required and is validated.
• An item number associated with the received product must be identified. The item number is
required, but is not validated.
• The system prompts for quantity using the Universal Quantity Behavior Type–No UOM.
• The quantity associated to the unknown receipt must be identified. The quantity is required and
the system validates that it is greater than or equal to zero.
• The opportunity to modify the item quantity is provided when the user enters a purchase
order/vendor name/carrier/item combination already associated to an unknown receipt. The
quantity can be modified by entering the total amount of the item relative to the unknown receipt.
• Comments can be entered by the user. The comments are not required.
• A description can be entered by the user. The description is not required.
• The destination location (the location within the warehouse to which the item is received) must be
identified. The destination location is required and must correspond to a valid warehouse location.
• When there are no more unknown items to receive against the purchase order/vendor
name/carrier, the user selects F3: Done. The system returns the user to the purchase order
prompt.

HighJump Warehouse Advantage Functional Description 33

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 181 Unknown Receipt transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated when the destination location is entered by the user.
• The host system provides valid vendor and carrier data through the HighJump Advantage Link
layer. See the relevant Advantage Link application guide for details (for example, HighJump
Advantage Link for Flat File Guide).

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

34 HighJump Warehouse Advantage Functional Description

Warehouse Transfer In
The Warehouse Transfer In process manages the receipt of items from an external facility into the
warehouse. Based on a specific control number, items are identified to the system in parallel with the
placement of the items on the user's equipment.

After the user's equipment reaches a user-determined capacity, or there are no more items on the
transfer to receive, the system generates Warehouse Transfer In transactions and directs the user to
put away the items on their equipment.

Process Details

The following process details apply.

• A control number is identified by scanning or entering a meaningful identifier to associate with the
receipt. The control number is not required or validated, and only captured to include in the
transaction log.
• If the warehouse control option WHSE_XFER_IN_BY_MLP is enabled, the system prompts the
user to scan or enter an MLP.

Note
If the WHSE_XFER_IN_BY_MLP warehouse control option is enabled, the user cannot
proceed without entering or scanning an MLP.

• The user can receive multiple loose items directly onto their equipment, or an LP (license plate),
or multiple LPs onto their equipment. The user can switch between receiving loose items and LPs
via the F2: Switch option; however, the mode cannot be switched if at least one item is received
to the user's equipment. After the user's equipment is empty, the mode can be switched.

Note
The user cannot receive loose items if the warehouse control option
WHSE_XFER_IN_BY_MLP is enabled.

• The item number associated with the received product must be identified by entering or scanning
a valid item number or a valid alternative item number, or UPC number associated to the item
number.
• An unknown item (an item which does not exist in the warehouse) cannot be received with this
process.
• If the item is configured for full, inbound trace, or trace in/out lot control, the system prompts the
user for a lot number. When prompted, the lot number is required but not validated. If configured
for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. If configured for inbound trace or trace in/out lot control, the
specified lot number is maintained only while the inventory is on the user's equipment. The
specified lot number is discarded when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.

HighJump Warehouse Advantage Functional Description 35

 • If the item is configured for full, inbound trace, or trace in/out serial control, the system prompts
the user for serial numbers. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. When
configured for full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. If configured for inbound trace or trace in/out serial control, the
specified serial numbers are maintained only while the inventory is on the user’s equipment. The
specified serial numbers are discarded when the Directed Put-Away process is initiated.
• The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• The user can generate item labels after each item quantity is received to the user's equipment, or
enter a zero quantity if no labels are needed.
• The user can select the F6: Edit option to modify the item quantity received to their equipment or
specific LP until the user selects the F3: Done option. The user can also modify the item quantity
when entering an item number that already exists on the equipment or specified LP.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED. The damaged inventory is put on hold on the receiver’s
equipment.
• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. If multiple
holds are not allowed and multiple recalls exist, the system uses the hold code from the oldest
recall.

Note
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• After the user's equipment reaches a user-determined capacity, or there are no more items on
the transfer to receive, the user selects the F3: Done option. The F3: Done option triggers the
generation of Warehouse Transfer In transactions for the items on the user's equipment and
initiates the Directed Put-Away process.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 521 Warehouse Transfer In (Rcpt) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated when the F3: Done option is selected by the user.
• HighJump Warehouse Advantage generates 522 Warehouse Transfer In (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated after the user scans the destination location and the item/LP quantity to drop off at
the location.

36 HighJump Warehouse Advantage Functional Description

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create Item Labels when each item quantity is received to the
user's equipment. The user can enter zero if no labels are needed.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 37

Miscellaneous Return
The Miscellaneous Return process manages the receipt of returned items into the warehouse. Based
on a specific control number, items are identified to the system in parallel with the placement of the
items on the user's equipment.

When the user's equipment reaches a user-determined capacity, or when there are no more items on
the return to receive, the Miscellaneous Return transactions are generated and the user is directed to
put away the items on their equipment.

Process Details

The following process details apply.

• A control number is identified by scanning or entering a meaningful identifier to associate with the
return. The control number is not required or validated, and is only captured to include in the
transaction log.
• The system prompts the user to scan or enter the MLP if the warehouse control option
MISC_RTRN_BY_MLP is enabled.

Note
If the MISC_RTRN_BY_MLP warehouse control option is enabled, the user cannot proceed
without entering or scanning an MLP.

• The user can receive loose items directly onto their equipment, or an LP (license plate) or
multiple LPs onto their equipment. The user can switch between receiving loose items and LPs
via the F2: Switch function key; however, the mode cannot be switched if at least one item or LP
is received to the user's equipment. After the user's equipment is empty, the mode can be
switched.

Note
The user cannot receive loose items if the warehouse control option MISC_RTRN_BY_MLP
is enabled.

• The item number associated with the returned product must be identified by entering or scanning
a valid item number or a valid alternative item number, or UPC number associated to the item
number.
• An unknown item (an item that does not exist in the warehouse) cannot be received with this
process.
• The user is prompted for a lot number when the item is configured for full, inbound trace, or trace
in/out lot control. When prompted, the lot number is required but not validated. When configured
for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out lot control,
the specified lot number is maintained only while the inventory is on the user's equipment. The
specified lot number is discarded when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.

38 HighJump Warehouse Advantage Functional Description

 • The user is prompted for serial numbers when the item is configured for full, inbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. When
configured for full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out serial control,
the specified serial numbers are maintained while the inventory is on the user’s equipment. The
specified serial numbers are discarded when the Directed Put-Away process is initiated.
• The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• The user can generate item labels after each item quantity is received to the user's equipment, or
enter a zero quantity if no labels are necessary.
• The item quantity received to the user's equipment or specific LP can be modified by selecting
the F6: Edit option until the user selects the F3: Done option. The user can modify the item
quantity when entering an item number that already exists on the equipment or specified LP.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED. The damaged inventory is put on hold on the receiver’s
equipment.
• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from the
oldest recall.

Note
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• When the user's equipment has reached a user-determined capacity or when there are no more
items on the return to receive, the user selects the F3: Done option. The F3: Done option triggers
the generation of the Miscellaneous Return transactions for the items on the user's equipment
and initiates the Directed Put-Away process.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 547 Miscellaneous Return (Rcpt) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated when the F3: Done option is selected by the user.
• HighJump Warehouse Advantage generates 548 Miscellaneous Return (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated after the user scans the destination location and the item/LP quantity to drop off at
the location.

HighJump Warehouse Advantage Functional Description 39

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create Item Labels when each item quantity is received to the
user's equipment. The user can enter zero if no labels are needed.

Configuration Requirements

There are no configuration requirements.

40 HighJump Warehouse Advantage Functional Description

Receipt from Production
The Receipt from Production process manages the receipt of items produced from an internal
production location. Items are identified to the system in parallel with the placement of the items on
the user's equipment.

When the user's equipment reaches a user-determined capacity, or when there are no more items to
receive, the Receipt from Production receipt transactions are generated and the user is directed to
put away the items on their equipment.

Process Details

The following process details apply.

• The system prompts the user to scan or enter the MLP if the warehouse control option
RCP_PROD_BY_MLP is enabled.

Note
If the RCP_PROD_BY_MLP warehouse control option is enabled, the user cannot proceed
without entering or scanning an MLP.

• The user can receive multiple loose items directly to their equipment, or to an LP (license plate)
on their equipment.

Note
The user cannot receive loose items if the warehouse control RCP_PROD_BY_MLP is
enabled.

• Multiple LPs can be received onto the user's equipment. The user can switch between receiving
loose items and LPs via the F2: Switch function key; however, the mode cannot be switched if at
least one item is received to the user's equipment. After the user's equipment is empty, the mode
can be switched.
• The item number associated with the received product must be identified by entering or scanning
a valid item number or a valid alternative item number, or UPC number associated to the item
number.
• An unknown item (an item that does not exist in the warehouse) cannot be received with this
process.
• The user is prompted for a lot number when the item is configured for full, inbound trace, or trace
in/out lot control. When prompted, the lot number is required but not validated. When configured
for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out lot control,
the specified lot number is maintained only while the inventory is on the user's equipment. The
specified lot number is discarded when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.

HighJump Warehouse Advantage Functional Description 41

 • The user is prompted for serial numbers when the item is configured for full, inbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. When
configured for full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. When configured for inbound trace or trace in/out serial control,
the specified serial numbers are maintained only while the inventory is on the user’s equipment.
The specified serial numbers are discarded when the Directed Put-Away process is initiated.
• The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• The item quantity received to the user's equipment or specific LP can be modified until the user
selects the F3: Done option. The F3: Done option triggers the generation of the Receipt from
Production transactions relative to the items on the user's equipment. The user can modify the
item quantity when entering an item number that already exists on the user's equipment or
specified LP. Entering the total amount of the item relative to the user's equipment or specific LP
modifies the quantity.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED. The damaged inventory is put on hold on the receiver’s
equipment.
• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from the
oldest recall.

Note
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• When the user's equipment has reached a user-determined capacity or there are no more items
to receive, the user selects the F3: Done option. The F3: Done option triggers the generation of
the Receipt from Production transactions relative to the items on the user's equipment and
initiates the Directed Put-Away process.

42 HighJump Warehouse Advantage Functional Description

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 111 Receipt from Production (Rcpt) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated when the F3: Done option is selected by the user.
• HighJump Warehouse Advantage generates 112 Receipt from Production (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated after the user scans the destination location and the item/LP quantity to drop off at
the location.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 43

Reusable Container Receipt
The Reusable Container Receipt process manages the receipt of reusable containers into the
warehouse or adds new containers to the warehouse if the container does not exist.

The user can receive an unlimited quantity of containers. All containers received are ready to ship.
For every receipt, a reusable container receipt transaction is generated and the user is directed to
receive another container.

Process Details

The following process details apply.

• The associated container number must be identified by entering or scanning the container.
• If the container is already registered in the warehouse and is marked as IN, the user is prompted
to scan or enter another container number after displaying a message indicating that the
container is already in the warehouse.
• If the container does not exist in the warehouse, the user is prompted to confirm to add this
container into the warehouse.
• The user is prompted to scan or enter the type of the reusable container (valid types are “P” for
pallet, “T” for tote and “O” for other). This container is registered into the warehouse and is ready
to ship.
• If the container is already registered in the warehouse and is marked as OUT, the status of the
container is changed to IN and the receipt date is updated.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 173 Reusable Container Receipt transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. Transactions are
generated when the user changes the status of the container or creates a new container in the
warehouse.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

44 HighJump Warehouse Advantage Functional Description

Directed Receipt
The Directed Receipt process manages the receipt of a single inbound order's items into the
warehouse based on a directed receipt request created with the Unload Inbound Order process.
Based on the directed receipt work request, the system suggests the optimal inbound order, receiver,
and location from which to receive. An inbound order can correspond to a vendor purchase order,
transfer order, or return order. Based on a specific inbound order, items are identified to the system in
parallel with the placement of the items on the user's equipment.

After the user's equipment reaches a user-determined capacity, or there are no more items on the
inbound order to receive, the system generates inbound order-specific Directed Receipt transactions
and directs the user to put away the items on their equipment.

Process Details

The following process details apply.

• The system determines if there is a least one open directed receipt request in the work queue. If
no open directed receipt request is found, the system displays the "no work available" message.
• If at least one open directed receipt request is found, the system assigns the user to the directed
receipt request and increments the number of workers assigned to the request.
• The user must confirm the assigned purchase order, receiver, and location by scanning or
entering the system suggested receipt location.

Note
A receiver is a logical grouping of a set of receiving transactions for a specific purchase
order. A receiver could be a truck identifier, a shipment identifier, or any other meaningful
identifier the user chooses to enter. The logical assignment provides a basis to maintain,
view, and report on the receiving transactions. A receiver remains open until the user closes
the receiver. Closing a receiver removes the receiver from the list of open receivers, but will
not close the associated purchase order.

• A "receiver" can only be associated to a single purchase order; however, a purchase order can
be associated to multiple receivers.
• The user can only receive against a single receiver at a time; however, multiple users can receive
against the same receiver simultaneously.
• Purchase orders may be indicated as closed by the host system via the purchase order import
process. Closed purchase orders can be received against within this process if the directed
receipt work request is in an Available status.
• All purchase order detail lines can be received against while the purchase order master and
directed receipt work request remain in an Open status. The purchase order line is not assumed
to be closed when the total quantity received is equal to or greater than the expected purchase
order quantity.
• After scanning the purchase order, if there are any PO comments with the comment type of “R”,
the system displays the comments.
• After scanning the item number, if there are any detail comments for that item with the comment
type of “R”, the system displays the comments.

HighJump Warehouse Advantage Functional Description 45

 • If the warehouse control option DIR_RCPT_BY_MLP is enabled, the system prompts the user to
scan or enter an MLP.

Note
If the DIR_RCPT_BY_MLP warehouse control option is enabled, the user cannot proceed
without entering or scanning an MLP.

• The user can receive multiple loose items directly onto their equipment, to an LP (license plate),
or multiple LPs onto their equipment. The transaction defaults to items or LP-based receiving
based on the warehouse specific Item/HU Flag setting. The user can switch between receiving
loose items and LPs via the F2: Switch function key; however, the mode cannot be switched
unless the user's equipment is empty. After the user's equipment is empty, the mode can be
switched.

Note
The user cannot receive loose items if the warehouse control option DIR_RCPT_BY_MLP is
enabled.

• The user must identify the item number associated with the received product by entering or
scanning a valid item number or a valid alternative item number, or UPC number associated to
the item number.
• An unknown item (an item that does not exist in the warehouse) cannot be received with this
process.
• An unexpected item (an item that is not associated to the purchase order, but is a valid item in the
warehouse) can be received within this process. If an unexpected item number is entered, the
user must confirm the acceptance of the unexpected item. If accepted, the unexpected item is
received to the user's equipment; however, the item is not automatically added to the purchase
order.

Note
The RCV ITEM NOT ON PO system control option enables this feature. If the option is
disabled, the user receives an error message when an unknown item is scanned.

• If the item is configured for full, inbound trace, or trace in/out lot control, the system prompts the
user for a lot number. When prompted, the lot number is required but not validated. If configured
for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory. If configured for inbound trace or trace in/out lot control, the
specified lot number is maintained only while the inventory is on the user's equipment. The
specified lot number is discarded when the Directed Put-Away process is initiated.
• The system prompts for quantity using the Universal Quantity Behavior Type–Receipt.
• If the item is configured for full, inbound trace, or trace in/out serial control, the system prompts
the user for serial numbers. When prompted, the user scans each serial number in an “X of Y”
method for the received quantity in the base unit of measure for the item, with the ability to use
the F3: Done option during scanning to change received quantity to “X”. Scanned serial numbers
are validated and must be unique for the item in the warehouse. For receipt records, scanned
serial numbers are randomly assigned and distributed throughout purchase order lines. If
configured for full serial control, the serial numbers are maintained permanently within HighJump
Warehouse Advantage inventory. If configured for inbound trace or trace in/out serial control, the
specified serial numbers are maintained only while the inventory is on the user’s equipment. The
specified serial numbers are discarded when the Directed Put-Away process is initiated.
• The quantity received, regardless of the selected unit of measure, is converted to the item's base
unit of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.

46 HighJump Warehouse Advantage Functional Description

 • The system automatically reconciles the quantity received to the line(s) containing the item on the
specified purchase order. When multiple lines exist for the item on the purchase order, the
quantity is allocated in line number and schedule number sequence.
• An overage quantity can be received within this process. If an overage quantity is entered, the
user must confirm the acceptance of the overage quantity. If accepted, the entered quantity is
received to the user's equipment.

Note
The system uses the following steps to determine when the quantity received is an overage
quantity.
1) Sums the purchase order quantity for the item and warehouse to determine the total
quantity expected for the item. For example, if the purchase order includes two line items with
a quantity of 35 and 15, the purchase order quantity is 50.
2) Calculates the receipt percentage overage. The control type RECPT OVERAGE indicates
the receipt overage percent allowed. For example, if the receipt overage allowed is 10%, the
system calculates the receipt percent overage by using the following calculation:
(10 + 100) ÷ 100 = 110%.
3) Calculates the receipt maximum quantity by multiplying the purchase order quantity by the
receipt percentage overage. For example, if the purchase order quantity is 50 and the receipt
percentage overage is 110%, the maximum quantity that can be received for an item is 55.
4) During receiving, the system sums the quantity that has been received to determine the
receipt quantity and compares the receipt quantity to the maximum quantity. If the receipt
quantity is greater than the receipt maximum quantity, the system displays a message to the
user.

• The user can generate item labels after each item quantity is received to the user's equipment, or
enter a zero quantity if no labels are needed.
• The user can modify the item quantity received to their equipment or specific LP until they select
the F3: Done option. The F3: Done option triggers the generation of purchase order-specific
receipt transactions relative to the items on the user's equipment. The user can also modify the
item quantity when entering an item number that already exists on the equipment or specified LP
by entering the total amount of the item relative to their equipment or specific LP.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. After entering the quantity of damaged product, the user must enter or select reason
code type RECEIPT DAMAGED, which places the damaged inventory on hold on the receiver’s
equipment.

Note
Damaged item quantities are not reconciled against the purchase order.

• Received inventory on which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. Where
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from the
oldest recall.

Note
If an item is recalled, VAS applies only if the Condition for the VAS Profile has Process Held
Inventory set to “Yes”.

• After the user's equipment has reached a user-determined capacity or there are no more items
on the purchase order to receive against the receiver, the user selects the F3: Done option. The
F3: Done option triggers the generation of purchase order-specific receipt transactions relative to
the items on the user's equipment and initiates the Directed Put-Away process.

HighJump Warehouse Advantage Functional Description 47

 • Directed receipt work requests and receivers remain in an open and assignable state until the
user selects the F3: Done option at the initial assign purchase order and receipt location
confirmation prompt.

Interface Requirements

The following interface requirements apply.

• The host system provides valid inbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• Each purchase order detail line item identifier is provided to HighJump Warehouse Advantage
using the item's unique item number.
• Each purchase order detail line item quantity is provided to HighJump Warehouse Advantage in
the item's base unit of measure. No conversion is performed by the HighJump Warehouse
Advantage application.
• The host system provides valid vendor and carrier data through the HighJump Advantage Link
layer. See the relevant Advantage Link application guide for details (for example, HighJump
Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 151 Inbound Order Receipt (Rcpt) activity
transactions as detailed in the HighJump Warehouse Advantage Log Transactions specification.
The transactions are generated when the user selects F3: Done.
• HighJump Warehouse Advantage generates 152 Inbound Order Receipt (Put) activity
transactions as detailed in the HighJump Warehouse Advantage Log Transactions specification.
The transactions are generated after the user scans the destination location and the item/LP
quantity to drop off at the location.

Reporting/Labeling Requirements

The system prompts the user to create Item Labels when each item quantity is received to the user's
equipment. The user can enter zero if no labels are needed.

Configuration Requirements

There are no configuration requirements.

48 HighJump Warehouse Advantage Functional Description

Directed Put-Away
The Directed Put-Away process manages the movement of inventory items from the user's equipment
into their optimal, system-determined storage locations.

Using item-specific put-away rules to predetermine the put-away location for each item on the user's
equipment, users are directed to storage locations using an optimum flow sequence to minimize
travel. Inventory accuracy is maintained by confirming the specific item number and item quantity
being moved from the user's equipment or specific MLP or LP to the specified location and LP (if
applicable). When moving the entire contents of the user's equipment, MLP, or specific LP, each item
number and quantity associated to the user's equipment, MLP, or LP is not confirmed.

A movement transaction is generated for each item quantity moved from the user's equipment or LP
to the specified location and LP (if applicable). The specific movement transaction is based on the
process that initiated the Directed Put-Away process. When the user's equipment is empty, the user
is returned back to the process that initiated the Directed Put-Away process.

Notes
At any level of the Directed Put-Away process, the system prompts for serial numbers if the
item is configured for full serial control and the quantity entered is less than the total quantity
for the quantum of inventory being put away. When prompted, the user scans each serial
number in an “X of Y” method for the quantity being put away.
The system only allows combining an item/lot in a loose item location or on an LP if the hold
status and all hold codes (if any) match.
Received inventory for which a recall has been placed is automatically put on hold on the
receiver’s equipment. The system sends a receipt notice and a hold event to the host. If
multiple holds are not allowed and multiple recalls exist, the system uses the hold code from
the oldest recall.

Put-Away Level 1 Process Details

The following process details apply.

Put-Away Level 1
• The Directed Put-Away process manages the put-away of License Plate-controlled pending
inbound Value Added Service (VAS) task inventory residing on the user's equipment first.
• If the system determines that pending inbound VAS task LPs exist on the user’s equipment, then
the system proceeds to Put-Away of a VAS LP.
• The system determines if the system-level flag CROSS-DOCK is enabled. The CROSS-DOCK
flag is retrieved from the system control table during the Log-On process. If the CROSS-DOCK
flag is not enabled, then the system proceeds to Put-Away Level 2.

Put-Away of a VAS LP
• The system prompts the user to scan or enter the LP belonging to the highest priority, and oldest
inbound VAS Task. The user may enter to accept the system suggested LP, or they may
manually enter a value for any LP that exists on the user’s equipment and that has pending VAS
tasks assigned to it. The user may also select the F4: List option to list all of the LPs that are on
the user’s equipment for which inbound VAS tasks exist. Any LP displayed in the list may be
selected.

HighJump Warehouse Advantage Functional Description 49

 • The system determines and suggests to the user the VAS type location that is required for the
lowest sequenced pending VAS task for the associated LP. The location must be confirmed by
entering or scanning a location associated to the suggested VAS type. The system verifies that
the identified location is a valid license-controlled location that is associated to a VAS location
type for at least one pending task for the LP, or that the location is a Pickup & Delivery type
location.
• If the identified location is a Pickup & Delivery location, a Directed Pickup work request is created
for the inventory.
• The user confirms the move by scanning the LP value of the active LP. Upon confirmation, the
system moves the LP and its contents to the selected VAS type location.
• The system determines whether any other pending VAS Task LPs exist on the user's equipment.
If no other pending VAS Task LPs are found, the system determines if the system-level cross-
dock flag is enabled. The system-level cross-dock flag is retrieved from the system control table
during the Log-On process. If the cross-dock flag is not enabled, then the system proceeds to
Put-Away Level 2.

Cross-Dock Equipment Contents

Note
The cross-docking process excludes outbound orders that specify lot, or held inventory.
Cross-docking does not support the “order by” feature.

• The system retrieves the cross-dock profile values relative to all of the items on the user's
equipment.
• A cross-dock profile consists of the following elements.

Type Description Status Number of

days Out (1)
1 Attempt to directly "cross-dock" the entire 0=Disabled n
equipment contents to fulfill planned pick requests
1=Enabled
for a single, open order.
2 Attempt to indirectly "cross-dock" the entire 0=Disabled n
equipment contents to fulfill planned pick requests
1=Enabled
using a collection of open orders (including the
entire equipment contents).
3 Attempt to directly "cross-dock" the entire 0=Disabled n
equipment contents to fulfill planned pick requests
1=Enabled
using planned (i.e. Directed Move) moves and
replenishment of a single item.
1. Number of days Out: This setting controls the criteria for the order selection. When
zero, the number of days out defaults to 999. Only orders whose earliest ship date is
less than or equal to the current date plus the number of days out are considered
candidates for the selection.

Note
Cross-docking only tracks serial numbers when the item is configured for full serial control.

• If the cross-dock profile 1 is enabled, the system proceeds to Cross-dock Profile 1.

• If the cross-dock profile 2 is enabled, the system proceeds to Cross-dock Profile 2.
• If the cross-dock profile 3 is enabled, the system proceeds to Cross-dock Profile 3.

50 HighJump Warehouse Advantage Functional Description

 • Otherwise, the system proceeds to Put-Away Level 2.

Cross-dock Profile 1
• If cross-dock profile 1 is enabled, the system determines the first order which meets the following
criteria:
− The order is released for picking.
− The order's earliest ship date is less than or equal to the current date plus the number of days
out. When multiple items exist on the user’s equipment, the system uses the lowest value of
number of days out among each of the distinct item profiles.
− The order's staging location is assigned.
− All item quantities on the user's equipment can be applied to the order without exceeding the
open quantities of any of the items needed for the order.
− The pick detail records associated to the order and corresponding to the items on the user's
equipment are not assigned to another user.
− If no order is found which meets the criteria, the system proceeds to Cross-dock Profile 2.
• The system updates the employee ID in the pick detail records associated to the order and
corresponding items on the user's equipment.
• The system increments the number of workers assigned in the work queue associated to the pick
detail records.
• The system displays the order number and staging location associated to the system-determined
order.
• If the user does not want to cross-dock the contents of their equipment to the suggested order,
the user can select the F3: Put option. If the F3: Put option is selected, the system proceeds to
Put-Away Level 2.
• If the user wants to cross-dock the contents of their equipment to the suggested order, the user
can select the F6: Dock option.
• The system directs the user to the staging location associated to the cross-dock order. The
location must be confirmed by scanning or entering the suggested location. The system validates
the entered location corresponds to the suggested location.
• If the destination location is not item-controlled, then the system prompts the user to enter the
destination LP. The user can select the F4: Put LP option to put the LP from their equipment or
enter a new destination LP.
• The system does the following for each distinct item/lot number on the user's equipment:
− Determines the next open line associated to the cross-dock order and item number.
− Determines the quantity needed for the line.
− Computes the quantity to be applied (i.e., the pick quantity) for the open line as follows: If the
quantity needed is greater than the unallocated item/lot number quantity remaining on the
user's equipment, sets the pick quantity equal to the unallocated item/lot number quantity
remaining on the user's equipment. Otherwise, sets the pick quantity equal to the quantity
needed for the line.
− Increments the open line's picked quantity with the computed pick quantity.
− Increments the open line's staged quantity with the computed pick quantity.
− Increments the open line's loaded quantity with the computed pick quantity.

HighJump Warehouse Advantage Functional Description 51

 − Decrements the unallocated item/lot number quantity on the user's equipment with the pick
quantity.
− Increments the allocated item/lot number quantity in the staging location with the pick
quantity.
− Generates a Cross-dock for Picking (Put) transaction to reflect the item/lot number quantity
picked for the order, item, and line number.
− Repeats the item/lot number allocation until the unallocated item/lot number quantity is zero.

Cross-dock Profile 2
• If cross-dock profile 2 is enabled, the system determines if the following criteria can be met:
− The sum quantity of each distinct item on the user's equipment, plus the sum quantity of each
distinct item residing in all cross-dock locations, is less than or equal to sum open quantities
of each distinct item needed for the orders. To determine the open quantity needed, only
orders meeting the following criteria are considered:
• The order is released for picking.
• The order's earliest ship date is less than or equal to the current date plus the number of
days out. When multiple items exist on the user’s equipment, the system uses the lowest
value of number of days out among each of the distinct item profiles.
• The order's staging location is assigned.
• All item quantities on the user's equipment, plus all item quantities in all cross-dock
locations of the warehouse, can be applied to the order’s quantities without exceeding the
open quantities of any of the items needed for the orders.
• The pick detail records associated to the order and corresponding to the items on the
user's equipment are not assigned to another user.
• If these criteria are not meet, the system proceeds to Cross-dock Profile 3.
• If at least one distinct item on the user's equipment fails to meet the above criteria, the system
proceeds to Put-Away Level 2.
• If the user does not want to cross-dock the contents of their equipment, the user can select the
F3: Put option. If the F3: Put option is selected, the system proceeds to Put-Away Level 2.
• If the user wants to cross-dock the contents of their equipment to a cross-dock location, the user
can select the F6: Dock option.
• The cross-dock location is identified by scanning or entering a location. The system verifies the
location corresponds to a valid cross-dock location.
• If the destination location is not item-controlled, then the system prompts the user to enter the
destination LP. The user can select the F4: Put LP option to put the LPs from their equipment or
enter a new destination LP.

52 HighJump Warehouse Advantage Functional Description

 • The system moves the contents of the user’s equipment to the specified cross-dock location. A
cross-dock transaction is generated for each item/lot number moved from the user’s equipment to
the cross-dock location. The transaction defaults to items or LPs based on the Item/HU indicator
of the destination location (cross-dock location).

Cross-dock Profile 3
• If cross-dock profile 3 is enabled, the system determines if the following criteria can be met:
− Specific item quantities on the user’s equipment can be applied to the move task without
exceeding the open quantity of the item needed for the move task.
− If the user has more than one item on their equipment, the user can either put away or cross-
dock any item that satisfies a cross-dock opportunity.
− The move task's due date and time due is less than or equal to the current date plus the
number of days out.
− The move task's staging location is assigned and does not have the status of “Full”.
− The pick detail records associated to the move task and corresponding to the item on the
user's equipment are not assigned to another user.
− If no order is found which meets the criteria, the system proceeds to Put-Away Level 2.
• The system displays the item with the option F6: Dock and F3: Put. If the F3: Put option is
selected, the system proceeds to Put-Away Level 2.
• The user can select F6: Dock option to cross-dock the item to the location specified.
• If the destination location is not item-controlled, then the system prompts the user to enter the
destination LP. The user can select the F4: Put LP option to put the LP from their equipment or
enter a new destination LP.
• The system updates the Directed Move or Replenishment request with the quantity dropped off.
The transaction defaults to items or LPs based on the Item/HU indicator of the destination
location.

Put-Away Level 2 Process Details

The following process details apply.

Put-Away Level 2
• The Directed Put-Away process manages the put-away of MLP or LP-based inventory residing on
the user's equipment first. If there are no MLPs or LPs on the user's equipment, the system
proceeds to Put-Away Level 3.
• The system determines the number of MLPs on the user's equipment. If there is more than one
MLP, the preferred MLP to be put away must be identified by entering or scanning an MLP
identifier associated to the user's equipment (an MLP is not suggested because the system
cannot determine how the MLPs are physically positioned on the user's equipment). If there is
only one MLP on the user's equipment, the user is not prompted to scan an MLP.

Put-Away of MLPs
• The system determines the number of LPs associated with the selected MLP.
− If there is more than one distinct LP, the user must identify which LP is to be put away by
entering or scanning a valid LP.

HighJump Warehouse Advantage Functional Description 53

 − By default, the system suggests the next LP to be put away based on LP number sequence.
• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.
• If the MLP has an LP (or LPs) with one or more items, the user can put away the entire MLP by
selecting the F4: Move All option.
• The system determines if there are any items associated to the LP that can be cross-docked
against a planned move request. An item is eligible for cross-dock against a planned move
request if a planned move request exists for the item which meets the following criteria:
− The planned move request is open (the requested quantity associated to the planned move
request has not been fulfilled and has not been flagged as "pick complete").
− The planned move request's due date is less than or equal to the current date.
• If no item on the LP meets the criteria, the system proceeds to Put-Away of LPs.

Put-Away of LPs
• The system determines the number of distinct item numbers on the selected LP.
− If there is more than one distinct item, the user must identify what item is to be put away by
either (a) entering or scanning a valid item number, valid alternative item number, or UPC
number associated to an item on the selected LP, (b) accepting the suggested item, or (c)
pressing the F4: Put LP option to put away a single item LP.
− By default, the system suggests the next item to be put away based on item number
sequence. If the F4: Put LP option is selected, the system proceeds to Put-Away of All Items
from LP.
− If the LP is associated with more than one item, the user can put away the entire LP by
selecting the F4: Move All option.

Put-Away of an Item from LP

• If there is only one distinct item number on the selected LP, the user is not prompted to scan an
item number.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, the preferred lot number to be put away must be identified by
entering or scanning a lot number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The user can put away the entire quantity of an item (or items) in a single location by selecting
the F4: Move All option.
• The system executes the single-item put-away rules for the identified item number and lot
number. For a complete list of the single-item put-away rules, see HighJump Warehouse
Advantage Picking and Put-Away Rules.
− The put-away location must be identified by either entering or scanning the suggested
location, or by entering or scanning a valid override location. The put-away location can be
overridden by scanning any valid location that already contains the item, any multiple-item

54 HighJump Warehouse Advantage Functional Description

 location in the item's put-away class, any multiple-item location in the item's overflow put-
away class, any empty location, cross-dock location, staging location, or aisle location.
− If the suggested put-away location is overridden with a valid location, a 101 "Putaway
Location Over-ride" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the suggested put-away location is overridden with a staging or a Pickup & Delivery
location, a Directed Pickup work request is created for the put-away inventory.
− If the suggested location has reached a user-determined physical capacity, the user can
select the F2: Full option. The F2: Full option flags the location as "full", and then re-executes
the Single-item put-away rules. After a location is flagged as "full", the location remains
flagged as "full" until at least one item quantity is removed from the location. A 102 "Location
Reported Full" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the suggested location is a system-determined "empty" location, but the location is not
physically empty, the user can select the F5: Count option. If the F5: Count option is selected,
the system generates a Cycle Count by Location work queue task. A 103 "Location Reported
not Empty" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a
loose item and dissolves the LP after the final item is put away. If the Item/HU indicator on
the entered location is ‘H’, the user is prompted and required to enter a destination License
Plate Identifier.
• If the F4: Move All option is selected, the system proceeds to Put-Away of Individual Item, All Lots
Quantity from LP.

Put-Away of Individual Item/Lot Quantity from LP

• The item/lot quantity to be moved from the specified LP on the user's equipment is entered in the
displayed unit of measure. By default, the displayed unit of measure is (a) the largest defined unit
of measure for the item (if multiple units of measure are available for the item) relative to the
quantity of the identified item on the LP, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• The quantity moved, regardless of the selected unit of measure, is converted to the item's base
unit of measure when placed in the specified put-away location.
• The system validates that the quantity entered is less than or equal to the quantity of the item
number and lot number(s) specified to be moved.
• If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a loose
item and dissolves the LP after the final item is put away. If the Item/HU indicator on the entered
location is ‘H’, the user is prompted and required to enter a destination License Plate Identifier.
• The system moves the specified item quantity of the LP from the user's equipment to the
specified location and LP (if specified). A movement transaction is generated for each item
quantity moved from the LP to the specified location and LP (if applicable). The specific
movement transactions are based on the process that initiated the Directed Put-Away process.
• If the total quantity of the item is moved and there is only one distinct item number associated to
the LP, the user can elect to move the entire LP and contents to the put-away location by
selecting the F4: Put LP option. The system moves the LP and contents of the LP from the user's
equipment to the specified location. The system generates a movement transaction for each item

HighJump Warehouse Advantage Functional Description 55

 quantity moved from the LP to the specified location. The specific movement transactions are
based on the process that initiated the Directed Put-Away process.

Put-Away of Individual Item, All Lots Quantity from LP

• The item quantity to be moved from the specified LP on the user's equipment is assumed to be
the quantity associated with the item on the LP.
• The quantity moved, regardless of the selected unit of measure, is converted to the item's base
unit of measure when placed in the specified put-away location.
• If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a loose
item and dissolves the LP after the final item is put away. If the Item/HU indicator on the entered
location is ‘H’, the user is prompted and required to enter a destination License Plate Identifier.
• The system moves the specified item quantity of the LP from the user's equipment to the
specified location and LP (if specified). A movement transaction is generated for each item
quantity moved from the LP to the specified location and LP (if applicable). The specific
movement transactions are based on the process that initiated the Directed Put-Away process.
• If the total quantity of the item is moved and there is only one distinct item number associated to
the LP, the user can elect to move the entire LP and contents to the put-away location by
selecting the F4: Put LP option. The system moves the LP and contents of the LP from the user's
equipment to the specified location. The system generates a movement transaction for each item
quantity moved from the LP to the specified location. The specific movement transactions are
based on the process that initiated the Directed Put-Away process.

Put-Away of All Items from LP

• If there is more than one distinct item, the user can elect to put all of the items away in a single
location by selecting the F4: Move All option. The F4: Move All option executes the multiple-item
put-away rules. The multiple-item put-away rules are:

Rule #1: Attempt to find an empty, multiple-item location in the zone associated to the user's
equipment.
− The put-away location must be identified by either entering or scanning the suggested
location, or by entering or scanning a valid override location. The put-away location can be
overridden by scanning any valid multiple-item, staging, or aisle location.
− If the suggested put-away location is overridden with a valid location, a 101 “Putaway
Location Over-ride” Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a
loose item. If the Item/HU indicator on the entered location is ‘H’, the user is prompted and
required to enter a destination License Plate Identifier.
− If the suggested location has reached a user-determined physical capacity, the user can
select the F2: Full option. The F2: Full option flags the location as "full", and then re-executes
the Multiple-item put-away rules. After a location is flagged as "full", the location remains
flagged as "full" until at least one item quantity is removed from the location. A 102 "Location
Reported Full" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the suggested put-away location is overridden with either a staging or Pickup & Delivery
location, a Directed Pickup work request is created for the put-away inventory.

56 HighJump Warehouse Advantage Functional Description

 Rule #2: Attempt to find a partial, multiple-item location in the zone associated to the user's
equipment.
− The put-away location must be identified by either entering or scanning the suggested
location, or by entering or scanning a valid override location. The put-away location can be
overridden by scanning any valid multiple-item, staging, or aisle location.
− If the suggested put-away location is overridden with a valid location, a 101 “Putaway
Location Over-ride” Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the suggested location has reached a user-determined physical capacity, the user can
select the F2: Full option. The F2: Full option flags the location as full, and then re-executes
the Multiple-item put-away rules. After a location is flagged as full, the location remains
flagged as full until at least one item quantity is removed from the location. A 102 "Location
Reported Full" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a
loose item and dissolves the LP after the final item is put away. If the Item/HU indicator on
the entered location is ‘H’, the user is prompted and required to enter a destination License
Plate Identifier.
− If moving the source LP, along with the LP's contents, to the location the user enters or scans
the source LP.
− If moving the LP's contents from the source LP to another LP residing in the location, the user
enters or scans an LP corresponding to an LP residing in the location.
− If moving the LP's contents from the source LP as loose items within the location, the user
should not specify an LP.
• The system moves the contents of the LP from the user's equipment to the specified location and
LP (if specified). A movement transaction is generated for each item quantity moved from the LP
to the specified location and LP (if applicable). The specific movement transactions are based on
the process that initiated the Directed Put-Away process.
• If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a loose
item and dissolves the LP after the final item is put away. If the Item/HU indicator on the entered
location is ‘H’, the user is prompted and required to enter a destination License Plate Identifier.

HighJump Warehouse Advantage Functional Description 57

Put-Away Level 3 Process Details
• The Directed Put-Away process manages the put-away of loose inventory residing on the user's
equipment after all LPs residing on the user's equipment have been put away.
• The system determines if there are any items associated to the user's equipment that can be
cross-docked against a planned-move request. An item is eligible for cross-dock against a
planned move request if a planned move request exists for the item which meets the following
criteria:
− The planned move request is open (the requested quantity associated to the planned move
request has not been fulfilled and has not been flagged as "pick complete").
− The planned move request's due date is less than or equal to the current date.
• If no item on the user's equipment meets the criteria, the system proceeds to Put-Away of Items.

Put-Away of Items
• The system executes the single-item put-away rules for each item number/lot number on the
user's equipment. For a complete list of the single-item put-away rules, see HighJump
Warehouse Advantage Picking and Put-Away Rules.
• The system determines the number of distinct item numbers on the user's equipment.
− If there is more than one distinct item, the user must identify what item is to be put away by
either (a) entering or scanning a valid item number, valid alternative item number, or UPC
number associated to an item on the selected LP, (b) accepting the suggested item, or (c)
pressing the F4: Move All option to select all items to be put away.
− By default, the system suggests the next item to be put away based on descending picking
flow and put-away location. If the F4: Move All option is selected, the system proceeds to
Put-Away of All Items from Equipment.

Put-Away of an Item from Equipment

• If there is only one distinct item number on the user's equipment, the user is not prompted to scan
an item number.
• The system determines the number of distinct lot numbers associated with the selected item on
the user's equipment.
• If there are multiple lot numbers, the preferred lot number to be put away must be identified by
entering or scanning a lot number associated to the selected item on the user's equipment.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the user's
equipment, the user is not prompted to scan a lot number.
• If there are multiple lot numbers for the selected item, the user can elect to put away the entire
quantity associated to all of the lot numbers for the selected item in a single location by selecting
the F4: Move All option.
• The system executes the single-item put-away rules for the identified item number and lot
number.

Note
If the F4: Move All lot numbers option is selected, only one of the lot numbers is used by the
put-away rules). For a complete list of the single-item put-away rules, see HighJump
Warehouse Advantage Picking and Put-Away Rules.

58 HighJump Warehouse Advantage Functional Description

 − The put-away location must be identified by either entering or scanning the suggested
location, or by entering or scanning a valid override location. The put-away location can be
overridden by scanning any valid location that already contains the item, any multiple-item
location in the item's put-away class, any multiple-item location in the item's overflow put-
away class, any empty location, cross-dock location, staging location, or aisle location.
− If the suggested put-away location is overridden with a valid location, a 101 “Putaway
Location Over-ride” Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the suggested put-away location is overridden with a staging or a Pickup & Delivery
location, a Directed Pickup work request is created for the put-away inventory.
− If the suggested location has reached a user-determined physical capacity, the user can
select the F2: Full option. The F2: Full option flags the location as "full", and then re-executes
the Single-item put-away rules. After a location is flagged as "full", the location remains
flagged as "full" until at least one item quantity is removed from the location. A 102 "Location
Reported Full" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a
loose item. If the Item/HU indicator on the entered location is ‘H’, the user is prompted and
required to enter a destination License Plate Identifier.
− If the suggested location is a system-determined "empty" location, but the location is not
physically empty, the user can select the F5: Count option. If the F5: Count option is selected,
the system generates a Cycle Count by Location work queue task. A 103 "Location Reported
not Empty" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
• If the F4: Move All option is selected, the system proceeds to Put-Away of Individual Item, All Lots
Quantity from Equipment.

Put-Away of Individual Item/Lot Quantity from Equipment

• The item/lot quantity to be moved from the user's equipment is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity of the
identified item on the user's equipment, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• The quantity moved, regardless of the selected unit of measure, is converted to the item's base
unit of measure when placed in the specified put-away location.
• The system validates that the quantity entered is less than or equal to the quantity of the item
number and lot number(s) specified to be moved.
• If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a loose
item. If the Item/HU indicator on the entered location is ‘H’, the user is prompted and required to
enter a destination License Plate Identifier.
• The system moves the specified item quantity from the user's equipment to the specified location.
A movement transaction is generated for each item quantity moved from the user's equipment to
the specified location and LP (if applicable). The specific movement transactions are based on
the process that initiated the Directed Put-Away process.

HighJump Warehouse Advantage Functional Description 59

 Put-Away of Individual Item, All Lots Quantity from Equipment
• The item quantity to be moved from the user's equipment is assumed to be the quantity
associated with the item on the user's equipment.
• The quantity moved, regardless of the selected unit of measure, is converted to the item's base
unit of measure when placed in the specified put-away location.
• If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a loose
item. If the Item/HU indicator on the entered location is ‘H’, the user is prompted and required to
enter a destination License Plate Identifier.
• The system moves the specified item quantity from the user's equipment to the specified location
and LP (if specified). A movement transaction is generated for each item quantity moved from the
LP to the specified location and LP (if applicable). The specific movement transactions are based
on the process that initiated the Directed Put-Away process.

Put-Away of All Items from Equipment

• If there is more than one distinct item, the user can elect to put all of the items away in a single
location by selecting the F4: Move All option. The F4: Move All option executes the multiple-item
put-away rules. The multiple-item put-away rules are:

Rule #1: Attempt to find an empty, multiple-item location in the zone associated to the user's
equipment.
− The put-away location must be identified by either entering or scanning the suggested
location, or by entering or scanning a valid override location. The put-away location can be
overridden by scanning any valid multiple-item, staging, or aisle location.
− If the suggested put-away location is overridden with a valid location, a 101 “Putaway
Location Over-ride” Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the suggested put-away location is overridden with either a staging or Pickup & Delivery
location, a Directed Pickup work request is created for the put-away inventory.
− If the suggested location has reached a user-determined physical capacity, the user can
select the F2: Full option. The F2: Full option flags the location as full, and then re-executes
the Multiple-item put-away rules. After a location is flagged as full, the location remains
flagged as "full" until at least one item quantity is removed from the location. A 102 "Location
Reported Full" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a
loose item. If the Item/HU indicator on the entered location is ‘H’, the user is prompted and
required to enter a destination License Plate Identifier.

Rule #2: Attempt to find a partial, multiple-item location in the zone associated to the user's
equipment.
− The put-away location must be identified by either entering or scanning the suggested
location, or by entering or scanning a valid override location. The put-away location can be
overridden by scanning any valid multiple-item, staging, or aisle location.
− If the suggested put-away location is overridden with a valid location, a 101 “Putaway
Location Over-ride” Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.

60 HighJump Warehouse Advantage Functional Description

 − If the suggested location has reached a user-determined physical capacity, the user can
select the F2: Full option. The F2: Full option flags the location as "full", and then re-executes
the Multiple-item put-away rules. After a location is flagged as "full", the location remains
flagged as "full" until at least one item quantity is removed from the location. A 102 "Location
Reported Full" Exception Log entry is generated and saved in the HighJump Warehouse
Advantage Exception Log.
− If the Item/HU indicator on the entered location is ‘I’, the system puts away the item as a
loose item. If the Item/HU indicator on the entered location is ‘H’, the user is prompted and
required to enter a destination License Plate Identifier.
− The system moves the contents of the user's equipment to the specified location. A
movement transaction is generated for each item quantity moved from the user's equipment
to the specified location and LP (if applicable). The specific movement transactions are based
on the process that initiated the Directed Put-Away process.

Pick Plan for Put-Away

When an inventory is incremented in a storage type location, allocation queue records are generated
for the items. For more information on how allocation records and allocation queue records are
processed, see HighJump Warehouse Advantage Technical Reference Guide.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 312 Cross-dock for Picking (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated as each item/lot number quantity is allocated to a specific open order line (applies
when moving items with respect to Cross-Dock Profile 1).
• HighJump Warehouse Advantage generates 312 Cross-dock for Picking (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated as each item/lot number quantity is moved from the user's equipment to the
specified cross-dock location line (applies when moving items with respect to Cross-Dock Profile
2).
• HighJump Warehouse Advantage generates 262 Cross-dock for Directed Move (Put) and 264
Cross-dock for Directed Move (Production) transactions as detailed in the HighJump Warehouse
Advantage Log Transactions specification. The transactions are generated as each item/lot
number quantity is moved to the planned move destination location line (applies when moving
items with respect to Planned Move Cross-Dock).
• HighJump Warehouse Advantage generates process-specific movement transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated as each item/lot number quantity is moved into the specified location.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 61

VAS Execute
The VAS Execute process manages the execution of VAS (value added services) operations for
received inventory. During the receiving process, the VAS Profile Verification process determines that
VAS operations are needed for the inventory if any VAS Profiles exist for: the item’s properties (item
number, UOM, inventory class, inventory category, inventory type, client code, DIA); the properties of
the inbound order the inventory is received against (order type, carrier, vendor); the transaction type.

When a user enters or scans a VAS type location that contains LPs for which pending VAS task
operations exist, the system initiates the execution of VAS tasks. As the user identifies and confirms
VAS LPs, the system directs the user to perform the VAS operations on items.

Notes
During receiving, inventory on which a recall has been placed is automatically put on hold on
the receiver’s equipment. If an item is recalled, VAS operations apply only if the VAS Profile
has Process Held Inventory set to “Yes”.
If a VAS task is created for an item that is later recalled, the VAS task is executed regardless
of the setting for the VAS Profile’s Condition for Process Held Inventory.

There are three types of VAS operation tasks: Command, Interrogation or Disposition. If the task type
is Interrogation or Disposition, the system automatically applies the VAS operations to the entire item
quantity. If the task type is Command, the user enters the item quantity on which they performed the
VAS operation.

As the user completes VAS task operations, the process completes VAS task work requests and
generates VAS Execute specific transactions. Depending on operation responses and operation type
(Disposition and Interrogation), the system may create additional VAS tasks for inventory. The user
can also mark the inventory as damaged with this process.

The system continues to execute VAS tasks against an LP until the user completes all of the pending
tasks associated to the active VAS location type. When all tasks for an LP are completed, the system
moves the LP to the user’s equipment and initiates the Directed Put-Away process.

Process Details

VAS Execute—Enter VAS Location and Find VAS LP

• The user is prompted to identify the VAS location to begin the process. The VAS location is a
VAS type location that contains LP-based inventory for which pending VAS operation work tasks
exist. The VAS location is identified by scanning or entering a location. The system verifies that
the input location is a VAS type location.
• Based on the input VAS location, the system finds the next highest priority pending VAS LP that
exists in the location and has at least one VAS operation task still pending. The system suggests
an LP to the user, along with a short description of the VAS task to be performed.
• If the system is unable to find a pending VAS LP in the location, the system prompts the user to
scan or enter an LP requiring VAS operations.
− If the user identifies an LP, the system verifies that the identified LP is a valid LP that is not
currently assigned to another user and that it has at least one pending VAS task that needs
to be performed in a VAS type location that is the same type as the user’s current location.
− If the identified LP does not have any pending VAS tasks, the system displays a message to
the user indicating that no VAS work is available.

62 HighJump Warehouse Advantage Functional Description

 • If the identified, valid VAS LP is not currently located in the user’s current VAS location, the
system prompts the user to move the LP to the current location. The user scans or enters the
current VAS location to confirm the move. The system generates a VAS Audit Log Move
transaction and a VAS Move transaction.

VAS Execute—Enter Item and Display VAS Task

• The system determines the next best item on the LP requiring VAS operations and displays the
next item along with the task code and description of the VAS task to be performed. The user
identifies the item by scanning or entering the item number, UPC or alternate item number value.
Alternatively, if there are multiple items requiring VAS operations on the LP, the user may select
the item from a list by pressing the F8: LST option. As the item is identified, the system verifies
that the item exists on the LP and that the item has a pending VAS task to perform at their
location.
• If the identified item does not have any pending VAS Tasks, the system displays a message to
the user stating that VAS tasks for the item are no longer available. Then the system repeats the
process and attempts to find the next available item.
• When work is identified, the system displays a description of the VAS tasks that need to be
performed. If there is more than one task available, the user can press the F8:LST option to
select the task from a list.
• As the task is identified, the system assigns the VAS task work request to the user and
increments the number of workers assigned.
• Based on the purchase order that is associated with the selected VAS task, the system
determines if there are VAS specific purchase order master and detail comments that need to be
displayed. The system displays the VAS comments to the user and then the user presses Enter
to continue.
• Based on the selected VAS task, the system determines if the task is either a Command type
task or an Interrogative or Disposition type task. If the task is a Command Task, the system
proceeds to VAS Execute—Command Task, otherwise the system proceeds to VAS Execute—
Interrogative/Disposition Task.

Notes
Command—Displays text to the user instructing or informing them of the VAS operation to
perform. The user reads the instructions and indicates they have completed the operation.
Interrogative—Provides instructions to the user for determining disposition. During the
inspection process of an item, the system displays the suggested disposition and instructions.
The system prompts the user if any quantity of the item/lot on the LP should be held. If the
user indicates that it should be held, then the system prompts the user for a VAS reason
code and the held portion of the inventory is immediately moved into a “damaged” storage
location and placed on hold.
Disposition—Provides a series of questions to the user. The system displays a list of valid
responses. Each response can optionally be associated to a VAS profile, so if the user
selects the response, the VAS operations for that profile is automatically added to the VAS
operations required by this inventory.

VAS Execute—Interrogative/Disposition Task

• Based on the selected VAS task, the system displays defined interrogative/disposition questions
to the user. The system prompts the user to press Enter to continue.

HighJump Warehouse Advantage Functional Description 63

 • When the user selects the Enter key on the question screen, the system displays the list of
defined VAS responses. The VAS responses are specific to the VAS question that is associated
with the selected VAS Task. If the user selects the F5: DG option to identify damaged items, the
system proceeds to VAS Execute—VAS Hold/Damage.
• Based on the selected VAS response, the system generates the VAS Execute specific
transactions. The system updates the VAS Task specific work requests for the entire quantity and
LP.
• The system unassigns the user from the selected VAS task work request.
• The system determines if a Prompt for Quantity to Hold value has been defined for the selected
response. If the value is “Yes”, then the system proceeds to VAS Execute—Hold/Damage.
• The system determines if there are other pending VAS task operations associated with the
currently selected LP and VAS Location type.
− If other tasks exist, the system proceeds to VAS Execute—Enter Item and Display VAS Task.
− If no other tasks exist, the system prompts the user to pick up the LP and place it on their
equipment. After the user moves the LP to their equipment, the system initiates the Directed
Put-Away process.

VAS Execute—Command Task

• Based on the selected VAS task, the system displays the defined VAS command instructions to
the user in the user’s locale. The system prompts the user to press Enter to continue.
• If there is more than one lot number for the item on the current LP, the system prompts the user
for lot number
• The system prompts item quantity using the Universal Quantity Behavior Type–Request.
Damaged items can be identified and immediately put away during the process by selecting the
F5: DG option displayed at the quantity prompt.
• The user is prompted for serial numbers when the item is configured for full serial control. When
prompted, the user scans each serial number in an “X of Y” method for the received quantity in
the base unit of measure for the item, with the ability to use the F3: Done option during scanning
to change the quantity to “X”. Scanned serial numbers are validated and must belong to that
quantum of inventory.
• The quantity entered, regardless of the selected unit of measure, is converted to the item's base
unit of measure and is used to perform all VAS command specific transactions. The system
updates the quantity completed for the selected VAS tasks work request.
• The system determines if there is any remaining quantity associated to the selected VAS task
work request. If the remaining quantity value is zero, the system un-assigns the user from the
selected task and decrements the number of workers assigned.
• The system prompts the user to enter a destination LP on which to place the current VAS task
item quantity. The user may press Enter to leave the inventory on the current LP or they may
enter a different LP. If the user enters a different LP, the system validates that the identified LP is
either new or that it exists in the current VAS location.

64 HighJump Warehouse Advantage Functional Description

 • If the destination LP entered is not the source LP, the system moves the inventory to the new LP
and decrements the quantity of the source LP. The system generates a VAS Audit Log Move
transaction and a VAS Move transaction and then creates the remaining VAS tasks for the new
LP. Then the system validates the source LP still exists. If the source LP does not exist, the
system updates all remaining VAS tasks to complete for the source LP. If the source LP does
exist, then the system checks to see if there are any remaining VAS tasks to work on in the
current VAS location. If there is no work to complete in the VAS location for the destination LP,
then the system creates a Directed Pickup work queue request for the destination LP.
• The system determines if there are other pending VAS task operations associated with the
currently selected LP and VAS Location type.
− If other tasks exist, the system proceeds to VAS Execute—Enter Item and Display VAS Task.
− If no other tasks exist, the system prompts the user to pick up the LP and place it on their
equipment. After the user moves the LP to their equipment, the system initiates the Directed
Put-Away process.

VAS Execute—VAS Hold/Damage

• The system may prompt the user for the VAS Damage Reason Code.
− If the user selected F5: DG, the system prompts the user for the reason code.
− If the user performed a disposition or interrogation task type, and the response they selected
is marked “Yes” for Prompt for Quantity to Hold and a reason code is associated to the
response, the system does not prompt the user for the reason code.
• If there is more than one lot number for that item on the current LP, the system prompts the user
to enter the lot number of the damaged inventory.
• The system prompts for item quantity to be held using the Universal Quantity Behavior Type–
Request.
• The user is prompted for serial numbers when the item is configured for full serial control. When
prompted, the user scans each serial number in an “X of Y” method for the received quantity in
the base unit of measure for the item, with the ability to use the F3: Done option during scanning
to change the quantity to “X”. Scanned serial numbers are validated and must belong to that
quantum of inventory.
• The quantity held, regardless of the selected unit of measure, is converted to the item's base unit
of measure and placed in the location associated to the user's equipment. While on the
equipment, the item quantity is visible within the HighJump Warehouse Advantage system but not
available for picking.
• After entering the quantity of damaged items, the system prompts the user to scan a put-away
location. The system verifies that the entered location corresponds to a valid storage location.
• If the put-away location entered is LP-controlled, then the system prompts the user for a
destination LP.
• The system moves the damaged item quantity to the specified storage location and decrements
the quantity of the item in the source location. Then, the system generates a VAS Audit Log
Damage transaction and a VAS Damage transaction.
• If the source VAS LP no longer exists, the system updates all pending VAS tasks to complete for
the LP. The system proceeds to VAS Execute—Enter VAS Location and Find VAS LP.

HighJump Warehouse Advantage Functional Description 65

 • If the source VAS LP exists and the quantity completed for the VAS task is greater than or equal
to the LP’s inventory quantity for the item, the system updates the VAS task to complete for the
LP and item. Then the system determines if more pending VAS tasks need to be completed for
the VAS location type. If no VAS tasks exist, the system creates a Directed Pickup work queue.
The system proceeds to VAS Execute—Enter VAS Location and Find VAS LP.
• If the source VAS LP exists and the quantity completed for the VAS task is less than the LP’s
inventory quantity for the item, then the system proceeds to VAS Execute—Enter VAS Location
and Find VAS LP.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 600 VAS Execute transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
when a VAS Task (command, disposition or interrogative) is executed. As a configuration option,
the user may define their own three character VAS task specific transaction code to be used in
place of the default 600 transaction code.
• HighJump Warehouse Advantage generates a 601 VAS Move (Pick) transaction as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated when inventory is moved between VAS locations.
• HighJump Warehouse Advantage generates a 602 VAS Move (Put) transaction as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
when inventory is moved between VAS locations or the inventory is put away.
• HighJump Warehouse Advantage generates a 603 VAS Damage transaction as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
when inventory is damaged during the VAS Execute process.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

The following configuration requirements apply.

Before using this process, all VAS task commands and interrogative and disposition questions must
be configured using the VAS Web pages in HighJump Advantage Dashboard.

For information about the Web pages, see “Value Added Services Pages” in HighJump Advantage
Dashboard Functional Description.

66 HighJump Warehouse Advantage Functional Description

Movement
Movement includes the following processes:
• Directed Pickup
• Move
• Request an Item
• Create Pickup
• Replenishment
• Directed Move
• Execute Planned Move
• Execute Planned Move Pickup

Directed Pickup
The Directed Pickup process manages the movement of product within the warehouse based on a
directed pickup request created when inventory is staged to either a Staging or Pickup & Delivery
location using the Staged Receipt or Directed Put-away processes. Based on the Directed Pickup
request, the process suggests the location associated to the request and then directs the user to pick
a specific item and quantity, MLP, or LP from the location in parallel with moving the product to the
user's equipment.

After the user's equipment reaches a user-determined capacity, or there are no more items on the
directed pickup request to pick, the system directs the user to put away the items on their equipment.

Process Details
• The system determines if there is at least one open directed pickup request in the work queue. If
no open directed pickup request is found, the system displays the "no work available" message.
• If at least one open directed pickup request is found, the system suggests the location associated
with the directed pickup request.
− If the user enters or scans the suggested location, the system assigns the user to the
directed pickup request and increments the number of workers assigned to the request.
− If the user overrides the suggested location, the system determines if there is at least one
open directed pickup request in the user-identified location.
• If no request is found, the system displays the "no work available" message.
• If a request is found, the system assigns the user to the directed pickup request and
increments the number of workers assigned to the request.
• The license control option of the pickup location determines the picking method.
− If the user should pick loose items, the system proceeds to Directed Pickup – Picking Loose
Items.
− If the user should pick by LP, the system proceeds to Directed Pickup – Picking LP-based
Items.

HighJump Warehouse Advantage Functional Description 67

 − If the user should pick by MLP, the system proceeds to Directed Pickup – Picking MLP-based
Items.

Directed Pickup—Picking Loose Items

• To identify the item number to be picked, the user must enter or scan a valid item number, valid
alternative item number, or UPC number associated to the suggested item.
• If the item is configured for full lot control, the system prompts the user for a lot number. The user
must identify the preferred lot number by scanning or manually entering a lot number associated
to the selected item in the location.
• The system determines the quantity to be picked from the location, item, lot number, and LP. The
item/lot quantity to be picked from the suggested location is entered in the displayed unit of
measure.
• By default, the displayed unit of measure is (a) the largest defined unit of measure for the item (if
multiple units of measure are available for the item) relative to the quantity to be picked of the
identified item/lot, or (b) the standard unit of measure of the item (if multiple units of measure are
not available for the item). If multiple units of measure are available for the item, the user can
select a unit of measure by either (a) pressing the F2: UOM option to display the next smallest
unit of measure or (b) pressing the F8: LST option to select a unit of measure from the available
list of units of measure.

Note
The F2: UOM and F8: LST options are only available if multiple unit of measure records exist
for the specific item/lot.

• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• If the item is configured for full serial control and the quantity to be picked does not represent the
entire quantum of inventory, the system prompts the user for serial numbers. When prompted, the
user scans each serial number in an “X of Y” method. The system validates that each serial
number belongs to that quantum of inventory.
• The system moves the specified item quantity from the source location to the user's equipment,
and then generates a directed pickup transaction for each item quantity.
• The system increments the quantity picked associated to the directed pickup request. After
picking the requested quantity, the system completes the directed pickup request.
• After the user's equipment reaches a user-determined capacity or there are no directed pickup
work requests, the user selects the F3: Done option. The F3: Done option initiates the Directed
Put-Away process.

68 HighJump Warehouse Advantage Functional Description

 Directed Pickup—Picking LP-based Items
• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The user scans or enters an LP to
identify the source LP. The system verifies the LP corresponds to an existing LP meeting the
following criteria:
− The LP is not on hold.
− The LP resides in the specified pick location.
− The LP is associated to unallocated inventory.
− The LP contains the item to be picked.
• The system moves the specified LP to the user's equipment. A directed pickup transaction is
generated for each LP moved to the user's equipment.
• The system determines if the quantity remaining to be picked associated to the directed pickup
request is greater than zero. If the remaining quantity is zero, the directed pickup request is
completed.
• After the user's equipment has reached a user-determined capacity or there are no directed
pickup work requests, the user selects the F3: Done option. The F3: Done option initiates the
Directed Put-Away process.

Directed Pickup—Picking MLP-based Items

• When picking items associated to an MLP-based location, the user is prompted to identify a
source MLP. The source MLP is the MLP containing the item to be picked. The user scans or
enters an MLP to identify the source MLP. The system verifies the MLP corresponds to an
existing MLP meeting the following criteria:
− The MLP is not on hold.
− The MLP resides in the specified pick location.
− The MLP is associated to unallocated inventory.
− The MLP contains the item to be picked.
• The system moves the specified MLP to the user's equipment. A directed pickup transaction is
generated for each MLP moved to the user's equipment.
• The system determines if the quantity remaining to be picked associated to the directed pickup
request is greater than zero. If the remaining quantity is zero, the directed pickup request is
completed.
• After the user's equipment has reached a user-determined capacity or there are no directed
pickup work requests, the user selects the F3: Done option. The F3: Done option initiates the
Directed Put-Away process.

HighJump Warehouse Advantage Functional Description 69

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 211 Directed Pickup (Pick) transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for each item quantity moved to the user's equipment.
• HighJump Warehouse Advantage generates 212 Directed Pickup (Put) transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated when the user moves MLPs/LPs/items into a destination location.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

70 HighJump Warehouse Advantage Functional Description

Move
The Move process manages the movement of items between locations within the warehouse. Based
on a specific source location, license plate (LP), or master license plate (MLP), item quantities are
identified to the system in parallel with the movement of the items from the location to the user's
equipment.

After the user's equipment reaches a user-determined capacity or there are no more items to be
moved, the system directs the user to put the items on their equipment away.

Process Details

The following process detail applies.

• The user can move items directly from a location (loose items), from an LP (license plate), or from
a master license plate (MLP) residing in a location.

Move—Moving Loose Items

• The system prompts the user to identify a source location to begin the process. The source
location is the location containing the item or items to be moved and the type of location (LP,
MLP, or item-based), determines whether loose items, LPs, or MLPs will be picked up. The user
identifies the source location by scanning or entering any location. The system verifies the
location corresponds to a valid non-equipment type.
• The system prompts the user to identify the item number associated with the product to be moved
by entering or scanning a valid item number, valid alternative item number, or UPC number
associated to the item number.
• If the item is configured for full lot control, the system prompts the user for a lot number.
• The system prompts for quantity to move using the Universal Quantity Behavior Type–Request.
• The system verifies the quantity is greater than zero, and does not verify the quantity is less than
or equal to the quantity of the item/lot number residing in the location.
• If the item is configured for full serial control and the quantity to be moved does not represent the
entire quantum of inventory, the system prompts the user for serial numbers. When prompted, the
user scans each serial number in an “X of Y” method. The system validates that each serial
number belongs to that quantum of inventory.
• The system moves the specified item quantity from the source location to the user's equipment
and LP or MLP (if specified). A movement transaction is generated for each item quantity moved
to the user's equipment and LP or MLP (if applicable).
• The system returns the user to the source location prompt. After the user's equipment reaches a
user-determined capacity or when there are no more items to be moved, selecting the F3: Done
option initiates the Directed Put-Away process.

HighJump Warehouse Advantage Functional Description 71

 Move—Moving MLP-based Items
• The system prompts the user to identify a source location to begin the process. The source
location is the location containing the item or items to be moved, and the type of location (MLP,
LP, or item-based) determines whether loose items, MLPs, or LPs will be picked up. The user
identifies the source location by scanning or entering any location. The system verifies the
location corresponds to a valid non-equipment type.
• When moving items associated to an MLP-based location, the system prompts the user to identify
a source MLP to begin the process. The source MLP is the MLP containing the LP or LPs to be
moved. The user identifies the source MLP by scanning or entering an MLP. The system verifies
the MLP corresponds to an existing MLP meeting the following criteria:
− The MLP is residing in a non-equipment type location.
− The MLP is associated to unallocated inventory.
• The user must either (a) identify which LP to move by scanning a valid LP number, (b) select the
F2: Take MLP option, or (c) select the F3: Done option. If the user scans a valid LP, the system
proceeds to Move—Moving LP-based Items. If the user selects the F2: Take MLP option, the
system proceeds to Move—Move Entire MLP from Location. If the user selects the F3: Done
option, the system initiates the Directed Put-Away process.

Move—Moving LP-based Items

• The system prompts the user to identify a source location to begin the process. The source
location is the location containing the item or items to be moved and the type of location (MLP,
LP, or item-based) determines whether loose items, MLPs, or LPs will be picked up. The user
identifies the source location by scanning or entering any location. The system verifies the
location corresponds to a valid non-equipment type.
• When moving items associated to an LP-based location, the system prompts the user to identify a
source LP to begin the process. The source LP is the LP containing the item or items to be
moved. The user identifies the source LP by scanning or entering an LP. The system verifies the
LP corresponds to an existing LP meeting the following criteria:
− The LP is residing in a non-equipment type location.
− The LP is associated to unallocated inventory.
• The system lists the quantity and item number for each item associated to the LP.
• The user must identify which item to move by either (a) entering or scanning a valid item number,
valid alternative item number, or UPC number associated to an item on the selected LP or (b)
pressing the F2: Take LP option to move all items associated to the LP. If the user selects the F2:
Take LP option, the system proceeds to Move—Move Entire LP from Location; otherwise, the
system proceeds to Move—Movement of Individual Item/Lot Quantity from LP.

Move—Movement of Individual Item/Lot Quantity from LP

• If the item is configured for full lot control, the preferred lot number to be moved must be identified
by entering or scanning a lot number associated to the selected item on the LP.
• The system verifies that the identified item and lot number exists on the specified LP. The item
quantity to be removed from the specified LP is entered in the displayed unit of measure.

72 HighJump Warehouse Advantage Functional Description

 • By default, the displayed unit of measure is (a) the largest defined unit of measure for the item (if
multiple units of measure are available for the item), or (b) the standard unit of measure of the
item (if multiple units of measure are not available for the item). If multiple units of measure are
available for the item, the user can select a unit of measure by either (a) pressing the F2: UOM
option to display the next smallest unit of measure or (b) pressing the F8: LST option to select a
unit of measure from the available list of units of measure.

Note
The F2: UOM and F8: LST options are only available if multiple unit of measure records exist
for the specific item/lot.

• The system verifies that the quantity is greater than zero and less than or equal to the quantity of
the item/lot number residing on the LP.
• If the item is configured for full serial control, the system prompts the user for serial numbers.
When prompted, the user scans each serial number in an “X of Y” method. The system validates
that each serial number belongs to that quantum of inventory.
• The system moves the specified item quantity from the source location and LP to the user's
equipment and LP (if specified). A movement transaction is generated for each item quantity
moved to the user's equipment and LP (if applicable).
• The system returns the user to the source location prompt. When the user's equipment has
reached a user-determined capacity or when there are no more items to be moved, the user
selects the F3: Done option. The F3: Done option initiates the Directed Put-Away process.

Move—Move Entire MLP from Location

• The user can elect to move an entire MLP and its contents from a location by selecting the F2:
Take MLP option.
• The system moves the MLP and its contents from the location associated to the MLP to the
user's equipment. A movement transaction is generated for each item quantity associated to the
MLP.

Move—Move Entire LP from Location

• The user can elect to move an entire LP and its contents from a location by selecting the F2:
Take LP option.
• The system moves the LP and its contents from the location associated to the LP to the user's
equipment. A movement transaction is generated for each item quantity associated to the LP.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 201 Move (Pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity moved to the user's equipment.
• HighJump Warehouse Advantage generates 202 Move (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity moved to the destination location.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

HighJump Warehouse Advantage Functional Description 73

Configuration Requirements

There are no configuration requirements.

Request an Item
The Request an Item process allows a user to create or modify a directed move task to move a
specified quantity of an item to a specified location. This process can be utilized to initiate the
movement of materials to a production location within the warehouse, or to manually initiate the
replenishment of materials to forward pick locations.

A directed move request consists of the following information:

• A user-assigned order number (optional)
• A user-assigned priority
• A user-assigned delivery date
• A user-assigned delivery time
− Item number to be delivered
− Quantity to be delivered
− Deliver-to location
• Multiple item number/delivery-to location details can be associated to each directed move
request.

74 HighJump Warehouse Advantage Functional Description

Process Details

The following process details apply.

Request an Item—Identify Order

• The user is prompted to identify an order number to begin the process. An order number is a
user-defined identifier to associate to the directed move request. The logical assignment provides
a basis to maintain, view, and report on the directed move request. By default, the system
displays the order number, priority, date due, and time due associated with the first open directed
move request.
• The order number is identified by either entering a user-defined identifier, selecting the displayed
open order number, or by leaving the order number blank. The order number is not required.
• The system validates that the order number (a) is unique, or (b) corresponds to an existing, open
directed move request.
• If the order corresponds to an existing, open directed move request the system proceeds to
Request an Item—Details.
• The priority associated with the directed move request must be identified by entering a priority, or
by accepting the default priority. The system validates the priority is a numeric value between 1
and 99.
• The date due associated with the directed move request must be identified by entering a valid
date (in mmddyyyy format), or by selecting the F2: Today option to select the current date as the
due date. The system validates the date is a valid date.
• The time due associated with the directed move request must be identified by entering a valid
time (in hhmm format), or by selecting the F2: Now option to select the current time as the due
time. The system validates the time is a valid time between 0000 and 2359.
• The destination location (the location to which the product is to be delivered) is identified by
scanning or entering any location. The system verifies the location corresponds to a valid
location.

Request an Item—Details
• The item number associated with the product to be delivered must be identified by entering or
scanning a valid item number or a valid alternative item number or UPC number associated to the
item number.
• The system will not verify the availability of inventory associated to the identified item.
• If the item request already exists for the specified order and destination location, the system
proceeds to Request an Item—Edit Item Quantity.

HighJump Warehouse Advantage Functional Description 75

 Request an Item—Add Item Quantity
• The system prompts for quantity using the Universal Quantity Behavior Type–Request.
• The system verifies that the quantity is greater than zero, and does not verify the quantity with
respect to available inventory for the item.
• After a quantity is entered, the system creates a directed move work queue task with the
specified order number, priority, date due, and time due (if the directed move work queue task
does not already exist). A directed move detail request is created for the specified item number,
quantity, and deliver-to location. An allocation queue record is generated for the item.
• A directed move request transaction is generated for each deliver-to location/item quantity
associated to the directed move request.

Request an Item—Edit Item Quantity

• The item to be moved displays its current quantity associated to the item request and the total
quantity already picked for the request.
• The system prompts the user to enter a new remaining quantity to be picked using the Universal
Quantity Behavior Type–Request. The system validates the entered quantity is not negative. The
system calculates the difference between the current remaining quantity to be picked and the new
remaining quantity to be picked and adds the difference to the requested quantity to determine
the new requested quantity.
• The system determines if the picked quantity is equal to the new requested quantity.
− If the picked quantity is equal to the new requested quantity, the system updates the pick
detail status to “Pick Complete”. If all item requests associated to the directed move request
are picked complete, the system closes the work queue entry associated to the directed
move request. Any allocation records associated with the task are removed and an allocation
queue record is generated for the item.
− If the picked quantity is not equal to the new requested quantity, the system determines the
work queue status. If the work queue status is closed, the system proceeds to Request an
Item—Identify Order. If the work queue status is not closed, the system proceeds to Request
an Item—Details.
• A directed move request transaction is generated for each deliver-to location/item quantity
associated to the directed move request.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 250 Directed Move Request transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated after the deliver-to location/item quantity is entered.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

76 HighJump Warehouse Advantage Functional Description

Create Pickup
The Create Pickup process provides functionality to create a directed pickup by scanning a master
license plate (MLP) or license plate (LP).

Process Details

The following process details apply.

Create Pickup —Enter MLP or LP

• The system verifies the MLP or LP corresponds to an existing MLP or LP and meets the following
criteria:
− The MLP or LP is valid.
− The MLP or LP is residing in a non-equipment-type location.
− The MLP or LP is associated with an unallocated inventory.
− The MLP or LP is not on hold.
• If a directed pickup already exists for the MLP or LP, the system raises the pickup priority based
on a user-specified control value (not to exceed 99).
• If no directed pickup already exists for the MLP or LP, the system creates a directed pickup with
the default priority. The system prompts the user to press Enter to confirm the new directed
pickup.

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 77

Replenishment
Replenishments define the process of moving items between warehouse locations to maintain
inventory levels in the forward pick locations. Replenishment is a two-step process:
1. Create replenishment.
2. Fulfill replenishment.

Process Details

The following process details apply.

Create Replenishment

A replenishment request is generated when the inventory for an item drops below the specified
replenishment level for the location during any order fulfillment process or when a top off request is
generated by a user through HighJump Advantage Dashboard, HighJump Warehouse Advantage
web, or HighJump Warehouse Advantage application.

Replenishment Request Types

The two types of replenishment requests are MinMax and TopOff, as described in the following table.
Replenishment Work Type Description
Type
MinMax 71 Generated by the system when the inventory in a
forward pick location drops below the location’s
minimum trigger quantity during any outbound order
fulfillment processes (e.g., picking).
TopOff 72 Created by a user through:
• HighJump Advantage Dashboard > Planned
Moves > Replenishments > Generate Top Off
Replenishments.
• HighJump Warehouse Advantage web > Items >
select the Forward Pick Locations link > select
the Generate Replenishment link for the location.
• HighJump Warehouse Advantage application
through the “Request TopOff” menu option.

Fulfill Replenishment

Replenishment requests are fulfilled by using the Execute Planned Move process. Based on the
replenishment request which contains the required quantity of the specific item, the process
determines the optimal pick location based on the item UOM’s picking rule. The Execute Planned
Move process then directs the user to pick the item and quantity from the source location, moves it to
the user’s equipment, and then directs the user to the requested destination location. See Execute
Planned Move for more details on this process flow.

78 HighJump Warehouse Advantage Functional Description

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates a 307 TopOff Replenishment Request transaction
whenever a TopOff is requested as detailed in the HighJump Warehouse Advantage Log
Transactions specification. The transactions are generated for each request and contain the
indicated starting location and ending location.
• Execute Planned Move generates 305 Replenishment (Pick) and 306 Replenishment (Put)
transactions whenever a planned move of type replenishment is fulfilled. For further details, see
HighJump Warehouse Advantage Log Transactions.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

Min/Max replenishments happen based on how Forward Pick locations are configured in the
HighJump Warehouse Advantage Base Web.

Directed Move
Directed Moves are a type of planned move. This type of planned move can be generated in one of
two ways: through the Warehouse Advantage application menu option for “Request an Item” or
“Component Kit Request”. In either case, the requests are fulfilled using the Execute Planned Move
process.
For more information about…. See the following section…
Creating a work request to move inventory for an item to Request an Item
a specified destination location
Moving inventory required to fulfill a kit bill of materials Component Kit Request
to a kitting location
How these types of work requests get fulfilled Execute Planned Move

HighJump Warehouse Advantage Functional Description 79

Execute Planned Move
Execute Planned Move is the process used to fulfill all types of Planned Move requests and activities
supported in HighJump Warehouse Advantage including Directed Moves (Item Requests, Kit
Component Requests), Replenishments (MinMax, TopOff), and Slot Moves.

At a high level, the Execute Planned Move process is divided into the following steps.

Step 1—Assign Work

• Execute Planned Move considers only planned moves of the work types for Replenishment
TopOff, Replenishment MinMax, Directed Move, and Slot Move.
• The system assigns and suggests a Planned Move work queue to the user based on the priority
and age of the requests available for fulfillment. The system also makes sure that the requested
item’s picking location is in the user’s equipment zone and that the requested item has allocated
inventory.
• If the user has inventory for any planned move requests currently on their equipment, then the
system further narrows its selection criteria to work queues with the same destination pick area.
During Step 3—Outsort, the system groups planned move requests by destination pick area to
help improve efficiency.
• If the system cannot find more work that meets the criteria above or if the user indicates they are
done by using the F3 function key, then the system proceeds to Step 3—Outsort.
• Users are allowed to override the suggested item. If the user overrides the suggested item, the
system checks to make sure the planned move request is still available and that its pick location
is in the user’s equipment zone. If it is, the system unassigns the user from the previously
suggested planned move work queue and assigns them to the one they selected.

Step 2—Picking
• The system directs the user to pick the required item and move it to their equipment. After they
have picked the inventory required, the system proceeds to Step 1—Assign Work to find another
item for the user to pick.
• After the pick is complete for this item, the system searches for another Planned Move work
queue that has the same destination pick area.
• If there are no open tasks with items going to a location in the same pick area as the item
currently on the equipment, the user is directed to put away the item on the equipment before
moving to the next task. This ensures efficient and optimum put-away location path management.

Step 3—Outsort
• The user is directed to take the inventory picked to the destination locations and put it away.
These destination locations were determined when the work request was placed. For instance, if
this planned move is a replenishment, the destination is the forward pick location.

80 HighJump Warehouse Advantage Functional Description

Process Details

The following process details apply.

Execute Planned Move—Find Next Work Item

• When looking for candidate work, Execute Planned Move makes sure that the pick location is in
the user’s equipment zone and if the user already has inventory on their equipment, the system
only looks at work queues with a destination location in the same pick area as the work queues
already assigned to the user. Also, the work must have allocated inventory.
• If the system finds available work that meets the criteria, the system proceeds to Execute
Planned Move—Assign Next Work Item. If there is more than one candidate work queue, the
system selects the work queue with the highest priority and oldest due date/time.
• If no work is found that meets the criteria, the system displays the "no work available" message.
The user presses Enter to acknowledge the message and the system displays the menu.

Execute Planned Move—Assign Next Work Item

• The system then assigns the work request to the user which prevents the same work request
from being suggested to multiple users.

Execute Planned Move—Suggest Next Work Item

• The system suggests the assigned item to the user.
• To accept the suggested item, the user presses Enter. If the user accepts the suggested item,
then the system proceeds to Execute Planned Move—Prompt for Location.
• To override the suggested item, the user enters or scans a valid item number or a valid
alternative item number, or UPC number associated to an item and associated to the planned
move request. The user can press the F8: LST function key to display a list of available items. If
the user overrides the suggested item, then the system proceeds to Execute Planned Move—
Next Work Item Override.

Execute Planned Move—Next Work Item Override

• The system finds the allocated location for the selected item. For a complete list of the single-item
pick rules, see the HighJump Warehouse Advantage Picking and Put-Away Rules document.
• If the source location for the planned move request has changed and is now outside of the user’s
equipment zone, then the system indicates to the user that the work was re-planned outside of
their equipment zone. The system proceeds to Execute Planned Move—Suggest Next Work Item
to re-suggest the original item.
• If the user’s selected work request is still in their equipment zone and is available, the system un-
assigns the user from the originally suggested item and assigns the user to the overridden item.
Then the system proceeds to Execute Planned Move—Prompt for Location.

HighJump Warehouse Advantage Functional Description 81

 Execute Planned Move—Prompt for Location
• The user must verify that they are at the pick location by entering or scanning the suggested
location. The pick location cannot be overridden. If the user confirms they are at the pick location
the system proceeds to Execute Planned Move—Prompt for LP, Item, Lot.
• If the user does not confirm the pick location and selects one of the following options listed in the
table below, the system un-assigns the user from the task.
Option Description
F7: Empty The user selects this option if the suggested location does not contain the
suggested item. The option does the following:
1. Flags the inventory for the specified item in the location as “unavailable”.
2. Generates a Cycle Count by Location work queue request for the
suggested location.
3. Removes associated allocation records, and inserts record for item into
the allocation queue.
The system logs an entry into the exception log noting that the user indicated
an inventory exception. The exception log entry contains information such as
the work queue ID, item, location and the user. The system then proceeds to
Execute Planned Move—Find Next Work Item.
F2: Close The user selects this option to close the request. The system flags the work
request pick status as STAGED and closes the work record if there are no
open picks left on the work record. Any associated allocation records are
removed and an allocation queue record is generated for the item that had an
allocation removed.
The system logs an entry into the exception log noting that the user elected to
close the planned move request. The exception log entry contains information
such as the work queue ID, item, location and the user. The system then
proceeds to Execute Planned Move—Find Next Work Item.
F8: Skip The user selects this option to skip the request. The system keeps track of the
work the user skipped in their current session and does not suggest that work
again until they exit to the menu to reset their session. This work is available
for another user.
The system logs an entry into the exception log noting that the user skipped
the selected work. The exception log entry contains information such as the
work queue ID, item, location and the user. The system proceeds to Execute
Planned Move—Find Next Work Item.
F3: Done The user selects this option if their equipment has reached a user-determined
capacity. The system proceeds to Execute Planned Move—Outsort.

82 HighJump Warehouse Advantage Functional Description

 Execute Planned Move—Prompt for LP, Item, Lot
• The system determines whether inventory is stored in the location on license plates or as loose
inventory.
If the item is… Then…
loose The system prompts the user to scan the item number. The system
validates that the item exists.
on an LP The system prompts the user to scan the LP. The system validates that
the LP exists.
• After the LP and/or item number are scanned and validated, the system determines whether the
item is lot-controlled.
If the item is… Then…
not lot-controlled The system prompts the user to scan the quantity. The system validates
that the quantity exists.
lot-controlled The system determines whether there is more than one lot on the LP or in
the location (loose items).
• If there is only one lot, the system prompts the user to enter the
quantity of item number.
• If there are multiple lots, the system prompts the user to scan the lot
number. The system determines whether the lot exists in the location.
If the location is license-controlled, the system validates the item/lot
exists on the LP.
• The system proceeds to Execute Planned Move—Prompt for Quantity.
• If the user selects the F7: Empty function key to indicate the location does not contain any
inventory for the required item, the system does the following.
a) Marks inventory as unavailable for the item in the location.
b) Creates a Location Cycle Count request for the location.
c) Removes any allocation records for the item in the location.
d) Creates an allocation queue record for the item, if an allocation is removed.
e) Logs an exception noting the location was marked empty for the item.
f) Unassigns the user from the work queue.
g) Unassigns the user from the pick details.
h) Proceeds to Execute Planned Move—Find Next Work Item.

HighJump Warehouse Advantage Functional Description 83

 Execute Planned Move—Prompt for Quantity
• The system determines the quantity to be picked from the location based on the following
procedure.
Step Description
1 Get the allocated quantity to pick.
Example
Planned Quantity - Quantity Picked so far = Remaining Quantity
210 – 100 = 110
If Remaining Quantity = 110 and the Allocated Quantity = 100, the allocated
quantity is selected.
Calculated Quantity = 100.
2 Find the largest UOM of the item that is evenly divisible by the calculated
quantity.
Examples
The following examples assume the following information:
Pallet 100, Case 10, Each 1.
If the quantity is… Then use…
166 Each
110 Case
200 Pallet
Calculated Quantity = 110, UOM Divisible = Case
3 If the selected UOM’s standard handling quantity is defined, multiply it by two.
The calculated quantity should be less than the new calculated standard handling
quantity. If the calculated quantity is greater than the new calculated standard
handling quantity, then set calculated quantity to the calculated standard handling
quantity minus 1.
Examples
UOM’s Standard Handling Quantity = 50
Calculated Standard Handling Quantity = 100
Is calculated quantity of 110 < 100? No
New Calculated Quantity = 99 (changed to Calculated Standard Handling
Quantity - 1).

• To accept the suggested UOM and quantity, the user presses Enter.
• To override the suggested UOM, the user presses the F2:UOM function key to get the next UOM
conversion factor, or presses the F8:LST function key to display a list of available UOMs from
which the user may choose.

84 HighJump Warehouse Advantage Functional Description

 • The system validates the quantity entered.
− If the quantity picked is greater than the suggested quantity, the system verifies that the total
picked quantity is less than or equal to the suggested quantity plus the picking tolerance
percent of the destination location.
− If the quantity picked is less than the suggested quantity, the system displays the “Quantity
picked is less than the available. Change status to Unavailable?” prompt.
If the suggested quantity could not Then…
be picked…
due to damage or because the The user presses Y. The system completes the
remainder of the suggested quantity following tasks.
doesn’t exist in the location • Flags the inventory for the specified item in the
location as unavailable, and
• Generates a Cycle Count by Location work
queue request for the suggested location.
• Allocation records are removed for the item in
the suggested location.
• An allocation queue record are generated for
the item if allocation records were removed.
based on the physical limitations of the The user presses N.
user's equipment or by user preference
• The user is prompted for serial numbers when the item is configured for full serial control and the
quantity picked does not represent the entire quantum of inventory. When prompted, the user
scans each serial number in an “X of Y” method. The system validates that each serial number
belongs to that quantum of inventory.
• The system prompts the user for the destination license plate. The system automatically provides
the license plate if there is already a license plate on the equipment going to the same destination
location. If there is more than one license plate going to this destination, the default license plate
is the one with the largest license plate number. The destination license plate can be:
− a new license plate.
− a license plate already on the equipment that has inventory going to the same destination
location.
− the same license plate as the source license plate and is being wholly consumed by this pick.
• The system moves the specified item quantity from the source location to the user's equipment.
Then the system proceeds to Execute Planned Move—Handle Quantity Exceptions.

Execute Planned Move—Handle Quantity Exceptions

• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.

HighJump Warehouse Advantage Functional Description 85

 Execute Planned Move—Outsort
• The system directs the user to the destination with the lowest pick flow and location ID.
Option If the user… Then the user may…
A has inventory on their Press the F8: LST function key to display the destination
equipment that is locations. The user can choose any location from the list.
going to more than
The system directs the user to the selected location.
one location
B has more than one Press the F2: LP function key which allows them to enter a
license plate on their specific license plate they want to put away. The system
equipment verifies that the license plate exists on the equipment and
directs the user to the destination location associated with the
inventory on the license plate. If they cannot reach the
destination location, the user may drop their inventory at a P&D
location (option C).
C cannot get to the Drop the inventory at a P&D (Pickup and Delivery) location.
suggested destination The user must scan the license plate to put in the P&D location.
The system moves the license plate to the P&D location and
creates a Planned Move Pickup request. The system generates
a 256 Planned Move (PD Put) log transaction. One transaction
is written for each unique combination of item/lot that just
moved to the P&D location.
The system determines whether the equipment is empty.
If the Then the system…
equipment
is…
empty Proceeds to Execute Planned Move—
Find Next Work Item.
not empty Returns the user to the beginning of the
Execute Planned Move—Outsort
process.
• The user must verify they are at the location by entering or scanning the suggested location.
• The system suggests one of the license plates that needs to be put away in the destination
location. The user must enter or scan any license plate that needs to be put away in this location.
• The system validates that the license plate entered is on the equipment and has inventory
scheduled to go into the location.
• If the destination location is license plate-controlled, then the system prompts the user for the
destination license plate. The destination license plate can be:
− the same as the license plate used to move the inventory while it was on the equipment.
− a new license plate.
− a license plate already in the location as long as it is not on hold.

86 HighJump Warehouse Advantage Functional Description

 • The system moves the license plate contents to the destination location and completes the
following tasks.
Task Description
1 If the destination is not license plate-controlled then the license plate is destroyed. If the
destination is license plate-controlled then the destination license plate is created or
updated as appropriate.
2 The system generates the appropriate log transactions. One transaction is written for
each unique combination of item/lot that just moved to the destination.
• 252 = Directed Move
• 258 = Slot Move
• 306 = Replenishment
3 The system determines whether the destination location is a production location.
If the destination Then the system…
location…
is a production Removes the inventory put into the production location,
location creates host notification(s) of inventory adjustments, then
determines whether the work completed was a slot move.
is not a production Determines whether the work completed was a slot move.
location

4 The system determines whether the work completed was a slot move.
If the work… Then the system…
was a slot move • Updates the status of the slotting work queue that
corresponds to the work queue to Complete. The status
indicates to HighJump Slotting Advantage that the slot
move is complete and the item moved to its new location.
• If the destination location is a pick location, the system
inserts a Forward Pick record for the item and destination
location if one does not already exist for the item in the
location.
• Determines whether the equipment is empty.
was not a slot move Determines whether the equipment is empty.

5 The system determines whether the equipment is empty.

If the equipment Then the system…
is…
empty Proceeds to Execute Planned Move—Find Next Work Item.
not empty Returns the user to the beginning of the Execute Planned
Move—Outsort process.

HighJump Warehouse Advantage Functional Description 87

Allocation Process to Find a Pick Location

When the system creates an Execute Planned Move request, an allocation queue entry is created.
Pick Plan Allocation process runs the picking rules to determine the optimal pick location and pick
area for the item. In certain circumstances, such as no current inventory, the picking rules may not be
able to identify a pick location. If the Pick Plan process is not able to find an appropriate location for
the pick, no allocation record is created.

Troubleshooting

The HighJump Advantage Dashboard includes Unfulfillable Planned Moves web pages that can
assist you with troubleshooting when the system cannot complete an Execute Planned Move request.
For more information about the Unfulfillable Planned Moves web pages, see HighJump Advantage
Dashboard Functional Description.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates a pair of transaction log entries that correspond to
the type of planned move just executed. Pick transactions are generated for each unique item,
pick location and quantity picked from each license plate (if the location is license plate-
controlled) or lot (if the item is lot-controlled). A similar level of detail is logged for the (put)
transaction.
• The transaction pairs include the following:
− Directed Move generates a 251 Directed Move (Pick) transaction and a 252 Directed Move
(Put) transaction.
− Directed Move generates a 253 Directed Move (Production Pick) transaction and a 254
Directed Move (Production Put) transaction.
− Planned Move generates a 255 Planned Move (PD Pick) transaction and a 256 Planned
Move (PD Put) transaction.
− Execute Planned Move generates 305 Replenishment (Pick) transaction and 306
Replenishment (Put) transaction.
• Refer to the HighJump Warehouse Advantage Log Transactions specification for further details.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

88 HighJump Warehouse Advantage Functional Description

Execute Planned Move Pickup
The Execute Planned Move Pickup process manages the movement of product within the warehouse
based on a Planned Move Pickup request. The system creates a Planned Move Pickup request when
inventory is put in a P&D (Pickup and Delivery) location during the Execute Planned Move Outsort
process.

Based on the outstanding Planned Move Pickup requests, the process suggests a P&D location and
license plate (LP) to pick up. The user can override the suggested pick up location and license plate.

When the user's equipment has reached a user-determined capacity, or when there are no more
license plates in the P&D location with Planned Move Pickup requests, the system directs the user to
put away the license plates on their equipment using the Execute Planned Move Outsort process.

Process Details

The following process details apply.

• The system determines if there is at least one open Planned Move Pickup request in the work
queue. If no open Planned Move Pickup request is found, the system displays the "No work is
available" message.
• If at least one open Planned Move Pickup request is found, the system prompts the user to scan
the P&D location associated with the Planned Move Pickup request that they want to pick up. The
system suggests the P&D location with the highest priority and within the priority, the oldest
Planned Move Pickup request. If the user overrides the suggested location, the system
determines if there is at least one open Planned Move Pickup request in the work queue for that
location.
• The system prompts the user to scan the LP and verifies the LP is the one requested or that it
exists in the location with an open Planned Move Pickup request in the work queue.
• The system moves the specified LP to the user's equipment and closes the Planned Move Pickup
request.
• When the user's equipment has reached a user-determined capacity or when there are no
Planned Move Pickup requests, the user selects the F3: Done option. The F3: Done option
initiates the Execute Planned Move Outsort process.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates a 255 Planned Move (PD Pick) log transaction as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transaction
is generated for each item/lot combination on the license plate.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 89

Picking
Picking includes the following processes:
• Bulk Pick by Wave
• Bulk Pick by Load
• Order Picking
• Batch Picking by Order
• Batch Picking by Container
• Pick/Pass by Order
• Label Picking—Confirm by Label
• Label Picking—Confirm by Batch
• Warehouse Transfer Out
• Miscellaneous Issue
• Reprint Packing Slip

Note
For serial-controlled items, picking and staging using LPs is recommended.

Bulk Pick by Wave

The Bulk Pick by Wave process manages the fulfillment, or picking, of a logical grouping of order-
related items within the warehouse.

Based on the logical grouping ("wave") created within HighJump Advanced Fulfillment Application,
the process determines the optimal pick location associated to each item on the wave and then
directs the user to pick a specific aggregated item quantity from each location in parallel with moving
the product to the user's equipment. The aggregate pick quantity is automatically allocated to the
individual orders within the wave.

When the user's equipment has reached a user-determined capacity, or when there are no more
items to pick on the wave, the system directs the user to deliver the product to the destination location
associated with each order on the user's equipment.

Process Details

The following process details apply.

• The system determines if the employee is already assigned to a pick area. If the employee is not
assigned to a pick area, the system proceeds to Bulk Pick by Wave—Assign Pick Area.
• If the employee is assigned to a pick area, and there is only one defined pick area in the
warehouse, the system proceeds to Bulk Pick by Wave—Check Work Queue.
• A pick area is identified by scanning or entering a valid pick area. The system defaults to the pick
area assigned to the user. The system verifies the pick area corresponds to a valid pick area in
the warehouse. The system proceeds to Bulk Pick by Wave—Check Work Queue.

90 HighJump Warehouse Advantage Functional Description

 Bulk Pick by Wave—Assign Pick Area
• A pick area is identified by scanning or entering a valid pick area. The system verifies the pick
area corresponds to a valid pick area in the warehouse.
• The system updates the pick area in the employee table with the specified pick area. The system
proceeds to Bulk Pick by Wave—Check Work Queue.

Bulk Pick by Wave—Check Work Queue

• The system determines if there is a Bulk Pick by Wave work queue task meeting the following
criteria:
− The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• If no open Bulk Pick by Wave work queue is found, the system displays the "no work available"
message. The system proceeds to the Main Menu process.
• If there is more than one Bulk Pick by Wave work queue that meets the criteria, the system
defaults to the work queue based on priority, date due, time due, and wave identifier.
• The wave to be picked must be identified by accepting the suggested wave, or by entering a
wave corresponding to the following criteria:
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• The system assigns the user to the work queue associated with the identified wave and
increments the number of workers assigned on the work queue.

Bulk Pick by Wave—Display Order Comments

• For each distinct order associated to the pick detail task and associated to the wave, the system
determines if there are any order comments. If there are comments, the system displays the
comments. The user can page forwards or backwards through the comments. The comments are
displayed in order number, header/footer, and sequence order.

Bulk Pick by Wave—Display Metrics

• The system determines if the "display work metrics" system flag is enabled. If enabled, the
system displays the wave, number of distinct orders, number of remaining pick detail tasks, total
weight, and total cube associated with the remaining (open) pick detail tasks for the wave.

HighJump Warehouse Advantage Functional Description 91

 Bulk Pick by Wave—Scan Start Location
• A start location is identified by scanning or entering any valid location. The start location is
required.

Bulk Pick by Wave—Find Next Item to Pick

• The system attempts to find the next pick detail task meeting the following criteria:
− The pick detail task is associated to the identified wave.
− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
− The pick detail task's pick flow and location identifier is greater than or equal to the pick flow
and location identifier associated with the starting location.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

• If an item is found, the system proceeds to Bulk Pick by Wave—Select Item to Pick.
• If a pick detail task is not found for the starting location, the system attempts to find the next pick
detail task meeting the following criteria, ordered by the pick detail task's pick flow and location
identifier.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

− The pick detail task is associated to the identified wave.

− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• If an item is found, the system proceeds to Bulk Pick by Wave—Select Item to Pick.
• If a pick detail task is not found based on pick flow and location identifier, and there are items on
the user's equipment, the system proceeds to Bulk Pick by Wave—Update Pick Information
Before Out sorting.
• If a pick detail task is not found based on pick flow and location identifier, and there are no items
on the user's equipment, the system proceeds to Bulk Pick by Wave—Unassign.

Bulk Pick by Wave—Select Item to Pick

• The next item number to be picked must be identified by entering or scanning a valid item number
or a valid alternative item number or UPC number associated to an item and associated to the
selected wave and pick area. By default, the system suggests the next item to pick. The user can
press the enter key to accept the suggested item number to be picked, or select the F8: List
option to select an item from a list of available items. The list of available items contains distinct
items numbers meeting the following criteria:
− The pick detail task is associated to the identified wave.

92 HighJump Warehouse Advantage Functional Description

 − The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• The system attempts to assign the user to all of the pick detail records associated to the selected
item and wave. If the system cannot assign the user to all of the pick detail records associated to
the selected item and wave, the system proceeds to Bulk Pick by Wave—Find Next Item to Pick.

Bulk Pick by Wave—Display Order Detail Comments

• For each distinct order associated to the pick detail task and associated to the wave and item, the
system determines if there are any order detail comments. If there are comments, the system
displays the detail comments. The user can page forwards or backwards through the detail
comments. The detail comments are displayed in order number, line number, and sequence
order.

Bulk Pick by Wave—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Bulk Pick by Wave—Pick an Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Bulk Pick by Wave—Out Sorting.

Bulk Pick by Wave—Pick an Item

• If picking loose items, the system proceeds to Bulk Pick by Wave—Picking Loose Items. If picking
from an LP, the system proceeds to Bulk Pick by Wave—Picking LP-based Items.

Bulk Pick by Wave—Picking Loose Items

• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Wave—Find Next Item to Pick.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the wave, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the allocated quantity of the item.

HighJump Warehouse Advantage Functional Description 93

 • The item/lot number quantity to be picked from the suggested location is entered in the displayed
unit of measure. By default, the displayed unit of measure is (a) the largest defined unit of
measure for the item (if multiple units of measure are available for the item) relative to the
quantity to be picked of the identified item/lot number, or (b) the standard unit of measure of the
item (if multiple units of measure are not available for the item). If multiple units of measure are
available for the item, the user can select a unit of measure by either (a) pressing a function key
to display the next smallest unit of measure or (b) selecting a unit of measure from the available
list of units of measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location,
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location. (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Wave—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system moves the specified item quantity from the source location to the user's equipment.
• The system increments the quantity picked on the pick detail request(s) associated to the wave
and item. If more than one pick detail exists for the wave, the amount picked is allocated based
on order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• The system generates a pick transaction for each item/lot number quantity allocated to each pick
detail.
• The system proceeds to Bulk Pick by Wave—Replenishment Check.

94 HighJump Warehouse Advantage Functional Description

 Bulk Pick by Wave—Picking LP-based Items
• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated to the allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Wave—Find Next Item to Pick.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the wave, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.

HighJump Warehouse Advantage Functional Description 95

 • If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Wave—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system increments the quantity picked on the pick detail request(s) associated to the wave
and item. If more than one pick detail exists for the wave, the amount picked is allocated based
on order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• If the specified item quantity is less than the total sum quantity associated to the LP, the system
decrements the item/lot number quantity from the source LP and leaves the LP remaining in the
source location.
• If the specified item quantity equals the total sum quantity associated to the LP, the item/lot
number quantity associated to the LP is converted to order/item/lot number -specific quantities. If
the quantity is allocated to more than one unique order, the source LP is (logically) deleted from
the system. If the quantity is allocated to a single order, the LP is moved to the user's equipment.
• A pick transaction is generated for each item/lot number quantity allocated to each pick detail.

Bulk Pick by Wave—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• The system proceeds to Bulk Pick by Wave—Find Next Item to Pick.

Bulk Pick by Wave —Handle Quantity Exceptions

• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.

Bulk Pick by Wave—Update Pick Information Before Out Sorting

• The system updates the pick detail status to "PICKED” for each pick detail currently associated to
the wave, and where the picked quantity is greater than or equal to the planned quantity and the
staged quantity is less than or equal to the picked quantity (i.e., the entire planned amount is
picked, but not entirely staged).
• If all of the lines on the pick detail for the order have been picked as planned and there are no
remaining picks to be fulfilled, the system closes the work queue.

96 HighJump Warehouse Advantage Functional Description

 Bulk Pick by Wave—Out Sorting
• The system unassigns the user from the current work queue and the assigned pick details.
• The out sorting process manages the delivery of LP-based inventory residing on the user's
equipment first. If there are no LPs on the user's equipment, the system proceeds to Bulk Pick by
Wave—Out Sorting Determine Order by Items.
• If there are no remaining open pick details associated to the order, the system proceeds to Bulk
Picking by Wave—Unassign.

Bulk Pick by Wave—Out Sorting Determine Order by LP

• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.

Bulk Pick by Wave—Out Sorting Determine Order by Item

• The system determines the number of orders on the LP or equipment. If there is more than one
order on the LP or equipment, the preferred item to be put away is scanned and used to
determine the order. If there is only one order on the LP or equipment, the user is not prompted to
scan the item number and the system determines the order number allocated to the contents of
the LP or equipment.

Bulk Pick by Wave—Out Sorting of Items

• The system determines the next item/lot number quantity residing on the user's equipment, based
on order number/item number/lot number sequence.
• For the LP/order number/item number/lot number quantity:
− The system determines the order number allocated to the item/lot number.
− The system retrieves the staging location defined for the pick detail record(s) associated to
the order and wave.
− If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
− If a staging location is assigned, the system directs the user to the location associated to the
order and wave. The location must be identified by either entering or scanning the suggested
location or any valid staging or door location.
− The system updates the pick detail staging location with the specified location for each pick
detail currently associated to the order and wave.
− The system displays the LP and order number, instructing the user to "move to" the
associated staging or door location and the user is prompted to verify the LP.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the item.
− If there is more than one lot number for the item the system displays the order number, item,
lot number (if applicable), and quantity to be moved to the associated staging or door location
and the user is prompted to verify the lot number.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the quantity.

HighJump Warehouse Advantage Functional Description 97

 − The user is prompted for serial numbers when the item is configured for full, outbound trace,
or trace in/out serial control and the quantity of inventory does not represent the entire
quantum of inventory (for example, a partial quantity of an item/lot number taken from an LP).
When prompted, the user scans each serial number in an “X of Y” method. The system
validates that each serial number belongs to that quantum of inventory.
• The serial numbers on the equipment are allocated to a specific order. If the equipment
has the same inventory quantum for two different orders, the user may scan any serial
number for that quantum, even if the scanned serial number is not associated to the
order that is being put away. When this happens, the system will transfer the scanned
serial number to the order displayed on screen. After an associated serial number is
staged, it cannot be transferred to another order.
− The user is prompted to enter a destination LP.
• If the inventory is on an LP and there is only one order associated to the LP, the user can
hit the F4: Put LP function button and proceed to Bulk Pick by Wave—Out Sorting Put
LP.
• If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
• If moving the specified item quantity as loose items within the location, the user should
not specify an LP.
− The system increments the quantity staged and quantity loaded (if the deliver to location is a
door location) on the pick detail request(s) associated to the wave and item. If more than one
pick detail exists for the wave, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− The system generates a staging transaction for each item/lot number quantity allocated to
each pick detail's staged quantity.
− The system generates a loading transaction for each item/lot number quantity allocated to
each pick detail's loaded quantity.
• The system proceeds to Bulk Pick by Wave—Out Sorting Loose Items.

Bulk Pick by Wave—Out Sorting Put LP

• For each item/lot number quantity associated to the LP, the system does the following:
− The system increments the quantity staged and quantity loaded (if the deliver to location is a
door location) on the pick detail request(s) associated to the wave and item. If more than one
pick detail exists for the wave, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− Generates a staging transaction for each item/lot number quantity allocated to each pick
detail's staged quantity.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system moves the LP from the user's equipment into the staging/door location.

98 HighJump Warehouse Advantage Functional Description

 • The system proceeds to Bulk Pick by Wave—Update Pick Information After Out Sorting.

Bulk Pick by Wave—Update Pick Information After Out Sorting

• The system updates the pick detail status to "STAGED” for each pick detail currently associated
to the wave, and where the picked quantity is greater than or equal to the planned quantity and
the picked quantity is equal to the staged quantity (i.e., the entire planned amount is picked and
staged).
• The system updates the pick detail status to "LOADED” for each pick detail currently associated
to the wave, and where the picked quantity is greater than or equal to the planned quantity and
the picked quantity is equal to the staged quantity and the staged quantity is equal to the loaded
quantity (i.e., the entire picked amount is staged and loaded).

Bulk Pick by Wave—Unassign

• The system decrements the number of workers assigned on the work queue.
• If the number of workers assigned is zero and at least one of the pick details associated to the
work queue has a status of "RELEASED", the system updates the work queue status to
unassigned ("U").
• If the number of workers assigned is zero and all of the pick details associated to the work queue
have a status of "PICKED", the system updates the work queue status to complete ("C").
• The system unassigns the user from the work queue.
• The system proceeds to Bulk Pick by Wave—Find Work Queue.

Interface Requirements

The following interface requirements apply.

• The host system provides valid outbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 301 Picking (pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's picked quantity.
• HighJump Warehouse Advantage generates 302 Picking (put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's staged quantity.
• HighJump Warehouse Advantage generates 322 Picking (put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's loaded quantity.
• HighJump Warehouse Advantage generates 855 Serial Number Transfer transactions when the
item is configured for full, outbound trace, or trace in/out serial control as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for both the source and destination order.

HighJump Warehouse Advantage Functional Description 99

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

100 HighJump Warehouse Advantage Functional Description

Bulk Pick by Load
The Bulk Pick by Load process manages the fulfillment, or picking, of a physical grouping of order-
related items within the warehouse.

Based on the physical grouping ("load") created within HighJump Advanced Fulfillment Application,
the process determines the optimal pick location associated to each item on the load and then directs
the user to pick a specific aggregated item quantity from each location in parallel with moving the
product to the user's equipment. The aggregate pick quantity is automatically allocated to the
individual orders within the load.

When the user's equipment has reached a user-determined capacity, or when there are no more
items to pick on the load, the system directs the user to deliver the product to the destination location
associated with each order on the user's equipment.

Process Details

The following process details apply.

• The system determines if the employee is already assigned to a pick area. If the employee is not
assigned to a pick area, the system proceeds to Bulk Pick by Load—Assign Pick Area.
• If the employee is assigned to a pick area, and there is only one defined pick area in the
warehouse, the system proceeds to Bulk Pick by Load—Check Work Queue.
• A pick area is identified by scanning or entering a valid pick area. The system defaults to the pick
area assigned to the user. The system verifies the pick area corresponds to a valid pick area in
the warehouse. The system proceeds to Bulk Pick by Load—Check Work Queue.

Bulk Pick by Load—Assign Pick Area

• A pick area is identified by scanning or entering a valid pick area. The system verifies the pick
area corresponds to a valid pick area in the warehouse.
• The system updates the pick area in the employee table with the specified pick area. The system
proceeds to Bulk Pick by Load—Check Work Queue.

Bulk Pick by Load—Check Work Queue

• The system determines if there is a Bulk Pick by Load work queue task meeting the following
criteria:
− The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.

HighJump Warehouse Advantage Functional Description 101

 • If no open Bulk Pick by Load work queue is found, the system displays the "no work available"
message. The system proceeds to the Main Menu process.
• If there is more than one Bulk Pick by Load work queue that meets the criteria, the system
defaults to the work queue based on priority, date due, time due, and load identifier.
• The load to be picked must be identified by accepting the suggested load, or by entering a load
corresponding to the following criteria:
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• The system assigns the user to the work queue associated with the identified load and
increments the number of workers assigned on the work queue.

Bulk Pick by Load—Display Order Comments

For each distinct order associated to the pick detail task and associated to the load, the system
determines if there are any order comments. If there are comments, the system displays the
comments. The user can page forwards or backwards through the header comments. The comments
are displayed in order number, header/footer, and sequence order.

Bulk Pick by Load—Display Metrics

The system determines if the "display work metrics" system flag is enabled. If enabled, the system
displays the load, number of distinct orders, number of remaining pick detail tasks, total weight, and
total cube associated with the remaining (open) pick detail tasks for the load.

Bulk Pick by Load—Find Next Item to Pick

• The system attempts to find the next pick detail task meeting the following criteria, ordered by the
pick detail task's pick flow and location identifier.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

− The pick detail task is associated to the identified load.

− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• If an item is found, the system proceeds to Bulk Pick by Load—Select Item to Pick.
• If a pick detail task is not found based on pick flow and location identifier, and there are items on
the user's equipment, the system proceeds to Bulk Pick by Load—Out sorting.
• If a pick detail task is not found based on pick flow and location identifier, and there are no items
on the user's equipment, the system proceeds to Bulk Pick by Load—Update Pick Information
Before Out sorting.

102 HighJump Warehouse Advantage Functional Description

 Bulk Pick by Load—Select Item to Pick
• The next item number to be picked must be identified by entering or scanning a valid item number
or a valid alternative item number or UPC number associated to an item and associated to the
selected load and pick area. By default, the system suggests the next item to pick. The user can
press the enter key to accept the suggested item number to be picked, or select the F8: LST
option to select an item from a list of available items. The list of available items contains distinct
items numbers meeting the following criteria:
− The pick detail task is associated to the identified load.
− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• The system attempts to assign the user to all of the pick detail records associated to the selected
item and load. If the system cannot assign the user to all of the pick detail records associated to
the selected item and load, the system proceeds to Bulk Pick by Load—Find Next Item to Pick.

Bulk Pick by Load—Display Order Detail Comments

• For each distinct order associated to the pick detail task and associated to the load and item, the
system determines if there are any order detail comments. If there are comments, the system
displays the detail comments. The user can page forwards or backwards through the detail
comments. The detail comments are displayed in order number, line number, and sequence
order.

Bulk Pick by Load—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Bulk Pick by Load—Pick an Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Bulk Pick by Load—Out sorting.

Bulk Pick by Load—Pick an Item

• If picking loose items, the system proceeds to Bulk Pick by Load—Picking Loose Items. If picking
from an LP, the system proceeds to Bulk Pick by Load—Picking LP-based Items.

Bulk Pick by Load—Picking Loose Items

• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Load—Find Next Item to Pick.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.

HighJump Warehouse Advantage Functional Description 103

 • The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the load, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the suggested location is entered in the displayed
unit of measure. By default, the displayed unit of measure is (a) the largest defined unit of
measure for the item (if multiple units of measure are available for the item) relative to the
quantity to be picked of the identified item/lot number, or (b) the standard unit of measure of the
item (if multiple units of measure are not available for the item). If multiple units of measure are
available for the item, the user can select a unit of measure by either (a) pressing a function key
to display the next smallest unit of measure or (b) selecting a unit of measure from the available
list of units of measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Load—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system moves the specified item quantity from the source location to the user's equipment.
• The system increments the quantity picked on the pick detail request(s) associated to the load
and item. If more than one pick detail exists for the load, the amount picked is allocated based on
order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• The system generates a pick transaction for each item/lot number quantity allocated to each pick
detail.
• The system proceeds to Batch Pick by Load—Replenishment Check.

104 HighJump Warehouse Advantage Functional Description

 Bulk Pick by Load—Picking LP-based Items
• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated to the allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Load—Find Next Item to Pick.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the load, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.

HighJump Warehouse Advantage Functional Description 105

 − If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Bulk Pick by Load—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system increments the quantity picked on the pick detail request(s) associated to the load
and item. If more than one pick detail exists for the load, the amount picked is allocated based on
order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• If the specified item quantity is less than the total sum quantity associated to the LP, the system
decrements the item/lot number quantity from the source LP and leaves the LP remaining in the
source location.
• If the specified item quantity equals the total sum quantity associated to the LP, the item/lot
number quantity associated to the LP is converted to order/item/lot number -specific quantities. If
the quantity is allocated to more than one unique order, the source LP is (logically) deleted from
the system. If the quantity is allocated to a single order, the LP is moved to the user's equipment.
• The system generates a pick transaction for each item/lot quantity allocated to each pick detail.

Bulk Pick by Load—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• The system proceeds to Bulk Pick by Load—Find Next Item to Pick.

Bulk Pick by Load—Handle Quantity Exceptions

• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.

Bulk Pick by Load—Update Pick Information Before Out sorting

• The system updates the pick detail status to "PICKED” for each pick detail currently associated to
the load, and where the picked quantity is greater than or equal to the planned quantity and the
staged quantity is less than or equal to the picked quantity (i.e., the entire planned amount is
picked, but not entirely staged).
• If all of the lines on the pick detail for the order have been picked as planned and there are no
remaining picks to be fulfilled, the system closes the work queue.

Bulk Pick by Load—Out sorting

• The system unassigns the user from the current work queue and the assigned pick details.

106 HighJump Warehouse Advantage Functional Description

 • The out sorting process manages the delivery of LP-based inventory residing on the user's
equipment first. If there are no LPs on the user's equipment, the system proceeds to Bulk Pick by
Load—Out sorting Determine Order by Items.
• If there are no remaining open pick details associated to the order, the system proceeds to Bulk
Picking by Load—Unassign.

Bulk Pick by Load—Out sorting Determine Order by LP

• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.

Bulk Pick by Load—Out sorting Determine Order by Item

• The system determines the number of orders on the LP or equipment. If there is more than one
order on the LP or equipment, the preferred item to be put away is scanned and used to
determine the order. If there is only one order on the LP or equipment, the user is not prompted to
scan the item number and the system determines the order number allocated to the contents of
the LP or equipment.

Bulk Pick by Load—Out sorting of Items

• The system determines the next item/lot number quantity residing on the user's equipment, based
on order number/item number/lot sequence.
• For the LP/order/number/item number/lot number quantity:
− The system determines the order number allocated to the item/lot number.
− The system retrieves the staging location defined for the pick detail record(s) associated to
the order and Load.
− If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
− If a staging location is assigned, the system directs the user to the location associated to the
order and Load. The location must be identified by either entering or scanning the suggested
location or any valid staging or door location.
− The system updates the pick detail staging location with the specified location for each pick
detail currently associated to the order and Load.
− The system displays the LP and order number, instructing the user to "move to" the
associated staging or door location and the user is prompted to verify the LP.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the item.
− If there is more than one Lot for this item the system displays the order number, item, lot
number (if applicable), and quantity to be moved to the associated staging or door location
and the user is prompted to verify the lot.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the quantity.
− The user is prompted for serial numbers when the item is configured for full, outbound trace,
or trace in/out serial control and the quantity of inventory does not represent the entire

HighJump Warehouse Advantage Functional Description 107

 quantum of inventory (for example, a partial quantity of an item/lot number taken from an LP).
When prompted, the user scans each serial number in an “X of Y” method. The system
validates that each serial number belongs to that quantum of inventory.
• The serial numbers on the equipment are allocated to a specific order. If the equipment
has the same inventory quantum for two different orders, the user may scan any serial
number for that quantum, even if the scanned serial number is not associated to the
order that is being put away. When this happens, the system will transfer the scanned
serial number to the order displayed on screen. After an associated serial number is
staged, it cannot be transferred to another order.
− The user is prompted to enter a destination LP.
• If the inventory is on an LP and there is only one order associated to the LP, the user can hit the
F4: Put LP function button and proceed to Bulk Pick by Load—Out sorting Put LP.
• If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
• If moving the specified item quantity as loose items within the location, the user should
not specify an LP.
− The system increments the quantity staged and quantity loaded (if the deliver to location is a
door location) on the pick detail request(s) associated to the Load and item. If more than one
pick detail exists for the Load, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− The system generates a staging transaction for each item/lot number quantity allocated to
each pick detail's staged quantity.
− The system generates a loading transaction for each item/lot number quantity allocated to
each pick detail's loaded quantity.
• The system proceeds to Bulk Pick by Load—Out sorting Loose Items.

Bulk Pick by Load—Out sorting Put LP

• For each item/lot number quantity associated to the LP, the system does the following:
− The system increments the quantity staged and quantity loaded (if the deliver to location is a
door location) on the pick detail request(s) associated to the Load and item. If more than one
pick detail exists for the Load, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− Generates a staging transaction for each item/lot number quantity allocated to each pick
detail's staged quantity.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system moves the LP from the user's equipment into the staging/door location.
• The system proceeds to Bulk Pick by Load—Update Pick Information After Out sorting.

108 HighJump Warehouse Advantage Functional Description

 Bulk Pick by Load—Update Pick Information After Out sorting
• The system updates the pick detail status to "STAGED” for each pick detail currently associated
to the Load, and where the picked quantity is greater than or equal to the planned quantity and
the picked quantity is equal to the staged quantity (i.e., the entire planned amount is picked and
staged).
• The system updates the pick detail status to "LOADED” for each pick detail currently associated
to the Load, and where the picked quantity is greater than or equal to the planned quantity and
the picked quantity is equal to the staged quantity and the staged quantity is equal to the loaded
quantity (i.e., the entire picked amount is staged and loaded).

Bulk Pick by Load—Unassign

• The system decrements the number of workers assigned on the work queue.
• If the number of workers assigned is zero and at least one of the pick details associated to the
work queue has a status of RELEASED, the system updates the work queue status to
unassigned (U).
• If the number of workers assigned is zero and all of the pick details associated to the work queue
have a status of PICKED, the system updates the work queue status to complete (C).
• The system unassigns the user from the work queue.
• The system proceeds to Bulk Pick by Load—Find Work Queue.

Interface Requirements

The following interface requirements apply.

• The host system provides valid outbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 301 Picking (Pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's picked quantity.
• HighJump Warehouse Advantage generates 302 Picking (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's staged quantity.
• HighJump Warehouse Advantage generates 322 Loading (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's loaded quantity.
• HighJump Warehouse Advantage generates 855 Serial Number Transfer transactions when the
item is configured for full, outbound trace, or trace in/out serial control as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for both the source and destination order.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 109

Order Picking
The Order Picking process manages the fulfillment, or picking, of single order-related items within the
warehouse.

Based on a specific order identifier, the process determines the optimal pick location associated to
each item on the order and then directs the user to pick a specific aggregated item quantity from each
location in parallel with moving the product to the user's equipment. The aggregate pick quantity is
automatically allocated to the individual order's lines within the order.

When the user's equipment has reached a user-determined capacity, or when there are no more
items to pick on the order, the system directs the user to deliver the product to the destination location
associated with the order on the user's equipment.

Process Details

The following process details apply.

• The system determines if the employee is already assigned to a pick area. If the employee is not
assigned to a pick area, the system proceeds to Order Picking—Assign Pick Area.
• If the employee is assigned to a pick area, and there is only one defined pick area in the
warehouse, the system proceeds to Order Picking—Check Work Queue.
• A pick area is identified by scanning or entering a valid pick area. The system defaults to the pick
area assigned to the user. The system verifies the pick area corresponds to a valid pick area in
the warehouse. The system proceeds to Order Picking—Check Work Queue.

Order Picking—Assign Pick Area

• A pick area is identified by scanning or entering a valid pick area. The system verifies the pick
area corresponds to a valid pick area in the warehouse.
• The system updates the pick area in the employee table with the specified pick area. The system
proceeds to Order Picking—Check Work Queue.

Order Picking—Check Work Queue

• The system determines if there is an Order Picking work queue task meeting the following
criteria:
− The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• If no open Order Picking work queue is found, the system displays the "no work available"
message. The system proceeds to the Main Menu process.

110 HighJump Warehouse Advantage Functional Description

 • If there is more than one Order Picking work queue which meets the criteria, the system defaults
to the work queue based on priority, date due, time due, and order number.
• The order to be picked must be identified by accepting the suggested order, or by entering an
order number corresponding to the following criteria:
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• The system assigns the user to the work queue associated with the identified order and
increments the number of workers assigned on the work queue.

Order Picking—Display Order Comments

For the specified order, the system determines if there are any order comments. If there are
comments, the system displays the comments. The user can page forwards or backwards through
the comments. The comments are displayed in order number, header/footer, and sequence order.

Order Picking—Display Metrics

The system determines if the "display work metrics" system flag is enabled. If enabled, the system
displays the order number, number of distinct orders (1), number of remaining pick detail tasks, total
weight, and total cube associated with the remaining (open) pick detail tasks for the order.

Order Picking—Find Next Item to Pick

• The system attempts to find the next pick detail task meeting the following criteria, ordered by the
pick detail task's pick flow and location identifier.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

− The pick detail task is associated to the identified order.

− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• If an item is found, the system proceeds to Order Picking—Select Item to Pick.
• If a pick detail task is not found based on pick flow and location identifier, and there are items on
the user's equipment, the system proceeds to Order Picking—Out sorting.
• If a pick detail task is not found based on pick flow and location identifier, and there are no items
on the user's equipment, the system proceeds to Order Picking—Update Pick Information Before
Out sorting.

HighJump Warehouse Advantage Functional Description 111

 Order Picking—Select Item to Pick
• The next item number to be picked must be identified by entering or scanning a valid item number
or a valid alternative item number or UPC number associated to an item and associated to the
selected order and pick area. By default, the system suggests the next item to pick. The user can
press the enter key to accept the suggested item number to be picked, or select the F8: LST
option to select an item from a list of available items. The list of available items contains distinct
item numbers meeting the following criteria:
− The pick detail task is associated to the identified order.
− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• The system attempts to assign the user to all of the pick detail records associated to the selected
item and order. If the system cannot assign the user to all of the pick detail records associated to
the selected item and order, the system proceeds to Order Picking—Find Next Item to Pick.

Order Picking—Display Order Detail Comments

• For each distinct order associated to the pick detail task and associated to the order and item, the
system determines if there are any order detail comments. If there are comments, the system
displays the detail comments. The user can page forwards or backwards through the detail
comments. The detail comments are displayed in order number, line number, and sequence
order.

Order Picking—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Order Picking—Pick an Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Order Picking—Update Pick Information Before Out sorting.

Order Picking—Pick an Item

• If picking loose items, the system proceeds to Order Picking—Picking Loose Items. If picking
from an LP, the system proceeds to Order Picking—Picking LP-based Items.

Order Picking—Picking Loose Items

• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Order Picking—Find Next Item to Pick.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.

112 HighJump Warehouse Advantage Functional Description

 • The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the suggested location is entered in the displayed
unit of measure. By default, the displayed unit of measure is (a) the largest defined unit of
measure for the item (if multiple units of measure are available for the item) relative to the
quantity to be picked of the identified item/lot number, or (b) the standard unit of measure of the
item (if multiple units of measure are not available for the item). If multiple units of measure are
available for the item, the user can select a unit of measure by either (a) pressing a function key
to display the next smallest unit of measure or (b) selecting a unit of measure from the available
list of units of measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Order Picking—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system moves the specified item quantity from the source location to the user's equipment.
• The system increments the quantity picked on the pick detail request(s) associated to the order
and item. If more than one pick detail exists for the order, the amount picked is allocated based
on order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• A pick transaction is generated for each item/lot number quantity allocated to each pick detail.

HighJump Warehouse Advantage Functional Description 113

 Order Picking—Picking LP-based Items
• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated to allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Order Picking—Find Next Item to Pick.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number associated to the LP.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.

114 HighJump Warehouse Advantage Functional Description

 • If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", and (b) generates a Cycle Count by Location work queue request for the
suggested location, (c) removes associated allocation records, and (d) inserts record for item
into the allocation queue. The system proceeds to Order Picking—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system increments the quantity picked on the pick detail request(s) associated to the order
and item. If more than one pick detail exists for the order, the amount picked is allocated based
on order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• If the specified item quantity is less than the total sum quantity associated to the LP, the system
decrements the item/lot number quantity from the source LP and leaves the LP remaining in the
source location.
• If the specified item quantity equals the total sum quantity associated to the LP, the item/lot
number quantity associated to the LP is converted to order/item/lot number -specific quantities. If
the quantity is allocated to more than one unique order, the source LP is (logically) deleted from
the system. If the quantity is allocated to a single order, the LP is moved to the user's equipment.
• A pick transaction is generated for each item/lot number quantity allocated to each pick detail.

Order Picking—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• The system proceeds to Order Picking—Find Next Item to Pick.

Order Picking—Handle Quantity Exceptions

• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.

Order Picking—Update Pick Information Before Out sorting

• The system updates the pick detail status to "PICKED" for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
staged quantity is less than or equal to the picked quantity (the entire planned amount is picked,
but not entirely staged).
• If all of the lines on the pick detail for the order have been picked as planned and there are no
remaining picks to be fulfilled, the system closes the work queue.

HighJump Warehouse Advantage Functional Description 115

 Order Picking—Out sorting
• The system un-assigns the user from the current work queue and the assigned pick details.
• The out sorting process manages the delivery of LP-based inventory residing on the user's
equipment first. If there are no LPs on the user's equipment, the system proceeds to Order
Picking—Out sorting Loose Items.
• If there are no remaining open pick details associated to the order, the system proceeds to Order
Picking—Unassign.

Order Picking—Out sorting by LP

• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.
• The system determines the order number allocated to the contents of the LP.
• The system retrieves the staging location defined for the pick detail record(s) associated to the
order.
• If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
• If a staging location is assigned, the system directs the user to the location associated to the
order. The location must be identified by either entering or scanning the suggested location or
any valid staging or door location.
• The system updates the pick detail staging location with the specified location for each pick detail
currently associated to the order.
• The system displays the LP and order number, instructing the user to "move to" the associated
staging or door location and the user is prompted to scan the LP.
• The user is prompted to enter a destination LP.
− The user can hit the F4: Put LP function button and proceed to Order Picking—Out sorting
Put LP.
− If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
− If moving the specified item quantity as loose items within the location, the user should not
specify an LP.

Order Picking—Out sorting Put LP

• For each item/lot number quantity associated to the LP, the system does the following:
− Increments the quantity staged and quantity loaded (if the deliver to location is a door
location) on the pick detail request(s) associated to the order and item. If more than one pick
detail exists for the order, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.

116 HighJump Warehouse Advantage Functional Description

 − Generates a staging transaction for each item/lot number quantity allocated to each pick
detail's staged quantity.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system moves the LP from the user's equipment into the staging/door location.
• The system proceeds to Order Picking—Update Pick Information After Out sorting.

Order Picking—Out Sorting Loose Items

• The system determines the next item/lot number quantity residing on the user's equipment, based
on order number/item number/lot sequence.
• For the order/number/item number/lot number quantity:
− The system determines the order number allocated to the item/lot number.
− The system retrieves the staging location defined for the pick detail record(s) associated to
the order.
− If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
− If a staging location is assigned, the system directs the user to the location associated to the
order. The location must be identified by either entering or scanning the suggested location or
any valid staging or door location.
− The system updates the pick detail staging location with the specified location for each pick
detail currently associated to the order.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the item.
− If there is more than one Lot for this item the system displays the order number, item, lot
number (if applicable), and quantity to be moved to the associated staging or door location
and the user is prompted to verify the lot.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the quantity.
− The user is prompted for serial numbers when the item is configured for full, outbound trace,
or trace in/out serial control and the quantity of inventory does not represent the entire
quantum of inventory (for example, a partial quantity of an item/lot number taken from an LP).
When prompted, the user scans each serial number in an “X of Y” method. The system
validates that each serial number belongs to that quantum of inventory.
− The user is prompted to enter a destination LP.
• If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
• If moving the specified item quantity as loose items within the location, the user should
not specify an LP.
− The system increments the quantity staged and quantity loaded (if the deliver to location is a
door location) on the pick detail request(s) associated to the order and item. If more than one
pick detail exists for the order, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.

HighJump Warehouse Advantage Functional Description 117

 − If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− A staging transaction is generated for each item/lot number quantity allocated to each pick
detail's staged quantity.
− A loading transaction is generated for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system proceeds to Order Picking—Out Sorting Loose Items.

Order Picking—Update Pick Information After Out Sorting

• The system updates the pick detail status to STAGED for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
picked quantity is equal to the staged quantity (that is, the entire planned amount is picked and
staged).
• The system updates the pick detail status to LOADED for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
picked quantity is equal to the staged quantity and the staged quantity is equal to the loaded
quantity (the entire picked amount is staged and loaded).

Order Picking—Unassign
• The system decrements the number of workers assigned on the work queue.
• If the number of workers assigned is zero and all of the pick details associated to the work queue
have a status of PICKED, the system updates the work queue status to completed (C).
• If the number of workers assigned is zero and all of the pick details associated to the work queue
do not have a status of PICKED, the system un-assigns the user from the work queue (U) and
removes all of the work queue assignments for the work queue.
• The system proceeds to Order Picking—Find Work Queue.

Interface Requirements

The following interface requirements apply.

• The host system provides valid outbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 301 Picking (Pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's picked quantity.
• HighJump Warehouse Advantage generates 302 Picking (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's staged quantity.
• HighJump Warehouse Advantage generates 322 Loading (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's loaded quantity.

118 HighJump Warehouse Advantage Functional Description

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create the packing slip for the order.

Configuration Requirements

There are no configuration requirements.

Batch Picking by Order

The Batch Picking by Order process manages the fulfillment of one or many (a "batch") cartonization
groupings (a "container") of order-related items within the warehouse.

Based on priority/date due/time due/order number, the system suggests the next available grouping
to the user. For each grouping, the system directs the user to select the associated container type (for
example, box, tote, or envelope) and to associate an LP to the container in parallel with physically
labeling the container and placing the container on their equipment.

When the user's equipment has reached a user-determined capacity, or when there are no groupings
available, the user begins their pick tour. The process determines the optimal pick location for each
item associated to the assigned groupings, and then directs the user to pick a specific aggregated
item quantity from each location. For each quantity picked, the system directs the user to move
container-specific item quantities into each container.

When all of the items associated to the groupings have been picked, the system directs the user to
deliver the containers to the destination location associated with each order on the user's equipment.

Process Details

The following process details apply.

• The system determines if the employee is already assigned to a pick area. If the employee is not
assigned to a pick area, the system proceeds to Batch Picking by Order—Assign Pick Area.
• If the employee is assigned to a pick area, and there is only one defined pick area in the
warehouse, the system proceeds to Batch Picking by Order—Check Work Queue.
• A pick area is identified by scanning or entering a valid pick area. The system defaults to the pick
area assigned to the user. The system verifies the pick area corresponds to a valid pick area in
the warehouse. The system proceeds to Batch Picking by Order—Check Work Queue.

Batch Picking by Order—Assign Pick Area

• A pick area is identified by scanning or entering a valid pick area. The system verifies the pick
area corresponds to a valid pick area in the warehouse.
• The system updates the pick area in the employee table with the specified pick area. The system
proceeds to Batch Picking by Order—Check Work Queue.

Batch Picking by Order—Check Work Queue

• The system determines if there is a Batch Picking by Order/Container work queue task meeting
the following criteria:

HighJump Warehouse Advantage Functional Description 119

 − The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• If no open Batch Picking by Order/Container work queue is found and no containers are assigned
to the user, the system displays the "no work available" message. The system proceeds to the
Main Menu process.
• If no open Batch Picking by Order/Container work queue is found and at least one container is
assigned to the user, the system proceeds to Batch Picking by Order—Display Order Comments.
• If there is more than one Batch Picking by Order/Container work queue that meets the criteria,
the system defaults to the work queue based on priority, date due, and time due.
• If there is at least one container assigned to the user, the user can select the F3: Done option
when they have been assigned the preferred number of containers (based on physical limitations
or user-preference). The system proceeds to Batch Picking by Order—Display Order Comments.
• The order to be picked must be identified by accepting the suggested order, or by entering an
order corresponding to the following criteria:
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• The system assigns the user to the work queue associated with the identified order and
increments the number of workers assigned on the work queue.

Batch Picking by Order—Assign Container

• The system determines the container type associated with the Batch Picking by Order/Container
work queue.
• The system instructs the user to select the container type associated to the Batch Picking by
Order/Container work queue.
• The container type is not entered, and therefore cannot be overridden.
• The user is prompted to scan an LP to associate to the container. The system verifies the LP
corresponds to a unique identifier.
• The system assigns the identified LP to the container.

120 HighJump Warehouse Advantage Functional Description

 • The system determines if there is another Batch Picking by Order/Container work queue task
associated to the order and meeting the following criteria:
− The work queue is open (i.e., there is at least one open pick detail task associated to the
work queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• If no open Batch Picking by Order/Container work queue is found for the order, the system
proceeds to Batch Picking by Order—Check Work Queue.
• The system assigns the user to the work queue associated with the identified order and
increments the number of workers assigned on the work queue. The system proceeds to Batch
Picking by Order—Assign Container.

Batch Picking by Order—Display Order Comments

• For each distinct order associated to the assigned batch of containers, the system determines if
there are any order comments. If there are comments, the system displays the comments. The
user can page forwards or backwards through the comments. The comments are displayed in
order number, header/footer, and sequence order.

Batch Picking by Order—Display Metrics

• The system determines if the "display work metrics" system flag is enabled. If enabled, the
system displays the number of distinct orders, number of remaining pick detail tasks, total weight,
and total cube associated with the remaining (open) pick detail tasks for the assigned batch of
containers.

Batch Picking by Order—Find Next Item to Pick

• The system attempts to find the next pick detail task meeting the following criteria, ordered by the
pick detail task's pick flow and location identifier.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

− The pick detail task is associated to the assigned batch of containers.

− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• If an item is found, the system proceeds to Batch Picking by Order—Select Item to Pick.
• If a pick detail task is not found based on pick flow and location identifier, and there are items on
the user's equipment, the system proceeds to Batch Picking by Order—Out Sorting.

HighJump Warehouse Advantage Functional Description 121

 • If a pick detail task is not found based on pick flow and location identifier, and there are no items
on the user's equipment, the system proceeds to Batch Picking by Order—Update Pick
Information Before Out sorting.

Batch Picking by Order—Select Item to Pick

• The next item number to be picked must be identified by entering or scanning a valid item number
or a valid alternative item number or UPC number associated to an item and associated to the
selected assigned batch of containers and pick area. By default, the system suggests the next
item to pick. The user can press the enter key to accept the suggested item number to be picked,
or select the F8 LST option to select an item from a list of available items. The list of available
items contains distinct item numbers meeting the following criteria:
− The pick detail task is associated to the assigned batch of containers.
− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• The system attempts to assign the user to all of the pick detail records associated to the selected
item and assigned batch of containers. If the system cannot assign the user to all of the pick
detail records associated to the selected item and assigned batch of containers, the system
proceeds to Batch Picking by Order—Find Next Item to Pick.

Batch Picking by Order—Display Order Detail Comments

• For each distinct order associated to the pick detail task and associated to the assigned batch of
containers and item, the system determines if there are any order detail comments. If there are
comments, the system displays the detail comments. The user can page forwards or backwards
through the detail comments. The detail comments are displayed in order number, line number,
and sequence order.

Batch Picking by Order—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Batch Picking by Order—Pick an
Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Batch Picking by Order—Update Pick Information Before Out
Sorting.

Batch Picking by Order—Pick an Item

• If picking loose items, the system proceeds to Batch Picking by Order—Picking Loose Items. If
picking from an LP, the system proceeds to Batch Picking by Order—Picking LP-based Items.

122 HighJump Warehouse Advantage Functional Description

 Batch Picking by Order—Picking Loose Items
• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Order—Find Next Item to Pick.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.
• The system determines if the batch collection flag is enabled.
− If enabled, the system calculates the quantity needed by summing the remaining quantities of
the item among all containers assigned to the user. With this mode, the user is picking an
aggregate quantity to be dispersed among one or many containers.
− If not enabled, the system calculates the quantity needed by summing the remaining
quantities of the item on the first carton assigned to the user. With this mode, the user is
picking an aggregate quantity to be dispersed in only one container.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the suggested location is entered in the displayed
unit of measure. By default, the displayed unit of measure is (a) the largest defined unit of
measure for the item (if multiple units of measure are available for the item) relative to the
quantity to be picked of the identified item/lot number, or (b) the standard unit of measure of the
item (if multiple units of measure are not available for the item). If multiple units of measure are
available for the item, the user can select a unit of measure by either (a) pressing a function key
to display the next smallest unit of measure or (b) selecting a unit of measure from the available
list of units of measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.

HighJump Warehouse Advantage Functional Description 123

 • If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Order—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system proceeds to Batch Picking by Order—Replenishment Check.

Batch Picking by Order—Picking LP-based Items

• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated to the allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Order—Find Next Item to Pick.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines if the batch collection flag is enabled.
− If enabled, the system calculates the quantity needed by summing the remaining quantities of
the item among all containers assigned to the user. With this mode, the user is picking an
aggregate quantity to be dispersed among one or many containers.
− If not enabled, the system calculates the quantity needed by summing the remaining
quantities of the item on the first carton assigned to the user. With this mode, the user is
picking an aggregate quantity to be dispersed in only one container.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number associated to the LP.

124 HighJump Warehouse Advantage Functional Description

 • The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable" (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Order—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system decrements the item/lot number quantity from the source LP and leaves the LP
remaining in the source location. If the remaining quantity associated to the LP is zero, the
system (systematically) deletes the LP.
• The system proceeds to Batch Picking by Order—Replenishment Check.

Batch Picking by Order—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• The system proceeds to Batch Picking by Order—Determine Container.

HighJump Warehouse Advantage Functional Description 125

 Batch Picking by Order—Handle Quantity Exceptions
• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.

Batch Picking by Order—Determine Container

• The system determines the first container where the container's picked quantity is less than the
planned quantity.
• The system determines the quantity to be moved to the container. The quantity to be moved is
the lesser value of (a) the sum quantity remaining to be picked associated to the item and
container (a container can be associated to multiple lines of the same order and item), or (b) the
quantity of the item/lot number picked.
• The system displays the quantity to be moved, and instructs the user to scan the LP associated
to the container. The user must confirm the movement of the quantity to the container by either
(a) scanning the suggested LP, (b) scanning an LP residing on the user's equipment and
associated to the order, or (c) by identifying a new, unique LP.
• If a unique container is identified, the system proceeds to Batch Picking by Order—Confirm New
Container.

Batch Picking by Order—Move Quantity to Container

• The system increments the quantity picked on the pick detail requests associated to the container
and item.
• The system shows screen text for the quantity to be moved to container using the Universal
Quantity Behavior Type–Default Quantity.
• If more than one pick detail exists for the container and item, the amount picked is allocated
based on line number sequence. The item/lot number quantity allocated at a container/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• The order/item/lot number quantity is added or updated to the specified LP.
• A pick transaction is generated for each item/lot number quantity allocated to each pick detail.
• If the remaining amount to be moved to a container is greater than zero, the system proceeds to
Batch Picking by Order—Determine Container.
• If the remaining amount to be moved to a container is equal to zero, the system proceeds to
Batch Picking by Order—Find Next Item to Pick.

Batch Picking by Order—Confirm New Container

• If the user identifies a new container, the system displays the "Drop into New Container"
message.
• The user must respond to the message by pressing the F1 Cancel option, or by pressing Enter.
• If the F1 Cancel option is selected, the system proceeds to Batch Picking by Order—Determine
Container.
• If a new container is confirmed, the user is prompted for the container type to associate to the LP.
• The system marks the suggested carton as "closed" and assigns the identified LP to the
container. The system proceeds to Batch Picking by Order—Move Quantity to Container.

126 HighJump Warehouse Advantage Functional Description

 Batch Picking by Order—Update Pick Information Before Out Sorting
• The system updates the pick detail status to PICKED for each pick detail currently associated to
the assigned batch of containers, and where the picked quantity is greater than or equal to the
planned quantity and the staged quantity is less than or equal to the picked quantity (i.e., the
entire planned amount is picked, but not entirely staged).
• If all of the lines on the pick detail for the order have been picked as planned and there are no
remaining picks to be fulfilled, the system closes the work queue.

Batch Picking by Order—Out Sorting

• The system unassigns the user from the current work queue and the assigned pick details.
• The out sorting process manages the delivery of LP-based inventory residing on the user's
equipment first. If there are no LPs on the user's equipment, the system proceeds to Batch
Picking by Order—Out Sorting Loose Items.
• If there are no remaining open pick details associated to the order, the system proceeds to Batch
Picking by Order—Unassign.

Batch Picking by Order—Out Sorting by LP

• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.
• The system determines the order number allocated to the contents of the LP.
• The system retrieves the staging location defined for the pick detail records associated to the
order.
• If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
• If a staging location is assigned, the system directs the user to the location associated to the
order. The location must be identified by either entering or scanning the suggested location or
any valid staging or door location.
• The system updates the pick detail staging location with the specified location for each pick detail
currently associated to the order.
• The system displays the LP and order number, instructing the user to "move to" the associated
staging or door location.
• The user is prompted to enter a destination LP.
− The user can hit the F4: Put LP function button and proceed to Batch Picking by Order—Out
Sorting Put LP.
− If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
− If moving the specified item quantity as loose items within the location, the user should not
specify an LP.

HighJump Warehouse Advantage Functional Description 127

 Batch Picking by Order—Out Sorting Put LP
• For each item/lot number quantity associated to the LP, the system does the following:
− Increments the quantity staged and quantity loaded (if the deliver to location is a door
location) on the pick detail request(s) associated to the order and item. If more than one pick
detail exists for the order, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− Generates a staging transaction for each item/lot number quantity allocated to each pick
detail's staged quantity.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system moves the LP from the user's equipment into the staging/door location.
• The system proceeds to Batch Picking by Order—Update Pick Information After Out Sorting.

Batch Picking by Order—Out Sorting Loose Items

• The system determines the next item/lot number quantity residing on the user's equipment, based
on order number/item number/lot sequence.
• For the order/number/item number/lot number quantity:
− The system determines the order number allocated to the item/lot number.
− The system retrieves the staging location defined for the pick detail record(s) associated to
the order.
− If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
− If a staging location is assigned, the system directs the user to the location associated to the
order. The location must be identified by either entering or scanning the suggested location or
any valid staging or door location.
− The system updates the pick detail staging location with the specified location for each pick
detail currently associated to the order.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the item.
− If there is more than one Lot for this item the system displays the order number, item, lot
number (if applicable), and quantity to be moved to the associated staging or door location
and the user is prompted to verify the lot.
− The system displays the order number, item, and quantity to be moved to the associated
staging or door location and the user is prompted to verify the quantity.
− The user is prompted for serial numbers when the item is configured for full, outbound trace,
or trace in/out serial control and the quantity of inventory does not represent the entire
quantum of inventory (for example, a partial quantity of an item/lot number taken from an LP).
When prompted, the user scans each serial number in an “X of Y” method. The system
validates that each serial number belongs to that quantum of inventory.

128 HighJump Warehouse Advantage Functional Description

 − The user is prompted to enter a destination LP.
• If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
• If moving the specified item quantity as loose items within the location, the user should
not specify an LP.
− The system increments the quantity staged and quantity loaded (if the deliver to location is a
door location) on the pick detail request(s) associated to the order and item. If more than one
pick detail exists for the order, the item/lot quantity is allocated to the staged/loaded quantity
based on order number/line number sequence. The item/lot number quantity allocated to the
staged/loaded quantity at an order/item summary level is decremented from the user's
equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− A staging transaction is generated for each item/lot number quantity allocated to each pick
detail's staged quantity.
− A loading transaction is generated for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system proceeds to Batch Picking by Order—Out Sorting Loose Items.

Batch Picking by Order—Update Pick Information After Out Sorting

• The system updates the pick detail status to STAGED for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
picked quantity is equal to the staged quantity (i.e., the entire planned amount is picked and
staged).
• The system updates the pick detail status to LOADED for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
picked quantity is equal to the staged quantity and the staged quantity is equal to the loaded
quantity (i.e., the entire picked amount is staged and loaded).

Batch Picking by Order—Unassign

• The system decrements the number of workers assigned on the work queue.
• If the number of workers assigned is zero and all of the pick details associated to the work queue
have a status of PICKED, the system updates the work queue status to completed (C).
• If the number of workers assigned is zero and all of the pick details associated to the work queue
do not have a status of PICKED, the system unassigns the user from the work queue (U) and
removes all of the work queue assignments for the work queue.
• The system proceeds to Batch Picking by Order—Find Work Queue.

HighJump Warehouse Advantage Functional Description 129

Interface Requirements

The following interface requirements apply.

• The host system provides valid outbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 301 Picking (Pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's picked quantity.
• HighJump Warehouse Advantage generates 302 Picking (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's staged quantity.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The system prompts the user to create the packing slip for the order.

Configuration Requirements

There are no configuration requirements.

130 HighJump Warehouse Advantage Functional Description

Batch Picking by Container
The Batch Picking by Container process manages the fulfillment of one or many (a "batch")
cartonization groupings (a "container") of order-related items within the warehouse.

The process is based on the assumption that (1) an LP identifier is systematically pre-assigned to
each container, and (2) a group of LPs have been printed via an "on-demand" process or batch label
printing process, and are available to the user to scan.

Based on priority/date due/time due, the system suggests the next available grouping to the user. For
each grouping, the system directs the user to scan the pre-assigned LP associated to the container
and to select the associated container type (for example, box, tote, or envelope) in parallel with
physically labeling the container and placing the container on their equipment.

When the user's equipment has reached a user-determined capacity, or when there are no groupings
available, the user begins their pick tour. The process determines the optimal pick location for each
item associated to the assigned groupings, and then directs the user to pick a specific aggregated
item quantity from each location. For each quantity picked, the system directs the user to move
container-specific item quantities into each container.

If a container is short-picked (i.e., the container is dropped-off before picking all of the expected
items), the system assigns a unique, generic LP to the remaining group of items. This process does
not contain the functionality to generate the label associated to the LP.

When all of the items associated to the groupings have been picked, the system directs the user to
deliver the containers to the destination location associated with each order on the user's equipment.

Process Details

The following process details apply.

• The system determines if the employee is already assigned to a pick area. If the employee is not
assigned to a pick area, the system proceeds to Batch Picking by Container—Assign Pick Area.
• If the employee is assigned to a pick area, and there is only one defined pick area in the
warehouse, the system proceeds to Batch Picking by Container—Check Work Queue.
• A pick area is identified by scanning or entering a valid pick area. The system defaults to the pick
area assigned to the user. The system verifies the pick area corresponds to a valid pick area in
the warehouse. The system proceeds to Batch Picking by Container—Check Work Queue.

Batch Picking by Container—Assign Pick Area

• A pick area is identified by scanning or entering a valid pick area. The system verifies the pick
area corresponds to a valid pick area in the warehouse.
• The system updates the pick area in the employee table with the specified pick area. The system
proceeds to Batch Picking by Container—Check Work Queue.

Batch Picking by Container—Check Work Queue

• The system determines if there is a Batch Picking by Container work queue task meeting the
following criteria:
− The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).

HighJump Warehouse Advantage Functional Description 131

 − The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• If no open Batch Picking by Container work queue is found and no containers are assigned to the
user, the system displays the "no work available" message. The system proceeds to the Main
Menu process.
• If no open Batch Picking by Container work queue is found and at least one container is assigned
to the user, the system proceeds to Batch Picking by Container—Display Order Comments.
• If there is more than one Batch Picking by Container work queue that meets the criteria, the
system defaults to the work queue based on priority, date due, and time due.
• If there is at least one container assigned to the user, the user can select the F3: Done option
when they have been assigned the preferred number of containers (based on physical limitations
or user-preference). The system proceeds to Batch Picking by Container—Display Order
Comments.
• The container to be picked must be identified by scanning the label associated with the
suggested LP, or by scanning the label associated to an LP corresponding to the following
criteria:
− The work queue associated to the LP/container is not assigned to another user.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
• The system assigns the user to the work queue associated with the identified LP/container and
increments the number of workers assigned on the work queue.
• The system determines the container type associated with the Batch Picking by Container work
queue.
• The system instructs the user to select the container type associated to the Batch Picking by
Container work queue.
• The container type is not entered, and therefore cannot be overridden.
• The system proceeds to Batch Picking by Container—Check Work Queue.

Batch Picking by Container—Display Order Comments

• For each distinct order associated to the assigned batch of containers, the system determines if
there are any order comments. If there are comments, the system displays the comments. The
user can page forwards or backwards through the comments. The comments are displayed in
order number, header/footer, and sequence order.

132 HighJump Warehouse Advantage Functional Description

 Batch Picking by Container—Display Metrics
• The system determines if the "display work metrics" system flag is enabled. If enabled, the
system displays the number of distinct orders, number of remaining pick detail tasks, total weight,
and total cube associated with the remaining (open) pick detail tasks for the assigned batch of
containers.

Batch Picking by Container—Find Next Item to Pick

• The system attempts to find the next pick detail task meeting the following criteria, ordered by the
pick detail task's pick flow and location identifier.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

− The pick detail task is associated to the assigned batch of containers.

− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• If an item is found, the system proceeds to Batch Picking by Container—Select Item to Pick.
• If a pick detail task is not found based on pick flow and location identifier, and there are items on
the user's equipment, the system proceeds to Batch Picking by Container—Out Sorting.
• If a pick detail task is not found based on pick flow and location identifier, and there are no items
on the user's equipment, the system proceeds to Batch Picking by Container—Update Pick
Information Before Out sorting.

Batch Picking by Container—Select Item to Pick

• The next item number to be picked must be identified by entering or scanning a valid item number
or a valid alternative item number or UPC number associated to an item and associated to the
selected assigned batch of containers and pick area. By default, the system suggests the next
item to pick. The user can press the enter key to accept the suggested item number to be picked,
or select the F8: LST option to select an item from a list of available items. The list of available
items contains distinct items numbers meeting the following criteria:
− The pick detail task is associated to the assigned batch of containers.
− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• The system attempts to assign the user to all of the pick detail records associated to the selected
item and assigned batch of containers. If the system cannot assign the user to all of the pick
detail records associated to the selected item and assigned batch of containers, the system
proceeds to Batch Picking by Container—Find Next Item to Pick.

HighJump Warehouse Advantage Functional Description 133

 Batch Picking by Container—Display Order Detail Comments
• For each distinct order associated to the pick detail task and associated to the assigned batch of
containers and item, the system determines if there are any order detail comments. If there are
comments, the system displays the detail comments. The user can page forwards or backwards
through the detail comments. The detail comments are displayed in order number, line number,
and sequence order.

Batch Picking by Container—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Batch Picking by Container—Pick an
Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Batch Picking by Container—Update Picking Information Before
Out Sorting.

Batch Picking by Container—Pick an Item

• If picking loose items, the system proceeds to Batch Picking by Container—Picking Loose Items.
If picking from an LP, the system proceeds to Batch Picking by Container—Picking LP-based
Items.

Batch Picking by Container—Picking Loose Items

• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
unavailable, (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Container—Find Next Item to Pick.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location
• The system determines if the batch collection flag is enabled.
− If enabled, the system calculates the quantity needed by summing the remaining quantities of
the item among all containers assigned to the user. With this mode, the user is picking an
aggregate quantity to be dispersed among one or many containers.
− If not enabled, the system calculates the quantity needed by summing the remaining
quantities of the item on the first carton assigned to the user. With this mode, the user is
picking an aggregate quantity to be dispersed in only one container.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.

134 HighJump Warehouse Advantage Functional Description

 • The item/lot number quantity to be picked from the suggested location is entered in the displayed
unit of measure. By default, the displayed unit of measure is (a) the largest defined unit of
measure for the item (if multiple units of measure are available for the item) relative to the
quantity to be picked of the identified item/lot number, or (b) the standard unit of measure of the
item (if multiple units of measure are not available for the item). If multiple units of measure are
available for the item, the user can select a unit of measure by either (a) pressing a function key
to display the next smallest unit of measure or (b) selecting a unit of measure from the available
list of units of measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Container—Find Next Item to
Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system proceeds to Batch Picking by Container—Replenishment Check.

Batch Picking by Container—Picking LP-based Items

• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated to the allocated inventory.

HighJump Warehouse Advantage Functional Description 135

 • If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Container—Find Next Item to Pick.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines if the batch collection flag is enabled.
− If enabled, the system calculates the quantity needed by summing the remaining quantities of
the item among all containers assigned to the user. With this mode, the user is picking an
aggregate quantity to be dispersed among one or many containers.
− If not enabled, the system calculates the quantity needed by summing the remaining
quantities of the item on the first carton assigned to the user. With this mode, the user is
picking an aggregate quantity to be dispersed in only one container.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number associated to the LP.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.

136 HighJump Warehouse Advantage Functional Description

 • If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Batch Picking by Container—Find Next Item to
Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system decrements the item/lot number quantity from the source LP and leaves the LP
remaining in the source location. If the remaining quantity associated to the LP is zero, the
system (systematically) deletes the LP.
• The system proceeds to Batch Picking by Container—Replenishment Check.

Batch Picking by Container—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• The system proceeds to Batch Picking by Container—Determine Container.

Batch Picking by Container—Determine Container

• The system determines the first container where the container's picked quantity is less than the
planned quantity.
• The system determines the quantity to be moved to the container. The quantity to be moved is
the lesser value of (a) the sum quantity remaining to be picked associated to the item and
container (a container can be associated to multiple lines of the same order and item), or (b) the
quantity of the item/lot number picked.
• The system displays the quantity to be moved, and instructs the user to scan the LP associated
to the container. The user must confirm the movement of the quantity to the container by either
(a) scanning the suggested LP, (b) scanning an LP residing on the user's equipment and
associated to the order, or (c) by identifying a new, unique LP.
• If a unique container is identified, the system proceeds to Batch Picking by Container—Confirm
New Container.

Batch Picking by Container—Move Quantity to Container

• The system increments the quantity picked on the pick detail request(s) associated to the
container and item.
• The system shows screen text for the quantity to be moved to container using the Universal
Quantity Behavior Type–Default Quantity.

HighJump Warehouse Advantage Functional Description 137

 • If more than one pick detail exists for the container and item, the amount picked is allocated
based on line number sequence. The item/lot number quantity allocated at a container/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• The order/item/lot number quantity is added or updated to the specified LP.
• A pick transaction is generated for each item/lot number quantity allocated to each pick detail.
• If the remaining amount to be moved to a container is greater than zero, the system proceeds to
Batch Picking by Container—Determine Container.
• If the remaining amount to be moved to a container is equal to zero, the system proceeds to the
system proceeds to Batch Picking by Container—Find Next Item to Pick.

Batch Picking by Container—Confirm New Container

• If the user identifies a new container, the system displays the "Drop into New Container"
message.
• The user must respond to the message by pressing the F1 Cancel option, or by pressing Enter.
• If the F1 Cancel option is selected, the system proceeds to Batch Picking by Container—
Determine Container.
• If a new container is identified, the user is prompted for the container type to associate to the LP.
• The system marks the suggested carton as "closed" and assigns the identified LP to the
container. The system proceeds to Batch Picking by Container—Move Quantity to Container.

Batch Picking by Container—Handle Quantity Exceptions

• If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic
cycle count is configured as immediate the user may be prompted to cycle count the location.
See the Opportunistic Cycle Counting topic for more information.

Batch Picking by Container—Update Pick Information Before Out Sorting

• The system updates the pick detail status to "PICKED" for each pick detail currently associated to
the assigned batch of containers, and where the picked quantity is greater than or equal to the
planned quantity and the staged quantity is less than or equal to the picked quantity (the entire
planned amount is picked, but not entirely staged).

Batch Picking by Container—Out Sorting

• The system un-assigns the user from the current work queue and the assigned pick details.
• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.
• The system determines the order number allocated to the contents of the LP.
• The system retrieves the staging location defined for the pick detail record(s) associated to the
order and assigned batch of containers.
• If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.

138 HighJump Warehouse Advantage Functional Description

 • If a staging location is assigned, the system directs the user to the location associated to the
order and assigned batch of containers. The location must be identified by either entering or
scanning the suggested location or any valid staging or door location.
• The system updates the pick detail staging location with the specified location for each pick detail
currently associated to the order and assigned batch of containers.
• The system displays the LP and order number, instructing the user to "move to" the associated
staging or door location.
• The user is prompted to enter a destination LP.
− The user can hit the F4: Put LP function button and proceed to Batch Picking by Container —
Out Sorting Put LP.
− If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
− If moving the specified item quantity as loose items within the location, the user should not
specify an LP.

Batch Picking by Container—Out Sorting Put LP

• For each item/lot number quantity associated to the LP, the system does the following:
− Increments the quantity staged and quantity loaded (if the deliver to location is a door
location) on the pick detail request(s) associated to the order and item. If more than one pick
detail exists for the order, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− Generates a staging transaction for each item/lot number quantity allocated to each pick
detail's staged quantity.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system moves the LP from the user's equipment into the staging/door location.
• The system proceeds to Batch Picking by Container—Update Pick Information After Out Sorting.

Batch Picking by Container—Update Pick Information After Out Sorting

• The system updates the pick detail status to STAGED for each pick detail currently associated to
the assigned batch of containers, and where the picked quantity is greater than or equal to the
planned quantity and the picked quantity is equal to the staged quantity (the entire planned
amount is picked and staged).
• The system updates the pick detail status to LOADED for each pick detail currently associated to
the assigned batch of containers, and where the picked quantity is greater than or equal to the
planned quantity and the picked quantity is equal to the staged quantity and the staged quantity is
equal to the loaded quantity (the entire picked amount is staged and loaded).

HighJump Warehouse Advantage Functional Description 139

 Batch Picking by Container—Unassign
• The system decrements the number of workers assigned on the work queue.
• If the number of workers assigned is zero and all of the pick details associated to the work queue
have a status of PICKED, the system updates the work queue status to completed (C).
• If the number of workers assigned is zero and all of the pick details associated to the work queue
do not have a status of PICKED, the system un-assigns the user from the work queue (U) and
removes all of the work queue assignments for the work queue.
• The system proceeds to Batch Picking by Container—Find Work Queue.

Interface Requirements

The following interface requirements apply.

• The host system provides valid outbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 301 Picking (Pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's picked quantity.
• HighJump Warehouse Advantage generates 302 Picking (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's staged quantity.

Reporting/Labeling Requirements

The following reporting or labeling requirements applies.

• This process is dependent on pre-printed LPs to be generated and available to the user.
• The system prompts the user to create the packing slip for the order.

Configuration Requirements

There are no configuration requirements.

140 HighJump Warehouse Advantage Functional Description

Pick/Pass by Order
The Pick/Pass by Order process manages order fulfillment, or the “picking” of items for a single order
within the warehouse. For the process, items are moved into a user-specified tote on the user’s
equipment and passed by material handling equipment such as a conveyor from pick area to pick
area until the order is fulfilled.

To begin pick/pass by order, the user is prompted to enter a pick area in the system. Of the orders
that qualify for pick/pass order picking, the system determines the one with the highest priority in that
pick area. The user enters the tote number in which items will be placed for the order and begins
picking. After all items are picked from that pick area, the system determines if items from other pick
areas are required for the order.

If additional picks are required, the tote is moved to the next pick area’s pickup location. If all picks
are complete for the order, the system directs the user to deliver the product to the destination
location for the order.

Note
If the user’s tote reaches capacity before all picks are complete, the system can direct the
user to deliver product to the destination location for the order.

Assumption

The system allows only one user to work an order at a time.

Process Details

The following process details apply.

• The system determines if the employee is already assigned to a pick area. If the employee is not
assigned to a pick area, the system proceeds to Pick/Pass by Order—Assign Pick Area.
• If the employee is assigned to a pick area, and there is only one defined pick area in the
warehouse, the system proceeds to Pick/Pass by Order—Check Work Queue.
• A pick area is identified by scanning or entering a valid pick area. The system defaults to the pick
area assigned to the user. The system verifies the pick area corresponds to a valid pick area in
the warehouse. The system proceeds to Pick/Pass by Order—Check Work Queue.

Pick/Pass by Order—Assign Pick Area

• A pick area is identified by scanning or entering a valid pick area. The system verifies the pick
area corresponds to a valid pick area in the warehouse.
• The system updates the pick area in the employee table with the specified pick area. The system
proceeds to Pick/Pass by Order—Check Work Queue.

Pick/Pass by Order—Check Work Queue

• The system determines if there is a Pick/Pass by Order work queue task meeting the following
criteria:
− The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.

HighJump Warehouse Advantage Functional Description 141

 − The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
− No other user is assigned to the work queues for the order.
• If no open Pick/Pass Order work queue is found for the pick area, the system displays the "no
work available" message. The system proceeds to the Main Menu process.
• If there is more than one Pick/Pass Order work queue which meets the criteria, the system
defaults to the work queue based on priority, date due, and time due.
• The system determines if there is a tote associated with the order. If no tote is found for the order,
the system proceeds to Pick/Pass by Order—Identify Order.

Pick/Pass by Order—Identify Order via Tote

• The order to be picked must be identified by accepting the suggested tote, or by entering a tote
where the order is associated with a Pick/Pass Order work queue task that meets this criteria:
− The work queue is open (there is at least one open pick detail task associated to the work
queue, independent of the specified pick area).
− The number of workers assigned is less than the number of workers required.
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.
• The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
− No other user is assigned to the work queues for the tote’s order.
• The user can press F2: Order to identify a specific order to be picked. If F2: Order is selected, the
system proceeds to Pick/Pass by Order—Identify Order.
• The system assigns the user to the work queue associated with the identified order and
increments the number of workers assigned on the work queue. The system proceeds to
Pick/Pass by Order—Display Order Comments.

Pick/Pass by Order—Identify Order

• The order to be picked must be identified by accepting the suggested order, or by entering an
order number corresponding to the following criteria:
− The work queue is associated to at least one pick detail task meeting the following criteria:
• The pick detail task is not assigned to another employee.
• The pick detail task's planned quantity is greater than the picked quantity.
• The pick detail task has allocated inventory.

142 HighJump Warehouse Advantage Functional Description

 • The pick detail's planned pick location is in a location within the zone associated to the
user's equipment.
− No other user is assigned to the work queues for the order.
• The system assigns the user to the work queue associated with the identified order and
increments the number of workers assigned on the work queue. The system proceeds to
Pick/Pass by Order—Assign New Container to Order.

Pick/Pass by Order—Assign New Container to Order

The container to be assigned to the order must be identified by entering or scanning a unique
identifier.

Pick/Pass by Order—Display Order Comments

For the specified order, the system determines if there are any order comments. If there are
comments, the system displays the comments. The user can page forwards or backwards through
the comments. The comments are displayed in order number, header/footer, and sequence order.

Pick/Pass by Order—Display Metrics

The system determines if the "display work metrics" system flag is enabled. If enabled, the system
displays the order number, number of distinct orders (1), number of remaining pick detail tasks, total
weight, and total cube associated with the remaining (open) pick detail tasks for the order.

Pick/Pass by Order—Find Next Item to Pick

• The system attempts to find the next pick detail task meeting the following criteria, ordered by the
pick detail task's pick flow and location identifier.

Note
The pick flow and location identifier associated with each pick detail task is determined in the
order release process.

− The pick detail task is associated to the identified order.

− The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• If an item is found, the system proceeds to Pick/Pass by Order—Select Item to Pick.
• If a pick detail task is not found based, and there are items on the user's equipment, the system
proceeds to Pick/Pass by Order—Move.

Pick/Pass by Order—Select Item to Pick

• The next item number to be picked must be identified by entering or scanning a valid item number
or a valid alternative item number or UPC number associated to an item and associated to the
selected order and pick area. By default, the system suggests the next item to pick. The user can
press the enter key to accept the suggested item number to be picked, or select the F8: List
option to select an item from a list of available items. The list of available items contains distinct
items numbers meeting the following criteria:
− The pick detail task is associated to the identified order.

HighJump Warehouse Advantage Functional Description 143

 − The pick detail task's planned quantity is greater than the picked quantity.
− The pick detail task has allocated inventory.
− The pick detail's planned pick location is in a location within the zone associated to the user's
equipment.
• The system attempts to assign the user to all of the pick detail records associated to the selected
item and order. If the system cannot assign the user to all of the pick detail records associated to
the selected item and order, the system proceeds to Pick/Pass by Order—Find Next Item to Pick.
• The user also has the option to select the F2: Full if the tote is full or F3: Done.
− If F2: Full is selected, the system proceeds to Pick/Pass by Order—Out Sorting.
− If F3: Done is selected, the system unassigns the user from the work and moves the tote to
the pick area’s P&D location.

Pick/Pass by Order—Display Order Detail Comments

• For each distinct order associated to the pick detail task and associated to the order and item, the
system determines if there are any order detail comments. If there are comments, the system
displays the detail comments. The user can page forwards or backwards through the detail
comments. The detail comments are displayed in order number, line number, and sequence
order.

Pick/Pass by Order—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Pick/Pass by Order—Pick an Item.
• If F3: Done is selected, the system unassigns the user from the work and moves the tote to the
pick area’s P&D location.

Pick/Pass by Order—Pick an Item

The user can pick items directly from a location (loose items), or from an LP (license plate) residing in
a location. If picking loose items, the system proceeds to Pick/Pass by Order—Picking Loose Items. If
picking from an LP, the system proceeds to Pick/Pass by Order—Picking LP-based Items.

Pick/Pass by Order—Picking Loose Items

• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable”, (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Pick/Pass by Order—Find Next Item to Pick.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number in the location.
• The quantity defaults to the quantity to be picked.

144 HighJump Warehouse Advantage Functional Description

 • The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the location.
• The system verifies that the specified item/lot/number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Pick/Pass by Order Picking—Find Next Item to
Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• The system moves the specified item quantity from the source location to the user's equipment.
• The system increments the quantity picked on the pick detail requests associated to the order
and item. If more than one pick detail exists for the order, the amount picked is allocated based
on order number/line number sequence. The item/lot quantity allocated at an order/item summary
level is decremented from the pick location and incremented to the user's equipment location.
• A pick transaction is generated for each item/lot number quantity allocated to each pick detail.

Pick/Pass by Order—Picking LP-based Items

• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.

HighJump Warehouse Advantage Functional Description 145

 − The LP contains the item to be picked.
− The LP is associated to the allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable,” (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Pick/Pass by Order—Find Next Item to Pick.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum of the allocated quantity associated to the item on the order, or (b)
the allocated quantity of the item/lot number associated to the LP.
• The quantity defaults to the quantity to be picked.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Pick/Pass by Order—Find Next Item to Pick.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an N.
• The system increments the quantity picked on the pick detail requests associated to the order
and item. If more than one pick detail exists for the order, the amount picked is allocated based
on order number/line number sequence. The item/lot number quantity allocated at an order/item
summary level is decremented from the pick location and incremented to the user's equipment
location.
• If the specified item quantity is less than the total sum quantity associated to the LP, the system
decrements the item/lot number quantity from the source LP and leaves the LP remaining in the
source location.

146 HighJump Warehouse Advantage Functional Description

 • If the specified item quantity equals the total sum quantity associated to the LP, the item/lot
number quantity associated to the LP is converted to order/item/lot number -specific quantities. If
the quantity is allocated to more than one unique order, the source LP is (logically) deleted from
the system. If the quantity is allocated to a single order, the LP is moved to the user's equipment.
• The system generates a pick transaction for each item/lot quantity allocated to each pick detail.

Pick/Pass by Order—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• The system proceeds to Pick/Pass by Order—Find Next Item to Pick.

Pick/Pass by Order—Handle Quantity Exceptions

If opportunistic cycle counts are configured a cycle count may be generated. If the opportunistic cycle
count is configured as immediate the user may be prompted to cycle count the location. See the
Opportunistic Cycle Counting topic for more information.

Pick/Pass by Order—Move
• The system checks to if there are more picks for the order.
• If there is not, the system proceeds to Pick/Pass by Order—Out Sorting.
• If there is, the system checks to if there are more picks for pick area and the order.
− If there is, the system proceeds to Pick/Pass by Order—P&D Location.
− If there is not, the system checks to see if a conveyor associated to the pick area.
• If there is, the system proceeds to Pick/Pass by Order—Conveyor Location.
• If there is not, the system proceeds to Pick/Pass by Order—Out Sorting.

Pick/Pass by Order—P&D Location

The P&D location must be identified by either entering or scanning the suggested P&D location. The
P&D location cannot be overridden. The tote is moved to the P&D location for the pick area, and the
system proceeds to Pick/Pass by Order—Check Work Queue.

Pick/Pass by Order—Conveyor Location

The conveyor location must be identified by either entering or scanning the suggested conveyor
location. The conveyor location cannot be overridden. The tote is moved to the conveyor location for
the pick area, and the system proceeds to Pick/Pass by Order—Check Work Queue.

Pick/Pass by Order—Out Sorting

The out sorting process manages the delivery of LP-based inventory residing on the user's equipment
first. If there are no LPs on the user's equipment, the system proceeds to Pick/Pass by Order—Out
Sorting Loose Items.

HighJump Warehouse Advantage Functional Description 147

 Pick/Pass by Order—Out Sorting by LP
• The system determines the number of LPs on the user's equipment. If there is more than one LP,
the preferred LP to be put away must be identified by entering or scanning an LP identifier
associated to the user's equipment (an LP is not suggested because the system cannot
determine how the LPs are physically positioned on the user's equipment). If there is only one LP
on the user's equipment, the user is not prompted to scan an LP.
• The system determines the order number allocated to the contents of the LP.
• The system retrieves the staging location defined for the pick detail records associated to the
order.
• If a staging location has not been assigned, the system prompts the user to scan a staging
location for the order. The system validates that the location corresponds to a valid staging or
door location.
• If a staging location is assigned, the system directs the user to the location associated to the
order. The location must be identified by either entering or scanning the suggested location or
any valid staging or door location.
• The system updates the pick detail staging location with the specified location for each pick detail
currently associated to the order.
• The system displays the LP and order number, instructing the user to "move to" the associated
staging or door location and the user is prompted to scan the LP.
• The user is prompted to enter a destination LP.
− The user can press F4: Put LP to proceed to Pick/Pass by Order—Out Sorting Put LP.
− If moving the specified item/lot number quantity to an LP residing in the location, the user
should enter or scan an LP corresponding to an LP residing in the location.
− If moving the specified item quantity as loose items within the location, the user should not
specify an LP.

Pick/Pass by Order—Out Sorting Put LP

• For each item/lot number quantity associated to the LP, the system does the following:
− Increments the quantity staged and quantity loaded (if the deliver to location is a door
location) on the pick detail requests associated to the order and item. If more than one pick
detail exists for the order, the item/lot number quantity is allocated to the staged/loaded
quantity based on order number/line number sequence. The item/lot number quantity
allocated to the staged/loaded quantity at an order/item summary level is decremented from
the user's equipment location and incremented to the staging/door location.
− If a destination LP was specified, the order/item/lot number quantity is added or updated to
the specified LP.
− Generates a staging transaction for each item/lot number quantity allocated to each pick
detail's staged quantity.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system moves the LP from the user's equipment into the staging/door location.
• The system proceeds to Pick/Pass by Order—Update Pick Information After Out Sorting.

148 HighJump Warehouse Advantage Functional Description

 Pick/Pass by Order—Update Pick Information After Out Sorting
• The system updates the pick detail status to STAGED for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
picked quantity is equal to the staged quantity (i.e., the entire planned amount is picked and
staged).
• The system updates the pick detail status to LOADED for each pick detail currently associated to
the order, and where the picked quantity is greater than or equal to the planned quantity and the
picked quantity is equal to the staged quantity and the staged quantity is equal to the loaded
quantity (the entire picked amount is staged and loaded).
• The system proceeds to Pick/Pass by Order—Find Work Queue.

Interface Requirements

The following interface requirements apply.

• The host system provides valid outbound order master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 300 Pick/Pass Move transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
when a tote is moved from pick area to P&D location (conveyor).
• HighJump Warehouse Advantage generates 301 Picking (pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's picked quantity.
• HighJump Warehouse Advantage generates 302 Picking (put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's staged quantity.
• HighJump Warehouse Advantage generates 322 Picking (put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity allocated to each pick detail's loaded quantity.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There following configuration requirement applies.

• The Pick Pass Sequence needs to be defined for the pick area sequence a tote will travel
through.

HighJump Warehouse Advantage Functional Description 149

Label Picking—Confirm by Label
The Label Picking process manages the manual fulfillment of one or many orders within the
warehouse. Label picking includes printing or re-printing labels then confirming the labels individually
or in a batch after they are picked.

After labels are confirmed, the system automatically updates the relevant order information to allow
the orders to become available for loading and shipping.

Process Details

The following process details apply.

Confirm by Batch—Enter a Label ID

• The user is prompted to enter a label identification number. The system validates the following.
− If the label identification number exists and if it has not already been confirmed.
− If the label identification number has already been confirmed, the system displays an error
message to the user. The system proceeds to Confirm by Label—Enter Label Selection.

Confirm by Label—Enter Label Selection

• The user is prompted to enter a selection for the label.
− If the user wants to confirm the label, the user can select the F3:Confirm option. The system
creates a record for processing to confirm the label and proceeds to Confirm by Label—Label
Confirmed.
− If the user wants to void the label, the user can select the F4: Void option. The system
creates a record for processing to void the label and proceeds to Confirm by Label—Enter a
Label ID.
− If the user wants to indicate that the label was short picked, the user can select the F5: Short
option. The system proceeds to Confirm by Label—Enter New Quantity.

Confirm by Label—Enter New Quantity

• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The system validates if the quantity entered is greater than zero and less than or equal to the
planned quantity. The system creates a record for processing to short the item and proceeds to
Confirm by Label—Enter a Label ID.

Confirm by Label—Label Confirmed

• The system displays the number of labels confirmed and resets the confirmed label counter. The
system automatically updates the order information with the picked quantities. The order is
available for loading and shipping.

Interface Requirements

There are no interface requirements.

150 HighJump Warehouse Advantage Functional Description

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

The following configuration requirements apply.

• A stored procedure makes the final confirmation of labels (including updates to the label status,
moves for inventory, and transaction logging). The stored procedure must be configured to run on
a scheduled basis.
For more information, see the "Configure Confirm Label Picking Job" section of HighJump
Advantage Application Database Installation Guide.

Label Picking—Confirm by Batch

The Label Picking process manages the manual fulfillment of one or many orders within the
warehouse. Label picking includes printing or re-printing labels then confirming the labels individually
or in a batch after they are picked.

After labels are confirmed, the system automatically updates the relevant order information to allow
the orders to become available for loading and shipping.

Process Details

The following process details apply.

Confirm by Batch—Select Batch

• The user is prompted to enter a batch identification number. The system validates the batch
identification number exists, there are no picked or unprinted labels, and the batch has labels with
an unconfirmed status. If any label in the batch has not yet been printed or has already been
confirmed, the system displays an error message to the user.

Confirm by Batch—Enter an Exception Label ID

• The user is prompted to enter a label ID for a label in the batch if the label was short picked or not
picked. The system validates the label ID exists in the batch identification number and the label
has not been confirmed. The system proceeds to Confirm by Batch—Enter Label Selection.
• If the user wants to confirm all labels in the batch, the user can select the F3: Confirm Batch
option. The system creates a record for processing to confirm the label and proceeds to Confirm
by Batch—Labels Confirmed.

Confirm by Batch—Enter Label Selection

• The user is prompted to enter a selection for the label.
− If the user wants to void the label, the user can select the F4: Void option. The system
creates a record for processing to void the label and proceeds to Confirm by Batch—Enter an
Exception Label ID.
− If the user wants to indicate the label was short picked, the user can select the F5: Short
option. The system proceeds to Confirm by Batch—Enter New Quantity.

HighJump Warehouse Advantage Functional Description 151

 Confirm by Batch—Enter New Quantity
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The system validates the quantity entered is greater than zero and less than or equal to the
planned quantity. The system creates a record for processing to short the item and proceeds to
Confirm by Batch—Enter an Exception Label ID.

Confirm by Batch—Labels Confirmed

• The system displays the number of labels confirmed and resets the confirmed label counter. The
system automatically updates the order information with the picked quantities. The order is
available for loading and shipping.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 304 Confirm Label Picking transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There following configuration requirements apply.

• A stored procedure makes the final confirmation of labels (including updates to the label status,
moves for inventory, and transaction logging). The stored procedure must be configured to run on
a scheduled basis.
For more information, see the "Configure Confirm Label Picking Job" section of HighJump
Advantage Application Database Installation Guide.

Warehouse Transfer Out

The Warehouse Transfer Out process manages the transfer, or picking, of a user-specified item and
quantity within the warehouse.

Based on a specific item number and quantity, the process determines the optimal pick location
associated to each item and then directs the user to pick an item quantity from a location in parallel
with moving the product to the user's equipment.

When the user's equipment reaches a user-determined capacity, or when there are no more items to
be picked, a user-specified destination location is entered and the inventory associated to the user's
equipment is deleted from the system.

Process Details

The following process details apply.

• A control number is identified by scanning or entering a meaningful identifier to associate with the
transfer. The control number is not required and is not validated, and is only captured to include
in the transaction log.

152 HighJump Warehouse Advantage Functional Description

 Warehouse Transfer Out—Request an Item to be Picked
• The item number to be picked must be identified by entering or scanning a valid item number or a
valid alternative item number or UPC number associated to the item number.
• The system will not verify the availability of inventory associated to the identified item.
• The system prompts for quantity using the Universal Quantity Behavior Type–Request.
• The system verifies that the quantity is greater than zero, and does not verify the quantity with
respect to available inventory for the item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Warehouse Transfer Out—Drop-off.

Warehouse Transfer Out—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Warehouse Transfer Out—Pick an
Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Warehouse Transfer Out—Drop-off.

Warehouse Transfer Out—Pick an Item

• The user can pick items directly from a location (loose items), or from an LP (license plate)
residing in a location. If picking loose items, the system proceeds to Warehouse Transfer Out—
Picking Loose Items. If picking from an LP, the system proceeds to Warehouse Transfer Out—
Picking LP-based Items.

Warehouse Transfer Out—Picking Loose Items

• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Warehouse Transfer Out—Determine Pick Location.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum quantity remaining to be picked associated to the requested item
quantity or (b) the quantity of the item/lot number in the location.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.

HighJump Warehouse Advantage Functional Description 153

 • To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", and (b) generates a Cycle Count by Location work queue request for the
suggested location, (c) removes associated allocation records, and (d) inserts record for item
into the allocation queue. The system proceeds to Warehouse Transfer Out—Determine Pick
Location.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system decrements the item/lot quantity from the pick location, and increments the item/lot
number quantity on the user's equipment.
• The system increments the quantity picked of the item.
• The system generates a pick transaction for each item/lot number quantity picked.

Warehouse Transfer Out—Picking LP-based Items

• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP exists in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated to the allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Warehouse Transfer Out—Determine Pick Location.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.

154 HighJump Warehouse Advantage Functional Description

 • If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum quantity remaining to be picked associated to the item, or (b) the
quantity of the item/lot number associated to the LP.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Warehouse Transfer Out—Determine Pick
Location.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system decrements the item/lot number quantity from the pick location, and increments the
item/lot quantity on the user's equipment.
• The system increments the quantity picked of the item.
• A pick transaction is generated for each item/lot number quantity picked.
• If the specified item/lot number quantity is less than the total sum quantity associated to the LP,
the system decrements the item/lot quantity from the source LP and leaves the LP remaining in
the source location.
• If the specified item/lot number quantity equals the total sum quantity associated to the LP, the LP
is moved to the user's equipment.
• The system generates a pick transaction for each item/lot number quantity picked.

HighJump Warehouse Advantage Functional Description 155

 Warehouse Transfer Out—Replenishment Check
• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and if an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system does not verify the availability of inventory associated to the identified item.
• If the remaining quantity to be picked is greater than zero, the system proceeds to Warehouse
Transfer Out—Determine Pick Location.
• If the remaining quantity to be picked is equal to zero, the system proceeds to Warehouse
Transfer Out—Request an Item to be Picked.

Warehouse Transfer Out—Drop-Off

• The system prompts the user to scan the destination location to which the inventory is being
transferred. The destination location is required but not validated, and is only captured to include
in the transaction log.
• The system deletes the inventory associated to the user's equipment.

Note
The inventory is NOT moved to the specified destination location.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 540 Warehouse Transfer Out (Pick) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated for each item quantity moved to the user's equipment.
• HighJump Warehouse Advantage generates 541 Warehouse Transfer Out (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated for each item quantity removed from the user's equipment.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

156 HighJump Warehouse Advantage Functional Description

Miscellaneous Issue
The Miscellaneous Issue process manages the issue, or picking, of a user-specified item and quantity
within the warehouse.

Based on a specific item number and quantity, the process determines the optimal pick location
associated to each item and then directs the user to pick an item quantity from a location in parallel
with moving the product to the user's equipment.

When the user's equipment reaches a user-determined capacity, or when there are no more items to
be picked, a user-specified destination location is entered and the inventory associated to the user's
equipment is deleted from the system.

Process Details

The following process details apply.

• A control number is identified by scanning or entering a meaningful identifier to associate with the
issue. The control number is not required and is not validated, and is only captured to include in
the transaction log.

Miscellaneous Issue—Request an Item to be Picked

• The item number to be picked must be identified by entering or scanning a valid item number or a
valid alternative item number or UPC number associated to the item number.
• The system will not verify the availability of inventory associated to the identified item.
• The system prompts for quantity to be picked using the Universal Quantity Behavior Type–
Request.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Miscellaneous Issue—Drop-off.
• The user is prompted for a quantity relative to each available unit of measure for the item. The
system verifies that the quantity is greater than or equal to zero. The quantity entered, regardless
of the selected unit of measure, is converted to the item's base unit of measure and added to the
total quantity of the item/lot number.
• The system verifies that the quantity is greater than zero, and does not verify the quantity with
respect to available inventory for the item.

Miscellaneous Issue—Location Found

• The pick location must be identified by either entering or scanning the suggested location. The
pick location cannot be overridden. The system proceeds to Miscellaneous Issue—Pick an Item.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Miscellaneous Issue—Drop-off.

Miscellaneous Issue—Pick an Item

• If picking loose items, the system proceeds to Miscellaneous Issue—Picking Loose Items. If
picking from an LP, the system proceeds to Miscellaneous Issue—Picking LP-based Items.

HighJump Warehouse Advantage Functional Description 157

 Miscellaneous Issue—Picking Loose Items
• The item number to be picked must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Miscellaneous Issue—Determine Pick Location.
• The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. The preferred lot number to be picked must be identified by entering or
scanning a lot number; when configured for full lot control the lot number must be associated to
the selected item in the location.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum quantity remaining to be picked associated to the requested item
quantity or (b) the quantity of the item/lot number in the location.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.
• The system verifies that the specified item/lot number is not associated to an LP residing in the
pick location.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Miscellaneous Issue —Determine Pick Location.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.

158 HighJump Warehouse Advantage Functional Description

 • The system decrements the item/lot number quantity from the pick location, and increments the
item/lot number quantity on the user's equipment.
• The system increments the quantity picked of the item.
• The system generates a pick transaction for each item/lot number quantity picked.
• The system proceeds to Miscellaneous Issue—Replenishment Check.

Miscellaneous Issue—Picking LP-based Items

• When picking items associated to an LP-based location, the user is prompted to identify a source
LP. The source LP is the LP containing the item to be picked. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is not on hold.
− The LP is residing in the specified pick location.
− The LP contains the item to be picked.
− The LP is associated the allocated inventory.
• If the suggested location does not contain the suggested item, the user can select the F7: Empty
option. The F7: Empty option (a) flags the inventory for the specified item in the location as
unavailable, (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Miscellaneous Issue—Determine Pick Location.
• The system lists the quantity and item number for each item associated to the LP.
• The system determines the number of distinct lot numbers associated with the selected item on
the LP.
• If there are multiple lot numbers, or the item is configured for outbound trace or trace in/out lot
control, the preferred lot number to be picked must be identified by entering or scanning a lot
number associated to the selected item on the LP.
• If the item is not lot-controlled, or there is only one lot number for the selected item on the LP, the
user is not prompted to scan a lot number.
• The system determines the quantity to be picked from the location. The quantity to be picked is
the lesser value of (a) the sum quantity remaining to be picked associated to the item, or (b) the
quantity of the item/lot number associated to the LP.
• The quantity defaults to the quantity to be picked.
• The item/lot number quantity to be picked from the specified LP is entered in the displayed unit of
measure. By default, the displayed unit of measure is (a) the largest defined unit of measure for
the item (if multiple units of measure are available for the item) relative to the quantity to be
picked of the identified item/lot number, or (b) the standard unit of measure of the item (if multiple
units of measure are not available for the item). If multiple units of measure are available for the
item, the user can select a unit of measure by either (a) pressing a function key to display the
next smallest unit of measure or (b) selecting a unit of measure from the available list of units of
measure.
• To identify damaged items, the user can select the F5: DG option displayed at the quantity
prompt. The system (a) generates a Cycle Count by Location work queue request for the location
and (b) generates a "Damage Reported" Exception Log entry in the HighJump Warehouse
Advantage Exception Log.

HighJump Warehouse Advantage Functional Description 159

 • The system validates that the quantity entered is less than or equal to the quantity to be picked
from the LP.
• The user is prompted for serial numbers when the item is configured for full serial control only if
the picked quantity does not represent the entire quantum of inventory. The user is prompted for
serial numbers when the item is configured for outbound trace or trace in/out serial control. When
prompted, the user scans each serial number in an “X of Y” method. Scanned serial numbers are
validated and must be unique for the item in the warehouse; when configured for full serial control
the serial number must belong to that quantum of inventory.
• If the quantity picked is less than the quantity suggested, the system displays the "Quantity
picked is less than available. Change status to Unavailable?" prompt.
− If the suggested quantity could not be picked due to inventory issues, the user should
respond with a "Y". The system (a) flags the inventory for the specified item in the location as
"unavailable", (b) generates a Cycle Count by Location work queue request for the suggested
location, (c) removes associated allocation records, and (d) inserts record for item into the
allocation queue. The system proceeds to Miscellaneous Issue —Determine Pick Location.
− If the suggested quantity could not be picked based on physical limitations of the user's
equipment or by user-preference, the user should respond with an "N".
• The quantity to be picked, regardless of the selected unit of measure, is converted to the item's
base unit of measure.
• The system decrements the item/lot number quantity from the pick location, and increments the
item/lot quantity on the user's equipment.
• The system increments the quantity picked of the item.
• A pick transaction is generated for each item/lot number quantity picked.
• If the specified item/lot number quantity is less than the total sum quantity associated to the LP,
the system decrements the item/lot quantity from the source LP and leaves the LP remaining in
the source location.
• If the specified item/lot number quantity equals the total sum quantity associated to the LP, the LP
is moved to the user's equipment.
• The system generates a pick transaction for each item/lot number quantity picked.
• The system proceeds to Miscellaneous Issue—Replenishment Check.

Miscellaneous Issue—Replenishment Check

• If the source location is a forward pick location, the quantity remaining in the location is less than
the forward pick's replenishment, and an open replenishment request for the item and location
does not exist, the system generates a replenishment request for the specified item and location.
The amount to be picked is set to the replenishment quantity defined for the item and forward pick
location.
• The system will not verify the availability of inventory associated to the identified item.
• If the remaining quantity to be picked is greater than zero, the system proceeds to Miscellaneous
Issue—Determine Pick Location.
• If the remaining quantity to be picked is equal to zero, the system proceeds to Miscellaneous
Issue—Request an Item to be Picked.

160 HighJump Warehouse Advantage Functional Description

 Miscellaneous Issue—Drop-Off
• The system prompts the user to scan the destination location to which the inventory is being
issued. The destination location is required but not validated, and is only captured to include in
the transaction log.
• The system deletes the inventory associated to the user's equipment.

Note
The inventory is NOT moved to the specified destination location.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 545 Miscellaneous Issue (Pick) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated for each item quantity moved to the user's equipment.
• HighJump Warehouse Advantage generates 546 Miscellaneous Issue (Put) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated for each item quantity removed from the user's equipment.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 161

Reprint Packing Slip
The Reprint Packing Slip process manages the re-printing of the packing slip report for any pick in the
warehouse.

Process Details

The following process details apply.

• The system prompts the user to enter the load ID and validates if it exists (Wave ID or Load ID).
• The system determines if at least one order on the pick and is staged.
• If there are multiple orders on the pick, the system does the following:
− Prompts the user to enter order number.
− Verifies the order number is associated to the load ID and all lines on the order are staged.
• The system prompts the user for the printer to use when printing the report. It defaults the printer
by the warehouse and type in the label printing configuration.
• The system prompts the user if the print was successful. The user can reprint the packing slip if
necessary.

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The process can be configured into any other processes which require re-printing of packing slip
reports.

Configuration Requirements

There following configuration requirement applies.

• A printer must exist and should be configured to communicate with HighJump Warehouse
Advantage Application.

162 HighJump Warehouse Advantage Functional Description

Shipping
Shipping includes the following processes:
• Packing
• Post Manifest Container
• License Plate Audit Check
• License Plate Audit
• Loading
• Load Audit
• Unload/Unpick
• Shipping
• Shipping by Container
• Reusable Container Shipping
• Reprint Bill of Lading

HighJump Warehouse Advantage Functional Description 163

Packing
The Packing process manages the movement of allocated (picked) item/lot quantities into a packing
container.

Based on a user-identified staging location, order number, and load ID, the user identifies the items
and quantities to be associated to the container (LP) in parallel with placing the product into the
container.

Process Details

The following process details apply.

Packing—Enter Packing Location

• The user enters the staging location containing allocated inventory to be packed. The system
validates that the location is a staging location.

Packing—Enter Order to Pack

• If there is inventory allocated to an order in the staging location and the order is completely
picked and staged, the system suggests the order to the user. The user may enter any order that
has inventory staged in the location. If an order’s inventory was put into the staging location on a
license plate, the user can select the F2: By Source LP option to pack by LP (license plate).
Using this option the user may scan the source license plate instead of having to enter the order
number. The system proceeds to Packing—Pack from LP.
• The user is prompted to enter the order number that they want to pack. The order number
defaults to an order number that is completely picked and staged and has inventory in the staging
location. It is possible to start packing an order that is not completely picked and staged.
• The system verifies the order number is associated to a valid order number, and that the
specified staging location contains allocated inventory associated to the order.
• The system determines whether the order has been split across more than one load. If it has
been split across more than one load, then the system prompts the user for the load they want to
pack. The system verifies the load ID is a load identifier associated to the specified order and that
the order/load has inventory in the staging location.
• If the order has loose inventory sitting in the staging location, meaning the inventory in the staging
location is not on a license plate, the system proceeds to Packing—Select Item to Pack,
otherwise it proceeds to Packing—Pack from LP.

Packing—Pack from LP
• The system prompts the user to scan the source license plate.
• If the user is done packing for this order they can select F3: Done which takes them to the order
number prompt. The system proceeds to Packing—Enter Order to Pack.
• The system verifies the LP is in the staging location and is associated with the order for which the
packer indicated they were going to perform packing. If HighJump Warehouse Advantage
Adapter for HighJump Ship or HighJump Advantage Link for Flagship is used, the system also
validates that the license plate has not been manifested.
• If there is loose inventory for the order in the staging location, the user may select F2: Pack
Loose. The system proceeds to Packing—Pack Loose.

164 HighJump Warehouse Advantage Functional Description

 • The system suggests the first item it finds in the source LP. The system prompts the user to scan
the item ID that they want to pack.
• If the user wants to move the complete contents of the source license plate into the container
being packed, they can select the F4: MoveAll function key. The system proceeds to Packing—
Scan the Destination Container.
• The system validates that the item entered exists on the LP.
• The system determines whether the item is lot-controlled. If the item is lot-controlled, the system
completes the following tasks:
− Prompts the user for the lot number. The system suggests one of the lots for this item that
can be found in the license plate; however, the user may pack any lot that exists for this item
in the license plate.
− Validates that the lot exists in the license plate for this item.
• The system determines the quantity of the indicated inventory in the source license plate.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The user is prompted for serial numbers when the item is configured for full, outbound trace, or
trace in/out serial control and the quantity of inventory does not represent the entire quantum of
inventory (for example, a partial quantity of an item/lot number taken from an LP). When
prompted, the user scans each serial number in an “X of Y” method. The system validates that
each serial number belongs to that quantum of inventory.

Packing—Scan the Destination Container

• The system prompts the user to scan the license plate of the container into which the inventory is
being packed. If the LP entered does not already exist, then the system creates it and proceeds
to Packing—Identify Container Type.
• If the license plate that was entered already exists, the system validates the following criteria:
− The license plate number corresponds to a license plate staged in this staging location.
− The LP is associated with the order being packed.
− If HighJump Advantage Link for Flagship is used, the system validates that the LP is not
already manifested.
• The system proceeds to Packing—Pack Inventory.

Packing—Identify Container Type

• The system prompts the user to identify the container type to associate to the new container.
• The system verifies the container type is associated to a valid container type used in the
warehouse.
• The system creates a license plate and pick container.
• The system moves the inventory from the source license plate to the destination license plate and
updates the packed quantity on the pick details.

Packing—Pack Inventory
• After the destination LP has been validated, the inventory is moved from the source into the
destination license plate.
• The system generates a 315 log transaction.

HighJump Warehouse Advantage Functional Description 165

 • If the user was packing from a source license plate, the system checks if the source LP is now
empty. If it is empty, the system displays a message to the user indicating the source license
plate is empty.
• The system checks to see if everything has been packed for the order. If so, the system displays
a message to the user indicating packing is complete for the order and the system proceeds to
Packing—Enter Order to Pack.
• If the user was packing from a source LP, then the system returns to the Packing—Pack from LP.
Otherwise, it returns to Packing—Select Item to Pack.

Packing—Select Item to Pack

• The item number to be packed must be identified by entering or scanning a valid item number or
a valid alternative item number such as a UPC number. The system validates the item
corresponds to an item meeting the following criteria:
− The item is associated to the specified order and load ID.
− The item is associated to allocated inventory for the order residing in the specified staging
location.
• If user is done packing items to the LP, the user selects the F3: Done option. The system
proceeds to Packing—Enter Order to Pack.
• If the item is lot-controlled, the system prompts the user to scan the lot number associated to the
specified item. The system validates the item/lot combination corresponds to an item/lot
combination meeting the following criteria:
− The item/lot combination is associated to allocated inventory for the order/item/lot residing in
the specified staging location.
• The system determines the remaining quantity available to be packed from the location.
• The user is then prompted to enter the quantity of inventory being moved from the staging
location into the packing container.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The user is prompted for serial numbers when the item is configured for full, outbound trace, or
trace in/out serial control and the quantity of inventory does not represent the entire quantum of
inventory (for example, a partial quantity of an item/lot number taken from an LP). When
prompted, the user scans each serial number in an “X of Y” method. The system validates that
each serial number belongs to that quantum of inventory.
• The system then proceeds to Packing—Scan the Destination Container.

Packing—Check for Parcel Manifesting

• The system checks to see if the manifest_carrier_flag for the carrier associated with the order
being packed into the container is set to ‘Y’. If the flag is set to’ N’, the process returns to
Packing—Enter Order to Pack.
• The system prompts the user to scan the license plate to manifest. The license plate defaults to
the first license plate on the order or load found in the location.
• If the container’s carrier is a parcel carrier, the system checks to see if the user should be
prompted for container dimensions. If not, the container dimensions are taken from the container
type and the process goes to the weight prompt.
• If dimensions are to be entered, the user is prompted for length, width, and height.

166 HighJump Warehouse Advantage Functional Description

 • The container weight is calculated from the items in the containers and the user is prompted to
confirm or override.
• The user is prompted for the printer for the parcel system to use when printing the parcel label.
• The system sends the container information to the parcel system and receives a tracking number
and freight charge.
• The system returns to Packing—Enter Order to Pack.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 315 Packing transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. A single transaction is available
for each item/lot packed.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 167

Post Manifest Container
The Post Manifest Container process allows the user to manifest containers that have been picked for
an order with a parcel carrier but not pre-manifested.

Process Details

The following process details apply.

Post Manifest Container—Select Container

• The user is prompted to identify a container to be manifested. The following validations occur:
− The LP exists.
− The LP is associated to an order with a parcel carrier.
− The LP has a manifest status of ‘NEW’ or ‘NONE’.

Post Manifest Container—Enter Dimensions and Weight

• The system determines if the user should be prompted for container dimensions. If not, the
container dimensions are taken from the container type and the process goes to the weight
prompt.
• If dimensions are to be entered, the user is prompted for length, width, and height.
• The container weight is calculated from the items in the container plus the container weight and
the user is prompted to confirm or override.
• The user is prompted for the printer for the parcel system to use when printing the parcel label.
• The system sends the container information to the parcel system and receives a tracking number
and freight charge.
• The system returns to Post Manifest Container—Select Container

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

The following configuration requirement applies.

• A manifest system must exist and be configured to communicate with HighJump Warehouse
Advantage.

168 HighJump Warehouse Advantage Functional Description

License Plate Audit Check
The License Plate Audit Check process determines if an inspection and review of an LP’s contents is
required.

The system determines if the license plate requires an audit check based on whether an audit check
is required for the employee that picked the LP, the items on the LP, or an audit cost value.

Process Details

The following process details apply.

• The system determines if the warehouse is set up to use license plates.
• If the warehouse is not set up to use license plates, the system displays the message “Must be
using LP’s” to the user. The user presses Enter to confirm and the system exits the process.
• The system prompts the user to identify an LP. The LP is identified by scanning or entering an
LP.
• The system verifies the LP exists.
• The system determines if the picks for the employee that picked the selected the LP require an
audit.
• If an audit is required, the system displays a message indicating an audit is required for the LP.
The user presses Enter to confirm and the system proceeds to the beginning of the LP Audit
Check process.
• If an audit is not required, the system determines if any items on the LP require an audit.
• If any items on the LP require an audit, the system displays a message indicating an audit is
required for the LP. The user presses Enter to confirm and the system proceeds to the beginning
of the LP Audit Check process.
• If no items on the LP require an audit, then the system determines if the total cost of all of the
items on the LP is greater than or equal to the system defined audit cost value.
• If the total cost of all of the items on the LP is greater than or equal to the audit cost value, the
system displays a message indicating an audit is required for the LP. The user presses Enter to
confirm and the system proceeds to the beginning of the LP Audit Check process.
• If the total cost of all of the items on the LP is less than the audit cost value, the system displays a
message indicating no audit is required for the LP. The user presses Enter to confirm and the
system proceeds to the beginning of the LP Audit Check process.

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

If you want the system to compare the total cost of all of the items on the LP to an audit cost in order
to determine if an audit is required, enable and define the system control, AUDIT_COST.

HighJump Warehouse Advantage Functional Description 169

License Plate Audit
The License Plate Audit process manages the inspection and review of a LP’s contents.

Based on a user-selected LP, the user identifies the items and quantities physically associated to the
LP. The system displays an error message when a quantity mismatch is identified.

After all of the items have been counted by the user, the system verifies that all of the expected items
were counted. The system then directs the user to count any uncounted items associated to the LP.

Process Details

The following process details apply.

LP Audit—Select LP to Audit
• The user is prompted to identify a source LP to be audited. The source LP is identified by
scanning or entering an LP. The system verifies the LP corresponds to an existing LP meeting
the following criteria:
− The LP is associated to un-allocated inventory, staged inventory, or loaded inventory.
• The system flags each item on the LP as "un-verified" to denote each item's quantity has not
been verified, or counted.

LP Audit—Select Item to Count

• The item number to be counted must be identified by entering or scanning a valid item number or
a valid alternative item number or UPC number associated to the item number. The system does
not validate that the item corresponds to an item associated to the LP.
• If the user is done counting all of the items associated to the LP, the user selects the F3: Done
option. The system proceeds to Loading—Verify All Items Have Been Counted.

LP Audit—Enter Item Quantity

• The total quantity associated to the item and LP is entered by the user. If the item is lot-
controlled, the user should enter the total quantity associated to the item across all lots
associated to the item and LP.
• If the quantity of the item entered equals the total quantity of the item associated to the LP, the
system:
− Updates the item on the LP as "verified".
− Generates an LP Audit transaction.
− Proceeds to LP Audit—Select Item to Count.

170 HighJump Warehouse Advantage Functional Description

 • If the quantity of the item entered does not equal the total quantity of the item associated to the
LP, the system:
− Displays the quantity entered and the total quantity of the item associated to the LP.
− Generates a 401 "Quantity Mismatch” Exception Log entry.
− Updates the item on the LP as verified.
− Generates an LP Audit transaction.
− Proceeds to LP Audit—Select Item to Count.

LP Audit—Verify All Items are Counted

• The system determines if there is at least one item on the LP flagged as unverified. If there is at
least one unverified item, the system selects the first unverified item associated to the LP and
proceeds to LP Audit—Enter Item Quantity.
• If all items associated to the LP have been verified, the system proceeds to LP Audit—Select LP
to Audit.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 885 LP Audit transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. A single transaction is available
for each item counted.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• Generation of Packing Lists and BOL are not included within the process.

Configuration Requirements

The following configuration requirements apply.

• The quantity of an existing item associated to the LP cannot be modified with this process.
• A new item cannot be added to the LP with this process.

HighJump Warehouse Advantage Functional Description 171

Loading
The Loading process manages the movement of staged inventory within the warehouse. Loading can
be performed in a system-directed or automatic mode.

System Directed Loading

Based on a specified order or load ID, the system directs the user to move a specific staged item/lot
number quantity or LP in parallel with moving the product to the user's equipment.

When the user's equipment reaches a user-determined capacity, or when there are no more items to
be moved, the system directs the user to deliver the product to the door location associated with the
order on the user's equipment.

Automatic Loading

Based on a specific order or load ID, the system automatically moves all staged item/lot number
quantities and LPs to a door location.

Automatic loading moves the staged inventory associated to the load ID to a single door location. The
door location is the door location defined for the first order associated to the load ID. Movement to
more than one distinct door location defined across multiple orders is not supported.

Process Details

The following process details apply.

Note
If HighJump Advanced Fulfillment Application is being used—or if the host has specified a
load ID on the order—the user enters the load ID when prompted for it. Otherwise, the user
must enter the order ID when prompted for the load ID, as the order is considered the load.

Loading—Check Work Queue

• The system determines if there is a Load work queue task meeting the following criteria:
− The work queue is unassigned (the work queue is not assigned to another user, not marked
as "complete" and not marked as "on hold").
− The work queue is associated to at least one pick detail task meeting the following criteria:
The pick detail task's staged quantity is greater than zero, and the staged quantity is greater
than the loaded quantity.
• If an unassigned Load work queue is not found, the system proceeds to Loading—Select Load
ID.
• If there is more than one Load work queue that meets the criteria, the system defaults to the work
queue based on priority, date due, and time due.

Loading—Select Load ID
• The order or load to be shipped must be identified by accepting the suggested order or load, or
by entering an identifier corresponding to the following criteria:
− The identifier is associated to a load ID of an existing Load work queue.

172 HighJump Warehouse Advantage Functional Description

 • The system determines if the Load work queue is on hold. If the Load work queue is on hold, the
system displays the "ORDER/LOAD ON HOLD" error message and proceeds to Loading—Check
Work Queue.
• The system assigns the user to the Load work queue associated with the identified load ID and
increments the number of workers assigned on the work queue.
• The user can be directed to load order-specific item/lot number quantities and order-specific LPs
("system-directed" loading), or to automatically move all of the associated staged inventory en
masse ("auto-loading"). The mode of operation (system-directed vs. auto-loading) is determined
by the system control setting for Directed Loading.
− If directed loading is enabled, the system proceeds to Loading—System Directed.
− If directed loading is not enabled, the system proceeds to Loading—Automatic.

Loading—System Directed
• The system finds the first pick detail task (ordered by order number) associated to the identified
load ID, where the pick detail's staged quantity is greater than the loaded quantity.
• The system prompts the user to scan the order number to be loaded. The order number defaults
to the order number associated to the first pick detail task.
• The system verifies the order number is associated to a valid order number, is associated to the
load ID, and is associated to at least one pick detail task where the pick detail task's staged
quantity is greater than the loaded quantity.
• The system retrieves the door location defined for the pick detail records associated to the order
and load ID.
− If a door location has not been assigned, the system prompts the user to scan a door location
for the order. The system validates that the location corresponds to a valid door location.
− The system updates the pick detail staging location with the specified location for each pick
detail currently associated to the order.

Loading—Select Item/LP
• The user can move items directly from a location (loose items), or by LP (license plate) residing in
a location. The mode of operation (loose vs. LP) is determined by the system-level "item/LP" flag.
− If the "item/LP" flag is enabled to scan an item, or enabled to scan either an item or LP, the
system proceeds to Loading—Select Item to Load.
− If the "item/LP" flag is only enabled to scan an LP, the system proceeds to Loading—Select
LP to Load.

Loading—Select Item to Load

• The system finds the first allocated item/lot quantity residing in a staging location and associated
to the order number and load ID (ordered by staging location ID, item number, and lot number).

Loading—Display Item/Lot Quantity

• The system displays the order number, item number, staging location, and quantity associated to
the allocated inventory.
• If there is more than one item/lot quantity associated to the order number and load ID, the user
can select the F8: Next option to view the next allocated item/lot quantity. The system proceeds
to Loading—Display Item/Lot Quantity.

HighJump Warehouse Advantage Functional Description 173

 • If there is more than one item/lot quantity associated to the order number and load ID, the user
can select the F4: Prev option to view the previous allocated item/lot quantity. The system
proceeds to Loading—Display Item/Lot Quantity.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Loading—Drop-off.
• The user can select the F6: Use option to confirm loading of the displayed item/lot number.
• The system displays the staging location associated to the selected item/lot number, and directs
the user to scan the item number.
• The item number to be loaded must be identified by entering or scanning the valid item number or
a valid alternative item number or UPC number associated to the suggested item.
• If the item is lot-controlled, the system displays the lot number associated to the selected item/lot
number, and directs the user to scan the lot number.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The user is prompted for serial numbers when the item is configured for full, outbound trace, or
trace in/out serial control and the quantity of inventory does not represent the entire quantum of
inventory (for example, a partial quantity of an item/lot number taken from an LP). When
prompted, the user scans each serial number in an “X of Y” method. The system validates that
each serial number belongs to that quantum of inventory.
• The system moves the specified item/lot number quantity from the staging location to the user's
equipment. A movement transaction is generated for each item quantity moved to the user's
equipment.
• The system finds the next allocated item/lot number quantity residing in a staging location and
associated to the order number and load ID (ordered by staging location ID, item number, and lot
number). If an item if found, the system proceeds to Loading—Display Item/Lot Quantity. If an
item is not found, the system proceeds to Loading—Drop-off.

Loading—Select LP to Load
• The system finds the first allocated, staged LP residing in a non-equipment location and
associated to the order number and load ID (ordered by location ID).
• The system displays the location associated to the LP, and directs the user to scan the LP.
• The LP to be loaded must be identified by entering or scanning the suggested LP, or by entering
or scanning an LP meeting the following criteria:
− The LP is associated to the order and load ID.
− The LP is associated to a staged LP.
− The LP is not on hold.
• If the user's equipment has reached a user-determined capacity, the user selects the F3: Done
option. The system proceeds to Loading—Drop-off.
• The system moves the LP and its associated item/lot quantities from the location associated to
the LP to the user's equipment. The system generates a movement transaction for each item/lot
quantity associated to the LP.
• The system determines if there is at least one allocated item/lot quantity residing in a staging
location and associated to the order number and load ID. If there is at least one item/lot quantity
remaining to be staged, the system proceeds to Loading—Select Item/LP. If there are no
remaining item/lot quantities remaining to be staged, the system proceeds to Loading—Drop-off.

174 HighJump Warehouse Advantage Functional Description

 Loading—Drop-off
• The system directs the user to the door location associated to the order. The location must be
identified by scanning the suggested location. The suggested location cannot be overridden.
• The Loading—Drop-off process manages the drop-off of LP-based inventory residing on the
user's equipment first. If there are no LPs on the user's equipment, the system proceeds to
Loading—Drop-off Loose Items.

Loading—Drop-off LPs
• For each LP residing on the user's equipment:
− For each item number/lot number quantity associated to the LP, the system does the
following:
• Increments the quantity loaded on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot quantity is allocated to
the loaded quantity based on order number/line number sequence. The item/lot number
quantity allocated to the loaded quantity at an order/item summary level is decremented
from the user's equipment location and incremented to the door location.
• Generates a loading transaction for each item/lot quantity allocated to each pick detail's
loaded quantity.
− The system updates the LP's location to the specified door location.
• If there are loose items remaining on the user's equipment, the system proceeds to Loading—
Drop-off Loose Items.
• The system unassigns the user to the Load work queue associated with the identified load ID and
determines the number of workers assigned on the work queue.
• The system proceeds to Loading—Check Work Queue.

Loading—Drop-off Loose Items

• For each item number/lot number quantity residing on the user's equipment, the system does the
following:
− Increments the quantity loaded on the pick detail request(s) associated to the order and item.
If more than one pick detail exists for the order, the item/lot number quantity is allocated to
the loaded quantity based on order number/line number sequence. The item/lot quantity
allocated to the loaded quantity at an order/item summary level is decremented from the
user's equipment location and incremented to the door location.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system unassigns the user to the Load work queue associated with the identified load ID and
determines the number of workers assigned on the work queue.
• The system proceeds to Loading—Check Work Queue.

Loading—Automatic
• The system finds the first pick detail task (ordered by order number) associated to the identified
load ID, where the pick detail's staged quantity is greater than the loaded quantity.
• The system retrieves the door location defined for the pick detail record(s) associated to the order
and load ID.

HighJump Warehouse Advantage Functional Description 175

 − If a door location has not been assigned, the system prompts the user to scan a door
location. The system validates that the location corresponds to a valid door location.
− The system updates the pick detail staging location with the specified location for each pick
detail currently associated to the load ID.
• The system finds the first pick detail task (ordered by order number) associated to the identified
load ID, where the pick detail's staged quantity is greater than the loaded quantity.

Loading—Automatic Load Items/LPs for Order

• The system automatically loads all of the loose item/lot quantities and LPs associated to the order
number load ID.
• The Loading—Automatic process manages the loading of staged LP-based inventory first.

Loading—Automatic Load LPs for Order

• For each staged LP associated to the order and load ID:
− For each item number/lot number quantity associated to the LP, the system does the
following:
• Increments the quantity loaded on the pick detail requests associated to the order and
item. If more than one pick detail exists for the order, the item/lot quantity is allocated to
the loaded quantity based on order number/line number sequence. The item/lot number
quantity allocated to the loaded quantity at an order/item summary level is decremented
from the location associated to the LP and incremented to the door location.
• Generates a loading transaction for each item/lot quantity allocated to each pick detail's
loaded quantity.
− The system updates the LP's location to the specified door location.

Loading—Automatic Load Items for Order

• For each item number/lot number quantity associated to the order and load ID, the system does
the following:
− Increments the quantity loaded on the pick detail requests associated to the order and item. If
more than one pick detail exists for the order, the item/lot number quantity is allocated to the
loaded quantity based on order number/line number sequence. The item/lot number quantity
allocated to the loaded quantity at an order/item summary level is decremented from the
location associated to the item/lot and incremented to the door location.
− Generates a loading transaction for each item/lot number quantity allocated to each pick
detail's loaded quantity.
• The system finds the next pick detail task (ordered by order number) associated to the identified
load ID, where the pick detail's staged quantity is greater than the loaded quantity and the pick
detail's order number is greater than the previous order number. If a pick detail task is found, the
system proceeds to Loading—Automatic Load Items/LPs for Order.
• The system unassigns the user to the Load work queue associated with the identified load ID and
determines the number of workers assigned on the work queue.
• The system proceeds to Loading—Check Work Queue.

176 HighJump Warehouse Advantage Functional Description

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 320 Loading (Auto) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item/lot quantity moved from the staging location to the door location.
• HighJump Warehouse Advantage generates 321 Loading (Pick) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item/lot quantity moved from the staging location to the user's equipment.
• HighJump Warehouse Advantage generates 322 Loading (Put) transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item/lot quantity moved from the user's equipment to the door location.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 177

Load Audit
The Load Audit process manages the inspection and review of a load’s contents after all orders for
the load have been loaded. Based on the load, the user identifies the items and quantities physically
in the door location. The system displays an error message when a quantity mismatch is identified.

After all of the items have been counted by the user, the system verifies that all of the expected items
were counted. The system then directs the user to count any uncounted items associated to the load.

Process Details

The following process details apply.

Load Audit—Select Order

• The user is prompted to identify a source order or load ID to be audited. The source order or load
ID is identified by entering an identification number. The system defaults the first ship request in
the work queue. The work queue is sorted by priority and due date. The system verifies the
entered order or load ID exists.
• The system looks for any items not fully picked. (The quantity picked does not equal the quantity
ordered.)
− If the system finds items where the quantity picked does not equal the quantity ordered, the
system proceeds to Load Audit—Verify Quantity Ordered and Quantity Picked.
− If the system does not find items where the quantity picked does not equal the quantity
ordered, the system proceeds to Load Audit—Verify Quantity Picked and Quantity Loaded.

Load Audit—Verify Quantity Ordered and Quantity Picked

• The system displays the order number, item number, line number, the quantity ordered, and the
quantity picked. The user must confirm the item information is correct.
• If user is done verifying items, the system looks for any items not fully loaded. (The quantity
loaded does not equal the quantity picked.)
• If the system finds items where the quantity loaded does not equal the quantity picked, the
system proceeds to Load Audit—Verify Quantity Picked and Quantity Loaded.
• If the system does not find items where the quantity picked does not equal the quantity ordered,
the system determines if the shipment is a partial shipment.
− If the shipment is partial shipment, the system generates a transaction.
− If the shipment is not a partial shipment, the system determines if confirmation is required. If
confirmation is required, the system proceeds to Load Audit—Ready to Ship. If confirmation
is not required, the system determines if a packing slip is required.
• If a packing slip is not required, the system updates the work queue load audit request to
complete, updates work queue dependencies, and generates a transaction. Then the
system proceeds to Load Audit—Confirmation.
• If a packing slip is required, the system proceeds to Load Audit—Ready to Print Reports.

178 HighJump Warehouse Advantage Functional Description

 Load Audit—Verify Quantity Picked and Quantity Loaded
• The system displays the order number, item number, line number, the quantity picked, and the
quantity loaded. The user must confirm the item information is correct.
• If user is done verifying items, the system determines if the shipment is a partial shipment.
− If the shipment is partial shipment, the system generates a transaction.
− If the shipment is not a partial shipment, the system determines if confirmation is required. If
confirmation is required, the system proceeds to Load Audit—Ready to Ship. If confirmation
is not required, the system determines if a packing slip is required.
• If a packing slip is not required, the system updates the work queue load audit request to
complete, updates work queue dependencies, and generates a transaction. Then the
system proceeds to Load Audit—Confirmation.
• If a packing slip is required, the system proceeds to Load Audit—Ready to Print Reports.

Load Audit—Ready to Ship

• The system prompts the user to indicate if the order is ready to ship by displaying the following
prompt: “Is <order number> ready to ship?” The user enters ’Y’ or ‘N’.
− If the order is ready to ship, the system determines if a packing slip is required.
• If a packing slip is not required, the system updates the work queue load audit request to
complete, updates work queue dependencies, and generates a transaction. Then the
system proceeds to Load Audit—Confirmation.
• If a packing slip is required, the system proceeds to Load Audit—Ready to Print Reports.

Load Audit—Ready to Print Reports

• The system prompts the user to indicate if they are ready to print reports by displaying the
following prompt “Ready to print reports?” The user enters ’Y’ or ‘N’.
• If the user is ready to print reports, the system prints packing list and bill of lading reports.
• The system updates the work queue load audit request to complete, updates work queue
dependencies, and generates a transaction. Then the system proceeds to Load Audit—
Confirmation.

Load Audit—Confirmation
• The system confirms to the user that the load is ready to ship by displaying the following prompt:
“Load <order number> is ready to ship.”
• The user selects Enter to confirm.
• The system proceeds to Load Audit—Select Order.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 330 Load Audit transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. A single transaction is available
for each item counted.

HighJump Warehouse Advantage Functional Description 179

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The process can be configured to print packing list and bill of lading reports.

Configuration Requirements

There are no configuration requirements.

Unload/Unpick
The Unload/Unpick process manages the movement of staged and loaded inventory within the
warehouse.

Based on a specified order or load ID, the system directs the user to unload/unpick a specific loaded
or staged item/lot number quantity or LP in parallel with moving the product to the user's equipment.
Systematically, the unloaded/unpicked item quantities are deallocated from the associated pick detail
tasks.

When the user's equipment reaches a user-determined capacity, or when there are no more items to
be unloaded/unpicked, the user is directed to put away the items on their equipment.

Process Details

The following process details apply.

Unload/Unpick—Select Load ID
• The order or load to be unloaded/unpicked must be identified by entering an identifier
corresponding to the following criteria:
− The identifier is an order or load associated to a pick detail task.
• The system determines the distinct number of order identifiers associated to the load ID. If there
is only one distinct order identifier found, the system proceeds to Unload/Unpick—Select Item/LP.
• If there is more than one distinct order identifier associated to the load ID, the system prompts the
user to identify the order associated to the load ID. The system verifies the number is associated
to a valid order number, and is an order number associated to the load ID.

Unload/Unpick—Select Item/LP
• The user can unload items directly from a location (loose items), or by LP (license plate) residing
in a location. The mode of operation (loose vs. LP) is determined by the system-level "Item/LP"
flag.
− If the Item/LP Flag is enabled to scan an item, or enabled to scan both an item or LP, the
system proceeds to Unload/Unpick—Select Item to Unload/Unpick.
− If the Item/LP flag is only enabled to scan an LP, the system proceeds to Unload/Unpick—
Select LP to Unload/Unpick.

180 HighJump Warehouse Advantage Functional Description

 Unload/Unpick—Select Item to Unload/Unpick
• When moving loose items, the user is prompted to identify a source location. The source location
is the location containing the allocated (picked) item or items to be unloaded. The source location
is identified by scanning or entering any location which meets the following criteria:
− The location corresponds to a valid non-equipment type location.
− The location contains allocated inventory associated to the order.
• The item number to be unloaded/unpicked must be identified by entering or scanning a valid item
number or a valid alternative item number or UPC number associated to the item number. The
system validates the item corresponds to an item meeting the following criteria:
− The item is associated to the specified order.
− The item is associated to allocated inventory for the order residing in the specified location.
• If the user's equipment has reached a user-determined capacity, or there are no more items to
unload/unpick, the user selects the F3: Done option. The system proceeds to the Directed Put-
Away process.
• If the item is configured for full, outbound trace, or trace in/out lot control, the preferred lot number
to be moved must be identified by entering or scanning a lot number associated to the selected
item. The system validates the item/lot combination corresponds to an item/lot combination
meeting the following criteria:
− The item/lot combination is associated to allocated inventory for the order/item/lot residing in
the specified staging location.
• The system determines the remaining quantity available to be unloaded/unpicked from the
location.
• The item/lot quantity to be picked from the suggested location is entered in the displayed unit of
measure.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.
• The system validates that the quantity entered is less than or equal to the available item/lot
quantity to be unloaded/unpicked from the location.
• The system verifies that the specified item/lot quantity is not associated to an LP residing in the
specified location.
• The user is prompted for serial numbers when the item is configured for full, outbound trace, or
trace in/out serial control and the quantity of inventory does not represent the entire quantum of
inventory (for example, a partial quantity of an item/lot number taken from an LP). When
prompted, the user scans each serial number in an “X of Y” method. The system validates that
each serial number belongs to that quantum of inventory.
• The user is prompted to enter a destination LP. The destination LP is not required.
− If moving the specified item/lot quantity to an LP residing on the user's equipment, the user
should enter or scan an LP corresponding to a unique LP or an LP residing on the user's
equipment.
− If moving the specified item/lot quantity as loose items to the user's equipment, the user
should not specify an LP.

HighJump Warehouse Advantage Functional Description 181

 • If the specified location corresponds to a staging location, the system:
− Decrements the quantity staged on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot quantity is deallocated from
the staged quantity based on order number/line number sequence. The item/lot quantity
deallocated from the staged quantity at an order/item summary level is decremented from the
staging location and incremented to the user's equipment.
− Adds or updates the specified destination LP with the item/lot quantity.
− Generates an unpick transaction for each item/lot quantity deallocated to each pick detail's
staged quantity.
• If the specified location corresponds to a door location, the system:
− Decrements the quantity loaded on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot quantity is deallocated from
the loaded quantity based on order number/line number sequence. The item/lot quantity
deallocated from the loaded quantity at an order/item summary level is decremented from the
door location and incremented to the user's equipment.
− Adds or updates the specified destination LP with the item/lot quantity.
− Generates an unload transaction for each item/lot quantity deallocated to each pick detail's
loaded quantity.
• The system proceeds to Unload/Unpick—Select Item to Unload/Unpick.

Unload/Unpick—Select LP to Unload/Unpick
• The user is prompted to scan an LP to unload/unpick. The LP to be unloaded/unpicked must be
identified by entering or scanning an LP meeting the following criteria:
− The LP is associated to the order.
− The LP is associated to a staged or loaded LP.
− The LP is not on hold.
− The LP is not residing in an equipment location.
• If the user's equipment has reached a user-determined capacity, or there are no more items to
unload/unpick, the user selects the F3: Done option. The system proceeds to the Directed Put-
Away process.
• The user must identify what item is to be unloaded/unpicked by either (a) entering or scanning a
valid item number, valid alternative item number or UPC number associated to an item on the
selected LP or (b) pressing the F2:Take LP option to unload/unpick all items associated to the LP.
If the F2: Take LP option is selected, the system proceeds to Unload/Unpick—Move Entire LP
from Location.

Unload/Unpick of Individual Item/Lot Quantity from LP

• If the item is configured for full, outbound trace, or trace in/out lot control, the preferred lot number
to be moved must be identified by entering or scanning a lot number associated to the selected
item on the LP.
• The system verifies that the identified item and lot exists on the specified LP.
• The system prompts for quantity using the Universal Quantity Behavior Type–Default Quantity.

182 HighJump Warehouse Advantage Functional Description

 • The user is prompted for serial numbers when the item is configured for full, outbound trace, trace
in/out serial control and the quantity of inventory does not represent the entire quantum of
inventory (for example, a partial quantity of an item/lot taken from an LP). When prompted, the
user scans each serial number in an “X of Y” method. The system validates that each serial
number belongs to that quantum of inventory when configured for full serial control.
• If the specified location corresponds to a staging location, the system:
− Decrements the quantity staged on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot quantity is deallocated from
the staged quantity based on order number/line number sequence. The item/lot quantity
deallocated from the staged quantity at an order/item summary level is decremented from the
staging location and incremented to the user's equipment.
− Decrements the order/item/lot quantity from the source LP.
− Generates an unpick transaction for each item/lot number quantity deallocated to each pick
detail's staged quantity.
• If the specified location corresponds to a door location, the system:
− Decrements the quantity loaded on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot number quantity is
deallocated from the loaded quantity based on order number/line number sequence. The
item/lot number quantity deallocated from the loaded quantity at an order/item summary level
is decremented from the door location and incremented to the user's equipment.
− Decrements the order/item/lot number quantity from the source LP.
− Generates an unload transaction for each item/lot quantity deallocated to each pick detail's
loaded quantity.
• The system proceeds to Unload/Unpick—Select Item to Unload/Unpick.

Unload/Unpick Entire LP from Location

• The user can select to move an entire LP and its contents from a location by selecting the F2:
Take LP option. The F2: Take LP option is only available if all item/lot quantities are not on hold.
• For each item number/lot number quantity associated to the LP:
− If the specified location corresponds to a staging location, the system:
• Decrements the quantity staged on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot number quantity is
deallocated from the staged quantity based on order number/line number sequence. The
item/lot number quantity deallocated from the staged quantity at an order/item summary
level is decremented from the staging location and incremented to the user's equipment.
• Generates an unpick transaction for each item/lot quantity deallocated to each pick
detail's staged quantity.
− If the specified location corresponds to a door location, the system:
• Decrements the quantity loaded on the pick detail request(s) associated to the order and
item. If more than one pick detail exists for the order, the item/lot number quantity is
deallocated from the loaded quantity based on order number/line number sequence. The
item/lot number quantity deallocated from the loaded quantity at an order/item summary
level is decremented from the door location and incremented to the user's equipment.
• Generates an unload transaction for each item/lot number quantity deallocated to each
pick detail's loaded quantity.

HighJump Warehouse Advantage Functional Description 183

 • The system updates the LP's location to the user's equipment.
• The system proceeds to Unload/Unpick—Select Item to Unload/Unpick.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 391 Unload/Unpick (pick) transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for each item/lot quantity moved from the staging or door location to the user's
equipment.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

184 HighJump Warehouse Advantage Functional Description

Shipping
The Shipping process manages the shipment of items from the warehouse. Based on specified load
ID, the system collects the carrier, PRO number, and seal number associated with the shipment. For
each order on the shipment, the system generates order/item/line-specific shipment transactions in
parallel with removing the associated inventory from the warehouse.

Note
If the order being shipped is a transfer order, the system also creates an inbound order
(including inbound order master/detail, where the order type is transfer, and ASN
master/detail) for the destination warehouse. It is based on all LPs shipped as part of the
outbound transfer order.
For customers who use simple transfers with ASNs, the system creates a vendor record to
represent the source warehouse, where Vendor Code is set to Warehouse ID and Vendor
Name is set to Warehouse Name. This functionality applies to shipping by load and shipping
by container.

The system does not perform any validation with respect to the order's quantities picked, planned, or
loaded.

Note
Holds placed by item or LP are valid for all inventory throughout the warehouse. For inventory
being processed for outbound orders, holds also apply to unshipped items on forks, at
staging locations, and at door locations. To return the held inventory to a storage location,
follow the Unload/Unpick process.

Process Details

S1 – Shipping by Load—Check Work Queue

• The system determines if there is a Ship work queue task meeting the following criteria:
− The work queue is unassigned (in other words, the work queue is not assigned to another
user, not marked as complete, and not marked as on hold.)
• If an unassigned Ship work queue is not found, the system displays the "no work available"
message. The system proceeds to the Main Menu process.
• If there is more than one Ship work queue that meets the criteria, the system defaults to the work
queue based on priority, date due, and time due.
• The load to be shipped must be identified by accepting the suggested load, or by entering an
identifier corresponding to the following criteria:
− The identifier is associated to a load ID of an existing Ship work queue.
• The system determines if the Ship work queue is on hold. If the Ship work queue is on hold, the
system displays the "ORDER/LOAD ON HOLD" error message and proceeds to Shipping—
Check Work Queue.
• The system determines if the Ship work queue is complete (i.e., a shipment has already been
performed against the load ID). If the Ship work queue is complete, the system generates the
error message Shipping Complete.

HighJump Warehouse Advantage Functional Description 185

 Shipping—Verify Shipment
• The system verifies that all picked items for the orders on the shipment are loaded.
• The system checks the orders associated with the load and verifies that the carrier for the orders
is NOT a parcel carrier. (Parcel containers are shipped with the Close Manifest Process.)
• If there are lines that are not fully loaded, the system displays the message LOADING
INCOMPLETE.
• Verifies that either all items have been picked for each line on an order or that orders with under
picked lines have the partial ship flag set to Y.
• If there are under picked lines that are not allowed the system displays the message ORDER
UNDERPICKED.
• If the work queue is unassigned, the system assigns the user by setting the work status to A and
incrementing the number of workers. The system also locks all other work queues for the load by
setting their status to A.

Shipping—Collect Shipment Information

• The user is required to identify the carrier to associate to the shipment. The carrier can be
identified by either entering the carrier name, or by selecting the carrier from a list of carrier
names. By default, the carrier defaults to the carrier name associated to the first order on the
shipment. The carrier name is required and is validated.
• The carrier name is not captured in the transaction log.
• A PRO number is identified by scanning or entering a meaningful identifier to associate with the
shipment. The PRO number is not required and is not validated.
• The PRO number is not captured in the transaction log.
• A seal number is identified by scanning or entering a meaningful identifier to associate with the
shipment. The seal number is not required and is not validated.
• The seal number is not captured in the transaction log.
• After all the data is gathered, the system puts it into a record and publishes the Shipped Load
message.

Shipping—Process Shipped Load Message

• The Shipped Load message is transmitted by HighJump Message Bus from the HighJump
Warehouse Advantage Base application to the HighJump Warehouse Advantage Base
application (self-subscribed publish/receive). The receipt of the Shipped Load Message initiates a
process object that updates inventory, updates control information, and logs the transaction.
• The Employee ID passed in the message is verified by a lookup in t_employee.
• The Advantage Link Flag is checked if is it set two queries are called that inserts data into to
t_al_host_shipment_master and t_al_host_shipment_detail.
• The order detail lines on the load are updated with shipment quantity.
• All picked inventory associated with the load is deleted.
• Shipment date is updated for order master records associated with the load and their statuses are
set to S.
• The status of pick detail records are set to ‘SHIPPED’ for the load.

186 HighJump Warehouse Advantage Functional Description

 • The work queue for the load is set to complete.
• Dependent work queues are updated based on the work queues that have been completed.
• One transaction type 340 (Shipping) is generated and placed in the transaction log. A transaction
type 341 (Shipping Detail) is also generated for each item shipped and placed in the transaction
log.

Interface Requirements

HighJump Warehouse Advantage generates 340 Shipping and 341 Shipping Detail transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification.

Reporting/Labeling Requirements

Generation of Packing Lists and BOL are not included within the process.

Configuration Requirements

There are no configuration requirements.

Shipping by Container
The Shipping by Container process manages the shipment of parcel items from the warehouse.
Based on specified Container ID, the system generates order/item/line-specific shipment transactions
in parallel with removing the associated inventory from the warehouse.

Note
Holds placed by item or LP are valid for all inventory throughout the warehouse. For inventory
being processed for outbound orders, holds also apply to unshipped items on forks, at
staging locations, and at door locations. To return the held inventory to a storage location,
follow the Unload/Unpick process.

Process Details

S1 – Shipping by Container—Enter Container

• The container to be shipped must be identified by entering the container label.
• The system determines if the container is an existing LP in the warehouse.

Shipping by Container—Verify Container

• The system verifies that the container has been picked.
• The system verifies the container is NOT a parcel container.

Shipping by Container—Process Shipped Container Message

• The Shipped Container message is transmitted by HighJump Message Bus from the HighJump
Warehouse Advantage Base application to the HighJump Warehouse Advantage Base
application (self-subscribed publish/receive). The receipt of the Shipped Container Message
initiates a process object that updates inventory, updates control information, and logs the
transaction.

HighJump Warehouse Advantage Functional Description 187

 • The Advantage Link Flag is checked and if it set, then two queries are called that insert data into
t_al_host_shipment_master and t_al_host_shipment_detail.
• The order detail lines for the container are updated with shipment quantity.
• All picked inventory associated with the container is deleted.
• Shipment date is updated for order master records associated with the container and their
statuses are set to ‘S’.
• The status of pick detail records are set to ‘SHIPPED’ for the container.
• Dependent work queue (t_work_q_dependency) is deleted for the ship work queue that has been
completed.
• One transaction type 340 (Shipping) is generated and placed in the transaction log. A transaction
type 341 (Shipping Detail) is also generated for each item shipped and placed in the transaction
log.

Interface Requirements

HighJump Warehouse Advantage generates 340 Shipping and 341 Shipping Detail transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification.

Reporting/Labeling Requirements

Generation of Packing Lists and BOL are not included within the process.

Configuration Requirements

The system does not perform any validation with respect to the order's quantities picked, planned, or
loaded.

Reusable Container Shipping

The Reusable Container Shipping process manages the shipment of reusable containers from the
warehouse.

Process Details

Reusable Container Shipping—Enter Container

• The user is prompted to enter or scan a container number for the container to be shipped.
• The system determines if the container is a reusable container.
− If the container is not a reusable container, the system displays a message to the user
indicating the container does not exist. The user presses Enter to continue and the system
prompts the user to enter a container number.
− If the container is a reusable container, the system determines if the container is checked out.
• If the container is checked out, the system displays a message to the user indicating the
container is checked out. The user presses Enter to continue and the system prompts the
user to enter a container number.
• If the container is not checked out, the system proceeds to Reusable Container
Shipping—Enter Order Number.

188 HighJump Warehouse Advantage Functional Description

 Reusable Container Shipping—Enter Order Number
• The user is prompted to enter or scan an order number.
• The system verifies the order number exists and retrieves the ship-to customer code from the
order. The system updates the status of the container to be checked out, updates the customer
code associated to the container, and sets the receipt/ship date to now.
• The system displays the following prompt, “Transaction Complete”. The user presses Enter to
continue and the system proceeds to Reusable Container Shipping—Enter Container.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 174 Reusable Container Ship transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

Reprint Bill of Lading

The Reprint Bill of Lading process manages the reprinting of the bill of lading report for any order in
the warehouse.

Process Details

The following process details apply.

• The system prompts the user to enter a valid order number.
• The system validates if the order exists in the warehouse.
• The system prompts the user for the printer to use when printing the report. It defaults the printer
by the warehouse and type in the label printing configuration.
• The system prompts the user if the print was successful. The user can reprint the bill of lading if
necessary.

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

The following reporting or labeling requirement applies.

• The process can be configured into any other processes which require to re-print bill of lading
reports.

HighJump Warehouse Advantage Functional Description 189

Configuration Requirements

There following configuration requirement applies.

• A printer must exist and should be configured to communicate with HighJump Warehouse
Advantage Application.

190 HighJump Warehouse Advantage Functional Description

Inventory
Inventory includes the following processes:
• View Inventory
• Inventory Adjustment
• Scrap

For information about the Web pages you can use to view inventory information, see “Inventory
Pages and Reports” in HighJump Advantage Dashboard Functional Description.

View Inventory
The View Inventory process displays the inventory details associated to a specific item, location,
license plate, lot number, serial number, or order number. The user can configure a scanned field to
display the inventory data on one or more screens in the required sequence. The process groups the
information by displayed elements, for example LP, item, and location, and sums up the quantity.

Using the HighJump Warehouse Advantage web page, Search View Inventory Controls, you can
configure the system to display the associated details based on the scanned input on the RF screen.
For example, if a warehouse does not use lot numbers, you can configure the warehouse to not
display lot number information on the RF screen.

Process Details

The following process details apply.

• When there is a duplicate entry, the user is prompted to select the fields to display. For example,
if the scanned value matches both an item and a lot number, the system displays item and lot.
The user selects from these options to confirm which criteria should be used.
• When multiple display screens are configured for the scanned field, the user can select the “View”
function key to toggle between the available display screens. The user can move forward through
the sequence of configured screens and return to the first screen after the last configured display.
• If there are multiple inventory records for the field, then the user can select the “Next” and
“Previous” function keys to move back and forth through the inventory records.
• By default, the system displays the lowest unit of measure.
• When multiple units of measure (UOM) are defined for the displayed item, the user can select the
UOM function key to select an alternate unit of measure to display. Any remainder from the UOM
selected displays as the lowest UOM for the item (usually eaches).
• The current view remains the same for subsequent scans of the same field. For example, if the
user scans a location and changes the display screen, that screen remains active upon a
subsequent location scan.

HighJump Warehouse Advantage Functional Description 191

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

Build Master LP
The Build Master LP process allows the user to build a master license plate (MLP) from existing
license plates (LPs). MLPs can be built from either storage inventory LPs or picked inventory LPs;
however an MLP cannot contain both types of LPs. Users can also set additional restrictions for
mixing LPs.

Process Details

The following process details apply.

• The system prompts the user to scan or enter the MLP. The MLP can be either an existing or new
MLP.
− If the MLP exists, the system prompts the user to confirm moving the MLP to the user’s fork
location and displays the number of LPs currently associated with the MLP.
− If the MLP is new, the system creates the MLP on the user’s fork location.
• The system prompts the user to scan or enter the LP to add to the MLP.
− The LP must exist.
− The user cannot mix storage and picking LPs within an MLP. For example, if the MLP
contains LPs associated with orders, the user cannot add a storage LP to the MLP.

Note
If the warehouse control option BUILD_MLP_MIX_TYPE is enabled, the user can set control
values allowing further restrictions for mixing LPs by order or load.

• If the scanned LP is associated with a different MLP, the system prompts the user to confirm
movement to the current MLP.
• The user can continue scanning or entering additional LPs to the current MLP until the user
selects the F3: Done option.
• The system prompts the user to scan or enter a destination location. The destination location
must be MLP-controlled.
− If the LPs are associated with picked inventory, the destination must be a staging location or
door.
• The system displays a transaction complete message, and prompts the user for confirmation.

192 HighJump Warehouse Advantage Functional Description

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates an 860 Build Master LP (Pick) transaction as
detailed in the HighJump Warehouse Advantage Log Transactions specification. The transactions
are generated for each item quantity moved to the MLP.
• HighJump Warehouse Advantage generates an 861 Build Master LP (Put) transaction as detailed
in the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for each item quantity when the MLP is put into a destination.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

Inventory Adjustment
The Inventory Adjustment process manages the adjustment of a specific quantum associated to a
master license plate (MLP), license plate (LP), or inventory location. Users can scan an MLP, LP, or
location and adjust the associated items. If the inventory does not exist at the location, then the user
can create it using this process.

Based on a user-specified MLP, LP, or location, the user enters the total quantity that is associated to
a specific item/lot number and expiration date. After the user enters a reason code for the adjustment,
the system updates the MLP/LP/location and inventory with the difference between the existing
quantity and the entered quantity (delta quantity), and generates an adjustment transaction.

Note
If the inventory being created has an open recall against it, the system notifies the user that
the inventory has been recalled and puts it on hold. If multiple holds are not allowed and
multiple recalls exist, the system uses the hold code from the oldest recall.

• When there is a duplicate entry, the user is prompted to select the fields to display. For example,
if the scanned value matches both an LP and a location, the system displays LP and Location.
The user selects from these options to confirm which criteria should be used.
• Users can create inventory including MLPs/LPs/items in a location.
• Users can create items with the full inventory quantum (lot number, serial number, and expiration
date).
• Inventory with the following statuses can be adjusted:
− Available
− Unavailable
− Held
• Inventory in active and inactive locations can be adjusted.
• Inventory adjustments cannot be made for picked inventory.

HighJump Warehouse Advantage Functional Description 193

 • Users can remove the inventory by setting the inventory quantity to zero; MLPs and LPs are
removed if the user removes all of its contents.
• An inventory adjustment of allocated inventory triggers re-allocation after the adjustment process
completes.
• The inventory adjustment process captures a reason code from a configurable list along with
details about the adjustment.

Process Details

The following process details apply.

Inventory Adjustment—Select Location, MLP, or LP

• The system prompts the user to scan or enter a value for location, MLP, or LP that requires
adjustment.
− The system identifies if the value scanned is a location, MLP, or LP.

Note
The Inventory Adjustment process does not adjust picked inventory or inventory that is
located in an equipment location.

• When there is a duplicate entry, the user is prompted to select the fields to be display. For
example, if the scanned value matches both an LP and a location, the system displays LP and
Location. The user selects from these options to confirm which criteria should be used.
• If the user enters or scans a location to adjust, it must meet the following criteria:
− The system verifies the location identifier or short location identifier entered is valid.
− The system verifies if the location corresponds to a non-equipment location.
− The system verifies if the entered location is MLP, LP or item-controlled.
• If the location is MLP-controlled, the system proceeds to Inventory Adjustment—Select
MLP.
• If the location is LP-controlled, the system proceeds to Inventory Adjustment—Select LP.
• If the location is item-controlled, the system proceeds to Inventory Adjustment—Select
Item.
• If the user enters or scans an MLP or LP to adjust, it must meet the following criteria:
− The MLP/LP exists in a non-equipment type location.
− The MLP/LP must be an inventory type of “IV”.
− The MLP/LP does not exist.
• If the entered value is an MLP, the system proceeds to Inventory Adjustment—Select LP.
• If the entered value is an LP, the system proceeds to Inventory Adjustment—Select Item.
• If the user enters or scans an unknown value to adjust, the system proceeds to Inventory
Adjustment—Check for New MLP/LP.

194 HighJump Warehouse Advantage Functional Description

 Inventory Adjustment—Check for New MLP/LP
• If the user enters an MLP or LP that does not exist, the system adds the MLP/LP as new
inventory and uses format validation to validate the entry. The system prompts for confirmation
and the user must enter Y or N.
• The system prompts the user to confirm if the new value is an MLP or LP.
• The user must enter the location where the MLP or LP should be stored.

Note
The location must be MLP/LP-controlled.

− If the user selects MLP, the system proceeds to Inventory Adjustment—Select LP.
− If the user selects LP, the system proceeds to Inventory Adjustment—Select Item.

Inventory Adjustment—Select MLP

• The system prompts the user to enter or scan the MLP in the location to be adjusted.
• If the user selects the F8: List option, the system displays the MLPs associated to the location. If
the user chooses an MLP from this list, the system proceeds to Inventory Adjustment—Select LP.
• If the user enters an MLP that does not exist, the system uses format validation to validate the
entry. The system prompts for confirmation and the user must enter Y or N.
• If the user enters an MLP that exists in a different location, the system prompts the user to
confirm the move to the new location and the user must enter Y or N.
• If the user selects Y, the system prompts the user to generate a cycle count for the source
location. The user must enter Y or N.
• If the user enters or scans an MLP, the system proceeds to Inventory Adjustment—Select LP.

Inventory Adjustment—Select LP
• The system prompts the user to enter or scan the LP in the location to be adjusted.
• If the user selects the F8: List option, the system displays the LPs associated to the location
and/or the MLP that was previously scanned. If the user chooses an LP from this list, the system
proceeds to Inventory Adjustment—Select Item.
• If the user enters an LP that does not exist, the system uses format validation to validate the
entry. The system prompts for confirmation and the user must enter Y or N.
• If the user enters an LP that exists in a different location, the system prompts the user to confirm
the move to the new location. The user must enter Y or N.
• If the user selects Y, the system prompts the user to generate a cycle count for the source
location. The user must enter Y or N.
• If the user has previously scanned an MLP to adjust, and scans an LP that is not currently
associated with the MLP, the system prompts the user to confirm movement to the current MLP.
• If the user enters or scans an LP, the system proceeds to Inventory Adjustment—Select Item.

HighJump Warehouse Advantage Functional Description 195

 Inventory Adjustment—Select Item
• The system prompts the user to enter or scan the item in the location to be adjusted.
• If the user selects the F8: List option, the system displays the inventory quantum’s based on
previously selected data.
− The user selects the F4: Prev and F8: Next options to navigate through the list of
items/lots/expiration dates.
− The user selects the F6: Edit option to adjust the selected item/lot/expiration from the list. If
the user selects this option, the system proceeds to Inventory Adjustment—Enter Quantity.
• The system proceeds to Inventory Adjustment—Enter Lot Number.

Inventory Adjustment—Enter Lot Number

• If the item is configured for full lot control, the system prompts the user to scan a lot number. The
system uses format validation to validate the lot number.
• The system proceeds to Inventory Adjustment—Enter Expiration Date.

Inventory Adjustment—Enter Expiration Date

• If the item is expiration date-controlled, the system prompts the user to enter the expiration date.
The valid date format is MMDDYYYY.
• The system proceeds to Inventory Adjustment—Check for New Item.

Inventory Adjustment—Check for New Item

• If the item/lot/expiration date does not match an item that is already associated to the MLP, LP or
location, the system prompts the user to confirm the item being adjusted is new.
− If the user confirms that the item is not new by selecting ‘N’, the system proceeds to Inventory
Adjustment—Select Item.
− If the user confirms that the item is new by selecting ‘Y’, the system proceeds to Inventory
Adjustment—Enter Quantity.

Inventory Adjustment—Enter Quantity

• The system displays the full list of the UOMs for the item. The system prompts the user to enter
quantities for multiple UOMs from that list, and the aggregated quantity for each UOM displays.
• The system prompts for quantity using the Universal Quantity Behavior Type–Count.
• If the item is configured for full serial control, the system prompts the user for serial numbers. For
information about serial numbers, see Serial Number Processing for Inventory Adjustment.

Inventory Adjustment—Enter Reason Code

• The system prompts the user to enter or select a reason code. The reason code must meet the
following criteria:
− The reason code type must be “Inventory Adjustment.”
− The reason code action must be set to adjust inventory.

196 HighJump Warehouse Advantage Functional Description

 • The user can select from the following values.
− 07–Cycle Count
− 08–Damaged
− 09–Quality Control
• If the expected reason code does not exist or the user does not enter a reason code, the
transaction is not complete and the system displays the “Reason Not Found” error message.
• The system determines the delta quantity between the existing quantity and the collected quantity
of the quantum. The delta quantity will either be zero, negative, or positive.
• The system does not update the inventory status.
− When the user creates new inventory items, the system sets the status to “Available” unless
there is a recall on the item.
• The system updates the inventory by adjusting the quantum in the specified location.
• The system generates an inventory adjustment transaction for the quantum.
• The transaction completes and the system proceeds to Inventory Adjustment—Select Location,
MLP, or LP.

Serial Number Processing for Inventory Adjustment

• The system prompts the user for serial numbers when the item is configured for full serial control
and one of the following is true:
− The collected quantity does not match the existing number of serial numbers for that
quantum.
− The collected quantity does not match the existing quantity in the system for that quantum.
• If the serial number does not exist in the warehouse, the system prompts the user to confirm the
serial number. The system allows the user to add the serial number to that location.
• If the serial number entered exists in a different quantum, the system prompts the user to confirm
the serial number and whether it should be moved to the new quantum.

Note
The system does not allow movement of a serial number to a different quantum that is
associated with the following.
- a different order.
- a different shipment.
- a different hold status, or all hold codes do not match.

− If the move is allowed, the system generates an 855 Serial Number Transfer transaction.
− If a serial number is moved to another quantum, a location cycle count is scheduled for the
location of the original quantum of inventory (even if the original quantum and destination
quantum are in the same location). The original quantum of inventory is placed in
“Unavailable” status. The original quantum is temporarily without a serial number, so the
count of serial numbers will not match the quantum quantity until that cycle count is
completed.

Note
A location count is scheduled for the location of the original quantum only if a cycle count is
not already scheduled for that location.

HighJump Warehouse Advantage Functional Description 197

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates an 851 Inventory Adjustment transaction for updates
to item-controlled locations, as detailed in the HighJump Warehouse Advantage Log Transactions
specification.
• HighJump Warehouse Advantage generates an 852 Inventory Adjustment transaction for updates
to an LP-controlled location, as detailed in the HighJump Warehouse Advantage Log
Transactions specification.
• HighJump Warehouse Advantage generates an 853 Inventory Adjustment transaction for updates
to an MLP-controlled location, as detailed in the HighJump Warehouse Advantage Log
Transactions specification.
• HighJump Warehouse Advantage generates an 855 Serial Number Transfer transaction for any
movement of items to a new location, as detailed in the HighJump Warehouse Advantage Log
Transactions specification.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

Scrap
The Scrap process manages the removal (scrapping) of a specific item/lot quantity from an inventory
location.

Based on a user-specified location, item and lot the user identifies the quantity to be systematically
removed from the location in parallel with physically removing the product from the location. The
system subtracts the quantity from the location, and generates a scrap transaction.

Process Details

The following process details apply.

Scrap—Select Location
• The user is prompted to scan the location containing the item or items to be removed from the
system (scrapped). The user must identify the location by entering or scanning a valid location
identifier or valid short location identifier. The system verifies the location corresponds to a non-
equipment location.
• The user is prompted to scan the item number associated with the product to be scrapped. The
item number associated with the product to be scrapped must be identified by entering or
scanning a valid item number or a valid alternative item number or UPC number associated to the
item number.
• The system verifies that the identified item exists in the specified location.

198 HighJump Warehouse Advantage Functional Description

 • The user is prompted for a lot number when the item is configured for full, outbound trace, or
trace in/out lot control. When prompted, the lot number is required. If the item is configured for full
lot control the system validates the lot number.
• The quantity of the item/lot to be subtracted from the location is entered in the displayed unit of
measure.
• The system prompts for quantity using the Universal Quantity Behavior Type–Request.
• The system verifies that the total quantity collected is greater than zero, and does not verify the
quantity is less than or equal to the quantity of the item/lot number residing in the location.
• The user is prompted for serial numbers when the item is configured for full, outbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the scrap quantity in the base unit of measure for the item. If the item is configured for
full serial control, scanned serial numbers are validated and must exist in that location.

Note
For full serial control, the user is not prompted for serial numbers if the entire inventory
quantum is destroyed.

• The system updates the inventory by subtracting the item/lot number quantity from the inventory
in the location.
• A scrap transaction is generated for the location/item/lot quantity.
• The system proceeds to Scrap—Select Location.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 544 Inventory Scrap transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item/lot quantity scrapped.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 199

Kitting
Kitting includes the following processes:
• Component Kit Request
• Kit Completion
• Unkitting

For information about the Web pages you can use to view completed kit information, see “Completed
Kits Pages” in HighJump Advantage Dashboard Functional Description.

Component Kit Request

The Component Kit Request process allows the user to request kits to be assembled and creates the
move work queues for the component items to the kitting location.

Process Details

The following process details apply.

• The system prompts the user for the Kit ID to be assembled, the kitting location for assembly, and
the quantity of the kit to be assembled.
• The system creates Directed Move requests for the components to be moved to the kitting
location. Allocation queue records are generated for all components requested. The system uses
the Bill of Material for the kit to determine the item number and quantity of the kit components to
move.

Note
If a component item is found to be unusable (damaged) after the item is delivered to the
kitting location, the user must use the Move process to manually move replacement material
to the kitting location.

Interface Requirements

The following interface requirements apply.

• The host system provides valid bill of materials master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 270 Kit Request transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item quantity requested.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

200 HighJump Warehouse Advantage Functional Description

Kit Completion
The Kit Completion process allows the user to specify the number of kits completed in the assembly
process. The kit components are decremented from inventory and the kit item inventory is
incremented.

Process Details

The following process details apply.

• The system prompts the user for the kit item that is completed.
• The user is prompted for a lot number when the kit item is configured for full, inbound trace, or
trace in/out lot control. When prompted, the lot number is required but not validated. When
configured for full lot control, the specified lot number is maintained permanently within HighJump
Warehouse Advantage inventory.
• The system prompts for quantity of completed kits using the Universal Quantity Behavior Type–
Request.
• The user is prompted for serial numbers when the kit item is configured for full, inbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the quantity of completed kits in the base unit of measure for the item. Scanned serial
numbers are validated and must be unique for the item in the warehouse. When configured for
full serial control, the serial numbers are maintained permanently within HighJump Warehouse
Advantage inventory.
• The system prompts for the assembly kit location.
• If the assembly location contains more than one item/lot number combination for a component
item, or the component item is configured for outbound trace, or trace in/out serial control, the
user is prompted for the component items.
− The user is prompted for a lot number when the component item is configured for full,
outbound trace, or trace in/out lot control. When prompted, the lot number is required. If the
item is configured for full lot control the system validates the lot number.
− The system prompts for component item decrement quantity using the Universal Quantity
Behavior Type–Default Quantity.
− The user is prompted for serial numbers when the component item is configured for full,
outbound trace, or trace in/out serial control. When prompted, the user scans each serial
number in an “X of Y” method for the quantity in the base unit of measure for the item. If the
item is configured for full serial control, scanned serial numbers are validated and must exist
in that location.

Note
For full serial control, the user is not prompted for serial numbers if the entire inventory
quantum is destroyed.

• If the assembly location does not contain more than one item/lot number combination for a
component item and the component item is not configured for outbound trace or trace in/out serial
control, the system uses the Bill of Materials for the kit item to determine the item numbers and
quantity of the component items consumed.
• The system decrements the component items from inventory in the kitting location and
increments the kit item inventory on the user’s equipment.

HighJump Warehouse Advantage Functional Description 201

 • The user selects the F3: Done option to initiate the Directed Put-Away process to move the kit
inventory to an inventory location.

Interface Requirements

The following interface requirements apply.

• The host system provides valid bill of materials master and detail data through the HighJump
Advantage Link layer. See the relevant Advantage Link application guide for details (for example,
HighJump Advantage Link for Flat File Guide).
• HighJump Warehouse Advantage generates 272 Kit Completion (Remove Component)
transactions as detailed in the HighJump Warehouse Advantage Log Transactions specification.
• HighJump Warehouse Advantage generates 273 Kit Completion (Create Kit) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification.
• HighJump Warehouse Advantage generates 274 Kit Completion (Put Kit) transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

Unkitting
The Unkitting process allows kits to be broken down and placed into inventory as the component
items. The kit item inventory is decremented from inventory and the kit components are incremented.

Note
The kits must reside in a kitting location to perform this function. Kits can be moved from
inventory to a kitting location using the Directed Move feature.

Process Details

The following process details apply.

• The system prompts the user for the kitting location and kit item number.
• The user is prompted for a lot number when the kit item is configured for full, outbound trace, or
trace in/out lot control. When prompted, the lot number is required. If the item is configured for full
lot control the system validates the lot number.
• The system prompts for quantity to unkit using the Universal Quantity Behavior Type–Request.
• The user is prompted for serial numbers when the kit item is configured for full, outbound trace, or
trace in/out serial control. When prompted, the user scans each serial number in an “X of Y”
method for the quantity in the base unit of measure for the item. If the item is configured for full
serial control, scanned serial numbers are validated and must exist in that location.

Note
For full serial control, the user is not prompted for serial numbers if the entire inventory
quantum is destroyed.

202 HighJump Warehouse Advantage Functional Description

 • If the kit components are not lot-controlled or serial-controlled, the system uses the Bill of Material
for the kit to determine the item number and quantity of the kit components to return to inventory.
If they are, the user is prompted for the component items.
− The user is prompted for a lot number when the component item is configured for full,
inbound trace, or trace in/out lot control. When prompted, the lot number is required but not
validated. When configured for full lot control, the specified lot number is maintained
permanently within HighJump Warehouse Advantage inventory.
− The system prompts for quantity.
− The user is prompted for serial numbers when the component item is configured for full,
inbound trace, or trace in/out serial control. When prompted, the user scans each serial
number in an “X of Y” method for the quantity in the base unit of measure for the item.
Scanned serial numbers are validated and must be unique for the item in the warehouse.
When configured for full serial control, the serial numbers are maintained permanently within
HighJump Warehouse Advantage inventory.
• The system decrements the completed kits from inventory in the kit location and increments the
kit component item inventory on the user’s equipment.

Note
If the inventory being created has an open recall against it, the system warns the operator
that the inventory has been recalled and puts it on hold. Where multiple holds are not allowed
and multiple recalls exist, the system uses the hold code from the oldest recall.

• The user selects the F3: Done option to initiate the Directed Put-Away process to move the
inventory from the equipment to an inventory location.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 275 Unkitting (Create Component) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification.
• HighJump Warehouse Advantage generates 276 Unkitting (Remove Kit) transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification.
• HighJump Warehouse Advantage generates 277 Unkitting (Put Component) transactions as
detailed in the HighJump Warehouse Advantage Log Transactions specification.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 203

Administrative
Administrative includes the following processes:
• Cycle Count
• Cycle Count Check
• On Demand Cycle Count
• Cycle Count Scheduling
• Opportunistic Cycle Counting
• Physical
• Location Status
• RF Messaging

Cycle Count
The Cycle Count process manages the directed counting of all of the master license plates (MLPs),
license plates (LPs), and items in a specific location within the warehouse. Based on a system-
directed location and pick flow and priority, the system directs the user to perform a count of each
location.

After all of the known items, LPs, and MLPs, or item/lot number/expiration date combinations are
counted, the system prompts the user to count additional items or item/lot number/expiration date
combinations residing in the location. After all of the MLPs/LPs/items are counted, the system moves
the uncounted inventory to a lost location.

Note
If the inventory being created has an open recall against it, the system warns the operator
that the inventory has been recalled and puts it on hold. Where multiple holds are not allowed
and multiple recalls exist, the system uses the hold code from the oldest recall.

Based on the collected quantity, the system determines the delta quantity between the existing
quantity and the collected quantity. The system generates the appropriate cycle count transactions.

Process Details

The following process details apply.

Cycle Count—Enter Zone

• The system determines if the warehouse control option PROMPT_ZONE_CC is enabled.
• If the warehouse control option is enabled, the user is prompted to scan or enter the zone they
want to count.
• The system proceeds to Cycle Count—Enter Starting Location.

Cycle Count—Enter Starting Location

• The system determines if the warehouse control option PROMPT_START_LOC_CC is enabled.

204 HighJump Warehouse Advantage Functional Description

 • If the warehouse control option is enabled, the user is prompted to scan or enter the location
where they want to start looking for cycle count work. The location must be within the zone
previously entered.
• The system proceeds to Cycle Count—Find Next Work Queue.

Cycle Count—Find Next Work Queue

• The system determines if there is a Cycle Count work queue task meeting the following criteria:
− The work queue is not complete and not on hold.
− The number of workers assigned is less than the number of workers required.
− The work queue is assigned to the user or the work queue has not been assigned to any
user.
• If no open Cycle Count work queue is found and the warehouse control option ON_DEMAND_CC
is enabled, the system prompts the user to scan any location.
• If no open Cycle Count work queue is found and the warehouse control option ON_DEMAND_CC
is disabled, the system displays No Work Available.
• The system assigns work based on priority and pick flow depending on the threshold. Threshold
can be set by using the Interleave web pages in HighJump Warehouse Advantage base web.
− If the priority is higher than the threshold, work is assigned by priority and the pick flow is
ignored. The threshold is set to 30 by default.
− If a location is requested for cycle count multiple times, the priority for that location increases.
− If the threshold is below the specified or default threshold, then work is assigned based on
pick flow.

Cycle Count—Confirm Location

• The system prompts the user to scan the location associated to the Cycle Count work queue. The
location must be identified by entering or scanning the suggested location or any location if the
warehouse control option ON_DEMAND_CC is enabled.
• The user can select from the following options:
− Enter or scan the location suggested by the system.
− Override the location and provide a new location to count if the warehouse control option
ON_DEMAND_CC is enabled. For example, if the user finds a location (that may require
counting) on the way to the suggested location, the user can override the suggested location.
• The system determines if the location is an MLP/LP or item-controlled location.
− If the location is MLP-controlled, the system proceeds to Cycle Count—MLP.
− If the location is LP-controlled, the system proceeds to Cycle Count—LP.
− If the location is item-controlled, the system proceeds to Cycle Count—Item.

Cycle Count—MLP
• The system determines the value of the warehouse control option LP_UNIT_CNT_ENABLED.
− If the warehouse control option is disabled, the system proceeds to Cycle Count—Enter MLP.
− If the warehouse control option is enabled, the system proceeds to Cycle Count—Count
MLP.

HighJump Warehouse Advantage Functional Description 205

 Cycle Count—Count MLP
• The system prompts the user to enter the total number of MLPs in the location.
− If the quantity entered matches the system quantity, the system assumes that all MLPs, LPs,
and items are correct and logs the transaction. The system proceeds to Cycle Count—Find
Next Work Queue.
− If the quantity entered does not match the system quantity, the system forces the user to
count the entire location. The system proceeds to Cycle Count—Enter MLP.

Cycle Count—Enter MLP

• The system prompts the user to enter or scan the MLP in the location.
• If the MLP does not exist, the system proceeds to Cycle Count—Create MLP.
• If the MLP does not exist in the count location, the system proceeds to Cycle Count—Move
MLP/LP.
• The system displays the expected number and total quantity entered or scanned.
• The user must identify the MLP to be counted by entering or scanning the barcode.
− If the warehouse control option LP_UNIT_CNT_ENABLED is disabled, the system proceeds
to Cycle Count—LP.
− If the user selects the F3: Done option, the system proceeds to Cycle Count—Uncounted.
− If the user enters or scans an MLP associated to a different location, the system moves the
MLP, LPs, and items to the count location and a logs a transaction.

Cycle Count—Create MLP

• If the user enters an MLP that does not exist, the system uses format validation to validate the
entry. The system prompts for confirmation and the user must enter Y or N.
− The system proceeds to Cycle Count—LP.

Cycle Count—LP
• The system determines the value of the warehouse control option LP_UNIT_CNT_ENABLED.
− If the warehouse control option is enabled, system proceeds to Cycle Count—Count LP.
− If the warehouse control option is disabled, system proceeds to Cycle Count—Enter LP.

Cycle Count—Count LP
• The system prompts the user to enter the total number of LPs in the location.
− If the quantity entered matches the system quantity, the system assumes that all LPs and
items are correct and logs the transaction. The system proceeds to Cycle Count—Find Next
Work Queue.
− If the quantity entered does not match the system quantity, the system forces the user to
count the entire location. The system proceeds to Cycle Count—Enter LP.

Cycle Count—Enter LP
• The system prompts the user to enter or scan the LP in the location or associated to the MLP.
• If the LP does not exist, the system proceeds to Cycle Count—Create LP.

206 HighJump Warehouse Advantage Functional Description

 • If the LP does not exist in the count location, the system proceeds to Cycle Count—Move
MLP/LP.
• The system displays the expected number and total quantity entered or scanned.
• The user must identify the LP to be counted by entering or scanning the barcode.
− If the warehouse control option LP_UNIT_CNT_ENABLED is disabled, or the count LP
process failed, the system proceeds to Cycle Count—Enter LP.
− If the user selects the F3: Done option and the location is LP-controlled, the system proceeds
to Cycle Count—Uncounted.
− If the user selects the F3: Done option and the location is MLP-controlled, the system
proceeds to Cycle Count—Enter MLP.
− If the user enters or scans an LP associated to a different location, the system moves the LP
to the count location and a logs a transaction.

Cycle Count—Create LP
• If the user enters an LP that does not exist, the system uses format validation to validate the
entry. The system prompts for confirmation and the user must enter Y or N.
− If the warehouse control option LP_UNIT_CNT_ENABLED is disabled, or the count LP
process failed, the system proceeds to Cycle Count—Enter Item.

Cycle Count—Item
• The system determines the value of the warehouse control option ITM_UNIT_CNT_ENABLED.
− If the warehouse control option is disabled, the system proceeds to Cycle Count—Enter Item.
− If the warehouse control option is enabled, the system proceeds to Cycle Count—Count Item.

Cycle Count—Enter Item

• The system finds the next item associated to the MLP/LP/location. The prompting order of the
items is by FIFO date and then item number.
• The system prompts the user to scan the next item.
• If no additional items are associated to the MLP/LP/location, the system prompts the user to scan
any additional items.
• The user may override the suggested item and scan any item associated to the MLP/LP/location.
• The user must identify the item to be counted by entering or scanning the barcode.
− If the warehouse control option ITM_UNIT_CNT_ENABLED is enabled, the system proceeds
to Cycle Count—Count Item.
− If the warehouse control option ITM_UNIT_CNT_ENABLED is disabled or the count item
process failed, the system proceeds to Cycle Count—Enter Lot.
− If the user selects the F3: Done option and the location is MLP or LP-controlled, the system
proceeds to Cycle Count—Enter LP.
− If the user selects the F3: Done option and the location is item-controlled, the system
proceeds to Cycle Count—Uncounted.
− If the user selects the F8: Del Item option and the location is item-controlled, the system
proceeds to Cycle Count—Remove Item.

HighJump Warehouse Advantage Functional Description 207

 Cycle Count—Count Item
• The system prompts the user to enter the total number of items associated to the
MLP/LP/Location.
− If the quantity entered matches the system quantity, the system assumes that all lots and
expiration dates of the items are correct and logs the transaction. The system proceeds to
Cycle Count—Enter Item.
− If the quantity entered does not match the system quantity, the system forces the user to
count the entire location. The system proceeds to Cycle Count—Enter Item.

Note
The system requires a full recount of the item. The user can complete the recount at the end
of the cycle count process or initiate it immediately by scanning the same item during the
enter item process.

Cycle Count—Enter Lot

• If the item is configured for full lot control, the system prompts the user to scan a lot number.
• The system proceeds to Cycle Count—Enter Expiration Date.

Cycle Count—Enter Expiration Date

• If the item is configured for expiration date control, the system prompts the user to scan an
expiration date.
• The system proceeds to Cycle Count—Enter Quantity.

Cycle Count—Enter Quantity

• The system prompts for quantity using the Universal Quantity Behavior Type–Count.
• The system prompts the user to enter the quantity of items being counted. The user can add
multiple quantities for an item associated to multiple UOMs.
• The system determines if the total quantity entered matches the previous count or the system
value.
− If the total quantity entered matches the previous count, the system proceeds to Cycle
Count—Update Inventory.
− If the total quantity entered does not match the previous count, the system sets the value of
the previous count to be equal to the total quantity collected and proceeds to Cycle Count—
Enter Quantity for a recount.
• If the item is configured for full serial control, the system prompts the user for serial numbers. For
more information, see Serial Number Processing for Cycle Count.

Cycle Count—Update Inventory

• The system determines the delta quantity between the existing quantity of the location and the
collected quantity. The delta quantity is either zero, negative, or positive.

208 HighJump Warehouse Advantage Functional Description

 • The system performs the following updates to inventory:
− Updates the inventory by adding the item/lot number/expiration date delta quantity to the
inventory in the location.
− Updates the inventory in the lost location by subtracting the item/lot number/expiration date
delta quantity to the inventory in the location.
• The system updates the inventory status to "Available" if the current status is "Available" or
"Unavailable". The system will not update the inventory status if the status is "On-Hold".
• The system generates a cycle count transaction for the delta quantity.
• If the delta quantity is non-zero, the system creates a Cycle Count work queue for the locations
that contain the item. Locations marked with the NEVER_COUNT and NEVER_AUTO classes
are not counted.

Cycle Count—Uncounted
• The system performs the following for each MLP/LP/item/lot/expiration:
− Sets the collected quantity to zero.
− Determines the delta quantity between the existing quantity of the item/lot number/expiration
date associated to the location and the collected quantity (the delta quantity is negative).
− Performs the following updates to inventory:
• Updates the inventory by adding the item/lot number/expiration date delta quantity to the
inventory in the location.
• Updates the inventory in the lost location by subtracting the item/lot number/expiration
date delta quantity to the inventory in the location.
• The system updates the inventory status to "Available" if the current status is "Available" or
"Unavailable". The system will not update the inventory status if the status is "On-Hold".
• The system generates a cycle count transaction for the delta quantity.
− If the inventory being updated is in an item-controlled location, the system creates a Cycle
Count work queue for all locations that have the item/lot/expiration date and have not been
picked. Locations marked with the NEVER_COUNT or NEVER_AUTO classes are not
counted.
• The system proceeds to Cycle Count—Close Work Queue.

Cycle Count—Delete Item

• The system performs the following for each lot/expiration date associated to the item:
− Sets the collected quantity to zero.
− Determines the delta quantity between the existing quantity of the lot number/expiration date
associated to the location and the collected quantity (the delta quantity is negative).
− Performs the following updates to inventory:
• Updates the inventory by adding the item/lot number/expiration date delta quantity to the
inventory in the location.
• Updates the inventory in the lost location by subtracting the item/lot number/expiration
date delta quantity to the inventory in the location.

HighJump Warehouse Advantage Functional Description 209

 • The system updates the inventory status to "Available" if the current status is "Available" or
"Unavailable". The system will not update the inventory status if the status is "On-Hold".
• The system generates a cycle count transaction for the delta quantity.
− If the inventory being updated is in an item-controlled location, the system creates a Cycle
Count work queue for all locations that have the item/lot/expiration date and have not been
picked. Locations marked with the NEVER_COUNT or NEVER_AUTO classes are not
counted.
• The system proceeds to Cycle Count—Item.

Cycle Count—Close Work Queue

• The system updates the work queue to "complete" and decrements the number of workers
assigned to the work queue.
• The system proceeds to Cycle Count—Find Next Work Queue.

Cycle Count—Move MLP/LP

• The system performs the following for each item/lot number quantity associated to the MLP/LP:
− Sets the collected quantity to the quantity associated to the item/lot/expiration date.
− Determines the delta quantity between the existing quantity and the collected quantity (the
delta quantity is zero.)
− Updates the inventory by subtracting the item/lot/expiration date quantity from the MLPs/LPs
in the current location and adding the item/lot/expiration date quantity to the location being
counted.
− Generates a cycle count work queue for the location where the MLP/LP was previously
located.
• The system updates the MLP/LP location to the location being counted.
• The system increments the number of MLPs/LPs associated to the location.
• The system generates a cycle count transaction for the MLP/LP/item/lot/expiration date delta
quantity.
• If the user previously scanned an MLP and the warehouse control option
LP_ITM_CNT_ENABLED is enabled, the system proceeds to Cycle Count—MLP.
• If the user previously scanned an MLP and the warehouse control option
LP_ITM_CNT_ENABLED is disabled, the system proceeds to Cycle Count—LP.
• If the user previously scanned an LP and the warehouse control option LP_ITM_CNT_ENABLED
is enabled, the system proceeds to Cycle Count—LP.
• If the user previously scanned an LP and the warehouse control option LP_ITM_CNT_ENABLED
is disabled, the system proceeds to Cycle Count—Item.

210 HighJump Warehouse Advantage Functional Description

 Serial Number Processing for Cycle Count

The following applies to the Cycle Count process.

• The system prompts the user for serial numbers when the item is configured for full serial control
and one of the following is true:
− The collected quantity does not match the existing number of serial numbers for that
quantum.
− The collected quantity does not match the existing quantity in the system for that quantum.
• If the serial number does not exist anywhere in the warehouse, the system prompts the user to
confirm the serial number. The system allows the user to add the serial number to that location.
• If the serial number entered exists in a different quantum, the system prompts the user to confirm
the serial number and whether it should be moved to the new quantum.

Note
The system does not allow movement of a serial number to a different quantum that is
associated with the following.
- a different order.
- a different shipment.
- a different hold status, or all hold codes do not match.

− If the move is allowed, the system generates an 855 Serial Number Transfer transaction.
− If a serial number is moved to another quantum, a location cycle count is scheduled for the
location of the original quantum of inventory (even if the original quantum and destination
quantum are in the same location). The original quantum of inventory is placed in Unavailable
status. The original quantum is temporarily without a serial number, so the count of serial
numbers will not match the quantum quantity until that cycle count is completed.

Note
A location count is scheduled for the location of the original quantum only if a cycle count is
not already scheduled for that location.

• If the quantity entered by the user is same as the inventory quantity, the system generates an 800
log transaction.
• If the quantity entered by the user is different from the inventory quantity, the system updates the
inventory record and creates a Cycle Count work queue The system also generates an 801 log
transaction.
• If an MLP or LP is moved to the count location, the system generates an 802 log transaction.
• In both cases where the inventory quantity is same/different from the entered quantity, the system
creates a hold record if recalled inventory was adjusted.

HighJump Warehouse Advantage Functional Description 211

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 800 Cycle Count Transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for counts that match the system expected inventory.
• HighJump Warehouse Advantage generates 801 Cycle Count Change transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for inventory adjustment made to the location due to cycle count.
• HighJump Warehouse Advantage generates 802 Cycle Count Move transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for inventory movements to the location when there is a mismatch in counts.
• HighJump Warehouse Advantage generates 855 Serial Number Transfer transactions when the
item is configured for full serial control as detailed in the HighJump Warehouse Advantage Log
Transactions specification. The transactions are generated only when serial numbers are moved
from one location to another.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

Cycle Count Check

The Cycle Count Check process manages the directed counting of all of the master license plates
(MLPs), license plates (LPs), and items in a specific location within the warehouse. Based on a
system-directed location and pick flow and priority, the system directs the user to perform a count of
each location.

After all of the known items, LPs, and MLPs, or item/lot number/expiration date combinations are
counted, the system prompts the user to count additional items or item/lot number/expiration date
combinations in the location. If the counted quantity of MLPs, LPs, or items does not match the
expected quantity, the system generates a Cycle Count work queue for the location. The cycle count
check process does not update inventory.

Note
If the inventory being created has an open recall against it, the system warns the operator
that the inventory has been recalled and puts it on hold. Where multiple holds are not allowed
and multiple recalls exist, the system uses the hold code from the oldest recall.

Based on the collected quantity, the system determines the delta quantity between the existing
quantity and the collected quantity. The system generates the appropriate cycle count check
transactions.

212 HighJump Warehouse Advantage Functional Description

Process Details

The following process details apply.

Cycle Count Check—Enter Zone

• The system determines if the warehouse control option PROMPT_ZONE_CC is enabled.
• If the warehouse control option is enabled, the user is prompted to scan or enter the zone they
want to count.
• The system proceeds to Cycle Count Check—Enter Starting Location.

Cycle Count Check—Enter Starting Location

• The system determines if the warehouse control option PROMPT_START_LOC_CC is enabled.
• If the warehouse control option is enabled, the user is prompted to scan or enter the location
where they want to find cycle count check work. The location must be within the zone previously
entered.
• The system proceeds to Cycle Count Check—Find Next Work Queue.

Cycle Count Check—Find Next Work Queue

• The system determines if there is a Cycle Count Check work queue task meeting the following
criteria:
− The work queue is not complete and not on hold.
− The number of workers assigned is less than the number of workers required.
− The work queue is assigned to the user or the work queue has not been assigned to any
user.
• If no open Cycle Count Check work queue is found and the warehouse control option
ON_DEMAND_CC is enabled, the system prompts the user to scan any location.
• If no open Cycle Count Check work queue is found and the warehouse control option
ON_DEMAND_CC is disabled, the system displays “No Work Available” on the device.
• The system assigns work based on priority and pick flow depending on the threshold. Threshold
can be set by using the Interleave web pages in HighJump Warehouse Advantage base web.
− If the priority is higher than the threshold, work is assigned based on priority and the pick flow
is ignored. The threshold is set to 30 by default.
− If a location is requested for cycle count check multiple times, the priority for that location
increases.
− If the threshold is below the specified or default threshold, then work is assigned based on
pick flow.

Cycle Count Check—Confirm Location

• The system prompts the user to scan the location associated to the Cycle Count Check work
queue. The location must be identified by entering or scanning the suggested location or any
location if the warehouse control option ON_DEMAND_CC is enabled.
• The user can select from the following options:
− Enter or scan the location suggested by the system.

HighJump Warehouse Advantage Functional Description 213

 − Override the location and provide a new location to count if the warehouse control option
ON_DEMAND_CC is enabled. For example, if the user finds a location that may require
counting on the way to the suggested location, the user can override the suggested location.
• The system determines if the location is an MLP/LP or item-controlled location.
− If the location is MLP-controlled, the system proceeds to Cycle Count Check—MLP.
− If the location is LP-controlled, the system proceeds to Cycle Count Check—LP.
− If the location is item-controlled, the system proceeds to Cycle Count Check—Item.

Cycle Count Check—MLP

• The system determines the value of the warehouse control option LP_UNIT_CNT_ENABLED.
− If the warehouse control option is disabled, the system proceeds to Cycle Count Check—
Enter MLP.
− If the warehouse control option is enabled, the system proceeds to Cycle Count Check—
Count MLP.

Cycle Count Check—Count MLP

• The system prompts the user to enter the total number of MLPs in the location.
− If the quantity entered matches the system quantity, the system assumes that all MLPs, LPs,
and items are correct and logs the transaction. The system proceeds to Cycle Count Check—
Find Next Work Queue.
− If the quantity entered does not match the system quantity, the system forces the user to
count the entire location. The system proceeds to Cycle Count Check—Enter MLP.

Cycle Count Check—Enter MLP

• The system prompts the user to enter or scan the MLP in the location.
• If the MLP does not exist in the count location, the system proceeds to Cycle Count Check—
Move MLP/LP.
• The system displays the expected number and total quantity entered or scanned.
• The user must identify the MLP to be counted by entering or scanning the barcode.
− If the warehouse control option LP_UNIT_CNT_ENABLED is disabled, the system proceeds
to Cycle Count Check—LP.
− If the warehouse control option LP_UNIT_CNT_ENABLED is enabled, system proceeds to
Cycle Count Check—Enter MLP.
− If the user selects the F3: Done option, the system proceeds to Cycle Count Check—
Uncounted.
− If the user enters or scans an MLP associated to a different location, the system moves the
MLP, LPs, and items to the count location and a logs a transaction.

Cycle Count Check—LP

• The system determines the value of the warehouse control option LP_UNIT_CNT_ENABLED.
− If the warehouse control option is enabled, system proceeds to Cycle Count Check—Count
LP.

214 HighJump Warehouse Advantage Functional Description

 − If the warehouse control option is disabled, system proceeds to Cycle Count Check—Enter
LP.

Cycle Count Check—Count LP

• The system prompts the user to enter the total number of LPs the location.
− If the quantity entered matches the system quantity, the system assumes that all LPs and
items are correct and logs the transaction. The system proceeds to Cycle Count Check—Find
Next Work Queue.
− If the quantity entered does not match the system quantity, the system forces the user to
count the entire location. The system proceeds to Cycle Count Check—Enter LP.

Cycle Count Check—Enter LP

• The system prompts the user to enter or scan the LP in the location or associated to the MLP.
• If the LP does not exist in the count location, the system proceeds to Cycle Count Check—Move
MLP/LP.
• The system displays the expected number and total quantity entered or scanned.
• The user must identify the LP to be counted by entering or scanning the barcode.
− If the warehouse control option LP_UNIT_CNT_ENABLED is enabled, the system proceeds
to Cycle Count Check—Enter LP.
− If the warehouse control option LP_UNIT_CNT_ENABLED is disabled or the count LP
process failed, the system proceeds to Cycle Count Check—Enter Item.
− If the user selects the F3: Done option and the location is LP-controlled, the system proceeds
to Cycle Count Check—Uncounted.
− If the user selects the F3: Done option and the location is MLP-controlled, the system
proceeds to Cycle Count Check—Enter MLP.
− If the user enters or scans an LP associated to a different location, the system generates a
Cycle Count work queue and a logs a transaction.

Cycle Count Check—Item

• The system determines the value of the warehouse control option ITM_UNIT_CNT_ENABLED.
− If the warehouse control option is disabled, the system proceeds to Cycle Count Check—
Enter Item.
− If the warehouse control option is enabled, the system proceeds to Cycle Count Check—
Count Item.

Cycle Count Check—Enter Item

• The system finds the next item associated to the MLP/LP/location. The prompting order of the
items is by FIFO date and then item number.
• The system prompts the user to scan the next item.
• If no additional items are associated to the MLP/LP/location, the system prompts the user to scan
any additional items.
• The user may override the suggested item and scan any item associated to the MLP/LP/location.
• The user must identify the item to be counted by entering or scanning the barcode.

HighJump Warehouse Advantage Functional Description 215

 − If the warehouse control option LP_UNIT_CNT_ENABLED is enabled, the system proceeds
to Cycle Count Check—Count Item.
− If the warehouse control option LP_UNIT_CNT_ENABLED is disabled or the count item
process failed, the system proceeds to Cycle Count Check—Enter Lot.
− If the user selects the F3: Done option and the location is MLP or LP-controlled, the system
proceeds to Cycle Count Check—Enter LP.
− If the user selects the F3: Done option and the location is item-controlled, the system
proceeds to Cycle Count Check—Uncounted.
− If the user selects the F8: Del Item option and the location is item-controlled, the system
proceeds to Cycle Count Check—Remove Item.

Cycle Count Check—Count Item

• The system prompts the user to enter the total number of items associated to the
MLP/LP/location.
− If the quantity entered matches the system quantity, the system assumes that all lots and
expiration dates of the items are correct and logs the transaction. The system proceeds to
Cycle Count Check—Enter Item.
− If the quantity entered does not match the system quantity, the system forces the user to
count the entire location. The system proceeds to Cycle Count Check—Enter Item.

Note
The system requires a full recount of the item. The user can complete the recount at the end
of the cycle count process or initiate it immediately by scanning the same item during the
enter item process.

Cycle Count Check—Enter Lot

• If the item is configured for full lot control, the system prompts the user to scan a lot number.
• The system proceeds to Cycle Count Check—Enter Expiration Date.

Cycle Count Check—Enter Expiration Date

• If the item is configured for expiration date control, the system prompts the user to scan an
expiration date.
• The system proceeds to Cycle Count Check—Enter Quantity.

Cycle Count Check—Enter Quantity

• The system prompts for quantity using the Universal Quantity Behavior Type–Count.
• The system prompts the user to enter the quantity of items being counted. The user can add
multiple quantities for an item associated to multiple UOMs.
• The system determines if the total quantity entered matches the previous count or the system
value.
− If the total quantity entered matches the previous count, the system proceeds to Cycle Count
Check—Update Inventory.
− If the total quantity entered does not match the previous count, the system sets the value of
the previous count to be equal to the total quantity collected and proceeds to Cycle Count
Check—Enter Quantity for a recount.

216 HighJump Warehouse Advantage Functional Description

 • If the item is configured for full serial control, the system prompts the user for serial numbers. For
more information, see Serial Number Processing for Cycle Count Check.

Cycle Count Check—Update Inventory

• The system determines the delta quantity between the existing quantity of the location and the
collected quantity. The delta quantity is either zero, negative, or positive.
− If the delta quantity is not zero, the system generates a Cycle Count work queue for the
location being counted.
• The system generates a cycle count check transaction.

Cycle Count Check—Uncounted

• The system performs the following for each MLP/LP/item/lot/expiration:
− Sets the collected quantity to zero.
− Determines the delta quantity between the existing quantity of the item/lot number/expiration
date associated to the location and the collected quantity (the delta quantity is negative).
• If the delta quantity is not zero, the system generates a Cycle Count work queue for the
location being counted.
• The system generates a cycle count transaction for the delta quantity.
− If the inventory being updated is in an item-controlled location, the system creates a Cycle
Count work queue for the location being counted. Locations marked with the
NEVER_COUNT or NEVER_AUTO classes are not counted.
• The system proceeds to Cycle Count Check—Close Work Queue.

Cycle Count—Delete Item

• The system performs the following for each lot/expiration date associated to the item:
− Sets the collected quantity to zero.
− Determines the delta quantity between the existing quantity of the lot number/expiration date
associated to the location and the collected quantity (the delta quantity is negative).
• If the delta quantity is not zero, the system generates a Cycle Count work queue for the
location being counted.
• The system generates a cycle count transaction for the delta quantity.
− If the inventory being updated is in an item-controlled location, the system creates a Cycle
Count work queue for the location being counted. Locations marked with the
NEVER_COUNT or NEVER_AUTO classes are not counted.
• The system proceeds to Cycle Count Check—Item.

Cycle Count Check—Close Work Queue

• The system updates the work queue to "complete" and decrements the number of workers
assigned to the work queue.
• The system proceeds to Cycle Count Check—Find Next Work Queue.

HighJump Warehouse Advantage Functional Description 217

 Cycle Count Check—Move MLP/LP
• The system performs the following for each item/lot number quantity associated to the MLP/LP:
− Sets the collected quantity to the quantity associated to the item/lot/expiration date.
− Determines the delta quantity between the existing quantity and the collected quantity (the
delta quantity is zero.)
• If the delta quantity is not zero, the system generates a Cycle Count work queue for the
source location and the location being counted.
• The system updates the MLP/LP location to the location being counted.
• The system increments the number of MLPs/LPs associated to the location.
• The system generates a cycle count transaction for the MLP/LP/item/lot/expiration date delta
quantity.
• If the user previously scanned an MLP and the warehouse control option
LP_ITM_CNT_ENABLED is enabled, the system proceeds to Cycle Count Check—MLP.
• If the user previously scanned an MLP and the warehouse control option
LP_ITM_CNT_ENABLED is disabled, the system proceeds to Cycle Count Check—LP.
• If the user previously scanned an LP and the warehouse control option LP_ITM_CNT_ENABLED
is enabled, the system proceeds to Cycle Count Check—LP.
• If the user previously scanned an LP and the warehouse control option LP_ITM_CNT_ENABLED
is disabled, the system proceeds to Cycle Count Check—Item.

Serial Number Processing for Cycle Count Check

The following applies to the Cycle Count Check process.

• The system prompts the user for serial numbers when the item is configured for full serial control
and one of the following is true:
− The collected quantity does not match the existing number of serial numbers for that
quantum.
− The collected quantity does not match the existing quantity in the system for that quantum.
• If the serial number does not exist anywhere in the warehouse, the system prompts the user to
confirm the serial number. The system allows the user to add the serial number to that location.
• If the serial number entered exists in a different quantum, the system prompts the user to confirm
the serial number and whether it should be moved to the new quantum.

Note
The system does not allow movement of a serial number to a different quantum that is
associated with the following.
- a different order.
- a different shipment.
- a different hold status, or all hold codes do not match.

− If the move is allowed, the system generates an 855 Serial Number Transfer transaction.

218 HighJump Warehouse Advantage Functional Description

 − If a serial number is moved to another quantum, a location cycle count is scheduled for the
location of the original quantum of inventory (even if the original quantum and destination
quantum are in the same location). The original quantum of inventory is placed in Unavailable
status. The original quantum is temporarily without a serial number, so the count of serial
numbers will not match the quantum quantity until that cycle count is completed.

Note
A location count is scheduled for the location of the original quantum only if a cycle count is
not already scheduled for that location.

• If the quantity entered by the user is same as the inventory quantity, the system generates an 810
log transaction.
• If the quantity entered by the user is different from the inventory quantity, the system creates a
Cycle Count work queue. The system also generates an 811 log transaction.
• If an MLP or LP is moved to the count location, the system generates an 812 log transaction.
• In both cases where the inventory quantity is same/different from the entered quantity, the system
creates a hold record if recalled inventory was adjusted.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 810 Cycle Count Transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for counts that match the system expected inventory.
• HighJump Warehouse Advantage generates 811 Cycle Count Change transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for inventory adjustment made to the location due to cycle count.
• HighJump Warehouse Advantage generates 812 Cycle Count Move transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for inventory movements to the location when there is a mismatch in counts.
• HighJump Warehouse Advantage generates 855 Serial Number Transfer transactions when the
item is configured for full serial control as detailed in the HighJump Warehouse Advantage Log
Transactions specification. The transactions are generated only when serial numbers are moved
from one location to another.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 219

On Demand Cycle Count
The On Demand Cycle Count process allows the cycle count process to be "on-demand" by allowing
users to scan any countable location in the warehouse and begin a cycle count. Administrators can
turn the on-demand feature on or off with a control value.

Process Details

The following process details apply.

• The warehouse control option called 'ON_DEMAND_CC' triggers the On Demand Cycle Count
process.
• The warehouse control is active when the next_value is set to 1. When the control is ON, the user
can override the suggested location in the Cycle Count process.
• The user is unassigned from the originally assigned work, and assigned to a work queue for the
location entered. The system generates a new work queue record if no record exists for the
location. Also, if no work is originally found, the system prompts the user to enter any location and
a work queue is generated for the newly entered location.
• If the location is a loose location and the item is not lot-controlled, the user is directed to enter the
next location after the quantity prompt instead of the item again.
• If the location is LP-controlled and the item is not lot-controlled, the user is directed to enter the
next LP after the quantity prompt instead of the item again.

Cycle Count Scheduling

The Cycle Count Scheduling process generates Cycle Count Check or Cycle Counts work queues for
applicable locations for a given frequency. For example, you may have specific warehouse locations
you want cycle counted every 30 days. You can use this process to ensure these locations are cycle
counted for your required frequency.

You create cycle count classes to define the count frequency and assign locations to the cycle count
class. Typically, the Cycle Count Scheduling process is scheduled to run on a daily basis. Based on
the cycle count class frequency and the day in the count cycle, the process determines the locations
that need cycle count check work queues created to ensure all assigned locations are cycle counted
in the count frequency.

For example, assume you have 360 locations assigned to a cycle count class with a 30-day
frequency. If the Generate Count Checks process runs daily, the process creates 12 cycle count
check work queues each day to ensure all assigned locations are cycle counted in the required
frequency.

Before you Begin

Before this process can run, you need to create cycle count classes and define the count frequency.
You can create multiple cycle count classes if you have locations that need to be cycle counted on a
different frequency. After you define the cycle count classes, you assign locations to the cycle count
class. After you configure the classes and locations, you need to schedule the process to run.

220 HighJump Warehouse Advantage Functional Description

 Create Cycle Count Classes

HighJump Warehouse Advantage uses warehouse-level control settings to determine the class of the
cycle count. You can access controls by selecting Warehouse Setup > Warehouse Control in the
HighJump Warehouse Advantage Base Web.

When you create cycle count classes, you need to use the following naming convention: CYC
followed by a number. For example, CYC1 and CYC2.

The following table describes the applicable fields for the warehouse control.
Field Description
Warehouse ID The warehouse ID for which you are scheduling.
Control Type The defined cycle count class identifier using the following naming
convention: CYC and a number. For example, CYC1 and CYC2.
Description The description of the cycle count class. The value you enter in this field
displays as an option in the Cycle Count Class field on the Edit/Add
Location page in the HighJump Warehouse Advantage Base Web.
C1 The work type. Valid values are “Cycle Count” and “Cycle Count
Checks.”
C2 The count frequency type. Valid values are “Fixed Days” and “Fixed
Counts.”
F1 The number of days in the count frequency for the class or total number
of counts generated for the class. For example, 30, 60, or 90 days.

Assign Locations to Cycle Count Classes

Using HighJump Warehouse Advantage Base Web, you need to assign the locations to the cycle
count class.

The following cycle count classes allow specific locations to be left uncounted.
• NEVER_COUNT class indicates the location has never had a cycle count generated, either
manually or using a web page.
• NEVER_AUTO class indicates that cycle counts are not generated for a location; however, a user
can use the web page to schedule a cycle count, or perform an On Demand Cycle Count at the
location.

Complete the following procedures for every location you want to assign to a cycle count class.
1. Select Warehouse Setup > Locations.
2. Enter the search parameters and click Query.
3. Select the edit (#) link of the location you want to assign to the cycle count class.
4. Select the appropriate cycle count class from the Cycle Count Class field.
5. Click Update.

HighJump Warehouse Advantage Functional Description 221

 Scheduling

You need to schedule the “Generate Cycle Count” and “Cycle Count Check” process object in the
Warehouse Advantage application. You can schedule the process objects to run at a time most
convenient for you. You should consider the number of days in the count frequency for cycle count
classes when determining the frequency in which to run the process object.

For more information about scheduling a process object, see the “Executing a Process Object via
Microsoft’s Scheduled Tasks” topic in HighJump Advantage Platform Administrator’s Guide.

Cycle Count Class

The locations to be counted are assigned to a Cycle Count Class. The Cycle Count Class specifies
the number of days or the number of counts for which the locations assigned must be counted. The
automated count scheduling updates the application status console for each Cycle Count Class with
the following fields:
• Cycle Count Class
• Days to generate cycle counts
• Start date of most recent cycle
• Number of locations in Cycle Count Class
• Number of location counts in Cycle Count Class completed this cycle
• Number of location counts in Cycle Count Class generated this cycle but not yet completed
• Number of locations in Cycle Count Class remaining to count this cycle but blocked by location
status
• Number of counts scheduled

The cycle resets when no locations are left to be counted in the class.

Process Details

The process does the following.

1. Gets a list of all of the warehouses.
2. Selects the first or next warehouse in the list.
3. Finds the cycle count class for the locations in the selected warehouse.
4. Determines the frequency of the cycle count class by checking the value in the warehouse control
table.
5. Determines the number of locations for the cycle count class that are not counted for the
warehouse.
a) If the process does not find any locations, it goes to Step 9.
6. Determines the number of locations that need to be counted today.
a) If the process does not find any locations, it goes to Step 9.
7. Randomly selects locations to be counted in the selected warehouse.
8. Creates a cycle count or cycle count check work queue for each selected location.

222 HighJump Warehouse Advantage Functional Description

 9. Determines if there are other cycle count classes for locations in the warehouse.
a) If there are more cycle count classes for the warehouse, the process goes to Step 4.
b) If there are no more cycle count classes for the warehouse, the process goes to Step 2.

Manual Scheduling

Manual scheduling allows the generation of either Cycle Count Check or Cycle Counts work queues.
Counts generated by manual scheduling are created immediately.

The following cycle count classes allow specific locations to be left uncounted.
• NEVER_COUNT class indicates the location has never had a cycle count or cycle count check
generated, either manually or using a web page.
• NEVER_AUTO class indicates that cycle counts are not generated for a location; however, a user
can use the web page to schedule a cycle count, or perform an On Demand Cycle Count at the
location.

HighJump Advantage Dashboard web pages allow the user to perform manual scheduling. For more
information, see “Generate Cycle Counts” in HighJump Advantage Dashboard Functional Description.

Opportunistic Cycle Counting

The Opportunistic Cycle Counting process manages the directed counting of all of the MLPs, LPs and
items in a specific location within the warehouse. The process is identical to the Cycle Count process
with the following exception: Opportunistic Cycle Counting is initiated by the system. While the user is
picking or completing a planned move, if the remaining quantity in the location is less than or equal to
the Next Value, the system completes one of the following actions.
Action If this action is selected, the system…
No Count does not generate a cycle count. No action is taken.
Generate Count generates a cycle count work queue for the location.
Immediate Count directs the user to count the location immediately—before
putting away the picked items on their equipment.

HighJump Warehouse Advantage Base Web Example

The Next Value and actions are defined in HighJump Warehouse Advantage Base Web.

HighJump Warehouse Advantage Functional Description 223

Physical
The Physical process manages the creation and adjustment of specific location/item/lot quantities
associated to inventory.

Based on a user-specified location, the user identifies the quantity associated with each item
number/lot number residing in the location.

The system updates the inventory with the delta quantity (the difference between the existing quantity
and the entered quantity), and generates a physical adjustment transaction.

Note
If the inventory being created has an open recall against it, the system warns the operator
that the inventory has been recalled and puts it on hold. Where multiple holds are not allowed
and multiple recalls exist, the system uses the hold code from the oldest recall.

Process Details

The following process details apply.

Physical—Select Location to Count

• The user is prompted to scan the location containing the item or items to be counted. The user
must identify the location by entering or scanning a valid location identifier or valid short location
identifier. The system verifies the location corresponds to a non-equipment location.
• The system determines if the identified location is equal to the previous location identified. If the
location equals the previous location, the system proceeds to Physical—Select Item to Count.
• The system displays the "Clear Location?" prompt.
− If the contents of the location are to be cleared, the user should respond with a "Y". The
system performs the following for each item/lot quantity associated to the location:
• Sets the collected quantity to zero.
• Clears the LPs associated to items in the location.
• Determines the delta quantity between the existing quantity of the item/lot number
associated to the location and the collected quantity of the item/lot number (the delta
quantity is negative).
• Updates the inventory by adding the item/lot number delta quantity to the inventory in the
location.
• Generates a physical transaction for the item/lot number delta quantity.
− If the contents of the location are not to be cleared, the user should respond with an "N".
• The system proceeds to Physical—Select Item to Count.

Physical—Select Item to Count

• The user is prompted to scan the item associated to the inventory to be counted. The user must
identify the item by entering or scanning a valid item number, valid alternative item number, or
UPC number associated to the item.
• If the item is configured for full lot control, the lot number associated to the item must be identified
by entering or scanning a lot number. The system does not validate the lot number.

224 HighJump Warehouse Advantage Functional Description

 • The system prompts for quantity using the Universal Quantity Behavior Type–Count.
• The system determines the delta quantity between the existing quantity of the item/lot number
associated to the LP and the collected quantity of the item/lot number. The delta quantity will
either be zero, negative, or positive.
• If the item is configured for full serial control, the user is prompted for serial numbers. For more
information, see Serial Number Processing for Physical.
• The system allows the user to create LP assignments and associate item/lot number quantities to
those LPs.
• If the item/lot number is not already associated to the location, the system:
− Adds or updates the item/lot quantity to the inventory in the specified location.
• If the item/lot is already associated to the specified location, the system:
− Updates the inventory by adding the item/lot number delta quantity to the inventory in the
specified location.
• A physical transaction is generated for the item/lot number delta quantity.
• The system proceeds to Physical—Select Location to Count.

Serial Number Processing for Physical

The following applies to the Physical process.

• The user is prompted for serial numbers when the item is configured for full serial control and one
of the following is true:
− The collected quantity does not match the existing number of serial numbers for that
quantum.
− The collected quantity does not match the existing quantity in the system for that quantum.
• If the serial number does not exist anywhere in the warehouse, the system prompts the user to
confirm the serial number. The system allows the user to add the serial number to that location.
• If the serial number entered exists in a different quantum, the system prompts the user to confirm
the serial number and whether it should be moved to the new quantum.

Note
The system does not allow movement of a serial number to a different quantum that is
associated with the following.
- a different order.
- a different shipment.
- a different hold status, or all hold codes do not match.

− If the move is allowed, the system generates an 855 Serial Number Transfer transaction.
− If a serial number is moved to another quantum, a location cycle count is scheduled for the
location of the original quantum of inventory (even if the original quantum and destination
quantum are in the same location). The original quantum of inventory is placed in Unavailable
status. The original quantum is temporarily without a serial number, so the count of serial
numbers will not match the quantum quantity until that cycle count is completed.

Note
A location count is scheduled for the location of the original quantum only if a cycle count is
not already scheduled for that location.

HighJump Warehouse Advantage Functional Description 225

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 855 Serial Number Transfer transactions when the
item is configured for full serial control as detailed in the HighJump Warehouse Advantage Log
Transactions specification. The transactions are generated only when serial numbers are moved
from one location to another.
• HighJump Warehouse Advantage generates 880 Physical Inventory transactions as detailed in
the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for each item/lot quantity counted.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

226 HighJump Warehouse Advantage Functional Description

Location Status
The Location Status process manages the viewing and modification of the inventory status for a
specific location.

At a location-level, the system maintains a status to reflect the following.

Status Description
E Empty location. No inventory is associated to the location.
P Partial location. At least one item is in the location and the location has not
reached a user-determined capacity.
F Full location. At least one item is in the location and the location has reached a
user-determined capacity.
I Inactive location. The location and associated inventory are not available for
put-away and picking.

Process Details

The following process details apply.

Location Status—Select Location

• The user is prompted to scan the location to be viewed or modified. The user must identify the
location by entering or scanning a valid location identifier or valid short location identifier.
• The user is prompted to enter the location status. The system displays the current status of the
location. The possible location status codes are E, P, F, or I.
• The new status of the location must be identified by entering or scanning a valid status code (E,
P, F, or I).
• The system updates the location's status with the identified status.
• A location status transaction is generated for the location and selected status.

Interface Requirements

The following interface requirement applies.

• HighJump Warehouse Advantage generates 900 Location Status Admin transactions as detailed
in the HighJump Warehouse Advantage Log Transactions specification. The transactions are
generated for each location status modification.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 227

RF Messaging
The RF Messaging process allows messages to be broadcast via an RF device to a single user, a
department, or all users in the system from the HighJump Advantage Dashboard Base Web. The
messages display to users after they have completed their current transaction.

After an employee has received the message, they may submit a response, which can be viewed in
the HighJump Advantage Dashboard Base Web.

Process Details

The following process details apply.

• The system checks for any unread messages based on the priority and the date and time the
message was created.
• If the system finds a message, then the system determines if the message requires a response.
− If the message requires a response, the message displays to the user and the user is
prompted to enter a response after reading the message. The system updates the date and
time the message was read and the response.
− If the message does not require a response, the message displays to the user. The system
updates the date and time the message was read.

Interface Requirements

There are no interface requirements.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

228 HighJump Warehouse Advantage Functional Description

Quality Control
Quality Control includes the following process:
• Hold and Release

For information about the Web pages you can use to view information, see “Quality Control Pages” in
HighJump Advantage Dashboard Functional Description.

Hold and Release

The Hold and Release process manages the modification of a specific inventory status to reflect an
"on hold" or “available” status. When multiple holds is off, only available inventory can be put on hold.
When multiple holds is on, the same quantum of inventory can be put on hold for different reason
codes.

Based on user-specified entries, the user can identify a specific master license plate (MLP), license
plate (LP), or location containing the inventory, or to update all of the locations containing the
inventory. When inventory is released, the same reason code used to put the inventory on hold must
be used to release the inventory. The system updates the inventory status to "on hold” or “available”
and creates or removes hold records for the selected inventory. The system generates a hold or
release transaction reflecting the quantity for each quantum placed on hold or release and sends a
transaction to the host only when the inventory status changes. If the inventory is already on hold and
the user puts it on hold for a different reason, no transaction is created.

The system will not release a hold on an inventory if there is an open recall. If a recall applies to the
quantum released and multiple holds are not allowed, the system creates a hold using the reason
from the oldest recall in the system.

Process Details

The following process details apply.

Hold and Release—Select MLP/LP/Location/Item

• The system prompts the user to scan or enter an MLP, LP, location, or item.
• If the user enters or scans an MLP/LP/location/item, the value must meet the following criteria:
− The MLP/LP/location/item must exist.
− The MLP/LP/location must be a non-equipment location.
− The MLP/LP/location must have inventory associated to it.
− The MLP/LP/inventory must not be picked.
• The system prompts the user to enter additional information about the inventory to be put on hold
or released based on the scanned input.
• If the location is an MLP-controlled location, the system proceeds to Hold and Release—Scan
MLP.
• If the user scans an MLP or and LP-controlled location, the system proceeds to Hold and
Release—Scan LP.

HighJump Warehouse Advantage Functional Description 229

 • If the user scans an LP or an item-controlled location, the system proceeds to Hold and
Release—Scan Item.
• If the user scans an item, the system proceeds to Hold and Release—Enter Lot Number.

Hold and Release—Scan MLP

• The F8: List option lists the available MLPs. The list displays the following information about the
MLP to be put on hold or released:
− MLP License Plate
− Status
• The F2: Hold All option is available if there is inventory available in the location or the multiple
holds option is on. The F3: Release All option is available if there is held inventory in the location.

Note
These options should be used to hold or release all inventory in the location rather than a
specific MLP.

• The system proceeds to Hold and Release—Reason Code.

Hold and Release—Scan LP

• If the user enters or scans an LP to hold or release, it must meet the following criteria:
− The LP must exist in a non-equipment type location.
− The LP must be an inventory type of “IV”.
• The F8: List option lists the available LPs. The list displays the following information about the LP
to be put on hold or released:
− LP
− Status
• The F2: Hold All option is available if there is inventory available in the location or the multiple
holds option is on. The F3: Release All option is available if there is held inventory in the location.

Note
These options should be used to hold or release all inventory in the location rather than a
specific MLP.

• The system proceeds to Hold and Release—Reason Code.

Hold and Release—Scan Item

• If the user scans a valid item-controlled location, the system prompts the user to scan a specific
item for hold or release.
• The F8: List option lists the available items for the scanned location. The list displays the
following information about the item to be put on hold or released:
− License plate number
− Item number
− Lot number, if the item is lot-controlled
− Location
− Expiration Date, if the item is expiration date-controlled

230 HighJump Warehouse Advantage Functional Description

 − Quantity
• The F2: Hold All option is available if there is available inventory in the location or the multiple
holds option is on. The F3: Release All option is available if there is held inventory in the location.

Note
These options should be used to hold or release all inventory for the user selected inventory.

• If the user enters or scans an item, the system proceeds to Hold and Release—Enter Lot
Number.
• If the user enters F2: Hold All or F3: Release All, the system proceeds to Hold and Release—
Reason Code.

Hold and Release—Enter Lot Number

• If the item is configured for full lot control, the system prompts the user to scan a lot number.
• The F8: List option lists the available items for the scanned item. The list displays the following
information about the item to be put on hold or released:
− License plate number
− Item number
− Lot number, if the item is lot-controlled
− Location
− Expiration Date, if the item is expiration date-controlled
− Quantity
• The F2: Hold All option is available if there is available inventory in the location or the multiple
holds option is on. The F3: Release All option is available if there is held inventory in the location.

Note
These options should be used to hold or release all inventory for the user selected inventory.

• If the user enters or scans a lot number, the system proceeds to Hold and Release—Enter
Expiration Date.
• If the user enters F2 :Hold All or F3: Release All, the system proceeds to Hold and Release—
Reason Code.

Hold and Release—Enter Expiration Date

• If the item is expiration date-controlled, the system prompts the user to enter the expiration date.
The valid date format is MMDDYYYY.
• The F8: List option lists the available items for the scanned item. The list displays the following
information about the item to be put on hold or released:
− License plate number
− Item number
− Lot number, if the item is lot-controlled
− Location
− Expiration Date, if the item is expiration date-controlled
− Quantity

HighJump Warehouse Advantage Functional Description 231

 • The F2: Hold All option is available if there is available inventory in the location or the multiple
holds option is on. The F3: Release All option is available if there is held inventory in the location.

Note
These options should be used to hold or release all inventory for the user selected inventory.

• If the user entered or scanned an expiration date:

− If the original scan was an item, the system proceeds to Hold and Release—Enter Location.
− If the original scan was a location, the system proceeds to Hold and Release—Reason Code.
• If the user enters F2: Hold All or F3: Release All, the system proceeds to Hold and Release—
Reason Code.

Hold and Release—Scan Location

• The user is prompted to enter or scan the location.
• The F8: List option lists the available items for the scanned item. The list displays the following
information about the item to be put on hold or released:
− License plate number
− Item number
− Lot number, if the item is lot-controlled
− Location
− Expiration Date, if the item is expiration date-controlled
− Quantity
• The F2: Hold All option is available if there is available inventory in the location or the multiple
holds option is on. The F3: Release All option is available if there is held inventory in the location.

Note
These options should be used to hold or release all inventory for the user selected inventory.

• The system prompts the user to select a reason code for the transaction. The system proceeds to
Hold and Release—Reason Code.

Hold and Release—Reason Code

• The system prompts the user for a reason code. The user can enter the code or select from a list
of valid reason codes.
• The user can select from the following values:
− 02–Quality Control
− 03–Damage Inspection
− 04–Shipment Damage
− 05–Water Damage
• When the inventory is put on hold, the user must select a valid reason code. If the user enters a
reason code that is not valid for the transaction, the “Invalid Reason” error message displays.
• When the inventory is released, the user must use the same reason code that was used to put
the inventory on hold. If the user enters a reason code that is not valid for the transaction, the
“Invalid Reason” error message displays.

232 HighJump Warehouse Advantage Functional Description

 • The system proceeds to Hold and Release—Confirm Hold or Release.

Hold and Release—Confirm Hold or Release

• The user is prompted to confirm the hold or release of the selected inventory.
• If multiple holds is on and the inventory is in a Held status, the user has the option to enter F2:
Hold to add additional hold reason codes.
• The transaction completes. The system proceeds to Hold and Release—Select
MLP/LP/Location/Item.

Interface Requirements

The following interface requirements apply.

• HighJump Warehouse Advantage generates 700 QC Hold Item transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item-controlled inventory placed on hold.
• HighJump Warehouse Advantage generates 701 Hold Item transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each LP-controlled inventory placed on hold.
• HighJump Warehouse Advantage generates 702 Hold Item transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each MLP-controlled inventory placed on hold.
• HighJump Warehouse Advantage generates 710 Release Item transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each item-controlled inventory released.
• HighJump Warehouse Advantage generates 711 Release Item transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each LP-controlled inventory released.
• HighJump Warehouse Advantage generates 712 Release Item transactions as detailed in the
HighJump Warehouse Advantage Log Transactions specification. The transactions are generated
for each MLP-controlled inventory released.

Reporting/Labeling Requirements

There are no reporting or labeling requirements.

Configuration Requirements

There are no configuration requirements.

HighJump Warehouse Advantage Functional Description 233

Lot and Serial Trace Behavior
Trace behavior is inbound or outbound, as described in the following processes.

Inbound Trace

Outbound Trace

Inbound Trace
For processes that incorporate Inbound Trace behavior, the user is prompted for a lot and/or serial
number when the item is configured as inbound trace or trace in/out control. When prompted, the lot
and/or serial number is required but not validated. The lot and/or serial number is then recorded as
part of the receipt transaction.

Process Details

The following processes incorporate Inbound Trace behavior.

• Adjust Receipt of Shipment
• Directed Receipt
• Inventory Increment
• Kit Completion
• Miscellaneous Return
• Receipt from Production
• Receipt of Inbound Order
• Receipt of Shipment
• Staged Receipt
• Unkitting
• Unload/Unpick
• Warehouse Transfer In

234 HighJump Warehouse Advantage Functional Description

Outbound Trace
For processes that incorporate Outbound Trace behavior, the user is prompted for a lot and/or serial
number when the item is configured as outbound trace or trace in/out control. When prompted, the lot
and/or serial number is required but not validated. The lot and/or serial number is captured as part of
the pick transaction, and recorded for subsequent outbound transactions.

Process Details

The following processes incorporate Outbound Trace behavior.

• Batch Picking by Container
• Batch Picking by Order
• Bulk Pick by Load
• Bulk Pick by Wave
• Inventory Decrement
• Kit Completion
• Miscellaneous Issue
• Order Picking
• Pick Pass Order
• Scrap
• Unkitting
• Unload/Unpick
• Warehouse Transfer Out

HighJump Warehouse Advantage Functional Description 235

Pick Plan Behavior
This section describes the pick plan behavior in HighJump Warehouse Advantage.

When an inventory is incremented in a storage type location, allocation queue records are generated
for the items.

Whenever inventory is decremented in a storage type location, any associated allocation records are
removed for the items and an allocation queue record is generated for any items that had an
allocation removed.

For more information on how allocation records and allocation queue records are processed, see
HighJump Warehouse Advantage Technical Reference Guide.

236 HighJump Warehouse Advantage Functional Description

Waveless
Overview
Using Waveless, you can configure HighJump Warehouse Advantage to dynamically set the priority
of released outbound orders based on configured rules. Throughout the lifecycle of the sales order,
HighJump Warehouse Advantage reviews and periodically updates the priority of orders as
necessary. However, if you manually change the priority of an order, HighJump Warehouse
Advantage will not recalculate and change the priority. To use waveless, the system controls,
AUTO_RELEASE_ORDER and WAVELESS, must be enabled.

Rules

Overview

HighJump Warehouse Advantage uses the following types of rules to calculate the priority of an
outbound order.
Type of Rule Description
Priority Determines the priority value assigned to the outbound order.
Cutoff Time Defines the deadline for shipping the outbound order.
Processing Time Determines an estimated time to process the outbound order from the
beginning of picking to shipping.

When defining the rules, you set up an effective date and expiration date. You can also temporarily
override the rule during the time period to accommodate short-term changes.

Priority Rules

Overview

HighJump Warehouse Advantage uses priority rules to calculate the priority for an outbound order.
The system starts with a default priority value and adds to the value to change the priority. When the
system calculates a priority value, the values the system assigns are 1 through 99. For example, if
the process calculates a new priority value of 125, the system uses 99 for the new priority value.

HighJump Warehouse Advantage Functional Description 237

 You can use the following criteria to define priority rules.
Criteria Description
Carrier The priority value to assign to outbound orders associated with the
carrier.
Carrier and Service Level The priority value to assign to outbound orders associated with the
carrier and the designated service level.
Customer The priority value to assign to outbound orders associated with the
customer.
Item Number The priority value to assign to outbound orders that include the
item number.
Time Remaining between The priority value to assign to the outbound order based on the
Estimated Completion and time remaining. The system calculates the time remaining using
Cutoff the defined processing time and cutoff time rules.
Note
To use this criteria, you must set up cutoff time and process time
rules.

The system can apply multiple rules to an outbound order to calculate the new priority. When defining
the priority, you can enter a positive or negative value to calculate a higher or lower priority value.

Using the system control option, DEFAULT_PRIORITY, you can configure the default priority value
the system uses when calculating new priority values. To calculate the new priority value, the system
takes the default priority value and adds the delta value for all applicable rules for the outbound order.

Managing Priority Rules

You can use the Display Priority Rules page in HighJump Warehouse Advantage base web to
manage priority rules. To access the page, select Waveless Setup > Manage Priority Rules from
the Warehouse Advantage Menu.

238 HighJump Warehouse Advantage Functional Description

Cutoff Time Rules

Overview

HighJump Warehouse Advantage uses cutoff time rules to calculate the cutoff time for an outbound
order.

You can use the following criteria to define cutoff time rules.
Criteria Description
Carrier The cutoff time to assign to outbound orders associated with the
carrier.
Carrier and Service Level The cutoff time to assign to outbound orders associated with the
carrier and the designated service level.
Customer The cutoff time to assign to outbound orders associated with the
customer.
Route The cutoff time to assign to outbound orders associated with the
route.

Each rule defines the time of day and days of the week. For example, if a carrier picks up orders at
3:00 PM on Mondays and Wednesdays and at 12:00 PM on Fridays, you must define two rules. The
first rule defines the time of day as 3:00 PM and the days of the week as Monday and Wednesday.
The second rule defines the time of day as 12:00 PM and the days of week as Friday.

If more than one rule applies to an outbound order, the system uses the earlier cutoff time for the
outbound order.

Managing Cutoff Time Rules

You can use the Display Cutoff Time Rules page in HighJump Warehouse Advantage base web to
manage rules. To access the page, select Waveless Setup > Manage Cutoff Time Rules from the
Warehouse Advantage Menu.

HighJump Warehouse Advantage Functional Description 239

Processing Time Rules

Overview

HighJump Warehouse Advantage uses processing time rules to calculate the estimated time, in
minutes, it takes to process an order from the beginning of picking to shipping.

You can use the following criteria to define processing time rules.
Criteria Description
Customer The number of minutes to allow for outbound order processing for the
customer. You can define the rule to calculate the processing time per
order or per unit. If the rule is defined per unit, the system multiples the
number of units on the order by the defined number of minutes to calculate
the total processing time.
Item Number The number of minutes to allow for outbound order processing for the item.
You can define the rule to calculate the processing time per order or per
unit. If the rule is defined per unit, the system multiplies the number of units
on the order by the defined number of minutes to calculate the total
processing time.
Order Size The number of minutes to allow for outbound order processing based on a
size range. You can define the rule to calculate the processing time by size.
The size of the order can be measured in units, lines, cube, or weight.
Note
Since cube and weight is optional information to include with an order,
make sure accurate data is available if you want to measure the size of the
order in cube or weight.
For example, if you want to use weight to measure the size of an order and
only half of the items on the order include weight information, the calculated
processing time will be less than the actual time required to process the
outbound order.
Work Type The number of minutes to allow for outbound order processing for the work
type or work type and pick area. You enter a defined time for the work type
or work type and pick area.

The system can apply multiple rules to an outbound order to calculate the processing time. When
multiple rules apply to an outbound order, the system adds the processing time calculated for each
rule to determine the total processing time for the outbound order.

Using the system control option, DEFAULT_PROCESSING, you can configure the default processing
time the system uses when calculating the processing time for orders. To calculate the processing
time, the system takes the default processing value and adds the processing time for all applicable
rules for the outbound order.

240 HighJump Warehouse Advantage Functional Description

 Managing Processing Time Rules

You can use the Display Processing Time Rules page in HighJump Warehouse Advantage base web
to manage processing time rules. To access the page, select Waveless Setup > Manage
Processing Time Rules from the Warehouse Advantage Menu.

Researching Processing Time

You can use the Display Processing Times Results page in HighJump Warehouse Advantage base
web to search transaction history to help determine processing times to assign to rules. For example,
you can search the transaction history for a specific customer during a timeframe to view statistics
about processing orders for the customer. You can use the data as a guideline when defining
processing rules.

You can also use the page to identify the processing time impact of known outliers, such as specific
items or pick areas, which may need extra processing time. For example, assume a facility handles
mostly single cartons but also handles some large items that require a team lift or a different type of
equipment. You can use the analysis tool to determine the amount of processing time for the extra
handling. First, run an analysis of processing time for all activity from that work type and work area
and make note of the values. Then, rerun the analysis using the same criteria and include the large
item. Subtract the initial values from the subsequent values to determine the additional processing
time, if any, you want to allocate to processing outbound orders that include the larger item.

To access the Display Processing Time Results page, select Waveless Setup > Research
Processing Times from the Warehouse Advantage Menu. Using the Search Processing Time
Research page, you can enter your preferred search criteria.

The page provides the following information:

• The number of outbound orders matching the criteria.
• The total number of minutes spent processing all of the outbound orders from the beginning of
the pick activity to the end of order shipping.
• The average number of minutes spent processing the outbound orders.
• The minimum number of minutes spent processing an outbound order.
• The maximum number of minutes spent processing an outbound order.
• The number of minutes within one standard deviation.

HighJump Warehouse Advantage Functional Description 241

Order Consolidation
Overview
When importing orders into Warehouse Advantage, if two or more orders exist for the same
customer, the Order Consolidation process can combine these orders into a new order to maximize
warehouse efficiency. The system determines consolidation candidates with matching criteria
including customer, address, ship method, promise date, and more. Orders can only be consolidated
before they enter the picking process; picked or partially picked orders cannot be consolidated.

Import
Specific order details must be sent when importing, updating, or deleting an order.

Process Details

The following process details apply.

Importing a New Order

• Send the entire order, including the Master, Details, Comments, and Detail Comments.

Importing an Updated Order

• Send the entire order, including the Master, Details, Comments, and Detail Comments.

Deleting an Order
• Send the Master.

Deleting an Order Line

• Send the entire order as an update, with the exception of the line to be deleted.

242 HighJump Warehouse Advantage Functional Description

Consolidation Criteria
HighJump Warehouse Advantage uses certain criteria to identify valid candidates for order
consolidation. Consolidation candidates must have all of the following matching criteria:
Criteria Description
Customer The customer that placed the order.
Address The customer’s address.
Ship Method The method the order will be shipped.
Promise Date The promised date of order fulfillment.
Service Level The priority value to assign to outbound orders associated with the
carrier and the designated service level.
Carrier The priority value to assign to outbound orders associated with the
carrier.
Ship-to Location The destination location of the shipment. Can be narrowed to
Ship-to-State, Ship-to-City, and Ship-to-Zip.

Order consolidation is configurable to use various combinations of filtering criteria and warehouse
control flags.

Warehouse Controls
HighJump Warehouse Advantage uses the following warehouse controls for order consolidation:
Warehouse Control Description
MAX_CONS_ORDERS Max number of orders that can be grouped.
MAX_CONS_WEIGHT Total weight for group.
MAX_CONS_VOLUME Total volume for group.
ORDER_CONS_CUTOFF Only used if auto release is disabled. Determines at which point
the system should not consider orders to be consolidated (either
NOT RELEASED or RELEASED).

You can use any combination of MAX_CONS_ORDERS, MAX_CONS_WEIGHT, and

MAX_CONS_VOLUME simultaneously.

Shipping
The Order Consolidation—Shipping process sends the original order numbers and line details back to
the host, ensuring all orders that were consolidated are processed.

HighJump Warehouse Advantage Functional Description 243