Sterling Warehouse

Management System:
Implementation Guide
Fix Pack [Link]
 Copyright
This edition applies to the 9.1 Version of IBM® Sterling Warehouse Management System
and to all subsequent releases and modifications until otherwise indicated in new editions.
Before using this information and the product it supports, read the information in “Notices”
on page 441.
Licensed Materials - Property of IBM
IBM® Sterling Warehouse Management System
© Copyright IBM Corp. 2005 - 2011. All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA
ADP Schedule Contract with IBM Corp.

ii Implementation Guide
 Contents

Preface
Intended Audience .....................................................................................xxiii
Structure ..................................................................................................xxiii
Documentation ......................................................................................... xxvi
Conventions .............................................................................................. xxx

1 Introduction
1.1 Installing IBM Sterling Warehouse Management System with Your Own
Master Data ....................................................................................... 4
1.2 Installing IBM Sterling Warehouse Management System with Your Own
Configuration Data .............................................................................. 4
1.3 Installing IBM Sterling Warehouse Management System with Your Own
Transaction Data................................................................................. 5

Part I IBM Sterling Warehouse Management System Common

Configurations

2 Participant Modeling
2.1 Participant Model ................................................................................ 9
2.2 User Groups and Users .......................................................................10
2.2.1 Queue Management ......................................................................11
2.3 Reference Implementation ..................................................................11
2.3.1 For Participant Model (Configuration Data)........................................12
2.3.2 For User Groups and Users .............................................................14

iii
 2.3.3 For Saved Searches ...................................................................... 15
2.3.4 For Menu Groups.......................................................................... 15

3 Catalog and Product Management

3.1 Item Classifications (Configuration Data) .............................................. 17
3.2 Items .............................................................................................. 17
3.3 Reference Implementation.................................................................. 18
3.3.1 For Items (Master Data)................................................................ 18

4 Warehouse Layout Configuration

4.1 Warehouse Layout............................................................................. 21
4.1.1 Nodes ......................................................................................... 21
4.1.2 Location Size Codes ...................................................................... 21
4.1.3 Location Storage Codes................................................................. 22
4.1.4 Velocity Codes ............................................................................. 22
4.1.5 Zones ......................................................................................... 22
4.1.6 Locations .................................................................................... 22
4.1.7 Dock Scheduling .......................................................................... 23
4.1.8 Equipment Types ......................................................................... 24
4.1.9 Stations ...................................................................................... 24
4.2 Reference Implementation.................................................................. 25
4.2.1 For Warehouse Layout Configuration (Master Data)........................... 25
4.2.2 For Location Size Codes ................................................................ 26
4.2.3 For Location Storage Codes ........................................................... 27
4.2.4 For Dock Appointments Scheduling ................................................. 27
4.2.5 For Velocity Codes ........................................................................ 28
4.2.6 For Zones and Locations................................................................ 28
4.2.7 For Equipment ............................................................................. 28
4.2.8 For Devices ................................................................................. 29
[Link] Printers.................................................................................. 29
[Link] Weighing Scale ....................................................................... 29
4.2.9 For Stations................................................................................. 30

iv Implementation Guide
5 Inventory Rules Configuration
5.1 Inventory Tracking Attributes ..............................................................31
5.1.1 Product Class................................................................................31
5.1.2 Inventory Status ...........................................................................31
5.1.3 Inventory Adjustment Reasons .......................................................31
5.1.4 Inventory Status Transitions ...........................................................32
5.2 Reference Implementation ..................................................................33
5.2.1 For Product Class ..........................................................................33
5.2.2 For Inventory Status......................................................................33
5.2.3 For Inventory Adjustment Reasons ..................................................34
5.2.4 For Inventory Transitions ...............................................................35

6 Document Types
6.1 Document Types (Configuration Data)...................................................37

7 Productivity and Task Types

7.1 Productivity .......................................................................................39
7.2 Productivity Configurations ..................................................................40
7.2.1 Agents.........................................................................................40
7.3 Task Configurations ............................................................................41
7.3.1 Agents.........................................................................................41
7.4 Reference Implementation ..................................................................41
7.4.1 For Productivity Types (Configuration Data) ......................................41
7.4.2 For Task Types .............................................................................42
7.4.3 For SAM Definition (Configuration Data) ...........................................43
7.4.4 Task Execution Exceptions..............................................................45

Part II IBM Sterling Warehouse Management System Processes

and Features

8 Receive and Putaway

8.1 Receiving Processes............................................................................49
8.1.1 Mobile Application-Based Receiving Process ......................................50
[Link] Opportunistic Cross-Docking ......................................................51

v
 8.1.2 Paper-Based Receiving Process ...................................................... 52
8.2 Receiving Configurations .................................................................... 53
8.2.1 Receiving Pipeline......................................................................... 53
8.2.2 Activities ..................................................................................... 53
8.2.3 Setting Up Receiving Preferences.................................................... 54
[Link] Enterprise-Level Configurations ................................................. 54
[Link] Node-Level Configurations ........................................................ 54
8.2.4 Setting Up the Putaway Preferences................................................ 56
8.2.5 Setting up Receiving Disposition Codes ........................................... 57
[Link] Creating the Receiving Disposition ............................................. 57
[Link] Associating the Disposition Code with a Product Class .................. 58
[Link] Associating the Disposition Code with
Disposition Transition statuses .................................................. 58
[Link] Associating a Disposition Code for Receipt with QC....................... 59
[Link] Associating the Disposition Code with an Inventory Status ............ 59
8.2.6 Inventory Status Transitions .......................................................... 60
8.2.7 Agents ........................................................................................ 61
[Link] Putaway Complete Agent.......................................................... 62
8.2.8 Services...................................................................................... 63
[Link] Generate Putaway Request ....................................................... 64
[Link] Register Activity Demand For QC ............................................... 65
[Link] Register Activity Demand and Print Receiving Worksheet .............. 65
[Link] YNW_ Cross Dock Inventory_91 ................................................ 65
[Link] YNW_Generate Putaway Request_ 91......................................... 66
8.2.9 Prints.......................................................................................... 67
8.2.10 Productivity ................................................................................. 67
8.3 Managing the Receiving and Putaway Process on the Warehouse Floor ..... 67
8.3.1 Receiving and Putaway Flow Using an Order .................................... 67
[Link] Receiving Process .................................................................... 67
[Link] Putaway Process ..................................................................... 68
8.3.2 Receiving and Putaway Flow Using ASNs ......................................... 68
[Link] Receiving Process .................................................................... 68
[Link] Putaway Process ..................................................................... 69
8.4 Reference Implementation for Receiving............................................... 69
8.4.1 Inbound Rules Configuration .......................................................... 69

vi Implementation Guide
 [Link] Putaway Preferences.................................................................69
[Link].1 Putaway Task Types ............................................................70
[Link].2 Putaway Strategy ................................................................70
[Link] Node Receiving Preferences .......................................................70
[Link] Receiving Disposition Setup .......................................................71

9 Inventory Mass Maintenance

9.1 The Inventory Mass Maintenance Process ..............................................73
9.2 Inventory Mass Maintenance Configurations...........................................73
9.2.1 Agent ..........................................................................................73
[Link] Inventory Mass Maintenance......................................................74
9.2.2 API..............................................................................................75
[Link] manageChangeInventoryAttributesCriteria...................................75
9.2.3 Service ........................................................................................75
[Link] Inv Mass Maint ........................................................................75
9.3 Managing the Inventory Mass Maintenance
Process on the Warehouse Floor ..........................................................76
9.3.1 Performing the Inventory Mass Maintenance .....................................76

10 Location Mass Maintenance

10.1 Location Mass Maintenance Process ......................................................81
10.2 Location Mass Maintenance Configurations.............................................81
10.2.1 Agents.........................................................................................82
[Link] Location Mass Maintenance........................................................82
10.2.2 Services.......................................................................................85
[Link] Loc Mass Maint ........................................................................85
10.3 Managing the Location Mass Maintenance
Process on the Warehouse Floor ..........................................................85
10.3.1 Performing Location Mass Maintenance ............................................85

11 Managing Activity Demands

11.1 Creating an Activity Demand ...............................................................91
11.2 Activity Demand Search By All Attributes...............................................93
11.3 Activity Demand List...........................................................................94

vii
 11.4 Modifying An Activity Demand............................................................. 94
11.5 Deleting An Activity Demand............................................................... 96
11.6 Reference Implementation for Activity Demand ..................................... 97

12 Quality Control
12.1 Quality Control Process .....................................................................101
12.2 Quality Control Configurations............................................................103
12.2.1 Quality Control Pipeline ................................................................103
12.2.2 Activities ....................................................................................103
12.2.3 Setting Up the Quality Control Profile
At the Participant Or Catalog Level ...............................................103
12.2.4 Setting Up Disposition Codes ........................................................104
[Link] Enterprise-Level Disposition Setup ............................................105
[Link].1 Creating the Receiving Disposition .......................................105
[Link].2 Associating the Disposition Code with a Product Class.............106
[Link].3 Associating the Disposition Code with Disposition Transition
Statuses...........................................................................106
[Link] Node-Level Disposition Setup ...................................................107
[Link].1 Associating the Disposition Code with an Inventory Status ......107
[Link].2 Associating a Disposition Code for Receipt
with Quality Control ...........................................................108
12.2.5 Inventory Status Transitions .........................................................109
12.2.6 Setting Up Putaway Preferences ....................................................110
[Link] Putaway from Dock to QC Zone ................................................110
[Link] For Putaway from QC Zone to Storage ......................................111
12.2.7 Agents .......................................................................................112
12.2.8 Services.....................................................................................112
[Link] Register Activity Demand For QC ..............................................112
[Link] Register Activity Demand and Print Receiving Worksheet .............113
12.2.9 Prints.........................................................................................113
12.3 Managing the Quality Control Profile at the Transaction Level .................114
12.3.1 Creating a Quality Control Profile ...................................................114
12.3.2 Modifying a Quality Control Profile .................................................116
12.3.3 Deleting a Quality Control Profile ...................................................118
12.4 Managing the Quality Control Process on the Warehouse Floor................119

viii Implementation Guide

 12.4.1 Quality Control Flow For Receiving Using Order ............................... 119
[Link] Receiving Process................................................................... 119
[Link] Putaway Process .................................................................... 120
[Link] Inspection Process.................................................................. 120
[Link] Inspection Putaway ................................................................ 120
12.4.2 Quality Control Flow For Receiving Using ASNs ................................ 121
[Link] Receiving Process................................................................... 121
[Link] Putaway Process .................................................................... 121
[Link] Inspection Process.................................................................. 121
[Link] Inspection Putaway ................................................................ 122
12.5 Reference Implementation for Quality Control ...................................... 122
12.5.1 Putaway Preference Configuration ................................................. 123

13 Vendor Compliance
13.1 Vendor Compliance Process ............................................................... 125
13.2 Vendor Compliance Configurations ..................................................... 126
13.2.1 Setting Up the Discrepancy Codes ................................................. 126
13.3 Managing the Vendor Compliance Process on the Warehouse Floor ......... 127
13.3.1 Adding Discrepancy Details........................................................... 127
13.3.2 Editing Discrepancy Details........................................................... 131
13.3.3 Deleting Discrepancy Details......................................................... 131
13.4 Reference Implementation for Vendor Compliance ................................ 132
13.4.1 Discrepancy Codes Configuration................................................... 132

14 Move Request
14.1 Move Request Process ...................................................................... 135
14.1.1 Mobile Application-Based Move Request Process .............................. 135
14.1.2 Paper-Based Move Request Process ............................................... 136
14.2 Move Request Configurations ............................................................. 136
14.2.1 Agents....................................................................................... 136
14.2.2 Services..................................................................................... 136
[Link] Print Move Tickets .................................................................. 137
[Link] Generate Min Max Replenishment Move Request......................... 137
[Link] Generate Top Off Replenishment Move Request.......................... 137
14.2.3 Prints ........................................................................................ 138

ix
 14.2.4 Productivity ................................................................................138
14.3 Managing the Move Request Process on the Warehouse Floor .................138
14.3.1 Performing Move Tasks ...............................................................138
[Link] Using the Mobile Application ....................................................138
[Link] Using Paper ...........................................................................139
14.4 Reference Implementation for Move Requests ......................................139
14.4.1 Move Request Task Types.............................................................139
14.4.2 Move Request Cancellation Reasons ...............................................139
14.4.3 Putaway Preferences....................................................................139
[Link] Putaway Strategy ...................................................................140

15 Count
15.1 Count Processes...............................................................................143
15.1.1 Cycle Count Process ....................................................................143
15.1.2 Physical Count Process .................................................................144
[Link] Preparing for a Physical Count..................................................145
[Link] Running the Pre-Physical Inventory Script .................................151
[Link] Optimal Batch Sizes and Configuration Considerations .................152
[Link] Estimating the Personnel Requirements for Count Sheet
Data Entry During a Physical Count..........................................154
[Link].1 Calculations for a Warehouse with 15000 Locations
and One Task for Each Location..........................................154
[Link] Getting Started ......................................................................155
[Link] Count Sheet-Based Counting Process ........................................156
[Link] Recording Quantity on Count Sheets .........................................157
[Link] Completing Count Tasks ..........................................................157
[Link] Variance Count Process ...........................................................158
[Link] Completing Variance Tasks ......................................................159
[Link] Reprinting Count Sheets..........................................................159
[Link] Recording Count Data .............................................................160
[Link] Post Physical Count ................................................................160
[Link] Canceling Physical Count .........................................................162
15.1.3 The Mobile Application-Based Count Process ...................................163
15.2 Count Configurations ........................................................................163
15.2.1 Count Pipelines ...........................................................................163

x Implementation Guide
 [Link] Cycle Count Pipeline ............................................................... 164
15.2.2 Agents....................................................................................... 164
15.2.3 Prints ........................................................................................ 165
15.2.4 Productivity ................................................................................165
15.3 Managing the Count Process on the Warehouse Floor ............................ 166
15.3.1 Flow For Performing Cycle Count ................................................... 166
15.4 Reference Implementation for Count Processes .................................... 166
15.4.1 Count Program ........................................................................... 166
[Link] Count Calendar ...................................................................... 167
[Link] Count Program Conditions ....................................................... 167
15.4.2 Count Request Cancellation Reasons .............................................. 167
15.4.3 Count Task Types........................................................................ 167
15.4.4 Count Strategy ........................................................................... 168

16 Outbound
16.1 Outbound Process ............................................................................ 171
16.1.1 The Mobile Application-Based Pick and Pack Process ........................ 172
[Link] For Parcel Shipments .............................................................. 172
[Link].1 Full Case Pick and Pack Process........................................... 173
[Link].2 Less than Case Pick and Pack Process .................................. 173
[Link] For LTL/TL Shipments ............................................................. 174
[Link].1 Pick to Pallet Process ......................................................... 174
[Link].2 Pick from Forward Pick Area Process .................................... 175
16.1.2 Paper-Based Pick and Pack Processes............................................. 176
[Link] Full Case Pick and Pack Process for Parcel Shipments .................. 176
[Link] Less than Case Pick and Pack Process for Parcel Shipments.......... 177
[Link].1 Pick Process ..................................................................... 177
[Link].2 Pack Process..................................................................... 178
[Link] Manifest Process .................................................................... 178
[Link].1 Parcel Manifest ................................................................. 178
[Link] Pick and Pack Process for LTL/TL Shipments .............................. 178
[Link].1 Pick Process ..................................................................... 178
[Link].2 Pack Process..................................................................... 179
16.1.3 Material Handling Equipment-Based Pick Process ............................. 179
16.1.4 Resource Planning Process ........................................................... 182

xi
 16.1.5 Pack and Hold Process .................................................................183
16.1.6 Electronic Shipper’s Export Declaration Process ...............................184
16.2 Outbound Configurations ...................................................................185
16.2.1 Outbound Pipeline .......................................................................185
[Link] Outbound Pick Process Pipeline ................................................185
[Link] Outbound Container Pipeline for Outermost Cases ......................186
[Link] Outbound Container Pipeline for Parcel Cases .............................186
[Link] Outbound Container Pipeline for Pallets .....................................186
[Link] Outbound Shipment Pipeline ....................................................187
[Link] Load Pipeline .........................................................................188
16.2.2 Activities ....................................................................................188
16.2.3 Agents .......................................................................................189
16.2.4 Services.....................................................................................190
[Link] Change Shipment Status To Picked ...........................................190
[Link] Print Load BOL .......................................................................190
[Link] Alert Pro Number Set Expiration ...............................................191
[Link] Upload File To MHE .................................................................191
[Link] Download File From MHE .........................................................192
[Link] Download File To MHE With Reference.......................................194
[Link] Register Task Completion ........................................................194
[Link] Putaway Pack And Hold Shipment.............................................194
[Link] Send Retrieve Shipment Request..............................................195
[Link] Retrieve Pack and Hold Shipments............................................195
[Link] Process Retrieval For Pack and Hold Load ..................................196
[Link] SED Filing .............................................................................197
[Link] SED Hold Resolution ...............................................................197
16.2.5 Shipment Monitor........................................................................198
[Link] Packing Delayed.....................................................................199
16.2.6 Productivity ................................................................................199
16.2.7 Resource Planning .......................................................................199
[Link] Enabling Resource Planning for a Node ......................................199
[Link] Configuring the Node for Planning.............................................200
[Link] Creating Resource Pools ..........................................................201
[Link] Associating Resources to Resource Pools ...................................201
[Link].1 Assigning Shifts to Resources..............................................202

xii Implementation Guide

[Link].2 Setting Resource Efficiency ................................................. 202
[Link] Creating Task Type Resource Pool Associations .......................... 203
[Link] Creating Condition Sets........................................................... 204
[Link] Creating Planned Task Conditions ............................................. 204
[Link].1 Creating Conditions ........................................................... 205
16.2.8 Task Generation for Pack and Hold Shipments................................. 205
[Link] Creating a Hold Type .............................................................. 206
[Link] Configuring Activity Constraints................................................ 206
16.2.9 Electronic Shipper’s Export Declaration .......................................... 207
[Link] Creating a Hold Type .............................................................. 207
[Link].1 Hold Condition .................................................................. 209
16.3 Managing the Outbound Process on the Warehouse Floor....................... 210
16.3.1 Performing Outbound................................................................... 210
[Link] Resource Planning .................................................................. 211
[Link].1 Defining Standard Capacity................................................. 211
[Link].2 Viewing Capacity Details .................................................... 211
[Link].3 Viewing Demand Details..................................................... 213
[Link].4 Confirming a Plan .............................................................. 214
[Link] Picking.................................................................................. 215
[Link].1 Using the Mobile Application .............................................. 215
[Link].2 Using Printed Batch Sheets ................................................. 216
[Link].3 Using Material Handling Equipment ...................................... 217
[Link] Packing................................................................................. 217
[Link].1 Execution Console-Based Packing ........................................ 217
[Link].2 Mobile Application-Based Packing ........................................ 218
[Link] Verify Packing........................................................................ 218
[Link] Unpacking ............................................................................. 219
[Link].1 Execution Console-Based Unpacking .................................... 219
[Link].2 Mobile Application-Based Unpacking .................................... 219
[Link] Converting Inventory Container to Outbound Container
at the Weigh Station............................................................... 220
[Link] Pallet Shrink Wrapping............................................................ 221
[Link] Manifesting Parcel Containers .................................................. 221
[Link] Confirming LTL/TL Loads ......................................................... 221
[Link] Pack and Hold........................................................................ 222
[Link].1 Retrieval of Pack and Hold Shipments .................................. 222

xiii
 [Link].2 Retrieval of Pack And Hold Loads .........................................225
[Link] Electronic SED .......................................................................227
[Link].1 Entering the ITN................................................................227
16.4 Reference Implementation for Outbound Processes ...............................228
16.4.1 Shipment Groups ........................................................................228
16.4.2 Pick Location Assignment Configuration ..........................................229
16.4.3 Task Types .................................................................................230
[Link] Parcel Shipments ...................................................................230
[Link] LTL/TL Shipments...................................................................231
[Link] Paper-Based Pick....................................................................231
16.4.4 Pick Exceptions ...........................................................................232
16.4.5 Activity Constraints Configuration ..................................................232
[Link] Packing .................................................................................232
[Link].1 Non-Standard Single-SKU Container ....................................232
[Link].2 Standard Single-SKU Container ...........................................232
[Link].3 Multi-SKU or Multi Level Container .......................................233
[Link] Pallet Shrink Wrap..................................................................233
[Link] Carton Pack Complete .............................................................233
16.4.6 Resource Planning .......................................................................234
[Link] Node Planning Attributes .........................................................234
[Link] Resource Pool ........................................................................234
[Link] Task Type Associations ...........................................................238
[Link] Condition for Task Type Association ..........................................239
16.4.7 Prints........................................................................................240
[Link] Prints for the Mobile Application-Based Parcel Shipments .............240
[Link].1 Full Case Pick....................................................................241
[Link].2 Less Than Case Pick...........................................................241
[Link] Prints for the Mobile Application-Based LTL/TL Shipments ............241
[Link] Prints for Paper-Based Parcel Shipments....................................242
[Link] Prints for Paper-Based LTL/TL Shipments...................................242

17 Replenishment
17.1 Replenishment Process .....................................................................243
17.1.1 The Mobile Application-Based Replenishment Process .......................243
17.1.2 Paper-Based Replenishment Process ..............................................244

xiv Implementation Guide

 17.2 Replenishment Configurations............................................................ 244
17.2.1 Replenishment Strategy ............................................................... 244
17.2.2 Agents....................................................................................... 244
17.2.3 Services..................................................................................... 244
[Link] Print Move Tickets .................................................................. 245
[Link] Generate Min Max Replenishment Move Request......................... 246
[Link] Generate Top Off Replenishment Move Request.......................... 246
17.2.4 Prints ........................................................................................ 246
17.2.5 Productivity ................................................................................ 246
17.3 Managing the Replenishment Process on the Warehouse Floor................ 247
17.3.1 Performing Replenishment............................................................ 247
[Link] Using the Mobile Application .................................................... 247
[Link] Using Paper ........................................................................... 247
17.4 Reference Implementation for Replenishment ...................................... 248
17.4.1 Location Monitoring Rules............................................................. 248
[Link] Minimum and Maximum-Level Triggers ..................................... 248
[Link] Top-Off Replenishment Triggers ............................................... 248
17.4.2 Replenishment Task Types ........................................................... 249

18 Print Labels Manually

18.1 Print License Plate Labels Manually ..................................................... 251
18.2 Print UPC Case Code Labels Manually .................................................. 253

19 Value-Added Services
19.1 VAS Process .................................................................................... 257
19.1.1 Kitting Process ............................................................................ 257
[Link] Kitting Process in a Mobile Application-Based Warehouse ............. 258
[Link].1 VAS Execution Process ....................................................... 258
[Link] Kitting Process in a Paper-Based Warehouse .............................. 259
[Link].1 VAS Execution Process ....................................................... 259
19.1.2 Compliance Service Process .......................................................... 259
[Link] Compliance Service Process in a Mobile Application-Based Warehouse
260
[Link].1 VAS Execution Process ....................................................... 260
[Link] Compliance Service Process in a Paper-Based Warehouse ............ 261

xv
 [Link].1 VAS Execution Process .......................................................261
19.2 VAS Configurations...........................................................................262
19.2.1 VAS Pipeline ...............................................................................262
19.2.2 Activities ....................................................................................262
19.2.3 Agents .......................................................................................263
19.2.4 Service ......................................................................................264
[Link] Generate Putaway Request For Work Order................................264
19.2.5 Prints.........................................................................................265
19.2.6 Productivity ................................................................................265
19.3 Managing the VAS Process on the Warehouse Floor...............................265
19.3.1 Performing VAS...........................................................................265
[Link] Creating a Work Order Manually ...............................................265
[Link] Confirming a Work Order.........................................................266
19.4 Reference Implementation for VAS .....................................................266
19.4.1 Item Configuration ......................................................................266
19.4.2 Kitting Service Item Configuration .................................................267
19.4.3 Retrieval Strategy .......................................................................267
19.4.4 Putaway Strategy ........................................................................267
19.4.5 Compliance Service Item Configuration ..........................................268
19.4.6 Activity Constraints Configuration ..................................................268

20 Returns
20.1 Returns Process ...............................................................................269
20.1.1 Paper-Based Returns Process ........................................................269
20.2 Returns Configurations......................................................................271
20.2.1 Returns Pipeline ..........................................................................271
20.2.2 Setting Up the Receiving Preferences for Returns.............................271
[Link] Enterprise-Level Configurations ................................................272
[Link] Node-Level Configurations .......................................................272
20.2.3 Setting Up the Putaway Preferences for Returns ..............................273
20.2.4 Setting Up the Receiving Disposition Codes for Returns ....................274
[Link] Creating the Receiving Disposition ............................................274
[Link] Associating the Disposition Code with a Product Class .................275
[Link] Associating the Disposition Code with Disposition Transition statuses .
276

xvi Implementation Guide

 [Link] Associating a Disposition Code for Receipt with QC ..................... 276
[Link] Associating the Disposition Code with an Inventory Status ........... 277
20.2.5 Inventory Status Transitions ......................................................... 278
20.2.6 Agents....................................................................................... 279
20.2.7 Services..................................................................................... 279
[Link] GeneratePutawayRequest Service............................................. 279
[Link] Register Activity Demand For QC Service................................... 280
[Link] Register Activity Demand and Print Receiving Worksheet ............. 280
20.2.8 Prints ........................................................................................ 281
20.2.9 Productivity ................................................................................ 281
20.3 Managing the Returns Process on the Warehouse Floor ......................... 281
20.3.1 Performing Returns ..................................................................... 281
[Link] Creating and Authorizing Returns Process .................................. 281
20.4 Reference Implementation for Returns ................................................ 282
20.4.1 Inbound Rules Configuration for Returns ........................................ 282
[Link] Putaway Preferences............................................................... 282
[Link].1 Putaway Task Types ..........................................................283
[Link].2 Putaway Strategy .............................................................. 284
[Link] Node Receiving Preferences ..................................................... 284
[Link] Receiving Disposition Setup ..................................................... 284

21 Dynamic Item Velocity Calculation

21.1 Determining the Velocity Code ........................................................... 287
21.2 Dynamic Item Velocity Calculation Configurations ................................. 289
21.2.1 Agents....................................................................................... 289
21.2.2 Events ....................................................................................... 292
[Link] Agent Start ........................................................................... 292
[Link] Agent Completion................................................................... 292
21.2.3 Services..................................................................................... 292
[Link] Get Shipment Item Statistics ................................................... 293
[Link] Update Item Statistics ............................................................ 294
[Link] Enqueue Dynamic Velocity Code Calc Agent Message .................. 295
[Link] Item Statistics Data Loader ..................................................... 295
[Link] YNW_RaiseAlertForItemVelocityCodeAgentStart_91 .................... 297
[Link] YNW_ResolveAlertForItemVelocityCodeAgent_91 ........................ 297

xvii
 21.2.4 Mining Item Statistics for Pre-Existing Shipments ............................298
21.3 Calculating Dynamic Item Velocity ......................................................298
21.3.1 Setting the Time Period for Dynamic Item Velocity Calculation...........298
21.3.2 Viewing the Cumulative Item Share (Analysis Level) Graph ...............300
21.3.3 Viewing Item Velocity Code Change Requests History.......................301
21.3.4 Updating Item Velocity Code.........................................................302
21.3.5 Selecting Zones for Slotting ..........................................................303
21.3.6 Applying Saved Results for Slotting................................................305

22 Integration With Slotting Engines

22.1 Slotting Engines ...............................................................................307
22.2 Slotting Using IBM Sterling Warehouse Management System..................307
22.3 Integration ......................................................................................308
22.3.1 Interfacing with Slotting Engines ...................................................308
22.3.2 Slotting Configurations.................................................................310
[Link] Configuring to integrate with Slotting Engines ............................310
[Link] Configuring the Queue for Server Slotting..................................311
22.4 Reference Implementation.................................................................311
22.4.1 Reference Implementation Integration Strategy ..............................312
22.4.2 Slotting Configurations for OptiSlot™ .............................................313

A Transaction Data
A.1 Inbound ..........................................................................................315
A.1.1 PO-Based Receipt ........................................................................316
A.1.2 ASN-Based Receipts ....................................................................316
A.1.3 Transfer Order Shipments ...........................................................316
A.2 Inventory ........................................................................................316
A.3 Outbound........................................................................................317

B New Components for Existing IBM Sterling Selling and

Fulfillment Foundation Customers
B.1 APIs and User Exits ..........................................................................319
B.2 Services..........................................................................................321
B.2.1 Receiving or QC-Related Services ..................................................321

xviii Implementation Guide

 B.2.2 Move Request Services ................................................................ 322
B.2.3 Shipment Processing Services ....................................................... 322
B.2.4 Wave Processing Services ............................................................ 324
B.3 Monitor Events................................................................................. 325
B.4 Transactions.................................................................................... 326
B.5 Events ............................................................................................ 326

C Customizing the Reference Implementation

C.1 Customizing Reference Implementation Data ....................................... 329
C.1.1 Loading Your Own Master Data ..................................................... 329
C.1.1.1 Item..................................................................................... 329
C.1.1.2 Location................................................................................ 330
C.1.1.3 Equipment ............................................................................ 330
C.1.2 Loading Your Own Transaction Data............................................... 330
C.1.2.1 Location Inventory ................................................................ 331
C.2 Customizing Your Node ..................................................................... 331
C.2.1 Copying Node Configuration.......................................................... 331
C.2.2 Onboarding Clients (Enterprises) ................................................... 331
C.2.3 Offboarding Clients (Enterprises)................................................... 335
C.2.4 Deleting a Node .......................................................................... 336
C.3 Moving Data from the Test Environment to Production .......................... 336

D Localizing IBM Sterling Warehouse Management System

D.1 Resource Bundles............................................................................. 337

E Packing Using the Mobile Application

E.1 Understanding the Supported Pack Processes....................................... 339
E.1.1 Packing Based on Picking ............................................................. 339
E.1.2 Packing Based on Containerization................................................. 341
E.1.2.1 User-Directed Containerization ................................................. 341
E.1.2.2 System-Directed Containerization............................................. 341
E.2 Pack Strategies ................................................................................ 342
E.2.1 Shipment-Driven Packing ............................................................. 342
E.2.1.1 User-Directed Packing............................................................. 342

xix
 E.[Link] Packing Without Recording Item Details................................345
E.[Link] Packing With the System Identifying Item Details ..................346
E.[Link] Packing With the User Recording Item Details .......................347
E.[Link] Opening a Container ..........................................................350
E.[Link] Opening a Case or a Pallet ..................................................352
E.2.1.2 System-Directed Packing.........................................................353
E.[Link] Packing With the User Recording Item Details .......................356
E.2.1.3 Scanning the Task List Number ...............................................361
E.2.1.4 Scanning the Cart Location ......................................................362
E.2.2 Item-Driven Packing ....................................................................364
E.2.2.1 User-Directed Packing .............................................................364
E.[Link] Packing With the System Identifying Item Details ..................367
E.[Link] Packing With the User Recording Item Details .......................370
E.[Link] Creating a New Container ...................................................374
E.2.2.2 System-Directed Packing.........................................................376
E.[Link] Packing With the User Recording Item Details .......................380
E.[Link] Scanning a Container SCM..................................................383
E.2.2.3 Scanning a Pallet, Case, or Item ID ..........................................384
E.2.2.4 Scanning a SKU .....................................................................387
E.2.3 Scanning a Pack Location .............................................................390
E.2.4 Selecting a Pack Station ...............................................................391
E.2.5 Viewing Instructions ....................................................................392
E.2.6 Selecting a SKU ..........................................................................393
E.2.7 Scanning the Secondary Serial Number ..........................................396
E.3 Pack Verification ..............................................................................397
E.3.1 Confirming the Quantity ...............................................................404
E.3.2 Handling the Quantity Mismatch ....................................................406
E.3.3 Scanning the Number of SKUs.......................................................406
E.3.4 Handling the SKU Count Mismatch .................................................407
E.3.5 Scanning a SKU ..........................................................................408
E.3.6 Handling the Mismatch.................................................................411
E.4 Unpacking .......................................................................................412
E.4.1 Scanning the Unpack Criteria ........................................................415
E.5 Scanning a Location..........................................................................417
E.6 Scanning the Serial Number ..............................................................418

xx Implementation Guide
 E.7 Scanning the Container SCM.............................................................. 422
E.8 Scanning the Tag Attribute ................................................................ 424
E.9 Scanning the Expiration Date ............................................................. 428
E.10 Scanning the Quantity ...................................................................... 430

F Menu-Level Customization of the Mobile Application

F.1 Menu-Level Customization................................................................. 435
F.1.1 Avoiding Copying of HTML Files ..................................................... 436
F.1.2 Avoiding Copying of JSP Files ........................................................ 436

G XML Integration SED

Notices
Trademarks............................................................................................... 444

Index

xxi
xxii Implementation Guide
 Preface

This manual explains the IBM® Sterling Warehouse Management System

and the Reference Implementation provided along with it. This manual
also contains information about the various processes and solutions
offered by Sterling Warehouse Management System.

Intended Audience
This manual provides information for individuals who are responsible for
implementing and using the Sterling Warehouse Management System
Reference Implementation.

Structure
This document contains the following chapters:
Chapter 1, "Introduction"
This chapter introduces Sterling Warehouse Management System to you
and explains the different types of installations.
Chapter 2, "Participant Modeling"
This chapter explains the Participant Model of the Sterling Warehouse
Management System with the help of examples.
Chapter 3, "Catalog and Product Management"
This chapter explains the different catalogs or Product Management
configurations that are provided as part of Sterling Warehouse
Management System.

xxiii
 Chapter 4, "Warehouse Layout Configuration"
This chapter explains the standard warehouse layout configuration that is
provided with Sterling Warehouse Management System.
Chapter 5, "Inventory Rules Configuration"
This chapter explains the inventory tracking attributes configured in
Sterling Warehouse Management System.
Chapter 6, "Document Types"
This chapter lists the different document types that are provided in
Sterling Warehouse Management System.
Chapter 7, "Productivity and Task Types"
This chapter lists the task types, productivity types, and the Standard
Allowable Minutes provided as a part of the configuration data in Sterling
Warehouse Management System.
Chapter 8, "Receive and Putaway"
This chapter explains the Receiving process and solution offered by
Sterling Warehouse Management System.
Chapter 9, "Inventory Mass Maintenance"
This chapter explains the process of updating the attributes of an
inventory at the same time.
Chapter 10, "Location Mass Maintenance"
This chapter explains the process of updating the attributes of a set of
locations at the same time.
Chapter 11, "Managing Activity Demands"
This chapter explains how to create, modify, and delete Activity Demands
using Sterling Warehouse Management System.
Chapter 12, "Quality Control"
This chapter explains the Quality Control process and solution offered by
Sterling Warehouse Management System.
Chapter 13, "Vendor Compliance"
This chapter explains the Vendor Compliance process and solution
offered by Sterling Warehouse Management System.

xxiv Implementation Guide

Chapter 14, "Move Request"
This chapter explains the Move Request process and solution offered by
Sterling Warehouse Management System.
Chapter 15, "Count"
This chapter explains the Count process and solution offered by Sterling
Warehouse Management System.
Chapter 16, "Outbound"
This chapter explains the Outbound process and solution offered by
Sterling Warehouse Management System.
Chapter 17, "Replenishment"
This chapter explains the Replenishment process and solution offered by
Sterling Warehouse Management System.
Chapter 18, "Print Labels Manually"
This chapter explains process of printing License Plate Numbers and UPC
Case Code Labels manually.
Chapter 19, "Value-Added Services"
This chapter explains the VAS process and solution offered by Sterling
Warehouse Management System.
Chapter 20, "Returns"
This chapter explains the Returns process and solution offered by
Sterling Warehouse Management System.
Chapter 21, "Dynamic Item Velocity Calculation"
This chapter explains the process of calculating the dynamic velocity
codes for items and updating the same using Sterling Warehouse
Management System. It also explains slotting if integrated with a
third-party slotting engine.
Chapter 22, "Integration With Slotting Engines"
This chapter explains integration with Slotting Engines by Sterling
Warehouse Management System.
Appendix A, "Transaction Data"
This appendix explains the transaction data that has been provided as a
part of Sterling Warehouse Management System.

xxv
 Appendix B, "New Components for Existing IBM Sterling Selling
and Fulfillment Foundation Customers"
This appendix is meant to be a quick reference for individuals who are
already familiar with the Sterling Selling and Fulfillment Foundation to
see which components were added or modified in implementing Sterling
Warehouse Management System.
Appendix C, "Customizing the Reference Implementation"
This appendix explains how to customize the Reference Implementation
data provided as part of Sterling Warehouse Management System,
customize your node, use the test bed for production, and move data
from your test bed to production.
Appendix D, "Localizing IBM Sterling Warehouse Management
System"
This appendix explains how to localize Sterling Warehouse Management
System.
Appendix E, "Packing Using the Mobile Application"
This appendix explains how to pack, verify pack, and unpack using the
Mobile Application.
Appendix F, "Menu-Level Customization of the Mobile
Application"
This appendix explains how to avoid copying of HTMLs and JSPs while
performing menu level customization.
Appendix G, "XML Integration SED"
This appendix explains how XML is generated by the system which is
used to file the SED as a part of Sterling Warehouse Management
System.

Documentation
For more information about the Sterling Warehouse Management System
components, see the following manuals:
Q
Sterling Warehouse Management System: Release Notes
Q
Sterling Warehouse Management System: Installation Guide
Q
Sterling Warehouse Management System: Overview

xxvi Implementation Guide

Q
Sterling Warehouse Management System: Implementation Guide
Q
Sterling Warehouse Management System: Reports Guide
Q
Sterling Warehouse Management System: Business Intelligence
Guide
Q
Sterling Warehouse Management System: Printed Documents Guide
Q
Sterling Warehouse Management System: Billing Activity Reporting
Engine Guide
Q
Sterling Warehouse Management System: Upgrade Guide
Q
Sterling Warehouse Management System: Voxware Integration Guide
Q
Sterling Warehouse Management System: Javadocs
For more information about the IBM® Sterling Selling and Fulfillment
Foundation components, see the following manuals:
Q
Sterling Selling and Fulfillment Foundation: Release Notes
Q
Sterling Selling and Fulfillment Foundation: Installation Guide
Q
Sterling Selling and Fulfillment Foundation: Upgrade Guide
Q
Sterling Selling and Fulfillment Foundation: Configuration Deployment
Tool Guide
Q
Sterling Selling and Fulfillment Foundation: Performance Management
Guide
Q
Sterling Selling and Fulfillment Foundation: High Availability Guide
Q
Sterling Selling and Fulfillment Foundation: System Management
Guide
Q
Sterling Selling and Fulfillment Foundation: Localization Guide
Q
Sterling Selling and Fulfillment Foundation: Customization Basics
Guide
Q
Sterling Selling and Fulfillment Foundation: Customizing APIs Guide
Q
Sterling Selling and Fulfillment Foundation: Customizing Console JSP
Interface for End User Guide
Q
Sterling Selling and Fulfillment Foundation: Customizing the RCP
Interface Guide

xxvii
 Q
Sterling Selling and Fulfillment Foundation: Customizing User
Interfaces for Mobile Devices Guide
Q
Sterling Selling and Fulfillment Foundation: Customizing Web UI
Framework Guide
Q
Sterling Selling and Fulfillment Foundation: Customizing Swing
Interface Guide
Q
Sterling Selling and Fulfillment Foundation: Extending the Condition
Builder Guide
Q
Sterling Selling and Fulfillment Foundation: Extending the Database
Guide
Q
Sterling Selling and Fulfillment Foundation: Extending Transactions
Guide
Q
Sterling Selling and Fulfillment Foundation: Using Sterling RCP
Extensibility Tool Guide
Q
Sterling Selling and Fulfillment Foundation: Integration Guide
Q
Sterling Selling and Fulfillment Foundation: Product Concepts Guide
Q
Sterling Warehouse Management System: Concepts Guide
Q
Sterling Selling and Fulfillment Foundation: Application Platform
Configuration Guide
Q
Sterling Distributed Order Management: Configuration Guide
Q
Sterling Supply Collaboration: Configuration Guide
Q
Sterling Global Inventory Visibility: Configuration Guide
Q
Catalog Management: Configuration Guide
Q
Sterling Logistics Management: Configuration Guide
Q
Sterling Reverse Logistics: Configuration Guide
Q
Sterling Warehouse Management System: Configuration Guide
Q
Sterling Selling and Fulfillment Foundation: Application Platform User
Guide
Q
Sterling Distributed Order Management: User Guide
Q
Sterling Supply Collaboration: User Guide

xxviii Implementation Guide

Q
Sterling Global Inventory Visibility: User Guide
Q
Sterling Logistics Management: User Guide
Q
Sterling Reverse Logistics: User Guide
Q
Sterling Warehouse Management System: User Guide
Q
Sterling Selling and Fulfillment Foundation: Mobile Application User
Guide
Q
Sterling Selling and Fulfillment Foundation: Business Intelligence
Operational Reports Guide
Q
Sterling Selling and Fulfillment Foundation: Javadocs
Q
Sterling Selling and Fulfillment Suite: Glossary
Q
Parcel Carrier: Adapter Guide
Q
Sterling Selling and Fulfillment Foundation: Multitenant Enterprise
Guide
Q
Sterling Selling and Fulfillment Foundation: Password Policy
Management Guide
Q
Sterling Selling and Fulfillment Foundation: Properties Guide
Q
Catalog Management: Concepts Guide
Q
Sterling Selling and Fulfillment Foundation: Pricing Concepts Guide
Q
Sterling Selling and Fulfillment Foundation: Setting Up Quotes in
Distributed Order Management
Q
Sterling Sensitive Data Capture Server, Release 1.0: Configuration
Guide
Q
Sterling Sensitive Data Capture Server, Release 1.0: PA-DSS
Implementation Guide
Q
Sterling Selling and Fulfillment Foundation: Secure Deployment Guide
Q
Sterling Business Center: Item Administration Guide
Q
Sterling Business Center: Pricing Administration Guide
Q
Sterling Business Center: Customization Guide
Q
Sterling Business Center: Localization Guide
Q
Sterling Field Sales: Deployment Guide

xxix
 Q
Sterling Field Sales: Implementation Guide
Q
Sterling Field Sales: Localization Guide
Q
Sterling Field Sales: User Guide
Q
Sterling Field Sales: Customization Guide
Q
Visual Modeler: Administration Guide
Q
Visual Modeler: Best Practices Guide
Q
Visual Modeler: Implementation Guide
Q
Visual Modeler: Installation Guide
Q
Visual Modeler: Tutorial Guide

Conventions
The following conventions may be used in this manual:

Convention Meaning
... Ellipsis represents information that has been
omitted.
<> Angle brackets indicate user-supplied input.

mono-spaced text Mono-spaced text indicates a file name, directory

path, attribute name, or an inline code example or
command.
/ or \ Slashes and backslashes are file separators for the
Windows, UNIX, and LINUX operating systems. The
file separator for the Windows operating system is
"\" and the file separator for UNIX and Linux systems
is "/". The UNIX convention is used unless otherwise
mentioned.
<YANTRA_HOME_OLD> User-supplied location of the installation directory
for previously installed releases. This is only
applicable for Releases 7.7, 7.9, and 7.11.
<YFS_HOME_OLD> This is the <YANTRA_HOME>/Runtime directory of
previously installed releases. This is only applicable
for Releases 7.7, 7.9, and 7.11.
<INSTALL_DIR> User-supplied location of the Sterling Selling and
Fulfillment Foundation installation directory. This is
applicable for Release 8.0.

xxx Implementation Guide

xxxi
xxxii Implementation Guide
 1
Introduction

Sterling Warehouse Management System helps you manage operations in

mid-sized Finished Goods distribution centers (DCs). Shipments may be
shipped to consumers, retailers or distributors, or mom and pop stores.
The execution process includes the use of mobile devices for managing
operations in the warehouse. It includes support for parcel as well as
less-than-truckload (LTL) shipments. Shipment consolidation or
transportation optimization, customer compliance, productivity, space
optimization, and so on, are the key problems that Sterling Warehouse
Management System helps solve.
Sterling Warehouse Management System also provides a pre-configured
Reference Implementation. The Reference Implementation provides
standard configurations and processes followed in a typical finished
goods warehouse. Additionally, it may also include certain transactional
data necessary to demonstrate its ability.
You can opt to install the Reference Implementation, and may need to
integrate with third-party Distributed Order Management (DOM) or
Enterprise Resource Planning (ERP) solutions. In this case, Sterling
Warehouse Management System provides some default integration
mechanisms to upload the information to the host systems. The host
systems can be legacy systems or some other ERP systems.
Similarly, if Sterling Warehouse Management System is implemented
with the Mobile Application, to back up the Mobile Application process
certain transactions are configured such that they can be performed
through paper-based requests.

Introduction 3
Installing IBM Sterling Warehouse Management System with Your Own Configuration

Installing Sterling Warehouse Management System Reference

Implementation is optional. Also, there are various options when
installing the Reference Implementation:
Q
Installing IBM Sterling Warehouse Management System with Your
Own Master Data
Q
Installing IBM Sterling Warehouse Management System with Your
Own Configuration Data
Q
Installing IBM Sterling Warehouse Management System with Your
Own Transaction Data
For more information about the different options for installing the
Reference Implementation, see the Sterling Warehouse Management
System: Installation Guide.

1.1 Installing IBM Sterling Warehouse

Management System with Your Own Master Data
The default installation of Sterling Warehouse Management System
Reference Implementation is performed with the configuration data only.
To use your own master data, choose the default installation. To load the
master data, you can use the Sterling Selling and Fulfillment Foundation
Rapid Deployment Tools (RDT). For more information about the RDT, see
the Sterling Selling and Fulfillment Foundation: Installation Guide.
You can use the RDT for installing locations, installing items, and
changing the equipment configuration to point to the appropriate
locations.

1.2 Installing IBM Sterling Warehouse

Management System with Your Own
Configuration Data
If you choose to install the Reference Implementation with your own
configuration data, it is assumed that you understand the various
concepts and configurations involved. For more information about the
various concepts and configurations, see the Sterling Warehouse
Management System: Concepts Guide and the Sterling Warehouse
Management System: Configuration Guide.

4 Implementation Guide
 Installing IBM Sterling Warehouse Management System with Your Own Transaction

For understanding the details of the processes provided with Sterling

Warehouse Management System, see Part II, "IBM Sterling Warehouse
Management System Processes and Features". However, remember that
the data provided in the examples use the Sterling Warehouse
Management System Reference Implementation.

1.3 Installing IBM Sterling Warehouse

Management System with Your Own Transaction
Data
Using the transaction data provided with Sterling Warehouse
Management System helps you to understand the system processes and
features. All the examples provided in this document use the transaction
data provided with Sterling Warehouse Management System. However, if
you use your own transaction data, ensure that the data is complete and
in sync with the configuration and master data provided by Sterling
Warehouse Management System.

Introduction 5
Installing IBM Sterling Warehouse Management System with Your Own Transaction

6 Implementation Guide
 Part I
IBM Sterling Warehouse Management
System Common Configurations

This part of the manual explains the common configurations that are
needed for the Sterling Warehouse Management System.
The following topics are covered in detail:
Q
Participant Modeling
Q
Catalog and Product Management
Q
Warehouse Layout Configuration
Q
Inventory Rules Configuration
Q
Document Types
Q
Productivity and Task Types

7
8 Implementation Guide
 2
Participant Modeling

The Participant Model of the Sterling Warehouse Management System

maps to third-party logistics (3PL) requirements and has the ability to
add new clients (Enterprises). The Hub typically sits on top of the
Participant Model.
This chapter explains the Participant Model and its Reference
Implementation provided by Sterling Warehouse Management System.

2.1 Participant Model

The business entities that participate as trading partners with an
enterprise in the supply chain are referred to as Participants. Participants
can be given different roles. For example, a participant can be an
Enterprise, Seller, Buyer, Node, or Carrier.
Each role defined for a participant gives it a certain set of abilities and
attributes. Participants can be granted or revoked permissions that
determine how they can modify and process orders.
Each participant can have its own generic attributes defined, such as
shipping and billing addresses, communication protocols, or calendars.
Additionally, relationships between participants can be created by
defining parent and children organizations.
If a participant is given the role of Enterprise, it can maintain its own
inventory and catalog.
For more information about Participant Modeling, see the Sterling Selling
and Fulfillment Foundation: Product Concepts Guide and the Catalog
Management: Configuration Guide.

Participant Modeling 9
User Groups and Users

2.2 User Groups and Users

User groups are a collection of users who perform a similar task. For
example, a group of customer service representatives might be put in a
Customer Service Representative user group.
Users can belong to multiple user groups, to which permissions are
assigned. A user who belongs to multiple user groups retains the least
restrictive set of permissions defined by the groups they belong to. For
example, if a user belongs to a user group that permits them to use the
Application Consoles and they also belong to a user group that only
permits them to use the Application Consoles and Applications Manager,
the user will have access to both applications.
Each organization has its own user groups. User groups can only contain
users for the same organization that the user was created for, except in
the case of a user group created by the Hub organization, which can
contain users of any organization.
The set of user groups and menu groups that are provided with Sterling
Warehouse Management System are shown in Table 2–1.

Table 2–1 Users Groups and Menus

User Group Menu
Warehouse Manager WMS Node Warehouse Manager Menu
Inventory Supervisor WMS Node Inventory Supervisor Menu
Receiving Supervisor WMS Node Receiving Supervisor Menu
Shipping Supervisor WMS Node Shipping Supervisor Menu
Enterprise Specific Warehouse WMS Node User Menu
User
Enterprise User Enterprise User Menu
Node User WMS Lite Node User Menu
Mobile User WMS Mobile User Menu
Station User WMS Station User Menu
System Administrator WMS System Admin Menu
Sterling Warehouse Management YNW System Admin Menu
System System Administrator

10 Implementation Guide
 Reference Implementation

2.2.1 Queue Management

Queue Management is used to create queues for different users and
types of alerts. These queues can be designed to notify specified users of
alerts at configured levels and times. Queue Management is also used to
define how the configured users are notified.
For more information about Queue Management, see the Catalog
Management: Configuration Guide.
The queues provided with Sterling Warehouse Management System are
shown in Table 2–2.

Table 2–2 Queues

Queue Description

INV_CONTROL
Q
Alerts when move requests have exceptions during
release.
Q
Alerts, for each item, when the release wave does not
take the wave to the Released status.
Q
Short Pick Alerts if short picks are recorded for an
item.
Q
Alerts when the wave gets cancelled during Wave
Release. The Inventory Control alert should be
consolidated based on item for a Wave. That is, If a
wave contains 10 shipment with 2 distinct items, only
2 alerts should be raised in the inventory Queue.

RECEIVING
Q
Alerts when receipts have exceptions during receipts.
Q
Alerts when shipments are received but not putaway
within 4 hours of receipt.

SHIPPING
Q
Alerts if Shipments have not reached the Packed status
four hours before the Requested Ship Date.
Q
Alerts, for each shipment, when the release wave does
not take the wave to the Released status.

DEFAULT
Q
The default queue for any other exceptions is not
categorized in the above list.

2.3 Reference Implementation

This section explains the Reference Implementation for Participant
Modeling provided with the Reference Implementation of Sterling
Warehouse Management System.

Participant Modeling 11
Reference Implementation

2.3.1 For Participant Model (Configuration Data)

The Sterling Warehouse Management System comes with a
pre-configured Participant Model.
The structure of the Sterling Warehouse Management System Participant
Model is illustrated in Figure 2–1.

Figure 2–1 Participant Model

12 Implementation Guide
 Reference Implementation

In this figure,
1. DEFAULT is the Hub.
2. XYZ-CORP is the Enterprise.
Q
Enterprises have their own Inventory and Catalog Organizations.
Q
XYZ-CORP is its own Inventory and Catalog Organization.
3. XYZ-RETAILER is the Enterprise and Seller
Q
XYZ-RETAILER is the retail channel for XYZ-CORP
Q
XYZ-RETAILER inherits configurations from XYZ-CORP
4. XYZ-ONLINE is the Enterprise and Seller
Q
XYZ-ONLINE is the online channel for XYZ-CORP
Q
XYZ-ONLINE inherits configurations from XYZ-CORP
5. Vendors/Suppliers are modeled as both Sellers and Nodes.
6. Buyers/Customers are modeled as both Buyers and Nodes.
7. DC1 is the WMS node owned by DEFAULT.
Q
DC1 participates with XYZ-CORP.
Q
DC1 is assumed to follow a Mobile Application-based process.

8. DC2 is the Application Consoles node owned by DEFAULT.

Q
DC2 participates with XYZ-CORP.
Q
DC2 is assumed to maintain inventory externally.
9. DC3 is the WMS node owned by DEFAULT.
Q
DC3 participates with XYZ-CORP.
Q
DC3 is assumed to follow a paper-based process.
10. In addition to Parcel Carriers, some major LTL and TL Carriers are provided
as a part of the master data.

In addition to this factory setup, the PRO # generation logic for each of
the carriers is also configured.

Participant Modeling 13
Reference Implementation

2.3.2 For User Groups and Users

A user group is a collection of users who perform similar tasks. User
groups are created to specify screen level access permissions. Each user
needs to be associated with a specific user group.
All users are provided with specific, pre-configured menus, based on the
user group to which they belong.
The default password for the users is the same as the user name. This
password can be changed later.
The prefix of the user name represents the node or enterprise to which
the user belongs.
The set of users that are configured for warehouse operations are:

Table 2–3 Users

Users User Group Menu
dc1mgr Warehouse Manager WMS Node Warehouse
Manager Menu
dc3mgr
dc1invs Inventory Supervisor WMS Node Inventory
Supervisor Menu
dc3invs
dc1inbs Receiving Supervisor WMS Node Receiving
Supervisor Menu
dc3inbs
dc1shps Shipping Supervisor WMS Node Shipping
Supervisor Menu
dc3shps
dc1corpuser Enterprise Specific WMS Node User Menu
Warehouse User
dc3corpuser
xyzuser Enterprise User Enterprise User Menu
dc1u1 Node User WMS Lite Node User Menu
dc3u1
dc1m1 Mobile User WMS Mobile User Menu
dc1s1 Station User WMS Station User Menu
dc3s1

14 Implementation Guide
 Reference Implementation

Table 2–3 Users

Users User Group Menu
dc1admin System Administrator WMS System Admin Menu
dc3admin
ynwadmin Sterling Warehouse YNW System Admin Menu
Management System
System Administrator

2.3.3 For Saved Searches

All users are provided with favorites. These are based on individual users
and are saved searches that are expected to be used most often by that
user. Users can add or delete any search from these saved searches.

2.3.4 For Menu Groups

The application provides only the relevant menu options for each user,
based on their profile. The default menu is filtered according to the user’s
roles. The Reports menu displays for all supervisors.
The different menu groups provided are:

Table 2–4 Menu groups

Menu Permissions
WMS Node Warehouse Manager Menu Node user menu plus the
Applications Manager menu
WMS Node Inventory Supervisor Menu Node inventory and supply menu
options
WMS Node Receiving Supervisor Menu Inbound and inventory menu
options
WMS Node Shipping Supervisor Menu Outbound and other shipment
related menu items
WMS Node User Menu Standard node user menu
WMS Mobile User Menu Mobile menu
WMS Station User Menu Access to all stations and
approaching consoles
Enterprise User Menu Standard Enterprise user menu

Participant Modeling 15
Reference Implementation

Table 2–4 Menu groups

Menu Permissions
WMS System Admin Menu System Management Console,
Printers, Configuring Services,
Security Configurations (Users,
Groups, Menu), Agent Criteria
Setup, Inbound, Outbound UI’s
without save access.
Node Enterprise User Menu Access to standard node and
enterprise user menu

16 Implementation Guide
 3
Catalog and Product Management

This chapter explains the different Catalog and Product Management

configurations that can be performed using the Sterling Warehouse
Management System.
This chapter explains the Product Management and the Reference
Implementation provided with Sterling Warehouse Management System.

3.1 Item Classifications (Configuration Data)

Item classifications can be created to group a set of items logically. In
most warehouses item classifications are used for:
Q
Location storage preference: allowing only particular item
classifications to be stored in certain locations. For example, if the
location storage code is Refrigerated.
Q
Counting a particular classification of items.
The item classification hierarchy depends upon the type of items stored
in the warehouse.

3.2 Items
A product item is a physical unit that can be ordered, shipped, and
returned. A product item is uniquely defined by its item ID and unit of
measure. You can configure items, units of measure, master catalogs,
categories, classifications, and additional item attributes.
For more information about configuring product item inventory rules, see
the Sterling Global Inventory Visibility: Configuration Guide.

Catalog and Product Management 17

Reference Implementation

For more information about configuring product item sourcing rules, see
the Sterling Distributed Order Management: Configuration Guide.

3.3 Reference Implementation

This section explains the Reference Implementation for Product
Management, which is provided as part of Sterling Warehouse
Management System.

3.3.1 For Items (Master Data)

Table 3–1 shows the set of items which is provided with the Sterling
Warehouse Management System installation.

Table 3–1 Items

Item ID Number
Description (PREFIX-VARIABLE) of Items Comments Size/Weight
Normal NOR-00001 10 Normal item, 5x5x5/1LBS
neither
Tag-tracked nor
Serial-tracked.
Tag-controlled TAG-B-001 2 Tag-controlled 5x5x5/1LBS
item tracking
Batch Number
Serialized SZ-000001 2 Serialized item 5x5x5/1LBS
tracking Serials
during returns and
outbound
Serial-tracked ST-000001 2 Serial-tracked item 5x5x5/1LBS
Time-sensitive TS-000001 1 Time-sensitive 5x5x5/1LBS
item
Physical Kit PK-000001 1 Physical Kit item 5x5x5/1LBS
Logical Kit LK-000001 1 Logical Kit item 5x5x5/1LBS
Dynamic Physical DPK-00001 1 Dynamic Physical 5x5x5/1LBS
Kit Kit item
FIFO-tracked FIFO-0001 1 FIFO-tracked item 5x5x5/1LBS
Small container SMALL-CONTAINER 1 Item modeled as 10x15x10/1LBS
container

18 Implementation Guide
 Reference Implementation

Table 3–1 Items

Item ID Number
Description (PREFIX-VARIABLE) of Items Comments Size/Weight
Large container LARGE-CONTAINER 1 Item modeled as 10x15x20/2LBS
container
Component item COMP-0001 5 Component item. 5x5x5/1LBS
Tag-and Serial- TAGST-L01 1 Tag- and Serial- 5x5x5/1LBS
tracked tracked item
tracking lot
number.

Catalog and Product Management 19

Reference Implementation

20 Implementation Guide
 4
Warehouse Layout Configuration

This chapter explains the warehouse layout configuration and its

Reference Implementation provided by the Sterling Warehouse
Management System.

4.1 Warehouse Layout

The warehouse layout defines the physical layout and related attributes
of a warehouse.
This section describes some of the concepts related to the warehouse
layout.

4.1.1 Nodes
A Node (also called a warehouse) is an entity that receives or ships
inventory. A node belongs to an organization or enterprise, and may be
shared across all enterprises. For example, nodes are used by buyer
organizations for receiving inventory, and by seller organizations for
shipping inventory. A carrier organization, on the other hand, uses nodes
both for shipping and delivering inventory.
A node is defined for all types of warehouses, including distribution
centers, flow-through centers, returns or VAS centers, or third-party
distribution locations. For more information about defining a node, see
the Catalog Management: Configuration Guide.

4.1.2 Location Size Codes

A Location Size Code defines the capacity of a location. The capacity of a
location is specified by its length, width, and height.

Warehouse Layout Configuration 21

Warehouse Layout

4.1.3 Location Storage Codes

A Location Storage Code indicates the storage classification for a
location. Location storage code enables a warehouse to store all items of
a given storage profile at the same location. For example, inflammable
items are stored in locations equipped to handle fire hazards. Marking all
suitable locations with a certain storage code ensures that inflammable
items are stored safely at these fireproof locations.

4.1.4 Velocity Codes

Velocity Codes are attributed to a location. A velocity code associates the
location to a SKUs throughput. For example, fast moving items are
stored in the lower level locations or locations reachable by hand, in the
bulk zone.

4.1.5 Zones
A Zone classifies a set of locations that share common properties. A
warehouse is divided into multiple zones based on its attributes, like
package type and velocity codes. Inventory for a SKU is either stocked in
a specific zone or in multiple zones and locations. For example, case
storage and unit storage make separate zones. Camcorders are stored in
the lock and key zone, while television sets are stored in the bulk storage
zone.
A zone enables defining constraints for putaway, retrieval, and picking of
SKUs in the warehouse. Zone level constraints can also be applied on a
user using task management. For example, a user dedicated to pick only
in the refrigeration zone or a loose pick zone.
If a Zone contains a Location of VIRTUAL type, it is recommended that
locations of other types be avoided in the same zone.

4.1.6 Locations
A Location is the physical place where inventory is stored. A location
stores inventory of different sizes and classifications. For instance, a
location includes attributes like aisle number, bay number, and level
number. A location is classified as in-transit location, regular location,
virtual staging location, and dock location.

22 Implementation Guide
 Warehouse Layout

A location is always associated with a zone and a node. A location

number uniquely identifies a location in the warehouse. Typically, a
location number is a combination of the zone, aisle, bay, level and the
slot it belongs to.
A location is classified as:
Q
DOCK - when it is belongs to a dock location.
Q
INTRANSIT - when it is a mobile location. For example, the location
associated to a forklift.
Q
VIRTUAL - when it is associated to inventory that is deemed as not
being in the warehouse. For example, a bin location for variance
quantities.
Q
STAGING - when it is an intermediate location for a task. For
example, drop-off or floor locations.
Q
REGULAR - all other permanent and static storage locations.

4.1.7 Dock Scheduling

The Dock scheduling functionality of Sterling Warehouse Management
System enables you to manage the dock locations in a warehouse for
receiving inbound shipments and shipping outbound shipments. The dock
scheduling rule enables you to specify the number of days for which you
can take a dock appointment.
The dock scheduling functionality enables you to manage appointments.
Dock scheduling is based on the warehouse calendar associated with the
dock. This includes taking appointments for dock locations in the
warehouse to receive inbound shipments and ship outbound shipments.
Each appointment is assigned a unique reference number, called the
Appointment Number, with which the appointment can be traced.
For more information about dock locations, see the Sterling Warehouse
Management System: Configuration Guide.
For more information about scheduling dock appointments, see the
Sterling Warehouse Management System: User Guide.

Warehouse Layout Configuration 23

Warehouse Layout

4.1.8 Equipment Types

In a warehouse, different types of equipments are used to execute
various tasks. Examples of various types of equipment used in a
warehouse include sorter, tote, forklift, and pallet jack.
An individual equipment is identified through an equipment ID, and
categorized into one of the Equipment Types used in that warehouse. The
equipment used in a warehouse may be stationary (for example, a
sorter) or mobile (for example, Pallet Jack, Fork Lift, or Cart).
In Sterling Warehouse Management System, equipments are modeled in
one of the following ways:
Q
As a Set of Locations
The equipment that are stationary are typically modeled as locations.
Also certain mobile equipment that do not need to be tracked in
inventory like Fork Lifts or Pallet Jacks are modeled as Locations.
Q
As a License Plate
Mobile equipment that are physically moved around (between
different physical locations) and are required to be tracked at their
current location, are modeled as license plates. Examples of such
equipment include Carts and Totes.
Equipment modeled as license plates could be modeled as a case or
pallet depending on their size. For example, carts would be modeled
as Pallets, while totes would typically be modeled as cases.
Equipments modeled as license plates could have slots in them of
different sizes for carrying products. This information of slots is used
while s tasks that require these equipment for their execution. For
example, Cart manifest batch.
For more information about setting up an equipment type, see the
Setting Up an Equipment Type section in the Sterling Warehouse
Management System: Configuration Guide.

4.1.9 Stations
There are activities in a warehouse that are performed from stationary
locations. Some examples include Packing, VAS, Receiving, and
Manifesting.

24 Implementation Guide
 Reference Implementation

Each Station is associated with devices and labels or documents that are
printed on demand or automatically.

4.2 Reference Implementation

This section explains the Reference Implementation for Inventory Rules
Configuration, provided as a part of Sterling Warehouse Management
System.

4.2.1 For Warehouse Layout Configuration (Master Data)

This template provides the standard configuration for the Sterling
Warehouse Management System warehouse layout. The purpose of this
template is to accelerate the implementation of the Sterling Warehouse
Management System module.
The model warehouse layout is illustrated in Figure 4–1. This layout can
be further customized. Track B indicates than both pallets and cases are
tracked in the zone. Track N, does not track either cases or pallets.

Warehouse Layout Configuration 25

Reference Implementation

Figure 4–1 Warehouse Layout

4.2.2 For Location Size Codes

Conventionally, most Sterling Warehouse Management System
installations have standard Locations Size Codes. Location Size Codes are
typically configured in terms of standard pallet size.
Table 4–1 lists the default Location Size Codes provided with Sterling
Warehouse Management System.

Table 4–1 Location Size Codes

Location Size Code Size Weight
INFINITE N/A N/A
ONE-PALLET 40x48x72 1000 Pounds
TWO-PALLET (40x48)x2x72 2000 Pounds

26 Implementation Guide
 Reference Implementation

Table 4–1 Location Size Codes

Location Size Code Size Weight
EIGHT-PALLET (40x48)x2x(72)x4 (4 8000 Pounds
Levels)
TWO-CASE-STORAGE 20x24x36 300 Pounds

4.2.3 For Location Storage Codes

Certain items stored in the warehouse may need special treatment. To
facilitate this, we need locations with special Storage Codes.
The Location Storage configurations provided with Sterling Warehouse
Management System are REFRIGERATED and LOCK_AND_KEY.

4.2.4 For Dock Appointments Scheduling

Conventionally, most Sterling Warehouse Management Systems have
standard calendars for taking appointments. Dock appointments are
configured in terms of the standard warehouse calender.
Table 4–2 lists the default dock locations for DC1, along with their
associated calendars.

Table 4–2 Dock Locations and Calendars for DC1

Dock Location Calendar Dock Type
D1-010101 My Calendar is enabled Inbound and Outbound
D1-010102 My Calendar is enabled Inbound
D1-010103 My Calendar is enabled Outbound
D1-010104 Dock appointments cannot
be scheduled for this dock
location

Table 4–3 lists the default dock locations for DC3, along with their
associated calendars.

Warehouse Layout Configuration 27

Reference Implementation

Table 4–3 Dock Locations and Calendars for DC3

Dock Location Calendar Dock Type
D1-010101 DC3 Calendar is enabled Inbound and Outbound
D1-010102 DC3 Calendar is enabled Inbound
D1-010103 DC3 Calendar is enabled Outbound
D1-010104 Dock appointments
cannot be scheduled for
this dock location

4.2.5 For Velocity Codes

Velocity codes can be used to classify items based on their rate of
movement. Fast-moving items have the velocity code A.
The velocity codes provided with Sterling Warehouse Management
System are A, B, and C.

4.2.6 For Zones and Locations

Most implementations use one-up sequences for Locations and Zones.
The template provided by Sterling Warehouse Management System
follows the same strategy to create Locations and Zones.
The following Zones are pre-configured in Sterling Warehouse
Management System: BULK-ZONE1, BULK-ZONE2, BULK-ZONE3, DOCK-ZONE,
PACK-ZONE, VAS-ZONE, MANIFEST-ZONE, FORWARD-PICK-ZONE1 (Dedicated),
FORWARD-PICK-ZONE2 (Dynamic Slotting), and SHIP-SORT-ZONE.

Because most of our configuration data depends on Zones, they are

considered to be part of the configuration data. Locations, on the other
hand, are part of the master data.

4.2.7 For Equipment

The following standard equipment is considered to exist in the
warehouse:
Q
Flat Beds
Q
Fork Lifts
Q
Grab Trucks

28 Implementation Guide
 Reference Implementation

Q
Turret Trucks
Q
Single Slot Picking Carts
Q
Multi-Slot Picking Carts
Q
Shipment sorter.
All pieces of Equipment are associated with the same INTRANSIT location
having INFINITE capacity, except for the Multi Slot Picking Cart, which
has 16 locations in it, and the SHIPMENT-SORTER equipment, which has
20 locations in it.

4.2.8 For Devices

The warehouse also contains standard devices, such as printers and
weighing scales.

[Link] Printers
Table 4–4 shows the printers that are pre-configured with Sterling
Warehouse Management System.

Table 4–4 Printers

Printer Name Print Documents
HP-LASERJET-4300 PACKLIST, TASKLIST, VICS_BOL, COUNTSHEET,
RECEIVING_WORKSHEET, LTL_MANIFEST,
SHIPMENT_DOCUMENT, CERTIFICATE_OF_ORIGIN,
and COMMERCIAL_INVOICE_DOCUMENT
ZEBRA-140XIII CONTAINER_LABEL, UPS_PICKUP_SUMMARY,
UPS_CARRIER_LABEL, FEDEX_CARRIER_LABEL,
SPECIAL_TICKET_LABEL, WAVELABEL, AND
YNW_LPN_LABEL_DOCUMENT

[Link] Weighing Scale

Table 4–5 shows the weighing scale that is pre-configured with Sterling
Warehouse Management System:

Table 4–5 Weighing Scale

Name Description
Mettler Toledo Mettler Toledo weigh Scale

Warehouse Layout Configuration 29

Reference Implementation

4.2.9 For Stations

The standard stations provided by the Sterling Warehouse Management
System are:
Q
Pack Station
Q
Manifest Station
Q
Weigh Station
Q
Receive Station
Q
VAS Station

30 Implementation Guide
 5
Inventory Rules Configuration

Configuring Inventory Rules helps to track the inventory in a warehouse.

This chapter explains the inventory tracking attributes and its Reference
Implementation provided by the Sterling Warehouse Management
System.

5.1 Inventory Tracking Attributes

To track inventory in the warehouse, the inventory is identified by certain
attributes. This section explains these attributes.

5.1.1 Product Class

The Sterling Selling and Fulfillment Foundation identifies items as having
a Product Class. This attribute is mandatory on an order and is the most
important inventory attribute for an item.
Product Classes are typically used to indicate the condition of the
inventory for an item. For example, Good Quality or Refurbished.

5.1.2 Inventory Status

Inventory Status is an additional classification of inventory at a node.
The Inventory Status is directly connected to the availability of inventory.
Inventory Status is applied at the time of receiving, and during packing
or repair processes in a warehouse.

5.1.3 Inventory Adjustment Reasons

Inventory adjustments are associated with a reason code and reason
text. These codes are used as tracking mechanisms for the exceptions

Inventory Rules Configuration 31

Inventory Tracking Attributes

that require an adjustment. The inventory adjustment reason enables

tracking and reporting of adjustments at a reason code level.
Reason code values are also interfaced to HOST to ensure that
adjustments are attributed to the appropriate accounts.
Typically, inventory adjustment transactions are written for variances
during cycle count or exceptions where inventory is found or not found.

5.1.4 Inventory Status Transitions

Inventory should be considered available or unavailable for certain
operations based on the operations within the warehouse. For example,
inventory should be unavailable for orders until putaway is complete. As
soon as putaway is complete, the inventory should become available for
orders automatically, without any intervention from users.
To facilitate this, Inventory Statuses are assigned to inventory. The
Inventory Status of the inventory changes at different stages.
When inventory is received, it is assigned an appropriate Inventory
Status to show that the inventory is awaiting inspection. When the
inventory is moved to storage, the Inventory Status may change
appropriately.
Inventory Statuses can be associated with zones. In this case, whenever
a product moves into a particular zone, its Inventory Status gets
transitioned to the Inventory Status that the zone is associated with. So,
whenever a product is moved into the QC zone, its Inventory Status
changes to the Inventory Status associated with the QC zone, which may
indicate that the product is undergoing QC. When the product moves out
of the QC zone into storage, its Inventory Status changes to the
Inventory Status associated with the storage zone, which may indicate
that the product is available for orders. In case of products that fail QC,
they may be moved to the appropriate zone that is associated with an
Inventory Status to mark the products as damaged and thus unavailable,
or quarantined, or held until more QC is done on a larger sample.
If a product with the Inventory Status indicating that the product is
awaiting inspection is moved directly into storage, it retains its inventory
status. This is because no transition has been defined for the Inventory
Status of the storage zone, when a product with that Inventory Status
moves into storage. If the warehouse process so dictates, this can be
overwritten by setting an appropriate Inventory Status transition. In that

32 Implementation Guide
 Reference Implementation

case, products Putaway into the storage zone may become directly
available for orders, even though they have not cleared QC as yet.

5.2 Reference Implementation

This section explains the Reference Implementation for Inventory Rules
Configuration, which is provided as part of Sterling Warehouse
Management System.

5.2.1 For Product Class

The Product Classes configured as part of Sterling Warehouse
Management System are:
Q
FQ: stands for First Quality and indicates that inventory is in good
condition.
Q
FD: stands for Factory Defects and indicates that the inventory is
damaged.

5.2.2 For Inventory Status

The Sterling Warehouse Management System configurations for the
Inventory Status and associated Supply Type are shown inTable 5–1.

Table 5–1 Inventory Statuses

Status Description Supply Type

AI Awaiting-Inspection HELD

N Good ONHAND

QF QC-Failed HELD

QH QC-Hold HELD

QUH Quarantine Hold HELD

Inventory Rules Configuration 33

Reference Implementation

5.2.3 For Inventory Adjustment Reasons

The default configurations for Inventory Adjustment Reasons are shown
in Table 5–2.

Table 5–2 Inventory Adjustment Reasons

Reason Code Accounting bin (Y/N) Description
SHIP Used by the system
while confirming the
shipment.
RECEIPT Used by the system
while Receiving
PACK Y Used by the system
during the pack
process
INITIAL-LOAD Used by the system
while initially loading
the inventory into the
system.
CC Y Indicates that a
different bin location
is associated with the
Cycle Count
PC Y Indicates that a
different bin location
is associated with the
Physical Count
MISSING-STOCK Indicates that the
inventory is missing
OEM-DAMAGE Indicates that the
inventory is damaged
by the OEM.
DATA-ENTRY Indicates a Data Entry
error.
RECEIPT-ERROR Indicates an error
during the receiving
process
SHIP-ERROR Indicates an error
during the shipping
process

34 Implementation Guide
 Reference Implementation

Table 5–2 Inventory Adjustment Reasons

Reason Code Accounting bin (Y/N) Description
WHSE-DAMAGE Used if the item has
been damaged while
performing some
warehouse activities.
SCRAP Indicates if the item
has been scrapped.
PILFERAGE Indicates if the item
has been stolen.
OTHERS Indicates that the
adjustment is for any
other reason

5.2.4 For Inventory Transitions

The default configuration for inventory status transitions is as shown in
Table 5–3.

Table 5–3 Inventory Status transitions

Zones Transition
For QC Zones AI to QH

Inventory Rules Configuration 35

Reference Implementation

36 Implementation Guide
 6
Document Types

This chapter explains the Document Types provided with the Sterling
Warehouse Management System.

6.1 Document Types (Configuration Data)

Document types carry information through a configured business process
workflow. These documents are derived from base document types. A
base document type defines the business documents that the Sterling
Selling and Fulfillment Foundation handles and defines a common storage
structure for all the derived document types.
The following base document types are defined in the Sterling Selling and
Fulfillment Foundation:
Q
Order
Q
Load
Q
General
Q
Count
Q
Container
Q
Wave
Q
Work Order
Document types are specific business documents that are derived from a
base document type. For example, document types such as Sales Order
and Purchase Order are derived from the Order base document type.
For detailed information on document types, see the Catalog
Management: Configuration Guide.

Document Types 37
Document Types (Configuration Data)

As part of Sterling Warehouse Management System, a new Document

Type, Blind, has been created. This document type has configurations
similar to the Purchase Order Document Type. The only difference
between the two is that the Order is not available on the system for the
Blind Document Type. Therefore, in case of Blind Document Type, ASNs
can be created and received without the order information.
Table 6–1 shows the different document types provided with the Sterling
Warehouse Management System.

Table 6–1 Document Types

Document Type Description
0001 Sales Order
0003 Return Order
0005 Purchase Order
0006 Transfer Order
0010 Blind Receipt
0011 Blind Return
1001 Load
3001 Count
4001 Outbound Picking
5001 Container
7001 Work Order

38 Implementation Guide
 7
Productivity and Task Types

This chapter explains the Productivity and its Reference Implementation

provided by the Sterling Warehouse Management System.

7.1 Productivity
All the activities performed by the user are tracked at the activity level.
This is measured against productivity metrics associated with the activity.
This enables a warehouse to calculate labor efficiency and support
activity-based compensation to all users.
Each task type is associated with a productivity type. A productivity type
defines the Standard Allowable Minutes (SAM) and also enables you to
choose form a pre-defined set of references, such as, Shipment, Receipt,
and so forth. This helps you find out how much time it took to complete a
receipt and so on. For more information about Productivity, see the
Sterling Warehouse Management System: Configuration Guide.
Based on the task that you perform using the Mobile Application, the
system logs the productivity information. The mine productivity agent
then compiles this data and presents the information grouped by logical
references.
For paper-based tasks, users can report productivity at the console. This
information is used by the mine productivity agent.
Standard productivity functionality has been configured for the Sterling
Warehouse Management System. SAM is configured for each task type to
represent the physical process times.
The actual values for SAM can be determined only after the application
has been used in the floor of the warehouse. Rough estimates have been

Productivity and Task Types 39

Productivity Configurations

provided as a starting point, and will be adjusted over time for

benchmarks and challenges.
This chapter lists the task types, productivity types, and the SAM
provided as part of the configuration data in Sterling Warehouse
Management System.

7.2 Productivity Configurations

7.2.1 Agents
The agents configured for Productivity processing are:
Q
Productivity Purge
This agent purges productivity data for a period greater than the lead
days specified in the Productivity Purge criteria for a specific
Organization Code.
For more information about this agent, see the Sterling Warehouse
Management System: Configuration Guide.
Q
Mine Productivity
This agent captures the productivity information for all the tasks
performed within the Sterling Selling and Fulfillment Foundation Task
management framework. This information is extracted and
consolidated per user. The agent runs at some scheduled intervals,
for example as a end-of-day process. Every individual task in Sterling
Warehouse Management System captures its start and end time
automatically. The agent checks all completed tasks, that have not
been mined so far, collecting productivity metrics based on
productivity references relevant for that productivity type.
For more information about this agent, see the Sterling Warehouse
Management System: Configuration Guide.

40 Implementation Guide
 Reference Implementation

7.3 Task Configurations

7.3.1 Agents
The agents configured for Task processing are:
Q
Task Purge
This agent moves tasks that were created prior to thirty days and
that are in completed but cancelled status to the task history table.
This agent runs once at the end of each working day.
Q
Task History Purge
This agent purges tasks that were moved to the task history table
prior to thirty days. This agent runs once at the end of each working
day.

7.4 Reference Implementation

This section explains the Reference Implementation for Productivity,
which is provided as part of Sterling Warehouse Management System.

7.4.1 For Productivity Types (Configuration Data)

The consolidated list of Productivity Types is shown in Table 7–1.

Table 7–1 Productivity Types

Productivity Type Description
COUNT Count
PACKING Packing
VAS Value-Added Services
RECEIVE Receiving
PUTAWAY Putaway
RETRIEVAL Retrieval
PICKING_AT_BULK Picking at bulk location
PICKING_ACTIVE_AREA Forward pick area picking
REPLENISHMENT Replenishment

Productivity and Task Types 41

Reference Implementation

Table 7–1 Productivity Types

Productivity Type Description
MANIFESTING Manifesting
TRAILER_UNLOAD Trailer Unload

7.4.2 For Task Types

The consolidated list of Task Types is:

Table 7–2 Productivity Task Types

Associated Productivity
Task Type Type Description
COUNT0001 COUNT Cycle Count, Mobile Application-based.
COUNT0002 COUNT Cycle Count to be performed using paper.
VARIANCE01 COUNT Cycle Count, Variance Task, Mobile
Application-based.
VARIANCE02 COUNT Cycle Count, Variance Task to be performed
using paper.
COUNT0003 COUNT Physical Count Mobile Application-based.
COUNT0004 COUNT Physical Count to be performed using paper.
COUNT0005 COUNT Task Type to perform second-level Physical
Count. The Count Task is performed using
the Mobile Application.
COUNT0006 COUNT Task Type to perform second-level Physical
Count. The Count Task is performed using
Printed Count Sheets.
VARIANCE03 COUNT Physical Count, Variance Task, Mobile
Application-based.
VARIANCE04 COUNT Physical Count, Variance Task to be
performed using paper.
REPL-0001 REPLENISHMENT Paper-based Replenishment Task type.
REPL-0002 REPLENISHMENT Mobile Application-based Replenishment
Task Type
MOVE-0001 PUTAWAY Paper-based Move Request Task type.

42 Implementation Guide
 Reference Implementation

Table 7–2 Productivity Task Types

Associated Productivity
Task Type Type Description
MOVE-0002 PUTAWAY Mobile Application-based Move Request
Task Type
PICK0001 PICKING_AT_BULK Full Case Pick
PICK0002 PICKING_ACTIVE_AREA Less than Case Pick
PICK0003 PICKING_AT_BULK Pick to Pallet
PICK0004 PICKING_ACTIVE_AREA Pick from Forward Pick Area
PICK0005 PICKING_AT_BULK Pick for Parcel
PICK0006 PICKING_AT_BULK Pick for LTL/TL shipments
VAS-RETR01 RETRIEVAL VAS Retrieval, Mobile Application
VAS-RETR02 RETRIEVAL VAS Retrieval paper
VAS-PUT-01 PUTAWAY VAS Putaway, Mobile Application
VAS-PUT-02 PUTAWAY VAS Putaway, paper

7.4.3 For SAM Definition (Configuration Data)

The following tables list the initial SAM values that are provided as a part
of the configuration data. These are rough estimates. The actual values
for SAM can be determined only after the application has been used in
the floor of the warehouse. The warehouse needs to be monitored to get
the SAM for each of the productivity types.

Table 7–3 SAM Definitions

SAM per SAM per
source target SAM per SAM per SAM per
Productivity Types Location Location Task CASE PALLET
COUNT 1.50 0.00 0.00 0.00 0.00
PACKING 0.00 0.00 0.00 0.50 0.50
VAS 0.00 0.00 0.00 0.00 0.00
PUTAWAY 1.00 1.5 0.00 0.75 1.50
RETRIEVAL 1.00 1.5 0.00 0.75 1.50

Productivity and Task Types 43

Reference Implementation

Table 7–3 SAM Definitions

SAM per SAM per
source target SAM per SAM per SAM per
Productivity Types Location Location Task CASE PALLET
RECEIVE 0.00 0.00 0.00 1.50 1.50
PICKING_AT_BULK 0.75 0.00 1.00 0.00 0.00
PICKING 0.75 0.00 1.00 0.00 0.00
_ACTIVE_AREA
REPLENISHMENT 1.00 1.5 0.00 0.75 1.50
MANIFESTING 0.00 0.00 0.00 0.50 0.50
TRAILER_UNLOAD 0.00 0.00 0.00 0.50 1.00

Table 7–4 More SAM Definitions

SAM per SAM per SAM per
source target SAM per productivity
Productivity Types SAM per UNIT Aisle Aisle Item BATCH
COUNT 0.00 0.00 0.00 1.00 1.00
PACKING 0.00 0.00 0.00 0.00 1.00
VAS 0.50 0.00 0.00 1.00 2.00
PUTAWAY 0.00 0.25 0.50 0.00 2.00
RETRIEVAL 0.00 0.25 0.50 0.00 2.00
RECEIVE 0.00 0.00 0.00 0.50 1.00
PICKING_AT_BULK 0.25 0.50 0.00 0.00 3.00
PICKING 0.25 0.50 0.00 0.00 3.00
_ACTIVE_AREA
REPLENISHMENT 0.00 0.25 0.50 0.00 2.00
MANIFESTING 0.00 0.00 0.00 0.00 1.00
TRAILER_UNLOAD 0.00 0.00 0.00 0.50 1.00

44 Implementation Guide
 Reference Implementation

Table 7–5 SAM Definitions, Planning

Productivity Types SAM per Task SAM per CASE SAM per PALLET
PACKING 0.00 1.00 1.00
PICKING_AT_BULK 2.00 0.00 0.00
PICKING _ACTIVE_AREA 2.00 0.00 0.00
MANIFESTING 0.00 1.00 1.00
OUTBOUND_LABOR 0.00 1.50 0.00
VAS 0.00 0.00 0.00

Table 7–6 More SAM Definitions, Planning

SAM per
productivity
Productivity Types SAM per UNIT SAM per Item BATCH
PACKING 0.00 0.00 2.00
PICKING_AT_BULK 0.50 0.00 4.00
PICKING _ACTIVE_AREA 0.50 1.50 4.00
MANIFESTING 0.00 0.00 2.00
OUTBOUND_LABOR 0.50 0.50 4.00
VAS 1.00 2.00 3.00

7.4.4 Task Execution Exceptions

The list of Task Execution Exceptions is:

Table 7–7 Task Execution Exceptions

Exception
Code Description Exception Type
NOINV Inventory Not Available Pick
SHORTPICK Short Pick Pick

Productivity and Task Types 45

Reference Implementation

46 Implementation Guide
 Part II
IBM Sterling Warehouse Management
System Processes and Features

This part of the manual explains all the processes that are provided with
the Sterling Warehouse Management System solution.
Sterling Warehouse Management System provides the following features
and processes in order to meet your business requirements:
Q
Receive and Putaway
Q
Location Mass Maintenance
Q
Managing Activity Demands
Q
Quality Control
Q
Vendor Compliance
Q
Move Request
Q
Count
Q
Outbound
Q
Replenishment
Q
Value-Added Services
Q
Returns
Q
Dynamic Item Velocity Calculation
Q
Integration With Slotting Engines

47
48 Implementation Guide
 8
Receive and Putaway

The Sterling Warehouse Management System enables you to control the

receipt process with information that is available in a warehouse. Sterling
Warehouse Management System supports the least automated
warehouse through paper-based processes and all warehouses up to the
most automated, involving Material Handling Equipment (MHE) for
receipts.
This chapter explains the Receiving process and solution offered by
Sterling Warehouse Management System.

8.1 Receiving Processes

The Receiving processes followed in a mid-sized Finished Goods DC are:
Q
Receipts made for a PO:
The PO can be received with or without an ASN created for it.
Q
Receipts made without any order:
The warehouse receives ASNs that may be either sent through e-mail
or fax, or through EDI. In this case, receipts are made against the
ASN. The same process is followed for receiving Transfer Orders.
Q
Receipts made as Blind Receipts:
The product arrives in the warehouse without a PO or ASN. The
warehouse has the capability to record the receipt without entering
the ASN information.
The arrival of the order or shipment is recorded on the system by
starting the receipt of the order or shipment. A Receiving Worksheet is
printed automatically when the Receipt starts.

Receive and Putaway 49

Receiving Processes

Sterling Warehouse Management System assumes that the products

received are appropriately labeled. If items are received with no LPN
information, a new LPN is created and applied to the inbound product.
For non-LPN based Receiving, the products are sorted into individual
items from cases or pallets, for ease of counting. The counts are
recorded against the Receiving Worksheet.
Containers with LPNs are scanned for receipt through a Receiving station.
The order or shipment is identified for receipt before the containers are
scanned. It is expected that the lot serial information is supplied for the
item in the warehouse as part of the inbound shipment. Lot or serial
information is expected to be either available with the LPN or not
required.
Containers with LPN are received and Putaway to a separate bulk storage
zone.

Note: The Receiving Process detailed in the following two

sections applies to the following document types: Purchase
Orders, Transfer Orders, and Blind Receipts.

8.1.1 Mobile Application-Based Receiving Process

Containers with LPNs are scanned for receipt using the Mobile
Application. Orders or shipments are identified for receipt before the
containers are scanned. It is expected that the lot information of the item
is supplied as a part of the ASN. The lot information is expected to be
either available with the LPN or not required. If the LPN is not available,
a new LPN is generated and quantity received is confirmed.
Inventory is received into the location associated with the Receiving Dock
and is visible through the Location Inventory Console.
The Receiving process using the Mobile Application is:
1. Log in to the Mobile Application and select the shipment to receive.
If the ASN information is not available, create a shipment with
appropriate shipment lines and select the shipment to receive.
In case of Blind Receipts, you can create a shipment without any
shipment line.
2. If the LPN information is available, scan the LPN from the outer box.

50 Implementation Guide
 Receiving Processes

3. If the LPN information is not available,

Q
Apply a pre-printed LPN to the box.
Q
Scan the item, tag or serial, and quantity.
4. Close the receipt. The Putaway tasks are generated.

[Link] Opportunistic Cross-Docking

This section explains the opportunistic cross-docking feature provided by
Sterling Warehouse Management System. This feature enables the
warehouse manager to reduce the effort required for putaway and
picking.
The opportunistic cross-docking process using the Mobile Application is:
1. The user receives the case or pallet.
2. The system identifies that a cross-docking opportunity exists for the
case or pallet if:
Q
The case or pallet is not a multi-SKU container
Q
The case or pallet does not contain time-sensitive items
Q
The case or pallet does not contain FIFO-tracked items
Q
The case is not within a pallet
Q
The case or pallet does not contain child containers
Q
The outbound pick task is in Open or Held for Inventory Shortage
status and does not have any requested tag or serial numbers
Q
The quantity required for the pick task is greater than or equal to
the quantity received, for loose picking
Q
The quantity required for the pick task is equal to the quantity
received, for suggested LPN
3. If a cross-docking opportunity exists for the case or pallet,
a. The source location for the pick task is replaced by the receiving
dock location
b. The system suggests the receiver to separate the case and pallet
from the other receipts
c. The system suggests a deposit task.

Receive and Putaway 51

Receiving Processes

d. The receiver deposits the case or pallet into the system-suggested

location.
e. Once cross docking is done for a case or pallet, the putaway
request is not generated.

Note: Opportunistic cross-docking is not performed for

Replenishment and Retrieval Tasks.
Opportunistic cross-docking is performed only for the
Mobile Application-based warehouse.

8.1.2 Paper-Based Receiving Process

While receiving with an order, receipts are recorded through the
Record/Report Receipt action available in the Order, Returns, and Receipt
consoles.
While receiving with an ASN, receipts are started through the Start
Receipt action available in the Shipment Console and recorded through
the Receive action. For Blind Order receipts, if the shipment information
is not available, you can create a shipment without any shipment line.
In both cases, the details of the receipt are entered and the receipt for
the order or shipment is then marked closed in the Receipt Console. The
closure of the receipt automatically triggers the generation of Putaway
tasks.
In the Paper-based Receiving process, Sterling Warehouse Management
System assumes that receipts are performed in loose SKUs and not in
LPNs. However, you may also choose to receive in LPNs.
The Receiving process using paper is:
1. The Receiving Worksheet is printed and given to the user.
2. The user records the receipt information in the Receiving Worksheet.
3. If receiving with order, the user records the receipt by clicking the
Report/Record Receipt action in the Receipt console.
4. If receiving with ASN, the user starts the receipt by clicking the Start
Receipt action in the Shipment Console and records the receipt by
clicking the Receive action.

52 Implementation Guide
 Receiving Configurations

5. The user closes the receipt manually using the Close Receipt action in
the Receipt Console.
6. The Putaway tasks are generated on closing the receipt and the
Putaway Batch Sheet is printed.

8.2 Receiving Configurations

This section explains the various configurations that may be done for the
Receiving process.

8.2.1 Receiving Pipeline

Figure 8–1 illustrates the Receiving Pipeline.

Figure 8–1 Receiving Pipeline

8.2.2 Activities
Activities in the warehouse are grouped into Activity Groups. The Sterling
Warehouse Management System provides a pre-defined set of activity
groups for a warehouse. Examples of activity groups include Receipt,
Inspection, Value Added Services, and Packing.
Each activity group is associated with activity codes that define each
activity that is performed. The Receipt activity group has these activities:

Receive and Putaway 53

Receiving Configurations

Divert for Quality Check, Receive, Pre-Receive, Receive-Return, Trailer

Unloading, and QC Retrieval.

Note: Activity Codes may be defined only when the

Warehouse Management System tree is loaded for Node
and Hub combination.

8.2.3 Setting Up Receiving Preferences

This section explains how to set up your Receiving Preferences for
receiving.

[Link] Enterprise-Level Configurations

To set up Enterprise-level Receiving Preferences:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. Now, from the Applications Manager menu bar, select Application >
Supply Collaboration.
4. From the tree in the application rules side panel, select Receiving >
Receiving Preferences. The Receiving Preferences screen displays.
5. In the Search Results panel, click . The Receiving Preference
Details pop-up window displays.
6. Enter information into the applicable fields.
For more information and field value descriptions, see the Sterling
Supply Collaboration: Configuration Guide.
7. Click .

[Link] Node-Level Configurations

To set up Node-level Receiving Preferences:
1. Log into the application as the Node user.

54 Implementation Guide
 Receiving Configurations

2. From the Application Console menu bar, select Configuration >

Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Receiving Preferences.
5. The Receiving Preferences: Purchase Order screen displays.
6. In the top panel, select the appropriate options for building pallets,
building cases, Disposition Code for receiving with QC, Disposition
Code for receiving without QC, and preference for closing receipt by
an agent.
Receiving can be done on Cases, Pallets, or both. Most warehouses
follow the process of not verifying the case content. The Case Content
Verification can be set while creating the ASN.
Table 8–1 lists the configurations set as a part of the Receiving
Preferences.

Table 8–1 Receiving Preferences Configuration

Case/Pallet Build Preference
Case Optional
Pallet Mandatory

In addition to this, the Disposition Code is set up as follows:

Q
Disposition Code for Receipt with QC: Requires Inspection
Q
Disposition Code for Receipt without QC: Good
For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. The lower panel displays the Enterprise-Level Receiving Preferences
that you have set up.
8. Click .

Receive and Putaway 55

Receiving Configurations

Note: Click to view the Receiving Preferences Details

screen that displays the detailed preferences set for
receiving the item, along with the QC percentage set for
the item.

8.2.4 Setting Up the Putaway Preferences

To set up the Putaway Preferences:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Putaway Preferences. The Putaway Preferences screen is displayed.
Use this to set the Putaway Preferences for single SKU, multi-SKU
container, and container with unknown contents.
5. Alternatively, click in the Activity Search screen to access the
Putaway Preferences screen.
6. In the Putaway Preferences screen, select the appropriate tab,
depending on whether you are setting up Putaway Preferences for
Single SKU, Multi-SKU Container, or Container with unknown
contents.
7. Click . The Putaway Preference Details screen displays.
8. In the Activity Code drop-down list, select the code to move the
products to storage.
9. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
10. Click .

56 Implementation Guide
 Receiving Configurations

11. To configure task types for putaway, click . The Putaway Strategy
screen displays. Configure the task types.
For more information about setting up putaway strategies, see the
Sterling Warehouse Management System: Configuration Guide.

8.2.5 Setting up Receiving Disposition Codes

This section explains how to create Disposition Codes. It also explains
how to associate the Disposition Code with a Product Class, with
disposition transition statuses, for receiving with QC, and with an
Inventory Status.

[Link] Creating the Receiving Disposition

This section explains how to create the Receiving Disposition.
Disposition Codes can be created to be assigned to the inventory at
different stages, such as receiving, during QC, and after QC. You can
have different Disposition Codes, depending upon whether the products
passed QC, failed QC, and so forth.
To create the Disposition Code to assign to the items in QC:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Receiving Disposition. The
Disposition List: Purchase Order screen is displayed.
5. In the Disposition List: Purchase Order screen, click . The
Disposition Details pop-up window displays.
6. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
7. Click .

Receive and Putaway 57

Receiving Configurations

A receiving disposition is created that can be associated with the

inventory during receiving.

[Link] Associating the Disposition Code with a Product Class

To associate the Disposition Code with a Product Class:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application > Supply
Collaboration.
4. From the tree in the application rules side panel, select Document
Specific > Receipt > Receiving Disposition. The Disposition List:
Purchase Order screen displays.
5. In the Disposition List: Purchase Order screen, click . The
Disposition Details pop-up window displays.
6. In the Product Class drop-down list, select the appropriate Product
Class for the Disposition Code.
7. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
8. Click .
The selected Disposition Code is now associated with the specified
Product Class. Whenever a product is dispositioned to the selected
Disposition Code, the Product Class automatically changes to the Product
Class that you specified here.

[Link] Associating the Disposition Code with

Disposition Transition statuses
To associate the Disposition Code with disposition transition statuses:
1. Follow steps 1-5 in Section [Link], "Associating the Disposition Code
with a Product Class".
2. In the Receiving Disposition drop-down list of the Disposition
Transitions pane, select the appropriate Inventory Statuses.

58 Implementation Guide
 Receiving Configurations

3. Click .
The selected Disposition Code is now associated with the specified
disposition transition statuses. The products being dispositioned to this
Disposition Code are assigned these Inventory Statuses consecutively,
until they reach the final disposition.

[Link] Associating a Disposition Code for Receipt with QC

To associate a Disposition Code for receiving with QC:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Receiving Preferences.
5. The Receiving Preferences: Purchase Order screen displays.
6. In the Disposition Code for Receipt with QC, enter the appropriate
Disposition Code. During receiving, this Disposition Code is assigned
to all items that require QC.
7. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
8. Click .

Note: Click to view the Receiving Preferences Details

screen that displays the detailed preferences set for
receiving the item, along with the QC percentage set for
the item.

[Link] Associating the Disposition Code with an Inventory Status

The Disposition Codes enable inspectors to utilize their own terminology,
instead of understanding inventory and storage implications.

Receive and Putaway 59

Receiving Configurations

Inventory is received with the specified Product Class and Inventory

Status of the Disposition Code entered.
If the Product Class is not specified, the Product Class from the Purchase
Order or the default Product Class from the item is used. It is mandatory
to have the Product Class specified at one of these levels.
To associate the Disposition Code with an Inventory Status:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Disposition Codes.
5. The Receiving Disposition: Purchase Order screen is displayed.
6. From the Inventory Status drop-down list, select the Inventory Status
to associate with the Disposition Code.
For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. Click .

8.2.6 Inventory Status Transitions

Inventory should be considered available or unavailable for certain
operations. For example, inventory should be unavailable for orders until
putaway is complete. As soon as putaway is complete, the inventory
should become available for orders automatically, without any
intervention from users.
To facilitate this, Inventory Statuses are assigned to inventory. The
Inventory Status of the inventory changes at different stages.
When inventory is received, it is assigned an appropriate Inventory
Status to show that the inventory is awaiting inspection. When the
inventory is moved to storage, the Inventory Status may change
appropriately.

60 Implementation Guide
 Receiving Configurations

Inventory Statuses can be associated with zones. In this case, whenever

a product moves into a particular zone, its Inventory Status gets
transitioned to the Inventory Status that is associated with the zone. So,
whenever a product is moved into the QC zone, its Inventory Status
changes to the Inventory Status associated with the QC zone, which may
indicate that the product is undergoing QC. When the product moves out
of the QC zone into storage, its Inventory Status changes to the
Inventory Status associated with the storage zone, which may indicate
that the product is available for orders. In case of products that fail QC,
they may be moved to the appropriate zone that is associated with an
Inventory Status to mark the products as damaged and thus unavailable,
quarantined, or held until more QC is done on a larger sample.
If a product with the Inventory Status indicating that the product is
awaiting inspection is moved directly into storage, it retains its Inventory
Status. This is because no transition has been defined for the Inventory
Status of the storage zone, when a product with that Inventory Status
moves into storage. If the warehouse process so dictates, this can be
overwritten by setting an appropriate Inventory Status transition. In this
case, products that are putaway into the storage zone may become
directly available for orders, even though they have not yet cleared QC

8.2.7 Agents
The agents configured for the Receiving processing are:
Q
Purge Receipt
This agent purges completed receipts. This agent is generally
triggered once in ten days or based on the receipt volume.
Q
Receipt Complete
This agent completes the receipts. This agent is generally triggered
once at the end of each working day.
For more information about these agents, see the Sterling Warehouse
Management System: Configuration Guide.
Q
Putaway Complete
This agent marks the completion of putaway tasks for a receipt.

Receive and Putaway 61

Receiving Configurations

[Link] Putaway Complete Agent

This agent marks the completion of putaway tasks for a receipt and
changes the status of the receipt to Putaway Complete.

Attributes
Table 8–2 lists the attributes for the Putaway Complete agent.

Table 8–2 Putaway Complete Agent Attributes

Attribute Value
Transaction Name Putaway Complete
Transaction ID PUTAWAY_COMPLETE.[Link]
Base Process Type None
Base Document Type None
Abstract Transaction None
APIs Called getReceiptDetails
getNodeInventory
User Exits Called None

Criteria Parameters
Table 8–3 lists the criteria parameters for the Putaway Complete agent.

Table 8–3 Putaway Complete Agent Criteria Parameters

Parameter Description
Action Required. Triggers the transaction. If left blank, it
defaults to Get, the only valid value.
CollectPendingJobs If this parameter is set to N, the agent does not collect
information on the pending jobs for this monitor. This
pending job information is used for monitoring the
monitor in the System Management Console.
Number of Records To Optional. Number of records to retrieve and process at
Buffer one time. If left blank or specified as 0 (zero), it
defaults to 5000.

62 Implementation Guide
 Receiving Configurations

Table 8–3 Putaway Complete Agent Criteria Parameters

Parameter Description
Next Task Queue Optional. Specifies in hours how long a failed task
Interval should be suspended before it is considered for
reprocessing. Defaults to 5 hours.
ColonyId The colony to be synchronized.
Initially, you must run the agent on the DEFAULT
colony provided by the Selling and Fulfillment
Foundation installation so that it populates the
PLT_COLONY_MAP table. After this, you can run the
agent on another ColonyId.

Statistics Tracked
None

Pending Job Count

For this transaction, the pending job count is the number of receipts for
which receiving is complete.

Events Raised
The following events are raised by this time-triggered transaction:

Table 8–4 Events Raised by the Putaway Complete Agent

Template
Transaction/Event Key Data Data Published Support?
ON_SUCCESS None YNW_PUTAWAY_COM Yes
PLETE.ON_SUCCESS.
xml

8.2.8 Services
The services provided for the Receiving process are:
Q
Generate Putaway Request
This service generates the requests for putaway tasks once receipt is
completed.

Receive and Putaway 63

Receiving Configurations

Q
Register Activity Demand For QC
This service computes the QC quantity (quantity of the products
received that needs to be diverted to the QC Zone for QC) and
creates an activity demand for it.
Q
Register Activity Demand and Print Receiving Worksheet
This service computes the QC quantity and prints it on the Receiving
Worksheet. It also creates an activity demand for the QC quantity.

Note: These services are already activated if you have

installed the factory defaults with the events turned on.

Q
YNW_ Cross Dock Inventory_91
This service identifies tasks on which opportunistic cross-docking can
be performed, replaces the source location specified for the selected
task with the dock location where the inventory is received, and
replaces the suggested LPN for the selected task by the LPN received.
Q
YNW_Generate Putaway Request_ 91
This service generates the requests for putaway tasks for cases and
pallets if cross docking is not done. Associate the
YNW_CrossDockInventory_91 service if putaway has to be called for
non cross-docked LPNs.

[Link] Generate Putaway Request

When a receipt is completed, the ON_RECEIPT_COMPLETE event of the
RECEIPT_COMPLETE transaction is raised, which invokes the
GeneratePutawayRequest service.
The GeneratePutawayRequest service then initiates the generation of the
requests for putaway tasks.
To activate the GeneratePutawayRequest service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_RECEIPT_COMPLETE event with the action Putaway
products on receipt, which invokes the GeneratePutawayRequest
service.

64 Implementation Guide
 Receiving Configurations

[Link] Register Activity Demand For QC

When a receipt is started, the ON_START_RECEIPT event of the
START_RECEIPT transaction is raised, which invokes the
YNW_RegisterActivityDemandForQC_91 service.
The YNW_RegisterActivityDemandForQC_91 service initiates the
computation of the quantity of product that needs to be diverted for a
shipment or order, based on the QC classification and QC percentage
setup. It then creates an activity demand for the same. During Putaway
this quantity of the product is diverted to the QC Zone for QC.
To activate the YNW_RegisterActivityDemandForQC_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_START_RECEIPT event with the action Register
Activity Demand For QC, which invokes the
YNW_RegisterActivityDemandForQC_ 91 service.

[Link] Register Activity Demand and Print Receiving Worksheet

When a receipt is started, the ON_START_RECEIPT event of the
START_RECEIPT transaction is raised, which invokes the
YNW_CompositeServiceOnStartReceipt_91 service.
The YNW_CompositeServiceOnStartReceipt_91 service initiates the
computation of the quantity of product that needs to be diverted for a
shipment or order, based on the QC classification and QC percentage
setup. It then creates an activity demand for the same. The QC
percentage computed is then printed on the Receiving Worksheet.
To activate the YNW_CompositeServiceOnStartReceipt_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_START_RECEIPT event with the action YNW CalcQC
And Print Recv WS (91), which invokes the
YNW_CompositeServiceOnStartReceipt_91 service.

[Link] YNW_ Cross Dock Inventory_91

The YNW_CrossDockInventory_91 service is a synchronous service.

Receive and Putaway 65

Receiving Configurations

Associate the YNWCrossDoc action with On Case Receipt or On Pallet

Receipt events. This action invokes the YNW_CrossDockInventory_91
service.
The YNW_CrossDockInventory_91 service performs the following:
1. Chooses a task based on pre-defined conditions.
For more information about the condition. see Section [Link],
"Opportunistic Cross-Docking".
2. Replaces the source location specified for the selected task with the
dock location where the inventory is received.
3. Replaces the suggested LPN for the selected task by the LPN
received.

[Link] YNW_Generate Putaway Request_ 91

When a case or pallet is closed, the ON_CASE_RECEIPT or
ON_PALLET_RECEIPT event of the Receive transaction is raised.
Associate the YNW_Putaway prodcuts on receipts action with On Case
Receipt or On Pallet Receipt events along with YNWCrossDock action.
This action invokes the YNW_GeneratePutawayRequest_91 service. This
service generates the requests for putaway tasks for case or pallet if
cross docking is not done.
Associate the YNW_GeneratePutawayRequest_91 service with
YNW_CrossDockInventory_91 service if putaway has to be called for non
cross-docked LPNs.
To activate the YNW_GeneratePutawayRequest_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_CASE_RECEIPT or ON_PALLET_RECEIPT event with
the YNW_Putaway products on receipt action, which invokes the
YNW_GeneratePutawayRequest_91 service.

66 Implementation Guide
 Managing the Receiving and Putaway Process on the Warehouse Floor

Note: The YNW_Putaway products on receipt action

should be invoked after invoking the YNWCrossDock
action.

8.2.9 Prints
The YNW_PrintReceivingWorkSheet_91 service has been provided, which
prints the Receiving Worksheet.

8.2.10 Productivity
For all tasks, such as, Pre-Receiving, Receiving, and Putaway associated
with Receiving, the productivity can be determined, based on the
Standard Allowable Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

8.3 Managing the Receiving and Putaway Process

on the Warehouse Floor
You can use the Application Console and the Mobile Application to
perform the Receiving and Putaway tasks. This section explains the UI
flow while performing receiving and putaway using Purchase Orders and
ASNs.

8.3.1 Receiving and Putaway Flow Using an Order

The UI flow for Receiving and Putaway using an Order is explained in this
section.

[Link] Receiving Process

Follow these steps in the Receiving process:
1. Start the Receipt from the Inbound Order console or Returns Console
using the Report/Record Receipt action. The Start Receipt pop-up
window displays.
2. Enter the details required, and start the receipt by clicking Save. The
Receive screen displays.

Receive and Putaway 67

Managing the Receiving and Putaway Process on the Warehouse Floor

For more information about the fields, see the Sterling Warehouse
Management System: User Guide.
3. In the Receive screen, enter the appropriate Disposition Code for
products and click Save.
This step needs to be performed using the Mobile Application if you
are using the Mobile Application for receiving.
4. In the Receipt Console, close the receipt by clicking Close Receipt.

[Link] Putaway Process

When the receipt is closed, putaway tasks are automatically generated
by the system. If you have configured the QC percentage, part of the
receipt is diverted to the QC zone. The rest may be diverted to storage.
If you have not configured the QC percentage, the entire receipt is
diverted to storage.

8.3.2 Receiving and Putaway Flow Using ASNs

The UI flow for Receiving and Putaway using an ASN is explained in this
section.

[Link] Receiving Process

Follow these steps in the Receiving process:
1. Start the Receipt from the Inbound Order Shipment Details screen in
the Shipment Console using the Start Receipt action. The Start
Receipt pop-up window displays.
2. Enter the details required, and start the receipt by clicking Save.
If you are using the Mobile Application for receiving, start receiving
using the Mobile Application. Otherwise, follow the steps given below:
3. Click the Receive action. The Receive Details screen displays.
4. In the Receive screen, enter the Disposition Code for products
requiring inspection (REQ-INSP) and click Save.
This step needs to be performed using the Mobile Application if you
are using the Mobile Application for receiving.
5. In the Receipt Console, close the receipt by clicking Close Receipt.

68 Implementation Guide
 Reference Implementation for Receiving

[Link] Putaway Process

When the receipt is closed, putaway tasks are automatically generated
by the system. If you have configured the QC percentage, part of the
receipt is diverted to the QC zone. The rest may be diverted to storage.
If you have not configured the QC percentage, the entire receipt is
diverted to storage.

8.4 Reference Implementation for Receiving

This section explains the Reference Implementation provided by Sterling
Warehouse Management System for Receiving.

8.4.1 Inbound Rules Configuration

This section describes the inbound rules configured in Sterling Warehouse
Management System.

[Link] Putaway Preferences

Once shipments are received, they are configured to automatically
generate tasks for putaway. The service to generate a putaway request is
configured as a part of the receipt transaction, on closure of the receipt.
Tasks are configured as one-step tasks. For all the task types, the
Execute Through Drop Off flag is set to “N”. Warehouses may manually
stage products in staging locations due to equipment constraints in the
destination aisle.
The considerations for putaway include:
Q
Location capacity.
Q
Putaway sequence.
Q
Consolidation opportunity along with locations that have the same
item, otherwise the items are placed in an empty location.
Q
Enterprise or other constraints.
Q
Location and item storage preferences based on Item Classification
(For example, Storage Type is Refrigerated).
Q
Zone–Task type preference.
Q
Receiving preference for QC based on Enterprise, Vendor and Item
Classification (For example, Product Line is PL001).

Receive and Putaway 69

Reference Implementation for Receiving

Table 8–5 shows the Sterling Warehouse Management System

configurations for Putaway Preferences.

Table 8–5 Putaway Preferences

Activity UOM Zones
Moving To Storage Less than Case FORWARD PICK
ZONES
Moving To Storage CASE BULK ZONES Tracking
Cases
Moving To Storage PALLET BULK ZONES Tracking
Pallets

[Link].1 Putaway Task Types

The Putaway strategy created makes use of task types to execute the
Putaway process.
The task types created to execute the Putaway process in the warehouse
are shown in Table 8–6.

Table 8–6 Putaway Task Types

Task Type Description
MOVE-0001 Paper-based Move Request
MOVE-0002 Mobile Application-based Move Request

[Link].2 Putaway Strategy

For paper-based warehouses, the Task Type MOVE-0001 is used. For
warehouses using the Mobile Application to execute the Putaway Tasks,
the Putaway strategy is configured to use the MOVE-0002 Task Type.

[Link] Node Receiving Preferences

Warehouses using the Mobile Application can receive cases, pallets, or
both. Most warehouses follow the process of not verifying the content of
cases.
Table 8–7 lists the configurations set as a part of the Receiving
Preferences for Purchase Orders, Transfer Orders, and Blind Receipts.

70 Implementation Guide
 Reference Implementation for Receiving

Table 8–8 lists the configurations set as a part of the Receiving

Preferences for Return Orders and Blind Returns, for both paper-based
warehouses and warehouses using the Mobile Application.

Table 8–7 Receiving Preferences Configuration for POs, Transfer

Orders, and Blind Receipts
Case/Pallet Build Preference
Case Optional
Pallet Mandatory

Table 8–8 Receiving Preferences Configuration for Return Orders and

Blind Orders
Case/Pallet Build Preference
Case Optional
Pallet Optional

[Link] Receiving Disposition Setup

Once the inventory is received into the warehouse, it can be transitioned
to the appropriate Product Class and Inventory Status based on the
Disposition Code. The user determines the disposition of the item and the
quantity. The disposition indicates whether the inventory is saleable,
requires further detailed quality checks, or should be scraped. These are
appropriately translated into the corresponding Product Class and
Inventory Status.
There are no Product Classes associated with the disposition codes
GOOD, REQ-INSP, and QC-PASSED for the Purchase Order, Transfer Order,
and Return Order document types. This is because the system needs to
retain the Product Class available on the shipment line.

The standard Disposition configurations provided are:

Table 8–9 Disposition Configurations

Product Inventory Final
Sl. No. Disposition Code Class Status Disposition
1 GOOD N (Good) Y
2 DAMAGED FD N (Good) Y

Receive and Putaway 71

Reference Implementation for Receiving

Table 8–9 Disposition Configurations

Product Inventory Final
Sl. No. Disposition Code Class Status Disposition
3 REQ-INSP AI (Awaiting N
Inspection)
3a QC-FAILED FD N (Good) Y
3b QC-PASSED N (Good) Y

Here, QC-FAILED and QC-PASSED are the disposition transitions for the
Disposition Code REQ-INSP.

72 Implementation Guide
 9
Inventory Mass Maintenance

Warehouse managers and inventory supervisors can use the Sterling

Warehouse Management System to update all the attributes of an
inventory at the same time.
The inventory mass maintenance task enables the modification of
inventory attributes, such as Ship By Date, Segment, COO, Inventory
Status, and Product Class.

9.1 The Inventory Mass Maintenance Process

Warehouse managers and inventory supervisors can use Inventory Mass
Maintenance to update the attributes of an inventory at the same time.
The inventory mass maintenance process involves the following tasks:
1. The inventory is selected based on the criteria specified.
2. The attributes of an inventory are updated with the new values.

9.2 Inventory Mass Maintenance Configurations

This section explains the various configurations that should be completed
before starting the inventory mass maintenance task.

9.2.1 Agent
The agent provided for the inventory mass maintenance process is
inventory mass maintenance.

Inventory Mass Maintenance 73

Inventory Mass Maintenance Configurations

[Link] Inventory Mass Maintenance

This agent is used to perform inventory mass maintenance and is
triggered from the Changed Attributes screen.
For more information about the Changed Attributes screen, see
Section 9.3.1, "Performing the Inventory Mass Maintenance".

Note: This agent can be triggered only from the

Application Console screen.

Attributes
Table 9–1 lists the attributes for the inventory mass maintenance agent.

Table 9–1 Inventory Mass Maintenance Agent Attributes

Attribute Value
Transaction Name Inventory Mass Maintenance
Transaction ID INV_MASS_MAINTENANCE
Base Process Type None
Base Document Type None
Abstract Transaction None
APIs Called ChangeLocationInventoryAttributes
User Exits Called None

Criteria Parameters
Table 9–2 lists the criteria parameters for the inventory mass
maintenance agent.

Table 9–2 Inventory Mass Maintenance Agent Criteria Parameters

Parameter Description
Action Required. Triggers the transaction. If left blank, it
defaults to Get, the only valid value.

74 Implementation Guide
 Inventory Mass Maintenance Configurations

Table 9–2 Inventory Mass Maintenance Agent Criteria Parameters

Parameter Description
Number of Records Optional. Number of records to retrieve and process at
one time. If left blank or specified as 0 (zero), it
defaults to 5000.
Node Required The warehouse management ship node for which
records are being processed.

Note: To determine the agent criteria for considering the

appropriate JMS Queue, the INV_MASS_MAINTENANCE
agent message service performs the following steps:
Q
It looks into the agent criteria set for the node. The
node is specified by the Node parameter.
Q
If none of the above is found, it considers the default
agent criteria.

9.2.2 API
The API provided to insert criteria records into
YFS_CHANGE_INV_ATTRS_CRITERIA from the console is
manageChangeInventoryAttributesCriteria.

[Link] manageChangeInventoryAttributesCriteria
The manageChangeInventoryAttributesCriteria inserts criteria records to
the YFS_CHANGE_INV_ATTRS_CRITERIA table. On successful insertion of
the records the ON_SUCCESS event of CHNG_INV_ATTRS_CRTRIA
transaction is raised. This event has to be configured to call the
YNW_Inv_Mass_Maint_91 service to add messages to the queue for the
Inventory Mass Maintenance agent to process.

9.2.3 Service
The service provided for Inventory Mass Maintenance is
YNW_Inv_Mass_Maint_91.

[Link] Inv Mass Maint

The YNW_Inv_Mass_Maint_91 service is an asynchronous service.

Inventory Mass Maintenance 75

Managing the Inventory Mass Maintenance Process on the Warehouse Floor

When the YNW_Inv_Mass_Maint_91 service is invoked from the

Application Console screen, this services places the message XML in the
JMS queue. The message XML contains the criteria to select the
inventory and update values of the inventory. The
INV_MASS_MAINTENANCE agent then picks up the messages from the
queue and updates the attributes of the inventory.

9.3 Managing the Inventory Mass Maintenance

Process on the Warehouse Floor
Use the Application Console to perform the inventory mass maintenance
task.

9.3.1 Performing the Inventory Mass Maintenance

Warehouse managers and inventory supervisors can use the Sterling
Warehouse Management System to perform a mass update of the
inventory status of, for example, an item, set of items, or locations, at
the same time. Application Console
To update the inventory status:
1. Log in to the application as the warehouse manager or inventory
supervisor.
2. From the Application Console menu, navigate to Inventory >
Inventory Mass Maintenance. The Inventory Mass Maintenance screen
appears.
For field value descriptions, see Table 9–3, Table 9–4, and Table 9–5.
3. Click Save. The inventory attributes are updated.

Table 9–3 Inventory Mass Maintenance

Field Description
Location Inventory
Node The node that contains the inventory to be updated.
Enterprise Select the enterprise associated with the inventory.

76 Implementation Guide
Managing the Inventory Mass Maintenance Process on the Warehouse Floor

Table 9–3 Inventory Mass Maintenance

Field Description
Zone Enter the name of the zone. The entire inventory
pertaining to this zone is selected for updating.
Alternately, you can click the icon to select a
specific zone.
Location Enter the name of the location. The entire inventory
pertaining to this location is selected for updation.
Alternately, you click the icon to select a specific
location.
Pallet ID Enter the pallet identifier.
Case ID Enter the case identifier.
Location Inventory Details
Inventory Status Select the inventory status from the drop-down list.
Ship by Date Enter the date range.
From - Enter the start date.
To - Enter the end date.
Alternately, you click to select the date range.
Segment Type Select the segment type of the inventory from the
drop-down list.
A segment type indicates an inventory category, such
as MTC (Made To Customer) or MTO (Made To Order).
Segment # Enter the segment number of the inventory. A
segment holds either the specific buyer or specific
order number that requires dedication.
Receipt # Enter the receipt number of the inventory. This is the
number used to identify the entire inventory attached
to a receipt.

Inventory Mass Maintenance 77

Managing the Inventory Mass Maintenance Process on the Warehouse Floor

Table 9–3 Inventory Mass Maintenance

Field Description
FIFO # Enter the FIFO number of the inventory.
FIFO number is a date-based inventory attribute that
helps understand the order in which stock arrived at a
given node. This is used to send out items that arrived
first rather than the ones that arrived later.
Country/Region Of Select the manufacturing country or region code that
Origin is to be associated with the inventory.
Alternately, you can click the icon to search for a
specific country or region.

Table 9–4 Inventory Mass Maintenance, Item Attributes

Field Description
Item ID Enter the item identifier.
Alternately, you can click the icon to search for a
specific item.
Product Class Select the product class.
Unit Of Measure Select the unit of measure.
Item Classification Enter the item classifications that are relevant for the
Attributes inventory to be updated.
Note: Item Classification attributes configured for an
enterprise for STORAGE 1, STORAGE 2, and STORAGE
3 purposes.

Table 9–5 Inventory Mass Maintenance, Tag Attributes

Field Description
Tag Attributes If the item is tag tracked, enter the tag attributes.
Note: If the item details are entered as the criteria
and the item is tag tracked, the tag panel is displayed,
where the tag attributes can be entered

78 Implementation Guide
Managing the Inventory Mass Maintenance Process on the Warehouse Floor

4. Click Proceed. The Inventory Mass Maintenance screen appears.

For more information about the field values, see Table 9–6.

Table 9–6 Inventory Mass Maintenance, Location Inventory

Field Description
Location Inventory
# of Loose Inventory Indicates the number of loose inventory items.
Items
# of Inventory Items Indicates the number of inventory items within a
Inside Licence Plates licence plate.
Location Inventory Attributes
Inventory Status Select the inventory status from the drop-down list.
Refers to an inventory sub classification based on the
results of the inventory control processes within the
warehouse.
Product Class Select the product class.
Ship by Date Or Add Enter the date by which the inventory needs to be
Days shipped.
Alternately, you can click to select the date range.
You can also add days to the already specified Ship by
Date of the inventory.
Note : If “Add Days” is specified as a negative
number, then in such case the Ship By Date value can
be less than current date, because of which the
inventory may get expired.
Segment Type Select the segment type of the inventory from the
drop-down list.
Segment # Enter the segment number of the inventory. A
segment holds either the specific buyer or specific
order number that requires dedication.
Receipt # Enter the receipt number of the inventory. This is the
number used to identify all the inventory attached to a
receipt.

Inventory Mass Maintenance 79

Managing the Inventory Mass Maintenance Process on the Warehouse Floor

Table 9–6 Inventory Mass Maintenance, Location Inventory

Field Description
FIFO # Enter the FIFO number of the inventory.
FIFO number is a date-based inventory attribute that
helps understand the order in which stock arrived at a
node. This is used to send out items that arrived first
rather than the ones that arrived later.
Country/Region Of Select the manufacturing country or region code to
Origin associate with the inventory.
Alternately, you can click the icon to search for a
specific country or region.
Tag Attributes
Tag Attributes If the item is tag tracked, enter the tag attributes.
Audit Reason
Reason Code Enter the reason code values.
Alternately, you can click the icon to search for a
specific reason code.
Reason Text Enter text to indicate the reason for the adjustment.

5. Click Save. The inventory attributes are updated.

80 Implementation Guide
 10
Location Mass Maintenance

Warehouse managers can use the Sterling Warehouse Management

System to update the attributes of a set of locations at the same time.
Location mass maintenance enables you to choose the locations to
update by selecting the criteria, such as zone, location size code, aisle
number, or range of locations.

10.1 Location Mass Maintenance Process

Warehouse managers and inventory supervisors can use Location Mass
Maintenance to update the attributes of a set of locations at the same
time.
The location mass maintenance process is:
1. The locations are selected based on the criteria.
2. The attributes of the locations can be updated with the new values.

10.2 Location Mass Maintenance Configurations

This section explains the various configurations that are completed for
Location Mass Maintenance.

Location Mass Maintenance 81

Location Mass Maintenance Configurations

Note: Location Mass Maintenance can be performed only

on zones where task execution, such as Picking or
Putaway, is not performed.

10.2.1 Agents
The agent provided for the Location Mass Maintenance process is
Location Mass Maintenance.

[Link] Location Mass Maintenance

This agent is used to perform location mass maintenance and is triggered
from the Changed Attributes screen.

Note: Because this agent modifies data that is generally

cached, it is advisable to run this agent after disabling
cache for the YFS_LOCATION table. For more information
about disabling cache for a specific table, see the Sterling
Selling and Fulfillment Foundation: Performance
Management Guide.

For more information about the Changed Attributes screen, see

Section 10.3.1, "Performing Location Mass Maintenance".

Note: This agent can only be triggered from the

Application Console screen.

Attributes
Table 10–1 lists the attributes for this agent.

Table 10–1 Location Mass Maintenance Attributes

Attribute Value
Transaction Name Location Mass Maintenance
Transaction ID LOCN_MASS_MAINT.[Link]
Base Process Type None

82 Implementation Guide
 Location Mass Maintenance Configurations

Table 10–1 Location Mass Maintenance Attributes

Attribute Value
Base Document Type None
Abstract Transaction None
APIs Called modifyLocation
User Exits Called None

Criteria Parameters
Table 10–2 lists the criteria parameters for this agent.

Table 10–2 Location Mass Maintenance Criteria Parameters

Parameter Description
Action Required. Triggers the transaction. If left blank, it
defaults to Get, the only valid value.
Number of Records Optional. Number of records to retrieve and process at
one time. If left blank or specified as 0 (zero), it
defaults to 5000.
Node Required The warehouse management ship node for which
records are being processed.
AgentCriteriaGroup The agent criteria group associated with the
warehouse management ship node for which velocities
are updated.

Location Mass Maintenance 83

Location Mass Maintenance Configurations

Note: To determine the agent criteria for considering the

appropriate JMS Queue, the LOCN_MASS_MAINT agent
message service performs the following steps:
Q
It looks into the agent criteria set for the node. The
node is specified by the Node parameter.
Q
If not found, it looks into the agent criteria that belongs
to the agent criteria group for that node. The agent
criteria group for the node is specified by the
AgentCriteriaGroup parameter.
Q
If none of the above is found, it considers the default
agent criteria.

Statistics Tracked
Table 10–3 lists the statistics tracked for this agent.

Table 10–3 Location Mass Maintenance Statistics

Statistic Name Description
NumLocationChanged Number of changed locations.

Events Raised
Table 10–4 lists the events raised by this agent.

Table 10–4 Events Raised by the Location Mass Maintenance

Transaction
Template
Transaction/Event Key Data Data Published Support?
AGENT_COMPLETION YNW_LOCN_MAS Yes
S_MAINT.AGENT_
[Link]

Note: The default message queue provided for this agent

is DEFAULTAGENTQUEUE. You can also associate your own
message queue with the agent.

84 Implementation Guide
 Managing the Location Mass Maintenance Process on the Warehouse Floor

10.2.2 Services
The service provided for Location Mass Maintenance is
YNW_Loc_Mass_Maint_91.

[Link] Loc Mass Maint

The YNW_Loc_Mass_Maint_91 service is an asynchronous service.
When the YNW_Loc_Mass_Maint_91 service is invoked from the
Application Console screen, this services places the message XML in the
JMS queue. The message XML contains the criteria to select the locations
and the update values of the locations. The LOCN_MASS_MAINT agent
then picks up the messages from the queue and updates the locations.
On updating the locations, this agent raises the AGENT_COMPLETION
event. This event invokes the YNW_LocMassMaint_91 action.
Once the YNW_LocMassMaint_91 action is invoked, an alert is raised to
indicate that the agent has completed its tasks. The raised alert is then
sent to the alert queue.

10.3 Managing the Location Mass Maintenance

Process on the Warehouse Floor
You can use the Application Console to perform Location Mass
Maintenance.

10.3.1 Performing Location Mass Maintenance

Warehouse managers can use Sterling Warehouse Management System
to update the attributes of a set of locations at the same time.
Location mass maintenance enables you to choose the locations to
update by selecting the criteria, such as zone, location size code, aisle
number, or range of locations.
To update the attributes of a group of locations:
1. Log into the application as the warehouse manager or inventory
supervisor.
2. From the Application Consolemenu, choose Inventory > Location
Mass Maintenance. The Location Mass Maintenance screen appears.
For the field value description, see Table 10–5.

Location Mass Maintenance 85

Managing the Location Mass Maintenance Process on the Warehouse Floor

3. In the Filter Locations area of the Location Mass Maintenance screen,

enter information in the applicable fields and click Proceed. The
Selected Criteria and Change Attributes areas appears.
The Selected Criteria area displays the criteria you have selected in
the Filter Locations area and the Number of Filtered Location.
For more information about the field values of the Changed Attributes
area, see Table 10–6.
4. In the Change Attributes area, enter information in the applicable
fields.
5. Click Save. The selected locations get updated with the new values.

Table 10–5 Location Mass Maintenance, Filter Locations

Field Description
Node The node that contains the locations to update.
From Location Enter the start location for the location range to
update.
You can also click the icon to search for the specific
location.
If you enter a value for the From Location, it is
mandatory to enter a value for the To Location.
To Location Enter the end location for the location range to
update.
You can also click the icon to search for the specific
location.
If you enter a value for the To Location, it is
mandatory to enter a value for the From Location.
Zone Enter the name of the zone. All locations of the zone
are selected for updation.
You can also click the icon to select the specific
zone.
Location Type Select a location type. All locations of this type are
selected for updation.
The valid values for location type are INTRANSIT
(mobile locations), STAGING (floor, drop-off),
VIRTUAL, REGULAR, and DOCK.

86 Implementation Guide
Managing the Location Mass Maintenance Process on the Warehouse Floor

Table 10–5 Location Mass Maintenance, Filter Locations

Field Description
Location Size Code Enter a location size code. All locations with this size
code are selected for updation.
You can also click the icon to select the specific
location size code.
Storage Code Select the storage code. All locations with this storage
code are selected for updation.
Aisle # Enter the aisle number of the location to update.
Bay # Enter the bay number of the location to update.
Level # Enter the level number of the location to update.
Freeze for Picking Select Y to update all locations that are frozen for
picking.
Pick Sequence Enter the pick sequence of the location to update.
Out Staging Location The location where inventory is temporarily dropped,
when transferring the inventory from the storage
locations.
You can also click the icon to search the out-staging
location.
Freeze For Putaway Select Y to update all locations that are frozen for
putaway.
Putaway Sequence Enter the putaway sequence of the location to update.
In Staging Location The location where inventory is temporarily dropped
when transferring the inventory to the storage
location.
You can also click the icon to search the in-staging
locations.
Velocity Code Select a velocity code. All locations with this velocity
code are selected for updation.

Location Mass Maintenance 87

Managing the Location Mass Maintenance Process on the Warehouse Floor

Table 10–6 Location Mass Maintenance, Change Attributes

Field Description
Node The node for which the attributes of the locations are
changed.
Location Size Code Enter the new location size code of the selected
locations.
You can also click the icon to search for the location
size code.
Storage Code Select the new storage code of the selected locations.
Velocity Code Select the new velocity code of the selected locations.
Aisle # Enter the new aisle number of the selected locations.
Bay # Enter the new bay number of the selected locations.
Level # Enter the new level number of the selected locations.
Freeze For Picking Select Y to mark all the selected locations as frozen for
picking.
Pick Sequence Enter the new pick sequence with which all selected
locations are updated.
Out Staging Location The new location where inventory is temporarily
dropped, when transferring the inventory from the
storage locations.
You can also click the icon to search the out-staging
location.
Freeze For Putaway Select Y to mark all the selected locations as frozen for
putaway.
Putaway Sequence Enter the new putaway sequence with which all
selected locations are updated.
In Staging Location The new location where inventory is temporarily
dropped, when transferring the inventory to storage
locations.
You can click the to search the in-staging location.
Remove SKU Check this box to remove the SKU dedication of the
Dedication selected locations.

88 Implementation Guide
Managing the Location Mass Maintenance Process on the Warehouse Floor

Note: When updating the location size code for a location

that contains inventory, the On Location Dimension Size
Change event gets raised automatically, which recalculates
the size of the location.
When updating the location size code, ensure that the
RECALC_LOCN_DIMENSIONS and LOCN_MASS_MAINT
agents are running.

Location Mass Maintenance 89

Managing the Location Mass Maintenance Process on the Warehouse Floor

90 Implementation Guide
 11
Managing Activity Demands

Activity Demands are demands created for certain items. As these items
are received, based on the number of items in demand, these items are
diverted to a location specifically for that particular activity code.
This chapter explains how to create, modify, and delete Activity Demands
using the Sterling Warehouse Management System.

11.1 Creating an Activity Demand

To create an Activity Demand:
1. Log into the application as the node user.
2. From the Application Console menu, select Inbound > Create Activity
Demand. The Create Activity Demand screen displays.
For information about the field values see Table 11–1 and Table 11–2.
3. In the Activity Demand area, enter the appropriate details.
4. In the Activity Demand Info area,
a. Enter the Demand Quantity
b. Select the UOM
5. Click Create Activity Demand. The Activity Demand screen displays.
For information about the field values see Table 11–5 and Table 11–6.
6. In Demand Location Id, enter the location to which the demanded
quantity is diverted.
You can also click to select the Demand Location Id.
7. If needed, select the Priority and enter the Demand Quantity.

Managing Activity Demands 91

Creating an Activity Demand

8. Click Save.

Table 11–1 Create Activity Demand, Activity Demand

Field Description
Document Type Select the document type.
Valid document types are Blind Return, Blind Receipt,
Transfer Order, and Purchase Order.
Node Indicates the node that ships the shipment.
Enterprise Select the enterprise that ships the shipment.
Activity Code Select the activity code.
Shipment # Enter the shipment number of the shipment.
You can also click to select the shipment number.
PO # Enter the purchase order number.
You can also click to select the PO number.
Seller Enter the seller that sells the shipment.
You can also click to select the seller.
Priority Select the priority of the activity demand being set up.
Item ID Enter the identifier of the item.
You can also click to select the item ID.
It is mandatory to enter the Item ID.
Product Class Select the product classification for the item.
It is mandatory to enter the Product Class.
Unit Of Measure Select the unit of measure for the item.
It is mandatory to enter the Unit of Measure.

Table 11–2 Create Activity Demand, Activity Demand Info

Field Description
Demand Quantity Enter the number of items in demand and select the
UOM from the drop-down list.

92 Implementation Guide
 Activity Demand Search By All Attributes

Note: You can also create an Activity Demand by using

the Inbound Order Shipment Details screen. Click the
Create Activity Demand action in the Shipment Lines area.

11.2 Activity Demand Search By All Attributes

To search for activity demands by all attributes.
1. Log in to the application.
2. From the Application Console menu bar, select Inbound > Activity
Demand Console. The Activity Demand By All Attributes search
screen is displayed. For more information about the field value
description, see Table 11–3.
3. Click Search to view the results in the Activity Demand List screen.
Table 11–3 Activity Demand Search By All Attributes
Field Description
Document Type Indicates the document type.
Node Indicates the node that ships the shipment.
Activity Code Select the activity from the drop-down list for which
you want to view the details.
Shipment # Enter the shipment number of the shipment.
You can also click to select the shipment number.
Item ID Enter the identifier of the item.
You can also click to select the item ID.
Seller Enter the seller that sells the shipment.
You can also click to select the seller.
PO # Enter the purchase order number.
You can also click to select the PO number.
Max Records Enter the maximum number of records to be listed as
a result of your search.

Managing Activity Demands 93

Modifying An Activity Demand

11.3 Activity Demand List

The Activity Demand List screen displays the result of an activity demand
search.
To view the results of an activity demand search:
1. Log in to the application.
2. From the Application Console menu bar, select Inbound > Activity
Demand Console. The Activity Demand By All Attributes search
screen is displayed. For more information about the field value
description, see Table 11–3.
3. Click Search. The Activity Demand List screen is displayed. For more
information about the field value description, see Table 11–4.
Q
Click View Details. The Activity Demand screen is displayed.
To delete an activity code, select the check box of the appropriate activity
code and click Delete.
Table 11–4 Activity Demand, Activity Demand List
Field Description
Activity Code Indicates the activity code.
Shipment # Indicates the shipment number of the shipment.
PO # Indicates the purchase order number.
Item ID Indicates the identifier of the item.
Description Indicates the description of the item.
UOM Indicates the unit of measure of the item.
Open Demand Qty Indicates the demand that is yet to be satisfied.

11.4 Modifying An Activity Demand

To modify an Activity Demand:
1. Log into the application.
2. From the Application Console menu bar, select Inbound > Activity
Demand Console. The Activity Demand By All Attributes search
screen displays.

94 Implementation Guide
 Modifying An Activity Demand

3. Enter the appropriate search criteria and click Search.

4. The Activity Demand List screen displays.
5. In the Activity Demand List screen, click the appropriate Activity
Code. The Activity Demand screen displays.
For information about the field values see Table 11–5 and Table 11–6.
6. Enter the appropriate values.
7. Click Save to save the values entered.

Table 11–5 Activity Demand, Activity Demand

Field Description
Document Type Indicates the document type.
Node Indicates the node that ships the shipment.
Enterprise Indicates the enterprise that ships the shipment.
Activity Group Indicates the activity group to which the activity code
belongs.
Activity Code Indicates the activity code.
The activity code is always 'Divert for Quality Check',
when modifying a QC Profile.
Priority Select the priority of the activity demand.
Shipment # Indicates the shipment number of the shipment.
PO # Indicates the purchase order number.
Demand Location ID Enter the location to which the demanded quantity is
diverted.
You can also click to select the Demand Location
ID.

Table 11–6 Activity Demand, Activity Demand Details

Field Description
Item ID Indicates the identifier of the item.
Item Description Indicates the description of the item.
Product Class Indicates the product classification for the item.

Managing Activity Demands 95

Deleting An Activity Demand

Table 11–6 Activity Demand, Activity Demand Details

Field Description
Demand Quantity Enter the quantity of the item that is in demand.
Unit Of Measure Indicates the unit of measure for the item.
Inventory Status Indicates the inventory status of the item.
Satisfied Quantity Indicates the quantity of the item that is satisfied.
Pallet Id Indicates the identifier of the pallet.
Case Id Indicates the identifier of the case.
Open Demand Qty The demand that is yet to be satisfied.
Segment Type The segment type of the item.
A segment type indicates an inventory category, such
as MTC (Made To Customer) or MTO (Made To Order).
Segment The segment number of the item. A segment holds
either the specific buyer or specific order number that
requires dedication.

Note: You can also modify an Activity Demand by using

the Inbound Order Shipment Details screen. To view or
modify an existing Activity Demand, click .

11.5 Deleting An Activity Demand

To delete an Activity Demand:
1. Log into the application.
2. From the Application Console menu bar, select Inbound > Activity
Demand Console. The Activity Demand By All Attributes search
screen displays.
3. Enter the appropriate search criteria and click Search.
4. The Activity Demand List screen displays.

96 Implementation Guide
 Reference Implementation for Activity Demand

5. In the Activity Demand List screen, select the box against the
appropriate Activity Code and click Delete.

Note: You can also delete an Activity Demand by using

the Inbound Order Shipment Details screen. To view or
modify an existing Activity Demand, click .

11.6 Reference Implementation for Activity

Demand
In the Reference Implementation for Sterling Warehouse Management
System, it is assumed that the inventory received from VENDOR3
requires Quality Check. As per the configuration, during receipt, 20 per
cent of the inventory received from VENDOR3 is sent to the QC Zone.
For the inventory received from VENDOR3, an activity demand is created
for 20 per cent of the inventory received.
For more information about the Reference Implementation provided for
Quality Control, see Section 12.5, "Reference Implementation for Quality
Control".

Managing Activity Demands 97

Reference Implementation for Activity Demand

98 Implementation Guide
Reference Implementation for Activity Demand

Managing Activity Demands 99

Reference Implementation for Activity Demand

100 Implementation Guide

 12
Quality Control

In the supply chain industry today, products are being sourced from
external vendors. These vendors vary from the highly sophisticated to
the highly skilled, but with low access to technology. A few
manufacturers have chosen to send their representatives to each facility
to oversee the quality and accuracy of the operation. Others have chosen
to instill a high degree of checks when the product is received into their
own facilities. Retailers also perform inspection to ensure accuracy and
quality of the product they receive from the manufacturers.
Quality Control (QC) helps address the quality control procedures that
may be performed at a warehouse receiving products from vendors.
This chapter explains the Quality Control process and solution offered by
Sterling Warehouse Management System.

12.1 Quality Control Process

Inventory received in a warehouse can be optionally sent for Quality
Control. These inventory items are diverted to the QC Zone. The quantity
diverted for QC can be configured. Sometimes, the entire quantity
received may be diverted for QC. You can also configure only a
percentage of the receipt for QC. The diversion of inventory to the QC
Zone is decided based on your defined receiving preferences, such as,
Vendor Classification, Item Classification, Buyer Organization, Seller
Organization, and so forth. For more information about configuring the
receiving preferences, see the Sterling Supply Collaboration:
Configuration Guide.

Quality Control 101

Quality Control Process

The QC process is:

1. The start of a receipt for an inbound shipment in the warehouse
computes the QC quantity. QC computations are based on receiving
preferences.
2. While attempting to putaway the inventory or license plates, these
demands are honoured before considering the diversion of products
to storage.
3. Putaway tasks are suggested to warehouse operators for moving out
products from the dock to QC, Storage, Cross dock, and so forth.
4. Products brought for QC are inspected.
5. The inspection process determines the disposition of products and
their Product Class and Inventory Status.
6. Based on the inspection outcome, the inspected products are either
put away to storage or more inventory from storage may be called in
manually for more inspection.

Note:
Q
The QC process is valid for the Purchase Order, Transfer
Order, and Returns Order document types.
Q
The QC process is valid while receiving with both an
ASN and PO, with an ASN but without a PO, and
without an ASN but with a PO. In the first and second
cases, the QC quantity is determined as a percentage
of the shipment line. In the last case, the QC quantity
is determined as a percentage of the order line.
Q
The defined QC percentage is not used in the case of
Blind Receipts because there is no expected
information or order.

102 Implementation Guide

 Quality Control Configurations

12.2 Quality Control Configurations

This section explains the various configurations that may be done for the
QC process.

12.2.1 Quality Control Pipeline

The QC process is a part of the Inbound process. To see the complete
Inbound Pipeline, see Section 8.2.1, "Receiving Pipeline" in Chapter 8,
"Receive and Putaway".

12.2.2 Activities
Activities in the warehouse are grouped into Activity Groups. The Sterling
Warehouse Management System provides a pre-defined set of activity
groups for a warehouse. Examples of activity groups include Receipt,
Inspection, Value Added Services, and Packing.
Each activity group is associated with activity codes that define each
activity that is performed. The Inspection activity group has this activity:
Inspection.

Note: Activity Codes may be defined only when the

Warehouse Management System tree is loaded for Node
and Hub combination.

12.2.3 Setting Up the Quality Control Profile

At the Participant Or Catalog Level
Before you can use the QC process, you need to enable Quality Control
for the Enterprise and define the QC percentage. The QC percentage
defined by you determines the percentage of received goods that are
diverted to the QC zone for QC.
To turn on QC for an Enterprise and define the QC percentage:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.

Quality Control 103

Quality Control Configurations

3. From the Applications Manager menu bar, select Application > Supply
Collaboration.
4. From the tree in the application rules side panel, select Receiving >
Receiving Preferences. The Receiving Preferences screen displays.
5. In the Search Results panel, click . The Receiving Preference
Details pop-up window displays.
6. Enter information into the applicable fields. For more information and
field value descriptions, see the Sterling Supply Collaboration:
Configuration Guide.
7. Select the QC Required check-box.
8. In the Receiving Preference Details pop-up window, enter the QC
Percentage. The default QC percentage value is 100; you can change
it according to your business requirements.
9. Click .
During receipt, the quantity of received items to divert to the QC Zone,
for the classifications chosen by you in this screen, is determined by the
QC percentage specified here.

Note: If the QC Percentage value has not been defined, it

is set to 100 per cent, if the QC Required flag is set to Y.
This results in the entire received quantity to be diverted
to the QC Zone for QC.

12.2.4 Setting Up Disposition Codes

Disposition Codes allow inspectors to utilize their own terminology,
instead of understanding inventory and storage implications.
Inventory is received with the specified Product Class and Inventory
Status of the Disposition Code entered.
If the Product Class is not specified, the Product Class from the purchase
order or the default Product Class from the item is used. It is mandatory
to have the Product Class specified at one of these levels.
This section explains how to create Disposition Codes. It also explains
how to associate the Disposition Code with a Product Class, with

104 Implementation Guide

 Quality Control Configurations

Disposition Transition Statuses, for receiving with QC, and with an

Inventory Status.

[Link] Enterprise-Level Disposition Setup

This section describes the Disposition Codes set up at the Enterprise
level.

[Link].1 Creating the Receiving Disposition

Disposition Codes can be created to be assigned to the inventory at
different stages, such as receiving, during QC, and after QC. You can
have different Disposition Codes, depending upon whether the products
passed QC, failed QC, and so forth.
To create the Disposition Code to assign to the items in QC:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Receiving Disposition. The
Disposition List: Purchase Order screen is displayed.
5. In the Disposition List: Purchase Order screen, click . The
Disposition Details pop-up window displays.
6. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
7. Click .
A receiving disposition is created that can be associated with the
inventory during receiving.

Quality Control 105

Quality Control Configurations

[Link].2 Associating the Disposition Code with a Product

Class
Disposition Codes can be associated with Product Classes. Whenever a
product is dispositioned to the selected Disposition Code, the Product
Class automatically changes to the Product Class that you specify here.
To associate the Disposition Code with a Product Class:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application > Supply
Collaboration.
4. From the tree in the application rules side panel, select Document
Specific > Receipt > Receiving Disposition. The Disposition List:
Purchase Order screen displays.
5. In the Disposition List: Purchase Order screen, click . The
Disposition Details pop-up window displays.
6. In the Product Class drop-down list, select the appropriate Product
Class for the Disposition Code.
7. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
8. Click .
The selected Disposition Code is now associated with the specified
Product Class.

[Link].3 Associating the Disposition Code with Disposition

Transition Statuses
Disposition Transition Statuses aid in multi-level QC. If the product has to
be inspected consecutively by multiple inspectors checking different
attributes of the product, the product undergoes various inventory status

106 Implementation Guide

 Quality Control Configurations

transitions, as it completes one level of inspection and enters the

subsequent levels.
Disposition Codes can be associated with Disposition Transition Statuses.
The products being dispositioned to this Disposition Code are assigned
the Inventory Statuses specified here consecutively, until it reaches the
final disposition.
To associate the Disposition Code with Disposition Transition Statuses:
1. Follow steps 1-5 in Section [Link].2, "Associating the Disposition
Code with a Product Class".
2. In the Receiving Disposition drop-down list of the Disposition
Transitions pane, select the appropriate Inventory Statuses.
3. Click .
The selected Disposition Code is now associated with the specified
Disposition Transition Statuses.

[Link] Node-Level Disposition Setup

This section describes the Disposition Codes set up at the node level.

[Link].1 Associating the Disposition Code with an Inventory

Status
Disposition Codes can be associated with Inventory Statuses. Whenever
a product is dispositioned to the selected Disposition Code, the Inventory
Status automatically changes to the status that you specify here.
To associate the Disposition Code with an Inventory Status:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Disposition Codes.
5. The Receiving Disposition: Purchase Order screen is displayed.

Quality Control 107

Quality Control Configurations

6. From the Inventory Status drop-down list, select the Inventory Status
to associate with the Disposition Code.
For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. Click .

[Link].2 Associating a Disposition Code for Receipt

with Quality Control
Disposition Codes can be associated for Receipt with QC. During
receiving, this Disposition Code is assigned to all items that require QC.
To associate a Disposition Code for receiving with QC:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Purchase Order > Receiving Preferences.
5. The Receiving Preferences: Purchase Order screen displays.
6. In the Disposition Code for Receipt with QC field, enter the
appropriate Disposition Code. During receiving, this Disposition Code
is assigned to all items that require QC.
7. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
8. Click .

Note: Click to view the Receiving Preferences Details

screen that displays the detailed preferences set for
receiving the item, along with the QC percentage set for
the item.

108 Implementation Guide

 Quality Control Configurations

12.2.5 Inventory Status Transitions

Inventory should be considered available or unavailable for certain
operations based on the operations within the warehouse. For example,
inventory should be unavailable for orders until putaway tasks are
complete. As soon as putaway is complete, the inventory should become
available for orders automatically, without any intervention from users.
To facilitate this, Inventory Statuses are assigned to inventory. The
Inventory Status of the inventory changes at different stages.
When inventory is received, it is assigned an appropriate Inventory
Status to show that the inventory is awaiting inspection. When the
inventory is moved to storage, the Inventory Status may change
appropriately.
Inventory Statuses can be associated with zones. In this case, whenever
a product moves into a particular zone, its Inventory Status gets
transitioned to the Inventory Status with which the zone is associated.
So, whenever a product is moved into the QC zone, its Inventory Status
changes to the Inventory Status associated with the QC zone, which may
indicate that the product is undergoing QC. When the product moves out
of the QC zone into storage, its Inventory Status changes to the
Inventory Status associated with the storage zone, which may indicate
that the product is available for orders. Products that fail QC may be
moved to the appropriate zone that is associated with an Inventory
Status to mark the products as damaged and thus unavailable, or
quarantined, or held until more QC is done on a larger sample.
If a product with the Inventory Status indicating that the product is
awaiting inspection is moved directly into storage, it retains its Inventory
Status. This is because no transition has been defined for the Inventory
Status of the storage zone, when a product with that Inventory Status
moves into storage. If the warehouse process so dictates, this can be
overwritten by setting an appropriate Inventory Status Transition. In this
case, products putaway into the storage zone may become directly
available for orders, even though they have not yet cleared QC.

Quality Control 109

Quality Control Configurations

12.2.6 Setting Up Putaway Preferences

You can set up the Putaway preferences that are applicable while
receiving, when QC is enabled.
This section explains how to set up the Putaway Preferences.

[Link] Putaway from Dock to QC Zone

To set up the Putaway Preferences for putaway from the dock to the QC
Zone:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Putaway Preferences. The Putaway Preferences screen is displayed.
Use this to set the Putaway Preferences for a single SKU, a multi-level
container, and container with unknown contents.
5. Alternatively, click in the Activity Search screen to access the
Putaway Preferences screen.
6. In the Putaway Preferences screen, select the appropriate tab,
depending on whether you are setting up Putaway Preferences for a
Single SKU, a Multi-SKU Container, or a Container with unknown
contents.
7. Click . The Putaway Preference Details screen displays.
8. In the Activity Code drop-down list, select the code to divert for
quality check (QC).
9. In the Inventory Status drop-down list, select the appropriate
Inventory Status to indicate that the product is awaiting inspection.
10. In the Zone Priorities Panel > Zone drop-down list, select the zone
where QC is performed.

110 Implementation Guide

 Quality Control Configurations

11. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
12. Click .
13. To configure Task Types for Putaway, click . The Putaway Strategy
screen displays. Configure the Task Types.
For more information about setting up Putaway Strategies, see the
Sterling Warehouse Management System: Configuration Guide.

[Link] For Putaway from QC Zone to Storage

To set up the Putaway Preferences for Putaway from the QC Zone to
storage:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Putaway Preferences. The Putaway Preferences screen is displayed.
Use this to set the Putaway Preferences for a single SKU, a multi-level
container, and a container with unknown contents.
5. Alternatively, click in the Activity Search screen to access the
Putaway Preferences screen.
6. In the Putaway Preferences screen, select the appropriate tab,
depending on whether you are setting up Putaway Preferences for a
Single SKU, a Multi-SKU Container, or a Container with unknown
contents.
7. Click . The Putaway Preference Details screen displays.
8. In the Activity Code drop-down list, select the code to move the
product to the appropriate storage location.
9. In the Inventory Status drop-down list, select the appropriate
Inventory Status to indicate that the product has completed QC.

Quality Control 111

Quality Control Configurations

10. In the Zone Priorities panel > Zone drop-down list, select the zone for
storage.
11. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
12. Click .
13. To configure Task Types for putaway, click . The Putaway Strategy
screen displays. Configure the Task Types.
For more information about setting up Putaway Strategies, see the
Sterling Warehouse Management System: Configuration Guide.

12.2.7 Agents
No agent needs to be configured for the QC process.

12.2.8 Services
Either of the services provided for QC can be turned on.
The services provided for QC are:
Q
Register Activity Demand For QC
This service computes the QC quantity (quantity of the products
received that needs to be diverted to the QC Zone for QC) and
creates an activity demand for it.
Q
Register Activity Demand and Print Receiving Worksheet
This service computes the QC quantity and prints it on the Receiving
Worksheet. It also creates an activity demand for the QC quantity.

Note: These services are already activated if you have

installed the factory defaults with the events turned on.

[Link] Register Activity Demand For QC

When a receipt is started, the ON_START_RECEIPT event of the
START_RECEIPT transaction is raised, which invokes the
YNW_RegisterActivityDemandForQC_91 service.

112 Implementation Guide

 Quality Control Configurations

The YNW_RegisterActivityDemandForQC_91 service initiates the

computation of the quantity of product that needs to be diverted for a
shipment or order, based on the QC Classification and QC Percentage
setup. It then creates an activity demand for the same. During Putaway
this quantity of the product is diverted to the QC Zone for QC.
To activate the YNW_RegisterActivityDemandForQC_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the transaction repository.
3. Associate the ON_START_RECEIPT event with the action Register
Activity Demand For QC, which invokes the
YNW_RegisterActivityDemandForQC_91 service.

[Link] Register Activity Demand and Print Receiving Worksheet

When a receipt is started, the ON_START_RECEIPT event of the
START_RECEIPT transaction is raised, which invokes the
YNW_CompositeServiceOnStartReceipt_91 service.
YNW_CompositeServiceOnStartReceipt_91 initiates the computation of
the quantity of product that needs to be diverted for a shipment or order,
based on the QC classification and QC percentage setup. It then creates
an activity demand for the same. The QC percentage computed is then
printed on the Receiving Worksheet.
To activate the YNW_CompositeServiceOnStartReceipt_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the transaction repository.
3. Associate the ON_START_RECEIPT event with the action YNW CalcQC
And Print Recv WS (91), which invokes the
YNW_CompositeServiceOnStartReceipt_91 service.

12.2.9 Prints
The YNW_CompositeServiceOnStartReceipt_91 service is provided, which
prints the QC Quantity in the Receiving Worksheet.

Quality Control 113

Managing the Quality Control Profile at the Transaction Level

12.3 Managing the Quality Control Profile at the

Transaction Level
A QC Profile enables you to define the quantity that needs to be diverted
for QC. This diversion can be defined at the Item, Shipment, or PO level.
You might want to set up manual diversions for QC, for a Shipment or
PO, based on some information received from the manufacturer. For
example, consider a manufacturer that always supplies items from a
manufacturing plant in Boston. If, for some reason, the manufacturer
fulfills one PO from another plant in Chicago, you may decide to set up
QC diversion for this PO. This QC diversion overrides the QC
configuration previously set up for the manufacturer.
If you have manually entered a QC profile for an item in the shipment,
the QC percentage previously defined for that specific item is ignored and
the quantity specified by the QC profile is diverted for QC. For all other
items in the shipment, the QC percentage defined previously is used to
determine the quantity diverted for QC.

12.3.1 Creating a Quality Control Profile

To create a QC Profile:
1. Log into the application.
2. From the Application Console menu bar, select Inbound > Create QC
Profile. The Create Activity Demand screen displays.
For more information about the field values see Table 12–1 and
Table 12–2.
3. In the Activity Demand area, enter the appropriate details.
4. To view the current QC Profile, click Compute QC Qty. The current QC
Profile displays in the QC Profile Info area.
5. To enter a new QC Profile, in the QC Profile Info area:
c. Select Quantity to enter the Override QC Qty in units. Enter the
Override QC Qty and select the UOM.
d. Select Percentage to enter the Override QC Qty in percentage.
Enter the Override QC percentage.
6. Click Create Activity Demand. The Activity Demand screen displays.

114 Implementation Guide

 Managing the Quality Control Profile at the Transaction Level

For more information about the field values see Table 12–3 and
Table 12–4.
7. In Demand Location Id, enter the location to which the demanded
quantity is diverted.
You can also click to select the Demand Location Id.
8. If needed, select the Priority and enter the Demand Quantity.
9. Click Save.

Table 12–1 Create Activity Demand, Activity Demand

Field Description
Document Type Select the document type.
Valid Document Types are Blind Return, Blind Receipt,
Transfer Order, and Purchase Order.
Node Indicates the node that ships the shipment.
Enterprise Select the enterprise that ships the shipment.
Activity Code Indicates the activity code.
If Divert for Quality Check does not appear as the
activity code, select Divert for Quality Check from the
drop-down list.
Shipment # Enter the shipment number of the shipment.
You can also click to select the shipment number.
PO # Enter the Purchase Order number.
You can also click to select the PO number.
Seller Enter the seller that sells the shipment.
You can also click to select the seller.
Priority Select the priority of the activity demand being set up.
Item ID Enter the identifier of the item.
You can also click to select the item ID.
It is mandatory to enter the Item ID.

Quality Control 115

Managing the Quality Control Profile at the Transaction Level

Table 12–1 Create Activity Demand, Activity Demand

Field Description
Product Class Select the Product Class of the item.
It is mandatory to enter the Product Class.
Unit Of Measure Select the Unit of Measure of the item.
It is mandatory to enter the Unit of Measure.

Table 12–2 Create Activity Demand, QC Profile Info

Field Description
QC Profile% Indicates the current percentage to divert to QC.
Quantity Based on% Indicates the quantity to divert to QC.
Quantity Select the enterprise that ships the shipment.

Quantity Select this to enter the Override QC Qty in units.

In Override QC Qty, enter the new quantity to
divert to QC and select the UOM from the
drop-down list.
Percentage Select this to enter the Override QC Qty in
percentage.
In Override QC%, enter the new percentage to
divert to QC.

Note: You can also create a QC Profile by using the

Inbound Order Shipment Details screen. Click the Create
Activity Demand action in the Shipment Lines area.

12.3.2 Modifying a Quality Control Profile

To modify a QC Profile:
1. Log into the application.

116 Implementation Guide

 Managing the Quality Control Profile at the Transaction Level

2. From the Application Console menu bar, select Inbound > QC Profile
Console. The Activity Demand By All Attributes search screen
displays.
3. Enter the appropriate search criteria and click Search.
4. The Activity Demand List screen displays.
5. In the Activity Demand List screen, click the appropriate Activity
Code. The Activity Demand screen displays.
For more information about the field values see Table 12–3 and
Table 12–4.
6. Enter the appropriate details.
7. Click Save to save the details entered.

Table 12–3 Activity Demand, Activity Demand

Field Description
Document Type Indicates the document type.
Node Indicates the node that ships the shipment.
Enterprise Indicates the enterprise that ships the shipment.
Activity Group Indicates the activity group to which the activity code
belongs.
Activity Code Indicates the activity code.
The activity code is always Divert for Quality Check,
when modifying a QC Profile.
Priority Select the priority of the activity demand.
Shipment # Indicates the shipment number of the shipment.
PO # Indicates the Purchase Order number.
Demand Location ID Enter the location to which the demanded quantity is
diverted.
You can also click to select the demand location ID.

Quality Control 117

Managing the Quality Control Profile at the Transaction Level

Table 12–4 Activity Demand, Activity Demand Details

Field Description
Item ID Indicates the identifier of the item.
Item Description Indicates the description of the item.
Product Class Indicates the Product Class of the item.
Demand Quantity Enter the quantity of the item that is in demand.
Unit Of Measure Indicates the Unit of Measure of the item.
Inventory Status Indicates the inventory status of the item.
Satisfied Quantity Indicates the quantity of the item that is satisfied.
Pallet Id Indicates the identifier of the pallet.
Case Id Indicates the identifier of the case.
Open Demand Qty The demand that is yet to be satisfied.
Segment Type The segment type of the item.
A segment type indicates an inventory category.
Typical values are MTC (Made To Customer) and MTO
(Made To Order).
Segment The segment number of the item. A segment holds
either the specific buyer or specific order number that
requires dedication.

Note: You can also modify a QC Profile by using the

Inbound Order Shipment Details screen. To view or modify
an existing Activity Demand, click .

12.3.3 Deleting a Quality Control Profile

To modify a QC Profile:
1. Log into the application.
2. From the Application Console menu bar, select Inbound > QC Profile
Console. The Activity Demand By All Attributes search screen
displays.
3. Enter the appropriate search criteria and click Search.

118 Implementation Guide

 Managing the Quality Control Process on the Warehouse Floor

4. The Activity Demand List screen displays.

5. In the Activity Demand List screen, select the box against the
appropriate Activity Code and click Delete.

Note: You can also delete a QC Profile by using the

Inbound Order Shipment Details screen. To view or modify
an existing Activity Demand, click .

12.4 Managing the Quality Control Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform Quality Control. This section explains the UI flow while receiving
using Orders and ASNs.

12.4.1 Quality Control Flow For Receiving Using Order

The UI flow for QC while receiving using an Inbound or Return Order is
explained in this section.

[Link] Receiving Process

Follow these steps in the Receiving process:
1. Start the Receipt from the Inbound Order console or Returns Console
using the Report/Record Receipt action. The Start Receipt pop-up
window displays.
2. Enter the details required, and start the receipt by clicking Save. The
Receive screen displays.
For more information about the field values, see the Sterling
Warehouse Management System: User Guide.
3. In the Receive screen, enter the Disposition Code for products
requiring inspection (REQ-INSP) and click Save.
This step needs to be performed using the Mobile Application if you
are using the Mobile Application for receiving.
4. In the Receipt Console, close the receipt by clicking Close Receipt.

Quality Control 119

Managing the Quality Control Process on the Warehouse Floor

[Link] Putaway Process

When the receipt is closed, Putaway tasks are automatically generated
by the system. Depending upon the QC Percentage defined, part of the
receipt is diverted to the QC Zone. The rest may be diverted to storage.
The inventory status of the entire receipt is set to one which indicates
that the products are awaiting inspection.

[Link] Inspection Process

Follow these steps in the Inspection process:
1. To inspect the products that have been diverted to the QC Zone,
navigate to the Inspect Inbound Receipt console.
2. Enter the details required, and click Proceed. The Inspect Inbound
Receipt Details screen displays.
For more information about the fields, see the Sterling Warehouse
Management System: User Guide.
3. In the Inspect Inbound Receipt Details screen, for each shipment or
order line,
e. From the Disposition Code drop-down list, select the appropriate
Disposition Code into which the product is transitioned.
f. Enter the quantity.
4. Enter any other detail required.
For more information about the field values, see the Sterling
Warehouse Management System: User Guide.
5. Click Save.

[Link] Inspection Putaway

For Putaway of the products after inspection, use the Create Move
Request console or the Mobile Application to create Move Requests to
divert the inspected products to the appropriate locations.

120 Implementation Guide

 Managing the Quality Control Process on the Warehouse Floor

12.4.2 Quality Control Flow For Receiving Using ASNs

The UI flow for QC while receiving using an ASN is explained in this
section.

[Link] Receiving Process

Follow these steps in the Receiving process:
1. Start the Receipt from the Inbound Order Shipment Details screen in
the Shipment Console using the Start Receipt action. The Start
Receipt pop-up window displays.
2. Enter the details required, and start the receipt by clicking Save.
If you are using the Mobile Application for receiving, start receiving
using the Mobile Application. Otherwise, follow Step 3 through Step
5.
3. Click the Receive action. The Receive Details screen displays.
4. In the Receive Details screen, enter the Disposition Code for products
requiring inspection (REQ-INSP) and click Save.
This step needs to be performed using the Mobile Application if you
are using the Mobile Application for Receiving.
5. In the Receipt Console, close the receipt by clicking Close Receipt.

[Link] Putaway Process

When the receipt is closed, putaway tasks are automatically generated
by the system. Depending upon the QC Percentage defined, part of the
receipt is diverted to the QC Zone. The rest may be diverted to storage.
The inventory status of the entire receipt is set to one which indicates
that the products are awaiting inspection.

[Link] Inspection Process

Follow the same steps as specified for the QC flow, for the inspection
process, while receiving using a PO. For more information about the QC
flow, for the inspection process, when you are receiving using a PO, see
Chapter [Link], "Inspection Process".

Quality Control 121

Reference Implementation for Quality Control

[Link] Inspection Putaway

For Putaway of the products after inspection, use the Create Move
Request console or the Mobile Application to create Move Requests to
divert the inspected products to the appropriate locations.

12.5 Reference Implementation for Quality

Control
In the Reference Implementation for Sterling Warehouse Management
System, we assume that the inventory received from VENDOR3 requires
Quality Check. As per the configuration, during receipt, 20 per cent of
the inventory received from VENDOR3 is sent to the QC Zone.
The Activity Code QC is used for the QC process. Inventory for the
Activity Code QC is automatically moved to the QC Zone. An appropriate
Putaway strategy is created for this.
Once the goods are diverted to the QC Zone, you can use the Inspect
Receipt screen to inspect the products. Upon quality inspection, a
particular disposition is then applied to the product, which results in the
inventory being classified into a specific Product Class and Inventory
Status combination.
If a quality problem is spotted during the inspection process, additional
inventory is manually retrieved to the QC Zone from storage.
After inspection, the user initiates the putting away of inventory into the
storage locations.
Sterling Warehouse Management System provides Reference
Implementation for the DC1 and DC3 organizations.
To run through the QC feature provided:
1. Ensure that Sterling Warehouse Management System is installed with
transaction data. For more information about installing Sterling
Warehouse Management System with transaction data see the
Sterling Warehouse Management System: Installation Guide.
2. In the Shipment console, select a shipment coming from VENDOR3.
3. Start Receipt and execute the Receipt process.
4. As per the QC process set, 20 percent of the inbound quantity is
diverted to the QC Zone for QC.

122 Implementation Guide

 Reference Implementation for Quality Control

As the inventory moves to and from the QC Zone, the changes in the
inventory status are:
1. When the inventory arrives, its Inventory Status is initially set to AI
(Awaiting Inspection).
2. Once the inspector completes the inspection, the inventory status
may be changed to:
Q
QC Passed: The product passed QC and is moved back to storage.
The product quantity is available to the system.
Q
QC Failed: The products are written off and the quantity becomes
unavailable to the system.

Note: When the product is moved to the QC Zone, the

entire shipment is marked Awaiting Inspection, even
though only a part of it is diverted for QC. Once the
product passes QC, the entire shipment is marked GOOD.

12.5.1 Putaway Preference Configuration

The Zone priorities defined as a part of the Sterling Warehouse
Management System Reference Implementation are shown in
Table 12–5.

Table 12–5 Zone Priorities

Priority Zone
100 QC-ZONE

Quality Control 123

Reference Implementation for Quality Control

124 Implementation Guide

 13
Vendor Compliance

Retailers are increasingly mandating stricter requirements and pushing

for better vendor performance. Consequently, Vendor Compliance is very
important to reduce operating expenses and streamline the supply chain.
To improve and ensure good Vendor Compliance, users can record, view,
modify, and delete shipment discrepancies at the shipment, container, or
item level. Users can also record any additional information, such as the
extra time spent due to non-compliance, and add brief notes on the
observations.
A shipment reference is mandatory to record the discrepancy details. The
discrepancy details recorded can be associated with the pricing
information and used to compute the charge back or fee that the vendors
need to pay for not adhering to the retailer’s compliance.
This chapter explains the Vendor Compliance process and solution
provided with Sterling Warehouse Management System.

13.1 Vendor Compliance Process

After inventory is received into a warehouse, if the vendor compliance
has not been met, the discrepancies are recorded in the system. This
information may be used to calculate the charge back or fee that the
vendors need to pay for non-compliance.
The Vendor Compliance process is:
1. Before the receipt starts, the user records the non-compliance
details, if any, for the shipment, container, or item. For example, the
user may record the non-compliance before starting the receipt if
there is information from the ASN regarding the shipment level
non-compliance.

Vendor Compliance 125

Vendor Compliance Configurations

2. During receipt, the user records the non-compliance details, if any,

for the shipment, container, or item. For example, the user may
record the non-compliance during the receipt process if the
non-compliance is observed while receiving items.
3. After the receipt is completed, the user records the non-compliance
details, if any, for the shipment, container, or item. For example, the
user may manually compute an audit for the non-compliance details
and record it against the shipment.
The discrepancy details recorded are sent to an external system and may
be associated with the pricing information. This is used to compute the
charge back that the vendors need to pay, for not adhering to the
retailer’s compliance.

13.2 Vendor Compliance Configurations

This section explains the configurations that may be done for the Vendor
Compliance process.

13.2.1 Setting Up the Discrepancy Codes

Discrepancy codes indicate the nature of the discrepancy. Discrepancy
codes can be set up at the Shipment, Container, and Unit or Item levels.
To set up the Discrepancy Codes:
1. Log in to the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Applications >
Application Platform.
4. From the tree in the application rules side panel, select Presentation
> Custom Common Codes.
5. The Custom Common Codes screen displays.
6. Select the Common Code Type to edit. The Common Code Values
pop-up window displays.

126 Implementation Guide

 Managing the Vendor Compliance Process on the Warehouse Floor

7. To edit an existing Discrepancy Code, select the appropriate code

value. To add a custom Discrepancy Code, click . The Discrepancy
Details pop-up window displays.
8. Edit or enter the appropriate values.
9. Click .

13.3 Managing the Vendor Compliance Process

on the Warehouse Floor
You can use the Application Console to perform Vendor Compliance.

13.3.1 Adding Discrepancy Details

To add Vendor Compliance discrepancy details:
1. Log in to the Application Console.
2. From the Application Console menu, select Inbound > Inbound
Shipment Console. The Inbound Order Shipment By Status search
screen displays.
3. Enter the search criteria for the inbound shipments required and click
Search. The Inbound Order Shipment List screen displays.
For more information about the field descriptions for the inbound
order shipments, see the Sterling Warehouse Management System:
User Guide.
4. Select the appropriate shipment and click Record Discrepancy. The
Discrepancy screen displays.
For information about the field values see Table 13–1 to Table 13–5.
5. In the Discrepancy screen do one or more of the following, as
necessary:
Q
Click in the Shipment Level Discrepancy area to enter shipment level
discrepancy details
Q
Click in the Container Level Discrepancy area to enter container level
discrepancy details
Q
Click in the Item Level Discrepancy area to enter item or unit level
discrepancy details

Vendor Compliance 127

Managing the Vendor Compliance Process on the Warehouse Floor

A new row displays that enables you to enter the discrepancy details.
6. Enter the appropriate details.
7. Click Record Discrepancy to record the discrepancy.

Note: To delete a row of details that you have just

entered and not saved, click the icon next to that row.

Table 13–1 Discrepancy, Shipment Information

Field Description
Shipment # Indicates the shipment number of the shipment.
Order # Indicates the order number of the shipment.
Status Indicates the status of the shipment.
Enterprise Indicates the enterprise associated with the shipment.
Buyer Indicates the buyer associated with the shipment.
Seller Indicates the seller associated with the shipment.
Ship Node Indicates the node from where the shipment ships.
Receiving Node Indicates the node that receives the shipment.
Carrier Indicates the carrier for the shipment.

Table 13–2 Discrepancy, Quantity Discrepancy

Field Description
Order # Indicates the order number of the shipment.
Line Indicates the order line number of the shipment.
Item ID Indicates the item identifier of the item for which the
discrepancy exists.
Product Class Indicates the product classification for the item for
which the discrepancy exists.
Unit Of Measure Indicates the unit of measure for the item for which
the discrepancy exists.

128 Implementation Guide

 Managing the Vendor Compliance Process on the Warehouse Floor

Table 13–2 Discrepancy, Quantity Discrepancy

Field Description
Discrepancy Type Indicates the type of discrepancy.
Typical values are Under Receipt, Over Receipt, and
Damaged.
Discrepancy Quantity Indicates the number of units of the item for which
the discrepancy exists.

Table 13–3 Discrepancy, Shipment Level Discrepancy

Action Description
Delete This action button deletes the selected shipment level
discrepancies.
Field Description
Discrepancy Code Select the nature of the discrepancy.
Notes Enter notes, if any.
Effort Enter the additional time required to work around the
discrepancy.
Compliance Checked Enter the user who verified the discrepancy.
By
Date Checked Enter the date on which the discrepancy was
observed.
You can also click to select the date.
Responsible Select Carrier if the carrier is responsible for the
discrepancy.
Select Seller if the seller is responsible for the
discrepancy.

Table 13–4 Discrepancy, Container Level Discrepancy

Action Description
Delete This action button deletes the selected container level
discrepancies.

Vendor Compliance 129

Managing the Vendor Compliance Process on the Warehouse Floor

Table 13–4 Discrepancy, Container Level Discrepancy

Field Description
Discrepancy Code Select the nature of the discrepancy.
Quantity Enter the number of units of the item for which the
discrepancy exists.
UOM Select the unit of measure for the item for which the
discrepancy exists.
Notes Enter notes, if any.
Effort Enter the additional time required to work around the
discrepancy.
Compliance Checked Enter the user who verified the discrepancy.
By
You can also click to select the user.
Date Checked Enter the date on which the discrepancy was
observed.
You can also click to select the date.
Responsible Select Carrier if the carrier is responsible for the
discrepancy.
Select Seller if the seller is responsible for the
discrepancy.

Table 13–5 Discrepancy, Item Level Discrepancy

Action Description
Delete This action button deletes the selected item level
discrepancies.
Field Description
Discrepancy Code Select the nature of the discrepancy.
Item ID Enter the item identifier of the item for which the
discrepancy exists.
You can also click to select the Item ID.
UOM Select the Unit of Measure of the item for which the
discrepancy exists.

130 Implementation Guide

 Managing the Vendor Compliance Process on the Warehouse Floor

Table 13–5 Discrepancy, Item Level Discrepancy

Quantity Enter the number of units of the item for which the
discrepancy exists.
Notes Enter notes, if any.
Effort Enter the additional time required to work around the
discrepancy.
Compliance Checked Enter the user who verified the discrepancy.
By
You can also click to select the user.
Date Checked Enter the date on which the discrepancy was
observed.
You can also click to select the date.
Responsible Select Carrier if the carrier is responsible for the
discrepancy.
Select Seller if the seller is responsible for the
discrepancy.

13.3.2 Editing Discrepancy Details

1. Complete Step 1 through Step 4 in Section 13.3.1, "Adding
Discrepancy Details".
2. Select the discrepancies to edit.
3. Edit the appropriate field values.
4. Click Record Discrepancy to record the revised discrepancy.

13.3.3 Deleting Discrepancy Details

1. Complete Step 1 through Step 4 in Section 13.3.1, "Adding
Discrepancy Details".
2. Select the discrepancies to delete.
3. To delete the selected discrepancies, do one or more of the following,
as necessary:
Q
Click Delete in the Shipment Level Discrepancy area to delete shipment
level discrepancy details
Q
Click Delete in the Container Level Discrepancy area to delete container
level discrepancy details

Vendor Compliance 131

Reference Implementation for Vendor Compliance

Q
Click Delete in the Item Level Discrepancy area to delete item or unit
level discrepancy details

13.4 Reference Implementation for Vendor

Compliance
This section explains the Reference Implementation provided by Sterling
Warehouse Management System for Vendor Compliance.

13.4.1 Discrepancy Codes Configuration

This section describes the custom common codes configured in Sterling
Warehouse Management System.
The following Custom Common Codes support Vendor Compliance been
added as a part of this feature:
Q
Shipment Discrepancy
Q
Container Discrepancy
Q
Item Discrepancy
For each discrepancy level a specific set of discrepancy codes are
provided. Users can use the Applications Manager to add more
non-compliance codes.

Shipment Level
The discrepancy or non-compliance checks that are supported at the
shipment level are listed in Table 13–6.

Table 13–6 Shipment Level Discrepancy Codes

Discrepancy Codes Description
ASN_NOT_SENT No ASN Sent
DELAYED_SHIPMENT Delayed Shipment
EARLY_ARRIVAL Early Arrival
INCORRECT_CARRIER Incorrect Carrier
INCORRECTLY_LABELED Incorrect Labels
INCORRECT_BOL_PRO_NO Incorrect Bill of Lading or Pro Number

132 Implementation Guide

 Reference Implementation for Vendor Compliance

Table 13–6 Shipment Level Discrepancy Codes

Discrepancy Codes Description
INCORRECT_FREIGHT_TERMS Incorrect Freight Terms
INCORRECT_ITEMS Incorrect Items
INCORRECT_ORDER_REFERENCE Incorrect Order Reference
INCORRECT_PACK_LIST Incorrect Pack List
INCORRECT_PALLETIZATION Incorrect Palletization
LATE_ARRIVAL Late Arrival
MISSING_BOL_PRO_NO Missing Bill of Lading or Pro Number
MISSING_LABELS Missing Labels
MISSING_MSDS Missing Hazmat Material Safety Data
Sheets (MSDS)
MISSING_PACK_LIST Missing Pack List
NOT_PALLETIZED Products Not Palletized
NO_APPOINTMNENT No Appointment
QUANTITY_DISCREPANCY Quantity Discrepancy

Container Level
The discrepancy or non-compliance checks that are supported at the
container (case or pallet) level are listed in Table 13–7.

Table 13–7 Container Level Discrepancy Codes

Discrepancy Codes Description
DAMAGED_PALLET Damaged Pallet
DAMAGED_UPC_CODE Damaged UPC code
INCORRECT_CARTON_SIZE Incorrect Carton Size
INCORRECT_PALLET_NUMBERING Incorrect Pallet Numbering
MIXED_SKU_LPN Mixed SKU LPN
NON_STANDARD_CASE Non Standard case
NON_STANDARD_PALLET Non Standard Pallet
NOT_MARKED_RETURNABLE Not Marked Returnable

Vendor Compliance 133

Reference Implementation for Vendor Compliance

Table 13–7 Container Level Discrepancy Codes

Discrepancy Codes Description
NOT_SCANNABLE_UPC_CODE UPC Code Not Scannable
NO_CASE_LABELS No Case Labels
NO_PALLET_LABELS No Pallet Labels
OVER_LOADED_PALLET Overloaded Pallet
PALLET_NOT_SHRINK_WRAPPED Pallet not wrapped
UPC_CODE_UNREADABLE UPC Code Not Readable
UPC_NOT_IN_ORDER UPC Code Not in Order
INCORRECT_UPC_CODE Incorrect UPC Code

Item or Unit Level

The discrepancy or non-compliance checks that are supported at the item
or unit level are listed in Table 13–8.

Table 13–8 Item or Unit Level Discrepancy Codes

Discrepancy Codes Description
INCORRECT_SKU Incorrect SKU
INCORRECT_TICKET_ LABELS Incorrect Ticket Labels
INCORRECT_UPC Incorrect UPC Code
ITEM_ATTRIBUTES_MISSING Item Attributes Missing
MISSING_TICKET_LABELS Missing Ticket Labels
OVER_SHIPPED_QUANTITY Over Shipped Quantity
SHORT_SHIPPED_QUANTITY Short Shipped Quantity

134 Implementation Guide

 14
Move Request

Move requests are created to ensure that inventory is moved from one to
location to another, within a warehouse, in an automated manner. These
are not representative of transfers between warehouses, which are actual
shipments.
This chapter explains the Move Request process and solution offered by
the Sterling Warehouse Management System.

14.1 Move Request Process

The Sterling Warehouse Management System utilizes the Move Request
framework to create tasks for warehouse processes, including Receiving
and Work Order processing (VAS). This is used in the operations for
quality recall or to move products from processing areas back to stocking
locations.

14.1.1 Mobile Application-Based Move Request Process

The Move Request process using the Mobile Application is:
1. The user selects the Putaway menu option on the mobile terminal.
2. The user scans an item or LPN to move.
3. If the system suggests to putaway more inventory, the user scans
another item or LPN to move.
4. The user performs Step 3 until either the equipment is full or the
system does not suggest any more putaway tasks.
5. The system indicates to the user that the next step is to deposit the
inventory.

Move Request 135

Move Request Configurations

6. The system presents the location to move the LPN into, based on the
item and location characteristics.
7. The user confirms the location where the deposit is completed.

14.1.2 Paper-Based Move Request Process

When moving using paper, a batch sheet is created for the move
requests that have been created for the paper-based process. If an LPN
is being moved, the LPN is also printed on the batch sheet. Users can
confirm the completion of the move using the Confirm Batch console
screen.

14.2 Move Request Configurations

This section explains the various configurations that may be done for the
Move Request process.

14.2.1 Agents
The agent configured for the Move Request processing is:
Move Request Purge
This agent deletes the move request from the system. This agent is run
every day. It deletes move requests that were created thirty days prior to
the current date.
For more information about this agent, see the Sterling Warehouse
Management System: Configuration Guide.

14.2.2 Services
The services provided for the Move Request process are:
Q
Print Move Tickets
This service prints move tickets in a paper-based warehouse.
Q
Generate Min Max Replenishment Move Request
This service creates Replenishment tasks with normal priority when
the inventory goes below the minimum level. For paper-based
warehouses, it also prints Move Tickets.

136 Implementation Guide

 Move Request Configurations

Q
Generate Top Off Replenishment Move Request
This service creates Replenishment tasks with low priority when the
inventory falls below the maximum level. For paper-based
warehouses, it also prints Move Tickets.

[Link] Print Move Tickets

When a Move Request is released, the ON_SUCCESS event of the
RELEASE_MOVE_REQUEST transaction is raised, which invokes the
PrintMoveTickets service.
The PrintMoveTickets service then prints the Move Tickets in a
paper-based warehouse. These Move Tickets are used for performing
Putaway tasks.
To activate the PrintMoveTickets service:
1. Navigate to the Move Request Transaction repository.
2. Associate the ON_SUCCESS event of the RELEASE_MOVE_REQUEST
transaction with the action Print Move Tickets, which invokes the
PrintMoveTickets service.

Note: This service is already activated if you have

installed the factory defaults with the events turned on.

[Link] Generate Min Max Replenishment Move Request

When the inventory falls below the minimum level, the
LOCN_INV_MONITOR agent calls the YNW_GenerateMinMaxRplMR_91
service.
This service then creates Replenishment tasks with normal priority. For
paper-based warehouses, it also prints Move Tickets.

[Link] Generate Top Off Replenishment Move Request

When the inventory goes below the maximum level, the
LOCN_INV_MONITOR agent calls the YNW_GenerateTopOffRplMR_91
service.
This service then creates replenishment tasks with low priority. For
paper-based warehouses, it also prints Move Tickets.

Move Request 137

Managing the Move Request Process on the Warehouse Floor

14.2.3 Prints
The PrintMoveTickets service is provided, which prints the Move Tickets.

14.2.4 Productivity
For all tasks associated with Move Requests, the productivity can be
determined, based on the Standard Allowable Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

14.3 Managing the Move Request Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform Move Requests. This section explains the UI flow for performing
move tasks.

14.3.1 Performing Move Tasks

The UI flow for performing Move Tasks depends on whether the
warehouse is paper-based or Mobile Application-based.

[Link] Using the Mobile Application

Follow these steps in the Move Request process:
1. Log in to the Mobile Application.
2. From the menu, select the Putaway menu option.
3. The system suggests the available tasks.
4. Scan the source location, appropriate inventory, and quantity.
5. Scan the target location.
6. Click Deposit. The move task is completed.
7. If more tasks exists, the system suggests them to the user.
Otherwise, the message "No Open Tasks" is displayed.

138 Implementation Guide

 Reference Implementation for Move Requests

[Link] Using Paper

Follow these steps in the Move Request process:
1. Users are provided putaway batch sheets that contain information
about the inventory to move.
2. Log in to the Application Console.
3. From the Application Console navigation bar, select Task > Confirm
Batch. The Batch Confirmation screen displays.
4. Enter the batch number and target location.
5. Click Confirm. The paper-based move is confirmed.

14.4 Reference Implementation for Move

Requests
This section explains the Reference Implementation provided by the
Sterling Warehouse Management System for Move Requests.

14.4.1 Move Request Task Types

The move request task types provided are shown in Table 14–1.

Table 14–1 Move request Task Types

Task Type Description
MOVE-0001 Paper Based move request Task type.
MOVE-0002 Mobile Application-Based move request Task Type

14.4.2 Move Request Cancellation Reasons

The different Move Request cancellation reasons provided by Sterling
Warehouse Management System are: Default, Miscellaneous, and Data
Entry Error.

14.4.3 Putaway Preferences

Once shipments are received, they are configured to automatically
generate tasks for Putaway. The service to generate a Putaway request is
configured as a part of the receipt transaction, on closure of the receipt.
Tasks are configured as one-step tasks. For all the task types, the

Move Request 139

Reference Implementation for Move Requests

Execute through Drop off Flag is set to “N”. Warehouses may manually
stage products in staging locations due to equipment constraints in the
destination aisle.
The considerations for putaway include:
Q
Location capacity.
Q
Putaway sequence.
Q
Consolidation opportunity along with locations that have the same
item, otherwise the items are placed in an empty location.
Q
Enterprise or other constraints.
Q
Location and item storage preferences based on Item Classification
(For example, Storage Type is Refrigerated).
Q
Zone and Task Type preferences.
Q
Receiving preferences for QC based on Enterprise, Vendor and Item
Classification (For example, Product Line is PL001).
The Sterling Warehouse Management System configurations for Putaway
Preferences are shown in Table 14–2.

Table 14–2 Putaway Preferences

Activity UOM Zones
Moving To Storage Less than Case FORWARD PICK
ZONES
Moving To Storage CASE BULK ZONES Tracking
Cases
Moving To Storage PALLET BULK ZONES Tracking
Pallets

[Link] Putaway Strategy

For paper-based warehouses, the Task Type MOVE-0001 is used. For
warehouses using the Mobile Application to execute the Putaway Tasks,
the Putaway strategy is configured to use the MOVE-0002 Task Type.

140 Implementation Guide

Reference Implementation for Move Requests

Move Request 141

Reference Implementation for Move Requests

142 Implementation Guide

 15
Count

A count system enables you to execute counts in a planned or ad hoc

manner. One common type of count employed is counting year-end
inventories, which, although exhaustive and time consuming, does not
ensure accuracy throughout the year. The other method is to only count
items based on velocity or price, every quarter. However, the best
method is to ensure that count is performed periodically in the system.
Counts are typically done to eliminate mismatches between the system
and the actual inventory.
Count tasks may be either generated for a cycle count program or
requested by the inventory control department ad hoc. Count tasks may
also be initiated through system events that occur at a location level.
This events may include an exception being recorded while performing an
activity, such as putaway, retrieval or pick, a location quantity dropping
below minimum levels or reaching zero, and so forth.
This chapter explains the Count processes and solution offered by the
Sterling Warehouse Management System.

15.1 Count Processes

The types of Count processes that may be followed are:
Q
Cycle Count Process
Q
Physical Count Process

15.1.1 Cycle Count Process

Cycle Counts are done for a group of locations, on a daily basis, to
ensure that location inventory mismatches are eliminated. The

Count 143
Count Processes

procedures available in count include the ability to generate tasks based

on zones, product classes, or item classifications. For example, Velocity
code is A, B, or C.
Count requests are generated on a periodic basis. Count tasks are
generated for the count requests created. The count tasks are then
executed through count sheets or through the Mobile Application.
As part of the Reference Implementation, a separate pipeline has been
configured for the Cycle Count process.
The simplified Cycle Count process is:
1. The users perform the first level count tasks.
2. If no variance is found, the count is purged.
3. If variances are found,
Q
Other users perform the variance tasks.
Q
Variances, if any, are accepted.
Q
The count is purged.

15.1.2 Physical Count Process

Physical Counts are performed to synchronize the physical and system
inventory and are required as a part of the corporate policy or client
requirements. During the physical count process, the warehouse is closed
and no other activity is performed.
Count tasks are generated for all the locations in the warehouse. The
Count tasks are then performed using count sheets or the Mobile
Application.
As part of the Reference Implementation, a separate pipeline has been
configured for the Physical Count process.
The Physical Count process is:
1. A group of users perform the first level count tasks using batch
sheets generated. The data is then entered into the system.
2. If no variance is found, the count is purged.
3. If variances are found:

144 Implementation Guide

 Count Processes

Q
A different group of users perform the second level variance tasks
for those locations found with a variance.
Q
A random set of second level variance count sheets is identified
and locations corresponding to these are counted and the count
quantity is entered.
Q
Variances, if any, are accepted.
Q
The count is purged.

[Link] Preparing for a Physical Count

To ensure a proper physical count, follow the steps and recommendations
in the following sections.

Configuration-Level Changes
The configuration-level changes that need to be performed when
preparing for a physical count are:
1. Creating a Pipeline-Related Configuration
2. Configuring a New Synchronous Service
3. Configuring a Task Type
4. Configuring Inventory Adjustment Reasons
5. Configuring Prints

Creating a Pipeline-Related Configuration

To create the pipeline-related configuration:
1. Log into the application as the system administrator.
2. Navigate to the Count Execution Repository.
3. Navigate to the Pipelines Repository.
4. Look for the Physical Count Execution Pipeline. To do this:
a. Open the existing pipeline and Save As the new physical count
pipeline.
b. Modify this pipeline to reflect all the transactions and statuses.
c. Click Save.

Count 145
Count Processes

Note: It is recommended that you do not modify this

pipeline once the physical count process begins.

Configuring a New Synchronous Service

To configure a new synchronous service, a new action, and enable the
ON_SUCCESS event:
1. Navigate to the Count Execution Services Repository.
2. Create a new synchronous service called YNW_CallPIBatchingService
as shown in Figure 15–1.

Figure 15–1 YNW_CallPIBatchingService

3. Click the XSL Translator component of the

YNW_CallPIBatchingService service. Configure it to invoke the
[Link] file. The XSL component
is located in the path template/xsl/ynw.
4. Click the API component of the service. Select Standard Sterling
Supply Chain API and select the createBatchForReferences API from
the drop-down list. Click Save.
5. Navigate to the Count Execution Action Repository.
6. Select Batching and click to create a new action called
InvokePIBatching.
7. In the Invoked Services tab, click . The Service List pop-up window
displays. Select the YNW_CallPIBatchingService synchronous service
and click . In the Action Detail screen, click .
8. Navigate to Transactions Repository.
9. For each of the following transactions, configure the ON_SUCCESS
event to invoke the InvokePIBatching action and click Save:
– Create Count Tasks
– Create Variance Tasks

146 Implementation Guide

 Count Processes

Configuring a Task Type

To configure task type configuration:
1. From the Applications Manager menu bar, select Warehouse
Management for the corresponding node.
2. From the tree in the application rules side panel, select Task
Management > Task Types. The Task Type screen displays.
3. Configure the Count Task types for the Activity group called COUNT
and select Use Sterling Warehouse Management System to plan trips
by batching tasks. Execute the tasks using Printed Tickets. The
number of count requests allowed is 1. To arrive at an optimal
number of tasks for each batch, refer to the example provided in
Section [Link].

Configuring Inventory Adjustment Reasons

To establish Inventory Adjustment-related configuration:
1. From the Applications Manager menu bar, select Warehouse
Management.
2. From the tree in the application rules side panel, select Inventory >
Inventory Adjustment Reasons.
3. The Inventory Adjustment Reasons screen displays. Ensure that the
Inventory Adjustment Reason code for the physical count is
associated with an accounting bin.

Note: This associated accounting bin MUST be in a zone

that tracks LPN.

Configuring Prints
To establish print-related configuration:
1. From the tree in the application rules side panel, select System
Administration > Devices. The Device Setup screen displays.
2. Ensure that the printer is configured to the "PICOUNTSHEET" Print
Document type. To do this, select your printer displayed in the Device
Setup screen. Click the Details tab. The Device Sub Type screen
displays. Select the Print Document Type as "PICOUNTSHEET". Click
Save.

Count 147
Count Processes

3. Copy the following files, located in the

<INSTALL_DIR>/repository/xapi/template/merged/prints/label
directory, to the print label directory set up for labels on your
Loftware print server: PI_CountSheet.lwl, PI_CountSheet_Last.lwl,
PI_CountSheet_Mid.lwl, [Link].
4. Navigate to the Task Execution Repository.
5. Navigate to the Transaction Repository.
6. Ensure that the BATCH_CREATED event is configured in the Create
Batch transaction. To do this, double-click on the BATCH_CREATED
event. Modify the displayed Print Count Sheet action to invoke the
PIPrintTaskList service instead of the PrintTaskList service. Click Save.

Transaction-Level Changes
The transaction-level changes that need to be performed when preparing
for a physical count are:
1. Searching for Staging Locations, Docks, and Shipping Lanes
2. Cleaning Up the Inventory in Virtual Locations
3. Searching for ASNs in Open Status
4. Searching for Shipments in Open Status
5. Cleaning Up the Inventory in Staging Locations, Docks, and Shipping
Lanes

Searching for Staging Locations, Docks, and Shipping Lanes

To search for all staging locations, docks, and shipping lanes:
1. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
2. From the Applications Manager menu bar, select Warehouse
Management > Warehouse Layout. Perform a search for a Location
and specify the Location Type as Staging to retrieve all staging
locations and shipping lanes. Likewise, enter the Location type as
Dock and Intransit to retrieve dock and intransit locations
respectively. Record all these retrieved locations on a paper.
3. Log out of the application and log in again as the node user.

148 Implementation Guide

 Count Processes

4. Ensure that all staging locations, docks, and shipping lanes are
empty. To do this, from the Application Console menu bar, select
Inventory > Location Inventory Console and perform a search for all
the staging locations, docks, and shipping lanes.

Cleaning Up the Inventory in Virtual Locations

Warehouses clean out the inventory in the virtual or accounting bin
locations at the beginning of a cycle or physical count process. For more
information about cleaning up the inventory in accounting bin locations,
see the Sterling Warehouse Management System: User Guide.

Searching for ASNs in Open Status

Ensure that all open ASNs for any quantity received is completely
received and closed as follows:
1. From the Application Console menu bar, select Task > Task Console
and search for all move tasks such as putaway, ad hoc,
replenishment, and kitting. The search should not return any records.

Note: Step 1 can be achieved by running the

ynw_pre_pi_checks.xml script with the menu option
"Count of Open Tasks by Activity Code and Task Type".
For more information about the ynw_pre_pi_checks.xml
script, see Section [Link], "Running the Pre-Physical
Inventory Script".

2. If the above search returns records, then all such tasks should either
be completed or canceled.
3. From the Application Console menu bar, select Inbound > Inbound
Receipt Console and search for receipts in Receipt Started and
Receipt In Progress statuses. The search should not return any
records.

Count 149
Count Processes

Note: Step 3 can be achieved by running the

ynw_pre_pi_checks.xml script with the menu option
"Count of Open Receipts by Status.".
For more information about the ynw_pre_pi_checks.xml
script, see Section [Link], "Running the Pre-Physical
Inventory Script".

4. If the above search returns records, then all such receipts should be
closed.

Searching for Shipments in Open Status

Ensure that no shipments are in Incomplete status. To do this:
1. From the Application Console menu bar, select Outbound > Outbound
Shipment Console.
2. Perform a search for shipments between the statuses.
This search should not return any records. If the search returns
records, all such shipments should either reach Shipment shipped or
Shipment canceled status.

Note: You can also ensure that no shipments are

Incomplete by running the ynw_pre_pi_checks.xml script
with the menu option "Count of Open Shipments by
Status".
For more information about the ynw_pre_pi_checks.xml
script, see Section [Link], "Running the Pre-Physical
Inventory Script".

Cleaning Up the Inventory in Staging Locations, Docks, and

Shipping Lanes
To clean up the inventory in staging locations, docks, and shipping lanes:
1. From the Application Console menu bar, select Inventory > Move
Request Console.
2. Perform a search for Move Requests in Released status.

150 Implementation Guide

 Count Processes

This search should not return any records. If the search returns
records, then all such Move Requests should either reach Closed
status or Canceled status.

Note: You can clean up the inventory in staging locations,

docks, and shipping lanes by running the
ynw_pre_pi_checks.xml script with the menu option
"Count of Open Move Requests By Status".
For more information about the ynw_pre_pi_checks.xml
script, see Section [Link], "Running the Pre-Physical
Inventory Script".

3. Before you begin the physical inventory count, ensure that no

background agents are running. Only the following count-related
agents should be running:
– Create Count Tasks
– Create Variance Tasks
– Auto Accept Variance
– Purge Count Request

[Link] Running the Pre-Physical Inventory Script

The ynw_pre_pi_checks.xml script helps you to generate a report on all
open tasks, and in the inventory available in the staging, virtual, and
in-transit locations. This report is generated in the pi_checks
<Node>.html file in the <INSTALL_DIR>/bin directory.
The ynw_pre_pi_checks.xml script is available in the <INSTALL_DIR>/bin
directory.
To run the pre-physical inventory script:
1. Perform the following steps:
a. Navigate to <INSTALL_DIR>/bin directory.
b. Set or export the YFS_HOME environment variable to
<INSTALL_DIR>/bin directory.
c. Execute the following command:

Count 151
Count Processes

./[Link] (cmd) -f ynw_pre_pi_checks.xml -DNode = <Node>

You need to specify the node for which you want to execute the
report as a parameter.
2. The above script generates a report in the pi_checks <Node>.html
file in the <INSTALL_DIR>/bin directory. This file contains the
following sections:
a. Staging and Virtual Location with Inventory
b. Count of Open Tasks by Activity Code and Task Type
c. Count of Open Shipments by Status
d. Count of Open Receipts by Status
e. Count of Open Move Requests By Status

[Link] Optimal Batch Sizes and Configuration Considerations

A warehouse has zones with locations of different size codes. Depending
on the size of the locations, the number of items or LPNs stored for each
location varies. Considering that each batch sheet is given to one single
user, it is important to ensure that the number of batches or count
sheets generated represent an equivalent distribution of work. The
following example illustrates this point:
Consider location size codes LS1, LS2, LS3, and LS4, capable of
accommodating a maximum of 1 LPN, 5 LPNs, 10 LPNs, and 20 LPNs,
respectively.
First-Level Count Tasks are generated at the location level. In a count
sheet, each row has a location, an LPN Number, and an Item.
Consider the following parameters:
Q
The approximate number of rows for each page = 10
Q
The number of tasks for each batch = 10
Q
The total number of rows = (Number of LPNs for each location x
Number of tasks per batch)
Q
Number of sheets for each batch = (Total Rows/ Rows per page)
Table 15–1 shows the count strategy used for each of the location size
code.

152 Implementation Guide

 Count Processes

Table 15–1 Count Strategy for Various Location Size Codes

Number of Sheets per
Location Size Codes Number of Rows Batch
LS1 1 x 10 = 10 10/10 = 1
LS2 5 x 10 = 50 50/10 = 5
LS3 10 X 10 = 100 100/10 = 10
LS4 20 x 10 = 200 200/10 = 20

Because each of the count sheets is given to one count operator, there is
variation in the quantum of work. To equalize this for all count operators,
you need to set up count strategies at the location size code levels.
Ensure that you keep the number of sheets for each batch to an optimal
level.
Now, configure separate location size codes for LS1, LS2, LS3, and LS4
with the corresponding count strategies CS1, CS2, CS3, and CS4. Each
count strategy maps to a task type that takes into account the size of the
location. The greater the location size, the smaller the number of tasks
for each batch. To achieve this, you should configure four task types: T1,
T2, T3, and T4 where the only variable parameter for each of this task
type is the limit on the number of tasks for each batch.
The number of tasks for each batch can be 10 for LS1, 2 for LS2, 1 for
LS3, and 1 for LS4.
Table 15–2 shows the minimum number of sheets for each batch using
this strategy and configuration.

Table 15–2 Count Strategy for Various Location Size Codes-II

Number of Sheets per
Location Size Code Number of Rows Batch
LS1 1 x 10 = 10 10/10 = 1
LS2 5 x 2 = 10 10/10 = 1
LS3 10 x 1 = 10 10/10 = 1
LS4 20 x 1 = 20 20/10 = 2

Count 153
Count Processes

[Link] Estimating the Personnel Requirements for Count Sheet

Data Entry During a Physical Count
The personnel requirements for data entry depends on various factors.
This section presents some guidelines on how to determine your specific
requirements and the factors that need consideration.
In one test that has been conducted, 10 locations (count tasks) for each
batch (count request) were configured and count sheets were generated.
The kind of location inventory profile used for this sample was that every
location had either one LPN or one item. These sheets were used to
perform the actual count and the data related to actual inventory was
recorded on them. These count sheets were then handed over to a
person who transferred the data from the sheet to the system by
searching for the count request number from the Application Console.
Tests were conducted for different types of batches. Samples included
batches that had a variance for 30% of its locations, some that did not
have a variance for any of its locations, and some that had locations with
inventory across multiple enterprises. The average time for data entry
was about 2 minutes for each batch sheet.
However, when actual count entries are done, the following factors also
need to be considered:
1. Regardless of the experience level of the count operator, there might
be clarifications they would need when they perform the actual
physical count. This clarification adds to the total time taken.
2. An operator who starts the day entering data spending two minutes
for each count sheet cannot be expected to be as efficient throughout
an entire eight- or ten-hour day. Fatigue sets in as the day
progresses.
3. If more variances are found, the time for the overall count entry
increases.
4. Considering the above three factors, it is recommended that you add
a time buffer of about 50% over the average of 2 minutes for each
count sheet. This results in allotting 3 minutes for each count sheet.

[Link].1 Calculations for a Warehouse with 15000 Locations

and One Task for Each Location

154 Implementation Guide

 Count Processes

1. 10 locations for each count sheet results in to 15000/10 = 1500

count sheets.
2. If it takes 3 minutes for each count sheet, then it amounts to
1500 x 3 = 4500 minutes (75 person hours) for count sheet entry
for the first round count sheet data entry.
3. Assuming 1 person day = 8 person hours, it amounts to 75/8 =
9.5 person days or 10 person days approximately.
4. Assuming that 30% of the tasks have variances, you have 15000
x 0.3 = 4500 tasks.
5. This amount may go up depending on the number of locations
having multiple items. Variance (second) count tasks are
generated at the location-item level as opposed to the Count
(first) tasks that are generated at the location level. To
accommodate for this factor, multiply it by a factor of 20% which
amounts to 4500 x 1.2 = 5400 tasks.
6. 5400 tasks translates into 5400/10 = 540 count sheets. Assuming
that variance count entry takes roughly the same time as count
entry, this will take 540 x 3= 1620 minutes.
7. Assuming 1 person day = 8 person hours, it amounts to 1620/60
x 8 = 3.5 person days or approximately 4 person days to enter
data for the second round counting.
Thus, it takes approximately 10 person days for the first count
and 4 person days for the variance count.

Note: The above description is just an example. You need

to consider other factors specific to your warehouse, which
have a bearing on data entry.

[Link] Getting Started

It is a good practice to have all the users logged out of Sterling
Warehouse Management System before starting the physical count
process.

Note: Generating physical count requests at the zone

level is recommended.

Count 155
Count Processes

To generate the physical count:

1. From the Application Console menu, select Inventory > Create Count
Request Console.
2. Create a count request for the Request Type "PHYSICAL COUNT" for a
zone ID.
3. When the Create Count Task agent runs, count tasks are created and
the batch number is stamped on them. Corresponding count sheets
are printed automatically on the configured printer.
4. Assign a group of count operators to count each zone. This is a
manual assignment where the user is instructed to count a certain
zone.

[Link] Count Sheet-Based Counting Process

The Count Sheet-Based process is:
1. The count operator collects the count sheets.
2. The count operator visits each location printed on the count sheet,
locates the item, and records the total quantity.
3. If a location has LPNs, the operator records the LPN quantity against
the LPN Number printed on the count sheet.
4. If a new LPN or loose item is found, the operator records the
information in the additional count sheet. For more information about
the template for the additional count sheet, see the Sterling
Warehouse Management System: Printed Documents Guide.

Note: The additional count sheet cannot be printed from

the Application Console. Instead, use the Physical Count
Sheet provided in the Sterling Warehouse Management
System: Printed Documents Guide.

5. The count operator hands over the count sheet to the data entry
operators to enter data into the system.
In the additional count sheet, enter the batch number, location, item,
LPN number, and so forth. Mark the additional page numbers on
these count sheets. The page number of the first additional count
sheet should succeed the page number of the last page in the printed

156 Implementation Guide

 Count Processes

count sheet. For example, if Batch Number 40000 has a total of 10

pages, the additional count sheet is marked as 11.

Note: The modify variance count feature is also available

after completing all the count tasks in a batch. However, it
should not be used to modify the count results.

[Link] Recording Quantity on Count Sheets

To record quantity on count sheets:
1. Each count sheet printed has the Batch Number stamped on it. Use
that number as a Control Number.
2. Count operators with Count Sheets should enter their user ID in the
"COUNTED BY" space at the top of the sheet.
3. For each Location on the Count Sheet, enter the Count Quantity
counted for each item or LPNs listed.
4. If an additional item or a new LPN is found in a Location, besides the
ones listed on the Count Sheet, use the additional count sheet
provided to enter the Location, LPN, Item, and Count Quantity. For
more information about the template for the additional count sheet,
see the Sterling Warehouse Management System: Printed Documents
Guide.

[Link] Completing Count Tasks

Once the count operator hands over the count sheets to the data entry
operators, the counted data is entered into the system. To complete a
count task from the Application Console, do the following:
1. From the Application Console menu bar, select Task > Confirm Batch.
2. Enter the Batch Number printed on the count sheet and select
Confirm. The Record Count Result Details screen displays for the first
task as part of the count sheet.
3. Enter the count quantity matching the items or LPNs as mentioned on
the count sheet. Click Save.
4. Click if the count sheet has more than one task to complete.

Count 157
Count Processes

5. After you enter the data for all the tasks as part of the count request,
the status of the count request changes from Count Task Created to
Count Task Completed or Count Task Completed With No Variance.

Note: If the count operator records one or more new

LPNs in any location when counting, record the new LPNs
as loose inventory upon completion of the count tasks.

[Link] Variance Count Process

The Variance Count process is:
1. When the Create Variance Task agent runs, the variance tasks are
generated for the locations found with a variance.
2. A new Batch Number is stamped on the count sheet and the count
sheets are printed automatically.
3. The count operator picks up the count sheet generated for the
variance tasks and visits each location.
4. When executing the variance tasks, the count operator locates the
item, and records the total quantity.
5. If a location has LPNs, the count operator records the LPN quantity
against the LPN Number printed on the sheet.
6. The count operator records the quantity of any loose inventory
separately on the printed count sheet.
7. When recording the variance tasks on the Record Count Result Details
screen, the system displays the system inventory similar to the
details shown during the first level count task. The variance tasks
generated must be completed like the first count tasks from the
Application Console.

Note: The Sterling Selling and Fulfillment Foundation

provides the ability to modify variance count in a batch.
The modify variance count feature can be used to modify
the variance tasks by updating the record count results.

158 Implementation Guide

 Count Processes

[Link] Completing Variance Tasks

Once the count operator hands over the count sheets to the data entry
operators, the counted data is entered into the system. To enter the
counted data into the system from the Application Console:
1. From the Application Console menu bar, select Task > Confirm Batch.
2. Enter the Batch Number printed on the count sheet and select
Confirm. The Record Count Result Details screen displays for the first
task as part of the count sheet.
3. Enter the count quantity matching the items or LPNs as entered on
the count sheet. Click Save.
4. Click if the count sheet has more than one task to complete.
5. Once you enter the count quantity for all of the tasks as part of the
count request, the status of the count request changes from Variance
Task Created to Variance Task Completed, Variance Task Completed
With No Variance, or Variance Task Completed With Resolvable
Variance.

[Link] Reprinting Count Sheets

If count operators decide to do a recount for some of the items found
with a variance, they need to reprint the count sheets. To do this:
1. From the Application Console menu bar, select Task > Task Console.
2. Select Task > Batch.
3. Enter the Batch Number and click Search. The Batch List screen
displays.
4. Select the entered Batch Number.
5. Click Print. The Print Dialog displays.
6. Select the Print Service name as PIPrintTaskList.
7. Select the configured printer.
8. Select the number of copies as 1.
9. The count sheet is printed with the Batch Number stamped on it.
All the records of the printed count sheets are similar to the ones that
were printed during the variance task creation. If you are not counting all
of the items, specify only those items on the count sheet that need to be

Count 159
Count Processes

counted. This is a manual activity where the count operator is instructed

to count certain items. Subsequently, the count sheets are handed over
to another count operator for recounting.

[Link] Recording Count Data

Once the count operator completes the counting and hands over the
count sheets to the data entry operators, the counted data is entered
into the system. To do this:
1. From the Application Console menu bar, select Task > Confirm Batch.
2. Enter the Batch Number printed on the count sheet and select
Confirm. The Update Count Result Details screen displays for the first
task as part of the count sheet.
3. Enter the count quantity for the recounted items. Click Save.
4. Click if the count sheet has more than one task to complete.
5. Once you enter the count quantity for all of the tasks as part of the
count request, the status of the count request does not change.

Note: The status of the count request remains the same

as it was during the variance task completion.

[Link] Post Physical Count

The physical inventory count ends only when all of the first count entry
and variance (recount) tasks have been completed. To ensure this:
1. From the Application Console menu bar, select Task > Task Console
and search for all the open tasks for the Activity Group "COUNT". This
search should not return any records. If the search returns records,
then all such count tasks should be Completed.
2. If a count operator has to record a new LPN in a location. The
operator can use the Ad hoc Move option in the Mobile Application to
convert the loose inventory recorded at the time of count results in
the Sterling Selling and Fulfillment Foundation into the new LPN
record. To perform this warehouse operation:
a. Log in to the Mobile Application as the RF or mobile application
user.

160 Implementation Guide

 Count Processes

b. From the Mobile Application menu bar, select Ad hoc Move.

c. Enter the source location and the item.
d. In the deposit screen, scan the item and quantity.
e. In the location field, scan the new LPN found and press Tab.
f. Scan the deposit location which is the same as the source location
in the location field.
g. Press F3 to confirm.
h. Press F10 to log out.

Note: Repeat Step a through Step f. for each LPN found.

3. To clean up the virtual accounting bin locations associated with the

Inventory Adjustment Reason code used during the physical count:
a. Set or export the YFS_HOME environment variable to
<INSTALL_DIR> directory.
b. Open the [Link] file from
the <INSTALL_DIR>/bin directory. Edit this file to provide the
appropriate values for the EnterpriseCode, Node, LocationId,
ReasonCode, and ReasonText attributes.

Note: The ReasonCode entered in the file should not be

associated with any accounting bin.

c. Ensure that the [Link] for WebSphere or [Link] for

WebLogic is available in your classpath.

d. From the <INSTALL_DIR>/bin directory, run the following ANT

command:
ant -f [Link]
4. After all the physical inventory tasks are complete, from the
Application Console menu bar, select Configuration > Launch
Applications Manager. The Applications Manager opens in a new
window.

Count 161
Count Processes

5. From the Applications Manager menu bar, select Applications >

Application Platform.
6. From the tree in the application rules side panel, select Process
Modeling. The Process Modeling screen displays.
7. In the Process Modeling screen, click General.
8. Navigate to the Transaction Repository and modify the Print Count
Sheet action associated with the BATCH_CREATED event to invoke
the PrintTaskList service instead of the PIPrintTaskList service. To do
this:
a. Select the Invoked Services tab in the Action Detail screen.
b. Select the PIPrintTaskList and click .
c. Click the Service List po-up window displays. Select
PrintTaskList and click .
d. Save and close the Action Detail screen.
e. Save and close the Transaction Detail screen.
9. Navigate to the Count Execution Repository.
10. Navigate to the Transaction Repository.

11. For each of the following transactions, disable the ON_SUCCESS

event to invoke the InvokePIBatching Action:
Q
Create Count Tasks
Q
Create Variance Tasks
12. Navigate to the Count Execution Services Repository.

13. Select YNW_CallPIBatchingService and delete it.

14. Navigate to the Actions Repository.

15. Select Batching and delete the InvokePIBatching action.

[Link] Canceling Physical Count

If you cancel a count request, the Sterling Warehouse Management
System cancels all count tasks without updating any information.

162 Implementation Guide

 Count Configurations

15.1.3 The Mobile Application-Based Count Process

To perform the Count process using the Mobile Application:
1. The operator logs in to the Mobile Application.
2. The system suggests the location to count.
3. The user scans the location and LPN, or the item and quantity.
4. If the count does not match, the user either confirms the count or
rescans the location and LPN, or the item and quantity.
5. Any variance reported is stored.
6. The system may suggest the next location to count if there are more
count tasks to be performed.
7. After the Count is completed, the supervisor logs in to the Mobile
Application.
8. The system lists the locations with Count variances.
9. The supervisor goes to a location and selects a variance task.
10. The system displays the location, item, and count quantity.

11. The supervisor counts the item and enters the lot information and
quantity.
12. The system is updated with the correct inventory picture.

13. The inventory adjustments are uploaded to the host system.

15.2 Count Configurations

This section explains the various configurations that may be done for the
Count process.

15.2.1 Count Pipelines

This section illustrates the various count pipelines.

Count 163
Count Configurations

[Link] Cycle Count Pipeline

Figure 15–2 illustrates the Cycle Count Pipeline.

Figure 15–2 Cycle Count Pipeline

15.2.2 Agents
The agents configured for the Count process are:
Q
Execute Count Program
This agent creates count requests based on the count program
defined. It also considers the count calender for generating tasks.
This agent is run once every day.
Q
Create Count Tasks
This agent creates new count tasks from the count requests that have
been generated.
Q
Create Second Tasks
This agent creates second count tasks at the request level for count
requests that have been generated.
Q
Create Variance Tasks
This agent creates variance-level tasks for count requests.

164 Implementation Guide

 Count Configurations

Q
Create Third Count Tasks
This agent creates third count tasks at the variance level for count
requests that have been generated.
Q
Auto Accept Variance
This agent accepts the variance of the count requests that have been
completed.
Q
Purge Count Request
This agent purges the completed count requests that were created
thirty days prior to the current date. It also purges the corresponding
count results of these count requests.
Q
Purge Corporate Count Request
This agent purges the corporate count program.
For detailed information about the agents and setting up the agent
criteria, see the Sterling Warehouse Management System: Configuration
Guide.

15.2.3 Prints
The ON_SUCCESS event of the CREATE_BATCH transaction prints the
Count Batch Sheet.

Note: This event is already activated if you have installed

the factory defaults with the events turned on.

15.2.4 Productivity
For all tasks, such as count and variance, associated with the Count
process, the productivity can be determined, based on the Standard
Allowable Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

Count 165
Reference Implementation for Count Processes

15.3 Managing the Count Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform Count tasks. This section explains the flow while performing
cycle count.

15.3.1 Flow For Performing Cycle Count

The flow for performing cycle count is:
1. Run the Execute Count Program agent. Count requests are
generated.
2. Run the Create Count Tasks agent. Count tasks are generated.
3. Complete the count tasks using either the Mobile Application or paper.
4. Run the Create Variance Tasks agent. Variance tasks are created.
5. Perform the variance tasks.
6. Run the Auto Accept Variance agent. The variances are accepted and
the inventory is adjusted.

15.4 Reference Implementation for Count

Processes
This section explains the Reference Implementation provided by the
Sterling Warehouse Management System for Count Processes.

15.4.1 Count Program

A default count program and calendar is provided.
The calender is marked with the days on which the warehouse is open.
These working days can also be changed by the supervisor.
Based on the working days in the calender and the Count Program
Conditions set, Count tasks are generated on the appropriate days.

166 Implementation Guide

 Reference Implementation for Count Processes

[Link] Count Calendar

This configuration is provided as a part of the Reference Implementation
of the Sterling Warehouse Management System.

Table 15–3 Count Calendar Configurations

Days Time Working Day
Monday to Sunday 00:00 to 23:59 Yes

To change your working days and shift times, you can create a new
calendar and associate it with the Count program. For more information
about creating a new calendar, see the Sterling Warehouse Management
System: Configuration Guide.

[Link] Count Program Conditions

The count program condition provided by Sterling Warehouse
Management System is Count Bulk Zones 156 times a Year.

15.4.2 Count Request Cancellation Reasons

The different Count request cancellation reasons provided by Sterling
Warehouse Management System are Default, Miscellaneous, and Data
Entry Error.

15.4.3 Count Task Types

Different Task Types must be created for Cycle and Physical Count. Count
tasks can be performed either through paper-based task types or
through mobile devices.
Table 15–4 lists the various Task Types that are created to facilitate the
Count processes.

Table 15–4 Count Task Types

Task Type Description
COUNT0001 Cycle Count to be performed using the Mobile
Application.
COUNT0002 Cycle Count to be performed using paper.

Count 167
Reference Implementation for Count Processes

Table 15–4 Count Task Types

Task Type Description
VARIANCE01 Cycle Count and Variance Task to be performed using
the Mobile Application.
VARIANCE02 Cycle Count and Variance Task to be performed using
paper.
COUNT0003 Physical Count to be performed using the Mobile
Application.
COUNT0004 Physical Count to be performed using paper.
COUNT0005 Task Type to perform Second level Physical Count. The
Count Task is performed using the Mobile Application.
COUNT0006 Task Type to perform Second level Physical Count.
The Count Task is performed using printed Count
Sheets.
VARIANCE03 Physical Count and Variance Task to be performed
using the Mobile Application.
VARIANCE04 Physical Count and Variance Task to be performed
using paper.

15.4.4 Count Strategy

Count strategies are provided by Sterling Warehouse Management
System for the distribution centers DC1 and DC3.
Table 15–5 lists the Count strategies for DC1.

Table 15–5 Count Strategies for DC1

Count Strategy Task Type Request Type
RF-Based Cycle Count COUNT0001
RF-Based Cycle Count COUNT0001 Cycle Count
Physical Count RF Based COUNT0003 Physical Count
Second Level Physical Count RF COUNT0005 Physical Count
Based
Cycle Count RF Based Second COUNT0005 Cycle Count
Level
Variance Physical Count RF Based VARIANCE03 Physical Count

168 Implementation Guide

 Reference Implementation for Count Processes

Table 15–5 Count Strategies for DC1

Count Strategy Task Type Request Type
Cycle Count Variance RF Based VARIANCE01
RF Based Variance Tasks VARIANCE01 Cycle Count

Table 15–6 lists the Count strategies for DC3.

Table 15–6 Count Strategies for DC3

Count Strategy Task Type Request Type
Cycle Count Paper Based COUNT0002
Cycle Count Paper Based COUNT0002 Cycle Count
Physical Count Paper Based COUNT0004 Physical Count
Second Level Physical Count paper COUNT0006 Physical Count
Based
Variance Physical Count Paper VARIANCE04 Physical Count
Based
Cycle Count Variance Task Paper VARIANCE02
Based
Variance Task Paper based VARIANCE02 Cycle Count

Count 169
Reference Implementation for Count Processes

170 Implementation Guide

 16
Outbound

The Outbound execution process starts from the point when pick tasks
are released for an outbound shipment and ends at the point where the
packages are loaded into trailers.
Seamless and flawless execution of this process is an integral part of how
reduced order turnaround time and inventory accuracy is achieved. The
ability of a system to mirror the routing of inventory in order to comply
with the customer and item requirements are key to reducing turnaround
time.
This chapter explains the Outbound process and solution offered by the
Sterling Warehouse Management System.

16.1 Outbound Process

The Outbound process includes managing and controlling outgoing
materials starting from the download of orders through to the shipping of
products from the warehouse. It combines the order download, wave
creation or release, pick, pack, and ship processes.
The Outbound process starts with routing the shipments. In this version
of Sterling Warehouse Management System, routing is considered to be a
part of the Master Data and the routing information should be installed
separately.
The Outbound rules configuration starts when the shipment status is
Sent To Node. It is assumed that, as a part of Sterling Warehouse
Management System, the routing information is handled explicitly.
Picking tasks are executed using the Mobile Application, batch sheets, or
Material Handling Equipments (MHE). During picking, additional

Outbound 171
Outbound Process

attributes, such as serial numbers can be captured. The Pick process

differs, based on which of these methods is used for execution.

16.1.1 The Mobile Application-Based Pick and Pack

Process
This section explains the Pick and Pack process for parcel shipments and
LTL/TL shipments in a Mobile Application-Based warehouse.

[Link] For Parcel Shipments

Orders are picked in a batch mode to allow for a 'pick and sort' type of
picking. They are then processed through a wave. The Mobile Application
Cart Manifest batch picking is also configured. In warehouses that use
the Mobile Application, all types of picks are executed using the
application.
Expedited orders are picked using the wave method. The use of this
model enables immediate release. This pick is executed using the Mobile
Application.
Containerization (volume and quantity) is performed by the system
during wave release and the items are picked directly into the shipping
container. The container is packed automatically as it is being picked.
The Cart Manifest Pick Execution process using the Mobile Application is:
1. The user, with the appropriate skill set, logs in to the Mobile
Application.
2. The system suggests the pick location and quantity to the user.
3. The user scans the tote number or cart number.
4. The user scans an LPN that matches the quantity asked.
5. The user is presented the next task to pick.
6. The shipment is dropped off at the location suggested and the
location is scanned for confirmation.
For Parcel shipments, picking and packing can be done using either:
Q
Full Case Pick and Pack Process
Q
Less than Case Pick and Pack Process

172 Implementation Guide

 Outbound Process

[Link].1 Full Case Pick and Pack Process

In this process, the user picks full cases from the bulk storage.
Though packing is not required for full case picking, the inventory is
brought into the weigh station to print the labels and add some dunnage
materials, if any. This is where the inventory container is converted into
an outbound container.
The Full Case Pick and Pack process using the Mobile Application is:
1. The system releases the wave.
2. Pick tasks are generated and suggested to the user. Nothing is
printed during the wave release.
3. The user logs in to the Mobile Application and scans the pallet.
4. The user performs the suggested case pick tasks.
5. The user picks the case, scans the pre-printed LPN label available on
the case, and places the case onto the pallet.
6. The user repeats Step 4 and Step 5 until either the pallet is full or all
the tasks are completed.
7. If either the pallet is full or all the tasks are completed, the inventory
is deposited at the weigh station.
8. The user scans the pre-printed SCM and completes the pack process
of the case manually by scanning the container at the Weigh Station.
9. Shipping labels are printed for the containers and the Pack List is
printed for the last container.

[Link].2 Less than Case Pick and Pack Process

The Cart Manifest Batch Pick process provided by the Mobile Application
is used to pick loose SKUs from the forward pick area. Products are
considered to be picked and then sorted.
The Less than Case Pick and Pack process using the Mobile Application is:
1. The system releases the wave.
2. Pick tasks are generated.
3. The system containerizes and batches the wave. Batch sheets are
printed.

Outbound 173
Outbound Process

4. The user, with appropriate skill set, logs in to the Mobile Application
and associates a cart with a batch number.
5. The user scans the containers.
6. The system suggests tasks to the user. The user scans the pick
location, item identifier, and quantity.
7. The system suggests the sort location and the user sorts the item to
the containers. Then the system suggests next sort location until all
picked items are sorted.
8. The user repeats Step 6 and Step 7 until either the cart is full or all
the tasks are completed
9. If either the cart is full or all the tasks are completed, the inventory is
deposited at the weigh station.
10. The user scans the container SCM and completes the pack process of
the case manually by scanning the container at the Weigh Station.
11. Shipping labels are printed for the containers and the Pack List is
printed for the last container.

[Link] For LTL/TL Shipments

LTL/TL shipments can be picked either from the Bulk or Forward Pick
areas based on the inventory availability. Tasks are most often suggested
to pick from the Bulk Storage. The Pick to Pallet Task Type is used to pick
from the Bulk Storage. If there are one or more picks from the Forward
Pick area, the inventory is finally consolidated at the shipment sort
locations.
Containerization (volume and quantity) is not performed by the system
for LTL/TL shipments.
The Mobile Application-Based Pick and Pack Process for LTL/TL shipments
follows the batch picking strategy, limiting the number of shipments per
batch to one. This ideally behaves like an order picking scenario.

[Link].1 Pick to Pallet Process

The Pick to Pallet process for LTL and TL shipments, using the Mobile
Application is:
1. The user picks the empty pallet, SCM label roll, and Fork Lift.

174 Implementation Guide

 Outbound Process

2. The user logs in to the Mobile Application.

3. The user scans the Fork Lift number (Equipment ID) in the Mobile
Application.
4. The user applies the SCM label on the pallet and scans the new pallet
SCM.
5. The user scans the location from which he or she is picking.
6. The user scans the LPN.
7. The user repeats Step 5 and Step 6 until either the pallet becomes
full or the pick for the order is complete.
8. The user deposits the pallet at the deposit location (usually the weigh
station).
9. The pallet is diverted to the pallet shrink wrap location once the
weight is captured.

Pallet Shrink Wrap Process

The Pallet Shrink Wrap process is:
1. The pallet is brought to the Pallet Shrink Wrap station and the user
scans the pallet.
2. The user shrink wraps the pallet and adds some dunnage material, if
any.
3. On shrink wrapping the pallet, the container or shipping label gets
printed. The user affixes the container or shipping label to the pallet.
4. The pallet is then manually moved to the shipment sorter location,
where the pallet is sorted based on the shipment. The pallet is then
loaded into the trailer.

[Link].2 Pick from Forward Pick Area Process

An order pick process is used to pick from the Forward Pick Area.
The Pick from Forward Pick process for LTL and TL shipments, using the
Mobile Application is:
1. The user picks an empty case and SCM label roll.
2. The user logs in to the Mobile Application.
3. The user scans the equipment ID used for picking.

Outbound 175
Outbound Process

4. The user scans the case.

5. The user scans the location from which he or she is picking.
6. The user scans the item number and enters the quantity.
7. The user repeats Step 5 and Step 6 until either the case becomes full
or the pick for the order is complete.
8. The user deposits the case at the deposit location (usually the weigh
station).
9. The user manually completes the pack process of the case by
scanning the container at the Confirm Carton Pack Complete station.
The shipping label gets generated for the container.
10. Once the weight has been captured, the case is manually moved to
the shipment sorter location. At the shipment sorter location, the
inventory is sorted by shipment and shipped out in the appropriate
carrier.

16.1.2 Paper-Based Pick and Pack Processes

This section explains the Full Case and Less Than Case Pick and Pack
process for parcel shipments in a paper-based warehouse.

[Link] Full Case Pick and Pack Process for Parcel Shipments
The paper-based full case pick and pack process for parcel shipments
follows the batch picking strategy. System-suggested containerization is
used for this process.
The Full Case Pick and Pack Process for Parcel Shipments in a
paper-based warehouse is:
1. The wave is released in the system.
2. As part of the wave release, the consolidated Batch Sheet and
container labels are printed for all shipments in the wave.
3. The supervisor hands over the Batch Sheet and container labels to
the user.
4. If the quantity to pick is equal to the case quantity, the user picks the
container and affixes the label.

176 Implementation Guide

 Outbound Process

If the quantity to pick is greater than the case quantity, the user
picks an empty container that can accommodate the quantity
specified in the label. The user then places the appropriate quantity
into the container and affixes the label to the container.
5. The user deposits the inventory at the appropriate location (usually
the Manifest station).
6. Later, the user confirms the batch. As a part of this batch
confirmation, the picking and packing are recorded on the system.

[Link] Less than Case Pick and Pack Process for Parcel
Shipments
This section explains the paper-based pick and pack process for parcel
shipments.

[Link].1 Pick Process

The less than case pick process for parcel shipments in a paper-based
warehouse follows the batch picking strategy.
System-suggested containerization is not used for this picking process.
The Less Than Case Pick Process for Parcel Shipments in a paper-based
warehouse is:
1. The wave is released in the system.
2. As part of the wave release, the Batch Sheet is printed for picking to
Parcel Shipments at the Forward Pick Area.
3. The supervisor hands over the Batch Sheet to the user.
4. The user carries the Batch Sheet and picks against the Batch Sheet.
5. The user deposits the inventory at the appropriate location (usually
the Pack Station).
6. Later, the user confirms the batch. As a part of this batch
confirmation, picking is recorded on the system.

Outbound 177
Outbound Process

[Link].2 Pack Process

The Less Than Case Pack process for Parcel Shipments in a paper-based
warehouse is:
1. The user scans the shipment information available on the Batch
Sheet.
2. The user clicks on the New Case or New Pallet action in the Pack
Station and adds the content into the container.
3. When the container is completely packed, the user manually closes
the container. On closing each container, the shipping label for the
particular container gets printed. Upon closing the last container of
the shipment, the packing slip gets printed.

[Link] Manifest Process

This section describes the manifest process for Parcel shipments.

[Link].1 Parcel Manifest

The standard Manifest process is followed for manifesting Parcel
Containers. Appropriate carrier labels are printed at the Manifest Station
for parcel containers. By default, FEDX integration is provided
out-of-the-box.

[Link] Pick and Pack Process for LTL/TL Shipments

This section explains the paper-based pick and pack process for LTL/TL
shipments.

[Link].1 Pick Process

The paper-based pick process for LTL/TL shipments follows the batch
picking strategy, limiting the number of shipments per batch to one. This
ideally behaves like an order picking scenario.
System-suggested containerization is not used for this process.
The paper-based pick process for LTL/TL shipments is:
1. The wave is released in the system.
2. As part of the wave release, separate Batch Sheets are printed for
each shipment included in the wave.

178 Implementation Guide

 Outbound Process

3. The supervisor hands over the Batch Sheet to the user.

4. The user picks the inventory from the location suggested in the Batch
Sheet (from the Bulk Area as well as the Forward Pick Area).
5. The user deposits the inventory at the appropriate location (usually
the Pack station).
6. Later, the user confirms the batch. As a part of this batch
confirmation, picking is recorded on the system.

[Link].2 Pack Process

The paper-based pack process for LTL/TL shipments is:
1. The user scans the shipment information available on the Batch
Sheet.
2. The user clicks on the New Case or New Pallet action in the Pack
Station.
3. When the container is completely packed, the user manually closes
the container. On closing each container, the shipping label for the
particular container gets printed. Upon closing the last container of
the shipment, the packing slip gets printed.

16.1.3 Material Handling Equipment-Based Pick Process

The MHE-based pick process enables picking using external systems,
such as, Pick to Light and Pick to Voice systems.
When a wave is released, if there are tasks designated for execution
using external systems, the MHE adapter generates interface files for
integration with these external systems. Each equipment type used for
picking has one interface file.
Sterling Warehouse Management System sends this interface file to the
external system and also prints the appropriate labels, batch sheet, or
packing list.
The Pick process for an MHE-based warehouse is:
1. The wave is released and recorded in Sterling Warehouse
Management System.

Outbound 179
Outbound Process

2. As part of the wave release, Sterling Warehouse Management System

sends interface files for each task (to be executed using the external
system) to the MHE.
Table 16–1 provides information about the details contained in the
interface files sent to the MHE.
3. The operator scans the barcode (Batch #, Carton #, or Shipment #)
on the external system.
4. The external system indicates the item and quantity to pick, for the
barcode scanned. For example, Pick To Light systems light up the
appropriate location with the quantity display.
5. The operator picks the items specified, deposits them in the
destination location, and indicates to the external system that the
picking is complete.
6. The external system sends back an interface file to the Sterling
Warehouse Management System to confirm the completion of the
pick.
Confirmation can be sent at various levels, such as CartonNo,
BatchNo, or ShipmentNo (task references).
Table 16–2 provides information about the details contained in the
interface files received from the MHE.
7. Sterling Warehouse Management System marks the tasks as
completed. When all the tasks of a batch are completed, Sterling
Warehouse Management System marks the batch as completed.
The same process is also followed for Parcel and LTL/TL shipments.

Table 16–1 Interface File Sent to the MHE

Field Description Start Position End Position
TaskHDR The record identifier. 1 7
TaskId The task identifier. 8 47
BatchNo The batch number. 48 87
ShipmentNo The shipment number. 88 127
CartonNo The carton number. 128 167
ItemId The item identifier. 168 207

180 Implementation Guide

 Outbound Process

Table 16–1 Interface File Sent to the MHE

Field Description Start Position End Position
Quantity The quantity. 208 221
UnitOfMeasure The unit of measure. 222 261
SourceZoneId The source zone. 262 301
SourceLocationId The source location. 302 341
TargetLocationId The target location. 342 381
PrimaryTaskReference The task reference. 382 421
ContainerScm The outbound 422 441
container SCM

Note: The interface file sent to the MHE is preceded by

"Start Here" and terminated by "All Done".

Table 16–2 Interface File Received From the MHE

Field Description Start Position End Position
TaskHDR The record identifier. 1 7
TaskId The task identifier. 8 47
BatchNo The batch number. 48 87
ShipmentNo The shipment number. 88 127
PickToContainer Either the outbound 128 167
container SCM or a
container number.
ItemId The item identifier. 168 207
Quantity The quantity. 208 221
UnitOfMeasure The unit of measure. 222 261
PickFromContainer The inventory 262 301
container SCM.
AssignedToUserId The user identifier. 302 341
It is mandatory to
pass this parameter.

Outbound 181
Outbound Process

Table 16–2 Interface File Received From the MHE

Field Description Start Position End Position
TargetLocationId The target location. 342 381
It is mandatory to
pass this parameter.
PrimaryTaskReference The task reference. 382 421

Note: Ensure that the start position and end position of

each field in the interface file is as specified in Table 16–2.
Failure to do so cause Sterling Warehouse Management
System to be unable to read the downloaded interface file.

16.1.4 Resource Planning Process

The Resource Planning tool provides warehouses the ability to plan for
expected workload and determine the number of resources required to
complete each activity. Having visibility to expected resources enables a
warehouse to accurately plan for overtime, temporary staffing, moving
demands to different dates, and so forth, thus optimizing the resource
costs.
This section explains the resource planning process with an example.
1. Consider that 5200 shipments must be shipped on 5/25/2006 to
multiple carriers and customers. A "Shipping" resource pool is
associated with the "Shipping" activity.
2. These shipments must be picked, packed, manifested, and shipped.
Each of these activities are associated to a resource pool with one or
more resources (operators) in the pool. For example, one or more
pickers are resources associated with the "Picking" resource pool.
Similarly, each resource pool has a set of resources. Consider there is
a shortage of resources in the warehouse for completing the
"Shipping" activity.
3. The outbound supervisor or warehouse manager who plans the
"Shipping" activity for 5/25/2006 logs in to the Application Console,
views the resource availability, and identifies shortages in some
resource pools.

182 Implementation Guide

 Outbound Process

4. The supervisor resolves the shortage by:

Q
Moving resources from other resource pools—If there is a less
demand for packers on 5/25/2006, the supervisor can move few
packers to the pickers resource pool to increase its capacity.
Q
Extending the shift timings by few hours—If the "Manifesting"
activity requires two extra hours of work by the available capacity,
the supervisor can extend the shift timings to meet the additional
requirement.
Q
Moving a few shipments to a future date—The supervisor can
move shipments to few customers to a future date, say
5/29/2006, by searching for shipments using multiple criteria on
the resource planning consoles.
5. The supervisor views the modified resource plan.
This is an iterative process. The supervisor revises the resource plan
till the demand and available capacity in all resource pools are
balanced.
6. The supervisor confirms the plan.
The final resource plan may have 4600 shipments ready to be
shipped on 5/25/2006 and 600 shipments moved to a future date.

16.1.5 Pack and Hold Process

Orders to be shipped in the future can be packed in advance. For
example, during certain seasons, orders may be placed in bulk. In such
cases, the shipments are picked and packed in advance to avoid overload
on the actual shipping day. Shipments that are packed and stored away
to be retrieved on the actual shipping day are known as Pack and Hold
shipments.
The Pack and Hold process using Sterling Warehouse Management
System is:
1. For warehouses that perform Pack and Hold, orders expected to be
shipped in the future are packed in advance, if the Pack and Hold flag
is checked for the shipments.
2. Putaway tasks are automatically generated by the system, when the
shipment pack is complete.

Outbound 183
Outbound Process

The Sterling Warehouse Management System provides a putaway

service to create a move request in order to move the shipment from
the Pack Station or Weigh Station to a designated Pack and Hold
location.
3. The shipping supervisor or warehouse manager selects the shipments
or loads containing shipments that are in Pack and Hold status.
4. Once the shipment or load is selected, the shipper manually retrieves
the shipments or loads to a selected location.

16.1.6 Electronic Shipper’s Export Declaration Process

Any shipper shipping international shipments from the United States of
America needs to file an electronic shipper’s export declaration (SED) for
Schedule B items with a value greater than $2500. The U.S. Census
Bureau and the U.S. Customs Service together offer an electronic
method for filing the SED, known as the Automated Export System
(AES). Participants in the AES include the United States Principal Parties
in Interest (USPPI).
After the electronic SED is filed through the AES, the Internal Transaction
Number (ITN) is generated.
The electronic SED filed is used for compiling the official U.S. export
statistics and for export control.
The Electronic SED process is as follows:
1. The shipments or loads included in an SED are kept on hold for filing
the SED.
2. The shipper submits the electronic SED to AES Direct using the AES
Direct Web Link or through Electronic Data Interchange (EDI).
3. After filing the SED through AES, the shipper gets the ITN.
4. For shipments, the shipper enters the ITN in the Shipment Details
screen. For loads, the shipper enters the ITN in the Load Details
screen.
After entering the ITN, the hold gets resolved.
5. For shipments, the containers carrier labels have the ITN stamped on
them when manifesting.

184 Implementation Guide

 Outbound Configurations

For loads, the shipper manually enters the ITN on the Load Bill Of
Lading (BOL).

16.2 Outbound Configurations

This section explains the various configurations that may be completed
for the Outbound execution process.

16.2.1 Outbound Pipeline

This section illustrates the various Outbound pipelines.

[Link] Outbound Pick Process Pipeline

Figure 16–1 illustrates the Outbound Pick process Pipeline.

Figure 16–1 Outbound Pick Process Pipeline

Outbound 185
Outbound Configurations

[Link] Outbound Container Pipeline for Outermost Cases

Figure 16–2 illustrates the Outbound Container Pipeline for outermost
cases.

Figure 16–2 Outbound Container Pipeline for Outermost Cases

[Link] Outbound Container Pipeline for Parcel Cases

Figure 16–3 illustrates the Outbound Container Pipeline for parcel cases.

Figure 16–3 Outbound Container Pipeline for Parcel Cases

[Link] Outbound Container Pipeline for Pallets

Figure 16–4 illustrates the Outbound Container Pipeline for pallets.

186 Implementation Guide

 Outbound Configurations

Figure 16–4 Outbound Container Pipeline for Pallets

[Link] Outbound Shipment Pipeline

Figure 16–5 illustrates the Outbound shipment Pipeline.

Figure 16–5 Outbound shipment Pipeline

Outbound 187
Outbound Configurations

[Link] Load Pipeline

Figure 16–6 illustrates the load pipeline.

Figure 16–6 Load Pipeline

16.2.2 Activities
Activities in the warehouse are grouped into Activity Groups. The Sterling
Warehouse Management System provides a pre-defined set of activity
groups for a warehouse. Examples of activity groups include Receipt,
Inspection, Value Added Services, and Packing.
Each activity group is associated with activity codes that define each
activity that is performed. The Packing activity group has these activities:
Pack and Resolve short pick, Pallet Shrink Wrap, and Carton Pack
Complete.

188 Implementation Guide

 Outbound Configurations

Note: Activity Codes may be defined only when the

Warehouse Management system tree is loaded for a Node
and Hub combination.

16.2.3 Agents
The agents configured for the Outbound processing are:
Q
Sent To Node
This agent changes the status of the shipment to Sent to Node.
Q
Create Wave
This agent creates waves based on the shipment selectors provided.
Q
Assign Lane
This agent assigns the lane for a shipment.
Q
Release Wave
This agent releases the waves and creates pick tasks for the
shipments.
Q
Containerize Wave
This agent creates system-suggested containers for the shipment.
Q
Batch Wave
This agent creates batches for tasks that require batching.
Q
Print Wave
This agent prints the various documents required for the wave, such
as, shipment labels, task lists, and so forth.
Q
Purge Wave
This agent deletes the wave from the shipment.
For detailed information about agents and setting up the agent criteria,
see the Sterling Warehouse Management System: Configuration Guide.

Outbound 189
Outbound Configurations

16.2.4 Services
This section describes the services provided for the Outbound process.

[Link] Change Shipment Status To Picked

When picking is completed for a shipment, the SHIPMENT_PICKED event
of the COMPLETE_TASK transaction is raised, which invokes the
YNW_changeShipmentStatusToPicked_91 service.
The YNW_changeShipmentStatusToPicked_91 service then changes the
shipment status to Picked.
To activate the YNW_changeShipmentStatusToPicked_91 service:
1. Navigate to the Task execution process.
2. Navigate to the Transaction repository.
3. Associate the SHIPMENT_PICKED event of the COMPLETE_TASK
transaction with the action Change Shipment Status, which invokes
the YNW_changeShipmentStatusToPicked_91 service.

Note: This service is already activated if you have

installed the factory defaults with the events turned on.

[Link] Print Load BOL

When the load is confirmed, the ON_SUCCESS event of the
RECEIVE_INTRANSIT_UPDATE transaction is raised, which invokes the
YNW_PrintLoadBOL_91 service. This service then prints the Bill of Lading
(BOL) of the load.
To activate the PrintLoadBOL service:
1. Navigate to the Load execution process.
2. Navigate to the Transaction repository.
3. Associate the ON_SUCCESS event of the
RECEIVE_INTRANSIT_UPDATE transaction with the action YNW Print
Load BOL(91), which invokes the PrintLoadBOL service.

190 Implementation Guide

 Outbound Configurations

Note: This service is already activated if you have

installed the factory defaults with the events turned on.

[Link] Alert Pro Number Set Expiration

When the PRO number reaches a certain threshold value, an alert is
raised by the service AlertProNumberSetExpiration.
To activate the AlertProNumberSetExpiration service:
1. Navigate to the Application Platform > Participant Modelling.
2. Select the node.
3. In the Node Attributes tab, click LTL Carrier Preferences.
4. Select any carrier from the list.
5. Click . The PRO Number Generation Scheme pop-up window
displays.
6. In the Notification Service drop-down list, select
AlertProNumberSetExpiration.

Note: This service is already activated by default.

[Link] Upload File To MHE

When the wave is released, the ON_SUCCESS event of the
PRINT_WAVE.4001 transaction is raised. Add the service
YNW_UploadFileToMHE_91 to the action YNW Print Wave(91). This
service then sends the interface file to the MHE.
To activate the YNW_UploadFileToMHE_91 service:
1. Navigate to the Outbound Picking Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_SUCCESS event of the PRINT_WAVE.4001
transaction with the action YNW Print Wave(91), which invokes the
YNW_UploadFileToMHE_91 service.

Outbound 191
Outbound Configurations

Note: It is mandatory that you modify the

customer_override.properties file in the
<INSTALL_DIR>/properties directory, and set the
following dynamic variables to point to the appropriate
locations:
Q
[Link]: Set this variable to point to the
yfs outputdirectory where Sterling Warehouse
Management System places the interface file for the
MHE.
Q
[Link]: Set this directory to point to
the yfs workingdirectory where the file is processed.
In addition, you also need to create the directories that
these variables point to, in your computer.
After making the changes, update the Sterling Selling and
Fulfillment Foundation runtime. For more information
about updating the Sterling Selling and Fulfillment
Foundation runtime, see the Sterling Warehouse
Management System: Installation Guide.

Note: This service is already activated by default.

[Link] Download File From MHE

The YNW_DownloadFileFromMHE_91 service is an asynchronous service.
The DownloadMHE server polls the incoming directory frequently, based
on the polling frequency configured. If the DownloadMHE server locates
an interface file in the incoming directory, it marks the task specified in
the interface file complete. When all the tasks of a batch are complete, it
marks the batch as completed.
The Argument tab of the Custom API component indicates the flow to be
invoked if the input file has only task references.

192 Implementation Guide

 Outbound Configurations

Note: It is mandatory that you modify the

customer_override.properties file in the
<INSTALL_DIR>/properties directory, and set the following
dynamic variables to point to the appropriate locations:
Q
[Link]: Set this variable to point to the
directory where the MHE places the interface file.
Q
[Link]: Set this variable to point to the
directory where the Sterling Warehouse Management
System places the interface file after the tasks are
completed.
Q
[Link]: Set this variable to point to the
directory where error logs, if any, are placed.
Q
[Link]: Set this variable to point to the
directory where the file is processed.
Q
[Link]: Set this variable to point to the
appropriate provider URL.
Q
yfs.MHE_QCF: Set this variable to point to the
appropriate Queue Connection Factory.
Q
[Link]: Set this variable to point to
the queue where the service queues up the tasks that
need to be completed.
In addition, you also need to create the directories that
these variables point to, in your computer.
After making the changes, update the Sterling Selling and
Fulfillment Foundation runtime. For more information
about updating the Sterling Selling and Fulfillment
Foundation runtime, see the Sterling Warehouse
Management System: Installation Guide.

Note: This service is already activated by default.

Outbound 193
Outbound Configurations

[Link] Download File To MHE With Reference

The YNW_DownloadFileToMHEWithReference_91 service is a synchronous
service.
When the MHE passes some reference instead of the task ID in the
interface file, this service inserts the tasks completed by the MHE into
the DownloadToMHEQueue.
If the name of this service changes, you also need to make the
corresponding change in the Arguments tab of the Custom API
component for the YNW_DownloadFileFromMHE_91 service. In the
Arguments tab, edit the Argument Value to the new name of the service
YNW_DownloadFileToMHEWithReference_91.

Note: This service is already activated by default.

[Link] Register Task Completion

The YNW_RegisterTaskCompletion_91 service is an asynchronous
service.
When this service is invoked, the MHEIntegrationJMSServer picks the
tasks to complete from the DownloadToMHEQueue and sends it to the
RegisterTaskCompletion API.

Note: This service is already activated by default.

[Link] Putaway Pack And Hold Shipment

When the packing for a shipment is complete and the shipment is moved
from the Pack Station or Weigh Station to the Pack and Hold location, the
PackAndHold hold type is applied to the Pack and Hold shipment, if the
hold type is configured. If the hold type is not configured, the hold is not
applied.
When all the containers of the shipment are packed the
ON_SHIPMENT_PACK_PROCESS_COMPLETE event is raised, which
invokes the YNW_PutAwayPackAndHoldShipment_91service.
The YNW_PutAwayPackAndHoldShipment_91 service creates one move
request for Pack and Hold shipments and one move request line for each
outermost container of the shipment. This move request generates the

194 Implementation Guide

 Outbound Configurations

tasks that move the outermost containers of the shipment from the Pack
Station or Weigh Station to the Pack and Hold location, according to the
putaway preferences configured for the PACK activity group. The move
request cannot be created unless the activities are properly set.
To activate the YNW_PutAwayShipment_91 service:
1. Navigate to the Pack Process Repository.
2. Navigate to the Transaction Repository.
3. Enable the ON_SHIPMENT_PACK_PROCESS_COMPLETE event of the
CHANGE_CONTAINER_STATUS or PACK_CONTAINER transaction.
4. Associate the ON_SHIPMENT_PACK_PROCESS_COMPLETE event with
the PutawayPackAndHoldShipment_91 action, which invokes the
YNW_PutAwayPackAndHoldShipment_91 service.

Note: You need to manually activate this service after

installing the factory defaults.

Note

Note: If you are following the Pack while Pick process for
Pack and Hold shipments, it is recommended that you
bring the container to the Weigh Station before starting
the putaway.

[Link] Send Retrieve Shipment Request

The YNW_SendRetrieveShipmentRequest_91 service is an asynchronous
service. This service places a request to retrieve a shipment from the
PACK_HOLD_QUEUE queue. When the user clicks the Retrieve Pack &
Hold Shipments action in the Shipment List screen or the OK button in
the Retrieve Pack & Hold Shipments pop-up window, the
YNW_SendRetrieveShipmentRequest_91 service is invoked.

[Link] Retrieve Pack and Hold Shipments

The YNW_RetrievePackAndHoldShipments_91 is an asynchronous
service.
When this service is invoked, the RetrievePackAndHoldShipments
integration server picks messages that are in the PACK_HOLD_QUEUE

Outbound 195
Outbound Configurations

queue and creates moves requests to move the outermost containers of

the Pack and Hold shipment into the requested location.

Note: It is mandatory that you modify the

customer_overrides.properties file in the
<INSTALL_DIR>/properties directory, and set the
following variables to point to the appropriate locations:
Q
PACK_AND_HOLD_QUEUE: Set this variable to point to
the queue where the service queues up the tasks to be
completed.
Q
Provider_URL: Set this variable to point to the
appropriate URL.
Q
PackandHold_QCF: Set this variable to point to the
appropriate Queue Connection Factory.
In addition, you also need to create the directories that
these variables point to, in your computer.
After making these changes, update the Sterling Selling
and Fulfillment Foundation runtime. For more information
about updating the Sterling Selling and Fulfillment
Foundation runtime, see the Sterling Warehouse
Management System: Installation Guide.

[Link] Process Retrieval For Pack and Hold Load

The YNW_ProcessRetrievalForPackAndHoldLoad_91 is an asynchronous
service.
When the user clicks the Retrieve Pack & Hold Shipments action in the
Load List screen, the YNW_ProcessRetrievalForPackAndHoldLoad_91
service is invoked.
This service gets a lists of all shipments included in the load and
internally calls the YNW_RetrievePackAndHoldShipments_91 service.
If you change the name of this service, you also need to make the
corresponding change in the Arguments tab of the Custom API
component for the YNW_ProcessRetrievalForPackAndHoldLoad_91
service. In the Arguments tab, edit the Argument Value to the new name
of the YNW_SendRetrieveShipmentRequest_91 service.

196 Implementation Guide

 Outbound Configurations

[Link] SED Filing

The electronic SED can be filed for a shipment or load based on the
condition mentioned in Section [Link].1, "Hold Condition", using the
xml obtained as an output of the YNW_SEDFiling_91 service.
When the YNW SED Filing(91) action is associated with the ON SUCCESS
event of the shipment level transaction, such as the
ON_SHIPMENT_PACK_PROCESS_COMPLETE transaction, the
YNW_SEDFiling_91 service gets invoked.
To activate the YNW_SEDFiling_91 service:
1. Navigate to the Outbound Shipment Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_SUCCESS event of the appropriate transaction in
the Shipment pipeline, such as the
ON_SHIPMENT_PACK_PROCESS_COMPLETE transaction, with the
YNW SED Filing(91) action. This invokes the YNW_SEDFiling_91
service.

Note: You can associate the ON_SUCCESS event of the

appropriate transaction in the Shipment pipeline, other
than the Confirm Shipment transaction.

[Link] SED Hold Resolution

When the ITN is generated after filing an SED, the user needs to enter
the ITN on the Shipment Details or Load Details console screen.
After the ITN is stamped on the Shipment Details or Load Details console
screen, the ON SUCCESS event of the Change Shipment or Modify Load
transaction is raised, which associates the YNW_SEDHoldResolution_91
service with the YNW SED Hold Resolution(91) action.
To activate the YNW_SEDHoldResolution_91 service:
1. Navigate to the Outbound Shipment Repository.
2. Navigate to the Transaction repository.
3. Associate the YNW SED Hold Resolution(91) action with the
ON_SUCCESS event of the Change Shipment transaction (for

Outbound 197
Outbound Configurations

shipments) or the Modify Load transaction (for loads). This invokes

the YNW_SEDHoldResolution_91 service for resolving the SED hold.

16.2.5 Shipment Monitor

This time-triggered transaction reports on the states of a shipment,
based on rules in the YFS_MONITOR_RULE table. This transaction
enables you to monitor the following situations:
Q
If the Shipment has been in a status for more than a specified
amount of time
Q
If the Shipment did not reach a status:
– n hours before a specified date
– n hours after a specified date
– n hours after reaching another status
Q
If the Shipment reached a status:
– n hours before a specified date
– n hours after a specified date
– n hours after reaching another status
Q
If the current time is:
– n hours before a specified date
– n hours after a specified date
– n hours after Shipment has reached a specified status
Q
If a specified date that is associated with the shipment is:
– n hours before another specified date
– n hours after another specified date
– n hours not before another specified date
– n hours not after another specified date
Monitoring rules can be configured for the shipment's origin and
destination points. They cannot be configured for a shipment's
intermediate pickup and drop off points. A shipment has intermediate
pickup or drop off only if it has multiple pickup or drop off points. For

198 Implementation Guide

 Outbound Configurations

example, a shipment has more than one load carrying it. The shipment
status on first load deposit, second load deposit, and so forth cannot be
monitored.
Once the last load deposits the shipment at its destination, then the
shipment status can be marked and monitored.
This is not a pipeline transaction. It also does not work from the task
queue.
For more information about milestones, date types, and monitoring rules,
see the Sterling Selling and Fulfillment Foundation: Application Platform
Configuration Guide.
This section describes the shipment monitor provided in the Outbound
process.

[Link] Packing Delayed

The YNW_PACKING_DELAYED_91 event is raised whenever shipments
which are due for shipping in two hours have not yet been packed. This
event invokes the service YNW_RaiseDelayInShipmentPackProcess_91,
which raises an alert to the SHIPPING queue.

16.2.6 Productivity
For all tasks, such as Picking and Packing associated with Outbound, the
productivity can be determined, based on the Standard Allowable
Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

16.2.7 Resource Planning

This section explains the various configurations that must be completed
for the resource planning process.

[Link] Enabling Resource Planning for a Node

Before you can use the resource planning feature for "Shipping", you
must enable resource planning for the node.
To configure the primary node attributes:
1. Log in to the application console as an administrator.

Outbound 199
Outbound Configurations

2. From the Application Console menu bar, select Configuration >

Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Applications >
Application Platform.
4. From the tree in the application rules side panel, select Participant
Modeling > Participant Setup. The Organization Search window
appears in the work area.
5. In the Organization Details window, select the Roles and Participation
tab > Node Attributes/Primary Info (on the right).
6. Select the Resource Planning Enabled check box to enable the
planning of resources and activities.
7. Enter other information in the applicable fields.
For more information about field value descriptions, see the Sterling
Selling and Fulfillment Foundation: Application Platform Configuration
Guide.
8. Click .

[Link] Configuring the Node for Planning

Configuring the node for planning is the initial step of resource planning.
This enables you to set up the planning calendar, shifts, and work days
for a ship node.
To configure the node for resource planning:
1. Log in to the application console as an Administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Applications >
Warehouse Management.
4. From the tree in the applications rule side panel, select Resource
Planning > Node Planning Attributes. The Node Attributes for Planning
screen appears.
5. Enter information in the applicable fields.

200 Implementation Guide

 Outbound Configurations

For more information about field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
6. Click .

[Link] Creating Resource Pools

A resource pool defines a set of resources that perform similar operations
in the warehouse.
To create a resource pool for "Shipping":
1. Log in to the application console as an administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Applications >
Warehouse Management.
4. From the tree in the applications rule side panel, select Resource
Planning > Resource Pools. The Resource Pool Search screen appears.
5. In the Resource Pool window, click . The Resource Pool Details
screen appears.
6. Enter "Shipping" as the Resource Pool ID.
7. Enter information in the applicable fields.
For more information about field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
8. Click .

[Link] Associating Resources to Resource Pools

You should assign resources to resource pools based on the requirement.
To associate resources to the "Shipping" resource pool:
1. From the Applications Manager menu bar, select Applications >
Warehouse Management.
2. From the tree in the applications rule side panel, select Resource
Planning > Resource Pools. The Resource Pool Search screen appears.
3. Select the "Shipping" resource pool. The Resource Pool Details screen
appears.

Outbound 201
Outbound Configurations

4. Click to add users to that resource pool. The Find User to Add to
Resource Pool screen appears.
5. Click icon to select users.

Note: A user can belong to only one resource pool at a

time. If a user is moved from one pool to another, the
default pool under which the user was originally accounted
changes.

[Link].1 Assigning Shifts to Resources

To assign shifts to resources:
1. From the Applications Manager menu bar, select Applications >
Warehouse Management.
2. From the tree in the applications rule side panel, select Resource
Planning > Resource Pools. The Resource Pool Search screen appears.
3. Select the "Shipping" resource pool. The Resource Pool Details screen
appears.
4. Select a particular resource. The Resource Details screen appears.
5. Choose the Shift Assignments tab.
6. Enter information in the applicable fields.
For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. Click .

[Link].2 Setting Resource Efficiency

You can set efficiencies for a resource within a particular resource pool.
This aids in tracking efficiency of each resource against various resource
pools.
To set efficiencies for a resource within the "Shipping" resource pool:
1. From the Applications Manager menu bar, select Applications >
Warehouse Management.

202 Implementation Guide

 Outbound Configurations

2. From the tree in the applications rule side panel, select Resource
Planning > Resource Pools. The Resource Pool Search screen appears.
3. Select the "Shipping" resource pool. The Resource Pool Details screen
appears.
4. Select a particular resource. The Resource Details screen appears.
5. Choose the Efficiencies tab.
6. Enter information in the applicable fields.
For more information about field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. Click .

[Link] Creating Task Type Resource Pool Associations

Task types are associated with a set of resource pools that are required
to perform a particular task. You can define conditions on various
attributes of a demand and associate a set of task types to this condition.
You can define a list of conditions within a condition set. Logically, each
condition represents related activities involved in fulfilling a demand. The
estimated capacity for fulfilling a demand is evaluated from the SAM
definitions associated with a task type.
You can create a new task type-resource pool association for "Shipping".
To create a task type-resource pool association:
1. Log in to the application console as an administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Applications >
Warehouse Management.
4. From the tree in the applications rule side panel, select Resource
Planning > Task Type Associations. The Task Type screen appears.
5. Select the Task Type Resource Pool Association Tab.
6. Click . The Task Type Resource Pool Association screen appears.
7. Enter information in the applicable fields.

Outbound 203
Outbound Configurations

For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
8. Click .

[Link] Creating Condition Sets

To create a condition set:
1. Log in to the application console as an Administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Applications >
Warehouse Management.
4. From the tree in the applications rule side panel, select Resource
Planning > Task Type Associations. The Task Type Association screen
appears.
5. Click . The Associate Resource Pools with Task Type screen
appears.
6. Enter information in the applicable fields.
7. Choose the Condition Task Type Association tab. The Condition Task
Type Association screen appears.
8. Click . The condition set pop-up window appears.
9. Enter information in the applicable fields.
For more information about field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
10. Click .

[Link] Creating Planned Task Conditions

The planned task conditions are created within a condition set.
To create a planned task condition:
1. From the Applications Manager menu bar, select Applications >
Warehouse Management.

204 Implementation Guide

 Outbound Configurations

2. From the tree in the applications rule side panel, select Resource
Planning > Task Type Associations. The Task Type Association screen
appears.
3. Choose the Condition Task Type Association tab. The Condition Task
Type Association screen appears.
4. Select the appropriate condition set and click . The Planned Task
Condition screen appears.
5. Enter information in the applicable fields.
For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
6. Click .

[Link].1 Creating Conditions

You can create condition names.
To create a condition name:
1. From the tree in the applications rule side panel, select Resource
Planning > Task Type Associations. The Task Type Association screen
appears.
2. Choose the Condition Task Type tab. The Condition Task Type
Association screen appears.
3. Choose the appropriate condition set and click . The Planned Task
Condition screen appears.
4. Click . The Condition Detail screen appears.
5. Enter information in the applicable fields.
For more information about field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
6. Click .

16.2.8 Task Generation for Pack and Hold Shipments

Orders to be shipped in the future can be packed in advance. For
example, during occasional seasons, orders may be placed in bulk. In
such cases, the shipments are picked and packed in advance to avoid
overload on the actual shipping day. Shipments that are packed and

Outbound 205
Outbound Configurations

stored away to be retrieved on the actual shipping day are known as

Pack and Hold shipments.
When the packing for a shipment is complete, putaway tasks are
automatically generated by the system. The Sterling Warehouse
Management System provides a service to create putaway tasks in order
to move the outermost containers of the Pack and Hold shipment from
the Pack Station or Weigh Station to the Pack and Hold location.
To configure putaway and retrieval of pack and hold shipments, you can
create a hold type and configure activity constraints.

[Link] Creating a Hold Type

When shipments are packed, the PackAndHold hold type is applied to all
shipments marked as Pack and Hold, if the PackAndHold hold type is
configured. The shipments to which this hold type is applied cannot be
shipped unless the hold type is resolved. The hold type is automatically
resolved once the shipments are retrieved.
The hold provided by Sterling Warehouse Management System is for the
DEFAULT enterprise. Your enterprise should either inherit configurations
from the DEFAULT enterprise, or have a copy of this hold type
implemented.
For more information about Creating a Hold Type, see the Sterling
Logistics Management: Configuration Guide.

[Link] Configuring Activity Constraints

Activities in the warehouse are grouped together in Activity Groups. Each
activity group is associated with activity codes that define each activity
that is performed.
To configure activity constraints:
1. Log in to the Sterling Selling and Fulfillment Foundation as an
administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the tree in the application rules side panel, select Warehouse
Management > Packing > Activities. The Activities screen appears.

206 Implementation Guide

 Outbound Configurations

4. Select the PACK activity code or any other activity code that you have
configured.
5. Click . The Putaway Preferences screen appears.
6. Select the Container with unknown contents tab.
7. Perform any one of the following:
a. To configure a pallet, click the Pallet tab.
b. To configure a case, click the Case tab.
8. Click . The Putaway Preference Details: Container with unknown
contents: Pallet or Putaway Preference Details: Container with
unknown contents: Case screen appears.
9. In Activity Code, select Moving to Storage.
10. In the Zone Priorities area, enter the appropriate Priority, and select
the appropriate Zone and Storage Code.
11. Click . The Applicable Putaway Strategies screen appears.
12. From the Putaway Strategies tree in the application rules side panel,
select Putaway to Storage. The Putaway Strategy Details screen
appears.
13. In the System Directed Putaway Task Types area, select the
appropriate Target Zone and Task Type.
14. Click .
For more information about defining activity constraints, see the
Sterling Warehouse Management System: Configuration Guide.

16.2.9 Electronic Shipper’s Export Declaration

Shippers of international shipments need to file the SED based on certain
conditions. The shipments or loads included in an SED are kept on hold
for filing the SED.

[Link] Creating a Hold Type

Shippers need to create the SEDHold hold type for both shipments and
loads. Shipments or loads to which this hold type is applied cannot be
shipped until the hold type is resolved. The hold type is resolved by the

Outbound 207
Outbound Configurations

system when the ITN is provided for the shipments or loads in the
Shipment Details or Load Details screens.

Shipments
To create a hold type for shipments:
1. Log in to the Sterling Selling and Fulfillment Foundation as an
administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the tree in the application rules side panel, select Logistic
Management > Document Specific (Shipping) > Sales Order > Hold
Types. The Hold Types : Sales Order (DEFAULT) screen appears.
4. Click . The Hold Type pop-up window appears.
5. In Hold Type, enter the hold type.
6. In Hold Type Description, enter the description of the hold.
7. Select the Hold Effects tab.
8. Click . The Transaction List pop-up window appears.
9. In the Available area:
a. Select the appropriate Process Type.
b. Use the right arrow to move the available modification types you
want to associate with the hold type.
10. Click .
For more information about creating a hold type, see the Sterling
Logistics Management: Configuration Guide.

Loads
To create a hold type for loads:
1. Log in to the Sterling Selling and Fulfillment Foundation as an
administrator.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.

208 Implementation Guide

 Outbound Configurations

3. From the tree in the application rules side panel, select Logistic
Management > Document Specific (Load) > Hold Types. The Hold
Types : Sales Order (DEFAULT) screen appears.
4. Click . The Hold Type pop-up window appears.
5. In Hold Type, enter the hold type.
6. In Hold Type Description, enter the description of the hold.
7. Select the Hold Effects tab.
8. Click . The Transaction List pop-up window appears.
9. From the Available area:
a. Select the appropriate Process Type.
b. Use the right arrow to move the available modification types you
want to associate with the hold type.
10. Click .
For more information about creating a hold type, see the Sterling
Logistics Management: Configuration Guide.

[Link].1 Hold Condition

The hold condition is an advanced XML condition. This condition displays
an advanced XML in the Applications Manager with readable text. The
values of the variables are customizable. When the hold condition is met
for a shipment or load, the SEDHold is applied to the load or shipment.
For more information about the XML generated by the system, see the
Chapter G, "XML Integration SED".
The shipper needs to file an electronic SED if the total cost of the
Schedule B items is greater than $2500 and the source and destination
countries are as specified in Table 16–3.

Table 16–3 Countries Requiring SED

From To
United States Canada (only if licence is required)
United States Foreign Countries
Puerto Rico United States

Outbound 209
Managing the Outbound Process on the Warehouse Floor

Table 16–3 Countries Requiring SED

From To
Puerto Rico Foreign Countries
Puerto Rico US Virgin Island
US Virgin Island Foreign Countries

The shipper does not need to file an electronic SED for the source and
destination countries specified in Table 16–4.

Table 16–4 Countries Not Requiring SED

From To
United States Canada (unless an export licence is
required)
US Virgin Islands United States
US Virgin Islands Puerto Rico

16.3 Managing the Outbound Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform the Outbound Process. This section explains the UI flow for
performing Outbound tasks.

16.3.1 Performing Outbound

The UI flow for performing Outbound consists of:
Q
Resource Planning
Q
Picking
Q
Packing
Q
Verify Packing
Q
Unpacking
Q
Converting Inventory Container to Outbound Container at the Weigh
Station

210 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

Q
Pallet Shrink Wrapping
Q
Manifesting Parcel Containers
Q
Confirming LTL/TL Loads
Q
Pack and Hold
Q
Electronic SED

[Link] Resource Planning

Use the Application Console to plan resources.
Resource Planning involves a combination of the following tasks, which
are explained in this section:
Q
Defining Standard Capacity
Q
Viewing Capacity Details
– Overriding Planned Capacity
– Transferring Resources Temporarily
– Extending Shifts for Resources
Q
Viewing Demand Details
– Moving Shipments
Q
Confirming a Plan

[Link].1 Defining Standard Capacity

To define the standard capacity for the "Shipping" resource pool:
1. From the navigation bar, select Outbound > Define Standard
Capacity. The Defining Standard Capacity screen appears.
2. Select the "Shipping" resource pool and click Standard Capacity. The
Resource Pool Current Standard Capacity Details screen appears.
3. Enter information in the applicable fields.
4. Click Save.
For more information about field value descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link].2 Viewing Capacity Details

Outbound 211
Managing the Outbound Process on the Warehouse Floor

To view the capacity details for various resource pools:

1. From the navigation bar, select Outbound > Resource Planning. The
RPCapacity Search By Date screen appears.
2. In Start Date, enter the date for which you want to begin planning
resources.
3. In #of days, enter the total number of days for which you want to
plan resources.
4. Within the Show Demand and Capacity Data in panel, choose the unit
of measure in which you want the capacity and demand to be
displayed.
5. Check the Consider Pending Task box, if you want to consider the
pending tasks to be completed as a backlog for the chosen date.
6. Click Search. The Resource Planning screen appears.
7. Within the Plan Resources Panel, when a capacity is chosen for a
resource pool on a specific date, the Capacity Details screen appears.

Overriding Planned Capacity

You can override the standard capacity allocated to an activity, according
to demand variations.
To change the planned capacity:
1. Open the Resource Planning screen.
2. Within the Other Resource Pools panel, click against the resource
pool for which you want to change the standard capacity.

3. Enter the new capacity values in the expanded view.

4. Click Save. The Override Capacity pop-up appears.
5. Enter the appropriate reason.
6. Click OK.
For more information about field value descriptions, see the Sterling
Warehouse Management System: User Guide.

Transferring Resources Temporarily

Use the Capacity Details screen to transfer resources from other resource
pools.

212 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

To transfer resources to the "Shipping" resource pool, from other

resource pools:
1. Open the Capacity Details screen.
2. Within the Other Resource Pools panel, choose the resources you
want to transfer and click Pull Resources. The Transfer Resources
screen appears.
3. Enter information in the applicable fields.
4. Click Save.
For more information about field value descriptions, see the Sterling
Warehouse Management System: User Guide.

Extending Shifts for Resources

You can extend shifts for a resource by assigning extra shifts, within a
resource pool.
To assign shifts to resources within the resource pool:
1. Open the Capacity Details screen.
2. Within the Member Resources panel, choose the resource you want to
assign to the shifts and click Assign Shifts. The Assign Shifts screen
appears.
3. Click to add new shifts and enter information in the applicable
fields.
4. Click Save.
For more information about field value descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link].3 Viewing Demand Details

You can view the resource demand details.
To view the resource demand details:
1. From the navigation bar, select Outbound > Resource Planning. The
RPCapacity Search By Date screen appears.
2. In Start Date, enter the date for which you want to begin planning
resources.

Outbound 213
Managing the Outbound Process on the Warehouse Floor

3. In #of days, enter the total number of days for which you want to
plan resources.
4. Within the Show Demand and Capacity Data in panel, choose the unit
of measure in which you want the capacity and demand to be
displayed.
5. Check the Consider Pending Task box, if you want to consider the
pending tasks to be completed as a backlog for the chosen date.
6. Click Search. The Resource Planning screen appears.
7. Choose the demand for a selected date against an appropriate
resource pool, the Demand Details screen appears.

Moving Shipments
You can move shipments to an appropriate date.
To move shipments to a later date:
1. Click against the appropriate date. The Move screen appears.
2. Enter information in the applicable fields.
3. Click Move.
For more information about field value descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link].4 Confirming a Plan

You can confirm a plan for resources.
To confirm the plan:
1. From the navigation bar, select Outbound > Resource Planning. The
RPCapacity Search By Date screen appears.
2. In Start Date, enter the date for which you want to begin planning
resources.
3. In #of days, enter the total number of days for which you want to
plan resources.
4. Within the Show Demand and Capacity Data in panel, choose the unit
of measure in which you want the capacity and demand to be
displayed.

214 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

5. Check the Consider Pending Task box, if you want to consider the
pending tasks to be completed as a backlog for the chosen date.
6. Click Search. The Resource Planning screen appears.
7. Click View Details. The Planning Summary screen appears.
8. Click Confirm Plan.
For more information about field value descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link] Picking
This section describes the picking process followed on the warehouse
floor.

[Link].1 Using the Mobile Application

With the Mobile Application, you can pick using one of the following
picking processes:
Q
Picking
Q
Cart Manifest Picking

Picking
The picking process using the Mobile Application is:
1. Log in to the Mobile Application.
2. From the Menu page, select Outbound Pick and press Enter. The
Criteria screen displays, which lets you enter the start location.
3. If you are picking a pallet or case and the system suggests to verify
the source location, verify the location.
4. If you are picking a non-license plated product, or a license plated
pallet or case, enter the SKU pick quantity.
If you are picking a non-license plated product by applying the license
plate, enter or scan the pre-printed license plate number.
5. If the system suggests SKU pick to a pallet, pick the SKU to a pallet.
If the system suggests SKU pick to a case, pick the SKU to a case.
6. If the system suggests a deposit task, deposit the pallet, case or SKU
into the system-suggested location.

Outbound 215
Managing the Outbound Process on the Warehouse Floor

For more information about field descriptions, see the Sterling Selling
and Fulfillment Foundation: Mobile Application User Guide.

Cart Manifest Picking

The Mobile Application Cart Manifest picking process enables you to
associate a cart that is used for picking inventory with a batch number.
This process is called inducting a cart.
The Cart Manifest picking process using the Mobile Application is:
1. Log in to the Mobile Application.
2. From the Menu page, select Induct Cart and press Enter. The Induct
Cart screen appears.
3. Scan the Cart ID and Batch # and associate the cart identifier with
the batch number.
4. The Cart Pick screen appears.
5. The system suggests the pick location, item identifier, and quantity.
6. Enter or scan the pick location, item identifier, and quantity.
7. The Sort screen appears, which suggests a slot location and quantity.
8. Scan the SCM of the container that is placed in the slot location and
sort the suggested quantity.
9. Repeat Step 7 and Step 8 until the sorting is complete.
10. Repeat Step 4 to Step 9 until the pick for the cart is complete.

11. The Deposit screen appears, which suggests the weighing location.

12. Click Deposit All. The inventory is deposited at the weigh station.
Complete the pack process of the case manually by scanning the
container at the Weigh Station.
For more information about field value descriptions, see the Sterling
Selling and Fulfillment Foundation: Mobile Application User Guide.

[Link].2 Using Printed Batch Sheets

Follow these steps in the Picking process:
1. Users are provided printed batch sheets that contain information
about the inventory to move.

216 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

2. Log in to the Application Console.

3. From the Application Console navigation bar, select Task > Confirm
Batch. The Batch Confirmation screen displays.
4. Enter the batch number and target location.
5. Click Confirm. The paper-based pick is confirmed.

[Link].3 Using Material Handling Equipment

Sterling Warehouse Management System automatically sends the
interface file to the MHE if external equipments are used for picking.
However, in case of exceptions, follow these steps to resend the interface
file to the MHE:
1. Log in to the Application Console as the warehouse manager or the
shipping supervisor.
2. From the Application Console navigation bar, select Outbound > Wave
Console. The Wave By Status search screen displays.
3. Enter the search criteria and click Search. The Wave List screen
displays.
4. In the Wave List screen do either of the following:
Q
Select the check box against the appropriate wave
Q
Click the appropriate Wave #
5. Click Send To MHE. The interface file is re-sent to the Material
Handling Equipment.

[Link] Packing
This section explains the pack process followed in a warehouse floor.

[Link].1 Execution Console-Based Packing

To perform pack:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select Outbound > Pack
Station. The Pack Details screen displays.
3. Enter or scan the appropriate information.

Outbound 217
Managing the Outbound Process on the Warehouse Floor

4. Click the Save action or press Alt+A to save the container properties
detail and packing notes, if entered.
5. Click the Reset action or press Alt+R to clear the information that you
entered or scanned.
6. After completing packing the container, click the Close Container
action to close the container.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link].2 Mobile Application-Based Packing

You can perform pack in the following two ways using the Mobile
Application:
Q
Shipment-Driven Packing
Q
Item-Driven Packing

Shipment-Driven Packing
You can perform Shipment-Driven Packing using the Mobile Application.
For more information about performing Shipment-Driven Packing using
the Mobile Application, see inSection E.2.1, "Shipment-Driven Packing" of
Appendix E, "Packing Using the Mobile Application".

Item-Driven Packing
You can perform Item-Driven Packing using the Mobile Application.
For more information about the packing process, see in Section E.2.2,
"Item-Driven Packing" of Appendix E, "Packing Using the Mobile
Application".

[Link] Verify Packing

You can verify packing for containers using the Mobile Application.
To verify packing:
1. Log in to the Mobile Application.
2. From the Menu, select Verify Pack and press Enter.
3. If the system suggests you to scan the pack location, scan the
location.

218 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

4. The Container Entry screen appears.

5. Enter or scan the container SCM.
6. If the system suggests you to scan the total number of units of items
in the container, scan the total number of units of items.
7. If the system shows you a mismatch, accept the mismatch or rescan
the total number of units of items.
8. If the system suggests you to scan total number of items in the
container, scan the total number of items.
9. If the system shows you a mismatch, accept the mismatch or rescan
the total number of items.
10. If the system suggests you to scan the item ID and item details, scan
the item ID and details.
11. If the system shows you a mismatch, accept the mismatch or rescan
the item ID and its details.
For more information about field value descriptions, see in Section E.3,
"Pack Verification" of Appendix E, "Packing Using the Mobile Application".

[Link] Unpacking
You can perform unpacking in the following two ways:

[Link].1 Execution Console-Based Unpacking

To unpack a container:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select Outbound > Pack
Station. The Pack Details screen displays.
3. Enter or scan the appropriate information.
4. Click the Unpack action to unpack the container whose details have
been entered.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link].2 Mobile Application-Based Unpacking

To perform unpack using the Mobile Application:

Outbound 219
Managing the Outbound Process on the Warehouse Floor

1. Log in to the Mobile Application.

2. From the Menu, select Unpack and press Enter. The Location Entry
screen appears which enables you to scan the location of unpack.
3. Enter or scan the location of unpack. The Container Entry screen
appears.
4. Enter or scan the container SCM.
5. The Unpack Criteria screen appears which enables you to scan the
carton SCM or item ID to be unpacked.
6. Enter or scan the carton SCM or item ID that you want to unpack.
7. If the system suggests you to scan the serial number for an item,
scan the serial number.
8. If the system suggests you to scan the lot number for an item, scan
the lot number.
9. If the system suggests you to scan the expiry date for an item, scan
the expiry date.
10. If the system suggests you to scan the quantity of an item unpacked,
scan the quantity.
For more information about field value descriptions, see in Section E.4,
"Unpacking" of Appendix E, "Packing Using the Mobile Application".

[Link] Converting Inventory Container to Outbound Container

at the Weigh Station
Follow these steps to convert an inventory container into an outbound
container:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select Outbound >
Weigh Station. The Weigh Station screen displays.
3. Enter or scan the appropriate information.
4. In Location, select the weigh station location.
5. In Scan Identifier, enter or scan the shipment number.

220 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

6. In Scan Identifier, enter or scan the inventory LPN. The system

automatically converts the inventory container into an outbound
container.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.

[Link] Pallet Shrink Wrapping

Follow these steps in the pallet shrink wrapping process:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select Outbound > Pallet
Shrink Wrap. The Pallet Shrink Wrap screen displays.
3. Enter or scan the pallet to shrink wrap.
4. Click Save. The pallet gets shrink wrapped.

[Link] Manifesting Parcel Containers

Follow these steps in the manifesting process:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select Outbound > Add
to Manifest. The Add to Manifest screen displays.
3. Enter or scan the parcel container.
4. Click the Add to Manifest action. The parcel container is manifested.

[Link] Confirming LTL/TL Loads

Follow these steps in the confirmation process:
1. Log into the Application Console.
2. From the Application Console navigation bar, select Outbound > Load
Console. The Load Search by Status screen displays.
3. Enter the criteria for searching the appropriate load.
4. From the Load List screen, select the load to confirm.
5. Click the Confirm Shipment action. The load is confirmed and the BOL
is printed.

Outbound 221
Managing the Outbound Process on the Warehouse Floor

[Link] Pack and Hold

This section explains the pack and hold process of the shipments and
loads.

[Link].1 Retrieval of Pack and Hold Shipments

Once a shipment is moved to a Pack and Hold location, the shipment
needs to be retrieved manually. The shipment supervisor or warehouse
manager looks for a Pack and Hold shipment being shipped that day and
retrieves the shipment containers to a location.
You can retrieve shipments using either the Retrieve Pack and Hold
Shipments screen or the Shipment List screen.
To retrieve shipments using the Retrieve Pack and Hold Shipments
screen:
1. Log in to the Sterling Selling and Fulfillment Foundation as a
warehouse manager or shipping supervisor.
2. Navigate to Outbound > Retrieve Pack And Hold Shipments. The
Retrieve Pack & Hold Shipments screen appears.
For field value descriptions, see Table 16–5.
3. Enter information in the applicable fields and click Retrieve. The
Retrieve Pack & Hold Shipments pop-up window appears.
For field value descriptions see Table 16–6 and Table 16–7.
4. In the Retrieve Pack And Hold Shipments area, enter information in
the applicable fields and click OK. The move request is generated for
the shipments.

Table 16–5 Retrieve Pack & Hold Shipments

Field Description
Node The node for which the Pack and Hold shipments are
retrieved.
Enterprise Select an enterprise. All pack and hold shipments of
this enterprise are selected to retrieve.
Buyer Select a buyer. All pack and hold shipments of this
buyer are selected to retrieve.
Seller Select a seller. All pack and hold shipments of this
seller are selected to retrieve.

222 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

Table 16–5 Retrieve Pack & Hold Shipments

Field Description
Shipment Mode Select a shipment mode. All pack and hold shipments
of this shipment mode are selected to retrieve.
Service Select the name of the carrier service. All pack and
hold shipments of the service are selected to retrieve.
Order # Select an order number. All pack and hold shipments
for this order number are selected to retrieve.
You can also click the icon to select the order
number.
Load # Select a load number. All pack and hold shipments for
this load number are selected to retrieve.
You can also click the icon to select the load
number.
BOL # Select a Bill Of Lading number. All pack and hold
shipments for this BOL number are selected to
retrieve.
PRO # Select a PRO Number. All pack and hold shipments for
this PRO number are selected to retrieve.
TRAILER # Select a trailer number. All pack and hold shipments
for this trailer number are selected to retrieve.
Held On Select a hold type. All shipments of this hold type for
the selected enterprise are listed.
All pack and hold shipments for this hold type are
selected to retrieve.
Expected Ship Date Enter the start expected ship date and time and the
end expected ship date and time. All pack and hold
shipments between this dates and times are selected
to retrieve.

You can also click the icons to choose the date.

Outbound 223
Managing the Outbound Process on the Warehouse Floor

Table 16–6 Retrieve Pack & Hold Shipments, Shipments Summary

Field Description
Number of Shipments The number of shipments satisfying the entered
criteria.
Number Of Shipment The total number of shipment lines satisfying the
Lines entered criteria.
No. of Pallets The number of pallets satisfying the entered criteria.
No. of Cases The number of cases satisfying the entered criteria.
Total Volume (CIN) The total volume of the shipments in cubic inches
satisfying the entered criteria.
Total Weight (LBS) The total weight of the shipments (in pounds)
satisfying the entered criteria.

Table 16–7 Retrieve Pack & Hold Shipments, Retrieve Pack And Hold
Shipments
Field Description
Location Enter the location into which you want to retrieve the
shipment. You can also click the icon to search for
the location.
It is mandatory to enter a value in this field.
Start No Earlier Than Enter the date and time to start the retrieval process

You can also click the icons to choose the date.

Finish No Later Than Enter the date and time to complete the retrieval
process.

You can also click the icons to choose the date.

To retrieve shipments that are in Pack and Hold status from the Shipment
List screen:
1. Log in to the Sterling Selling and Fulfillment Foundation as a
warehouse manager or shipping supervisor.
2. Navigate to Outbound > Outbound Shipment Console. The Shipment
By Status search screen appears.

224 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

3. Enter the appropriate details and click Search. The Shipment List
screen appears.
4. Check the boxes against the shipments to retrieve.
5. Select the Retrieve Pack & Hold Shipments action. The Retrieve Pack
& Hold Shipments pop-up window appears.
6. Enter information in the applicable fields.
For field value descriptions, see Table 16–9.
7. Click OK. The move request is generated for the loads.

Table 16–8 Retrieve Pack & Hold Shipments

Field Description
Location Enter the location into which you want to retrieve the
shipment. You can also click the icon to search for
the location.
It is mandatory to enter a value in this field.
Start No Earlier Than Enter the date and time to start the retrieving process.

You can also click the icons to choose the date.

Finish No Later Than Enter the date and time to complete the retrieving
process.

You can also click the icons to choose the date.

Note: Only the outermost containers of the Pack and Hold

shipments are considered for retrieving. These shipments
should have inventory in the Pack and Hold location and
should not have Putaway tasks already generated for
them.

[Link].2 Retrieval of Pack And Hold Loads

You can consolidate shipments that are in Pack and Hold status into a
load. You need to retrieve such loads manually to a location.
To retrieve loads using the Sterling Selling and Fulfillment Foundation:

Outbound 225
Managing the Outbound Process on the Warehouse Floor

1. Log in to the Sterling Selling and Fulfillment Foundation as a

warehouse manager or shipping supervisor.
2. Navigate to Outbound > Load Console. The Load By Status search
screen appears.
3. Enter the appropriate details and click Search. The Load List screen
appears.
4. Check the boxes against the loads to retrieve.
5. Select the Retrieve Pack & Hold Shipments action. The Retrieve Pack
& Hold Shipments pop-up window appears.
6. Enter information in the applicable fields.
For more information about the field value descriptions, see
Table 16–9.
7. Click OK. The move request is generated for the loads.

Table 16–9 Retrieve Pack And Hold Shipments

Field Description
Location Enter the location into which you want to retrieve the
load. You can also click the icon to search for the
location.
It is mandatory to enter a value in this field.
Start No Earlier Than Enter the date and time to start the retrieving process.

You can also click the icons to choose the date.

Finish No Later Than Enter the date and time to complete the retrieving
process.

You can also click the icons to choose the date.

Note: Only the outermost containers of the Pack and Hold

shipments present in the load are considered for
retrieving. These shipments should have inventory in the
Pack and Hold location and should not have Putaway tasks
already generated for them.

226 Implementation Guide

 Managing the Outbound Process on the Warehouse Floor

[Link] Electronic SED

The shipments or loads included in an SED are kept on hold for filing the
SED. After the electronic SED is filed for a shipment or load through AES
Direct, the ITN is generated. You need to enter the ITN for the shipments
or loads in the Shipment Details or Load Details screen.

[Link].1 Entering the ITN

This section explains how to enter the ITN for the following:
Q
Shipments
Q
Loads

Shipments
To enter the ITN for a shipment:
1. Log in to the Sterling Selling and Fulfillment Foundation as a
warehouse manager.
2. Navigate to Outbound > Outbound Shipment Console. The Shipment
By Status search screen appears.
3. Check Held Shipments and click Search. The Shipment List screen
appears.
4. Click the appropriate shipment number hyperlink. The Shipment
Details screen appears.
5. In ITN #, enter the ITN number generated for the SED to which the
shipment belongs. The hold gets resolved for the selected shipment.
For field value descriptions of the Shipment Details screen, see the
Sterling Warehouse Management System: User Guide.

Loads
To enter the ITN for a load:
1. Log in to the Sterling Selling and Fulfillment Foundation as a
warehouse manager.
2. Navigate to Inbound > Load Console. The Load By Status search
screen appears.
3. Check Held Loads and click Search. The Load Console Summary
screen appears.

Outbound 227
Reference Implementation for Outbound Processes

4. Check the box against the appropriate load and click View Details.
The Load List screen appears.
5. Click the appropriate load number hyperlink. The Load Details screen
appears.
6. In ITN #, enter the ITN number generated for the SED to which the
load belongs. The hold gets resolved for the selected load.
For field value descriptions of the Load Details screen, see the Sterling
Logistics Management: User Guide.

16.4 Reference Implementation for Outbound

Processes
This section explains the Reference Implementation provided by the
Sterling Warehouse Management System for outbound processes.

16.4.1 Shipment Groups

A shipment group can have multiple shipment selectors assigned to it. A
shipment selector consists of shipment item attributes used to distinguish
and group shipments.
The shipment selector criteria includes:
Q
Shipment attributes, including document type, Enterprise, priority,
order type, shipment value, Buyer, and receiving node.
Q
Delivery attributes, including mode and type of shipment, SCAC, and
service.
Q
Ship To attributes, including country or region and zip code.
Q
Turnaround time attributes, including requested ship date and cancel
dates.
Q
Item classifications. For example, Storage Code Refrigerated.
A shipment selector is a combination of all the attributes defined.
These constraints applied to each shipment are rolled up to a shipment
group level in order to limit the number of shipments released together.
A wave is created based on the defined constraints.

228 Implementation Guide

 Reference Implementation for Outbound Processes

The Shipment Groups created for the Sterling Warehouse Management

System include:

Table 16–10 Shipment Groups

Shipment Group Description Priority
Expedited Created for Emergency 10
Waves.
Parcel All Shipments with the Ship 20
Mode Parcel are grouped
into a single wave.
LTL-TL All Shipments with the Ship 30
Mode LTL/TL are grouped
together.
Catch all Catch all does not have any 40
shipment selector
configured. Shipments that
does not belong to the
Expedited, Parcel, or LTL-TL
shipment group are
captured in this group.

16.4.2 Pick Location Assignment Configuration

Pick Location Assignment (PLA) assigns warehouse locations to the
demand placed. PLA is defined at a shipment group level and can be
shared across multiple shipment groups. PLA rules are defined at the
item classification and UOM levels.
A list of zones are specified for a combination of item level attributes,
such as classifications and UOM. Multiple PLA rules may be specified to
ensure that the zone-level constraints are unique to the item
classification and UOM combination, or the item classification or UOM. For
example, for SKUs stocked in pallets, cases, and loose units, it is
advisable to have three distinct rules to cover zones that are applicable
for each UOM.
The PLA algorithm checks for inventory in the zones that are configured
for picking.

Outbound 229
Reference Implementation for Outbound Processes

The PLA configurations provided in the Sterling Warehouse Management

System are:

Table 16–11 PLA configurations

UOM ZONE
EACH (Less than Case) Forward Pick Zone and Dynamic Slotting Zone
CASE BULK-ZONEs
PALLET BULK-ZONEs

16.4.3 Task Types

This section describes the Task Types for Parcel and LTL/TL shipments,
Paper-Based picking, and Resource Planning.

[Link] Parcel Shipments

The Task Types used for the Mobile Application-based picking process are
displayed in Table 16–12.

Table 16–12 Parcel Shipments Task Type

System
Tasks Pack Suggested
Task Pick Performed while Containeri
Type Description Type Pick into through Pick zation
PICK000 Full Case Pick BatchPick Inventory Pallet Mobile N N
1 Device
PICK000 Cart Manifest BatchPick Container Mobile Y Y
2 Batch Pick (Case) Device
Using Mobile

230 Implementation Guide

 Reference Implementation for Outbound Processes

[Link] LTL/TL Shipments

The various Task Types that are created for picking LTL/TL shipments
are:

Table 16–13 LTL/TL Shipments Task Type

System
Tasks Pack Suggested
Task Pick Performed while Containeri
Type Description Type Pick into through Pick zation
PICK000 Pick to Pallet OrderPic Outbound Mobile Y N
3 k Container Device
(Pallet)
PICK000 Pick from OrderPic Outbound Mobile Y N
4 Forward Pick k Container Device
Area (Case)

[Link] Paper-Based Pick

The various Task Types that are created for Paper-Based picking are:

Table 16–14 Paper-based Picking Task Type

System
Tasks Pack Suggested
Task Pick Performed while Containeriz
Type Description Type Pick into through Pick ation
PICK00 Full Case Pick BatchPick Outbound Printed Y Y
09 for Parcel Container Tickets
(None)
PICK00 Pick for Parcel BatchPick Outbound Printed N N
10 at FPA Container Tickets
(None)
PICK00 Pick LTL/TL BatchPick Outbound Printed N N
11 Shipment Container Tickets
wise (None)

Outbound 231
Reference Implementation for Outbound Processes

16.4.4 Pick Exceptions

The pick exceptions that have been configured as a part of the Reference
Implementation in the Sterling Warehouse Management System are:

Table 16–15 Pick Exceptions

Exception Code Description Configuration
SHORTPICK Short Pick Suggest alternate pick location.
NOINV Inventory not Found Hold Task.

16.4.5 Activity Constraints Configuration

Activities in the warehouse are performed based on the attributes of the
inventory. The attributes considered are single-SKU inventory, multi-SKU
inventory, and container. Activity constraints define the constraints that
are in place for these activities.
Location priorities have been defined as a part of the Sterling Warehouse
Management System Reference Implementation.

[Link] Packing
This section explains the location priorities for Packing activities.

[Link].1 Non-Standard Single-SKU Container

Table 16–16 illustrates the location priorities for a Non-Standard
Single-SKU Container.

Table 16–16 Location Priorities

Priority Location
1 P1-000001
2 P1-000002
3 W1-000001
4 W1-000002

[Link].2 Standard Single-SKU Container

Table 16–17 illustrates the location priorities for a Standard Single-SKU
Container.

232 Implementation Guide

 Reference Implementation for Outbound Processes

Table 16–17 Location Priorities

Priority Location
100 W1-000001
200 W1-000002

[Link].3 Multi-SKU or Multi Level Container

Table 16–18 illustrates the location priorities for a Multi-SKU or
Multi-Level Container:

Table 16–18 Location Priorities

Priority Location
1 W1-000001
2 W1-000002

[Link] Pallet Shrink Wrap

Table 16–19 illustrates the location priorities for Pallet Shrink Wrap
activities.

Table 16–19 Location Priorities

Priority Location
10 W1-000001
20 W1-000002

[Link] Carton Pack Complete

Table 16–20 illustrates the location priorities for Carton Pack Complete
activities.

Table 16–20 Location Priorities

Priority Location
100 W1-000001
200 W1-000002

Outbound 233
Reference Implementation for Outbound Processes

16.4.6 Resource Planning

This section explains the Reference Implementation provided by the
Sterling Warehouse Management System for resource planning.

[Link] Node Planning Attributes

Configuring the node attributes is the initial step for resource planning. It
enables you to set up the calendar, shifts, service slots, and work days
for a ship node.
Table 16–21 lists the shifts and their timings set for the DC1 node.

Table 16–21 Shifts

Shifts Timings
Morning 08:00 - 16:00
Evening 16:00 - 23:59
Night 00:00 - 08:00

[Link] Resource Pool

A resource pool defines a set of resources that perform similar operations
in the warehouse. A resource pool is an aggregate collection of
resources.
The different resource pools for DC1 include:
Q
Weighing
Q
Picking
Q
Packing
Q
VAS
Q
Shipping
Q
Pack Station
Q
Weigh Station
Q
Manifest Station
Q
Fork Lift
Q
Cart

234 Implementation Guide

 Reference Implementation for Outbound Processes

Each resource pool is associated with a certain type of activity and has
one or multiple resources allocated to it. Resource pools defined for
Stations and Equipments are considered to be resources in the
warehouse and no other resources are allocated to these resource pools.
The capacity for each resource pool is calculated taking various factors
into account, such as the number of default users for that resource pool,
number of users who are pulled into that resource pool and their
efficiencies, and the period of their shift.
Table 16–22 lists the users associated with the Weighing resource pool
and the shift allotted to them. This table also displays the efficiency of
the user for each activity related to the other resource pools. All the
users are assumed to be efficient within the Weighing resource pool,
which is allotted to them.

Table 16–22 Weighing Resource Pool

Users Shift Resource Pool Efficiency
DC1Weigher1 Night Shift Weighing 100
(Weighing Operator)
Picking 30
Packing 70
VAS 20
Shipping 90
DC1Weigher2 Morning Shift Weighing 100
(Weighing Operator)
Picking 20
Packing 100
Shipping 80

Table 16–23 lists the users associated with the Picking resource pool and
the shift allotted to them. This table also displays the efficiency of the
user for each activity related to the other resource pools. All the users
are assumed to be efficient within the Picking resource pool, which is
allotted to them.

Outbound 235
Reference Implementation for Outbound Processes

Table 16–23 Picking Resource Pool

Users Shift Resource Pool Efficiency
DC1Picker1 (Picker) Night Shift Weighing 20
Picking 100
VAS 10
Shipping 40
DC1Picker2 (Picker) Night Shift Weighing 60
Picking 100
Packing 30
VAS 40
Shipping 50
DC1Picker3 (Picker) Morning Shift Weighing 40
Picking 100
Packing 30
VAS 60
Shipping 70
DC1Picker4(Picker) Evening Shift Weighing 30
Picking 100
Packing 20
VAS 10
DC1Picker5 (Picker) Evening Shift Picking 100

Table 16–24 lists the users associated with the Packing resource pool and
the shift allotted to them. This table also displays the efficiency of the
user for each activity related to the other resource pools. All the users
are assumed to be efficient within the Packing resource pool, which is
allotted to them.

236 Implementation Guide

 Reference Implementation for Outbound Processes

Table 16–24 Packing Resource Pool

Users Shift Resource Pool Efficiency
DC1Packer1 (Packer) Night Shift Weighing 100
Picking 10
Packing 100
VAS 80
Shipping 20
DC1Packer2 (Packer) Morning Shift Weighing 80
Picking 30
Packing 100
VAS 90
Shipping 10

Table 16–25 lists the users associated with the VAS Station Operator
resource pool and the shift allotted to them. This table also displays the
efficiency of the user for each activity related to the other resource pools.
All the users are assumed to be efficient within the VAS Station Operator
resource pool, which is allotted to them.

Table 16–25 VAS Station Operator Resource Pool

Users Shift Resource Pool Efficiency
DC1Vas1 (Vas Station Morning Shift Weighing 30
Operator)
Picking 20
Packing 90
VAS 100
DC1Vas2 (Vas Station Evening Shift Packing 80
Operator)
VAS 100

Table 16–26 lists the users associated with the Shipping resource pool
and the shift allotted to them. This table also displays the efficiency of
the user for each activity related to the other resource pools. All the

Outbound 237
Reference Implementation for Outbound Processes

users are assumed to be efficient within the Shipping resource pool,

which is allotted to them.

Table 16–26 Shipping Resource Pool

Users Shift Resource Pool Efficiency
DC1Shipper1 (Shipper) Morning Shift Weighing 80
Shipping 100
DC1Shipper2 (Shipper) Evening Shift Weighing 60
Picking 30
Packing 20
VAS 10
Shipping 100

[Link] Task Type Associations

A task type represents a process in the warehouse and is associated with
one or more set of resource pools that are required when performing a
particular task.
Table 16–27 lists the task types provided with Sterling Warehouse
Management System along with their resource pools.

Table 16–27 Task Types

Productivity
Task Type Tasks Type Defined Type Resource Pools
PICK0001 Full Case Pick using mobile Picking at bulk Picking, Forklift
PICK0002 Cart Manifest Batch Pick using Picking active area Picking, Cart
mobile
PICK0003 Pick to Pallet Picking at bulk Picking, Fork Lift
PICK0004 Pick from Forward Pick Area Picking active area Picking, Fork Lift
using mobile
PACKING Packing Packing Packing, Pack Station

238 Implementation Guide

 Reference Implementation for Outbound Processes

Table 16–27 Task Types

Productivity
Task Type Tasks Type Defined Type Resource Pools
MANIFEST Manifesting Manifesting Shipping, Manifest station
VAS Value Added Service VAS VAS Station, VAS
Trailer001 Manifesting Load Trailer Weighing, Weigh Station

[Link] Condition for Task Type Association

A condition set has lists of defined conditions. Each condition represents
related activities involved in fulfilling a demand. You can define
conditions based on various attributes of the shipment and a set of task
types associated with a condition.
Task types are associated with a set of resource pools that are required
to perform a particular task.
The estimated capacity for fulfilling a demand is evaluated from the SAM
definitions associated with a task type.
There are two sets of conditions for estimating the effort:
Q
VAS
Q
Non-VAS
Table 16–28 lists the condition sets for Task Type Association.

Table 16–28 Conditions for Task Type Association

Condition Set Condition Name Condition Value Associate Task type
VAS Identifying VAS Kit Code Is PK
requirement

Outbound 239
Reference Implementation for Outbound Processes

Table 16–28 Conditions for Task Type Association

Condition Set Condition Name Condition Value Associate Task type
Non-VAS Bulk Pick for ShipNode is DC1, ShipMode is PICK0001
PARCEL (Pack Parcel, and CASE or PALLET is
PACKING
Later) the UOM
MANIFESTING
Loose Pick for ShipNode is DC1, ShipMode is PICK0002
PARCEL (Pack Parcel, and EACH is the UOM
MANIFESTING
while Pick)
Bulk Pick for ShipNode is DC1, ShipMode is PICK0003
LTL/TL (Pack while LTL or TL, and CASE or PALLET
TRAILER001
Pick) is the UOM
Loose Pick for ShipNode is DC1, ShipMode is PICK0004
LTL/TL (Pack while LTL or TL, and EACH is the UOM
TRAILER‘001
Pick)

Note: The system evaluates conditions in accordance with

the condition set sequence defined. The conditions in the
first condition set are evaluated, and if any of the condi-
tions are satisfied, the system moves on to the next condi-
tion set and evaluates the conditions there. For each
condition that is satisfied, the system associates the rele-
vant task type to the resource pool.:

16.4.7 Prints
This section lists the different documents that are printed as part of the
Reference Implementation of the Sterling Warehouse Management
System.

[Link] Prints for the Mobile Application-Based Parcel Shipments

This section lists the documents printed for the Mobile Application-based
Parcel Shipments

240 Implementation Guide

 Reference Implementation for Outbound Processes

[Link].1 Full Case Pick

The documents printed for Full Case pick using the Mobile Application are
displayed in Table 16–29.

Table 16–29 Prints for Full Case Pick

Document Printed During
UCC 128 Shipping Label Packing
FedEx Carrier Label Manifesting
Pack Slip Packing

[Link].2 Less Than Case Pick

The documents printed for Less Than Case pick using the Mobile
Application are displayed in Table 16–30.

Table 16–30 Prints for Less Than Case Pick

Document Printed During
Cart Manifest Batch Sheet Wave release
UCC 128 Shipping Label Wave release
FedEx Carrier Label Manifesting
Pack Slip Packing

[Link] Prints for the Mobile Application-Based LTL/TL Shipments

The documents printed for the LTL/TL shipments are displayed in
Table 16–31.

Table 16–31 Prints for LTL/TL Shipments

Document Printed During
UCC 128 Shipping Label Packing
Bill of Lading Load confirmation
Pack Slip Packing

Outbound 241
Reference Implementation for Outbound Processes

[Link] Prints for Paper-Based Parcel Shipments

The documents for printed for paper-based Parcel Shipments are
displayed in Table 16–32.

Table 16–32 Prints for Paper-Based Parcel Shipments

Document Printed During
Batch Sheets Wave release
UCC 128 Shipping Label Packing--for user-defined containerization
Wave Release--for system-defined
containerization.
FedEx Carrier Label Manifesting
Pack Slip Packing

[Link] Prints for Paper-Based LTL/TL Shipments

The documents for printed for paper-based LTL/TL Shipments are
displayed in Table 16–33.

Table 16–33 Prints for Paper-Based LTL/TL Shipments

Document Printed at
Batch Sheets Wave release
UCC 128 Shipping Label Packing
FedEx Carrier Label Manifesting
Bill of Lading Load confirmation
Pack Slip Packing

242 Implementation Guide

 17
Replenishment

In a warehouse, as a product is removed from the Forward Pick Area, the

inventory in that location requires re-stocking. This process is called
Replenishment.
This chapter explains the Replenishment process and solution offered by
Sterling Warehouse Management System.

17.1 Replenishment Process

The Replenishment process provided by Sterling Warehouse Management
System is a single-step and demand-based only process. Dedicated
locations are used as replenishment locations.
The Replenishment process used by warehouses may be either Mobile
Application-based or paper-based.

17.1.1 The Mobile Application-Based Replenishment

Process
When replenishing using the Mobile Application:
1. Replenishment tasks are created and made available on the mobile
device.
2. The user logs in to the Mobile Application.
3. The system suggests available replenishment tasks to the user.
4. The system suggests the source location and the inventory.
5. The user picks the suggested inventory.
6. The system suggests the deposit location.

Replenishment 243
Replenishment Configurations

7. The user deposits the inventory and completes the tasks using the
Mobile Application.

17.1.2 Paper-Based Replenishment Process

When replenishing using paper:
1. Batch sheets are printed by the system, indicating moves.
2. The user completes the tasks specified, and notes exceptions, if any.
3. The Batch is confirmed on the console.

17.2 Replenishment Configurations

This section explains the various configurations that may be done for the
Replenishment process.

17.2.1 Replenishment Strategy

When the UOM is EACH, CASE, or PALLET, for replenishment, look in Bulk
Zones that track inventory.

17.2.2 Agents
The agent configured for the Replenishment processing is:
Move Request Purge
This agent deletes the move request from the system. This agent is run
every day. It deletes move requests that were created thirty days prior to
the current date.
For more information about this agent, see the Sterling Warehouse
Management System: Configuration Guide.

17.2.3 Services
The services provided for the Replenishment process are:
Q
Print Move Tickets
This service prints Move Tickets in a paper-based warehouse.

244 Implementation Guide

 Replenishment Configurations

Q
Generate Min Max Replenishment Move Request
This service creates replenishment tasks with normal priority when
the inventory falls below the minimum level. For paper-based
warehouses, it also prints Move Tickets.
This service is part of the Reference Implementation provided with
Sterling Warehouse Management System.
Q
Generate Top Off Replenishment Move Request
This service creates replenishment tasks with low priority when the
inventory falls below the maximum level. For paper-based
warehouses, it also prints Move Tickets.
This service is a part of the Reference Implementation provided with
Sterling Warehouse Management System.

[Link] Print Move Tickets

When a move request is released, the ON_SUCCESS event of the
RELEASE_MOVE_REQUEST transaction is raised, which invokes the
PrintMoveTickets service.
The PrintMoveTickets service then prints the replenishment Move Tickets
in a paper-based warehouse. These Move Tickets are used for performing
replenishment tasks.
To activate the PrintMoveTickets service:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Move Request
> Inventory.
5. Navigate to the Transaction repository.
6. Associate the ON_SUCCESS event of the RELEASE_MOVE_REQUEST
transaction with the action Print Move Tickets, which invokes the
PrintMoveTickets service.

Replenishment 245
Replenishment Configurations

Note: This service is already activated if you have

installed the factory defaults with the events turned on.

[Link] Generate Min Max Replenishment Move Request

When the inventory falls below the minimum level, the
LOCN_INV_MONITOR agent calls the YNW_GenerateMinMaxRplMR_91
service.
This service then creates replenishment tasks with normal priority. For
paper-based warehouses, it also prints Move Tickets.
This service is part of the Reference Implementation provided with
Sterling Warehouse Management System.

[Link] Generate Top Off Replenishment Move Request

When the inventory falls below the maximum level, the
LOCN_INV_MONITOR agent calls the YNW_GenerateTopOffRplMR_91
service.
This service then creates replenishment tasks with low priority. For
paper-based warehouses, it also prints Move Tickets.
This service is part of the Reference Implementation provided with
Sterling Warehouse Management System.

17.2.4 Prints
The PrintMoveTickets service has been provided, which prints the Move
Tickets.

17.2.5 Productivity
For all tasks associated with Replenishment, the productivity can be
determined, based on the Standard Allowable Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

246 Implementation Guide

 Managing the Replenishment Process on the Warehouse Floor

17.3 Managing the Replenishment Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform Replenishment. This section explains the UI flow for performing
Replenishment.

17.3.1 Performing Replenishment

The UI flow for performing replenishment depends on whether the
warehouse is paper-based or Mobile Application-based.

[Link] Using the Mobile Application

Follow these steps in the Replenishment process:
1. Log in to the Mobile Application.
2. From the menu, select the Replenishment menu option.
3. The system suggests the available tasks to the user.
4. Scan the source location, appropriate inventory, and quantity.
5. Scan the target location.
6. Click Deposit. The move task is completed.
7. If more tasks exists, the system suggests them to the user.
Otherwise, the message "No Open Tasks" is displayed.

[Link] Using Paper

Follow these steps in the replenishment process:
1. Users are provided putaway batch sheets which contain information
about the inventory to move.
2. Log in to the Application Console.
3. From the Application Console navigation bar, select Task > Confirm
Batch. The Batch Confirmation screen displays.
4. Enter the batch number and target location.
5. Click Confirm. The paper-based move is confirmed.

Replenishment 247
Reference Implementation for Replenishment

17.4 Reference Implementation for

Replenishment
This section explains the Reference Implementation provided by the
Sterling Warehouse Management System for Replenishment.

17.4.1 Location Monitoring Rules

Inventory levels are periodically checked through the inventory monitor.
The strategy used for inventory level-based Replenishment is based on:
Q
Minimum and Maximum-Level Triggers
Q
Top-Off Replenishment Triggers

[Link] Minimum and Maximum-Level Triggers

For minimum and maximum Replenishment of a zone, the inventory
monitor raises an event when the net inventory at a location falls below
the minimum level.
A request is then placed for retrieval. This request is based on the event
to replenish the location to the maximum level. That is, Replenishment
Quantity = Max Capacity – Net Inventory
When the Min-Max Replenishment event is raised, replenishment tasks
are created with normal priority.

[Link] Top-Off Replenishment Triggers

For Top-off Replenishment, the inventory monitor raises an event when
the net inventory at a location falls below the maximum level.
A request is then placed for retrieval. This request is based on the event
to replenish the location to the maximum level. That is, Replenishment
Quantity = Max Capacity – Net Inventory
When the Top-off Replenishment event is raised, replenishment tasks are
created with low priority.

248 Implementation Guide

 Reference Implementation for Replenishment

Note: It is recommended that Min-Max Replenishment is

run more often than Top-Off Replenishment. As part of the
Sterling Warehouse Management System Reference
Implementation, Min-Max Replenishment is run every four
hours while Top-Off Replenishment is run once every day.

17.4.2 Replenishment Task Types

The Replenishment task types provided are displayed in Table 17–1

Table 17–1 Replenishment Task Types

Task Type Description
REPL-0001 Paper-Based Replenishment Task type.
REPL-0002 Mobile Application-Based Replenishment Task Type

Replenishment 249
Reference Implementation for Replenishment

250 Implementation Guide

 18
Print Labels Manually

License Plate Labels and UPC Case Code Labels can be printed manually
upon user request.

18.1 Print License Plate Labels Manually

License Plate Labels can be printed manually upon user request. You can
print a License Plate Label from the Inbound Console.
To print a UPC Case Code Label manually:
1. Navigate to Inventory > Print Case/Pallet SKU Labels. The Print
Case/Pallet SKU Label search screen displays.

Figure 18–1 Print Case/Pallet SKU Label Screen

Print Labels Manually 251

Print License Plate Labels Manually

Table 18–1 Print Case/Pallet SKU Search Screen

Field Description
Node Indicates the node to which the item belongs.
Enterprise Select the Enterprise to which the item belongs.
Item ID Enter the identifier of the item.

You can also click to select the item identifier.

Unit of Measure Enter the unit of measure for the item.
Label Type Select the type of container for which the LPN labels
are printed.

2. Enter the appropriate search criteria and click Proceed. The Print
Case/Pallet SKU Label screen displays.

Figure 18–2 Print Case/Pallet SKU Label Screen

Table 18–2 Print Case/Pallet SKU Label, Item Information

Field Description
Node Indicates the node to which the item belongs.
Enterprise Indicates the Enterprise to which the item belongs.
Item ID Indicates the identifier of the item.
Item Description Indicates the description of the item.
Unit of Measure Indicates the unit of measure of the item.
Label Type Indicates the type of container.
The Label Type can be either Case or Pallet.

252 Implementation Guide

 Print UPC Case Code Labels Manually

Table 18–2 Print Case/Pallet SKU Label, Item Information

Field Description
Alternate UOM Indicates the alternate unit of measure of the item.
Quantity Indicates the quantity of items.
No of Labels Enter the number of labels to be printed.

3. In the Number of Labels field, enter the appropriate value.

4. Click Print. The Print pop-up window displays.
5. In the Print pop-up window,
a. From the Print Service Name drop-down list, select
YNW_PrintUPCCaseCodeLabel_91
b. From the Printer drop-down list, select the appropriate printer
c. In the No. of Copies text box, enter the number of copies to print
d. Click OK
You can also click the Start Again button in the Print Case/Pallet SKU
Label screen to print more shipment labels.

18.2 Print UPC Case Code Labels Manually

UPC Case Code Labels can be printed manually upon user request. You
can print a UPC Case Code Label from the Inventory Console.

To print a UPC Case Code Label manually:

1. Navigate to Inventory > Print Case/Pallet SKU Labels. The Print
Case/Pallet SKU Label search screen displays.

Print Labels Manually 253

Print UPC Case Code Labels Manually

Figure 18–3 Print Case/Pallet SKU Label Screen

Table 18–3 Print Case/Pallet SKU Search Screen

Field Description
Node Indicates the node to which the item belongs.
Enterprise Select the Enterprise to which the item belongs.
Item ID Enter the identifier of the item.

You can also click to select the item identifier.

Unit of Measure Enter the unit of measure for the item.
Label Type Select the type of container for which the LPN labels
are printed.

2. Enter the appropriate search criteria and click Proceed. The Print
Case/Pallet SKU Label screen displays.

254 Implementation Guide

 Print UPC Case Code Labels Manually

Figure 18–4 Print Case/Pallet SKU Label Screen

Table 18–4 Print Case/Pallet SKU Label, Item Information

Field Description
Node Indicates the node to which the item belongs.
Enterprise Indicates the Enterprise to which the item belongs.
Item ID Indicates the identifier of the item.
Item Description Indicates the description of the item.
Unit of Measure Indicates the unit of measure of the item.
Label Type Indicates the type of container.
The Label Type can be either Case or Pallet.
Alternate UOM Indicates the alternate unit of measure of the item.
Quantity Indicates the quantity of items.
No of Labels Enter the number of labels to be printed.

3. In the Number of Labels field, enter the appropriate value.

4. Click Print. The Print pop-up window displays.
5. In the Print pop-up window,
a. From the Print Service Name drop-down list, select
YNW_PrintUPCCaseCodeLabel_91.
b. From the Printer drop-down list, select the appropriate printer.
c. In the No. of Copies text box, enter the number of copies to print.
d. Click OK.
To print more shipment labels, click the Start Again button.

Print Labels Manually 255

Print UPC Case Code Labels Manually

256 Implementation Guide

 19
Value-Added Services

Value-Added Services (VAS) are performed to meet customer demands.

These can be activities performed on a product before the product is
delivered to the customer or a provided service that is performed at the
customer site.
VAS is performed in the warehouse on an ad hoc basis. The different
types of services include Kitting and Compliance Services.
This chapter explains the VAS process and solution offered by the
Sterling Warehouse Management System.

19.1 VAS Process

This section describes the two VAS Processes:
Q
Kitting Process
Q
Compliance Service Process

19.1.1 Kitting Process

Kitting is the assembling of components to form an item. The Kitting
process involves the retrieval of goods from regular inventory and the
movement of the goods into a VAS zone.
For this purpose, a Work Order is created with the service group Kitting.
The user specifies the item and quantity that has been requested. The
individual component items are also specified when creating the Work
Order.

Value-Added Services 257

VAS Process

[Link] Kitting Process in a Mobile Application-Based Warehouse

The user creates, allocates, and releases a Work Order for the service
item with the activity group Kitting. Once the Work Order is allocated and
released, Mobile Application-based Retrieval tasks are created. The
inventory is retrieved from the bulk storage area or from the loose
products area, based on the UOM required and moved to the appropriate
VAS zone.
The user then confirms the Work Order for the quantity created. Upon
confirmation, the system automatically consumes the inventory for the
components and creates inventory for the final item.
Putaway tasks are then automatically created and suggested in the
Mobile Application, to move the final inventory out of the VAS zone and
back into the stocking area.

[Link].1 VAS Execution Process

The process followed for Value-Added Services in a warehouse using the
Mobile Application is:
1. The user creates a Work Order for the service item with Kitting as the
service group.
2. The user allocates the Work Order and releases it.
3. The user, with the appropriate skill set, logs into the Task Controller.
4. The Retrieval task is presented to the user.
5. The location, LPN, or item and quantity combination to pick are
scanned.
6. The quantity is dropped off at the destination location suggested. LPN
tracking is disabled at this location.
7. The Work Order is confirmed at the VAS Station with appropriate
quantity against an activity.
8. The Work Order closes automatically when all quantity is confirmed.
9. Putaway tasks are automatically generated for the kit quantities.
The user uses the Mobile Application to complete the Putaway tasks.

258 Implementation Guide

 VAS Process

[Link] Kitting Process in a Paper-Based Warehouse

The user creates, allocates, and releases a Work Order for the service
item with activity group Kitting. Once the Work Order is allocated and
released, a Batch Sheet is created for retrieving inventory from the
storage area and moving it to the VAS zone. The inventory is retrieved
from the bulk storage area or from the loose products area, based on the
UOM required and moved to the appropriate VAS zone.
The user then confirms the Work Order for the quantity created. Upon
confirmation, the system automatically consumes the inventory for the
components and creates inventory for the final item.
Putaway tasks are then automatically created and Batch Sheets are
printed to move the final inventory out of the VAS zone and back into the
stocking area.

[Link].1 VAS Execution Process

The process followed for Value-Added Services in a warehouse using
paper is:
1. The user creates a Work Order for the service item with Kitting as the
service group.
2. The user allocates the Work Order and releases it.
3. The Batch Sheet is created for the moves.
4. The user completes the moves.
5. The user confirms the batch through the Confirm Batch action in the
console.
6. The Work Order is confirmed at the VAS Station, with appropriate
quantity against an activity.
7. The Work Order closes automatically when all quantity is confirmed.
8. Putaway tasks are automatically generated for the kit quantities.

19.1.2 Compliance Service Process

The compliance service is used in made-to-customer orders. Compliance
service is done to meet specific buyer requirements.

Value-Added Services 259

VAS Process

The Work Order is either automatically created while scheduling the

order containing the compliance service or manually created in the
Create Work Order console.

[Link] Compliance Service Process in a Mobile

Application-Based Warehouse
The user creates, allocates, and releases a Work Order for the service
item with activity group Inventory Compliance. Once the Work Order is
allocated and released, the Mobile Application-based Retrieval tasks are
created. The inventory is retrieved from the bulk storage area or from
the loose products area, based on the UOM required and moved to the
appropriate VAS zone.
The user then confirms the Work Order for the quantity created. Upon
confirmation, the system automatically consumes the inventory for the
components and creates inventory for the final item.
Putaway tasks are then automatically created and suggested in the
Mobile Application, to move the final inventory out of the VAS zone and
back into the stocking area.

[Link].1 VAS Execution Process

The process followed for Value-Added Services in a warehouse using the
Mobile Application is as follows:
1. The user creates a Work Order for the service item with Inventory
Compliance as the service group.
2. The user allocates the Work Order and releases it.
3. The user, with the appropriate skill set, logs into the Task Controller.
4. The Retrieval task is presented to the user.
5. The location, LPN, or item and quantity combination to pick are
scanned.
6. The quantity is dropped off at the destination location suggested. LPN
tracking is disabled at this location.
7. The Work Order is confirmed at the VAS Station with appropriate
quantity against an activity. The inventory attribute changes to the
appropriate segment type and segment number on confirming the
Work Order.

260 Implementation Guide

 VAS Process

8. The Work Order closes automatically when all quantity is confirmed.

9. Putaway tasks are automatically generated for the inventory on which
the compliance service has been performed.
The user uses the Mobile Application to complete the Putaway tasks.

[Link] Compliance Service Process in a Paper-Based

Warehouse
The user creates, allocates, and releases a Work Order for the service
item with activity group Inbound Compliance. Once the Work Order is
allocated and released, a Batch Sheet is created for retrieving inventory
from the storage area and moving it to the VAS zone. The inventory is
retrieved from the bulk storage area or from the loose products area,
based on the UOM required and moved to the appropriate VAS zone.
The user then confirms the Work Order for the quantity created. Upon
confirmation, the system automatically consumes the inventory for the
components and creates inventory for the final item.
Putaway tasks are then automatically created and Batch Sheets are
printed to move the final inventory out of the VAS zone and back into the
stocking area.

[Link].1 VAS Execution Process

The process followed for Value-Added Services in a warehouse using
paper is:
1. The user creates a Work Order for the service item with Inventory
Compliance as the service group.
2. The user allocates the Work Order and releases it.
3. The Batch Sheet is created for the moves.
4. The user completes the moves.
5. The user confirms the batch through the Confirm Batch action in the
console.
6. The Work Order is confirmed at the VAS Station with appropriate
quantity against an activity. The Inventory attribute changes to the
appropriate segment type and segment number on confirming the
Work Order.

Value-Added Services 261

VAS Configurations

7. Putaway tasks are automatically generated for the inventory on which

the compliance service has been performed.

19.2 VAS Configurations

This section explains the various configurations that may be done for the
VAS process.

19.2.1 VAS Pipeline

Figure 19–1 illustrates the VAS Pipeline.

Figure 19–1 VAS Pipeline

19.2.2 Activities
Activities in the warehouse are grouped into Activity Groups. The Sterling
Warehouse Management System provides a pre-defined set of activity
groups for a warehouse. Examples of activity groups include Receipt,
Inspection, Value Added Services, and Packing.
Each activity group is associated with activity codes that define each
activity that is performed. The VAS activity group has Kitting,
Inbound-Compliance, and Value Added Service.

262 Implementation Guide

 VAS Configurations

Note: Activity Codes may be defined only when the

Warehouse Management System tree is loaded for Node
and Hub combination.

19.2.3 Agents
No agent needs to be explicitly configured for the VAS Process.
The agents used for VAS processing are:
Q
Purge Work Order
This agent moves work orders that were created one month ago to
the history table. This agent is generally triggered once at the end of
each working day.
Q
Purge Work Order History
This agent purges the work order history that were created one
month ago. This agent is generally triggered once at the end of each
working day.
Q
Synchronize Task Queue
This agent represents the process of synching the order fulfillment
task queue. This agent is generally triggered once at the end of each
working day.
Q
Work Order Monitor
This agent monitors the work orders that have been created for VAS.
This agent is generally triggered once at the end of each working day,
depending upon the monitor rule.
For more information about these agents, see the Sterling Warehouse
Management System: Configuration Guide.

Value-Added Services 263

VAS Configurations

19.2.4 Service
The service provided for the VAS process is explained in this section.

[Link] Generate Putaway Request For Work Order

When the Work Order is completed, one of the following events of the
CONFIRM_WORK_ORDER transaction is raised:
Q
LPN_ACTIVITIES_COMPLETED: On completion of LPN activities
Q
SKU_ACTIVITIES_COMPLETED: On completion of SKU activities
Q
SNO_ACTIVITIES_COMPLETED: On completion of serial number
activities
The CONFIRM_WORK_ORDER transaction invokes the
YNW_GeneratePutawayRequestForWorkOrder_91 service.
The YNW_GeneratePutawayRequestForWorkOrder_91 service then
initiates the generation of the requests for putaway tasks.
You can also choose to putaway inventory from the VAS location only on
completion of all activities (that is, LPN activities, SKU activities, and
serial number activities). For this, activate the
ON_WORK_ORDER_COMPLETION event to raise the
CONFIRM_WORK_ORDER transaction, which invokes the
YNW_GeneratePutawayRequestForWorkOrder_91 service.
To activate the YNW_GeneratePutawayRequestForWorkOrder_91 service:
1. Navigate to the VAS process model.
2. Navigate to the transaction repository.
3. Associate the LPN_ACTIVITIES_COMPLETED,
SKU_ACTIVITIES_COMPLETED, SNO_ACTIVITIES_COMPLETED and
ON_WORK_ORDER_COMPLETION events with the action YNW Work
Order Putaway 91, which invokes the
YNW_GeneratePutawayRequestForWorkOrder_91 service.

Note: This service is already activated if you have

installed the factory defaults with the events turned on.

264 Implementation Guide

 Managing the VAS Process on the Warehouse Floor

19.2.5 Prints
The PrintMoveTickets service is provided, which prints the Move Tickets.

19.2.6 Productivity
For all tasks associated with VAS, the productivity can be determined,
based on the Standard Allowable Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

19.3 Managing the VAS Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform VAS. This section explains the UI flow for performing VAS.

19.3.1 Performing VAS

The UI flow for performing VAS includes creating work orders and
confirming work orders.

[Link] Creating a Work Order Manually

Follow these steps for creating a work order manually:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select VAS > Create
Work Order. The Create Work Order screen displays.
3. Enter the details required and click Proceed. The Create Work Order
screen displays.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.
4. Enter the appropriate components or activities and click Save.
The work order gets created.

Value-Added Services 265

Reference Implementation for VAS

[Link] Confirming a Work Order

Follow these steps for confirming a work order:
1. Log in to the Application Console.
2. From the Application Console navigation bar, select VAS > Work
Order Console. The Work Order search By Item screen displays.
3. Enter the criteria for searching the appropriate work order.
4. From the Work Order list screen, select the work order to confirm.
5. Click the Confirm action. The VAS Station screen displays.
6. Scan or enter the appropriate fields.
7. Click Confirm.
8. The work order gets confirmed.

19.4 Reference Implementation for VAS

This section explains the Reference Implementation provided by the
Sterling Warehouse Management System for VAS.

19.4.1 Item Configuration

A physical kit item (PK-000001) is provided as a part of the Reference
Implementation.
This kit item consists of two component items:

Table 19–1 Physical Kit Items

Component Items Kit Quantity
COMP-0001 1
COMP-0002 2

266 Implementation Guide

 Reference Implementation for VAS

19.4.2 Kitting Service Item Configuration

A service item is provided with these configurations for kitting services:

Table 19–2 Kitting Services

Service Item ID Service Activities
Kitting KITTING

19.4.3 Retrieval Strategy

The inventory is retrieved from the bulk storage area or from the loose
products area, based on the UOM required, and moved to the appropriate
VAS zone. This is based on the retrieval strategy.
The Retrieval strategies configured for VAS are:

Table 19–3 Retrieval Strategies

Description UOM Zones Task Type
Bulk Zones Retrieval CASE, PALLET BULK-ZONE1 VAS-RETR01 (Mobile
Application)
BULK-ZONE2
VAS-RETR02 (Paper)
BULK-ZONE3
Active Zone Retrieval EACH FORWARD-PICK VAS-RETR01 (Mobile
Application)
DYNAMIC-SLOT
VAS-RETR02 (Paper)

19.4.4 Putaway Strategy

For Work Orders that are related to a Sales Order, that is, for
build-to-order Work Orders, Putaway need not be done. In this case, the
Purpose of the Work Order, in the console, is displayed as Order. Once
the Work Order is confirmed, the supply of the kitted item increases.
When the wave is released, pick tasks are created to move the kitted
item to the Pack Station. The item then gets shipped out of the
warehouse.
For a build-to-stock Work Order, Putaway is suggested to the appropriate
storage areas. In this case, the Purpose of the Work Order, in the
console, is displayed as Stocked. On confirming such Work Orders,
Putaway tasks are generated to move the kitted item to appropriate
storage areas.

Value-Added Services 267

Reference Implementation for VAS

The Putaway strategies configured for VAS are:

Table 19–4 Putaway Strategies

Description UOM Zones Task Type
Putaway to Active Zone EACH FORWARD-PICK-ZONE1 VAS-PUT01 (Mobile
Application)
FORWARD-PICK-ZONE2
VAS-PUT02 (Paper)
Putaway to Bulk Zones CASE, PALLET BULK-ZONE1 VAS-PUT01 (Mobile
Application)
BULK-ZONE2
VAS-PUT02 (Paper)
BULK-ZONE3

19.4.5 Compliance Service Item Configuration

A service item is created with these configurations for compliance
services:

Table 19–5 Configuration Services

Service Item ID Service Activities
Special-Ticketing SPECIAL-TICKETING

19.4.6 Activity Constraints Configuration

Location priorities have been defined as a part of the Sterling Warehouse
Management System Reference Implementation.
The location priorities defined are displayed in Table 19–6.

Table 19–6 Location Priorities

Priority Location
10 V1-000001
20 V1-000002

268 Implementation Guide

 20
Returns

A return is the process of handling the return of products from a

customer to the distribution center (DC). Returns can be either created
against a Return Order or created without an Order reference. Return
Orders are created on the application console. Once a Return Order is
created and confirmed, a supervisor usually authorizes the return.
It is assumed that a returns receipt is always done using a paper-based
process. This also applies to warehouses following the Mobile
Application-based processes.

20.1 Returns Process

The Sterling Warehouse Management System supports paper based
receiving process for returns. This process is explained in the following
section.

20.1.1 Paper-Based Returns Process

When receiving returns with an Return Order, receipts are recorded
through the Record/Report Receipt action available in the Returns
Console.
The details of the receipt are entered and the receipt for the Return
Order is then marked Closed. The closure of the receipt automatically
triggers the generation of Putaway tasks.
In the Paper-based Returns process, it is assumed that receipts are done
in loose SKUs and not in LPNs.
The Returns process is:
1. The Receiving Worksheet is printed and given to the user.

Returns 269
Returns Process

2. The user records the receipt information on the worksheet.

3. The user selects the Report/Record Receipt action in the application
console and records the receipt on the system.
4. The user closes the receipt manually using the Close Receipt action.
5. The Putaway tasks are generated on closing the receipt.

270 Implementation Guide

 Returns Configurations

20.2 Returns Configurations

This section explains the various configurations that may be done for the
Returns process.

20.2.1 Returns Pipeline

Figure 20–1 illustrates the Returns Pipeline.

Figure 20–1 Returns Pipeline

20.2.2 Setting Up the Receiving Preferences for Returns

This section explains how to set up the Receiving Preferences for
Returns.

Returns 271
Returns Configurations

[Link] Enterprise-Level Configurations

To set up the Enterprise-level Receiving Preferences:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Reverse Logistics.
4. From the tree in the application rules side panel, select Receipt >
Receiving Preferences. The Receiving Preferences screen displays.
5. In the Search Results panel, click . The Receiving Preference
Details pop-up screen displays.
6. Enter information into the applicable fields.`
For more information and field value descriptions, see the Sterling
Supply Collaboration: Configuration Guide.
7. Click .

[Link] Node-Level Configurations

To set up the Node-level Receiving Preferences:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receipt >
Document Specific > Return Order > Receiving Preferences.
5. The Receiving Preferences: Return Order screen displays.
6. In the top panel, select the appropriate options for building pallets,
building cases, Disposition Code for receiving with QC, Disposition
Code for receiving without QC, and preference for closing receipt by
an agent.

272 Implementation Guide

 Returns Configurations

For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. The lower panel displays the Enterprise-Level Receiving Preferences
that you have set up.
8. Click .

Note: Click to view the Receiving Preferences Details

screen that displays the detailed preferences set for
receiving the item, along with the QC percentage set for
the item.

20.2.3 Setting Up the Putaway Preferences for Returns

To set up the Putaway Preferences for Returns:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Putaway Preferences. The Putaway Preferences screen is displayed.
Use this to set the Putaway Preferences for a single-SKU, multi-SKU
container, and container with unknown contents.
5. Alternatively, click in the Activity Search screen to access the
Putaway Preferences screen.
6. In the Putaway Preferences screen, select the appropriate tab,
depending on whether you are setting up Putaway Preferences for a
Single SKU, Multi-SKU Container, or Container with unknown
contents.
7. Click . The Putaway Preference Details screen displays.
8. In the Activity Code drop-down list, select the code to move the
products to storage.

Returns 273
Returns Configurations

9. Enter information into the other applicable fields. For more

information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
10. Click .
11. To configure task types for putaway, click . The Putaway Strategy
screen displays. Configure the task types.
For more information about setting up putaway strategies, see the
Sterling Warehouse Management System: Configuration Guide.

20.2.4 Setting Up the Receiving Disposition Codes for

Returns
This section explains how to create Disposition Codes. It also explains
how to associate the Disposition Code with a Product Class, with
Disposition Transition Statuses, for receiving with QC, and with an
Inventory Status.

[Link] Creating the Receiving Disposition

This section explains how to create the Receiving Disposition.
Disposition Codes can be created to be assigned to the inventory at
different stages, such as receiving, during QC, and after QC. You can
have different Disposition Codes, depending upon whether the products
passed QC, failed QC, and so forth.
To create the Disposition Code to assign to items in QC:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new screen.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Return Order > Receiving Disposition. The
Disposition List: Return Order screen is displayed.
5. In the Disposition List: Return Order screen, click . The
Disposition Details pop-up screen displays.

274 Implementation Guide

 Returns Configurations

6. Enter information into the other applicable fields. For more

information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
7. Click .
A receiving disposition is created that can be associated to the inventory
while receiving returns.

[Link] Associating the Disposition Code with a Product Class

To associate the Disposition Code with a Product Class:
1. Log into the application as the Enterprise user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new screen.
3. From the Applications Manager menu bar, select Application >
Reverse Logistics.
4. From the tree in the application rules side panel, select Document
Specific > Receipt > Receiving Disposition. The Disposition List:
Return Order screen displays.
5. In the Disposition List: Return Order screen, click . The
Disposition Details pop-up screen displays.
6. In the Product Class drop-down list, select the appropriate Product
Class for the Disposition Code.
7. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
8. Click .
The selected Disposition Code is now associated with the specified
Product Class. Whenever a product is dispositioned to the selected
Disposition Code, the Product Class automatically changes to the Product
Class that you specified here.

Returns 275
Returns Configurations

[Link] Associating the Disposition Code with Disposition

Transition statuses
To associate the Disposition Code with disposition transition statuses:
1. Follow Step 1 to Step 5 in Section [Link], "Associating the
Disposition Code with a Product Class".
2. In the Receiving Disposition drop-down list of the Disposition
Transitions pane, select the appropriate Inventory Statuses.
3. Click .
The selected Disposition Code is now associated with the specified
disposition transition statuses. The products being dispositioned to this
Disposition Code are assigned these Inventory Statuses consecutively,
until it reaches the final disposition.

[Link] Associating a Disposition Code for Receipt with QC

To associate a Disposition Code for receiving with QC:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Return Order > Receiving Preferences.
5. The Receiving Preferences: Return Order screen displays.
6. In the Disposition Code for Receipt with QC, enter the appropriate
Disposition Code. During receiving, this Disposition Code is assigned
to all items that require QC.
7. Enter information into the other applicable fields. For more
information and field value descriptions, see the Sterling Warehouse
Management System: Configuration Guide.
8. Click .

276 Implementation Guide

 Returns Configurations

Note: Click to view the Receiving Preferences Details

screen that displays the detailed preferences set for
receiving the item, along with the QC percentage set for
the item.

[Link] Associating the Disposition Code with an Inventory

Status
The Disposition Codes allow inspectors to utilize their own terminology,
instead of understanding inventory and storage implications.
Inventory is received with the specified Product Class and Inventory
Status of the Disposition Code entered.
If the Product Class is not specified, the Product Class from the Return
Order or the default Product Class from the item is used. It is mandatory
to have the Product Class specified at one of these levels.
To associate the Disposition Code with an Inventory Status:
1. Log into the application as the Node user.
2. From the Application Console menu bar, select Configuration >
Launch Applications Manager. The Applications Manager opens in a
new window.
3. From the Applications Manager menu bar, select Application >
Warehouse Management.
4. From the tree in the application rules side panel, select Receiving >
Document Specific > Return Order > Disposition Codes.
5. The Receiving Disposition: Return Order screen is displayed.
6. From the Inventory Status drop-down list, select the Inventory Status
to associate with the Disposition Code.
For more information and field value descriptions, see the Sterling
Warehouse Management System: Configuration Guide.
7. Click .

Returns 277
Returns Configurations

20.2.5 Inventory Status Transitions

Inventory should be considered available or unavailable for certain
operations. For example, inventory should be unavailable for orders until
putaway is complete. As soon as putaway is complete, the inventory
should become available for orders automatically, without any
intervention from users.
To facilitate this, Inventory Statuses are assigned to inventory. The
Inventory Status of the inventory changes at different stages.
During returns, when inventory is received, it is assigned an appropriate
Inventory Status to show that the inventory is awaiting inspection. When
the inventory is moved to storage, the Inventory Status may change
appropriately.
Inventory Statuses can be associated with zones. In this case, whenever
a product moves into a particular zone, its Inventory Status gets
transitioned to the Inventory Status that the zone is associated with. So,
whenever a product is moved into the QC zone, its Inventory Status
changes to the Inventory Status associated with the QC zone, which may
indicate that the product is undergoing QC. When the product moves out
of the QC zone into storage, its Inventory Status changes to the
Inventory Status associated with the storage zone, which may indicate
that the product is available for orders. In case of products that fail QC,
they may be moved to the appropriate zone that is associated with an
Inventory Status to mark the products as damaged and thus unavailable,
or quarantined, or held until more QC is done on a larger sample.
If a product with the Inventory Status indicating that the product is
awaiting inspection is moved directly into storage, it retains its Inventory
Status. This is because no transition has been defined for the Inventory
Status of the storage zone, when a product with that Inventory Status
moves into storage. If the warehouse process so dictates, this can be
overwritten by setting an appropriate Inventory Status transition. In that
case, products putaway into the storage zone may become directly
available for orders, even though they have not cleared QC as yet.

278 Implementation Guide

 Returns Configurations

20.2.6 Agents
The agents configured for the Returns processing are:
Q
Purge Receipt
This agent purges completed receipts. This agent is generally
triggered once in ten days or based on the receipt volume.
Q
Receipt Complete
This agent completes the receipts. This agent is generally triggered
once at the end of each working day.
For more information about these agents, see the Sterling Warehouse
Management System: Configuration Guide.

20.2.7 Services
The services provided for the Returns process are:
Q
GeneratePutawayRequest Service
This service generates the requests for putaway tasks once receipt is
completed.
Q
Register Activity Demand For QC Service
This service computes the QC quantity (quantity of the products
received that needs to be diverted to the QC Zone for QC) and
creates an activity demand for it.
Q
Register Activity Demand and Print Receiving Worksheet
This service computes the QC quantity and prints it on the Receiving
Worksheet. It also creates an activity demand for the QC quantity.

Note: These services are already activated if you have

installed the factory defaults with the events turned on.

[Link] GeneratePutawayRequest Service

When a receipt is completed, the ON_RECEIPT_COMPLETE event of the
RECEIPT_COMPLETE transaction is raised, which invokes the
GeneratePutawayRequest service.

Returns 279
Returns Configurations

The GeneratePutawayRequest service then initiates the generation of the

requests for putaway tasks.
To activate the GeneratePutawayRequest service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_RECEIPT_COMPLETE event with the action Putaway
products on receipt, which invokes the GeneratePutawayRequest
service.

[Link] Register Activity Demand For QC Service

When a receipt is started, the ON_START_RECEIPT event of the
START_RECEIPT transaction is raised. This invokes the
YNW_RegisterActivityDemandForQC_91 service.
The YNW_RegisterActivityDemandForQC_91 service initiates the
computation of the quantity of product that needs to be diverted for an
order, based on the QC classification and QC percentage setup. It then
creates an activity demand for the same. During Putaway this quantity of
the product is diverted to the QC Zone for QC.
To activate the YNW_RegisterActivityDemandForQC_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the Transaction repository.
3. Associate the ON_START_RECEIPT event with the action Register
Activity Demand For QC, which invokes the
YNW_RegisterActivityDemandForQC_91 service.

[Link] Register Activity Demand and Print Receiving Worksheet

YNW_CompositeServiceOnStartReceipt_91 Service
When a receipt is started, the ON_START_RECEIPT event of the
START_RECEIPT transaction is raised, which invokes the
YNW_CompositeServiceOnStartReceipt_91 service.
The YNW_CompositeServiceOnStartReceipt_91 service initiates the
computation of the quantity of product that needs to be diverted for an
order, based on the QC classification and QC percentage setup. It then

280 Implementation Guide

 Managing the Returns Process on the Warehouse Floor

creates an activity demand for the same. The QC percentage computed is

then printed on the Receiving Worksheet.
To activate the YNW_CompositeServiceOnStartReceipt_91 service:
1. Navigate to the Purchase Order Receipt Repository.
2. Navigate to the transaction repository.
3. Associate the ON_START_RECEIPT event with the action YNW CalcQC
And Print Recv WS (91), which invokes the
YNW_CompositeServiceOnStartReceipt_91 service.

20.2.8 Prints
The YNW_PrintReceivingWorkSheet_91 service is provided, which prints
the Receiving Worksheet.

20.2.9 Productivity
For all tasks, such as, Pre-Receiving, Receiving, and Putaway associated
with Returns, the productivity can be determined, based on the Standard
Allowable Minutes (SAM).
For more information about Productivity, see Chapter 7, "Productivity and
Task Types".

20.3 Managing the Returns Process on the

Warehouse Floor
You can use the Application Console and the Mobile Application to
perform Returns. This section explains the UI flow for performing
Returns.

20.3.1 Performing Returns

The UI flow for creating and authorizing returns is explained in this
section.

[Link] Creating and Authorizing Returns Process

Follow these steps for creating and authorizing returns:
1. Log into the Application Console.

Returns 281
Reference Implementation for Returns

2. From the Application Console navigation bar, select Reverse Logistics

> Create Return Order. The Return Entry screen displays.
3. Enter the appropriate information and click Create Return. The Return
Detail screen displays.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.
4. Enter appropriate information and Click Save to save the details
entered.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.
5. Click the Confirm action to confirm the return order.
6. Click the Authorize action to authorize the return order. The Authorize
Return screen displays.
7. In the Authorization Details Pane > Authorize Drop Status field, select
Authorized.
For more information about the field descriptions, see the Sterling
Warehouse Management System: User Guide.
8. Click Save. The return order gets authorized.

20.4 Reference Implementation for Returns

This section explains the Reference Implementation provided by Sterling
Warehouse Management System for Returns.

20.4.1 Inbound Rules Configuration for Returns

This section describes the inbound rules configured in Sterling Warehouse
Management System.

[Link] Putaway Preferences

Once shipments are received, they are configured to automatically
generate tasks for putaway. The service to generate a putaway request is
configured as a part of the receipt transaction, on closure of the receipt.
Tasks are configured as one-step tasks. For all the task types, the
Execute through Drop off Flag is set to “N”. Warehouses may manually

282 Implementation Guide

 Reference Implementation for Returns

stage products in staging locations due to equipment constraints in the

destination aisle.
The considerations for putaway include:
Q
Location capacity.
Q
Putaway sequence.
Q
Consolidation opportunity along with locations that have the same
item, otherwise the items are placed in an empty location.
Q
Enterprise or other constraints.
Q
Location and item storage preferences based on Item Classification
(For example, Storage Type is Refrigerated).
Q
Zone–Task type preference.
Q
Receiving preference for QC based on Enterprise, Vendor and Item
Classification (For example, Product Line is PL001).
The Sterling Warehouse Management System configurations for Putaway
Preferences include:

Table 20–1 Putaway Preferences

Activity UOM Zones
Moving To Storage Less than Case FORWARD PICK
ZONES
Moving To Storage CASE BULK ZONES Tracking
Cases
Moving To Storage PALLET BULK ZONES Tracking
Pallets

[Link].1 Putaway Task Types

Returns 283
Reference Implementation for Returns

The Putaway strategy created makes use of task types to execute the
Putaway process.
The task types created to execute the Putaway process in the warehouse
are:

Table 20–2 Putaway Task Types

Task Type Description
MOVE-0001 Paper-based Move Request
MOVE-0002 Mobile Application-based Move Request

[Link].2 Putaway Strategy

For paper-based warehouses, the Task Type MOVE-0001 is used. For
warehouses using the Mobile Application to execute the Putaway tasks,
the Putaway strategy is configured to use the MOVE-0002 Task Type.

[Link] Node Receiving Preferences

Warehouses can receive cases, pallets, or both. Most warehouses follow
the process of not verifying the content of cases.
The Node Receiving Preferences provided are:

Table 20–3 Receiving Preferences

Case/Pallet Receiving Preference
Case Do not Verify Contents
Pallet Verify Contents

[Link] Receiving Disposition Setup

Once the inventory is received into the warehouse, it can be transitional
to the appropriate Product Class and Inventory Status based on the
Disposition Code. The user determines the disposition of the item and the
quantity. The disposition indicates whether the inventory is saleable,
requires further detailed quality checks, or should be scraped. These are
translated into the appropriate Product Class and Inventory Status.

284 Implementation Guide

 Reference Implementation for Returns

The standard Disposition Configurations provided are:

Table 20–4 Disposition Configurations

Product Inventory Final
Sl. No. Disposition Code Class Status Disposition
1 GOOD N (Good) Y
2 DAMAGED FD N (Good) Y
3 REQ-INSP AI (Awaiting N
Inspection)
3a QC-FAILED FD N (Good) Y
3b QC-PASSED N (Good) Y

Here, QC-FAILED and QC-PASSED are the disposition transitions for the
Disposition Code REQ-INSP.

Returns 285
Reference Implementation for Returns

286 Implementation Guide

 21
Dynamic Item Velocity Calculation

The velocity code of a product is a measure of its movement in the

supply chain. Products are classified as having a velocity code A, B, or C.
Velocity code A indicates fast moving items and C indicates slow moving
items. The speed at which an item moves varies by regions, seasons,
and other parameters. For example, during winter, snow jackets can sell
more on the east coast of the US than on the west coast.
Presently, warehouses manually change the velocity codes for items
based on seasonality, recent past, or forecast for the near future.
Dynamic Item Velocity Calculation enables the system to update the
velocity codes for items automatically, without much manual
intervention.
The fast moving items are typically stored in active locations in a
warehouse to reduce the picking cost and time and improve the picking
efficiency. Therefore, warehouses would prefer to slot active areas based
on seasonal data.

Note: Dynamic Item Velocity Calculation and Slotting are

performed for zones where picking or putaway tasks are
not executed.

21.1 Determining the Velocity Code

Warehouse managers and inventory supervisors use the Dynamic Item
Velocity Calculation feature of Sterling Warehouse Management System
to intelligently determine the velocity codes of items.
Sterling Warehouse Management System arrives at the velocity codes for
items using the following:

Dynamic Item Velocity Calculation 287

Determining the Velocity Code

Q
Historical Data-Analysis of Prior Outbound Shipments
Dynamic Item Velocity Calculation involves the analysis of outbound
shipments. Historical data such as the number of outbound
shipments, number of outbound shipment lines, number of units,
number of cases, and number of pallets shipped for an item, for a
specific period of time, is used to determine how fast an item has
moved for that period of time.

Note: Set the value of the [Link]

property as [Link] in
customer_overrides.properties file to decide on the
criteria to determine the dynamic velocity. The value of the
[Link] property can be
set to NoOfUnits, NoOfShipmentLines, NoOfShipments,
NoOfPallets, or NoOfCases.
For example, if you want to predict the velocity for items
based on the number of shipments shipped in a specific
period of time, set
[Link]=
NoOfShipmentLines in the
customer_overrides.properties file.
The default value of the
[Link] property is
NoOfUnits.

Q
Forecast Data
The velocity codes of the items can also be determined based on the
number of orders or shipments predicted for the current season.
Sterling Warehouse Management System enables you to load the
forecasted data using the Item Statistics Data Loader service. For
more information about the Item Statistics Data Loader service, see
Section [Link], "Item Statistics Data Loader".
Q
Suggesting Cutoff Percentages
Based on historical or forecast data, the velocity codes of the items
can be determined based on the percentage share of each item that
is part of the total number of units of items shipped. The items are
arranged in descending order of their percentage share and a

288 Implementation Guide

 Dynamic Item Velocity Calculation Configurations

cumulative percentage share of each item is calculated. The pattern

of cumulative item percentages is observed and a cutoff percentage
is suggested based on this data. Each cutoff percentage corresponds
to a velocity code for the items. The items are grouped as fast-,
medium-, or slow-moving items based on the cutoff percentage range
in which their cumulative percentage falls.
The warehouse manager or inventory supervisor can override the
suggested cutoff percentages and accordingly update the item
velocity codes. For more information about overriding the cutoff
percentages, seeStep 2 of Section 21.3.4, "Updating Item Velocity
Code".
Q
Slotting
The Sterling Warehouse Management System provides the ability to
integrate with external slotting engines to re-slot active areas based
on the velocity codes of the items taking the historical data into
consideration.

21.2 Dynamic Item Velocity Calculation

Configurations
This section explains the various default configurations provided for the
Dynamic Item Velocity Calculation feature.

21.2.1 Agents
The agent configured for dynamic item velocity calculation is the
Dynamic Velocity Calculator agent.

Note: Because this agent modifies data that is generally

cached, it is advisable to run this agent after disabling
cache for the YFS_ITEM_NODE_DEFN table. For more
information about disabling cache for a specific table, see
the Sterling Selling and Fulfillment Foundation:
Performance Management Guide.

This agent is triggered from the Application Console. It takes the criteria
specified in the Application Console and translates it into actual dates
understood by the database. It gets the data regarding the number of

Dynamic Item Velocity Calculation 289

Dynamic Item Velocity Calculation Configurations

shipments, number of shipment lines, number of units, number of

pallets, and number of cases of items shipped in the specified date
range, computes the velocity codes for items, and updates the velocity
codes.

Note: If slotting is integrated with Dynamic Item Velocity

Calculation, a message to perform slotting along with
Dynamic Item Velocity Calculation is placed in the JMS
queue. This message is picked up by the Dynamic Velocity
Calculator agent to perform both Dynamic Item Velocity
Calculation and slotting.

Attributes
Table 21–1 lists the attributes for this agent.

Table 21–1 Dynamic Velocity Calculator Agent Attributes

Attribute Value
Transaction Name Dynamic Velocity Calculator
Transaction ID DYNAMIC_VELOCITY_CALC
Base Process Type None
Base Document Type None
Abstract Transaction None
APIs Called modifyItemNodeDefn
performSlotting, if you have integrated with slotting
engines.
User Exits Called None

Criteria Parameters
Table 21–2 lists the criteria parameters for this agent.

290 Implementation Guide

 Dynamic Item Velocity Calculation Configurations

Table 21–2 Dynamic Velocity Calculator Agent Criteria Parameters

Parameter Description
Action Required. Triggers the transaction. If this parameter is
left blank, it defaults to Get, the only valid value.
ShipNodeKey The warehouse management ship node for which
velocities are updated. This field is mandatory.
AgentCriteriaGroup The agent criteria group associated with the
warehouse management ship node for which velocities
are updated.
GetPendingJobs If this parameter is set to 'N', the agent does not
collect information on the pending jobs for this
monitor. The pending job information is used for
monitoring the monitor in the Sterling Warehouse
Management System.

Note: To determine the agent criteria for considering the

appropriate JMS Queue, the Enqueue Dynamic Velocity
Code Calc Agent Message service performs the following
steps:
Q
It looks into the agent criteria set for the node. The
node is specified by the ShipNodeKey parameter.
Q
If not found, it looks into the agent criteria that belongs
to the agent criteria group for that node. The agent
criteria group for the node is specified by the
AgentCriteriaGroup parameter.
Q
If none of the above is found, it considers the default
agent criteria for the node.
For more information about the Enqueue Dynamic Velocity
Code Calc Agent Message service, see Section [Link],
"Enqueue Dynamic Velocity Code Calc Agent Message".

Events Raised
Table 21–3 lists the events raised by this agent.

Dynamic Item Velocity Calculation 291

Dynamic Item Velocity Calculation Configurations

Table 21–3 Events Raised by the Dynamic Velocity Calculator Agent

Template
Event ID Key Data Data Published Support?
AGENT_START None None None
AGENT_COMPLETION None None None

Note: The default message queue provided for this agent

is DEFAULTAGENTQUEUE. You can also associate your own
message queue with the agent.

21.2.2 Events
The events provided for the Dynamic Velocity Calculator agent are:

[Link] Agent Start

This event is raised when the user submits a request to update the
velocity codes from the Application Console. This event raises an alert in
the open status, along with the time period criteria entered in the
Application Console. The alert is routed to the DEFAULT queue.

[Link] Agent Completion

This event is raised when the Dynamic Velocity Calculator agent
completes the process of updating the item velocity codes for all items
that qualify the time periodcriteria. This service closes the open alert
raised by the Agent Start event.

21.2.3 Services
The services provided for the Dynamic Item Velocity Calculation process
are:
Get Shipment Item Statistics
This service submits a request to update the item statistics for each
shipment and places a message regarding the shipment in the JMS
queue.

292 Implementation Guide

 Dynamic Item Velocity Calculation Configurations

Update Item Statistics

This service completes the request for updating the item statistics for a
shipment. When there is a message in the JMS queue, this service picks
up the message from the queue, gets statistics of items present in the
shipment, and updates the item statistics in the YFS_ITEM_STATISTICS
table.
Enqueue Dynamic Velocity Code Calc Agent Message
This service is invoked from the Application Console. It takes the XML
input from the UI and translates it into a suitable format using the XSL
translator and the processAgentMessage API. This service then places a
message in the JMS queue to be picked up by the Dynamic Velocity
Calculator agent.
Item Statistics Data Loader
This service is used to load item statistics from external systems. It
converts a data text file into XML format and calls the
manageItemStatistics API to load data into the system.
YNW_RaiseAlertForItemVelocityCodeAgentStart_91
This service raises an alert when a request to change the item velocity
codes is submitted from the Application Console. This service is invoked
by the Agent Start event.
YNW_ResolveAlertForItemVelocityCodeAgent_91
This service resolves the open alert raised by the
YNW_RaiseAlertForItemVelocityCodeAgentStart_91 service when the
Dynamic Velocity Calculator agent completes the process of updating
new velocity codes for the items.

[Link] Get Shipment Item Statistics

When a shipment enters the shipped status, the ON_SUCCESS event of
the Confirm Shipment or Close Shipment transaction invokes the Get
Shipment Item Statistics service. This service then places a message into
the JMS queue. This message contains details regarding the shipment.

Dynamic Item Velocity Calculation 293

Dynamic Item Velocity Calculation Configurations

Note: Ensure that you configure an action that invokes

the Get Shipment Item Statistics service. Associate the
action with the ON_SUCCESS event of the Confirm
Shipment transaction. Also ensure that Confirm Shipment
ON_SUCCESS event template has the EnterpriseCode
attribute. This attribute is required to determine the colony
in a multischema environment.
For more information about configuring an action, see the
Sterling Selling and Fulfillment Foundation: Application
Platform Configuration Guide.

To activate the Get Shipment Item Statistics service:

1. Navigate to the Outbound Shipment repository.
2. Navigate to the Transaction repository.
3. Associate the ON_SUCCESS event of the Confirm Shipment
transaction with the action that you created for Dynamic Item
Velocity Calculation. This invokes the Get Shipment Item Statistics
service.

Note: Ensure that you configure a separate JMS queue

and associate the Get Shipment Item Statistics service
with that message queue to enable the service to put
messages in that message queue.
The default message queue provided is
DEFAULTAGENTQUEUE.

[Link] Update Item Statistics

When there is a message in the JMS queue, the Update Item Statistics
service is invoked. This service:
1. Picks the message from the message queue.
2. Calls the getShipmentItemStatistics API to get the statistics of the
items belonging to the shipment that is shipped.
3. Calls the incrementItemStatistics API to update the statistics of the
items in the YFS_ITEM_STATISTICS table.

294 Implementation Guide

 Dynamic Item Velocity Calculation Configurations

To invoke the Update Item Statistics service, launch the Integration

Server.

Note: Ensure that you configure a separate JMS queue

and associate the Update Item Statistics service with that
message queue.
The default message queue provided is
DEFAULTAGENTQUEUE.

[Link] Enqueue Dynamic Velocity Code Calc Agent Message

The Enqueue Dynamic Velocity Code Calc Agent Message service is
invoked from the Application Console when updating the item velocity
code. This service:
1. Takes the data from the UI in XML format.
2. Translates the XML data into an appropriate format for the message
queue.
3. Places the data in the message queue.

Note: Ensure that you configure a separate JMS queue

and associate the Enqueue Dynamic Velocity Code Calc
Agent Message service with that message queue.
The default message queue provided is
DEFAULTAGENTQUEUE.

[Link] Item Statistics Data Loader

The Item Statistics Data Loader service is a data loading service. It is
used to get information about item statistics from an external system.
This service:
1. Converts a text file containing item statistics from an external system
into an XML file.
2. Passes the XML data as the input to the manageItemStatistics API,
which updates the item statistics records.
To invoke the Item Statistics Data Loader, launch the Integration Server.

Dynamic Item Velocity Calculation 295

Dynamic Item Velocity Calculation Configurations

Table 21–4 provides information about the details contained in the text
file used as input by the Item Statistics Data Loader service.

Table 21–4 Text File Format

Field Description Field Number
ITEMSTATISTICSHEDR The record identifier. 1
ItemId The item identifier. 2
Uom The Unit Of Measure of the 3
item.
ProductClass Product Class of the item. 4
EnterpriseCode The enterprise identifier. 5
ShipNodeKey The node identifier. 6
IsForcastedData Indicates that the statistics 7
are based on forecasted
data.
ShipYear The year of shipping. 8
ShipMonth The month of shipping. 9
ShipDate The day of shipping. 10
NoOfUnits Total number of units of 11
the item.
NoOfLooseUnits Number of loose units of 12
the item.
NoOfCases Number of case units of 13
the item.
NoOfPallets Number of pallet units of 14
the item.
NoOfShipmentLines Number of shipment lines 15
containing the item.
NoOfShipments Number of shipments 16
containing the item.
EstimatedNoOfLooseTa Estimated number of tasks 17
sks for the item from the
forward pick area.

296 Implementation Guide

 Dynamic Item Velocity Calculation Configurations

It is mandatory to provide values for the ItemId, Uom, EnterpriseCode,

ShipNodeKey, ShipYear, ProductClass, and ShipMonth parameters. The
default values for the non-mandatory parameters, IsForecastedData,
NoOfUnits, NoOfLooseUnits, NoOfCases, NoOfPallets,
NoOfShipmentLines, NoOfShipments, and EstimatedNoOfLooseTasks are
N, 0, 0, 0, 0, 0, 0, and 0. The value of ShipDate is defaulted to the first
day of the provided ship month.

[Link] YNW_RaiseAlertForItemVelocityCodeAgentStart_91
When the Dynamic Velocity Calculator agent starts, the Agent Start event
of the agent invokes the
YNW_RaiseAlertForItemVelocityCodeAgentStart_91 service. The service
then raises an open alert that stores the passed criteria.
To activate the YNW_RaiseAlertForItemVelocityCodeAgentStart_91
service:
1. Navigate to the General repository.
2. Navigate to the General Process Types.
3. Navigate to the Transaction repository.
4. Associate the Agent Start event of the Dynamic Velocity Calculator
agent with the Raise Agent Start Alert action which invokes the
YNW_RaiseAlertForItemVelocityCodeAgentStart_91 service.

Note: This service is already activated if you have

installed the factory defaults with events turned on.

[Link] YNW_ResolveAlertForItemVelocityCodeAgent_91
When the Dynamic Velocity Calculator agent completes the process of
updating the item velocity codes for the items, the Agent Completion
event of the agent invokes the
YNW_ResolveAlertForItemVelocityCodeAgent_91 service. This service
then resolves the open alert raised by the
YNW_RaiseAlertForItemVelocityCodeAgentStart_91 service when the
Dynamic Velocity Calculator agent started.
To activate the YNW_ResolveAlertForItemVelocityCodeAgent_91:
1. Navigate to the General repository.

Dynamic Item Velocity Calculation 297

Calculating Dynamic Item Velocity

2. Navigate to the General Process Types.

3. Navigate to the Transaction repository.
4. Associate the Agent Completion event of the Dynamic Velocity
Calculator agent with the Resolve Agent Alert action, which invokes
the YNW_ResolveAlertForItemVelocityCodeAgentStart_91 service.

21.2.4 Mining Item Statistics for Pre-Existing Shipments

A tool has been provided to mine the item statistics in the
YFS_ITEM_STATISTICS table for all pre-existing shipments. To mine item
statistics for the pre-existing shipments:
1. Set or export the YFS_HOME environment variable to the
<INSTALL_DIR> directory.
2. Ensure that the [Link] file is present in
the <INSTALL_DIR>/bin directory.
3. From the <INSTALL_DIR>/bin directory, run the following ANT
command:
sci_ant.cmd -f [Link]

Note: This command takes a long time to execute if the

number of shipments to be mined is large.

21.3 Calculating Dynamic Item Velocity

This section explains how to calculate dynamic velocity for items.

21.3.1 Setting the Time Period for Dynamic Item Velocity

Calculation
You can use Sterling Warehouse Management System to perform
Dynamic Item Velocity Calculation. This section explains how to set the
time period that is used to calculate dynamic velocity.
To set the time period:
1. Log in to the Application Console as a warehouse manager or an
inventory supervisor.

298 Implementation Guide

 Calculating Dynamic Item Velocity

2. From the Application Console menu, select Inventory > Recalculate

Item Velocity Code. The Recalculate Item Velocity Code screen
displays. For field value descriptions, see Table 21–5 and Table 21–6.
3. In theSelect Time Period panel, select the time period to perform the
analysis.

Table 21–5 Recalculate Item Velocity Code, Select Time Period

Action Description
Show Graph Click this action to view the Cumulative Item Share
(Analysis Level) graph. For field value descriptions, see
Table 21–7.
History Click this action to view the history of Item Velocity
Code Change requests. For field value descriptions,
see Table 21–8.
Field Description
Node Indicates the current node of the user.
Consider Shipments From the first drop-down list, select the start month.
Shipped between
From the second drop-down list, select the end month.
<start month> and
<end month> over the In the text box, enter the number of previous years to
last <number of be included in the analysis.
years> year(s)
Consider Current Year Check this box to consider the current year for the
analysis.

Table 21–6 Recalculate Item Velocity Code, CutOff Percentages

Action Description
Update Item Velocity Click this action to initiate the calculation of velocity
Code codes for items and update the new velocity codes.
Field Description
Velocity Code Indicates the velocity codes.

Dynamic Item Velocity Calculation 299

Calculating Dynamic Item Velocity

Table 21–6 Recalculate Item Velocity Code, CutOff Percentages

Suggested CutOff% Indicates the system-suggested cutoff percentages.

The cutoff percentages are shown on clicking the Show
Graph action. For more information about viewing the
Cumulative Item Share(Analysis Level) Graph, see
Section 21.3.2, "Viewing the Cumulative Item Share
(Analysis Level) Graph".
CutOff% Enter the cutoff percentages, based on which the
velocity codes are calculated.

21.3.2 Viewing the Cumulative Item Share (Analysis

Level) Graph
This section explains how to view the Cumulative Item Share (Analysis
Level) Graph. This graph indicates the cumulative item percentages and
the number of items in percentage that contribute towards those
percentages for a specific analysis level.
To view the Cumulative Item Share (Analysis Level) Graph:
1. Perform Step 1 through Step 3 of Section 21.3.1, "Setting the Time
Period for Dynamic Item Velocity Calculation".
2. In the Select Time Frame panel, click the Show Graph action to view
the Cumulative Item Percentages (Analysis Level) graph, which shows
the cut off percentages for different items.
Figure 21–1 illustrates the Cumulative Item Share (Analysis Level)
Graph. Table 21–7 explains the fields of the Cumulative Item Share
(Analysis Level) Graph.
The CutOff Percentages panel displays the system-suggested cutoff
percentages for different velocity codes. You can also enter the cutoff
percentages, which are used for calculation of new velocity codes. For
field value descriptions, see Table 21–6.

300 Implementation Guide

 Calculating Dynamic Item Velocity

Figure 21–1 Cumulative Item Share (Analysis Level) Graph

Table 21–7 Cumulative Item Share (Analysis Level) Graph

Field Description
Cumulative Percentage Indicates the sum of item percentages for all the
items.
No. of Items (in Indicates the number of items in percentage out of the
percentage) total number of items considered, which contribute
towards a certain cumulative percentage share at any
point the graph.

21.3.3 Viewing Item Velocity Code Change Requests

History
You can view the history of alerts raised by the
YNW_RaiseAlertForItemVelocityCodeAgentStart_91 service, so that you
can determine how you need to change the item velocity codes.
To view the history of item velocity code change requests:

Dynamic Item Velocity Calculation 301

Calculating Dynamic Item Velocity

1. Perform Step 1 through Step 3 of Section 21.3.1, "Setting the Time

Period for Dynamic Item Velocity Calculation".
2. In the Select Time Frame panel, choose History to view the history of
Item Velocity Code Change Requests. For field value descriptions, see
Table 21–8.

Table 21–8 Item Velocity Code Change Requests Fields

Action Description
View Details Click this action to view the Alert Details screen, which
displays details about the raised alert. For more
information about the Alert Detail screen, see the
Sterling Selling and Fulfillment Foundation: Application
Platform User Guide.
Field Description
Alert ID Indicates the identifier of the alert raised.
Suggested CutOff% Indicates the system-suggested cutoff percentages.
Type Indicates the type of alert raised.
Status Indicates that status of the alert.
Request Submitted By Indicates the person who submitted the request to
change the item velocity code.
Start Time Indicates the time the alert is raised.
End Time Indicates the time the alert is closed.

Note: The alerts raised are arranged in the descending

order of their time of creation, that is, the most recent
raised alert is present first.

21.3.4 Updating Item Velocity Code

This section explains how to update the velocity codes of the items.
To update the velocity codes of the items:
1. Perform Step 1 through Step 3 of Section 21.3.1, "Setting the Time
Period for Dynamic Item Velocity Calculation".

302 Implementation Guide

 Calculating Dynamic Item Velocity

2. In the CutOff Percentages panel, enter the cutoff percentages for

your own velocity codes. If the cumulative percentage of an item lies
in the range of cutoff percentages entered for velocity codes, the
velocity codes of the items are categorized as your own velocity
codes. The first velocity code corresponds to the fastest moving item.
For field value descriptions, see Table 21–6.
3. Click the Update Item Velocity Codes action to update the velocity
codes of the items, based on the new cutoff percentages specified.

Note: It is mandatory to enter values for all the fields in

the Item Velocity Code Calculation screen.
A new request to update item velocity codes for a node can
be submitted only if the previous requests are processed.

Q
If you have integrated with a slotting engine to perform slotting,
the Zone List pop-up window appears, which enables you to
re-slot active areas. For field value descriptions, see
Section 21.3.5, "Selecting Zones for Slotting".

Note: The Zone List pop-up displays after you click the
Update Item Velocity Code action if the
[Link] property is set in the
[Link] file. For more information
about configuring [Link] file, see
Section 22.3.2, "Slotting Configurations" of Chapter 22,
"Integration With Slotting Engines".

21.3.5 Selecting Zones for Slotting

This section explains how to select the zones to perform slotting.
To select the zones for slotting:
1. Perform Step 1 through Step 3 of Section 21.3.4, "Updating Item
Velocity Code". The Select Zone for Slotting pop-up window displays.
2. In the Zone List pop-up window, select the zones for slotting from the
list of forward pick zones. For field value descriptions, see Table 21–9.

Dynamic Item Velocity Calculation 303

Calculating Dynamic Item Velocity

3. To create move tasks to move the items based on slotting

assignments, check Create Moves.
4. Perform either of the following:
Q
Choose the Apply results from slotting option to apply slotting
assignments returned by the Slotting Engine.
Q
Otherwise, choose the Save results without applying option. This
saves all files generated by the Slotting Engine on that particular
date for future references. The files are saved in the following
folder:
<folder name configured in the properties files>/<Node
name>/<Date>
5. Click Reslot and Recalculate Item Velocity to apply or save the
slotting results.

Table 21–9 Zone List

Field Description
Zone Id Indicates the name of the forward pick zone.
Zone Description Indicates the description for the zone.
Create Moves Check this to create move tasks based on the
item-location dedications.
Apply results from Choose this option to apply slotting results returned
slotting by the Slotting Engine without saving them.
Save results without Choose this option to save all files generated by
applying the Slotting Engine on that particular date for
future references. When this option is chosen, the
results returned are not applied.

304 Implementation Guide

 Calculating Dynamic Item Velocity

Note: When performing slotting, if there are no default

preferences for the node, the preferences are picked up
from the template XML provide by Sterling Warehouse
Management System.

21.3.6 Applying Saved Results for Slotting

This section explains how to apply the saved slotting files to slot the
location-item pairs.
To apply saved slotting files:
1. Log into the Application Console as a warehouse manager or an
inventory supervisor.
2. From the Application Console menu, select Inventory > Apply Slotting
Suggestions. The Apply Slotting Suggestions screen displays.
3. Select the date from the 'Apply Slotting using files generated on'
drop-down. The slotting files generated on this date are used to slot
location-item pairs.
4. Check 'Use Preferences from the Selected Date as Default' option if
you want to use the slotting preferences, goals, and constraints file
generated on this date as the default preferences. When preferences
are set as default, the same preferences are used when slotting is
performed the next time.
5. Click the Apply Slotting action to apply the slotting results generated
on the selected date.
For more information about action descriptions, see Table 21–10.

Table 21–10 Apply Slotting

Action Description
Apply Slotting Click this action to apply the slotting results generated
on a particular date.
Field Description

Dynamic Item Velocity Calculation 305

Calculating Dynamic Item Velocity

Table 21–10 Apply Slotting

Apply Slotting using Select the date on which the slotting results are
the files generated on generated from the drop-down.
Use Preference from Check this box to keep the current slotting preferences
the Selected Date as as default preferences for the node. These preferences
Default are used when re-slotting is performed.

306 Implementation Guide

 22
Integration With Slotting Engines

Warehouses re-slot forward pick zones every season to utilize the most
cost-effective and efficient locations to store inventory. Slotting is
performed based on the velocity of the items. Slotting ensures that items
with highest velocity are placed in locations belonging to the Golden
zone. Locations in the Golden zone are easily accessible. Therefore, the
picking efficiency of the picker is increased when picking inventory in this
zone.

22.1 Slotting Engines

Slotting tools are often used by warehouses to increase space utilization
and picking efficiency, thus reducing storage and product retrieval costs.
Slotting engines use data, such as warehouse preferences, constraints,
goals, items to be slotted, slots, and historical data to create location
assignments for fast moving items.
Slotting engines also generate a list of moves based on the differences
between the current assignments and the optimized assignments. The
generated Moves List could also be a chain of dependent moves that
should be executed in a specific order.

22.2 Slotting Using IBM Sterling Warehouse

Management System
Sterling Warehouse Management System provides the ability to integrate
with third-party slotting solutions, for example, Sterling Warehouse
Management System has provided an integration with Optislot™, a
popular slotting engine from Optricity™.

Integration With Slotting Engines 307

Integration

Sterling Warehouse Management System enables you to perform slotting

of forward pick zones on a seasonal basis. Slotting in Sterling Warehouse
Management System is performed along with Dynamic Item Velocity
Calculation and is triggered from the Recalculate Item Velocity Code
screen. For more information about the Recalculate Item Velocity Code
screen, see Section 21.3, "Calculating Dynamic Item Velocity" of
Chapter 21, "Dynamic Item Velocity Calculation".

Note: Slotting is performed only for those zones where

picking or putaway tasks are not executed.

22.3 Integration
The following section explains how Sterling Warehouse Management
System integrates with the slotting engines and configurations required
for the integration.

22.3.1 Interfacing with Slotting Engines

Sterling Warehouse Management System provides the performSlotting
API, which invokes methods on the slotting adapter to perform slotting.
The slotting adapter initializes the third-party slotting engine. The
slotting adapter takes data, such as item details, location details, slotting
preferences, goals, and current dedications using APIs and modifies it to
a format understood by the third-party slotting engine. The modified
data is sent to the third-party slotting engine. The third-party slotting
engine slots the locations based on these preferences, goals, and
constraints and sends new slotting assignments back to the slotting
adapter. Optionally, if requested, the third-party slotting engine sends a
list of move suggestions, which contain suggestions to move the
inventory from the existing source location to a target location. The move
suggestions are generated by differentiating between the existing
slotting assignments and optimized slotting assignments. The slotting
adapter receives the slotting assignments and the moves list. After the
output from the slotting adapter is obtained as a list of moves or
assignments for each slot and item, the performSlotting API resets the
existing dedications and creates new dedications for the Forward Pick
zones. Optionally, you can create move tasks to move inventory from the
existing location to the assigned location, if required. For more

308 Implementation Guide

 Integration

information about the performSlotting API, see the Sterling Warehouse

Management System: Javadocs.

Figure 22–1 illustrates how Sterling Warehouse Management System

interfaces with third-party slotting engines.

Figure 22–1 Interfacing with Third-Party Slotting Engines

Slotting results obtained by integrating with slotting engines can be

saved in a folder to be reviewed and applied later. During the review
process, the preferences, constraints, and so forth contained in these
files could be modified.
The applySlotting API is used to apply slotting results obtained from the
slotting engine and optionally apply the slotting preferences from the
saved files. When invoked from the Application Console, the
YNW_ApplySlotting_9.1 service puts a message in the JMS Queue. The
message contains information about the folder containing the slotting
assignments generated on a date, which you want to apply. This
message is picked up by the service YNW_AppSlotPickMsg_9.1, which is
invoked by the server Slotting. The message is then provided to
applySlotting API. If slotting preferences used by the slotting engine on a

Integration With Slotting Engines 309

Integration

particular date are made the default preferences, the preferences are
saved and the same preferences are used when re-slotting is performed
again for the same node. For more information about the applySlotting
API, see the Sterling Warehouse Management System: Javadocs.

Note: The server Slotting is started by the integration

server.
Ensure that you configure a separate JMS queue and
associate it with the YNW_ApplySlotting_9.1 and
YNW_AppSlotPickMsg_9.1 services.

To interface with slotting engines, an adapter class that implements the

YNWSlottinIntfc Interface needs to be registered with the Sterling
Warehouse Management System. For more information about
implementing the YNWSlottinIntfc interface and registering it with the
Sterling Warehouse Management System, see the Sterling Warehouse
Management System: Javadocs.

22.3.2 Slotting Configurations

This section explains the various configurations that are performed for
the slotting integration process.

Note: Before performing slotting, ensure that there are

no open tasks with the forward pick locations as the source
or target locations.

[Link] Configuring to integrate with Slotting Engines

To integrate slotting using the Sterling Warehouse Management System:
1. Navigate to the <INSTALL_DIR>/properties directory.
2. In the customer_overrides.properties file:
a. Set the [Link] property to the name of the
slotting engine being used. It is recommended that you do not
use special characters in this property and that it is a single word.
b. Set the [Link].<Slotting Engine Name>.class
property to the appropriate class name. This class implements the

310 Implementation Guide

 Reference Implementation

YNWSlottingIntfc interface. Ensure that this class is present in

your CLASSPATH environment variable.
c. Set the [Link].<Slotting Engine Name>.folder
property to the name of the folder that stores the files generated
by the slotting engine.

Note: Ensure that the custom class is present in both the

CLASSPATH environment variable and the Agent Server
classpath when installing the Slotting Engine. Also, ensure
that you regenerate the Runtime after making the above
changes, while installing the Sterling Warehouse
Management System.

[Link] Configuring the Queue for Server Slotting

A seperate queue is to be configured for the server Slotting. The
configurations are:
1. Navigate to <INSTALL_DIR>/properties directory.
2. In the customer_overrides.properties file:
a. Add new parameters yfs.APPLY_SLOTTING_QUEUE,
yfs.ApplySlotting_QCF, and yfs.Provider_URL.
b. Set the value of these parameters to the name of the JMS queue,
QCF and provider URL.

22.4 Reference Implementation

For Reference Implementation, Sterling Warehouse Management System
has integrated with OptiSlot™ from Optricity™ to provide slotting
solutions. OptiSlot™ is a slotting engine that enables warehouses to
perform slotting based on various constraints. Sterling Warehouse
Management System supports slotting only if the following conditions are
satisfied for the zones that are being slotted:
Q
The forward pick zone is not dedicated to an enterprise and allows
the storage of products for all enterprises.
Q
The number of locations for each SKU is not limited when slotting
multiple forward pick zones at the same time. The Max No of

Integration With Slotting Engines 311

Reference Implementation

Locations Per SKU is defined for zones while configuring

Warehouse Layout.
For more information about configuring the Warehouse Layout,
see the Sterling Warehouse Management System: Configuration
Guide.
Post slotting, the integration provides ability to move the items to
theirrespective slot. In order to use this functionality:
Q
Items and product classes must not get mixed at any [Link]
inventory attributes should be allowed to mix at these locations.
Q
Locations must not track license plates.

Note: It is recommended that you reslot the same set of

forward pick zones every time. Selecting different set of
zones might lead to creation of duplicate slot assignments.

Note: To integrate with OptiSlot™, install OptiSlot™ along

with the Sterling Warehouse Management System. For
more information about installing OptiSlot™, see the
Sterling Warehouse Management System: Installation
Guide.

22.4.1 Reference Implementation Integration Strategy

OptiSlot™ uses three XML files to slot location-item pairs, namely,the
Project file, Slots file, and Items file. Sterling Warehouse Management
System mandates that the names of the files be [Link],
[Link], and [Link].
The Slots file contains information about zones and locations. This file
also contains statistics, such as the number of times a location is
accessed. The information in the Slots file isused by OptiSlot™ in
performing slotting.
The Items file contains information about case and pallet dimensions,
quantity of items, velocity of items, stacking pattern of items in a
location, and so forth.

312 Implementation Guide

 Reference Implementation

The Project file contains information about existing SKU dedications,

goals, preferences, and constraints on the basis of which slotting is
performed. The Project file is generated based on the template file
provided by Sterling Warehouse Management System. The template file
contains preferences for slotting. This template file is located in the
<INSTALL_DIR>/repository/xapi/template/merged/slotting/OptiSlo
t directory.
After these files are sent to OptiSlot™, OptiSlot™ slots the different
locations of the zone provided in the Slots file and assigns these slots to
the different SKUs provided in the Items file, based on the goals,
preferences, and constraints present in the Project file. Slot assignments
are returned by OptiSlot™, and these assignments are included as a part
of Project XML.
You can choose to apply these assignments or save them in a folder so
that they can be used when re-slotting is done in future. The Project XML
is saved along with the item XML and location XML in the following
folder:
<folder name configured in the properties files>/<Node
name>/<Date>
The slotting preferences and slotting results can be seen in the OptiSlot™
UI. If the results are not satisfactory, the preferences and constraints can
be modified, regenerated, and saved once satisfactory in the OptiSlot™
UI. For more information about launching the OptiSlot™ UI, see the
OptiSlot™ documentation.
Based on the location-item assignments, location dedications and move
tasks may be generated to move the items to the assigned locations.
Move tasks are generated using the Moves List provided by OptiSlot™.
The Moves List contains a chain of moves and a task is created for each
move in the chain, with the previous move in the chain as a predecessor
task. The first move task in the chain is released and the rest are held.
Each successor task is initiated only when the predecessor task is
completed.
Items that are unslotted are putaway to storage.

22.4.2 Slotting Configurations for OptiSlot™

This section explains the various configurations that are provided for
integrating with OptiSlot™.

Integration With Slotting Engines 313

Reference Implementation

To integrate using the Sterling Warehouse Management System:

1. Navigate to the <INSTALL_DIR>/properties directory.
2. In the customer_overrides.properties file:
a. Set the [Link] property to OptiSlot.
b. Set the [Link] property to
[Link].
c. Set the [Link] property to the
name of the folder that stores the files generated by OptiSlot™.

314 Implementation Guide

 A
Transaction Data

Transaction data is required to demonstrate the capabilities of Sterling

Warehouse Management System. In addition to that, installation
validations are done with the help of the transaction data. The
transaction data is configured such that the basic processes explained in
the documentation are fulfilled.
Transaction Data can be optionally run at the time of installing Sterling
Warehouse Management System. If the user opts to install Sterling
Warehouse Management System along with the transaction data, the
transaction data is created. Otherwise, some template XMLs files are
provided that can be used later to install the transaction data.
This appendix explains the transaction data that is provided as a part of
Sterling Warehouse Management System.

A.1 Inbound
The following scenarios are captured as a part of the transaction data.
The inbound process is based on a separate set of items that are not
used in inventory or outbound.
Q
PO Based Receipt
Q
ASN Based
Q
Blind Receipts
Q
Transfer Order Shipments (Order not on System)

Transaction Data 315

Inventory

A.1.1 PO-Based Receipt

The transaction data contains the setup for 5 to 6 Purchase Orders. Each
Purchase Order contains multiple items. Receipts are not created. Users
can log into the application and start receiving against the PO.
ASNs are generally sent out by the vendor to the warehouse or DC.
The following assumptions are made in terms of the transaction:
Q
VENDOR1 sends ASN information
Q
VENDOR2 does not send ASN information

A.1.2 ASN-Based Receipts

ASNs are sent out by VENDOR1. For ease of demonstration, a couple of
ASNs from VENDOR1, with item-level details, have been created.

A.1.3 Transfer Order Shipments

For the Transfer shipments, it is assumed that the ASN is sent with PLD
(Package Level Details).

A.2 Inventory
For inventory data, it is assumed that the warehouse tries not to mix
SKUs at the locations. Therefore, preferably, no more than one item
should be stored at the BULK/Forward Pick locations. The inventory data
is made in such a way that inventory is sufficient for all the outbound
shipments created.
It is assumed that five items are put in storage and inventory is created
for items NOR-00001 to NOR-00005. The Forward Pick Area with
dedicated locations is set up for items NOR-00001 to NOR-00005. In
addition to this, some inventory is added for serialized and tag-controlled
items.
The inventory at the Forward Pick Area is set up in such a way that:
1. If the Min-Max Replenishment is run, there are some Replenishment
Tasks created.
2. When running the Top-Off Replenishment after running Min-Max
Replenishment, some Replenishment Tasks are created.

316 Implementation Guide

 Outbound

A.3 Outbound
The transaction data for outbound varies based on the availability of the
Sterling Distributed Order Management application. If Sterling
Distributed Order Management is available, the process starts with
creating an order.
The categories of the shipment are:
Q
200 parcel shipments
Q
25 LTL shipments
Q
2 TL shipments
For the paper-based warehouses, the volumes of shipments are:
Q
50 parcel shipments
Q
5 to 10 LTL shipments
Q
1 TL shipments
Shipments are created in such a way that for Parcels, at least a few
shipments use both Full Case and Less than Case Pick processes.
Similarly, LTL shipments are created in such a way that the pick is made
from both Bulk and Forward Pick Area.
Shipments contain one item for which inventory is not existing in the
warehouse. This is to ensure that on release of the wave, appropriate
alerts are raised.
Routing is configured as a part of the Reference Implementation. On
installing the transaction data, the ROUTE_SHIPMENT and
SENT_TO_NODE agents are automatically executed. The shipment status
starts from the Sent To Node status.
The outbound transaction data is set up so that waves are created as
soon as the agent is run.

Transaction Data 317

Outbound

318 Implementation Guide

 B
New Components for Existing IBM Sterling
Selling and Fulfillment Foundation
Customers

This appendix is meant as a quick reference for individuals who are

already familiar with the Sterling Selling and Fulfillment Foundation to
see which components were added or modified when implementing the
Sterling Warehouse Management System.
Click the following categories to view the components that were
introduced or modified from the Sterling Selling and Fulfillment
Foundation to Sterling Warehouse Management System:
Q
APIs and User Exits
Q
Services
Q
Monitor Events
Q
Transactions
Q
Events

B.1 APIs and User Exits

Table B–1 lists the APIs and User Exits introduced in Sterling Warehouse
Management System, along with the features they affect.

New Components for Existing IBM Sterling Selling and Fulfillment Foundation Customers 319
APIs and User Exits

Table B–1 APIs and User Exits

API or User Exit Feature Affected
registerActivityDemand QC Divert Capability Based on Percentage
ForQC()
modifyPackListUE() Packing Slip for B2C shipments Print
getShipmentDiscrepan Vendor Compliance
cyList()
manageShipmentDiscr Vendor Compliance
epancy()
getAREActivityAuditList Billing Activity based Reporting Engine
()
getAREActivityCodeDet Billing Activity based Reporting Engine
ails()
getAREActivityCodeList Billing Activity based Reporting Engine
()
getAREActivityDetails() Billing Activity based Reporting Engine
getAREActivityList() Billing Activity based Reporting Engine
manageAREActivity() Billing Activity based Reporting Engine
manageAREActivityCod Billing Activity based Reporting Engine
e()
YNWBeforeCreateAREA Billing Activity based Reporting Engine
ctivityUE
manageItemStatistics Dynamic Item Velocity Calculation
incrementItemStatistic Dynamic Item Velocity Calculation
s
getShipmentItemStatis Dynamic Item Velocity Calculation
tics
getItemStatisticsGraph Dynamic Item Velocity Calculation
Data

For more information about the APIs and user exits mentioned in
Table B–1, refer to the Sterling Warehouse Management System:
Javadocs.

320 Implementation Guide

 Services

B.2 Services
This section lists the services that are new in Sterling Warehouse
Management System, and can be found in the service definitions.

B.2.1 Receiving or QC-Related Services

Table B–2 Receiving or QC-Related Services

Service Feature Affected
YNW_RegisterActivityDemandForQC_ QC Divert Capability Based on
91 Percentage
YNW_PrintReceivingWorkSheet_91 Receiving Worksheet Print
YNW_CompositeServiceOnStartRecei QC Divert Capability Based on
pt_91 Percentage
Receiving Worksheet Print
YNW_GetDataReceivingWorkSheet_9 Receiving Worksheet Print
1
YNW_GetDataForUPCCaseCodeLabel UPC Case Code Label Print
_91
YNW_GetLPNDataForAdditionalPrint_ License Plate Label Manual Print
91
YNW_LPNTranslator_91 License Plate Label Print
YNW_PrintAdditionalLPNLabels_91 License Plate Label Manual Print
YNW_PrintLPNLabelsOnStartReceipt_ License Plate Label Print, when receipt
91 is started.
YNW_PrintUPCCaseCodeLabel_91 UPC Case Code Label Print
Get Shipment Item Statistics Dynamic Item Velocity Calculation
Update Item Statistics Dynamic Item Velocity Calculation
Enqueue Dynamic Velocity Code Calc Dynamic Item Velocity Calculation
Agent Message
Item Statistics Data Loader Dynamic Item Velocity Calculation
Item Statistics Mining service Dynamic Item Velocity Calculation

New Components for Existing IBM Sterling Selling and Fulfillment Foundation Customers 321
Services

Table B–2 Receiving or QC-Related Services

Service Feature Affected
YNW_RaiseAlertForItemVeloctiyCode Dynamic Item Velocity Calculation
AgentStart_91
YNW_ResolveAlertForItemVeloctiyCo Dynamic Item Velocity Calculation
deAgentStart_91

B.2.2 Move Request Services

Table B–3 Move Request Services

Service Feature Affected
YNW_GenerateTopOffRplMR_91 Replenishments (Reference
Implementation)
YNW_GenerateMinMaxRplMR_91 Replenishments (Reference
Implementation)
YNW_RaiseMoveRequestException_9 Alerts for Move Request Release
1 Failures
YNW_GeneratePutawayRequestForW Automatic Generation of Putaway Task
orkOrder_91 After Work Order Completion
(Reference Implementation)

B.2.3 Shipment Processing Services

Table B–4 Shipment Processing Services

Service Feature Affected
YNW_RaiseDelayInShipmentPackProc Alerts for Delayed Outbound Shipments
ess_91
YNW_changeShipmentStatusToPicke Shipment Pipeline Configuration
d_91 includes Picked Status
YNW_ConditionForPrintingSpecialTick Special Ticket Label Print
et_91
YNW_GetB2CPackListData_91 Packing Slip for B2C shipments Print

322 Implementation Guide

 Services

Table B–4 Shipment Processing Services

Service Feature Affected
YNW_GetLoadDetailsForInternational International shipments labels
Shipments_91 (Certificate of Origin, NAFTA Certificate
of Origin, Commercial Invoice) Print
YNW_GetLoadDetailsForShippersExp Shippers Export Declaration Print
ortDeclaration_91
YNW_GetPackListPLDData_91 Packing Slip with Package Level Details
Print
YNW_GetShipmentDetailsForInternat International shipments labels
ionalShipments_91 (Certificate of Origin, NAFTA Certificate
of Origin, Commercial Invoice) Print
YNW_GetShipmentDetailsForShipper Shippers Export Declaration Print
sExportDeclaration_91
YNW_PrintCertificateOfOriginForLoad Certificate of Origin Print for Loads
s_91
YNW_PrintCertificateOfOriginForShip Certificate of Origin Print for Shipments
ments_91
YNW_PrintCommercialInvoiceForLoa Commercial Invoice Print for Loads
ds_91
YNW_PrintCommercialInvoiceForShip Commercial Invoice Print for Shipments
ments_91
YNW_PrintCombinedPickingPackingSl Combined Picking and Packing Slip
ip_91 Print
YNW_PrintPackListPLD_91 Packing Slip with Package Level Details
Print
YNW_PrintShippersExportDeclaration Shippers Export Declaration Print
ForLoads_91
YNW_PrintShippersExportDeclaration Shippers Export Declaration Print
ForShipments_91
YNW_PrintSpecialTicketLabels_91 Special Ticket Labels Print
YNW_getXrefItemDetails_91 Special Ticket Labels Print
YNW_GetPackListData_91 Packing Slip Print
YNW_GetRFIDData_91 RFID Slap and Ship Label Print
YNW_GetShippingLabelData_91 Shipping Label Print

New Components for Existing IBM Sterling Selling and Fulfillment Foundation Customers 323
Services

Table B–4 Shipment Processing Services

Service Feature Affected
YNW_PrintRFIDLabel_91 RFID Slap and Ship label Print
YNW_PrintShippingLabel_91 Shipping Label Print
YNW_PrintLoadBOL_91 Bill of Lading Print for Load
YNW_GetLoadBOLData_91 Bill of Lading for Load
YNW_GetShipmentBOLData_91 Bill of Lading Print for Shipment
YNW_PrintShipmentContainerLabels_ Shipping Label Print
91
YNW_PrintShipmentRFIDLabels_91 RFID Slap and Ship Label Print
YNW_PrintShipmentBOL_91 Bill of Lading Print for Shipment
YNW_PrintPackList_91 Packing Slip Print

B.2.4 Wave Processing Services

Table B–5 Wave Processing Services

Service Feature Affected
YNW_RaiseAlertForInventoryShortage_91 Alerts For Inventory
Exceptions During Outbound
Processes
YNW_RaiseAlertForShipmentInvShortage_91 Alerts For Inventory
Exceptions During Outbound
Processes
YNW_RaiseAlertForItemInvShortage_91 Alerts For Inventory
Exceptions During Outbound
Processes
YNW_RaiseInventoryShortageForLocationAndIt Alerts For Inventory
em_91 Exceptions During Outbound
Processes
YNW_RaiseInventoryShortageForItem_91 Alerts For Inventory
Exceptions During Outbound
Processes
YNW_DownloadFileFromMHE_91 Download of the interface file
sent by external MHEs.

324 Implementation Guide

 Monitor Events

Table B–5 Wave Processing Services

Service Feature Affected
YNW_DownloadFileToMHEWithReference_v Download of the interface
file, containing additional
reference data, sent by
external MHEs.
YNW_GetDataForWaveSummary_91 Wave Summary Print
YNW_PrintWave_91 Wave Summary Print
YNW_RegisterTaskCompletion_91 Download of the interface
file, containing additional
reference data, sent by
external MHEs.
YNW_UploadFileToMHE_91 Upload of the interface file
sent to external MHEs.
YNWPrintShippingLabel_91 Shipping Label Print

B.3 Monitor Events

Table B–6 lists the monitor event that is new in Sterling Warehouse
Management System.

Table B–6 Monitor Events

Monitor Event Feature Affected
YNW_PACKING_DELAYED_91 Alerts for Delayed Outbound Shipments

New Components for Existing IBM Sterling Selling and Fulfillment Foundation Customers 325
Events

B.4 Transactions
The transactions introduced in Sterling Warehouse Management System
are displayed inTable B–7.

Table B–7 Transaction

Transactiont Feature Affected Event
Create Second Count Physical Count On Success
Tasks
No Tasks Created
Pallet Shrink Wrap Pack Process for Pallets On Success
Putaway Complete Receiving On Success
VERIFY PACK Verifying Pack VERIFICATION DONE,
DISCREPANCY FOUND

B.5 Events
The events that have been implemented in Sterling Warehouse
Management System are displayed in Table B–8.

Table B–8 Events

Transaction Event
Start Receipt On Success
Close Receipt On Success
Create Batch On Success
Complete Task Shipment Picked
Release Wave Shortages Detected
Release Move Request On Success
Release Move Request Has Exceptions
Confirm Work Order LPN Activities Completed
Confirm Work Order SKU Activities completed
Confirm Work Order Serial Number Activities completed
Print Wave On Success

326 Implementation Guide

 Events

Table B–8 Events

Transaction Event
Confirm Shipment On Success
Receive Intransit Updates for Load On Success
VERIFY PACK VERIFICATION DONE
VERIFY PACK DISCREPANCY FOUND

Table B–9 Events

Agent Event
DYNAMIC_VELOCTIY_CALC AGENT_START
DYNAMIC_VELOCTIY_CALC AGENT_COMPLETION

New Components for Existing IBM Sterling Selling and Fulfillment Foundation Customers 327
Events

328 Implementation Guide

 C
Customizing the Reference Implementation

This appendix explains how to customize the Reference Implementation

data provided as a part of the Sterling Warehouse Management System,
customize your node, use the test environment for production, and move
data from your test environment to production.

C.1 Customizing Reference Implementation Data

Now that you are familiar with the Reference Implementation provided as
a part of Sterling Warehouse Management System, you can use the data
provided in the Reference Implementation as a starting point. This
section explains how to customize the Reference Implementation to meet
your needs.

C.1.1 Loading Your Own Master Data

You can load your own master data to go with our configuration data.
This master data can be based upon the master data that has been
provided as part of the Reference Implementation of Sterling Warehouse
Management System, which is located in:
<INSTALL_DIR>/Applications/nWMS/database/FactorySetup/ri/defau
ltri/ demo/MasterData
Here, <INSTALL_DIR> points to the Sterling Selling and Fulfillment
Foundation software installation directory.

C.1.1.1 Item
You can use the item data load capability to load your own master data.
For more information about initial data loading services and rapid

Customizing the Reference Implementation 329

Customizing Reference Implementation Data

deployment features, see the Selling and Fulfillment Foundation:

Integration Guide.
Ensure that you use the following values that are already available in the
configuration:
Q
Velocity codes
Q
Storage code
Q
Item-UOM
Q
Product Class

C.1.1.2 Location
You can either create your own locations or look at the locations provided
under the master data and create similar locations in your warehouse.
For more information about initial data loading services and rapid
deployment features, see the Selling and Fulfillment Foundation:
Integration Guide.
Ensure that you use the following values that are already available in the
configuration:
Q
Zones (most rules are tied to zones)
Q
Storage Type
Q
Storage classification
Q
Size codes

C.1.1.3 Equipment
You can either create your own equipment pointing to these locations or
look at the equipment provided under the master data and create similar
equipment pointing to locations in your warehouse.

C.1.2 Loading Your Own Transaction Data

You can choose to load your own transaction data to go with our
configuration data and master data. This transaction data can be based
upon the transaction data that has been provided as a part of the

330 Implementation Guide

 Customizing Your Node

Reference Implementation of the Sterling Warehouse Management

System, which is located in:
<YANTRA_HOME>/Applications/nWMS/database/FactorySetup/ynw/ri/
defaultri/TransactionData
Where, <YANTRA_HOME> points to the Sterling Selling and Fulfillment
Foundation software installation directory.

C.1.2.1 Location Inventory

If you chose to load your own master data, you would most likely need
to use the initial data loading service to load the inventory data. For
more information about initial data loading services and rapid
deployment features, see the Selling and Fulfillment Foundation:
Integration Guide.

C.2 Customizing Your Node

You can use the node data that has been provided to explore around and
fine tune some configurations. However, it is recommended that you use
the copy node functionality to copy the node data to a node of your
choice before modifying the data. This enables you to retain a copy of
the original Reference Implementation. You can look into this if you
cannot get something working after fine tuning some of the
configurations. For more information about copying and deleting
configurations for node or enterprise’ participation information, see the
Sterling Warehouse Management System: Configuration Guide.

C.2.1 Copying Node Configuration

To copy the node configurations from one node to another:
1. Copy the node data using the copy node functionality from the
Applications Manager.
2. Follow the steps provided in the Sterling Selling and Fulfillment
Foundation: Installation Guide to customize your new node.

C.2.2 Onboarding Clients (Enterprises)

On-boarding new clients is similar to customizing nodes; you can choose
to either use the enterprise provided with Sterling Warehouse

Customizing the Reference Implementation 331

Customizing Your Node

Management System, or just copy over the enterprise-related setup to

another client. The new client may source from an existing warehouse as
well as a new warehouse.
To on-board a new client:
1. Create a backup of the Master Configuration using the Configuration
Deployment Tool.
2. Create a new Enterprise in the participant model. Copy or Inherit the
configuration from the existing enterprise.

Figure 22–2 Creating a New Enterprise

332 Implementation Guide

 Customizing Your Node

For more information about creating a new enterprise, see the

Sterling Selling and Fulfillment Foundation: Application Platform
Configuration Guide.
3. Create a new warehouse using the copy node functionality in the
Applications Manager.

Figure 22–3 Creating a New Warehouse Using Copy Node

For more information about copying an existing node to a new node,

see the Sterling Warehouse Management System: Configuration
Guide.
4. On-board the new client to the new warehouse.

Figure 22–4 On-Boarding a New Client

Customizing the Reference Implementation 333

Customizing Your Node

For more information about on-boarding an enterprise to a node, see

the Sterling Warehouse Management System: Configuration Guide.
5. Remove (off-board) other enterprises from the new warehouse if you
do not want these enterprises to participate with the new warehouse.

Figure 22–5 Off-Boarding an Enterprise

For more information about off-boarding an enterprise from a node,

see the Sterling Warehouse Management System: Configuration
Guide.
6. On-board the new client to the existing warehouse.

Figure 22–6 On-Boarding a New Client

For more information about on-boarding an enterprise to a node, see

the Sterling Warehouse Management System: Configuration Guide.
7. Test the new client operations in the existing and as well as new
warehouses.

334 Implementation Guide

 Customizing Your Node

8. Deploy the configurations as follows:

d. Compare the configurations between the production and test
environments using the Configuration Deployment Tool.
The configuration differences appear in the Comparison Results
screen, as illustrated in Figure 22–7.
e. Migrate the new configuration to the production environment, by
selecting the appropriate difference and clicking Deploy.

Figure 22–7 Deploying Configurations

C.2.3 Offboarding Clients (Enterprises)

You can choose to off-board the enterprises from the node provided with
Sterling Warehouse Management System that has been shipped
out-of-the-box. This can be done by using the off-board enterprise
functionality.

Figure 22–8 Off-Boarding an Enterprise

Customizing the Reference Implementation 335

Moving Data from the Test Environment to Production

For more information about off-boarding an enterprise from a node,

see the Sterling Warehouse Management System: Configuration
Guide.

C.2.4 Deleting a Node

You can delete the data that Sterling Warehouse Management System
provides by using the delete node functionality. However, before you do
this, you should off-board the clients.
For more information about deleting the current node, see the Sterling
Warehouse Management System: Configuration Guide.

C.3 Moving Data from the Test Environment to

Production
Once you have configured the system to model your network warehouse
and completed the User Acceptance Test (UAT) using the data, to go into
production on a machine that is different from the test environment, use
the Sterling Selling and Fulfillment Foundation Configuration Deployment
Tool to copy the configuration from one schema to another. For more
details about Deploying Configuration Data, see the Sterling Selling and
Fulfillment Foundation: Installation Guide.

336 Implementation Guide

 D
Localizing IBM Sterling Warehouse
Management System

All the Sterling Warehouse Management System components use a

common resource bundle that contains the literals displayed on the
screen. Sterling Warehouse Management System enables you to
customize and localize resource bundles as needed.
In addition, literals used in customized screens have their own resource
bundle and should also be considered during the localization process. For
information about localizing your customization to Sterling Warehouse
Management System, see the Sterling Selling and Fulfillment Foundation:
Customization Guide.

Note: Literals cannot be localized in the following places:

Q
Condition Builder
Q
Order/Shipment Monitor
Q
Hard-coded literals in APIs

This appendix explains how to localize Sterling Warehouse Management

System.

D.1 Resource Bundles

Sterling Warehouse Management System always releases complete
resource bundles in the [Link] file with the localized
versions of the Sterling Warehouse Management System. Incremental
updates are not provided. If you localize the Sterling Warehouse

Localizing IBM Sterling Warehouse Management System 337

Resource Bundles

Management System, it is your responsibility (or that of your third-party

localization company) to compare and validate the differences between
the resource bundles shipped with the product to those you have
localized.
The resource bundles of the Sterling Warehouse Management System
application are located in the
<YNW_HOME>/resources/[Link] file.
For more information about localizing the resource bundles, see the
Sterling Selling and Fulfillment Foundation: Localization Guide.

338 Implementation Guide

 E
Packing Using the Mobile Application

The Mobile Application enables you to perform pack processes in a

warehouse.
You can use the Mobile Application for:
Q
Packing without recording item details.
Q
Packing with the system identifying item details.
Q
Packing with the user recording item details.
Q
Verify packing.
Q
Unpacking.
This appendix explains the processes of packing, verifying pack, and
unpacking using the Mobile Application.
For more information about the Mobile Application console framework,
see the Sterling Selling and Fulfillment Foundation: Mobile Application
User Guide.

E.1 Understanding the Supported Pack Processes

Packing in a warehouse depends on the way the inventory is picked and
the reference available to the packer. Packing also depends on the
containerization process.

E.1.1 Packing Based on Picking

This section explains the various ways of packing, depending upon the
different picking methods.

Packing Using the Mobile Application 339

Understanding the Supported Pack Processes

Mobile Application Cart Manifest Pick

Here, inventory is picked using the Mobile Application and sorted into
cart locations, based on the shipments to which they belong.
Q
If the packlist is available to the packer, the packer scans the
shipment number from the packlist to identify the shipment to
pack.
Q
If the packlist is not available to the packer, the packer scans the
cart ID first and then the cart location associated with the
shipment to pack.

Paper-Based Cart Manifest Pick

Here, inventory is picked using a batch sheet and sorted into cart
locations based on the shipments to which they belong.
Q
If the packlist is available to the packer, the packer scans the
shipment number from the packlist to identify the shipment to
pack.
Q
If the packlist is not available to the packer, the packer scans the
batch sheet number first and then the cart location associated
with the shipment to pack.

Mobile Application Cart Manifest Pick using Totes

Here, inventory is picked using the Mobile Application and sorted into
different totes. Each tote is associated with a shipment.
The packer scans the tote ID to identify the shipment to pack.

Mobile Application Pick using a Pallet

Here, inventory for each shipment is picked into a separate pallet using
the Mobile Application.
If the packlist is not available to identify the shipment to pack, the
packer scans the pallet ID.

Paper-Based Pick using a Pallet or Case

Here, each shipment is picked into a pallet or a case using a batch sheet.

340 Implementation Guide

 Understanding the Supported Pack Processes

Q
If the pick confirmation is done after picking at the batch console,
the packer scans the pallet ID or the case ID to identify the
shipment.
Q
If the pick confirmation is done at the pack station without the
pallet or the case, the packer scans the batch sheet number to
identify the shipment.
Q
If the pick confirmation is not done at all, the packer scans the
batch sheet number to identify the shipment.

E.1.2 Packing Based on Containerization

This section explains the various ways of packing based on the
containerization methods supported by the Mobile Application.

E.1.2.1 User-Directed Containerization

In this type of containerization, the packer decides on the appropriate
container to use for packing, based on the dimension of the container.
To pack a container:
1. Select the container in which you want to pack.
2. Apply a pre-printed container SCM to the container.
3. Scan the container SCM. You can alternately ask the system to
generate a SCM for you.
4. Pack inventory in the container.
5. To pack more containers, repeat Step 1 through Step 4 until you have
packed all containers for all the shipments.

E.1.2.2 System-Directed Containerization

In this type of containerization, the system suggests the appropriate
container for packing, based on the dimension of the container.
To pack a container:
1. Use the container suggested by the Mobile Application.
2. Apply a pre-printed container SCM to the container.
3. Scan the container SCM. You can alternately ask the system to
generate a SCM for you.

Packing Using the Mobile Application 341

Pack Strategies

4. Pack inventory in the container.

5. To pack more containers, repeat Step 1 through Step 4 until you have
packed all containers for all the shipments.

E.2 Pack Strategies

There are two strategies for packing: Shipment-Driven and Item-Driven.
This section explains these two pack strategies.

E.2.1 Shipment-Driven Packing

In this type of pack, the shipment is packed after identifying the
shipment number. Shipment-Driven packing is further categorized into
User-Directed Packing and System-Directed Packing.

Note: Multi-level container packing is not supported in

Shipment-Driven Packing.

E.2.1.1 User-Directed Packing

In this type of packing, the packer selects the appropriate container for
packing.
There are three ways of performing this type of packing.
Q
Packing Without Recording Item Details
Q
Packing With the System Identifying Item Details
Q
Packing With the User Recording Item Details
Figure 22–9 illustrates the Shipment-Driven, User-Directed Packing.
Figure 22–10 illustrates capturing the item attributes.

342 Implementation Guide

 Pack Strategies

Figure 22–9 Shipment-Driven, User-Directed Packing

Packing Using the Mobile Application 343

Pack Strategies

Figure 22–10 Capturing Item Attributes

344 Implementation Guide

 Pack Strategies

E.[Link] Packing Without Recording Item Details

The Mobile Application enables you to pack items without capturing the
item details.
To pack items without recording the item details:
1. From the Menu page, select Pack Shipment and press Enter. The Pack
screen displays, which enables you to scan the pack location. For
more information about scanning the pack location, see
Section E.2.3, "Scanning a Pack Location".
Q
If there is more than one pack station associated with a pack
location, the Select Pack Station screen displays, which enables
you to select the appropriate pack station. For more information
about selecting a pack station, see Section E.2.4, "Selecting a
Pack Station".
2. The Scan Identifier screen displays, which enables you to enter or
scan the task list number. For more information about scanning the
task list number, see Section E.2.1.3, "Scanning the Task List
Number".
Q
If multiple shipments are found with the same task list number,
and if you scan a cart identifier, the Shipment Identifier screen
displays, which enables you to scan the cart location. For more
information about scanning the cart location, see Section E.2.1.4,
"Scanning the Cart Location".
In the Shipment Identifier screen:
– If you want to continue packing, choose Go. The Open
Container screen displays, which enables you to open a case
or a pallet. For more information about opening a new
container, see Section E.[Link], "Opening a Container".
– To identify a new shipment for packing, choose Back. The Scan
Identifier screen displays. For more information about
scanning a task list number, see Section E.2.1.3, "Scanning
the Task List Number".
Q
Otherwise, the Open Container screen displays, which enables you
to open a case or a pallet. For more information about opening a
new container, see Section E.[Link], "Opening a Container".
3. In the Open Container screen:

Packing Using the Mobile Application 345

Pack Strategies

Q
To pack in a pallet or case, choose Open Case or Open Pallet. The
Open Case or Open Pallet screen displays which enables you to
open a pallet or a case. For more information about opening a
case or a pallet, see Section E.[Link], "Opening a Case or a
Pallet".
Q
Choose Done to pack for a new shipment.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, The Scan Identifier screen displays. For more
information about scanning a task list number, see
Section E.2.1.3, "Scanning the Task List Number".
4. In the Open Case or Open Pallet screen, scan the container SCM or
choose Generate. The Open Container screen displays. For more
information about opening a case or a pallet, see Section E.[Link],
"Opening a Case or a Pallet".
5. Repeat Step 3 through Step 4 to pack more containers for the
shipment.
6. Repeat Step 2 through Step 4 to pack more shipments.
7. After packing all the shipments, press F10 to go back to the main
menu.

E.[Link] Packing With the System Identifying Item Details

In this type of packing, the system automatically identifies the details of
the items.
To perform this type of pack, follow all the steps in Section E.[Link],
"Packing Without Recording Item Details".

Note: The inventory sorted in a container is packed in an

outbound container for the shipment. When you press
Open Case or Open Pallet in the Open Container screen
after packing the inventory for the shipment, empty
containers are generated for the shipment.

346 Implementation Guide

 Pack Strategies

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to enable the
system to record item details automatically:
Q
In the Applications Manager, copy and save the
rfpackshpmt resource. The following displays in the
Java Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value>.
Q
Set the value for the AutoRecordContents attribute to
'Y'.
For more information about creating a new resource and
adding a new menu entry, see Sterling Selling and
Fulfillment Foundation: Customization Guide.

E.[Link] Packing With the User Recording Item Details

The Mobile Application enables you to pack recording item details.
To pack with recording item details:
1. Perform Step 1 of Section E.[Link], "Packing Without Recording Item
Details".
2. The Scan Identifier screen displays, which enables you to enter or
scan the task list number. For more information about scanning the
task list number, see Section E.2.1.3, "Scanning the Task List
Number".
Q
If multiple shipments are found with the same task list number,
and if you scan a cart identifier, the Shipment Identifier screen
displays, which enables you to scan the cart location. For more
information about scanning the cart location, see Section E.2.1.4,
"Scanning the Cart Location".
In the Shipment Identifier screen:
– If you want to continue packing, choose Go. The Open
Container screen displays, which enables you to open a case
or a pallet. For more information about opening a new
container, see Section E.[Link], "Opening a Container".

Packing Using the Mobile Application 347

Pack Strategies

– To identify a new shipment for packing, choose Back. The Scan

Identifier screen displays. For more information about
scanning a task list number, see Section E.2.1.3, "Scanning
the Task List Number".
Q
Otherwise, the Open Container screen displays, which enables you
to open a case or a pallet. For more information about opening a
new container, see Section E.[Link], "Opening a Container".
3. In the Open Container screen:
Q
To pack in a pallet or case, choose Open Case or Open Pallet. The
Open Case or Open Pallet screen displays which enables you to
open a pallet or a case. For more information about opening a
case or a pallet, see Section E.[Link], "Opening a Case or a
Pallet".
Q
Choose Done to pack for a new shipment.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Scan Identifier screen displays. For more
information about scanning a task list number, see
Section E.2.1.3, "Scanning the Task List Number".
4. In the Open Case or Open Pallet screen, scan the container SCM or
choose Generate to pack in a case or a pallet. The SKU Entry screen
displays. For more information about scanning an item ID, see
Scanning an Item ID.
5. In the SKU Entry screen, choose Go to capture item details.
6. Repeat Step 3 through Step 5 to pack more containers for a
shipment.
7. Repeat Step 2 through Step 5 to pack more shipments.
8. After packing all the shipments, press F10 to go back to the main
menu.

Scanning an Item ID
In the SKU Entry screen:

348 Implementation Guide

 Pack Strategies

1. Scan the item ID.

2. Do either of the following:

Q
Choose Go.
– If there are more than one Inventory UOM, Product Class, or
Inventory Status associated with the item, the Select SKU
screen displays, which enables you to select the Inventory
UOM, Product Class, and Inventory Status of the item. For
more information about selecting the Inventory UOM, Product
Class, and Inventory Status, see Section E.2.6, "Selecting a
SKU".
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number. For
more information about scanning the serial number, see
Section E.6, "Scanning the Serial Number".

Note: You can also scan the serial number of an item in

the SKU Entry screen. The Serial Entry screen does not
appear.

– If you scan a serialized item with a secondary serial number,

the Secondary Serial Entry screen displays which enables you
to scan a secondary serial number. For more information about
scanning a secondary serial number, see Section E.2.7,
"Scanning the Secondary Serial Number".

Packing Using the Mobile Application 349

Pack Strategies

Note: If you scan a serial-tracked item with a secondary

serial number in the SKU Entry screen, the Secondary
Serial Entry screen does not appear.

– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– Otherwise, the Quantity Entry screen displays, which enables
you to enter quantity of items packed in a container. For more
information about scanning quantity, see Section E.10,
"Scanning the Quantity".
Q
Choose Close Cntr. The Open Container screen displays, which
enables you to open a new container for packing. For more
information about opening a container, see Section E.[Link],
"Opening a Container".

Table 22–1 Criteria Parameters

Field Description
Item ID Enter or scan the item ID of the item. You can also
scan the UPC Case Code of the item.

Table 22–2 Barcode Types

Field Barcode Type
Item ID ItemOrInventoryContainer

E.[Link] Opening a Container

In the Open Container screen, do either of the following:

350 Implementation Guide

 Pack Strategies

Q
Choose Open Case or Open Pallet to pack in a case or a pallet.
The Open Case or Open Pallet screen displays, which enables you
to open a new case or pallet for packing. For more information
about opening a case, see Section E.[Link], "Opening a Case or
a Pallet".

Q
Choose Done.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Scan Identifier screen displays. For more
information about scanning a task list number, see
Section E.2.1.3, "Scanning the Task List Number".

Table 22–3 Criteria Parameters

Fields Description
Shipment # Shipment to be packed.
Instructions Instructions associated with pack.

Packing Using the Mobile Application 351

Pack Strategies

Note: The instructions displayed contain a maximum of

twenty characters.

E.[Link] Opening a Case or a Pallet

In the Open Case or Open Pallet screen:
1. Scan the carton or pallet SCM and press tab or choose Generate if
you want the system to generate a SCM.
Q
If you are packing without recording item details, the Open
Container screen displays, which enables you to open a new
container for packing. For more information about opening a
container, see Section E.[Link], "Opening a Container".
Q
Otherwise, the SKU Entry screen displays, which enables you to
scan an item ID. For more information about scanning an item ID,
see Scanning an Item ID.

Table 22–4 Criteria Parameters

Fields Description
Shipment # Shipment number to be packed.
Carton SCM Enter or scan the carton or pallet SCM of the carton to
be packed.

352 Implementation Guide

 Pack Strategies

Table 22–5 Barcode Types

Field Barcode Type
Carton SCM CartonSCMscan

Note: If you are packing partially or completely unpacked

containers for a shipment and you have scanned an
outbound container SCM as a task list identifier in the Scan
Identifier screen, the scanned container SCM is suggested
in the Open Case or Open Pallet screen.

E.2.1.2 System-Directed Packing

In this type of pack, the system suggests containers for packing.
In System-Directed Pack, the packer can pack by capturing the item
details. This section explains the System-Directed Pack.
Figure 22–11 illustrates the Shipment-Driven, System-Directed Packing.
Figure 22–12 illustrates capturing item attributes.

Packing Using the Mobile Application 353

Pack Strategies

Figure 22–11 Shipment-Driven, System-Directed Packing

354 Implementation Guide

 Pack Strategies

Figure 22–12 Capturing Item Attributes

Packing Using the Mobile Application 355

Pack Strategies

E.[Link] Packing With the User Recording Item Details

The Mobile Application enables you to record item details while packing.
To pack by recording item details:
1. Perform Step 1 of Section E.[Link], "Packing Without Recording Item
Details".
2. The Scan Identifier screen displays, which enables you to enter or
scan the task list number. For more information about scanning the
task list number, see Section E.2.1.3, "Scanning the Task List
Number".
Q
If multiple shipments are found with the same task list number,
and if you scan a cart identifier, the Shipment Identifier screen
displays, which enables you to scan the cart location. For more
information about scanning the cart location, see Section E.2.1.4,
"Scanning the Cart Location".
Q
If there are any instructions associated with the shipment, the
Instructions screen displays. For more information about viewing
instructions, see Section E.2.5, "Viewing Instructions".
Q
Otherwise, the Container Entry screen displays which enables you
to scan a container SCM. For more information about scanning
container SCM, see Scanning the Container SCM.
3. In Container Entry screen, scan the container SCM and press Go. The
SKU Entry screen displays which enables you to scan an item ID. For
more information about scanning a SKU, see Scanning a SKU.
4. In the SKU Entry screen:
Q
Choose Go to continue capture item details for the shipment.
Q
Choose Close Cntr if you have done a short picking for the item.
5. Repeat Step 3 through Step 4 to pack more containers for a
shipment.
6. Repeat Step 2 through Step 4 to pack more shipments.
7. After packing all the shipments, press F10 to go back to the main
menu.

356 Implementation Guide

 Pack Strategies

Scanning the Container SCM

To scan Container SCM:
1. In the Container Entry screen, scan the container SCM.

2. Do either of the following:

Q
Choose Go. The SKU Entry screen displays, which enables you to
scan an item ID. For more information about scanning a SKU, see
Scanning a SKU.
Q
Choose Back.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Scan Identifier screen displays. For more
information about scanning a task list number, see
Section E.2.1.3, "Scanning the Task List Number".

Table 22–6 Criteria Parameters

Fields Description
Container Size System suggested container size.
Container SCM Enter or scan the container SCM.

Packing Using the Mobile Application 357

Pack Strategies

Table 22–7 Barcode Types

Field Barcode Type
Container SCM CartonSCMscan

Note: If you are packing partially or completely unpacked

containers for a shipment and you have scanned an
outbound container SCM as a task list identifier in the Scan
Identifier screen, the scanned container SCM is suggested
in the Container Entry screen.

Scanning a SKU
In the SKU Entry screen,
1. Scan the item ID.

2. Do either of the following:

Q
Choose Go.
– If there are more than one Inventory UOM, Product Class, or
Inventory Status associated with the item, the Select SKU
screen displays, which enables you to select the Inventory
UOM, Product Class, and Inventory Status of the item. For
more information about selecting the Inventory UOM, Product

358 Implementation Guide

 Pack Strategies

Class, and Inventory Status, see Section E.2.6, "Selecting a

SKU".
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number. For
more information about scanning the serial number, see
Section E.6, "Scanning the Serial Number".

Note: You can also scan the serial number of an item in

the SKU Entry screen. The Serial Entry screen does not
appear on choosing Go.

– If you scan a serialized item with a secondary serial number,

the Secondary Serial Entry screen displays which enables you
to scan a secondary serial number. For more information about
scanning a secondary serial number, see Section E.2.7,
"Scanning the Secondary Serial Number".

Note: If you scan a serial-tracked item with a secondary

serial number in the SKU Entry screen, the Secondary
Serial Entry screen does not appear on choosing Go.

– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the item scanned is a normal item, or if quantity of items
packed is recorded, the Quantity screen displays, which
enables you to scan the quantity. For more information about
scanning quantity, see Section E.10, "Scanning the Quantity".
– If you want to pack more items in the same container, the SKU
Entry screen displays.

Packing Using the Mobile Application 359

Pack Strategies

Q
Choose Close Cntr.
– If there are more containers to be packed for the shipment,
the Container Entry screen displays, which enables you to
scan a new container for packing. For more information about
scanning the container SCM, see Scanning the Container SCM.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Scan Identifier screen displays which enables
you to scan a task list number. For more information about
scanning the task list number, see Section E.2.1.3, "Scanning
the Task List Number".

Note: Choosing Close Cntr indicates that the container is

packed with number of units less than the suggested
number of units of items. The status of the container
changes to 'Short Picked'.

Table 22–8 Criteria Parameters

Fields Description
Item ID ID and description of the item.
When performing a single-level LPN packing, enter or
scan the item ID of an item. You can also scan the
UPC Case Code of the item.
When performing multi-level LPN packing, enter or
scan the case ID of the case to be packed for a
shipment.
Pack Qty Number of units of item to be packed.

Table 22–9 Barcode Types

Field Barcode Type
Item ID ItemOrInventoryContainer

360 Implementation Guide

 Pack Strategies

E.2.1.3 Scanning the Task List Number

To scan the task list number:
1. In the Scan Identifier screen, scan the task list number.

2. Choose Go.
Q
When performing a Shipment-Driven, User-Directed Pack:
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Open Container screen displays, which enables
you to open a new container to perform packing. For more
information about opening a container, see Section E.[Link],
"Opening a Container".
Q
When performing a Shipment-Driven, System-Directed Pack:
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– If there are instructions to be viewed for the shipment, the
Instructions screen displays, which enables you to view
instructions. For more information about viewing instructions,
see Section E.2.5, "Viewing Instructions".

Packing Using the Mobile Application 361

Pack Strategies

– Otherwise, the Container Entry screen displays which enables

you to scan a container SCM. For more information about
scanning container SCM, see Scanning the Container SCM.
Table 22–10 Criteria Parameters
Field Description
Task List # Enter or scan the shipment number, tote ID, batch
number, pallet ID or case ID, or the multi sort cart ID.
Enter or scan an outbound container SCM if you are
packing partially or completely unpacked container for
a shipment.

Table 22–11 Barcode Types

Field Barcode Type
Task List # TaskListScan

Note: The Sterling Warehouse Management System

recommends that you use Shipment-Driven Packing to
pack partially or completely unpacked containers for a
shipment.

E.2.1.4 Scanning the Cart Location

To scan the cart location:
1. In the Shipment Identifier screen, scan the cart location associated
with the shipment.

362 Implementation Guide

 Pack Strategies

2. Do either of the following:

Q
Choose Go.
When performing a Shipment-Driven, User-Directed pack:
– The Open Container screen displays, which enables you to
open a new container to perform pack. For more information
about opening a container, see Section E.[Link], "Opening a
Container".
When performing a Shipment-Driven, System-Directed pack:
– If there are instructions to be viewed for the shipment, the
Instructions screen displays, which enables you to view
instructions. For more information about viewing instructions,
see Section E.2.5, "Viewing Instructions".
– Otherwise, the Container Entry screen displays, which enables
you to scan container SCM. For more information about
scanning a container SCM, see Scanning the Container SCM.
Q
Choose Back. The Scan Identifier screen displays, which enables
you to scan the task list number. For more information about
scanning task list number, see Section E.2.1.3, "Scanning the Task
List Number".

Table 22–12 Criteria Parameters

Field Description
Cart Location Enter or scan the cart location associated with the
shipment being packed.

Packing Using the Mobile Application 363

Pack Strategies

Table 22–13 Barcode Types

Field Barcode Type
Cart Location CartLocation

E.2.2 Item-Driven Packing

In this case, the shipment to be packed is identified using item details of
an item belonging to that shipment. Once the shipment is identified, it is
packed.
Item-Driven packing is further categorized into User-Directed Packing
and System-Directed Packing.

Note: Multi-level container packing is not supported in

Item-Driven Packing.

E.2.2.1 User-Directed Packing

In this type of packing, the packer selects the appropriate container for
packing. The packer can pack shipments containing only one item.
There are two ways of performing this type of packing:
Q
Packing With the System Identifying Item Details
Q
Packing With the User Recording Item Details
Figure 22–13 illustrates the Item-Driven, User-Directed Packing.
Figure 22–14 illustrates capturing item attributes.

364 Implementation Guide

 Pack Strategies

Figure 22–13 Item-Driven, User-Directed Packing

Packing Using the Mobile Application 365

Pack Strategies

Figure 22–14 Capturing Item Attributes

366 Implementation Guide

 Pack Strategies

E.[Link] Packing With the System Identifying Item Details

In this type of packing, the system automatically identifies the details of
the items.
To perform packing with system recording item details:
1. From the Menu page, select Pack SKU and press Enter. The Pack
screen displays, which enables you to scan the pack location. For
more information about scanning the pack location, see
Section E.2.3, "Scanning a Pack Location".
Q
If there is more than one pack station associated with a pack
location, the Select Pack Station screen displays, which enables
you to select the appropriate pack station. For more information
about selecting a pack station, see Section E.2.4, "Selecting a
Pack Station".
2. The Pack SKU screen displays, which enables you to scan an item ID,
pallet, or case to pack. For more information about scanning an item
ID, pallet, or case, see Section E.2.2.3, "Scanning a Pallet, Case, or
Item ID".
Q
If a pallet or case is scanned and you want to capture the item in
it, the SKU Entry screen displays, which enables you to scan an
item ID. For more information about scanning an item ID, see
Section E.2.2.4, "Scanning a SKU".

Packing Using the Mobile Application 367

Pack Strategies

Note: When an item is scanned in the Pack SKU screen or

the SKU Entry screen, the shipment to which the item
belongs is identified using the Shipment barcode source.
The system also displays an appropriate message if there
are no shipments found for the scanned item in the pack
station.

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>
Q
Set the value for the MandateSKUScan attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

Note: You can also scan the serial number of an item in

the Pack SKU screen if the item is present as a loose SKU
at the pack location.
You can also scan a 2D barcode in the Item, Case, or Pallet
field. If a 2D barcode is captured in the SKU field, the
information present as a part of the barcode is not
captured again and relevant screens do not appear.
For example, if a tag-tracked item with lot number "L" has
tag information from the barcode translation that the item
belongs to lot "L", the Tag Entry window does not display.

Q
If the item has more that one Inventory UOM, Product Class, or
Inventory Status, the Select SKU screen displays, which enables

368 Implementation Guide

 Pack Strategies

you to select the UOM, Product Class, and Inventory Status of an

item. For more information about selecting the UOM, Product
Class, and Inventory Status of an item, see Section E.2.6,
"Selecting a SKU".
Q
If there are any instructions for the pack, the Instructions screen
displays, which enables to view instructions related to packing.
For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
3. The Create New Cntr screen displays, which enables you to scan a
container SCM. For more information about scanning container SCM,
see Section E.[Link], "Creating a New Container".
4. Follow Step 3 of Section E.[Link], "Packing With the User Recording
Item Details" if Mobile Application asks you to enter item details.
5. Repeat Step 3 to pack more containers for a shipment.
6. Repeat Step 2 through Step 3 to pack more shipments.
7. After packing for all the shipments, press F10 to go back to the main
menu.

Note: The inventory sorted in a container is packed in an

outbound container for the shipment. When you press
Open Case or Open Pallet in the Open Container screen
after packing the inventory for the shipment, empty
containers are generated for the shipment.

Packing Using the Mobile Application 369

Pack Strategies

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to enable the
system to record item details automatically:
Q
In the Applications Manager, copy and save the
rfpackshpmt resource. The following displays in the
Java Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value>.
Set the value for the AutoRecordContents attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

E.[Link] Packing With the User Recording Item Details

In this type of packing, you can record item details.
To pack by recording item details:
1. Perform Step 1 of Section E.[Link], "Packing With the System
Identifying Item Details".
2. The pack SKU screen displays, which enables you to scan an item ID,
pallet, or case to pack. For more information about scanning an item
ID, pallet, or case, see Section E.2.2.3, "Scanning a Pallet, Case, or
Item ID".
Q
If a pallet or case is scanned and you want to capture the item in
it, the SKU Entry screen displays, which enables you to scan an
item ID. For more information about scanning an item ID, see
Section E.2.2.4, "Scanning a SKU".

370 Implementation Guide

 Pack Strategies

Note: When an item is scanned in the Pack SKU screen or

the SKU Entry screen, the shipment to which the item
belongs is identified using the Shipment barcode source.
The system also displays an appropriate message if there
are no shipments found for the scanned item in the pack
station.

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>
Q
Set the value for the MandateSKUScan attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

Q
If the item has more than one Inventory UOM, Product Class, or
Inventory Status, the Select SKU screen displays, which enables
you to select the UOM, Product Class, and Inventory Status of an
item. For more information about selecting the UOM, Product
Class, and Inventory Status of an item, see Section E.2.6,
"Selecting a SKU".
Q
If there are any instructions for packing, the Instructions screen
displays, which enables to view instructions related to packing.
For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
3. The Create New Cntr screen displays, which enables you to scan a
container SCM. For more information about scanning container SCM,
see Section E.[Link], "Creating a New Container".
In the Create New Cntr screen:

Packing Using the Mobile Application 371

Pack Strategies

Q
To pack in a new case or a pallet, choose New Case or New Pallet.
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number of the
item. For more information about scanning the serial number,
see Section E.6, "Scanning the Serial Number".

Note: You can also scan the serial number of an item in

the Pack SKU screen if it is present as loose SKU in the
pack location. For more information about scanning a serial
number in the Pack SKU screen, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".

– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– Otherwise, the Quantity Entry screen displays, which enables
you to scan the quantity. For more information about scanning
quantity, see Section E.10, "Scanning the Quantity".
Q
To identify a new shipment to pack, choose Done.
– If a pallet or case is scanned and you want to capture the item
in it, the SKU Entry screen displays, which enables you to scan
an item ID. For more information about scanning an item ID,
see Section E.2.2.4, "Scanning a SKU".
– Otherwise, the pack SKU screen displays, which enables you
to scan an item ID, pallet, or case to pack. For more
information about scanning an item ID, pallet, or case, see
Section E.2.2.3, "Scanning a Pallet, Case, or Item ID".
4. Repeat Step 3 to pack more containers for a shipment.
5. Repeat Step 2 through Step 3 to pack more shipments.

372 Implementation Guide

 Pack Strategies

6. After packing for the entire shipments, press F10 to go back to the
main menu.

Confirming the Pack

In the Confirm Pack screen, do either of the following:

Q
Choose Continue Pack to pack more items for a shipment.
– If there is a tag attribute with the item, the Tag Entry screen
displays, which enables you to scan the tag attribute of the
item. For more information about scanning the tag attribute,
see Section E.8, "Scanning the Tag Attribute".
– If there is an expiration date with the item, the Expiry Date
Entry screen displays, which enables you to scan the
expiration date of the item. For more information about
scanning the expiration date, see Section E.9, "Scanning the
Expiration Date".
– Otherwise, the Quantity Entry screen displays, which enables
you to scan the quantity. For more information about scanning
quantity, see Section E.10, "Scanning the Quantity".
Q
Choose Close Container if you have completed packing for a
container. The Create New Cntr screen displays, which enables
you to pack in a new case or pallet. For more information about

Packing Using the Mobile Application 373

Pack Strategies

scanning container SCM, see Section E.[Link], "Creating a New

Container".

Table 22–14 Criteria Parameters

Fields Description
Container SCM SCM of the container being packed.
Item ID ID of the item being packed.
Qty Placed Number of units of item placed in a container.

E.[Link] Creating a New Container

To create a new container:

1. In the Create New Cntr screen, scan Container SCM and press tab.
Q
If the item has a serial number, the Serial Entry screen displays,
which enables you to scan the serial number of the item. For
more information about scanning the serial number, see
Section E.6, "Scanning the Serial Number".
Q
If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For more
information about scanning the tag attribute, see Section E.8,
"Scanning the Tag Attribute".

374 Implementation Guide

 Pack Strategies

Q
If the item has an expiration date, the Expiry Date Entry screen
displays, which enables you to scan the expiration date of the
item. For more information about scanning the expiration date,
see Section E.9, "Scanning the Expiration Date".
Q
Otherwise, the Quantity Entry screen displays, which enables you
to scan the quantity. For more information about scanning
quantity, see Section E.10, "Scanning the Quantity".
2. Do either of the following:
Q
Choose New Case or New Pallet if you want to pack in a case or
pallet.
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number of the
item. For more information about scanning the serial number,
see Section E.6, "Scanning the Serial Number".
– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– Otherwise, the Quantity screen displays, which enables you to
scan the quantity. For more information about scanning
quantity, see Section E.10, "Scanning the Quantity".
Q
Choose Done.
– If a pallet is scanned and there are more items in the pallet to
be packed, the SKU Entry screen displays, which enables you
to scan an item ID. For more information about scanning a
SKU, see Section E.2.2.4, "Scanning a SKU".

Packing Using the Mobile Application 375

Pack Strategies

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>
Q
Set the value for the MandateSKUScan attribute to 'Y.'
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

– Otherwise, the Pack SKU screen displays, which enables you

to scan a new pallet, case, or item ID. For more information
about scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".

Table 22–15 Criteria Parameters

Fields Description
Shipment # Shipment to be packed.
Item ID ID and description of the item to be packed.
Pack Qty The number of units of item to be packed.
Container SCM Enter or scan the container SCM.

Table 22–16 Barcode Types

Field Barcode Type
Container SCM CartonSCMscan

E.2.2.2 System-Directed Packing

In this type of packing, the system suggests containers for packing.

376 Implementation Guide

 Pack Strategies

In System-Directed Packing, the packer can pack shipments containing

only one item. The packing is done by user recording item details.
Figure 22–15 illustrates the Item-Driven, System-Directed Packing.
Figure 22–16 illustrates capturing item attributes.

Packing Using the Mobile Application 377

Pack Strategies

Figure 22–15 Item-Driven, System-Directed Packing

378 Implementation Guide

 Pack Strategies

Figure 22–16 Capturing Item Attributes

Packing Using the Mobile Application 379

Pack Strategies

E.[Link] Packing With the User Recording Item Details

In this type of pack, you can record item details.
To perform pack by recording item details:
1. From the Menu page, select Pack SKU and press Enter. The Pack
screen displays, which enables you to scan the pack location. For
more information about scanning the pack location, see
Section E.2.3, "Scanning a Pack Location".
Q
If there is more than one pack station associated with a pack
location, the Select Pack Station screen displays, which enables
you to select the appropriate pack station. For more information
about selecting a pack station, see Section E.2.4, "Selecting a
Pack Station".
2. The Pack SKU screen displays, which enables you to scan an item ID,
pallet, or case to pack. For more information about scanning an item
ID, pallet, or case, see Section E.2.2.3, "Scanning a Pallet, Case, or
Item ID".
Q
If a pallet or case is scanned and you want to capture the item in
it, the SKU Entry screen displays, which enables you to scan an
item ID. For more information about scanning an item ID, see
Section E.2.2.4, "Scanning a SKU".

380 Implementation Guide

 Pack Strategies

Note: When an item is scanned in the Pack SKU screen or

the SKU Entry screen, the shipment to which the item
belongs is identified using the Shipment barcode source.
The system also displays an appropriate message if there
are no shipments found for the scanned item in the pack
station.

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>
Q
Set the value for the MandateSKUScan attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

Q
If the item has more than one Inventory UOM, Product Class, or
Inventory Status, the Select SKU screen displays, which enables
you to select the UOM, Product Class, and Inventory Status of an
item. For more information about selecting the UOM, Product
Class, and Inventory Status of an item, see Section E.2.6,
"Selecting a SKU".
Q
If there are any instructions for packing, the Instructions screen
displays, which enables to view instructions related to packing.
For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
3. The Container Entry screen displays, which enables you to scan a
container SCM. For more information about scanning a container
SCM, see Section E.[Link], "Scanning a Container SCM".
In the Container Entry screen:

Packing Using the Mobile Application 381

Pack Strategies

Q
To continue packing, choose Go.
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan a serial number. For more
information about scanning a serial number, see Section E.6,
"Scanning the Serial Number".

Note: You can also scan the serial number of an item in

the Pack SKU screen if it is present as loose SKU in the
pack location. For more information about scanning a serial
number in the Pack SKU screen, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".

– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the quantity of items packed is recorded, the Quantity
screen displays, which enables you to scan the quantity. For
more information about scanning quantity, see Section E.10,
"Scanning the Quantity".
– If there are more containers to be packed for the shipment,
the Container Entry screen displays.
– If a pallet or case is scanned and you want to capture the item
in it, the SKU Entry screen displays, which enables you to scan
an item ID. For more information about scanning an item ID,
see Section E.2.2.4, "Scanning a SKU".
– The Pack SKU screen displays, which enables you to scan an
item ID, pallet, or case to pack. For more information about
scanning an item ID, pallet, or case, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
4. Repeat Step 3 to pack more containers for a shipment.

382 Implementation Guide

 Pack Strategies

5. Repeat Step 2 through Step 3 to pack new shipment.

6. After packing all shipments, press F10 to go back to main menu.

E.[Link] Scanning a Container SCM

To scan a container SCM:
1. In the Container Entry screen, scan the container SCM.

2. In the Container Entry screen:

Q
Choose Go to continue pack for the shipment.
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan a serial number. For more
information about scanning a serial number, see Section E.6,
"Scanning the Serial Number".

– If the item has a tag attribute, the Tag Entry screen displays,
\

which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".

Packing Using the Mobile Application 383

Pack Strategies

– If you have scanned the UPC Case Code of an item in the Pack
SKU or SKU Entry screen, which has quantity of items greater
than the shipment quantity, or if the quantity of items packed
is recorded, the Quantity screen displays, which enables you
to scan the quantity. For more information about scanning
quantity, see Section E.10, "Scanning the Quantity".
Q
Choose Cancel to pack a new shipment. The Pack SKU screen
displays, which enables you to pack a pallet, case, or item ID. For
more information about scanning a pallet, case, or item ID, see
Section E.2.2.3, "Scanning a Pallet, Case, or Item ID".

Table 22–17 Criteria Parameters

Fields Description
Container Size System suggested container size.
Pack Qty The number of units of item to be packed.
Container SCM Enter or scan the container SCM.

Table 22–18 Barcode Types

Field Barcode Type
Container SCM CartonSCMscan

E.2.2.3 Scanning a Pallet, Case, or Item ID

To scan a pallet, case, or item ID:
1. In the Pack SKU screen, scan the item ID, pallet ID, case ID, UPC
Code, or UPC Case Code of the item.

384 Implementation Guide

 Pack Strategies

2. Choose Go.
Q
If a multi-SKU pallet is scanned or if you have mandated to
capture the SKU when a single-SKU pallet is scanned, the SKU
Entry screen displays, which enables you to scan an item ID. For
more information about scanning a SKU, see Section E.2.2.4,
"Scanning a SKU".
Q
If there are any instructions for the packing, the Instructions
screen displays, which enables to view instructions related to
packing. For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
Q
Otherwise, either of the following screens displays:
– When performing an Item-Driven, User-Directed Pack, the
Create New Cntr screen displays, which enables you to scan a
container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Creating a New
Container".
– When performing an Item-Driven, System-Directed Pack, the
Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Scanning a Container
SCM".

Packing Using the Mobile Application 385

Pack Strategies

Table 22–19 Criteria Parameters

Field Description
Item ID, Pallet or Case Enter or scan the item ID, pallet ID, case ID, UPC
Code, or UPC Case Code of the item to be packed.

Table 22–20 Barcode Types

Field Barcode Type
Item ID/Case/Pallet ItemorInventoryContainer

386 Implementation Guide

 Pack Strategies

Note: You can also scan a 2D barcode in the Item, Case,

or Pallet field. If a 2D barcode is captured in the SKU field,
the information present as a part of the barcode is not
captured again and relevant screens do not appear.
For example, if a tag-tracked item with lot number "L" has
tag information from the barcode translation that the item
belongs to lot "L", the Tag Entry window does not display.

Note: If you have scanned the UPC Case Code or 2D

barcode of an item, the system will suggest only those
shipments to pack, in which the quantity of item is less
than or equal to the scanned UPC Case Code or 2D
barcode quantity.

Troubleshooting Tip:
Problem
When you scan the identifier of a pallet or item in the Scan
Identifier field, an "Task type for Pack process is not
configured" error message displays.
Cause
A task type is not configured under the "Packing" activity
group.
Resolution
Configure at least one task type under the "Packing"
activity group.

E.2.2.4 Scanning a SKU

In the SKU Entry screen:
1. Scan the item ID, UPC Code, or the UPC Case Code of the item.

Packing Using the Mobile Application 387

Pack Strategies

2. Choose Go.
Q
If there are more than one Inventory UOM, Product Class, or
Inventory Status associated with the item, the Select SKU screen
displays, which enables you to select the Inventory UOM, Product
Class, and Inventory Status of the item. For more information
about selecting the Inventory UOM, Product Class, and Inventory
Status, see Section E.2.6, "Selecting a SKU".
Q
If there are any instructions for the packing, the Instructions
screen displays, which enables to view instructions related to
packing. For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
Q
Otherwise, either of the following screens displays:
– When performing an Item-Driven, User-Directed Pack, the
Create New Cntr screen displays, which enables you to scan a
container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Creating a New
Container".
– When performing an Item-Driven, System-Directed Pack, the
Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Scanning a Container
SCM".

388 Implementation Guide

 Pack Strategies

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>.
Q
Set the value for the MandateSKUScan attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

Note: You can also scan a 2D barcode in the Item, Case,

or Pallet field. If a 2D barcode is captured in the SKU field,
the information present as a part of the barcode is not
captured again and relevant screens do not appear.
For example, if a tag-tracked item with lot number "L" has
tag information from the barcode translation that the item
belongs to lot "L", the Tag Entry window does not display.

Note: If you have scanned the UPC Case Code or 2D

barcode of an item, the system will suggest only those
shipments to pack, in which the quantity of item is less
than or equal to the scanned UPC Case Code or 2D bar
code quantity.

Table 22–21 Criteria Parameters

Field Description
Item ID Enter or scan the item ID, UPC Code, or the UPC Case
Code of the item to be packed.

Packing Using the Mobile Application 389

Pack Strategies

Table 22–22 Barcode Types

Field Barcode Type
Item ID Item

Note: When performing Item-Driven Packing:

If you have used item pick tasks to pick items and deposit
the picked items in the pack location, at least one item
pick task should be completed, in order to identify the
shipment to be packed on scanning the item.
In case of split pick tasks, where you have used an item
pick task to deposit the picked items in a staging location
and order pick tasks are generated from the staging
location to the pack location, the shipment can be
identified only if the order pick tasks are completed.

E.2.3 Scanning a Pack Location

To scan a pack location:
1. In Pack screen, scan the pack location.

2. Choose Go.

390 Implementation Guide

 Pack Strategies

Q
If there is more than one pack station for the scanned pack
location, the Select Pack Station screen displays, which enables
you to select the pack station. For more information about
selecting the pack station, see Section E.2.4, "Selecting a Pack
Station".
Q
Otherwise, either of the following screens appear:
– When performing a Shipment-Driven Pack, the Scan Identifier
screen displays, which enables you to scan the task list
number. For more information about scanning the identifier,
see Section E.2.1.3, "Scanning the Task List Number".
– When performing an Item-Driven Pack, the Pack SKU screen
displays, which enables you to scan a pallet, case, or item ID.
For more information about scanning a pallet, case, or item
ID, see Section E.2.2.3, "Scanning a Pallet, Case, or Item ID".

Table 22–23 Criteria Parameters

Field Description
Pack Location Enter or scan the pack location.

Table 22–24 Barcode Types

Field Barcode Type
Pack Location Location

Note: You can also choose Go or press F3 without

scanning a pack location. The Select Pack Station screen
displays, which shows a list of all the pack stations.

E.2.4 Selecting a Pack Station

To select a pack station:
1. In the Select Pack Station screen, select required pack station ID
from the list and tab out.
Q
When performing Shipment-Driven Packing:

Packing Using the Mobile Application 391

Pack Strategies

The Scan Identifier screen displays, which enables you to scan the
task list number for the shipment. For more information about
scanning the task list number, see Section E.2.1.3, "Scanning the
Task List Number".
Q
When performing Item-Driven Packing:
The Pack SKU screen displays, which enables you to scan a pallet,
case, or item ID. For more information about scanning a pallet,
case, or item ID, see Section E.2.2.3, "Scanning a Pallet, Case, or
Item ID".

Table 22–25 Criteria Parameters

Field Description
Pack Station ID Select the appropriate pack station.

E.2.5 Viewing Instructions

To view instructions:
1. In the Instructions screen, press Ok after viewing the instructions.
Q
When performing Shipment-Driven, System-Directed Packing:
The Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning a
container SCM, see Scanning the Container SCM.
Q
When performing Item-Driven, User-Directed Packing:

392 Implementation Guide

 Pack Strategies

The Create New Cntr screen displays, which enables you to scan
the container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Creating a New
Container".
Q
When perforrming Item-Driven, System-Directed Packing:
The Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning the
container SCM, see Section E.[Link], "Scanning a Container
SCM".

Table 22–26 Criteria Parameters

Field Description
Shipment # Shipment to be packed.
Instructions Shipment instructions associated with pack.

Note: The instructions displayed contain a maximum of

twenty characters.

E.2.6 Selecting a SKU

To select the UOM, Product Class, and Inventory Status of an item:
1. In the Select SKU screen, select the UOM, Product Class, and
Inventory Status for an item.

Packing Using the Mobile Application 393

Pack Strategies

2. Choose Go.
Q
When performing Shipment-Driven, User-Directed packing:
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number. For
more information about scanning the serial number, see
Section E.6, "Scanning the Serial Number".
– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– Otherwise, the Quantity Entry screen displays, which enables
you to scan the quantity. For more information about scanning
quantity, see Section E.10, "Scanning the Quantity".
Q
When performing Shipment-Driven, System-Directed packing:
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number. For

394 Implementation Guide

 Pack Strategies

more information about scanning the serial number, see

Section E.6, "Scanning the Serial Number".
– If the item has a tag attribute, the Tag Entry screen displays,
which enables you to scan the tag attribute of the item. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the quantity of items packed is recorded, the Quantity
screen displays, which enables you to scan the quantity. For
more information about scanning quantity, see Section E.10,
"Scanning the Quantity".
– Otherwise, the SKU Entry screen displays, which enables you
to scan an item ID. For more information about scanning an
item ID, see Scanning a SKU.
Q
When performing Item-Driven, User-Directed packing:
– If there are any instructions for packing, the Instructions
screen displays, which enables to view instructions related to
pack. For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
– Otherwise, the Create New Cntr screen displays, which
enables you to scan a container SCM. For more information
about scanning a container SCM, see Section E.[Link],
"Creating a New Container".
Q
When performing Item-Driven, System-Directed packing:
– If there are any instructions for packing, the Instructions
screen displays, which enables to view instructions related to
pack. For more information about viewing instructions, see
Section E.2.5, "Viewing Instructions".
– Otherwise, the Container Entry screen displays, which enables
you to scan the container SCM. For more information about
scanning the container SCM, see Section E.[Link], "Scanning
a Container SCM".

Packing Using the Mobile Application 395

Pack Strategies

E.2.7 Scanning the Secondary Serial Number

To scan the secondary serial number:
1. In the Secondary Serial screen, scan the secondary serial number.

2. Choose Go. The Serial Entry screen displays, which enables you to
scan a new serial. For more information about scanning the serial
number, see Section E.6, "Scanning the Serial Number".

Table 22–27 Criteria Parameters

Fields Description
Item ID ID and description of the item.
Serial # The serial number of the item.
Secondary Serial # Enter or scan the secondary serial number associated
with the serial.

396 Implementation Guide

 Pack Verification

Note: The Secondary Serial screen displays on scanning

the primary serial number only if the item is a serialized
item and has a secondary serial number.

E.3 Pack Verification

Pack verification can be done in any one or combination of the following
ways:
Q
By confirming the presence of the packed container in the pack
location.
Q
By comparing the total number of units of items in the container
with the value of the total number of units of items in the system.
Q
By comparing the total number of different items present in the
container with the value of the total number of items in the
system.
Q
By scanning each item and comparing the item details.
Figure 22–17 illustrates the Pack Verification process.

Packing Using the Mobile Application 397

Pack Verification

Figure 22–17 Pack Verification

398 Implementation Guide

 Pack Verification

Packing Using the Mobile Application 399

Pack Verification

Note: To verify packing, the VERIFY_PACK transaction is

provided. This transaction has two events:
VERIFICATION_DONE and DISCREPANCY_FOUND.
Whenever a pack verification process is completed
successfully, the VERIFICATION_DONE event is raised. This
event generates an XML that contains details of the
successfully verified pack containers. The details provided
in the XML are container location, container SCM, container
type, and the shipment to which the container belongs.
Whenever there is any mismatch found during the pack
verification process, the DISCREPANCY_FOUND event is
raised. This event generates an XML that contains details
of the container for which the mismatch is found. The
details provided in the XML are the container location,
container SCM, container type, pipeline key, shipment to
which the container belongs, item ID, product class, UOM,
quantity of an item verified in the container, and serial or
tag number of an item.

400 Implementation Guide

 Pack Verification

Note: To extend the Verify Pack functionality provided by

the Sterling Warehouse Management System:
Q
In the Applications Manager, copy and save the
rfverifypack resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packverify/[Link]?ConfirmCo
ntainerPresence=<Value>&VerifyTotalQty=<Value>&Ve
rifyItemCount=<Value>&DetailVerification=<Value>&V
alidateContainerPickUpStatus=<Value>&StopOnFirstMi
smatch=<Value>
Q
Set the values for the ConfirmContainerPresence,
VerifyTotalQty, VerifyItemCount, DetailVerification,
ValidateContainerPickUpStatus, and
StopOnFirstMismatch attributes. The default value of
ConfirmContainerPresence, VerifyItemCount, and
DetailVerification is 'Y'. The default value of
VerifyTotalQty, ValidateContainerPickUpStatus, and
StopOnFirstMismatch is 'N'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

Packing Using the Mobile Application 401

Pack Verification

Note: The behavior of the system when the

ConfirmContainerPresence, VerifyTotalQty,
VerifyItemCount, and DetailVerification parameters are set
to 'Y' or 'N' is as follows:
Q
The Mobile Application asks you to verify the container
location if ConfirmContainerPresence is set to 'Y'.
Otherwise, you are not asked to verify the container
location.
Q
The Mobile Application asks you to verify the total
number of units in the container if VerifyTotalQty is set
to 'Y'. Otherwise, you are not asked to verify total
quantity of units in the container.
Q
The Mobile Application asks you to verify the total
number of items present in the container if
VerifyItemCount is set to 'Y'. Otherwise, you are not
asked to verify the total number of items in the
container.
Q
The Mobile Application asks you to verify each item and
its details if DetailVerification is set to 'Y'. Otherwise,
you are not asked to verify each item and its details.
By default, the Mobile Application asks you to verify the
container location, total number of items in the container,
and each item with its details.

You can verify packing for innermost containers only.

To verify packing:
1. From the Menu page, select Verify Pack and press Enter.
Q
If pack verification is done by confirming the presence of the
packed container in the pack station, the Location Entry screen
displays, which enables you to scan a location. For more
information about scanning a location, see Section E.5, "Scanning
a Location".
Q
Otherwise, the Container Entry screen displays, which enables you
to scan the container SCM. For more information about scanning
the container, see Section E.7, "Scanning the Container SCM".

402 Implementation Guide

 Pack Verification

Note: When verifying the packing, if you scan a location

for a container, and the container location in the system
does not match with the location you scanned, the system
automatically changes the system value of the container
location to the location you scanned.

2. In the Container Entry screen, scan the container SCM and choose
Go.
Q
If pack verification is done by scanning the total number of units
of items in the container, the Quantity Confirmation screen
displays, which enables you to scan the total quantity. For more
information about scanning the total quantity, see Section E.3.1,
"Confirming the Quantity".
Q
If pack verification is done by scanning the number of items in the
container, the SKU Count screen displays, which enables you to
scan the number of items. For more information about scanning
the total number of items, see Section E.3.3, "Scanning the
Number of SKUs".
Q
If pack verification is done by scanning each item in the container,
the SKU Entry screen displays, which enables you to scan the
item ID. For more information about scanning the item ID, see
Section E.3.5, "Scanning a SKU".
3. Repeat Step 2 to verify packing for more containers.
4. After verifying the packing of all shipments in a location, with or
without verifying container presence, press F10 to go back to the
main menu.

Packing Using the Mobile Application 403

Pack Verification

Note: If you want the pack verification process as a part

of the container pipeline, add the VERIFY PACK transaction
to your container pipeline. Also, set the value of the
ValidateContainerPickUpStatus parameter to 'Y' as follows:
Q
In the Applications Manager, copy and save the
rfverifypack resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packverify/[Link]?ConfirmCo
ntainerPresence=<Value>&VerifyTotalQty=<Value>&Ve
rifyItemCount=<Value>&DetailVerification=<Value>&V
alidateContainerPickUpStatus=<Value>&StopOnFirstMi
smatch=<Value>.
Q
Set the value of ValidateContainerPickUpStatus to 'Y'.
This enables the system to ensure that the container is in
a valid pickup status for the VERIFY PACK transaction to
pick up. If there is any change in the drop status of the
transaction, the container status is updated to the new
status.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

E.3.1 Confirming the Quantity

To confirm the quantity:
1. In the Quantity Confirmation screen, scan the total quantity in the
container.

404 Implementation Guide

 Pack Verification

2. Choose Go.
Q
If there is a mismatch between the system quantity and the
quantity scanned by you, the Qty Mismatch screen displays, which
enables you to handle the quantity mismatch. For more
information about handling the quantity mismatch, see
Section E.3.2, "Handling the Quantity Mismatch".
Q
If you scan without any mismatch and if pack verification is done
by scanning the number of items in the container, the SKU Count
screen displays, which enables you to scan the number of items.
For more information about scanning the total number of items,
see Section E.3.3, "Scanning the Number of SKUs".
Q
If you scan without any mismatch and if pack verification is done
by scanning each item in the container, the SKU Entry screen
displays, which enables you to scan the item ID. For more
information about scanning the item ID, see Section E.3.5,
"Scanning a SKU".
Q
Otherwise, the Container Entry screen displays, which enables you
to scan the container SCM. For more information about scanning
the container SCM, see Section E.7, "Scanning the Container
SCM".

Table 22–28 Criteria Parameters

Field Description
Total Qty in Cntr Enter or scan the total number of units of items.

Packing Using the Mobile Application 405

Pack Verification

E.3.2 Handling the Quantity Mismatch

To handle the quantity mismatch:
1. In Qty Mismatch screen, view the quantity mismatch message.

2. Choose Done or Rescan. The Container Entry screen displays, which

enables you to scan the container SCM. For more information about
scanning the container SCM, see Section E.7, "Scanning the
Container SCM".

Table 22–29 Criteria Parameters

Field Description
Qty Entered The total number of units of all items you scanned.

E.3.3 Scanning the Number of SKUs

To scan the number of SKUs:
1. In the SKU Count screen, scan the number of SKUs.

406 Implementation Guide

 Pack Verification

2. Choose Go.
Q
If there is a mismatch between the system SKU count and the
count scanned by you, the SKU Count Mismatch screen displays,
which enables you to handle the SKU count mismatch. For more
information about handling the SKU count mismatch, see
Section E.3.4, "Handling the SKU Count Mismatch".
Q
If you scan without any mismatch and if pack verification is done
by scanning each item in the container, the SKU Entry screen
displays, which enables you to scan the item ID. For more
information about scanning the item ID, see Section E.3.5,
"Scanning a SKU".
Q
Otherwise, the Container Entry screen displays, which enables you
to scan the container SCM. For more information about scanning
container SCM, see Section E.7, "Scanning the Container SCM".

Table 22–30 Criteria Parameters

Field Description
Number of SKUs Enter or scan the total number of items in the
container.

E.3.4 Handling the SKU Count Mismatch

To handle the SKU count mismatch:
1. In the SKU Count Mismatch screen, view the message for SKU count
mismatch.

Packing Using the Mobile Application 407

Pack Verification

2. Choose Done or Rescan. The Container Entry screen displays, which

enables you to scan the container SCM. For more information about
scanning the container SCM, see Section E.7, "Scanning the
Container SCM".

Table 22–31 Criteria Parameters

Field Description
No. of SKU The total number items you scanned.
System Count The total number of items registered in the system.

E.3.5 Scanning a SKU

To scan a SKU, in the SKU Entry screen, do either of the following:
Q
Scan the item ID and choose Go.

408 Implementation Guide

 Pack Verification

Q
If pack verification is done by scanning the item details and if the
item is a normal item, the Quantity Entry screen displays, which
enables you to scan the quantity of an item inside a container. For
more information about scanning quantity, see Section E.10,
"Scanning the Quantity".
Q
If pack verification is done by scanning the item details and if the
item is a serial-tracked or a serialized item, the Serial Entry
screen displays, which enables you to scan the serial number of
the item. For more information about scanning the serial number,
see Section E.6, "Scanning the Serial Number".
Q
If pack verification is done by scanning the item details and if the
item is tag-tracked, the Tag Entry screen displays, which enables
you to scan the tag attribute. For more information about
scanning the tag attribute, see Section E.8, "Scanning the Tag
Attribute".
Q
If pack verification is done by scanning the item details and if the
item is a time-sensitive item, the Expiry Date screen displays,
which enables you to scan the expiration date. For more
information about scanning the expiration date, see Section E.9,
"Scanning the Expiration Date".
Q
If you have scanned a wrong item ID and if you set have the
value of the StopOnFirstMismatch to 'Y' to capture mismatch after
every item scan, the Mismatch screen displays. For more
information about handling mismatch, see Section E.3.6,
"Handling the Mismatch".

Packing Using the Mobile Application 409

Pack Verification

Note: You can configure the Mobile Application to show

mismatches after the first mismatch. To see the
mismatches:
Q
In the Applications Manager, copy and save the
rfverifypack resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packverify/[Link]?ConfirmCo
ntainerPresence=<Value>&VerifyTotalQty=<Value>&Ve
rifyItemCount=<Value>&DetailVerification=<Value>&V
alidateContainerPickUpStatus=<Value>&StopOnFirstMi
smatch=<Value>
Q
Set the value of DetailVerification and
StopOnFirstMismatch parameters to 'Y'.
If the StopOnFirstMismatch parameter is set to 'Y', the
verification happens after every item and its details are
captured. If there is any mismatch after you scan each
item, upon clicking 'Done' the pack verification process
fails for the container. The Container Entry screen displays,
which enables you to carry out pack verification for
another container. For more information about scanning
the container SCM, see Section E.7, "Scanning the
Container SCM".
If the StopOnFirstMismatch parameter is not set to 'N',
then all the discrepancies found for each item are captured
through the process. The validation in this case happens
after you have scanned all the items and click 'Done' in the
SKU Entry screen. If there is a mismatch through the
process, the Mismatch screen displays, which shows an
error message. For more information about handlinging the
mismatch, see Section E.3.6, "Handling the Mismatch".
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

Q
Choose Verification Done if you have scanned all the SKUs in the
container.

410 Implementation Guide

 Pack Verification

The Container Entry screen displays, which enables you to scan the
container SCM. For more information about scanning the container
SCM, see Section E.7, "Scanning the Container SCM".

Table 22–32 Criteria Parameters

Field Description
Item ID Enter or scan the item ID.

Table 22–33 Barcode Types

Field Barcode Type
Item ID ItemorOutboundCarton

E.3.6 Handling the Mismatch

To handle the mismatch:
1. In the Mismatch screen, view the mismatch found between the
system and the details you scanned.

2. Do either of the following:

Q
Choose Rescan or Done. The Container Entry screen displays,
which enables you to scan the container SCM. For more
information about scanning the container SCM, see Section E.7,
"Scanning the Container SCM".

Packing Using the Mobile Application 411

Unpacking

Table 22–34 Criteria Parameters

Field Description
Item ID ID and description of the item packed.
Qty Scanned Total number of units of item scanned.

Note: The Mismatch screen shows appropriate mismatch

messages. For example, when there is a mismatch in the
quantity of a serial-tracked or a serialized item, a message
for the serial-tracked or serialized item is displayed.
The Mismatch screen displays after every item scan only if
the 'StopOnFirstMismatch' parameter is set to 'Y'.

E.4 Unpacking
You can unpack containers using the Mobile Application. This section
explains the unpacking process using the Mobile Application.
Figure 22–18 illustrates the Unpacking process.

412 Implementation Guide

 Unpacking

Figure 22–18 Unpacking

Packing Using the Mobile Application 413

Unpacking

To unpack using the Mobile Application:

1. From the Menu page, select Unpack and press Enter. The Location
Entry screen displays, which enables you to scan an unpack location.
For more information about scanning the location, see Section E.5,
"Scanning a Location".
2. The Container Entry screen displays, which enables you to scan the
SCM of the container that you want to unpack. For more information
about scanning the container SCM, see Section E.7, "Scanning the
Container SCM".

Note: When unpacking, if you scan a location for a

container, and if the container location in the system does
not match with the location you scanned, the system
automatically changes the system value of the container
location to the location you scanned.

3. The Unpack Criteria screen displays, which enables you to scan the
carton SCM for a child carton or the item you want to unpack. For
more information about scanning the unpack criteria, see
Section E.4.1, "Scanning the Unpack Criteria".
In the Unpack Criteria screen:
Q
To record item details, choose Go.
– If an item is scanned and the item has a serial number, the
Serial Entry screen displays, which enables you to scan the
serial number of the item. For more information about
scanning the serial number, see Section E.6, "Scanning the
Serial Number".
– If an item is scanned and it has multiple tag attributes, the
Tag Entry screen displays, which enables you to scan the tag
attribute of the item. For more information about scanning the
tag attribute, see Section E.8, "Scanning the Tag Attribute".
– If an item is scanned and it has multiple expiration dates, the
Expiry Date Entry screen displays, which enables you to scan
the expiration date of the item. For more information about
scanning the expiration date, see Section E.9, "Scanning the
Expiration Date".

414 Implementation Guide

 Unpacking

– If an item is scanned and the quantity of unpacked items is to

be captured, the Quantity Entry screen displays, which
enables you to scan the quantity. For more information about
scanning the quantity, see Section E.10, "Scanning the
Quantity".
Q
To unpack a new container, choose Done. The Container Entry
screen displays, which enables you to scan the SCM of the
container that you want to unpack. For more information about
scanning the container SCM, see Section E.7, "Scanning the
Container SCM".
4. Repeat Step 1 through Step 3 to unpack more containers.
5. After unpacking all containers, press F10 to go back to the main
menu.

Note: You can also perform an undo container build using

Unpack. You can remove selected cases from an
overpacked inventory or outbound container. To remove
cases from a container:
Q
In the Container Entry screen, enter or scan the parent
container SCM and choose Go. For more information
about scanning the container SCM, see Section E.7,
"Scanning the Container SCM".
Q
In the Unpack Criteria screen, enter or scan the child
case LPN you want to remove from the container and
choose Go. For more information about scanning the
unpack criteria, see Section E.4.1, "Scanning the
Unpack Criteria".
Q
If there is more than one child container in the parent
container, the Unpack Criteria screen displays. Enter or
scan the container SCM for the remaining child
containers. For more information about scanning the
unpack criteria, see Section E.4.1, "Scanning the
Unpack Criteria".

E.4.1 Scanning the Unpack Criteria

To scan the item ID or carton SCM to unpack:

Packing Using the Mobile Application 415

Unpacking

1. In the Unpack Criteria screen, scan the item ID or carton SCM.

2. Do either of the following:

Q
Choose Done if you unpacked a carton. The Container Entry
screen displays, which enables you to scan another container to
unpack. For more information about scanning a container SCM,
see Section E.7, "Scanning the Container SCM"
Q
Choose Go to record the item details.
– If the item has a serial number, the Serial Entry screen
displays, which enables you to scan the serial number. For
more information about scanning the serial number, see
Section E.6, "Scanning the Serial Number".
– If the item has multiple tag attributes, the Tag Entry screen
displays, which enables you to scan the tag attribute. For
more information about scanning the tag attribute, see
Section E.8, "Scanning the Tag Attribute".
– If the item has multiple expiration dates, the Expiry Date
Entry screen displays, which enables you to scan the
expiration date. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the quantity of unpacked items is to be captured, the
Quantity Entry screen displays, which enables you to scan the
quantity. For more information about scanning quantity, see
Section E.10, "Scanning the Quantity".

416 Implementation Guide

 Scanning a Location

Table 22–35 Criteria Parameters

Field Description
Item ID or Carton SCM Enter or scan the item ID or carton SCM to be
unpacked.

Table 22–36 Barcode Types

Field Barcode Type
Item ID/ Carton SCM ItemOrOutboundCarton

E.5 Scanning a Location

To scan a location:
1. In the Location Entry screen, scan the location ID.
2. Choose Go. The Container Entry screen displays. For more
information about scanning a container, see Section E.7, "Scanning
the Container SCM".

Table 22–37 Criteria Parameters

Field Description
Location ID Enter or scan the pack location.

Packing Using the Mobile Application 417

Scanning the Serial Number

Table 22–38 Barcode Types

Field Barcode Type
Location Id Location

E.6 Scanning the Serial Number

To scan the serial number:
1. In the Serial Entry screen, scan the serial number.

2. Choose Done.
Q
When performing Shipment-Driven, User-Directed Packing:
– If there is a secondary serial number with the item, the
Secondary Serial screen displays, which enables you to scan
the secondary serial number of the item. For more information
about scanning secondary serial number, see Section E.2.7,
"Scanning the Secondary Serial Number".
– Otherwise, the SKU Entry screen displays, which enables you
to scan a new item ID. For more information about scanning
an item ID, see Scanning an Item ID.
Q
When performing Shipment-Driven, System-Directed Packing:

418 Implementation Guide

 Scanning the Serial Number

– If you want to pack more items in the same container, the SKU
Entry screen displays, which enables you to scan the item ID.
For more information about scanning the item ID, see
Scanning a SKU.
– If you want to pack more containers for the shipment, the
Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning the
container SCM, see Scanning the Container SCM.
– Otherwise, the Scan Identifier screen displays, which enables
you to scan the task list number. For more information about
scanning task list number, see Section E.2.1.3, "Scanning the
Task List Number".
Q
When performing Item-Driven, User-Directed Packing:
– If you scan a serialized item with a secondary serial number,
the Secondary Serial Entry screen displays which enables you
to scan a secondary serial number. For more information about
scanning a secondary serial number, see Section E.2.7,
"Scanning the Secondary Serial Number".

Note: If you scan a serial-tracked item with a secondary

serial number, the Secondary Serial Entry screen does not
appear on choosing Done.

– If you want to pack more containers for the same shipment,

Container Entry screen displays, which enables you to scan a
container SCM. For more information about scanning the
container SCM, see Section E.[Link], "Creating a New
Container".
– If you have scanned a pallet or case and you want to scan
more items in it, the SKU Entry screen displays, which enables
you to scan the item ID. For more information about scanning
item ID, see Section E.2.2.4, "Scanning a SKU".

Packing Using the Mobile Application 419

Scanning the Serial Number

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>
Q
Set the value for the MandateSKUScan attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

– Otherwise, the Pack SKU screen displays, which enables you

to scan a pallet, case, or item ID. For more information about
scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
Q
When performing Item-Driven, System-Directed Packing:
– If you scan a serialized item with a secondary serial number,
the Secondary Serial Entry screen displays which enables you
to scan a secondary serial number. For more information about
scanning a secondary serial number, see Section E.2.7,
"Scanning the Secondary Serial Number".

Note: If you scan a serial-tracked item with a secondary

serial number, the Secondary Serial Entry screen does not
appear on choosing Done.

– If you want to pack more containers for the same shipment,

the Container Entry screen displays, which enables you to
scan container SCM. For more information about scanning
container SCM, see Section E.[Link], "Scanning a Container
SCM".

420 Implementation Guide

 Scanning the Serial Number

– If you have scanned a pallet or case and you want to scan

more items in it, the SKU Entry screen displays, which enables
you to scan the item ID. For more information about scanning
item ID, see Section E.2.2.4, "Scanning a SKU".

Note: To extend the pack functionality provided by the

Sterling Warehouse Management System to mandate SKU
scan in single-SKU or multi-SKU pallet or case:
Q
In the Applications Manager, copy and save the
rfpacksku resource. The following displays in the Java
Server Page (JSP) field:
/rf/ynw/packshpmt/[Link]?Au
toRecordContents=<Value> &
MandateSKUScan=<Value>
Q
Set the value for the MandateSKUScan attribute to 'Y'.
For more information about creating a new resource and
adding a new menu entry, see the Sterling Selling and
Fulfillment Foundation: Customization Guide.

– Otherwise, the Pack SKU screen displays, which enables you

to scan a pallet, case, or item ID. For more information about
scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
Q
When verifying the packing:
– If there is any mismatch between the item details scanned by
you and the item details in the system and if the
StopOnFirstMismatch is 'Y', the Mismatch screen displays,
which enables you to handle the mismatch. For more
information about handling mismatch, see Section E.3.6,
"Handling the Mismatch".
– If there is no mismatch between the item details scanned by
you and the item details in the system or if there is a
mismatch between the item details scanned by you and the
item details in the system, and the StopOnFirstMismatch is 'N',
the Serial Entry screen displays, which enables you to scan
more serials.

Packing Using the Mobile Application 421

Scanning the Container SCM

Note: If you scan a serial-tracked and tag-controlled,

serial-tracked and time-sensitive, serialized and
tag-controlled, or serialized and time-sensitive item in the
Serial Entry screen, the system does not ask you to scan
the tag attribute or the expiry date of the item.

Q
When unpacking:
– If there are more items to be unpacked for a container, the
Unpack Criteria screen displays, which enables you to scan an
item ID or carton SCM for the container. For more information
about scanning an item ID or carton SCM, see Section E.4.1,
"Scanning the Unpack Criteria".
– Otherwise, the Container Entry screen displays, which enables
you to scan a new container to be unpacked. For more
information about scanning container SCM, see Section E.7,
"Scanning the Container SCM".

Table 22–39 Criteria Parameters

Fields Description
Item ID ID and description of the item.
Serials to Scan Number of serials left to be scanned.
Serial # Enter or scan the serial number of the item.
# Serials Scanned Number of serials left to be scanned.

E.7 Scanning the Container SCM

To scan the container SCM:
1. In the Container Entry screen, scan the container SCM.

422 Implementation Guide

 Scanning the Container SCM

2. Choose Go.
Q
When verifying the packing:
– If the container is not present in the scanned location, an
error displays.
– If the pack verification is done by scanning the total units of
items in a container, the Quantity Confirmation screen
displays, which enables you to scan the total quantity. For
more information about scanning the total quantity, see
Section E.3.1, "Confirming the Quantity".
– If the pack verification is done by scanning the number of
different items in the container, the SKU Count screen
displays, which enables you to scan the number of items. For
more information about scanning the number of items, see
Section E.3.3, "Scanning the Number of SKUs".
– If the pack verification is done by capturing the item details,
the SKU Entry screen displays, which enables you to scan the
item ID. For more information about scanning the item ID, see
Section E.3.5, "Scanning a SKU".
Q
When unpacking:
The Unpack Criteria screen displays, which enables you to scan
the item ID or carton SCM that you want to unpack. For more

Packing Using the Mobile Application 423

Scanning the Tag Attribute

information about scanning the item ID or carton SCM, see

Section E.4.1, "Scanning the Unpack Criteria".
Table 22–40 Criteria Parameters
Field Description
Container SCM Enter or scan the container SCM.

Table 22–41 Barcode Types

Field Barcode Type
Container SCM OutboundContainer

E.8 Scanning the Tag Attribute

To scan the tag attribute:
1. In the Tag Entry screen, scan the tag attribute.

2. Choose Go.
Q
When performing Shipment-Driven, User-Directed Packing:
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".

424 Implementation Guide

 Scanning the Tag Attribute

– Otherwise, the Quantity screen displays, which enables you to

scan the quantity. For more information about scanning the
quantity, see Section E.10, "Scanning the Quantity".
Q
When performing Shipment-Driven, System-Directed packing:
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the quantity of items packed is recorded, the Quantity
screen displays, which enables you to scan the quantity. For
more information about scanning the quantity, see
Section E.10, "Scanning the Quantity".
– If there are more items to be packed for a container, the SKU
Entry screen displays, which enables you to scan an item. For
more information about scanning an item, see Scanning a
SKU.
– If you want to pack a new container, the Container Entry
screen displays, which enables you to scan the container SCM.
For more information about scanning the container SCM, see
Scanning the Container SCM.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Scan Identifier screen displays, which enables
you to enter or scan the task list number. For more
information about scanning the task list number, see
Section E.2.1.3, "Scanning the Task List Number".
Q
When performing Item-Driven, User-Directed Packing:
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".

Packing Using the Mobile Application 425

Scanning the Tag Attribute

– Otherwise, the Quantity screen displays, which enables you to

scan the quantity. For more information about scanning the
quantity, see Section E.10, "Scanning the Quantity".
Q
When performing Item-Driven, System-Directed Packing:
– If the item has an expiration date, the Expiry Date Entry
screen displays, which enables you to scan the expiration date
of the item. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the quantity of items packed is recorded, the Quantity
screen displays, which enables you to scan the quantity. For
more information about scanning the quantity, see
Section E.10, "Scanning the Quantity".
– If you have scanned a pallet or case and you want to pack
more items in it, the SKU Entry screen displays, which enables
you to scan the item ID. For more information about the
scanning item ID, see Section E.2.2.4, "Scanning a SKU".
– Otherwise, the Pack SKU screen displays, which enables you
to scan a pallet, case, or item ID. For more information about
scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
Q
When verifying the packing:
– If there is any mismatch between the item details scanned by
you and the item details in the system, and if the value of
StopOnFirstMismatch is 'Y', the Mismatch screen displays,
which enables you to handle the mismatch. For more
information about handling the mismatch, see Section E.3.6,
"Handling the Mismatch".
– If the item has an expiration date, the Expiry Date Entry
screen displays when there is no mismatch between the item
details scanned by you and the item details in the system. The
Expiry Date Entry screen also displays when there is a
mismatch between the item details scanned by you and the
item details in the system, and the value of
StopOnFirstMismatch is 'N'. The Expiry Date Entry screen
enables you to scan the expiration date. For more information

426 Implementation Guide

 Scanning the Tag Attribute

about scanning the expiration date, see Section E.9, "Scanning

the Expiration Date".
– If there is no mismatch between the item details scanned by
you and the item details in the system or if there is a
mismatch between the item details scanned by you and the
item details in the system, and the value of
StopOnFirstMismatch is 'N', the Container Entry screen
displays, which enables you to scan the container SCM. For
more information about scanning the container, see
Section E.7, "Scanning the Container SCM".
Q
When unpacking:
– If the item has multiple expiration dates, the Expiry Date
Entry screen displays, which enables you to scan the
expiration date. For more information about scanning the
expiration date, see Section E.9, "Scanning the Expiration
Date".
– If the quantity of unpacked items is to be captured, the
Quantity Entry screen displays, which enables you to scan the
quantity. For more information about scanning the quantity,
see Section E.10, "Scanning the Quantity".
– If capturing quantity is not required and if you have more
items to be unpacked for the container, the Unpack Criteria
screen displays, which enables you to scan the item ID or the
carton SCM. For more information about scanning the unpack
criteria, see Section E.4.1, "Scanning the Unpack Criteria".
– Otherwise, the Container Entry screen displays, which enables
you to scan a new container SCM to be unpacked. For more
information about scanning the container SCM, see
Section E.7, "Scanning the Container SCM".

Table 22–42 Criteria Parameters

Fields Description
Item ID ID and description of the item.
Lot # Enter or scan the tag attribute of the item. You can
scan other tag attributes in this field, like batch
number, and so forth.

Packing Using the Mobile Application 427

Scanning the Expiration Date

Note: YOu can scan other tag attributes in the Tag Entry
screen. If the tag-tracked item has a batch number, you
are asked to scan the batch number.

E.9 Scanning the Expiration Date

To scan the expiration date:
1. In the Expiry Date Entry screen, scan the expiration date.

2. Choose Go.
Q
When performing Shipment-Driven, User-Directed Packing, the
quantity of items packed is recorded, the Quantity screen
displays, which enables you to scan the quantity. For more
information about scanning the quantity, see Section E.10,
"Scanning the Quantity".
Q
When performing Shipment-Driven, System-Directed Packing:
– If the quantity of items packed is recorded, the Quantity
screen displays, which enables you to scan the quantity. For
more information about scanning the quantity, see
Section E.10, "Scanning the Quantity".
– If there are more items to be packed for a container, the SKU
Entry screen displays, which enables you to scan an item. For

428 Implementation Guide

 Scanning the Expiration Date

more information about scanning an item, see Scanning a

SKU.
– If you want to pack a new container, the Container Entry
screen displays, which enables you to scan the container SCM.
For more information about scanning the container SCM, see
Scanning the Container SCM.
– Otherwise, the Scan Identifier screen displays, which enables
you to enter or scan the task list number. For more
information about scanning the task list number, see
Section E.2.1.3, "Scanning the Task List Number".
– Otherwise, the Scan Identifier screen displays, which enables
you to enter or scan the task list number. For more
information about scanning the task list number, see
Section E.2.1.3, "Scanning the Task List Number".
Q
When performing Item-Driven, User-Directed Packing, the
Quantity screen displays, which enables you to scan the quantity.
For more information about scanning the quantity, see
Section E.10, "Scanning the Quantity".
Q
When performing Item-Driven, System-Directed Packing:
– If the quantity of items packed is recorded, the Quantity
screen displays, which enables you to scan the quantity. For
more information about scanning the quantity, see
Section E.10, "Scanning the Quantity".
– If you have scanned a pallet or case and you want to pack
more items in it, the SKU Entry screen displays, which enables
you to scan the item ID. For more information about scanning
the item ID, see Section E.2.2.4, "Scanning a SKU".
– Otherwise, the Pack SKU screen displays, which enables you
to scan a pallet, case, or item ID. For more information about
scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
Q
When verifying the packing:
– If there is any mismatch between the item details you scanned
and the item details in the system, and if the
StopOnFirstMismatch is 'Y', the Mismatch screen displays,
which enables you to handle the mismatch. For more

Packing Using the Mobile Application 429

Scanning the Quantity

information about handling the mismatch, see Section E.3.6,

"Handling the Mismatch".
– If there is no mismatch between the item details scanned by
you and the item details in the system or if there is a
mismatch between the item details scanned by you and the
item details in the system, and the value of
StopOnFirstMismatch is 'N', the Quantity Entry screen
displays, which enables you to scan the quantity. For more
information about scanning the quantity, see Section E.10,
"Scanning the Quantity".
Q
When unpacking:
– If the quantity of unpacked items is to be captured, the
Quantity Entry screen displays, which enables you to scan the
quantity. For more information about scanning the quantity,
see Section E.10, "Scanning the Quantity".
– If capturing quantity is not required and if you have more
items to be unpacked for the container, the Unpack Criteria
screen displays, which enables you to scan the item ID or the
carton SCM. For more information about scanning the unpack
criteria, see Section E.4.1, "Scanning the Unpack Criteria".
– Otherwise, the Container Entry screen displays, which enables
you to scan a new container SCM to be unpacked. For more
information about scanning the container SCM, see
Section E.7, "Scanning the Container SCM".

Table 22–43 Criteria Parameters

Fields Description
Item ID ID and description of the item.
Expiry Date Enter or scan the expiration date of the item in the
shown locale.

E.10 Scanning the Quantity

To scan the quantity:
1. In the Quantity Entry screen, scan the quantity of the items in a
container counted in inventory or alternate UOM.

430 Implementation Guide

 Scanning the Quantity

2. Choose Go.
Q
When performing Shipment-Driven, User-Directed Packing:
The SKU Entry screen displays, which enables you to scan the
same item or a new item ID for packing. For more information
about scanning an item ID, see Scanning an Item ID.
Q
When performing Shipment-Driven, System-Directed Packing:
– If there are more items to be packed in the same container,
the SKU Entry screen displays, which enables you to scan
more items. For more information about scanning the item ID,
see Scanning a SKU.
– If you have more containers to be packed for a shipment, the
Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning the
container SCM, see Scanning the Container SCM.
– If multiple shipments are found with the same task list
number, and if you scan a cart identifier, the Shipment
Identifier screen displays, which enables you to scan the cart
location. For more information about scanning the cart
location, see Section E.2.1.4, "Scanning the Cart Location".
– Otherwise, the Scan Identifier screen displays, which enables
you to enter or scan the task list number. For more

Packing Using the Mobile Application 431

Scanning the Quantity

information about scanning the task list number, see

Section E.2.1.3, "Scanning the Task List Number".
Q
When performing Item-Driven, User-Directed Packing:
– If there are more items to be packed for a shipment and if the
items have a tag attribute or an expiration date with them, the
Confirm Pack screen displays, which enables you to confirm
your pack. For more information about confirming pack, see
Confirming the Pack.
– If there are more containers to pack for the shipment, the
Create New Cntr screen displays, which enables you to scan
the container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Creating a New
Container".
– If you have scanned a pallet or case and you want to pack
more items in it, the SKU Entry screen displays, which enables
you to scan the item ID. For more information about scanning
the item ID, see Section E.2.2.4, "Scanning a SKU".
– Otherwise, the Pack SKU screen displays, which enables you
to scan a pallet, case, or item ID. For more information about
scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
Q
When performing Item-Driven, System-Directed Packing:
– If there are more containers to pack for the shipment, the
Container Entry screen displays, which enables you to scan
the container SCM. For more information about scanning a
container SCM, see Section E.[Link], "Scanning a Container
SCM"
– If you have scanned a pallet or case and you want to pack
more items in it, the SKU Entry screen displays, which enables
you to scan the item ID. For more information about scanning
the item ID, see Section E.2.2.4, "Scanning a SKU".
– Otherwise, the Pack SKU screen displays, which enables you
to scan a pallet, case, or item ID. For more information about
scanning a pallet, case, or item ID, see Section E.2.2.3,
"Scanning a Pallet, Case, or Item ID".
Q
When Verifying Pack:

432 Implementation Guide

 Scanning the Quantity

– If there is any mismatch between the number of units of an

item for a container entered by you and the number of units of
the item for a container in the system, and if the
StopOnFirstMismatch parameter is 'Y', the Mismatch screen
displays, which enables you to handle the mismatch. For more
information about handling the mismatch, see Section E.3.6,
"Handling the Mismatch".
– If there is no mismatch between the number of units of an
item for a container entered by you and the number of units of
the item for the container in the system or if there is a
mismatch between the number of units of an item for a
container entered by you and the number of units of the item
for a container in the system, and the StopOnFirstMismatch is
'N', the SKU Entry screen displays, which enables you to scan
an item ID. For more information about scanning an item ID,
see Section E.3.5, "Scanning a SKU".
Q
When Unpacking:
– If you have more items to be unpacked for the container, the
Unpack Criteria screen displays, which enables you to scan the
item ID or the carton SCM. For more information about
scanning unpack criteria, see Section E.4.1, "Scanning the
Unpack Criteria".
– Otherwise, the Container Entry screen displays, which enables
you to scan a new container SCM to be unpacked. For more
information about scanning a container, see Section E.7,
"Scanning the Container SCM".

Table 22–44 Criteria Parameters

Fields Description
Item ID ID and description of the item.
UOM Unit of Measure of the item.
Quantity Enter the quantity of items packed.
Quantity is expressed in terms of inventory or
alternate UOM of the item.
Total Total number of units of item packed.

Packing Using the Mobile Application 433

Scanning the Quantity

434 Implementation Guide

 F
Menu-Level Customization of the Mobile
Application

There are occasions when a warehouse needs to set up different menu

options for the Mobile Application to specify resource-level parameters
for different behaviors. For example, a new Pack Shipment menu is
created to enable automatic recording of item details in the container
being packed or a new Ad hoc move menu is created for a particular
activity code and activity group.
When customizing the Mobile Application, the JSPs and HTMLs are mostly
changed. Therefore, a new resource ID for the new customized version is
created. All the JSP and HTML files corresponding to the factory shipped
resource IDs are copied into new directories corresponding to the new
resource ID. These newly created directories are at the same level as the
old directories from which the JSP and HTML files are copied. The HTML
files are modified by replacing the occurrence of <resourceId>.ppc with
<new resourceId>.ppc. The new resource ID is then associated with a
new menu item.

F.1 Menu-Level Customization

When performing menu-level customizations, the JSP and HTML files are
not modified. The Sterling Warehouse Management System enables you
to create a new menu for the Mobile Application and associate it with a
new resource ID, without making copies of the JSP and HTML files.
The following sections explain how to avoid copying the JSP and HTML
files when performing menu-level customizations.

Menu-Level Customization of the Mobile Application 435

Menu-Level Customization

F.1.1 Avoiding Copying of HTML Files

To avoid copying of HTML files:
1. Save the factory-shipped resource with a new ID by adding a prefix
that ends with a hypen (-) to the old resource ID.
For example, to create a new Ad hoc move, save the resource
"manualmove" with a prefix "1-". The new resource ID is
"1-manualmove".
2. Create a new menu and associate the new resource ID with it.
This ensures that the newly created resource also accesses the same
HTML files accessed by the factory-shipped resource.

F.1.2 Avoiding Copying of JSP Files

To avoid copying of JSP files:
1. Save the factory-shipped resource with a new ID.
2. In the resource details, the JavaServerPage parameter appears.
Remove "/extn" from the JavaServerPage parameter.
3. Create a new menu and associate the new resource ID with it.
This ensures that the newly created resource also accesses the same JSP
files accessed by the factory-shipped resource.

436 Implementation Guide

 G
XML Integration SED

The XML generated by the system which is used to file the SED through
the third party integration has the following format.

Yo

Table 22–45 Mapping of SED Header Attributes

Attribute Name Description
ShipmentReferenceNo The transportation reference number.
FileSED SED can be filed only when this
attribute has the value Y.
ExportationDate The exportation date of the shipment.
OrderNo Concatenates the order number of all
the orders included in the shipment.
CustomerID Set to BuyerOrganizationCode if
available,
Otherwise set to Receiving Node.
Shipnode The ShipNode, shipping the shipment.
SellerOrganisationCode The SellerOrganizationCode.
SellerTaxPayer This attributes is set to Seller
Organization or Tax payerId.
EnterpriseCode The EnterpriseCode.
BuyerOrganisationCode The BuyerOrganizationCode.
ExportTaxPayerID The ExportTaxPayerID.

XML Integration SED 437

 Table 22–45 Mapping of SED Header Attributes
Attribute Name Description
PackageType Set the value of this atttribute to
PARCEL if CarrierType = PARCEL.
Else set to 'CARTON'.
FromAddressLine1 This attributes concatenates the first
name and last name of the USPPI, if
company name is not available.
FromAddressLine2 It concatenates AddressLine1 and
AddressLine2 of the USPPI.
FromAddres Line3 It concatenates the City, State, and Zip
Code of the USSPI.
FromCountry The country of the USSPI, from which
the shipments is shipped.
ToCountry The country of the Ultimate Destination,
to which the shipments is shipped.
Related It signifies whether parties to
transaction are related or not.
FromZip The ZipCode of the country of the
USSPI, from where the shipment is
shipped.
FromState The state of origin of USPPI.
Mode The method of transportation.
isNo Vessel It signifies whether the shipment is
containerized, it is always set to Y.
IsHazardous It signifies whether the shipment
contains the hazardous materials.
Export LicenceNo The licence number.

Table 22–46 Mapping of SED Detail Attributes

Attribute Name Description
ItemID The identifier of item
ItemDesc The description of the item

438 Implementation Guide

Table 22–46 Mapping of SED Detail Attributes
Attribute Name Description
UnitofMeasure The unit of measure of the item
UnitCost The cost per unit
CostCurrency The cost in U.S. dollars.
ExportType Set to D if the items is domestic or else set to F.
Schedule_B_Code It identifies the Schedule B number.
UnitWeight The unit weight of the item.
UnitWeightUOM The unit of measure of the unit weight.
QuantityWithUOM The quantity of the Schedule B units.
TotalCost The total cost in U.S. dollars.
TotalWeight The total shipping weight.

XML Integration SED 439

440 Implementation Guide
 Notices

This information was developed for products and services offered in the
U.S.A.
IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to
state or imply that only that IBM product, program, or service may be
used. Any functionally equivalent product, program, or service that does
not infringe any IBM intellectual property right may be used instead.
However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not grant you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS)
information, contact the IBM Intellectual
Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

441
 Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or
any other country where such provisions are inconsistent with
local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. Some states do
not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own
risk.
IBM may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged,
should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA__95141-1003

442 Implementation Guide

U.S.A.
Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that
these measurements will be the same on generally available systems.
Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products and cannot
confirm the accuracy of performance, compatibility or any other claims
related to non-IBM products. Questions on the capabilities of non-IBM
products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to
change or withdrawal without notice, and represent goals and objectives
only.
This information is for planning purposes only. The information herein is
subject to change before the products described become available. This
information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples
include the names of individuals, companies, brands, and products. All of
these names are ficticious and any similarity to the names and addresses
used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source
language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing,
using, marketing or distributing application programs conforming to the

443
 application programming interface for the operating platform for which
the sample programs are written. These examples have not been
thoroughly tested under all conditions. IBM, therefore, cannot guarantee
or imply reliability, serviceability, or function of these programs. The
sample programs are provided "AS IS", without warranty of any kind.
IBM shall not be liable for any damages arising out of your use of the
sample programs.
Each copy or any portion of these sample programs or any derivative
work, must include a copyright notice as follows:
© IBM 2011. Portions of this code are derived from IBM Corp. Sample
Programs.
© Copyright IBM Corp. 2011.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and [Link] are trademarks or registered
trademarks of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at “Copyright and trademark information” at
[Link]/legal/[Link].
Adobe, the Adobe logo, PostScript, and the PostScript logo are either
registered trademarks or trademarks of Adobe Systems Incorporated in
the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central
Computer and Telecommunications Agency which is now part of the
Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel
Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and
Pentium are trademarks or registered trademarks of Intel Corporation or
its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or both.

444 Implementation Guide

ITIL is a registered trademark, and a registered community trademark of
the Office of Government Commerce, and is registered in the U.S. Patent
and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment,
Inc. in the United States, other countries, or both and is used under
license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium and the Ultrium Logo are
trademarks of HP, IBM Corp. and Quantum in the U.S. and other
countries.
Connect Control Center®, Connect:Direct®, Connect:Enterprise,
Gentran®, Gentran:Basic®, Gentran:Control®, Gentran:Director®,
Gentran:Plus®, Gentran:Realtime®, Gentran:Server®,
Gentran:Viewpoint®, Sterling Commerce™, Sterling Information
Broker®, and Sterling Integrator® are trademarks or registered
trademarks of Sterling Commerce, Inc., an IBM Company.
Other company, product, and service names may be trademarks or
service marks of others.

445
446 Implementation Guide
 Index

A Productivity Purge, 40
Purge Corporate Count Request, 165
Abstract Transaction field, 62, 74, 83 Purge Count Request, 165
Action field, 62, 74, 83 Purge Receipt, 61, 279
activating AlertProNumberSetExpiration, 191 Purge Wave, 189
activating PrintLoadBOL, 190 Purge Work Order, 263
activities QC, 112
outbound, 188 Receipt Complete, 61, 263, 279
receiving, 53, 103 Release Wave, 189
VAS, 262 Sent To Node, 189
activity codes Synchronize Task Queue, 263
outbound, 188 Task History Purge, 41
receiving, 53, 103 Task Purge, 41
VAS, 262 Work Order Monitor, 263
activity demand Alert Pro Number Set Expiration service, 191
creating, 91 APIs Called field, 62, 74, 83
deleting, 96 application consoles node, 13
modifying, 94
AgentCriteriaGroup field, 83
agents
B
Assign Lane, 189 Base Document Type field, 62, 74, 83
Auto Accept Variance, 165, 166 base document types, 37
Batch Wave, 189 container, 37
Containerize Wave, 189 count, 37
count, 164 general, 37
Create Count Tasks, 164, 166 load, 37
Create Second Tasks, 164 order, 37
Create Third Count Tasks, 165 wave, 37
Create Variance Tasks, 164, 166 work order, 37
Create Wave, 189 Base Process Type field, 62, 74, 82
Execute Count Program, 164, 166 batch sheets, 242
Mine Productivity, 40 blind receipts, 49
Move Request Purge, 136, 244 BOL # field, 223
Print Wave, 189

1
BOL (Bill of Lading), 241, 242 customizing reference implementation data, 329
Buyer field, 222 customizing your node, 331
buyers, 13
D
C
deleting a node, 336
cart manifest batch sheet, 241 demand details
Case, 176 viewing, 213
catalog configurations, 17 disposition codes
categories, 17 setting up, 104
Change Shipment Status To Picked service, 190 associating for receipt with QC, 108
classifications, 17 associating with disposition transition
compliance service process status, 106
in a mobile application-based warehouse, 260 associating with inventory status, 107
in a paper-based warehouse, 261 associating with product class, 106
configurations creating disposition code, 105
count, 163 dock scheduling, 23
location mass maintenance, 73, 81 document type, 38
agents, 73, 82 blind, 38
location mass maintenance, 74, new, 38
document types, 37
82
Download File from MHE service, 192, 194
services, 75, 85
DownloadMHE server, 192
loc mass maint, 75, 85 DownloadToMHEQueue, 194
move request, 136 dynamic Item velocity
outbound, 185 calculating, 287
QC, 103 Dynamic Item Velocity Calculation
receiving, 53 Abstract Transaction field, 290
replenishment, 244 Action field, 291
returns, 271 AgentCriteriaGroup field, 291
VAS, 262 Alert ID field, 302
vendor compliance, 126 APIs Called field, 290
ContainerSCM, 422 Apply results from slotting field, 304
copying node configuration, 331 Apply Slotting action, 305
count, 143 Apply Slotting using the files generated on
calendar, 167 field, 306
flow Base Document Type field, 290
cycle count, 166 Base Process Type field, 290
program conditions, 167 Create Moves field, 304
request cancellation reasons, 167 End Time field, 302
strategy, 168 GetPendingJobs field, 291
count program, 166 No. of Items(in percentage) field, 301
customers, 13 Request Submitted by field, 302
customization Save results without applying field, 304
menu level, 435 ShipNodeKey field, 291

2 Implementation Guide
 Start Time field, 302 E
Status field, 302
Transaction ID field, 290 Electronic Data Interchange (EDI), 184
Transaction Name field, 290 electronic SED, 184
Type field, 302 hold type
Use Preference from the Selected Date as creating, 207
Default field, 306 electronic shipper’s export declaration process, 184
User Exit Called field, 290 enterprise, 13
Zone Description field, 304 Enterprise field, 222
Zone Id field, 304 environment variable
dynamic item velocity calculation, 287 YANTRA_HOME, xxx
agents YANTRA_OLD_HOME, xxx
attributes, 290 YFS_OLD_HOME, xxx
criteria parameters, 290 equipments, 24, 28
events raised, 291 equipments model, 24
calculating velocity code as a license plate, 24
forecasting data, 288 as a set of locations, 24
historical data, 288 Expected Ship Date field, 223
suggesting cutoff percentages, 288
configurations, 289 F
agents, 289
events, 292 favorites, 15
services, 292 FD (Factory Defects), 33
updating item statistics for pre-existing FedEx carrier label, 241, 242
shipments, 298 Finish No Later Than field, 224, 225, 226
Consider Current Year field, 299 FQ (First Quality), 33
Cumulative Percentage field, 301
Cut Off Percentage, 300
managing on warehouse floor, 298
G
applying saved results for slotting, 305 GeneratePutawayRequest service, 64, 280
selecting zones for slotting, 303 Get Shipment Item Statistics service
updating item velocity code, 302 activating, 294
viewing history, 301
viewing the Cumulative Item Percentage
graph, 300 H
setting time period, 298
History action, 299
Shipped, 299
hold type
Suggested CutOff Percentage, 300
creating, 206
Suggested CutOff% field, 302
Update Item Velocitty Code action, 299
Velocity Code field, 299 I
View Details action, 302
inbound rules configuration
receiving, 69
returns, 282

3
installing the Sterling Warehouse Management storage code, 22, 27
System storage preference, 17
default installation, 4 Location field, 224, 225, 226
with your configuration data, 4 locations, 22, 28
with your master data, 4 dock, 23
with your transaction data, 5 intransit, 23
inventory regular, 23
adjustment reason, 31 staging, 23
rules, 31 virtual, 23
status, 31 LTL carriers, 13
status transition
receiving, 60, 109, 278
M
rules configuration, 32
tracking attributes, 31 managing process on outbound floor
item, 17, 18 packing, 217
classification, 17 managing QC profile at the transaction level, 114
hierarchy, 17 managing the count process on the warehouse floor
use, 17 count, 166
ID, 17 managing the location mass maintenance process of
inventory rules, 17 the warehouse floor, 76, 85
performing location mass maintenance, 76, 85
K managing the outbound process on the warehouse
floor
kitting, 257 retrieval of pack and hold shipment, 222
process master catalogs, 17
in a mobile application-based master data location, 329
warehouse, 258 Material Safety Data Sheets (MSDS), 133
in a paper-based warehouse, 259 menu groups, 10, 15
service item configuration, 267 MHE (Material Handling Equipments), 171
MHE-based
pick process, 179
L
MHEIntegrationJMSServer, 194
Load Bill Of Lading (BOL), 185 minimum/maximum level triggers, 248
Load # field, 223 mobile application-based
loading count, 163
your own equipment, 330 move request process, 135
your own item, 329 receiving process, 50, 52
your own location, 330 replenishment process, 243
your own location inventory, 331 mobile application-based move request
your own master data, 329 process, 135
your own transaction data, 330 mobile application-based pick and pack
location process, 172
monitoring rules, 248 LTL/TL shipments, 174
size code, 21, 26 pick from forward pick area, 175
default, 26 pick to pallet process, 174

4 Implementation Guide
 parcel shipments, 172 selling and fulfilment foundation mobile
full case, 173 application, 340
less than case, 173 cart manifest pick using totes
mobile application-based receiving selling and fulfilment foundation mobile
opportunistic cross-docking process, 51 application, 340
model warehouse layout, 25 cart pick
move request, 135 paper-based, 340
cancellation reasons, 139 item-driven pack, 364
moving data from test bed to production, 336 scanning a pallet, case or item ID, 384
scanning a SKU, 387
item-driven pack, user-directed pack, 364
N
item-driven, system-directed pack, 376
No. of Cases field, 224 packing with the user recording item
No. of Pallets field, 224 details, 380
node, 21 scanning container SCM, 383
Node field, 222, 299 item-driven, user-directed pack
node receiving preferences, 70, 284 confirming pack, 373
Node Required field, 75, 83 creating new container, 374
Number of Records field, 75, 83 packing with the system recording
Number Of Shipment Lines field, 224 contents, 367
Number of Shipments field, 224 packing with the user recording contents, 370
packing based on containerization, 341
packing based on picking, 339
O pick using a pallet or case
off-boarding enterprises, 335 paper-based, 340
on-boarding enterprises, 331 pick using pallet
Order # field, 223 selling and fulfilment foundation mobile
outbound, 171 application, 340
activity constraints configuration, 232 scanning container SCM, 422
pick process pipeline, 185 scanning expiry date, 428
prints, 240 scanning lot number, 424
rules configuration, 171 scanning pack location, 390
scanning secondary serial number, 396
scanning serial number, 418
P scanning the quantity, 430
selecting a SKU, 393
pack and hold, 222 selecting pack station, 391
retrieval of pack and hold shipments from shipment-driven pack, 342
load, 225 scanning cart location, 362
pack and hold process, 183 scanning task list number, 361
pack and hold shipments, 183, 206 shipment-driven pack, system-directed
task generation, 205 pack, 353
creating hold type, 206 shipment-driven pack, user-directed pack
pack processes opening a case or pallet, 352
cart manifest pick opening a container, 350

5
 packing with the system recording item pick and pack process for LTL/TL
details, 346 shipments, 178
packing with the user recording contents, 347 pick process for LTL/TL shipments, 178
scanning an item ID, 348 receiving process, 269
shipment-driven, system-directed pack replenishment process, 244
packing with the user recording item parcel carriers, 13
details, 356 participant model, 12
scanning a SKU, 358 figure, 13
scanning container SCM, 357 participant modeling, 9
shipment-driven, user-directed pack, 342 participants, 9
packing without recording contents, 345 password, 14
strategies, 342 physical count
system-directed containerization, 341 estimating personnel requirements
understanding, 339 calculations for a warehouse with 15000
unpacking, 412 locations and one task for each
scanning unpack criteria, 415 location, 154
user-directed containerization, 341 pick exceptions, 232
verify pack, 397 pick location assignment configuration, 229
confirming quantity, 404 pipeline
handling the quantity mismatch, 406 count, 163
handling the SKU count mismatch, 407 cycle count, 164
scanning a location, 417 outbound
scanning a SKU, 408 container pipeline for cases, 186
scanning the number of SKUs, 406 container pipeline for outermost cases, 186
verifying pack container pipeline for pallets, 186
handling the mismatch, 411 shipment pipeline, 187
viewing instructions, 392 QC, 103
pack slip, 241, 242 receiving, 53
packing slip, 241, 242 returns, 271
pallet, 25 VAS, 262
pallet shrink wrap process, 175 PLA algorithm, 229
paper-based PLA (Pick Location Assignment), 229
full case pick and pack process for parcel Print Load BOL service, 190
shipments, 176 PrintMoveTickets service, 137, 138, 245, 246, 265
less than case pack process for parcel prints, 113
shipments, 178 count, 165
less than case pick and pack process for parcel full case pick, 241
shipments, 177 less than case pick, 241
less than case pick process for parcel mobile application-based
shipments, 177 LTL/TL shipments, 241
manifest process, 178 parcel shipments, 240
move request process, 136 paper-based
pack process for LTL/TL shipments, 179 parcel shipments, 242
parcel manifest process, 178 receiving, 67, 138, 246, 265
pick and pack process, 176 returns, 281

6 Implementation Guide
PRO # field, 223 cleaning up the inventory in vir-
PRO # generation logic, 13
tual locations, 149
process
compliance service, 259 searching shipments in open
count, 143 status, 150
cycle count, 143 searching staging locations,
kitting, 257
location mass maintenance, 73, 81
docks, and shipping
move request, 135 lanes, 148
outbound, 171 variance count process, 158
physical count, 144 QC, 101
canceling physical count, 162 receiving, 49
completing count tasks, 157 returns, 269
completing variance tasks, 159 vendor compliance, 125
configuration -level changes, 145 product class, 31
configuring new synchronous product management configurations, 17
productivity, 39
service, 146 count, 165
configuring prints, 147 outbound, 199
configuring task type receiving, 67, 138, 246, 265
configuration, 147 returns, 281
types, 41
creating pipeline-related purchase order, 37
configuration, 145 putaway preferences, 282
inventory adjustment-related move request, 139
QC, 110
configuration, 147
receiving, 69
count sheet-based counting process, 156
setting up, 56, 273
estimating personnel requirements for count
putaway strategy, 284
sheet data entry during physical
move request, 140
count, 154
receiving, 70
filling out count sheets, 157
getting started, 155
optimal batch sizes and configuration Q
considerations, 152
post physical count, 160 QC
preparing for a physical count, 145 configurations, 103
recording quantity on count sheets, 157 percentage, 103
reprinting count sheets, 159 putaway preference configuration, 123
running pre-physical inventory script, 151 QC (Quality Control), 101
transaction-level changes, 148 UI flow while receiving using ASN, 68, 121
UI flow while receiving using order, 119
cleaning up of the inventory in QC profile
staging, docks, and ship- creating, 114
ping lanes, 150 deleting, 118
modifying, 116

7
queue management, 11 product class, 33
queues, 11 productivity types, 41
QC, 122
receiving, 69
R
replenishment, 248
receipts returns, 282
with PO, 49 SAM definition, 43
without PO, 49 saved searches, 15
receiving stations, 30
disposition codes task types, 42
associating for receipt with QC, 59, 276 user groups and users, 14
associating with disposition transition VAS, 266
status, 58, 276 velocity codes, 28
associating with inventory status, 277 vendor compliance, 132
associating with product class, 58, 275 warehouse layout configuration, 25
creating disposition code, 57, 274 weigh scale, 29
setting up, 57, 274 zones and locations, 28
disposition configurations, 71 Register Task Completion service, 194
disposition setup, 71, 284 RegisterTaskCompletion API, 194
preferences replenishment, 243
setting up, 54, 271 process, 243
setting up enterprise-level, 54, 272 quantity, 248
setting up node-level, 54, 272 strategy, 244
receiving disposition codes replenishment quantity, 248
associating resource bundles, 337
with inventory resource demands
status, 59 shipments
moving, 214
receiving worksheet, 49
resource planning, 234
reference implementation, 3, 4
condition for task type association, 239
activity demand, 97
node planning attributes, 234
count, 166
resource pool, 234
devices, 29
task type associations, 238
equipments, 28
resource pools
inventory adjustment reasons, 34
capacity details
inventory status, 33
viewing, 212
inventory transitions, 35
standard capacity
items, 18
defining, 211
location size codes, 26
roles, 9
location storage codes, 27
menu groups, 15
move request, 139 S
outbound, 228
participant model, 12 s, 225
printers, 29 sales order, 37
SAM

8 Implementation Guide
 definition, 43 suppliers, 13
estimates, 43
SAM (Standard Allowable Minutes), 39
T
saved searches, 15
SED task generation for pack and hold shipments
electronic, 227 configuring activity constraints, 206
enter ITN, 227 task types
SED filing service, 197 count, 167
SED Hold Resolution service, 197 move request, 139
Seller field, 222 outbound, 230
service LTL/TL shipments, 231
YNW_GeneratePutawayRequestForWorkOrder_ paper-based picking, 231
73, 264 parcel shipments, 230
Service field, 223 productivity, 42, 45
services putaway, 70, 283
move request, 136 replenishment, 249
outbound, 190 TL carriers, 13
putaway shipment, 194 top-off replenishment triggers, 248
QC, 112 Total Volume (CIN) field, 224
receiving, 63, 279 Total Weight (LBS) field, 224
replenishment, 244 TRAILER # field, 223
retrieve pack and hold shipments, 195 transaction data, 315
send retrieve shipment request, 195 ASN-based receipt, 316
VAS, 264 inbound, 315
setting up the QC profile at the participant or catalog inventory, 316
level, 103 outbound, 317
shipment PO-based receipt, 316
groups, 228 shipment categories, 317
monitors, 199 shipment volumes, 317
selector, 228 transfer order shipments, 316
Shipment Mode field, 223 transaction data location, 331
shipper’s export declaration (SED), 184 Transaction ID field, 62, 74, 82
Show Graph action, 299 Transaction Name field, 62, 74, 82
slotting, 307 types of VAS services, 257
configurations, 310
integration, 308
interfacing with slotting engines, 308 U
reference implementation, 311 UCC 128 shipping label, 241, 242
integration strategy, 312 UI Flow
slotting engines, 307 confirming a work order, 266
standard devices, 29 creating a work order, 265
Start No Earlier Than field, 224, 225, 226 creating and authorizing returns, 281
stations, 24 UI flow
Sterling Network Warehouse Management System move tasks, 138
introduction, 3 mobile application, 138

9
 outbound, 210 W
confirming LTL/TL loads, 221
converting inventory container to outbound warehouse layout, 21
container warehouse layout configuration, 21
weigh station, 220 window, 105
manifesting parcel containers, 221
pack station, 217 Y
pallet shrink wrapping, 221
picking using batch sheets, 216 YANTRA_HOME, xxx
picking using MHE, 217 YANTRA_OLD_HOME, xxx
picking using mobile application, 215 YFS_OLD_HOME, xxx
replenishment YNW Cross Dock Inventory service, 65
mobile application, 247 YNW_Generate Putaway Request_75, 66
paper, 247 YNW_GeneratePutawayRequestForWorkOrder_73
VAS, 265 service, 264
UI flow while receiving using order, 67
unit of measure, 17 Z
Upload File to MHE service, 191
user, 10 zones, 22, 28
User Exits Called field, 62, 74, 83 (AES)
user group, 14 automated export system, 184
user groups, 10 (EDI)
users, 14 electronic data interchange, 184
(ITN)
V internal transaction number, 184
(USPPI)
VAS united states principal parties in interest, 184
activity constraints configuration, 268
compliance service item configuration, 268
execution process
mobile application-based compliance
service, 260
mobile application-based kitting, 258
paper-based compliance service, 261
paper-based kitting, 259
item configuration, 266
putaway strategy, 267
retrieval strategy, 267
VAS (Value-Added Services), 257
velocity codes, 22, 28
vendor compliance, 125
configurations, 126
vendors, 13

10 Implementation Guide
11
12 Implementation Guide