RedPrairie DSD Atlas V1.1

Warehouse
Management System

Project Atlas

Detailed Solution
Definition

Author: Elliott Stacey Issue Date: June 2016
Version: Version 1.10
Last Saved On: 20/11/2017 20:58:00

1 Document Owner and Contributors

Owning Team Author(s)
Logistics Implementation Elliott Stacey
Contributing Team Author
Configuration Lead Gerry Lyons

1.1 Document History

Author Date Version Comment
George Georgiou June 2010 Draft 10.0 Food RedPrairie V10.00 DSD
Elliott Stacey June 2016 Draft 1.0 Atlas Draft Issued for review
Elliott Stacey June 2016 Draft 1.1

1.2 Document Review

Name Position Action
Colin Smith Senior Project Manager I
Tony Butler D&T Senior Product Owner (Logistics/Online) I
Paul Lane Project Manager (Project Lead) IR
Kevin Lidstone Project Manager (Configuration Manager) FR
Derek Lewington Project Manager (Shire Lead) FR
Dave Kelly Project Manager (Bedford Lead) FR
Keith Bullock Project Support Manager (Training Lead) FR
Tony Woodman Project Support Manager (UAT Lead) FR
Gerry Lyons Project Support Manager (Config Lead) FR
Mark Morgan D&T Product Owner (Logistics) FR
Tony Nuttall D&T Subject Matter Expert (Logistics) IR

S = Signed Approval Required, QA, Quality Assurance Review Required, FR =
Formal Review Required, IR = Informal Review, I = For Information.

2

Contents

1 Document Owner and Contributors ................................................2

1.1 Document History ..............................................................................2
1.2 Document Review .............................................................................2

2 Introduction........................................................................................3
3 RedPrairie Setup and Administration .............................................4

3.1 Workstation Settings..........................................................................4

4 Warehouse Setup ...............................................................................5

4.1 Locations ...........................................................................................5
4.2 Work Zones .......................................................................................5
4.3 Pick Face Setup - SKU Putaway Group ............................................6
4.4 Address Maintenance – Managing Stores .........................................6

5 Pre-Advices .........................................................................................8
6 Orders ...............................................................................................12
7 Capacity Tool....................................................................................12

7.1 Capacity Management for IDTs .......................................................12

8 Wave Tool .........................................................................................13

8.1 Wave Tool Use ................................................................................13

9 Order Allocation ..............................................................................13

9.1 Allocation Algorithm .........................................................................13
9.2 Allocation Process ...........................................................................13

10 Clustering ......................................................................................15

10.1 Clustering Move Tasks ....................................................................15

11 Consignment Preparation............................................................19

11.1 Consignment ...................................................................................19
11.2 Consignment Drop...........................................................................20

12 Container Pick Assembly.............................................................20

12.1 Container and Pallet Label Printing .................................................20
12.2 Container Picking – via RF Device ..................................................21

13 SKU Management ........................................................................25

13.2 SKU .................................................................................................26
13.3 SKU Family Group...........................................................................27
13.4 Write Off Packs and Write On Singles for Online ............................27

2 Introduction

The purpose of this document is to highlight the main differences and explain
the changes made to the RedPrairie Warehouse Management System for
Project Atlas in Bedford and Shire Park.

3

3 RedPrairie Setup and Administration
3.1 Workstation Settings

3.1.1 Workstation
The options within the Workstation Menu allow the setup of Workstations
and Workstation Groups.

3.1.1.1 Workstation
Access via:
Administration  Workstation  Workstation

You can use this screen to look at the setup of Workstations.
There are now 4 setups of Workstation Group used in Bedford/Shire:
Truckmount – larger RDTs used on Reach trucks, Max pallets set as 1
Wearables – Used for all functions except Loading, Max pallets set as 1

4

Loading – Max Pallets set as 2 so multi-pallet handling enabled for Loading
and Decant Sequence is LIFO (Last In First Out – highest position pallet is
first marshalled)

BXRelocate – Identical to Wearables except that Relocation – SKU
Confirmation on RDTs is turned off in Workstation Group Function Access for
Bedford completing Ecomm New Relocates to Boxed Bin Locations.

4 Warehouse Setup

The Warehouse setup will be completed by the configuration team and is
explained in more detail within their documentation and release notes.

4.1 Locations

Within the RedPrairie solution there are different types of location. The
location type will depend on what the location is required to be used for.

Bin: Bin Type locations are used in the Bedford Hanging solution, and now for
Boxed inventory that doesn’t require a Pick Face & Replenishments from
Reserve. When inventory is put into them certain attributes of the inventory
are stripped off and removed i.e. Pallet, Container, Tag ID, Receipt ID, Line
ID, Supplier, Pre-Advice Supplier, Pre-Advice SCION PO. This means all the
inventory in a location for the same SKU is essentially the same and displays
on one Inventory line record, and that the Pallet/Container (trolley) number
can be used again.
e.g. Hanging - 1AA001A, HG1UPIIN, HGREPRO, HGREWRK

Boxed – EBOXED, BS010A01, BXREPRO

Receive Dock: Receive Dock Type Locations are the receipts areas. These
are the system locations that goods will be received into via Pre-Advice or UPI
Receiving.
e.g. HG1GDSIN, BX1GDSIN, ECOGDSIN

4.2 Work Zones

Boxed Ecomm Receipts we have added:
BX1ECZONE1 Boxed Ecomm Receipt Zone

For Shire Park Boxed Reserved – 11, 12, 13 in one chamber, 20 in the other

BXRV11 Boxed Reserve Zone 11

BXRV12 Boxed Reserve Zone 12

BXRV13 Boxed Reserve Zone 13

BXRV20 Boxed Reserve Zone 20

5

4.3 Pick Face Setup - SKU Putaway Group

Boxed & GM SKUs without a Pick Face have a Putaway Group of BOXED.
New lines due in for Shire Park Boxed should be assigned to a Fixed pick
location the night before they arrive.
Putaway group is the Location Zone (Aisle) of the Location of the Pick Face.
Every 15 minutes a script runs and interfaces a SKU Update to trigger the
SKU Merge Rule if the Location Location Zone (Aisle) of the Location of the
Pick Face does not match the current SKU Putaway Group, or if a Pick Face
No Longer Exists and the SKU Putaway Group needs setting back to BOXED.
The Merge Rule has now been updated so it will only set the Putaway Group
if it is like RACKPICK and so it doesn’t error if a SKU has multiple Pick Faces.
e.g. Data  Location  Pickface

Face Type = Fixed
Location = AC2400
Data  Location  Location
Location = AC2400
Location Zone = ACRACKPICK
Data  SKU  SKU
Putaway Group = ACRACKPICK

4.4 Address Maintenance – Managing Stores

This screen is used to manage the stores/warehouses that the depot service.
Access via:
Data  General  Setup  Address

6

By selecting the User Defined Tab the following screen is displayed.

4.4.1 Store Delivery Schedule and Lead Time
This 7 digit Store Delivery Schedule number (Store Delivery Date SMTWTFS)
in User Defined Note 1 and Lead Time in User Defined Note 2, are used by a
merge rule to calculate the Ship By Date, which determines the WorkGroup,
set on new order Headers as they interface in, or on unfulfilled Allocation
Orders that are recycled.
Bedford/Shire only pick 6 days a week, Monday to Saturday. A Sunday pick
day would require a change to the merge rules.
If a Store Delivery Schedule number is not entered e.g. on a newly added
store, the default is 1111111 which basically means the store is setup for
delivery everyday. So the orders will be available to Wave Plan and pick if
required, if not they can be Capacity Managed and will rollover to the next
day.
3 digit Address IDs for Address Type Warehouse can now be updated
with a Store Delivery Schedule and Lead Time like stores.
4.4.2 Eligible for Customer Group Linking
In order to see a store in the Customer Group Linking screen, to be able to
link it to a Customer Group for Capacity Management, this check box needs
to be ticked.
This flag will also be used to filter which stores should be shown in the Insight
Pallet Browser Customer dropdown menu.

7

5 Pre-Advices

A valid and open Pre-Advice must exist within the RedPrairie WMS in order
for inventory to be received into the WMS.
There are now several types of Pre-Advice:

Type Created by Pre-Advice UPI Example
Received
1. Master (PO) Interface Received 1610908
2. Real Manually X FMSKU2476157D41H
3a. IDT UPI Interface X 3002864406
(Normal Transfer)  X
3b. IDT UPI
(Ecomm Transfer) X 

Interface X  9000000336

5.1.1 IDT UPI Receipt Pre-Advice
These are now 2 types of Pre-Advice for IDTs.

3a. Interfaced in when a Normal IDT Transfer Order is raised in RMS,
Normal Transfers begin with a 3.

3b. Interfaced in when an Ecomm IDT Transfer is csv uploaded into RMS
for inventory ring-fenced for Online, Ecomm Transfers begin with a 9.

Both are 10 digits long, and in the Pre-Advice Header screen,
Miscellaneous, neither of the Master Pre-Advice check boxes will be
ticked.

A depot should never try to receive IDT UPI Receipt Pre-Advice
When the sending depot ships pallets for the corresponding order to the
receiving depot, a number of related UPI (Unique Pallet Identifier) records
are created. These should be received in using UPI Receive on the watch
which updates the IDT UPI Receipt Pre-Advice.

Merge Rules will set:
Pre-Advice Header Status to UPI RECEIVE
Pre-Advice Lines for IDTs to Qty Due Tolerance (%) = 0

8

5.1.2 Boxed Receipt
A large proportion of Bedford’s Boxed comes in loose (non-palletised).
Inbound Containers should be snake loaded with the same SKUs together.
Boxes are manually unloaded and stacked onto pallet boards.
Pallet boards must to be built with:

 Only 1 SKU to a pallet
 All of the same Type (Box Size) and
 With the same inner Box Quantity

Type: Enter the Pallet Type, this relates to the size of the box.
The first letter represents the foot print of the box, and the number the height.
Please note, the number of Box Types has increased from 21 to 71 and some
of the existing Box Type dimensions/volumes have changed.

9

If you have a Single Box for a SKU on a pallet, because it came in an odd
Type (Box Size) or has a different inner Box Qty to the rest of the SKU, you
can enter the Type as S to make the Putaway direct to the Pick face instead
of reserve.
5.1.3 Boxed Putaway Algorithm
Data  Algorithms  Putaway  Putaway Algorithm Setup
Group Algorithm – Lists all Putaway Groups
Below is an example of one Boxed Aisle Putaway Group and how it selects
the Location.

10

Destination Condition Rule
Code
Pick Face None If Pallet Type (Box Size) on Receipt is S (Single
None box) Top up Pick Face location
Pick Face None If Pick Face location is empty
Fanned Any Will attempt to put inventory in locations according
Putaway to the sequence in the Pick Face Profile below.
Same Aisle Any Will attempt to put inventory in Location Zone
(Aisle) by lowest available Putaway Seq on
Neighbouring Any Locations
Aisles Will attempt to go in neighbouring aisles,
alternating outwards from the original Location
IQ01 Zone (Aisle)
If it finds no where on the search algorithms above
it will be put to IQ01 in Location Zone BX1IQZONE
e.g. No Putaway Group on the SKU because a
Pick Face hasn't been assigned
In Bedford, if it finds no Pick Face from Location
ECOGDSIN it will put to EBOXED in Location
Zone BOXED

11

6 Orders

Before allocating orders against received inventory we need to run 2 tools:
 Capacity Maintenance
 Wave Maintenance

These are explained in their own sections below.
Normal IDT orders are raised in RMS as Type 02 Transfer Orders:
e.g. 3001234567, they start 300 but with no store/depot and no T at the end.
Ecomm IDT orders are csv uploaded into RMS as Type 02 Transfer Orders:
e.g. 9001234567, they start 900 but with no store/depot and no T at the end.
Order Header User Defined Transfer Type = ONLINE
Other ways of identifying IDT orders are:
Order IDs 10 long ??????????
Delivery Address Customer 3 long ???

7 Capacity Tool
7.1 Capacity Management for IDTs

The Capacity Management Tool should not be used on IDT Orders.
If it is and the Orders are Closed, they will need to be raised again in RMS.
To prevent this happening by accident, we have Customer Group Linked all
the 3 digit Warehouse Addresses to:
Customer Group: INTER DEPOT TRANSFER
Description: Do not Remove & Unlink Warehouses please
If they are removed, the Application Support Team will need to re-add them
using a db load.
Note: The Capacity Management Light filters out IDT orders and does not
display them already.

12

8 Wave Tool

8.1 Wave Tool Use

The Wave Tool was designed to group Orders into Waves for the Hanging
WCS Dürkopp Sorters in Bedford, however it can be used much the same for
Boxed only Orders in Shire Park.

It is recommended that we create similar size Waves to Bedford currently in
terms of number of stores/orders so that there are not volume and
performance issues i.e. please do NOT put all orders on 1 large wave to
Commit from Wave Summary or try to Allocate from RedPrairie.

Remember:
On Transport Plan Templates the 3 digit warehouses for IDTs are DIRECT
We should only Commit 1 Wave at a time from Wave Summary
When processing IDTs, don’t accidentally re-commit any of the Retail Waves

9 Order Allocation

9.1 Allocation Algorithm

For Boxed Bin Locations there was a requirement to allocate from the lowest
stock holding locations first instead of just by FIFO (First In First Out) so that
they would empty more locations quicker for new SKUs coming in. This has
been achieved by changing the following Configuration:
Data, Algorithms, Allocation, Allocation Algorithm Setup
Group Algorithm, Allocation Group - NOEXPIRY
Allocation by Creation Date by Zone *RACKPICK
Miscellaneous, Override FIFO / LIFO ticked (Y)

9.2 Allocation Process

The Allocation Screen will return any Order Headers that match the search
criteria e.g. Work Group, where the Order Header is not closed. The Status
will usually be Released as the Wave Tool has just updated it from Hold (but
could be Allocated, In Progress or Picked if it stopped part way through or
there were shortages on the order that can now be allocated).

Highlight all of the rows returned and press Next.
The best way of highlighting all orders is selecting a Header, then pressing
Ctrl+A together.

13

At the bottom of the screen it will display:
XXXX records, selected YYYYY orders, press the Next button to continue…
Ensure that XXXX = YYYY so you know you haven’t missed highlighting any
of the Order Header rows for allocation (like shown below, where 264 out of
265 Orders are selected, because one has been missed).

If XXXX = 3000:

a) Check you entered a Work Group (Wave) and have not left this blank.
b) If you’ve entered the Work Group (Wave) correctly, then there may be over
3000 orders for one wave and there are a few options:

1. Short-term, to return less records so you can highlight and allocate
them all; first run your Allocation against the 3000. When this
completes the majority of the Order Headers will change to a Status of
Allocated. Now you can use the Status drop down to bring back all the
orders not in an Allocated state yet i.e. Released, to highlight and
allocate these.

14

2. If selecting by Status isn’t allowing you to highlight all the Order
Headers required, try doing it one Consignment at a time.

3. Longer-term, log a call with the Helpdesk and raise a Configuration
Change Request to have User Accounts for people Allocating set
higher than 3000 in Settings  Session Settings  Session  Record
Set Size.

10 Clustering

Clustering is the process that groups move tasks onto lists based on the
configuration of the Cluster Rules.

10.1 Clustering Move Tasks

In order to Cluster move tasks onto lists the cluster configurations must be run
from the Clustering screen. By choosing the Group ID CLUSTER TASKS the
correct Clustering Configs are all automatically applied to any work that has
been Allocated.

All Config IDs use the Universal Sequencing Rule:
From Location in Pick Sequence in Ascending order

10.1.1 Config ID - Boxed Container Clustering

Set Pallet to List ID 

Online Multi SKU IDT Packs Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Status must be Released
The Order Header must have the IDT flag Y (ticked)
The Order Header User Defined Type 14 (Transfer Type) is ONLINE
The Move Task Work Zone must be BXPK%
The SKU User Defined Check 7 (Boxed) is Y (ticked)
The SKU User Defined Type 20 must not be SINGLE

Online IDT Pack Restriction Rule
Pallet Type: BEP (Board for Ecomm Packs)
The sum of the Move Task Qty to Move has a max of 400 per list.
The Move Task Task Volume has a max of 1.0 and min of 0
The sum of the Move Task Task Count has a max of 400 per list.

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

15

Online Multi SKU IDT Single Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Status must be Released
The Order Header must have the IDT flag Y (ticked)
The Order Header User Defined Type 14 (Transfer Type) is ONLINE
The Move Task Work Zone must be BXPK%
The SKU User Defined Check 7 (Boxed) is Y (ticked)
The SKU User Defined Type 20 must be SINGLE

Online IDT Single Restriction Rule
Pallet Type: BES (Board for Ecomm Singles)
The sum of the Move Task Qty to Move has a max of 400 per list.
The Move Task Task Volume has a max of 1.0 and min of 0
The sum of the Move Task Task Count has a max of 400 per list.

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

Boxed Normal Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Work Group must not be E%
The Move Tasks must be in Work Zone BXPK%
The Order Header must not have the IDT flag Y (ticked)
The SKU User Defined Check 7 (Boxed) is Y (ticked) OR
User Defined Num 5 (Division) is 6000

Boxed Normal Restriction Rules
Pallet Type: B (Board)
The Move Task Task Volume has a max of 1.0 and min of 0.25
The sum of the Move Task Qty To Move has a max of 360 per list.

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

Boxed Low Vol Singles Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Work Group must not be E%
The Move Tasks must be in Work Zone BXPKSI

16

The Order Header must not have the IDT flag Y (ticked)
The SKU User Defined Check 7 (Boxed) is Y (ticked) OR
User Defined Num 5 (Division) is 6000

Boxed Low Volume Restriction Rule
Pallet Type: BQ (Board Quarter)
The Move Task Task Volume has a max of 0.25 and min of 0.0456
The sum of the Move Task Qty To Move has a max of 100 per list.

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

Boxed Low Vol Initials Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Work Group must not be E%
The Move Tasks must be in Work Zone BXPKIN
The Order Header must not have the IDT flag Y (ticked)
The SKU User Defined Check 7 (Boxed) is Y (ticked) OR
User Defined Num 5 (Division) is 6000

Boxed Low Volume Restriction Rule
Pallet Type: BQ (Board Quarter)
The Move Task Task Volume has a max of 0.25 and min of 0.0456
The sum of the Move Task Qty To Move has a max of 100 per list.
Move Tasks in the same Work Zone

Boxed Tote Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Work Group must not be E%
The Move Tasks must be in Work Zone BXPK%
The Order Header must not have the IDT flag Y (ticked)
The SKU User Defined Check 7 (Boxed) is Y (ticked) OR
User Defined Num 5 (Division) is 6000

Boxed Tote Restriction Rule
Pallet Type: BT (Board Ten Tote)
The Move Task Task Volume has a max of 0.0456 and min of 0

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

17

10.1.2 Config ID - Boxed IDT & RTV Clustering –

Set Pallet to List ID  Set Container to List ID 

Boxed IDT RTV Reserve Selection Rule
The Move Tasks must be a Task Type of Order
The Move Tasks must be in Work Zone BXRV*
The SKU User Defined Check 7 (Boxed) is Y (ticked) OR
User Defined Num 5 (Division) is 6000
The Move Task Qty To Move must be equal to the inventory on the Tag in
that Location
The Order Line must have a Rule ID of IDTORDER or Condition of QF

Boxed Full Board Restriction
Pallet Type: BF (Board Full)
The Move Task Task Count has a max of 1 per list (to do 1 location at a time)

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

Boxed IDT RTV Pickfaces Selection Rule
The Move Tasks must be a Task Type of Order
The Move Tasks must be in Work Zone BXPK*
The SKU User Defined Check 7 (Boxed) is Y (ticked) OR
User Defined Num 5 (Division) is 6000
The Order Line must have a Rule ID of IDTORDER or Condition of QF

Boxed IDT Pickface Restriction
Pallet Type: BDT (so the user can see the difference and know to keep the
garments in the cardboard boxes rather than transfer it into plastic crates)
The Move Task Task Count has a max of 1 per list (to do 1 location at a time)

Boxed Grouping Rule
Each list must be for:
Move Tasks with the same Customer
Move Tasks with the same Work Group (same Wave)
Move Tasks in the same Work Zone

10.1.3 Config ID – Ecomm Multi Orders –

Set Pallet to List ID 

Ecomm Large Multi Selection Rule
The Move Tasks must be a Task Type of Order
The Move Task Work Group must be EM%
The Move Tasks must be in Work Zone BXPK* OR HGPK0Z
The Order Header User Defined Num 10 > 8 OR
The Move Task Move Task ID has a SKU where Awkward is ticked (Y) OR

18

The Order Header Order Volume > 0.02773
The Order Header Type is 30, 31, 32, 34, 35 OR 33
Ecomm Large Multi Restriction Rule
Pallet Type: BLM
The Move Task Move Task ID Count has a max of 1 per list
Ecomm Large Multi Grouping Rule
Each list must be for:
Move Tasks with the same Work Group
Move Tasks with the same Move Task ID
Order Header with the same Ship Dock

11 Consignment Preparation

This section will describe how to create a consignment and how to link pallets
to a consignment.
Consignments are automatically created by the wave tool but can also be
manually built using Consignment Maintenance and the Consignment
Drop Maintenance

11.1 Consignment

Access via:
Data  General  Consignment  Consignment

Enter the consignment number in the Consignment field - usually in the
format HHMMWWD (Hour Hour Minute Minute Week Week Day)

19

Enter the shipment date in the Shipment Date field using the format
DD/MM/YYYY.
Enter the shipment time in the Shipment Time field using the format
HH:MM:SS
If you are manually building a Consignment for an IDT Transfer, do NOT tick
Transhipment and do NOT enter a To Site ID please.

11.2 Consignment Drop

Access via:
Data  General  Consignment  Consignment Drop

Press Add.
The consignment number created in Consignment Maintenance will
populate if the “right-click” shortcut option is used within the Consignment
Maintenance screen. If the shortcut is not used this will have to be added
manually.
If you’re manually building a Consignment Drop for an IDT, enter the Address
ID as the 3 digit Warehouse the IDT Transfer is going to e.g. 045 or 055

12 Container Pick Assembly
12.1 Container and Pallet Label Printing

The Container label has been updated to show extra information if the Order
Header IDT flag is Y (ticked).

20

If there is 1 SKU in the Container it will display the number of SKUs and the
number of grabs
e.g. 1 Sku and 13 Grabs would display as: S1 / 13g

If there is more than 1 SKU in the Container it will only display the number of
SKUs, not the number of grabs
e.g. 4 Skus would display as S4

This is primarily to help Bedford receiving the IDT Ecomm Transfers from
Shire Park, so the users don’t need to recount the number of items in
Containers with only a single SKU, and so they know how many different
SKUs they are looking for in Containers with multiple SKUs.

12.2 Container Picking – via RF Device

Each Pallet Type is setup up with a Number for Picking which determines how
many lists you pick up for each type.

Pallet Type Notes Number for Picking
BDT Blue Board - For Layer picking IDT's from 1
pickface
BEP Blue Board - For E-comm Pick Assembly 1
- Packs
BES Blue Board - For E-comm Pick Assembly 1
- Singles
BT Board Ten Totes for Pick Assembly 10

12.2.1 Shire - Receiving Normal IDT UPI Pallets

Log on to a Wearable RF Device:

Select option 2 – User Directed
Select option 1 – Receive
Select option 4 – UPI Receive

Enter or Scan the pallet to be received.

21

Scan the Goods In Location (BX1GDSIN, BX2GDSIN, BX3GDSIN) where the
pallet is to be received.

The user is returned to UPI Receiving screen and can receive the next UPI
pallet into the WMS.

12.2.2 Reprint Tag Labels for Normal IDT UPI Pallets Received

To make Tag labels unique when there is DU Range wraparound, a Merge
Rule on the UPI Receipt Line sets Tag ID = PalletId+MMYY+UPIReceiptLine

e.g. 123456706161
where Pallet ID = 1234567, Date = 0616 (June 2016), UPI Receipt Line = 1

Once the UPIs are Received, this creates Inventory, and then Tag Reprints
can be printed off with a barcode for the Putaway driver to scan with the
Truckmount.

Access via:

Operations  Inventory  Tag Reprint

There are a number of fields you can populate to search for the required
inventory which you wish to reprint the new Tag Label number for e.g.
General – Pallet - if an individual Tag ID is required
User Defined – Original ASN - if Tag IDs for a whole inbound load is required

Original ASN = Idt+Consignment+SendingDepot
e.g. I1234123055
where Idt = I, Consignment = 1234123 (HHMMWWD), Sending Depot = 055

22

Alternatively, just go to Data, UPI, UPI Receipt Line, enter the 1 of the Pallet
IDs, then copy the number from User Defined Settings 1 – Original ASN.

12.2.3 Bedford - Receiving Ecomm IDT UPI Pallets

Log on to a Wearable RF Device:

Select option 2 – User Directed
Select option 1 – Receive
Select option 4 – UPI Receive

Enter or Scan the pallet to be received.

Scan the Goods In Location (ECOGDSIN) where the pallet is to be received.

The user is returned to UPI Receiving screen and can receive the next UPI
pallet into the WMS.

23

12.2.4 Relocating Inventory from Ecomm IDT UPI Pallets

Log on to a BXRelocate RF Device:

Select Option 2 User Directed
Select Option 4 Relocate
Select Option 2 New Relocate

In most cases, the user will be expected to tab down and populate -
Qty: by counting the number of grabs of 1 particular SKU and typing it in
Locn: by scanning the ECOGDSIN Location
SKU: by scanning the SKU or EAN barcode on the product
If there is no Pick Face record for the SKU, the To Location will be EBOXED

EBOXED should be over-scanned with one of the new Boxed Ecomm Bin
Locations e.g. BS010A01
Scan the check string to confirm the new Boxed Ecomm Bin Location
If Qty: is not entered the system will auto-populate the Qty on the next screen
with the full amount from the Location entered.

24

If the following message is displayed it may be because inventory of the same
SKU exists on more than 1 pallet in ECOGDSIN, so try entering the Pallet as
well.

If Pall, Qty, Locn, and SKU have all been entered but the Inventory is still not
unique, the user should leave this inventory on the pallet until the end and
then either:

a) Speak to a manager/admin team to obtain the Tag number(s)
b) Go into Putaway 221 on the RDT, enter the Pallet ID and check the

SKU suggested matches what you physically have left
c) Use Inventory Query on the RDT to obtain the Tag number(s)

13 SKU Management

SKU data will be interfaced and maintained centrally or updated by scripts.
All of the SKU related screens are found under the Data menu.

13.1.1 Pack Configuration

The Pack Configuration for all Division 1000 SKUs will be CLOTHING.

Tag Volume - 1.0

Volume at Each - 

Ratio 1 to 2 - 9999.0
Tracking Level 1 – GRABS
Tracking Level 2 – PALLET

The DEFAULT Pack Configuration in Bedford & Shire has been setup the

same as CLOTHING.

25

13.2 SKU

Use this screen to view, add and modify SKU’s.

A new field on SKU, User Defined, Settings 1, Component Type (User
Defined 20) is now populated by integration/a Merge Rule with:
COMPLEX – a SKU containing more than 1 SKU e.g. Clothing Initial Packs
SINGLE – a Single SKU Pack Size 0001
1234567890001 – the Single SKU contained within a Simple Pack Size >0001

Volumetrics can be changed via this screen, but are only needed for Boxed
and are automatically populated by a script that calculates it dividing receipt
Box Type size by the InBox Qty.

To cater for all the IDT Transfers, a new additional script has been added
which runs every 15 minutes looking at Pre-Advice Lines in the below To
Depots with a Create Date/Time since last run and Supplier User Defined
Type 4 = Z9??? (where ??? is one of the below From Depots)

From Depot --> To Depot
055 Shire --> 045 Bedford
002 Daventry--> 045 Bedford
045 Bedford --> 055 Shire
002 Daventry--> 055 Shire

SKUs on the IDT Pre-Advice Lines in the To Depot have their SKU
Volumetrics (Dimensions - Each Height, Each Width, Each Depth, Each
Volume, Each Weight) updated with the same values taken from the From
Depot.

If the SKU in the To Depot has SKU Component User Defined Type 20
populated with a SKU ending 0001, this is also updated with an Each Volume
and Each Weight both divided by the last 4 digits of the Pack SKU on the IDT.

Description is prefixed with the type and Family Group of the product i.e.
BS = Boxed Single, BI = Boxed Initial
HS = Hanging Single, HI = Hanging Initial,
GM = Division 6000 (not Boxed and not Hanging) then
CHD = Childrens, WMN = Womens, MEN = Mens, A40 = Default for V10

In Shire Park, a new merge runs that sets all Clothing Hanging SKUs to:
Boxed = Y, Hanging = N, Sortable = N so that we can still receive in, putaway,
allocate, pick and ship any SKUs that are up and hang or where there is also
inventory in Bedford that is to be treated as Hanging.

On the User Defined Tab are details of:
The D/C/P – 0962 0047 for all V10 SKUs + the Pack Size

There are also changes for Clothing like:
Style, Size, Sortable, Hanging, Boxed, Initial etc.

26

13.3 SKU Family Group

This screen allows you to define the names of groups into which SKU’s can
be categorized. These are known as SKU Family Groups. For Bedford
Clothing these are Genders and Events.

Family Group Description
A40 Default Family Group
CHD Childrens
EC1 Events - Clothing Event 1
EC2 Events - Clothing Event 2
EGK Events - GOK
EHA Events - Halloween
EKD Events - Kids Dress Up
EOT Events - Other
EWS Events - Wetsuits
HOS Events - Hosiery
MEN Mens
WMN Womens

To setup a new Event:

1. RMS Config Team Create UDA6 value in RMS.
2. Notify RP Configuration Team if there’s a requirement for the new

value to be treated as separate family group (if not will default to EOT).
This is important because if it’s treated as a separate Family Group it
will not mix with other Events in the Pre-Sort Buffer.

3. Config update the merge rule to code new UDA 6 value as E??

4. For Hanging, Config need to create a Location subzone for the new

family group.

5. Then Config need to assign locations to the new location sub-zone.

6. Inventory can be received and putaway.

13.4 Write Off Packs and Write On Singles for Online

In Bedford, a new daemon v_SkuConvDae will run every 15 minutes, looking
for non-Condition Coded inventory in a Location with Work Zone BXPKSI or
BXRV*, where SKU Component Type is populated with a different SKU
number ending 0001, which is not Obsolete.

Where all these criteria are met the Inventory will be:
Adjusted off Reason Code HO - eCOMM Simple Pack inventory written off

Then inventory for the SKU ending 0001 in the Component Type field will be:
Adjusted on Reason Code HA eCOMM Single SKU inventory written on, for
original quantity multiplied by the original pack size into the same Location.

e.g. Data  SKU  SKU
1036439490003 (Pack SKU)

27

Component Type: 1118428410001
(not Obsolete, first 9 digits different to Pack SKU)
Data  Location  Location
Location = BV010A08
Work Zone = BXPKSI
Data  Inventory  Inventory
Condition = null
Total Qty = 10
SKU 1036439490003 Qty 10 Adjusted off Reason Code HO
SKU 1118428410001 Qty 30 (10 x 0003) Adjusted on Reason Code HA

28