20190630 DNP GDC Venlo EWM Functional Specification - v13

For Internal Use Only
CONFIDENTIAL
Page 1 of 176
September 14th, 2018
Project Brief DNP Project GDC Venlo WMS
DNP GDC Venlo EWM project
V13 Draft
Page 2 of 176
June 30, 2019
DNP GDC Venlo EWM-project
Functional Specification
COLOPHON
Project name DNP GDC Venlo EWM project
Objective of this The Functional Specification document gives an overview of the future
document system setup.
It describes:
 how the system will support the future business processes as

described in the Business Scenario Document)
 how the User Requirements (URS) are covered.
It also summarizes references to custom build solutions needed to

support business requirements not available in standard SAP. The detailed
designs of those build solutions are not in scope of this document.
Authors
Name Role Date Signature
Karsten Walther DNP IT Project Member

Sandwip Majhi DNP IT Project Member
Thomas
DNP IT Project Member
Vancaeneghem
Joachim van Goch DNP IT Project Member
Document history
Version Date: Author(s) Remarks
0.1 19-Oct-2018 Thomas Vancaeneghem Initial draft

0.2-0.7 12-2018 team Updated draft
0.8 01-2019 Raphke van der Weide Matrix user requirements – functional
requirements moved to appendix
0.9 14-Feb-2019 Thomas Vancaeneghem Appendix made consistent with URS
18-Feb-2019 Eelco Huisman Document content made consistent with URS
and BSD
10 20-Feb-2019 Eelco Huisman Remarks and questions Fred Niessen
27-Feb-2019 Remarks and questions Luc Claessens
Page 3 of 176
June 30, 2019
11 10-04-2019 Karsten Walther Added Mainfreight outbound flow.

12 29-04-2019 Thomas Vancaeneghem Updated after demos:
- inbound with/without ASN
- outbound Mainfreight
13 30-06-2019 Thomas Vancaeneghem Added inbound information after demo’s.
Page 4 of 176
June 30, 2019
Distribution list
Company Name Function
DNP Roel Horsten Head Global Distribution Centre DNP

DNP Marc Lambrecht Global Head of Warehousing, Distribution and Transportation
DNP Roel Horsten Head GDC Venlo
DNP Eelco Huisman Program Manager Officer
DNP Raphke van der Weide IT Project Manager
DNP Hao Wang Validation Officer
DNP Fred Niessen Manager Global Supply & Inventory Planning
DNP Frans Schumans Transport Coordinator & Regional CCR Manager
DNP Ruud Zuurbier Coordinator Distribution Service
DNP Johan Vosbeek Manager Outbound
DNP Luc Claessens Operations Manager
DNP Werner Spijkers Quality Assurance Manager
DNP Bram Joosten Inbound employee
DNP Uwe Schumacher Outbound employee
DNP Bart van den Broek Outbound employee
DNP Bjorn de Bie Quality Assurance employee
DNP Thomas Vancaeneghem IT team member
DNP Christian Reich IT team member
DNP Karsten Walther IT team member
DNP Sandwip Majhi IT team member
DNP Abhishek Bachhawat IT team member
DNP Joachim van Goch IT team member
GEODIS Anton de Haan Project Manager
GEODIS Paul van Tilborg IT DNP operation Venlo, key-user
GEODIS Alex Janssen Warehouse supervisor, key-user
GEODIS Toncko Zwolsman Quality Assurance Manager
Page 5 of 176
June 30, 2019
Contents
COLOPHON......................................................................................................................................................... 2
Functional Specification...........................................................................................................................................2
Authors....................................................................................................................................................................2
Document history....................................................................................................................................................2
Distribution list........................................................................................................................................................4
1. Objective of this document........................................................................................................................... 11
2. General......................................................................................................................................................... 12
F1-GT–01-001 System Landscape..........................................................................................................................12
F1-GT–01-002 APS.................................................................................................................................................12
F1-GT–01-003 Kardex............................................................................................................................................13
3. Master data.................................................................................................................................................. 13
Overview & Data Migration Plan...........................................................................................................................13
F1-MD-01-001 Basic master data (Vendor, material, customer, batch)................................................................14
F1-MD-01-005 Packaging specification.................................................................................................................15
F1-MD-01-006 Hazardous substance.....................................................................................................................16

F1-DM-01-003 Dangerous goods...........................................................................................................................16
F1-DM-01-001 Product Master data EWM............................................................................................................19
F1-MD-01-007 Storage bin EWM..........................................................................................................................19
F1-DM-01-002 SUID migration to SSCC.................................................................................................................19
4. Slot booking.................................................................................................................................................. 21
4.1. F1-SB-01-001 Slot booking tool.......................................................................................................................21
4.2. TU statuses (in- and outbound)......................................................................................................................21
4.3. Inbound appointment handling......................................................................................................................21
4.4. Outbound appointment handling...................................................................................................................23
5. Inbound........................................................................................................................................................ 27
Page 6 of 176
June 30, 2019
5.1. Inbound information.......................................................................................................................................27

5.1.1. F1-IB-01-001 Inbound delivery information.............................................................................................27
5.1.2. F1-IB-01-002 Batch information...............................................................................................................27
5.1.3. F1-IB-01-003 Inbound delivery information changes...............................................................................27
5.1.4. F1-IB-01-004 Inbound delivery cancellations...........................................................................................27
5.2. Inbound process scenarios..............................................................................................................................28

5.2.1. F1-IB-02-001 Inbound process – ASN with packing info...........................................................................28
5.2.2. F1-IB-02-003 Inbound process – no ASN..................................................................................................29
5.3. Inbound process steps....................................................................................................................................29

5.3.1. F1-IB-03-001 Create Purchase Order.......................................................................................................29
5.3.2. F1-IB-03-002 Create Inbound Deliveries..................................................................................................29
5.3.3. F1-IB-03-003 Distribute Inbound Deliveries to Warehouse (EWM).........................................................30
5.3.4. Request unloading appointment.............................................................................................................31
5.3.5. F1-IB-03-004 Create unloading appointment reference to Forwarder....................................................31
5.3.6. F1-IB-03-005 Create Transport Units & link Inbound Deliveries...............................................................31
5.3.7. F1-IB-03-006 Truck Arrival – Arrival at Checkpoint..................................................................................31
5.3.8. F1-IB-03-007 Check Transport Unit with received documents.................................................................32
5.3.9. F1-IB-03-008 Container gas measurement...............................................................................................32
5.3.10. Request unloading Customs...................................................................................................................32
5.3.11. F1-IB-03-009 Add missing information to Inbound Deliveries................................................................32
5.3.12. F1-IB-03-010 Assign dock to Transport Unit...........................................................................................32
5.3.13. F1-IB-03-011 Truck to dock....................................................................................................................33
5.3.14. Attach unloading card to dock door.......................................................................................................33
5.3.15. Unloading and placing of pallets on staging area...................................................................................33
5.3.16. F1-IB-03-012 Quantity check & systematic packing...............................................................................33
5.3.17. Registration on unloading card..............................................................................................................33
5.3.18. Driver goes to GEODIS order processing and handover loading card.....................................................34
5.3.19. Complete information on CMR..............................................................................................................34
5.3.20. F1-IB-03-013 Update Status TU to departure.........................................................................................34
5.3.21. F1-IB-03-014 Truck departure................................................................................................................34
5.3.22. F1-IB-03-015 Check in of Transportation Unit - RF-scan of pallets and printing of HU labels.................34
5.3.23. F1-IB-03-018 Put-away...........................................................................................................................36
5.3.24. F1-IB-03-019 Customs posting...............................................................................................................50
5.3.25. F1-IB-03-020 Approval for use...............................................................................................................50
5.3.26. F1-IB-03-021 Update status to “Available”............................................................................................50
5.4. Exception Handling Inbound...........................................................................................................................51

5.4.1. F1-IB-04-001 Repacking / repalletizing / (re)labelling..............................................................................51
5.4.2. F1-IB-04-002 Inbound Quality Inspection................................................................................................52
5.4.3. F1-IB-04-003 Inbound deviations.............................................................................................................53
5.5. F1-IB-12-001 Inbound: labels & documents....................................................................................................55

Page 7 of 176
June 30, 2019
6. Outbound..................................................................................................................................................... 56
F1-OB-01-001 Create outbound deliveries.............................................................................................................56

Express orders................................................................................................................................................... 56
Outbound Mainfreight.......................................................................................................................................56
Outbound SEA and AIR......................................................................................................................................57
Pre-generated pack data....................................................................................................................................58
F1-OB-01-002 Reversal processes on outbound deliveries.....................................................................................59
F1-OB-02-001 Release outbound deliveries to Forwarder.....................................................................................59

Mainfreight: interface........................................................................................................................................59
Sea/Air: PDF/e-mail...........................................................................................................................................59
F1-OB-03-001 Receive planning from Forwarder...................................................................................................60

Mainfreight........................................................................................................................................................60
SEA and AIR .......................................................................................................................................................62
Return orders for GDC and external warehouses..............................................................................................62
F1-OB-04-001 Create Transport Unit.....................................................................................................................63

Send loading reference to Forwarder................................................................................................................64
Mainfreight reference........................................................................................................................................64
F1-OB-04-002 EQ Inspection required...................................................................................................................64
F1-OB-04-003 Hub address....................................................................................................................................64
F1-OB-04-004 Outbound Shipment data...............................................................................................................64
F1-OB-05-001 Create Wave...................................................................................................................................65
F1-OB-05-002 Release Wave.................................................................................................................................65
F1-OB-06-001 Replenishment to pick bins and reverse replenishment..................................................................66
F1-OB-07-001 Pick task creation and removal strategy.........................................................................................68

Full pallet pick....................................................................................................................................................70
Partial pick with replenishment (COLLI/LAYER).................................................................................................71
Partial pick via Pick Point (DRUMS)....................................................................................................................72
Cold storage 2A Picking......................................................................................................................................72
Picking shuttles..................................................................................................................................................73
Picking Pentapharm...........................................................................................................................................73
F1-OB-08-001 VAS Activities in outbound process.................................................................................................73
F1-OB-09-001 Staging...........................................................................................................................................77
F1-OB-10-001 Perform Dangerous Goods air delivery activities............................................................................78
F1-OB-11-001 Update of packaging information in Outbound Delivery................................................................78

Page 8 of 176
June 30, 2019
F1-U1-12-001 Loading...........................................................................................................................................79
F1-OB-12-002 BOSS check.....................................................................................................................................79
F1-OB-13-001 Post Goods Issue & Truck Departure..............................................................................................80
F1-OB-14-001 Outbound documents.....................................................................................................................80
F1-OB-15-001 Outbound logistic labels.................................................................................................................81
7. Storage......................................................................................................................................................... 83
F1-ST-01-001 GDC Storage facility........................................................................................................................83

GDC - Warehouse structure...............................................................................................................................83
Storage conditions.............................................................................................................................................83
GDC Storage strategies......................................................................................................................................96
GDC Storage bin types and capacity..................................................................................................................98
Order pick area (OPA)........................................................................................................................................98
Stock status........................................................................................................................................................98
F1-ST-02-001 External Warehouse and Overflow Warehouse.............................................................................102
F1-ST-03-001 Physical inventory counting...........................................................................................................104
F1-IB-01-006 Cross dock inbound........................................................................................................................110
U1-ST-04-001 Deliver to destruction / Rework and Tolling..................................................................................110
F1-IN-01-001 Maximum 1 Truck per Aisle...........................................................................................................110
F1-IN-01-002 Queue setup...................................................................................................................................110
F1-IN-01-003 Overrule movements.....................................................................................................................111
F1-IN-01-004 Interleaving....................................................................................................................................111
F1-IN-01-005 Process based RF messages...........................................................................................................111
F1-IN-01-006 Create and move nested handling units.........................................................................................111
F1-IN-01-007 Batch and product changes with (re)label actions.........................................................................111
F1-IN-01-008 VAS Orders for internal warehouse activities.................................................................................112
F1-IN-01-009 Ad hoc repack of stock...................................................................................................................112
F1-IN-01-010 Cross Process RF requirements......................................................................................................112
F1-IN-02-010 Ad hoc movement of stock.............................................................................................................113
F1-IN-02-001 GDC & RDC.....................................................................................................................................114
F1-IN-02-010 Ad hoc movement of stock.............................................................................................................114

Page 9 of 176
June 30, 2019
8. Returns....................................................................................................................................................... 115
F1-RT-01-001 Returns to Supplier........................................................................................................................115
F1-RT-02-001 Returns from Customer (Inbound).................................................................................................115
9. Customs...................................................................................................................................................... 119
U1-CU-01-002 Receipts (including returns)..........................................................................................................120
U1-CU-01-003 Material changes.........................................................................................................................122
U1-CU-01-004 Outbound Customs activities.......................................................................................................123
U1-CU-01-007 Stock reconciliation......................................................................................................................124
10. Monitoring & Reporting & KPIs.................................................................................................................. 126
10.1. Monitoring..................................................................................................................................................126
10.2. Reporting....................................................................................................................................................126
10.2.1. Inbound................................................................................................................................................126
10.2.2. Storage.................................................................................................................................................126
10.2.3. Outbound.............................................................................................................................................127
10.2.4. General................................................................................................................................................ 127
10.3. Print Outputs..............................................................................................................................................128
10.4. KPIs.............................................................................................................................................................128
11. Appendix: SAP ERP and SAP EWM Organizational structure.......................................................................129
12. Appendix: Abbreviations........................................................................................................................... 130
13. Appendix: Link to URS............................................................................................................................... 131
General............................................................................................................................................................ 131
Master data..................................................................................................................................................... 132
Slot booking.....................................................................................................................................................134
Inbound........................................................................................................................................................... 135
Outbound........................................................................................................................................................ 142
Storage............................................................................................................................................................ 156
Returns............................................................................................................................................................ 162
Customs...........................................................................................................................................................163
Monitoring & Reporting & KPIs........................................................................................................................164
Appendix: List of development objects (RICEF)....................................................................................................173

Page 10 of 176
June 30, 2019
Page 11 of 176
June 30, 2019
1. Objective of this document

The objective of this document is to describe the future DNP GDC Venlo system setup.
It describes:
• how the system will support the future business processes as described in the Business
Scenario Document)
• how the User Requirements (URS) are covered.
It also summarizes references to custom build solutions needed to support business requirements not
available in standard SAP. The detailed designs of those build solutions are not in scope of this
document.
The document is the basis for:
- General:
o providing the solution overview
- Business:
o checking if this system setup is suitable to perform daily business activities.
o writing the Standard Operating Procedures (SOPs) and Work Instructions (WI)
- IT:
o defining the Detailed Designs
o checking the completeness of development list
o writing system test scripts
Page 12 of 176
June 30, 2019
2. General
F1-GT–01-001 System Landscape
F1-GT–01-002 APS
The automatic positioning system works standalone without interfaces to and from EWM. The tool reads
the screen of the terminal to know the destination of a crane.
Page 13 of 176
June 30, 2019
F1-GT–01-003 Kardex
For the Kardex storage bins, the operator uses normal RF-terminals. If the RF asks him to go to a certain
bin, the operator will operate the Kardex on the Kardex interface independent from the SAP terminal. No
interfaces or connection between Kardex and SAP are in scope.
3. Master data
Overview & Data Migration Plan
 Basic Material
 Batch
 Packaging specification
 Hazardous substance
 Dangerous Goods
 Product master data (EWM)
 Storage bin (EWM)
 Vendor
 Customer
 Customer specifics
 Product master data (EWM)
 Storage bin (EWM)
A separate Data Migration Plan document is available with all details of the data migration:
- Master data elements

- Tools
- Timing
- Responsibilities.
Page 14 of 176
June 30, 2019
F1-MD-01-001 Basic master data (Vendor, material, customer, batch)
 Material data
Material master data is synchronised with EWM by standard SAP CIF (Core Interface), thus the
information is available in both systems. All materials stored at GDC Venlo, overflow and partly external
warehouses will be transmitted. Special materials stored only at Eurofrigo will not be sent to EWM.
The CIF transmits only basic material data and the materials need to be extended in EWM with
warehouse specific information, hazardous information.
 Batches and classifications
Batch master data is synchronised with EWM by standard SAP CIF (Core Interface), thus the information
is available in both systems. The Q26 classification will also be created in EWM for the batches but this
information is not used and updated in EWM. The main information for batches is the expiry and
production date used to print on several labels/outputs. The whole logic of the batch
determination/management for outbound deliveries stays in Q26 and is provided in the corresponding
flows to EWM. In case of relabelling the batch, LIMS analyse number will be provided by DNP.
 Vendors
Vendor master data is synchronised with EWM by standard SAP CIF (Core Interface), thus the
information is available in both systems.
 Customers
Customer master data is synchronised with EWM by standard SAP CIF (Core Interface), thus the
information is available in both systems.
In EWM a BADI is activated which allows in future the on-boarding of additional SAP systems. This BADI
appends the originating system of the master and organizational data by adding a @system to the
customers, materials, plants, shipping points and so on.
Additionally, all customer numbers will be prefixed by a CU (for customer) and all Suppliers by SU (for
vendors).
Page 15 of 176
June 30, 2019
F1-MD-01-005 Packaging specification
<to be reviewed>
F1-MD-01-005 005 It must be possible to store packaging master data in EWM system of all
packaging levels at first receipt.
Packaging level master data are not filled in DNP Q26 at material creation and not complete before the
first receipt of a material.
GEODIS measures the dimensions and weights of all packaging levels at first receipt and registers the
data in DNP Q26 system. The data is needed in various SAP tables for having the correct data for the
sales orders and transport orders. The data update in DNP system will be done before transport and
customs documents are printed.
The following packaging master data will be registered. Not all levels may be applicable for all materials.
Packaging Data Unit Remark

level
Inner pack Length cm

Width cm
Height cm
Net weight kg
Gross weight kg
Quantity per inner pack # Always 1
Carton / bag Length cm
Width cm
Height cm
Net weight kg
Gross weight kg
Quantity per carton / bag #
Layer Length cm Based on pallet dimension
Width cm Based on pallet dimension
Height cm Based on overpack height
Gross weight kg Based on overpack weight
Quantity per layer #
Pallet Length cm
Page 16 of 176
June 30, 2019
Width cm
Height cm Including the pallet itself
Gross weight kg Including the pallet itself and additional
packing materials (if applicable and standard
for the material)
Quantity per pallet #
Layers per pallet #
F1-MD-01-006 Hazardous substance
Hazardous substance defines storage rules in the warehouse and influences the put away strategy into
the warehouse. In addition, these data are needed to create reports for e.g. the fire department (BRZO -
Bedrijfs Risico Zware Ongevallen – Company Risk Heavy Accidents) and
The Fire Department Report is available in EWM. This information is retrieved from the Safety Data Sheet
(SDS) and is manually maintained.
F1-MD-01-006 006 It must be possible to upload and store all relevant Hazardous substance
data in EWM system that are needed to define the correct put away strategy.
F1-DM-01-003 Dangerous goods
Specific master data is needed for dangerous goods. The dangerous goods master data is maintained in
P43 by the SHE department. This data will be transmitted from P43 to Q26 via SAP IDOC. This new
information will replace the old ZZDG dangerous goods information. With this the alignment and
consistency of the DG data for the DSM materials across several SAP systems is ensured. The following
regulations will be transmitted:
ADR - Road; RID - Railway; IMDG – Waterways, IATA_C – Airplane
The following dangerous goods master data is needed for reporting:
Level Data Source Maintained Remarks

in DNP Q26?
Dangero Dangerous good Y/N P43 Y

us goods
info
Packaging group P43 Y
ADR Class P43 Y
UN Number P43 Y
Tunnel restriction code P43 Y
Proper Shipping name P43 Y
Page 17 of 176
June 30, 2019
Technical name P43 Y If applicable

Packaging type DSM Order N If available
Manual
Hazard Identification P43 Y
Number
CMR substance MSDS N Hazards-statement / H-
identification phrases (H340, H341, H360,
H361)
Molecular composition MSDS, PDS N % CL, % F, %Br, %S
CAS Number MSDS, PDS N
Appearance MSDS N Solid/liquid
Auto ignition temperature MSDS N
Flashpoint MSDS N
NFPA Class GEODIS N Based on local checklist
Seveso Classification GEODIS N Based on local checklist
Fire compartment GEODIS N Location where product is
stored
H-Guide MSDS N
Dangerous goods data is also printed on various labels, but these are generated in the standalone
system PAGO where these data are stored as well. Data in PAGO is maintained by DNP with regular
updates.
Some programs / Sap scripts to be adjusted to reflect the new DG information:
Output type Appl. Program Sap script

EK00 1 V4 ZVADEK01 ENTRY ZVPICKLIST
YPKL 1 V2 ZVADEK01 ENTRY ZVPICKLIST
ZTDS 1 V1 ZVAOTRDI ENTRY ZV_SO_TRANS_DISP
YTDS 1 V7 ZVADTRDI ENTRY ZV_TRANS_DISP
ZTO2 1 V7 ZVTRORD ENTRY ZV_TRANS_ORD
ZTOR 1 V7 ZVTRORD ENTRY ZV_TRANS_ORD
Those outputs were printing the DG info as per deactivated item text:
YDDN 5 V2 ZVADDN01 ENTRY_PDF ZV_DELNOTE

YRDN 1 V2 ZVADDN01 ENTRY ZV_RET_DELNOTE
ZLO2 1 V7 ZLOLPROG ENTRY ZV_TRANS_ORD
ZLOL 1 V7 ZLOLPROG ENTRY ZV_TRANS_ORD
ZCMR – CMR document Program ZZWCMRPR is also printing DG texts; this output is moved to EWM.
Page 18 of 176
June 30, 2019
CMR for overflow/external?
CMR is also needed for external location and for Deinze (pre-mix site).
This is an example how the information is to be output:
UN 3077 ENVIRONMENTALLY HAZARDOUS SUBSTANCE, SOLID, N.O.S.
(MENADIONE NICOTINAMIDE BISULFITE) 9, III, (-)
If the UN number is not 3082 and not 3077 then the field MAPOL has to be added for ADR when the
value is E1 (Environmentally Hazardous)
UN1759 Corrosive solid, N.O.S. (thymol, m-cresol), 8, II, (E) Environmentally Hazardous
For Sea shipment the tunnel code can be skipped: (-) in the above example but Marine pollutant to be
added:
UN 3077 ENVIRONMENTALLY HAZARDOUS SUBSTANCE, SOLID, N.O.S.
(MENADIONE NICOTINAMIDE BISULFITE) 9, III, Marine Pollutant
For RID – Railroad the hazard ID number has to be printed first. Field: HNU
80 UN 1759 CORROSIVE SOLID, N.O.S. (THYMOL, M-CRESOL) 8, II, RID
IATA – Air, the packaging instruction has to be included. Field: PIN
UN 1759 CORROSIVE SOLID, N.O.S. (CONTAINS THYMOL, M-CRESOL) 8, II, PI 863
Data which will not be provided because it can be and is solved in one of the systems only.
Level Data Remarks

Material MOQ (Minimum Order Quantity) Not applicable for EWM. DNP always orders in MOQ
info in Q26 according to physical package
OQM (Order Quantity Multiple) Not applicable for EWM. DNP always orders in OQM
in Q26 according to physical package
ABC classification Not known in advance for new materials. GEODIS
can define ABC class based on consumption if useful
Page 19 of 176
June 30, 2019
for warehouse process
F1-DM-01-001 Product Master data EWM
Product master data must be maintained directly in EWM; thus, the information is only available in EWM
and not in ECC. The product master data for all materials stored at GDC Venlo, overflow and partly
external warehouses will be maintained. Detailed information regarding the specific fields can be found in
the data migration plan.
F1-MD-01-007 Storage bin EWM
The existing bins (locations where material is stored) which are in use today must be created in the EWM.
Detailed information regarding the specific fields can be found in the data migration plan.
F1-DM-01-002 SUID migration to SSCC
The slide below shows the connection between the DNP SUID and the SSCC code.
The SSCC codes from P36 will be transferred via IDOC to Q26 and could be re-used.
Page 20 of 176
June 30, 2019
Page 21 of 176
June 30, 2019
4. Slot booking
4.1. F1-SB-01-001 Slot booking tool
Dock Appointment Scheduling (DAS) will be used for slot booking. With this tool, appointments are
created to reserve a (un)loading capacity for a time slot.
This is a standard SAP tool with strong integration with SAP EWM. Status changes in DAS are reflected
in EWM and relevant EWM changes are reflected in the appointment in DAS.
There is a 1 on 1 relationship between an appointment and transportation unit.
Following will be setup:
- Docking Location WHA100

- Loading Point: LP01 DC Venlo (DAS linked to EWM)
4.2. TU statuses (in- and outbound)
The Transport Unit statuses from EWM are reflected in DAS in real-time.
- Arrival at checkpoint
- Arrival at door
- (un)loading started
- (un)loading finished
- Departed from door
- Departed from checkpoint
4.3. Inbound appointment handling
EWM for inbound will use the standard EWM-DAS scenario with trigger originating in DAS.
Page 22 of 176
June 30, 2019
The shipping office will create an appointment in DAS to reserve a time slot on the capacity of available
doors for unloading on the requested date & time.
Appointments are created with standard transaction code “Create Appointment – Graphical” or “Create
Appointment – Textual” which are both called from the EWM system and start the DAS tool.
This appointment number will be shared with the forwarder as a reference. If a TU is already available,
this can also be shared.
When arriving at GEODIS the truck driver reports to the office of GEODIS with the reference number
received.
Receiving Officer (RO) will change the status of the appointment to ‘Arrived at Checkpoint’, this
automatically updated the TU to the same status in DAS and EWM. This can be done with standard
transaction code “Process Appointments” in DAS, or with standard transaction code “/SCWM/TU –
Process TU” in EWM. Both systems are integrated and result in the same status update of both the
appointment and the linked transportation unit.
Page 23 of 176
June 30, 2019
DAS: Process Appointment:
EWM status overview:
DAS status overview:
4.4. Outbound appointment handling
EWM for outbound will use the standard EWM-DAS scenario with trigger originating in EWM.
Page 24 of 176
June 30, 2019
Outbound deliveries and shipments are received from Q26 into EWM. Outbound deliveries are
automatically reflected as Outbound Delivery Orders, shipments are reflected as Transportation Units in
EWM.
As soon as a link exists between 1 or more deliveries and a transportation unit, a provisional
appointment is automatically created in Dock Appointment Scheduling. This provisional
appointment contains the planned (requested) date and time for pickup.
The Shipping offices updates the status of the appointment with standard transaction “Process
Appointments” if capacity is available.
Page 25 of 176
June 30, 2019
The appointment number and date/time are shared with the forwarding agent as a reference. The
TU number can also be shared.
When arriving at GEODIS the truck driver reports to the office with the reference number received.
Shipping Officer (RO) will change the status of the appointment to ‘Arrived at Checkpoint’ in DAS, this
automatically updated the TU to the same status.
It is also possible to do this on the TU, which will automatically update DAS.
The SO will also assign a suitable door to the TU and will change the status of the TU to ‘Docked at
door’
Page 26 of 176
June 30, 2019
EWM status overview:
DAS status overview:

Page 27 of 176
June 30, 2019
5. Inbound
5.1. Inbound information
5.1.1. F1-IB-01-001 Inbound delivery information
5.1.2. F1-IB-01-002 Batch information
When an ASN message is sent from the supplier, the batch will already be filled on the delivery in Q26
before distribution to EWM. This is part of development ECC04.
When the batch is unknown before the trucks arrives in Venlo to deliver goods, GEODIS order processing
will fill the batch number manually in the inbound delivery in EWM without any additional information (e.g.
expiry date and manufacturing date). This is standard SAP setup, no custom build actions involved.
A batch record will be created automatically in EWM and Q26.
5.1.3. F1-IB-01-003 Inbound delivery information changes
Purchase orders do change regularly. Inbound deliveries do change incidentally. Expected receipt date is
often changed, both in PO and inbound delivery.
When an inbound delivery has been sent from SAP ERP Q26 to SAP EWM system, only the receipt date
can be changed, but quantities cannot be changed anymore (only actuals can be registered then).
5.1.4. F1-IB-01-004 Inbound delivery cancellations
A purchase order can be cancelled by setting the ‘Deletion Flag’.
Inbound deliveries are not intended to be cancelled but it is possible. Cancellation of an inbound delivery
in EWM before GR will set the inbound delivery to zero and confirm it with quantity zero to Q26. This
opens the requested quantity on the PO again and a new inbound delivery can be created if required.
When Goods Receipt was already posted for the inbound delivery when it is decided that the delivery
needs to be cancelled, reverse GR needs to be triggered from Q26 with an outbound delivery (102
movement triggered from Q26). The pallets can then be picked for that reversal outbound delivery, and
the related PO in Q26 will become open again.
Page 28 of 176
June 30, 2019
5.2. Inbound process scenarios
5.2.1. F1-IB-02-001 Inbound process – ASN with packing info
When the supplier sends an Advanced Shipping Notification (ASN) via interface message including
Handling Unit (SUID/SSCC) information, the inbound delivery is already available in Q26 and PEW
before the process starts. Hence, automated delivery creation is the start of the process.
If the pallets have a scannable SUID barcode, the operator in the Distribution Center can scan the HU’s
upon receipt without the need to enter packaging material, product, batch, quantity. This info is retrieved
by scanning the SUID barcode. Note that also the SSCC can be scanned if it is on the label, this means
that the option is already available to move to SSCC labels in the sending locations in the future.
Now the HU’s from the inbound deliveries are only stored in a Z-table and are not available at the
inbound delivery itself. The SAP standard qRFC cannot transfer the HU’s to EWM if they are not linked to
the inbound delivery. Some additional development is needed to link the HU’s from the z-tables to the
delivery.
The packed IBD should have this structure:
 PALLET 1 (Packaging material) LVL2

 Material Quantity Batch LVL3
 PALLET 2 (Packaging material) LVL2
The HU number in EWM is the SSCC number. Now the HU’s transmitted via IDOC from P36 M&T sites
do not contain the SSCC numbers. A development will transmit the HU and the SSCC numbers from
P36. All outgoing HU’s in P36 have an SSCC number assigned. IBD’s from other systems than P36 have
to be checked.
Development: ECC04 - Packing in ECC based on ASN with SUID
ASN with packing info – process and the relevant process steps can be found in the Business Scenario
Document.
5.2.1.1. F1-IB-01-002 Inbound process – ASN without packing info (with or without packaging
specification)
When the supplier sends an Advanced Shipping Notification (ASN) via interface message excluding
Handling Unit (SUID/SSCC) information, the inbound delivery is already available in Q26 and EWM
before the business process starts. Hence, automated delivery creation is the start of the process.
Handling Units (HU’s) are prerequisite for all the processes and therefore mandatory in EWM. In case this
Handling Unit data is not provided in the Inbound Delivery or Advanced Shipping notification (ASN), a
packing step is mandatory in EWM to create the required HU’s. The handling units can also be built on
RF by the operators.
Page 29 of 176
June 30, 2019
Packaging specifications can be used to pack handling units if they were not packed upfront. For the put
away process, packaging specifications are uploaded and used in the put away strategies to final bins. If
there is no packaging instruction available in EWM the goods can be received but they cannot be put-
away until the pack spec is maintained.
5.2.2. F1-IB-02-003 Inbound process – no ASN
When the supplier does not send an interface message upfront, the inbound delivery can only be created
after the truck driver has arrived at the DC. The documents accompanying the truck will be used to know
the contents of the truck and to create an inbound delivery.
Alternative: qRFC the purchase orders to EWM and then the IBD can be created in EWM and transmitted
into ERP with the goods receipt.
Handling Units (HU’s) are prerequisite for all the processes and therefore mandatory in EWM. In case this
Handling Unit data is not provided in the Inbound Delivery or Advanced Shipping notification (ASN), a
packing step is mandatory to create the required HU’s. The handling units can also be built on RF by the
operators.
Packaging specifications can be used to pack handling units if they were not packed upfront. For the put
away process, packaging specifications are uploaded and used in the put away strategies to final bins. If
there is no packaging instruction available in EWM the goods can be received but they cannot be put-
away until the pack spec is maintained.
Inbound process – Receipt from Overflow location and External location
The inbound process for receipts from overflow and external locations is described separately as part of
the chapter on overflow and external warehouses.
5.3. Inbound process steps
5.3.1. F1-IB-03-001 Create Purchase Order
5.3.2. F1-IB-03-002 Create Inbound Deliveries
The first prerequisite for the inbound process in EWM, is the Inbound Delivery. The EWM Inbound
Delivery forms the basis for the inbound process for goods delivered by both external vendors and DNP
production locations (“suppliers”). It is the starting point for the inbound process.
Inbound deliveries can be created in Q26 and distributed with standard qRFC to EWM for processing.
Page 30 of 176
June 30, 2019
Inbound deliveries can also be created in EWM and be distributed to EWM where they will automatically
be linked to a purchase order.
When created in ECC, the deliveries are distributed via the standard Interface to EWM. They are
replicated to an Inbound Delivery Notification in EWM. Based on this Inbound Delivery Notification and
the EWM customizing and Master Data, EWM generates the EWM Inbound Deliveries.
In 2 scenarios the inbound deliveries are created from Q26:
- If DNP planning department creates deliveries upfront

- If ASN is received from vendor/supplier, triggering automatic delivery creation in Q26
Purchasing Doc. Type Scenario IBD Creation System Distribute

Doc. Type Descript. to EWM
at save
NB Standard PO M&T Automated Q26 Yes

NB Standard PO External Vendor without Manually Geodis EWM Yes
ASN
NB Standard PO External Vendor with Automated Q26 Yes.
electronic ASN
NB Standard PO External Vendor with paper Manually DSM Q26 Yes
ASN or email
UB Stock transport Automated Q26 Yes
ord.
5.3.3. F1-IB-03-003 Distribute Inbound Deliveries to Warehouse (EWM)
In these scenarios, the inbound delivery needs to be distributed to EWM. This will result in an Inbound
Delivery Notification in EWM. This notification is automatically activated into an inbound delivery on EWM
side.
Inbound deliveries relevant for cross dock will be manually created in Q26. DNP informs the warehouse,
who will change the warehouse process type on the items relevant for crossdock.
EWM Objects – Inbound

Object Description
IDR Document Category Inbound Delivery Notification
Page 31 of 176
June 30, 2019
INB Document Type Inbound Delivery Notification

PDI Document Category Inbound Delivery
INB Document Type Inbound Delivery
5.3.4. Request unloading appointment
The driver or the transporting company contacts Geodis prior to pick up of goods to make an
appointment. This is not a system relevant step.
5.3.5. F1-IB-03-004 Create unloading appointment reference to Forwarder
The Geodis receiving officer will register this in Dock Appointment Scheduling by creating an
appointment.
In Dock Appointment Scheduling, an appointment is made to reserve unloading capacity (time slot). In
those appointments ship-from name, carrier name and number of pallets, driver name, ID number and
license plate can be entered if necessary.
This is standard SAP setup. No custom developments.
Forwarder receives unloading appointment number. (not system relevant)
5.3.6. F1-IB-03-005 Create Transport Units & link Inbound Deliveries
When an inbound truck arrives at the Distribution Centre, the relevant appointment is searched in DAS.
5.3.7. F1-IB-03-006 Truck Arrival – Arrival at Checkpoint
Driver reports to GEODIS office with unloading reference and documents e.g. CMR, T1 (if applicable) and
packing list.
When the receiving officer sets the appointment to status ‘Arrived at checkpoint’, a Transportation Unit is
automatically created in EWM. The receiving officer can now search for existing inbound deliveries or
create inbound deliveries for this supplier based on the quantities and batches on the documents
provided by the truck driver. He assigns the relevant deliveries to the TU. This is also possible for parcel
deliveries. The TU can be created and saved before the deliveries are known (empty TU). All deliveries
created can be searched for with selection on multiple inputs, including PO number, ERP Delivery
number and material number.
The transportation unit represents the physical load (truck, container) and can contain multiple deliveries.
It is possible in EWM to automatically create TU’s based on interface messages from external parties. In
the initial go live scope, this is not in scope for inbound.
Page 32 of 176
June 30, 2019
5.3.8. F1-IB-03-007 Check Transport Unit with received documents
GEODIS office receives the related documents CMR, T1 (if applicable) and packing list of a transport
from the driver and checks these documents.
When the inbound is relevant for T1, the receiving officer will register the MRN reference so that the stock
is automatically blocked for customs until customs informs us that the stock can be released.
This customs block is not blocking for the receiving and putaway process. It is only blocking for shipping
the goods out.
Development: EWM15 – Transaction for TU Details
A custom transaction code is built to facilitate the registration of the T1 reference number on the incoming
deliveries.
5.3.9. F1-IB-03-008 Container gas measurement
status: currently under investigation by GEODIS QA if process is still needed info Toncko Zwoltsman. Out
of scope?
5.3.10. Request unloading Customs
GEODIS office sends a request for unloading to Customs in case of T1-documents. This is done outside
of SAP, in the LSP system.
5.3.11. F1-IB-03-009 Add missing information to Inbound Deliveries
If no batch was entered in Q26 on the inbound delivery, a batch must be entered in EWM during the
receipt process. (for batch managed materials).
Warehouse planning adds missing batch information to the inbound deliveries with transaction
/SCWM/PRDI (Process inbound delivery) if necessary. The batch will be distributed to ERP. The
classification data and missing information will be maintained by DSM Quality Department in ERP.
5.3.12. F1-IB-03-010 Assign dock to Transport Unit
Development: EWM07 - Door determination inbound
To optimize the distance that operators need to drive to put away the stock the final locations, a PPF is
built to calculate the door which will need the least total distance for put away movements. This door will
Page 33 of 176
June 30, 2019
automatically be assigned but the Receiving Officer can change this assignment. This can be done until
the Goods Receipt is posted
Development: PRN05 - Unloading Card
When a door is assigned to an inbound TU, an unloading card should be printed. This form will be printed
using PPF functionality. The unloading card is given to the driver, so he knows to what door he needs to
drive his truck.
5.3.13. F1-IB-03-011 Truck to dock
When the driver has reported to the door provided by the goods receiving officer, the status of the
transportation unit must be set to ‘Docked at door’. This is done in EWM, in standard transaction code
/SCWM/TU.
Now the truck will be physically unloaded. No unloading with RF is in scope.
Development: PRN04 - Unloading List
At the door the unloading list is printed, this form will be printed using PPF functionality. It is printed on TU
level and contains the information of all deliveries contained in the TU (product, batch, quantity)
The goods are physically unloaded, counted and inspected by the responsible warehouse worker(s).
Missing goods, batch details and packing details need to be filled out on the unloading list which is
returned to the RO after the physical unloading is done.
5.3.14. Attach unloading card to dock door
Driver gives unloading card and unloading list to warehouse operator. (no system implications)
5.3.15. Unloading and placing of pallets on staging area
Warehouse operator will physically unload the truck. The pallets are placed on the staging area. (no
system implications)
5.3.16. F1-IB-03-012 Quantity check & systematic packing
System interaction see 5.3.22.
5.3.17. Registration on unloading card
No system actions
Page 34 of 176
June 30, 2019
5.3.18. Driver goes to GEODIS order processing and handover loading card
No system actions
5.3.19. Complete information on CMR
No system actions
5.3.20. F1-IB-03-013 Update Status TU to departure
Transport Unit status is updated, and driver gets permission to leave.
After unloading is done, the truck will leave the DC again.
There are 2 ways to end this process:
- If Departure from Checkpoint is posted on the TU or on the appointment, the TU is automatically

undocked from the door.
- If Departure from Door is done (so the door is free again, but the truck is still on the premises in
Venlo), then also departure from checkpoint needs to be done to end the process.
At the end of the process, TU will have had the following statuses in EWM:
 Arrival at Checkpoint (similar to ‘arrived’ from URS)

 Arrival at Door (similar to ‘docked’ from URS)
 Unloading started/finished (similar to 'unloaded' / 'released for dock departure' from URS)
 Departure from Door
 Departure from Checkpoint (similar to 'departed' from URS)
5.3.21. F1-IB-03-014 Truck departure
Physical departure of the truck, no system interactions.
5.3.22. F1-IB-03-015 Check in of Transportation Unit - RF-scan of pallets and printing of HU

labels
The unloaded goods on the receiving zone need to have labels before they can be put away into stock.
Warehouse operator will scan each pallet and will print handling unit labels. The handling unit label is
attached to the pallet. The check in is complete, when the last pallet has been provided with a label.
Handling Units (HU’s) are prerequisite for all the EWM processes and therefore mandatory in EWM. In
case this Handling Unit data is not provided in the Inbound Delivery or Advanced Shipping notification
(ASN) upon arrival, a packing step is mandatory to create the required HU’s.
Page 35 of 176
June 30, 2019
The standard EWM solution supports inbound deliveries with and without handling units. Packaging
specifications can be used to pack handling units if they were not created upfront. The handling units can
also be built on RF by the operators.
Goods Receipt will be posted per pallet (=handling unit) in EWM and communicated for the whole
delivery at once to ERP after the last HU.
GR in EWM is done by the operator on RF, with the standard functionality “GR by HU”.
Goods receipt registration is automatically posted from EWM to Q26 when the last pallet of an inbound
delivery has been posted goods receipt. This is a standard SAP EWM settings defined in customizing
under SCM Extended Warehouse Management > Extended Warehouse Management > Interfaces >
ERP Integration > General Settings > Set Control Parameters for ERP Version Control
This will trigger the interface to Q26 and post a goods receipt in ERP. The stock is available in Q26 either
in unrestricted use or in Quality inspection.
Development: EWM26 - Update External ID in HU at time of GR
When GR is posted in EWM, the link between the Handling Unit and the delivery document is registered
automatically in table /SCWM/HU_DLV. This is standard SAP functionality which makes it possible to
determine which handling units can be made available after receiving the approval message from
customs (see 5.3.25 and 5.3.26)
Development: EWM09 - SUID registration inbound
The “GR by HU” function is enhanced to enable registration of external identifiers (Storage Unit ID from
production sites). Pallets from DNP plants can have an SUID number which is communicated to the DNP
Q26 system. Q26 makes SSCC handling units and links the SUID to that handling unit as an external ID
(cf. development ECC04) In this case also EWM is informed of both numbers.
Pallets from other sources have no SUID. The standard “GR by HU” function also allows for the operator
to pack handling units on RF when no handling units were communicated upfront. He does this by
entering product, material, batch, quantity (where applicable/possible by scanning barcodes on the label).
5.3.22.1. F1-IB-03-016 Label
Development: PRN02 - Internal SSCC Label

Page 36 of 176
June 30, 2019
After pressing the “Create WT” function button, a put away warehouse task is created. At this point, also
the destination storage bin for the HU is known and an internal SSCC label will be printed on the belt
printer of the operator. The label will show the row number where the pallet needs to go. Because the row
number needs to be printed, the label can only be printed after creation of the put away task.
5.3.22.2. F1-IB-03-017 ADR Check during GR
EWM must be able to inform the warehouse operator during the receipt check on RF if ADR materials are
in the delivery to check if labelling is applied correctly.
Development: EWM02 - RF Screen on inbound for Dangerous goods labels
When the truck contains dangerous goods, the operator needs to get a screen on RF asking him to check
if the correct dangerous goods label is applied to the pallet.
5.3.23. F1-IB-03-018 Put-away
After check-in, for each SSCC (product-batch) a warehouse task is created to final location according to
the put away strategy. Damaged stock is put to a dedicated area. In exceptional cases DNP might inform
GEODIS that the product should be rebooked/placed to block/quarantine
5.3.23.1. Create Put-away warehouse task
Putaway in EWM starts with the determination of a warehouse process type based on the inbound
delivery document type INB. The default process type used in warehouse A100 is 1010.
Page 37 of 176
June 30, 2019
5.3.23.1.1. Determine Warehouse Process Type

Page 38 of 176
June 30, 2019
For returns deliveries the same functionality is used, but then a specific returns process type 4030
determined, which sends the goods to the returns area (storage type 0302 and 0101 for ADR4.2). See
chapter about the returns process for more details.
5.3.23.1.2. Define Warehouse Process Type
WPT 1010 – standard putaway process

Page 39 of 176
June 30, 2019
WPT 1016 –putaway to crossdock
This process type has exactly the same settings as 1010 but will be used in the storage type search
sequence to find another destination. It will not derive a final storage bin based on the product but will
guide the product to the crossdock storage type 0300.
Page 40 of 176
June 30, 2019
Standard SAP put away strategies will be followed. These will be derived based on:
Storage Type Search:
- Hazard Rating 1&2

- Put away Control Indicator is used to identify how products will be stored. This is based on the
way products are stored (High Rack, Open Storage, Pick Area...)
- Warehouse Process Type
- Quantity Classification
Storage Section Search:
- Hazard Rating 1 & 2

Page 41 of 176
June 30, 2019
- Storage Type
- Storage Section indicator
The principle rule is that a put away control indicator (PACI) is setup per storage type and that a section
indicator is setup for determination of the section.
When the final destination determined for a handling unit is in the highbay, physical restrictions are
considered. The movements are automatically split into two movements: 1 movement from the GR zone
to and ID point and a movement from ID point to final location in the highbay. This split is realized with
standard SAP functionality called Layout-Oriented Storage Control.
For every area that needs to be accessed via an intermediate location, a storage group is created. In
Venlo, this is one storage group per aisle in the highbay.
Page 42 of 176
June 30, 2019
Per group it is defined via which front-bin the handling units need to pass.
Put away Control Indicator
The put away control indicator will be used to identify how products will be stored. This is based on the
way products are stored (High Rack, Open Storage, Pick Area...).
The put away control indicators to be used:
Storage Type Search
WhN PACI Description
Sequence
A100 0105 Storage Type 0050
A100 0300 Phase 2 Highbay - Consumables
Page 43 of 176
June 30, 2019
A100 0301 Containers in the yard

A100 0500 Picking Ambient - 040
A100 0501 Picking Ambient - 060
A100 0502 Picking w/o REPL - Cold
A100 0503 Pentapharm
A100 0504 Samples
A100 100A P1 WH0 - Ambient: 0100
A100 101A P1 HB - Ambient: 0101> 0103> 0100
A100 101B P1 HB - Ambient: 0101> 0100
A100 102A P1 HB - Cold: 0102
A100 103A P1 HB - Cooled: 0103> 0102
A100 103B P1 HB - Cooled: 0103
A100 104A P2 HB - Ambient: 0104> 0101> 0103> 0100
A100 104B P2 HB - Ambient: 0104> 0101> 0100
Storage Type Search Sequence: the screenshot below shows how the system derives the correct area in
the warehouse based on the PACI on the product. For example: a product that has PACI 0300 on the
product master data will be sent to search sequence 0300 when a putaway task is created (see column
Srch Seq)
Page 44 of 176
June 30, 2019
Every search sequence has 1 or more storage types assigned, for example sequence 101A will put away
goods first to storage type 0101. When that is full, the system looks for a free storage bin in storage type
0103 and when that is full in 0100.
Page 45 of 176
June 30, 2019
Storage Section Indicator

Page 46 of 176
June 30, 2019
The section indicator will be used to identify in which area the products needs to be stored. This can
depend on the product (e.g. some products may not be stored high in the racks, some products need to
be under sprinklers, ADR class products need to be stored separately in the racks...) or on the ABC
classification (Fast, medium, slow movers)
The search principle for sections is a combination of several elements:
- The section indicators:
Section
Warehouse Section Indicator Description
indicator
A100 0001 Total Section
A100 0002 > 4 Meter
A100 0003 < 4 Meter
A100 0004 A lokaties
A100 3001 Crossdock
A100 3101 Containers in the yard
A100 5001 OPA Phase 1
A100 5002 OPA Phase 1 with Sprinkler
A100 5101 OPA Phase 2 - Ambient
A100 5102 OPA Phase 2 - Ambient Level B
A100 5201 0502 - 0001 - Containment
A100 5202 0502 - 0002 - Level A-E (geen lekbak)
A100 5203 0502 - 0003 - Level F-G
A100 5204 0502 - 0004 - Fixed Bin - DG
A100 5205 0502 - 0005 - ADR 4.2
A100 5206 0502 - 0006 - Extra Section I
A100 5207 0502 - 0007 - Extra Section II
A100 5301 A lokaties
A100 5302 B-G lokaties
A100 5401 Samples - Shuttles
A100 5405 Samples - Shelves
A100 5407 Samples - Freezer
- Hazardous Rating 1: Flammability Conditions

Page 47 of 176
June 30, 2019
HazRating 1 Description
0001 Solid
0002 Liquid
0003 Liquid ESRF F1
0004 Liquid Scheme A
0005 Liquid Scheme A + Stage op Lekbak
0006 Liquid Scheme B: Opslag op Lekbak
0007 Liquid Scheme B: Opslag + Stage op Lekbak
0008 Liquid Scheme B: Opslag op Lekbak met afvoer
0009 Liquid Scheme B: Opslag + Stage op Lekbak met afvoer
0010 ADR 4.2
0011 Solid PGS15
0012 Liquid PGS15
0013 ADR 4.1
- Hazardous Rating 2: Temperature Conditions
HazRating 2 Description
T1 <= 30°C
T2 <= 25 °C
T3 8°C - 25°C
T4 <= 15°C
T5 8°C - 15°C
T6 2°C - 8°C
T7 2°C - 8°C (Do Not Freeze)
T8 <= -15°C (Freeze)
The combination of these 3 elements leads to a determined section in the warehouse, where the stock is
allowed to be stored. This determination table has over 5500 entries, it has no added value to copy/paste
that table here.
See this customizing path in the system for reference:
Tcode SPRO > IMG >

Page 48 of 176
June 30, 2019
Page 49 of 176
June 30, 2019
This is standard SAP functionality; no customer specific enhancements are used to manipulate this
proves functionality.
After an area in the warehouse is determined, the system searches for an optimal storage bin. To
optimally used the capacity of the available bins, the smallest suitable bin should be chosen for a pallet.
This avoids small partial pallets occupying high bins.
Note: this check is performed for every warehouse task confirmed on a destination, so not only put away
in the inbound process but also for internal movements.
EWM13 - Calculation of HU Height (EWM)
When determining a suitable destination bin, a calculation needs to take place in the background
checking the height of the handling unit by calculating the pallet height with heights defined in the
packaging specifications. This height has to be used to determine the best fit storage bin as a destination.
The idea is that a small pallet should be put away into the smallest suitable bin.
5.3.23.2. Confirm Put-away warehouse task
Forklift drivers passing by, pick up the handling units by scanning the HU on the Staging Area. The
warehouse worker needs to confirm the Warehouse Task by scanning the final destination bin that is
shown on the RF device. This is standard SAP functionality, no enhancements in scope.
If necessary, the operator can change the destination bin during confirmation by using an exception code
CHBD - Change Destination Bin.
Page 50 of 176
June 30, 2019
5.3.24. F1-IB-03-019 Customs posting
Data is transferred automatically from DNP SAP Q26 to GEODIS Duty Management System.
Customs is informed when goods are received in the DC in Venlo. Geodis front office registers data in the
LSP tool. LSP is software used by Geodis for customs registration.
Interface messages are also sent and received from LSP to register actions and share data.
When goods are imported into the Netherlands and they are relevant for the T-1 procedure, the MRN
reference will be registered. Based on the registration of this reference, EWM gives all the stock received
with these deliveries a separate stock type so that this stock is blocked for picking until customs has
given confirmation that this stock can be released for shipping.
This customs block is only registered and visible in EWM, deliveries can already be promised to
customers based on ATP checks in ERP.
Development: CUS01 - TP-03 Material Receipt approval request
Upon goods receipt of the goods, an interface message is sent from Q26 to LSP to request approval.
Also, to release the stock some development was done.

Development: CUS02 - TP-04 Receipt of GR posting approval
5.3.25. F1-IB-03-020 Approval for use
The GEODIS DMS will send an approval for use message to Q26. This message will also trigger an
update of the stock type in EWM, allowing these goods to be picked.
5.3.26. F1-IB-03-021 Update status to “Available”
The release of the stock by customs is only relevant for the EWM system, as the stock was only blocked
locally in the warehouse during the goods receipt process. Q26 receives the message from customs and
immediately triggers a communication to EWM to release the stock.
Development: EWM27 - Inbound process: Post from Customs Blocked to Available stock after TP-04
Upon processing the message from customs in Q26, a function module is triggered in the EWM system
which updates the stock type of the relevant handling units to available stock.
Page 51 of 176
June 30, 2019
5.4. Exception Handling Inbound
5.4.1. F1-IB-04-001 Repacking / repalletizing / (re)labelling
QC check
On material level, it must be possible that goods are sent to a VAS-area.
A Warehouse Process Type indicator and Warehouse process type will be made available to indicate that
a certain product or delivery item needs to be routed via a VAS Work Center.
When a pallet is damaged during check-in, the operator can change the destination bin during
confirmation by using an exception code CHBD - Change Destination Bin.
The operator will then scan a location in the damages area (storage type 7001) for this pallet.
001 It must be possible to mark goods as damaged systematically in EWM system during check-in
scan and route to damage area.
Page 52 of 176
June 30, 2019
002 EWM system must be able to assign a damage location within the damage storage type
automatically after damages are classified in system as damage and a put away task is created at
aquarium.
003 The storage type search damaged goods must be influenced by the stock type of the material in
the HU.
004 The damaged material must be repacked using RF.
When a new HU should be created, a new HU label should be printed.
005 It must be possible to create an inbound VAS order without routing to the VAS area to register
the activities executed before Goods receipt.
E.g. repack and repalletize.
006 It must be possible to define a material as inbound VAS relevant to route it always to a VAS
area.
e.g. Relabel / additional label ‘feed premix only’
5.4.2. F1-IB-04-002 Inbound Quality Inspection
To be detailed
Page 53 of 176
June 30, 2019
5.4.3. F1-IB-04-003 Inbound deviations
Discrepancies which can occur are shown in the table below. The quantities are examples and only
applicable if the agreed tolerances (included in the PO / inbound delivery data) are exceeded. For every
discrepancy DNP office needs to be informed.
<Design not finalized yet. Over- and under delivery is decided. Wrong product/batch to be formalized>
<Check Rik>
5.4.3.1. Missing/Under: physically not all stock is on the vehicle
Missing: a product was ordered on the inbound delivery but is not physically on the vehicle.
Under: a product was ordered on the inbound delivery but only part of that quantity is physically on the
vehicle.
When the missing/under delivered stock will be delivered within 24 hours, it will still be received on the
original delivery. GR is posted automatically from EWM to Q26 when the last stock is received in EWM.
This means all stock becomes available at that time.
When the missing/under delivered stock will not be delivered within 24 hours, the full Goods receipt will
be posted for the delivery and the stock that is physically not available, will be moved to a quarantine
zone. This zone will not be a final put away location, meaning that goods receipt can be reversed for this
stock later, if it becomes clear that it will never be delivered.
Over: physically more stock is on the vehicle than was ordered

Page 54 of 176
June 30, 2019
Overdeliver tolerance on a delivery is not accepted, so overdelivered stock will be received on a new
inbound delivery.
If the stock will be rejected later, a return order (return to vendor) and a return delivery need to be created
in Q26 and distributed to the warehouse for pickup and goods issue of the goods to the vendor.
5.4.3.2. Over quantity
If in DNP system an inbound delivery exists, an over quantity on the delivery is not allowed (financial and
quality consequences). After a check with the factory, a new PO and/or inbound delivery is created in
DNP system and goods have to be checked in on this PO and/or inbound delivery. This process can take
a few weeks at DNP side.
Additional received goods must be placed on the right location at GEODIS for several reasons
(dangerous goods + cold/frozen + no unidentified products in warehouse).
Two options in the meantime:
1. Book the over quantity on the existing inbound delivery (full traceability). Consequences at DNP
side.
2. Do a plus booking (movement type 711 in SAP) manually on a storage location / stock status
‘found at inbound’. If an inbound delivery or PO becomes available via DNP for these additional
Page 55 of 176
June 30, 2019
quantities, the additional quantities need to be booked as minus first (movement type 712 in
SAP) and checked-in afterwards on the new inbound delivery.
5.4.3.3. Wrong material
Currently Goods Receipt is done before unloading. To correct the wrong receipt of a material a material
change (movement type 309) is done.
In the new situation Goods Receipt is done after unloading. The not received material will not be booked
on the inbound delivery and DNP is informed to start an investigation.
Like an over quantity, goods have to be stored at the right condition (cold/frozen, dangerous good) in the
warehouse. System wise two alternatives could apply:
1. Create a second inbound delivery (without PO) at GEODIS without interfacing to DNP
2. Create a found booking to special storage location /stock status without interfacing to DNP
How to register in DNP system after investigation is done and goods have to be booked in DNP system
as well?
5.4.3.4. Damaged goods
Goods are only classified as damaged if the goods cannot be repacked.
In the new process, quantities are received as available stock first and rebooked as soon as possible to a
dedicated area (storage type) for damages goods. This will be done by using Exception code CHBD
(Change Destination Bin) during the confirmation of the put away warehouse task. This area is a storage
type and is reflected in Q26 as a separate storage location, thus excluding it from ATP for sales.
It must be impossible to receive materials for which the MOC procedure is not finished (material data
including base unit of measure must be complete) in EWM system.
5.5. F1-IB-12-001 Inbound: labels & documents
Document / label System Remark

Unloading Card EWM
Unloading list EWM
Internal SSCC label EWM

Page 56 of 176
June 30, 2019
6. Outbound
F1-OB-01-001 Create outbound deliveries
DNP Customer Service department will create the sales orders. DNP will create outbound deliveries
based on the sales orders.
Standard orders
The call off times and their availability of deliveries and shipments in EWM will have to be defined
depending on the outcome of the new Mainfreight interface agreements. The call off times/lead times are
in the business scenario document. Final cut-off differs per transport type.
Express orders
There is no distinction between normal orders and express orders. Both orders are using the same
delivery and sales order type. The process for Express orders is manually triggered by the CSA
contacting Venlo / Geodis + Mainfreight that this particular order is an Express order. This will also be the
case in the future setup.
In future all orders where the requested delivery date will not fit into the agreed call off / lead times
(delivery time being too short) will be treated as Express deliveries and a manual communication will take
place between Mainfreight and DNP.
Outbound Mainfreight
The outbound delivery data will be sent to Mainfreight as IDOC type DELVRY03 message SHPORD. The
IDOC has to contain all relevant data as it is today transmitted via the IFTMIN IDOC. This means that the
DELVRY03 IDOC must be extended with the new simulated packaging data as the pre-generated pack
data will not work anymore with EWM.
The deliveries in Q26 should be created and completed (batches assigned and all relevant information
maintained) as soon as possible. This would be also the timing when the IDOC should be triggered in
order to meet the agreed call off times and give Mainfreight the needed time for the transport
optimization. A way how the CSA can be supported by triggering the delivery IDOC to Mainfreight has to
be detailed out. An option could be the VL06O transaction.
The CSA’s do not have to create transport orders anymore in Q26. With the triggering of the IDOC to
Mainfreight the process is finished in Q26.
Only in case of non-Mainfreight transport orders the CSA has to create a transport order in Q26. E.g. for
BALLINA BEVERAGES where the customer picks the goods up.
Page 57 of 176
June 30, 2019
Deliveries to be shipped from external warehouses like Eurofrigo, De Rijke or Bakeplus will also be
transmitted to Mainfreight via the DELVRY IDOC. Mainfreight can differentiate the deliveries by shipping
point or storage location. The transport optimization will consider the different pick up places.
There is no differentiation for groupage or direct leg transport orders. All deliveries will be sent to
Mainfreight and Mainfreight optimizes them.
The outbound delivery data and transport order data from DNP SAP Q26 are needed for warehouse
management activities in SAP EWM. The outbound delivery has to be distributed to EWM. This can be
done with the transaction VL06d. The business can distribute the delivery
Outbound SEA and AIR
Container transport orders will be manually created in Q26. The assignment of deliveries to these
transport orders is also done manually. Once the transport order is ready, transport order and related
deliveries will be sent to EWM. Timing and trigger to be detailed later.
When the delivery has been distributed to EWM, the delivery cannot be changed in DNP SAP Q26. In
case of changes the delivery has to be confirmed with zero quantities in EWM and then a new delivery in
Q26 has to be created. This can only happen after communication with the warehouse.
Can a delivery be assigned to a transport order in Q26 when it is blocked? Can a transport order be set to
the status planned if a delivery of this transport order is blocked? Should blocked deliveries be sent to
Mainfreight? BOSS check blocks deliveries… triggering BOSS check needs discussions.
A shipment transport order always represents a physical load, this can be a truck or a container, meaning
that 1 truck or container can only exist as 1 shipment. A shipment transport order can contain multiple
deliveries.
Transport order (DSM terminology) can contain of one or many deliveries. In SAP the DSM transport
order is called shipment. In EWM a shipment is called Transportation unit. The transportation unit always
represents a truck or a container.
For Sea and Air transports, it is possible that multiple transport orders are created in Q26 for 1 physical
container or truck. In this case, a transportation chain will be created in Q26 and 1 grouped transport
order will be created to inform the warehouse (EWM). EWM always gets only 1 transport order per
physical container/truck (1:1 relationship)
In SAP EWM a transport unit is created based on the EWM relevant shipments from Q26 and pre-
advice data of the forwarders for ROAD/Mainfreight.
DNP SAP Q26 SAP EWM Remark

Outbound delivery Outbound delivery
Page 58 of 176
June 30, 2019
Shipment Transport Unit Transport Unit corresponds to a Q26 shipment; 1:1 relation.
For 1 physical truck or container only 1 shipment is
communicated to EWM.
The delivery interface from Q26 to EWM is a standard SAP qRFC interface which contains all relevant
delivery information.
Pre-generated pack data
Today in Q26 the system works with so called pre-generated pack data. The delivery is being pre-packed
based on information of certain Z-tables and a certain logic. Pack data is currently only available in DNP
Q26 for full pallets and layers and NOT for less than a layer (‘unpacked’ in the outbound delivery), except
in case materials are packed manually. This means the information is incomplete in case of less than a
layer. Additional functionality is built in DNP Q26 in the logic of the picking list an all other documents
where quantities less than a layer are shown as loose cartons. This functionality will not be used anymore
in the future because EWM functionality is available as replacement. SAP does not allow the packing of
deliveries for storage locations managed by EWM.
New way of working:
Whenever in Q26 a delivery is saved, the system will call the EWM to perform a simulation of the
packing.
This information will be stored in custom table.
Development: ECC05 - calculation for container shipments / Mainfreight now done by PGPD (to support
CSA in future)
The users will get a custom transaction ZPACK where they can review the simulated packing.
They will see the delivery and each item of the delivery. For each item the number of pallets, boxes,
drums and the corresponding weights and volumes will be shown. This will always be valid for EWM
managed storage location all other storage loactions will use the SAP standard POP/POF transactions.
The users will have the possibility to re-pack this packing proposal. This repack information will be saved
and will trigger a VAS instruction to the warehouse that this delivery will deviate from the standard
packing.
In this case, GEODIS will print the packing instruction a paper instruction or show the instruction on
screen in a pack center to inform the operator how to pack. These deliveries deviating from the standard
packing rules, will be guided via a pack center to guarantee that an operator can pack accordingly.
Page 59 of 176
June 30, 2019
In all other cases, GEODIS will follow the standard packing specification per customer and per material
as received from DNP.
Additional functionality to be provided in the transaction ZPACK:
- Calculate the total on selected OBD’s:

o Select the OBD’s to calculate the total, total will be then presented in a separate line.
o Helps to decide if a combination fits in a container.
o Gives you an overview on total weights (Net, Gross and Tare) and volumes (Net, Gross
and Tare).
- Change packaging data in table “ZPACK” and VAS Code:
o If DSO/CSA wants to deviate from the standard he/she can adopt the packaging data.
The intention is then also transfer this to the text field for VAS-coding in the outbound
delivery to inform the warehouse on the deviation.
- Print transportation disposition sheet:
o Print- or reprint outbound documents to support the existing way of working.
- Create shipment on selected OBD’s:
o Based on the selected outbounds a shipment can be created.
DNP will send the packaging instruction to GEODIS as well in specific fields on the delivery. This will be
used by EWM to derive the correct packaging specification. The VAS instructions have to be transmitted
to EWM, today this are outputs in the delivery.
The existing outputs in Q26 using the pre-generated pack data will have to be adjusted to read the new
custom table information and use this information on the outputs.
For external/overflow warehouses and M&T sites where apparently also the pre-generated pack data is
used, the idea is to use the packing instructions from SAP standard.
When packing is completed, GEODIS interfaces the packed handling units to DNP Q26 (before loading
and goods issue). DNP Q26 should be updated accordingly.
F1-OB-01-002 Reversal processes on outbound deliveries
Picking can be cancelled for outbound deliveries, and outbound deliveries can be set to zero in EWM.
This will allow to create a new outbound delivery if needed.
F1-OB-02-001 Release outbound deliveries to Forwarder
Forwarder will get the outbound delivery data from DNP. Forwarder creates a complete planning with
these data. Outbound deliveries are combined into one truck load while optimizing the transport routes.
Page 60 of 176
June 30, 2019
Mainfreight: interface
A way how the CSA can be supported by triggering the delivery IDOC to Mainfreight has to be detailed
out.
Sea/Air: PDF/e-mail
The SEA/AIR transport orders which are created manually in Q26 will be released and communicated to
the forwarder as today either via the interface for BDP and e-mail for Rhenus and others.
F1-OB-03-001 Receive planning from Forwarder
Mainfreight
Forwarder creates final outbound planning and sends planning to DNP. This will be the so-called load
plan. This load plan will contain the Q26 delivery numbers, a simple loading sequence, a reference
number to the Mainfreight shipment and a pickup date + time + some possible additional information. This
has to be detailed out with Mainfreight and business.
This load plan will be an XML file which will be sent to the DSM middleware Webmethods. In
Webmethods this XML file will be transformed into a SHPMNT05 IDOC/ message SHPMNT and will be
passed to Q26 system.
This IDOC will create the shipment in SAP, shipment type 0011 (collective road). The shipment will
contain the mentioned information from the XML file. Additionally, a HU of the type Truck will be assigned
to the shipment in Q26. This allows the automatic TU creation in EWM when the shipment is transferred
to EWM.
The shipment in Q26 will be created/saved in the status “planning complete”. The status “planning
complete” will trigger two new outputs. One output ZEW1 will distribute all deliveries of the shipment to
EWM (in case they are not distributed). The second output will be the ZEWM output, which will transfer
the shipment to EWM as IDOC SHPMNT05 message SHPMNT. In order that the TU will be automatically
created in EWM all deliveries of the TU + a main HU (Truck) have to be assigned and must exist in EWM.
As a result of this flow the Q26 shipment and the EWM TU will have the same information / outbound
deliveries attached. Today Mainfreight sends an Excel sheet in which all deliveries are grouped into
truckloads, this Excel could be temporary used to create the shipments manually in Q26 until the
interface is in place. Discussion with Mainfreight started.
All other road shipments e.g. DHL Express and customer pickups will be manually created in Q26
Once the TU is processed in EWM a change message will update the Q26 transport order with certain
statuses (e.g. loading start / loading end/ truck arrival and so on). This is to be detailed.
During the processing of the transport order in Q26 two messages will be sent to Mainfreight. Those
messages correspond to the already today transmitted SEDI message. The first message (preliminary
Page 61 of 176
June 30, 2019
call off) will be triggered once all deliveries of the shipment have been packed in EWM and the packaging
information has been transferred to Q26. Packing status of the deliveries is “C” completed.
The “loading end” status in the Q26 shipment will trigger the second, the final call off message for
Mainfreight.
The external warehouses will not send the preliminary call off and final call off message to Mainfreight.
The packing information is not available for those warehouses and therefore the message does not have
any added value.
Page 62 of 176
June 30, 2019
SEA and AIR shipments
Still to be described
Return orders for GDC and external warehouses
The return order process will be handled as today. The CSA have to create a return order / delivery in
Q26. The return delivery will not be transmitted via IDOC to Mainfreight, this is a potential after go-live
improvement.
Mainfreight must be informed about the return delivery via phone / mail. Same communications channels
as today. There is no differentiation in the process, external and Venlo warehouses are treated the same.
Page 63 of 176
June 30, 2019
In case of an external warehouse the grey boxes are not applicable, as they are not assigned to EWM.
F1-OB-04-001 Create Transport Unit
When Outbound Deliveries are planned in an EWM-relevant shipment in Q26, a Transportation Unit is
created automatically as corresponding object in EWM.
In ECC the Outbound Deliveries are assigned to the Shipment and Whenwhen these Outbound
Deliveries are planned in an EWM-relevant shipment in Q26, a Transportation Unit is created
automatically as corresponding object in EWM.
Bboth objects deliveries and shipment are interfaced to EWM. In EWM the corresponding Outbound
Delivery Order(s) and the Transportation Unit (TU) are created with the corresponding assignment.
The HU Truck will be automatically assigned to the Q26 transport order when the loading plan from
Mainfreight is received and processed in Q26.
For all manual created road transport orders in Q26 e.g. DHL Express and customer pickups, the HU
(Truck) has to be assigned manually before releasing the transport order to EWM.
For SEA and AIR shipments the corresponding HU type (20/40-foot container, cooled) has to be manually
assigned to the transport order. This is already done today in Q26.
Page 64 of 176
June 30, 2019
In Q26 two shipments will exist for SEA/AIR shipments. A main leg shipment, which will be used to
communicate to the carrier and a subsequent leg shipment which will combine all main leg shipments for
one truck. This subsequent leg shipment will be communicated to EWM and used for the TU creation.
In all cases, the shipment/TU should be known in the warehouse before picking starts. This will allow
more efficient usage of the staging areas which are too fragmented today, leading to space constraints.
Send loading reference to Forwarder
When an outbound transportation unit is created in EWM (based on the shipment coming from ERP),
automatically also an appointment is created in DAS. The ERP shipment number is also used as external
TU number in EWM and registered automatically as Means of Transport ID in DAS.
This standard SAP functionality provides 1 close linked reference number between shipment-TU-
appointment across the 3 systems. This reference can also be communicated to BPD, Rhenus… as
reference for the driver.
Mainfreight reference
Mainfreight has requested to use their own reference. Solution to be designed
Warehouse planning will send loading reference to forwarder. <Check Karsten>
If necessary, it is also possible to create a TU manually in EWM, also for parcel deliveries. In this case,
the TU will be communicated to Q26 at GI and this will create the corresponding shipment in Q26.
If multiple deliveries are assigned to a TU, a loading sequence can be added manually.
F1-OB-04-002 EQ Inspection required
It must be possible in the system to mark shipments with ‘EQ inspection required’.
Shipments must be prepared one day before shipping to be checked by DNP.
EQ = External Quality.
Only needed twice per year.
F1-OB-04-003 Hub address
It must be possible to add a hub address on a shipment in the system for groupage shipments.
F1-OB-04-004 Outbound Shipment data
It must be possible to register the following outbound shipment data in the system:
- driver name
Page 65 of 176
June 30, 2019
- ID number
- licence plate
- container number
- seal number
- stowage weight
- tare weight of container
Development: EWM15 – Transaction for TU Details
A custom transaction code is built to facilitate the registration of the needed data on the outbound TU’s.
F1-OB-05-001 Create Wave
To optimize the use of resources, Outbound Delivery Orders are automatically assigned to a Wave upon
TU creation.
EWM14 - Wave Building
A custom enhancements is built to
- influence the description of waves (for transparency in the monitor)

- to enable creation of 1 Wave for a whole TU.
F1-OB-05-002 Release Wave
The EWM system is able to create warehouse tasks for multiple outbound deliveries at once. This can
either be done from the monitor or by releasing the wave for those deliveries. In practice, releasing a
wave is equals creating pick tasks for all the delivery items assigned to that wave.
Wave release can be done manual for 1 or multiple waves at the same time.
Waves can also be released automatically, based on a defined date/ time in the wave templates. This
means that waves are automatically released based on the date&time they should be ready for pick up.
Page 66 of 176
June 30, 2019
During wave releasethe wave release log is displayed. This log:
- informs the user if all picking tasks could be created

- if tasks could not be created, this log shows the reason why. This could be a stock shortage but
this can also be because the replenishment was not yet executed for the partial pick. Wave
release will look for partial picks in the OPA (Open Pick Area) which needs to be replenished
prior to pick task creation).
It must be possible to distinct express orders from normal orders in the system to be able to give priority
to all warehouse tasks.
The EWM system must be able to create warehouse tasks without assigning a specific handling unit for
external container storage (smelling, quarantine).
It must be possible to cancel picks for (part of) a delivery:
• Full line cancellation

• Partial line cancellation
• Partial pallet cancellation (repack and cancel)
Without the need of complete roll-back of the materials to (high bay) stock.
The system must be able to route outbound goods via VAS area automatically for VAS relevant
materials/deliveries to (re)label, re-palletize, repack.
Some VAS codes are not relevant for activities in a work center. The system must pick directly to staging
area.
It must be visible that these delivery items need a VAS activity.
Picked handling units from OPA which need a VAS activity after picking must be sent to a specific work
center of the order pick area.
The system must be able to create warehouse tasks from VAS area to staging area per Handling Unit.
The system must be able to route a delivery item to the VAS area if DNP has indicated with a VAS code
that the delivery is not packed according the generally agreed rules.
For a cross dock delivery, the system must look for stock in the cross-dock area first.
F1-OB-06-001 Replenishment to pick bins and reverse replenishment
In DC North, the pick bins will be replenished based on requested quantities on open deliveries (Order
Based replenishment). This is standard SAP functionality. This standard functionality also includes a
Page 67 of 176
June 30, 2019
creation log for the replenishment tasks, showing information about failed task creation (e.g. due to lack
of empty spaces in the destination area).
There are 2 pick areas that are filled with the replenishment process. This will be guided with standard
SAP setup and master data (Storage Type data on product master). The search strategy for
replenishment will look for ascending quantities, meaning that partial pallets will be chosen for
replenishment first. All tasks in the high bay are automatically added to queues, the queue setup and
queue (type) sequence will be used to give a higher priority to replenishment over normal pick actions in
the high bay.
The OPA areas are too small to store all pallets needed. A ‘reverse replenishment’ process will be setup
to bring leftover pallets back from pick area to high bay after picking is done.
It must be possible in EWM system to scan replenishments as well as reverse replenishment to a drop
zone (to remove seal) before scanning to the destination location.
Development: EWM17 – Batch specific replenishment
DNP sends deliveries to the warehouse with a preselected batch in the delivery. It is mandatory for the
warehouse to pick this specific batch. Therefore, an enhancement is needed to replenish the exact batch
requested in the outbound delivery.
Development: EWM21 - Reverse Replenishment monitor with function to create WTs
Because of space constraint, there are not enough pick bins to leave the remaining stock in the pick bins
after picking. Before performing replenishment for the next shift, a report will be run to see how many pick
bins need to be made available by returning the stock back to the high bay. The reverse replenishments
will be guided via a work center so that a label can be printed for the pallets. This label will then have the
correct quantity and the row number of the destination bin in the high bay.
Page 68 of 176
June 30, 2019
F1-OB-07-001 Pick task creation and removal strategy
Pick tasks are created by releasing the wave. If no wave exists, pick tasks can also be created manually
from the outbound delivery order. The release of the waves is done manually. During pick task creation,
the removal strategies are determined to find the best suitable stock. EWM provides several ways of
determining the proper bin for picking. The backbone of the process is the Warehouse Process Type
derived on the outbound delivery order. The warehouse process type determination can be influenced
with different elements such as:
- Control Indicator for Process Type Determination: This is an indicator on the general data of
a product and can also be used in the inbound process. It is intended to derive a specific process
type for a combination of (in-/outbound) document and product.
- The stock removal indicator can also be used to derive a product specific picking strategy. This
is indicator is intended specifically for stock removal. It is used in the determination of a Storage
Type Search Sequence for Stock Removal
Using these indicators, the system determines the removal strategies:
 Storage type search strategy: where to find the product in the warehouse
 Stock removal rule: how to prioritize the stock that was found
The created warehouse tasks are assigned to queues. If an operator works system-guided on his RF
device, the orders and tasks are presented in the sequence of the latest start date. So, the picks that
need to be ready first, are presented first.
If something needs to have a high priority due to shifted planning, the workflow controller can assign
warehouse order to queue priority. This way these WO’s will be presented first. The operator can also
logon to the queue priority specifically.
EWM system must be able to prioritize picks automatically in OPA (Order Pick Area) based on outbound
shipment planning (date/time) and expected lead time including VAS.
Picking tasks can be created from all relevant storage types in the warehouse: high bay, OPA,
containers, open storage…
WT’s to pick HU’s from containers will only request product, batch and quantity. The operator will be free
to scan any HU in the container that matches the request.
Picking tasks are created based on the requested quantity, this means that full pallets are picked from the
high bay and partial picks are picked from OPA. EWM Storage Control automatically sends you stock to a
Page 69 of 176
June 30, 2019
work center if needed (for example for VAS activities). If no actions are required, the HU can go straight
to the staging area and an HU print can be triggered on RF.
Picking from high bay will pass by a front bin, this is steered with so called “Layout oriented storage
control”. Everything in and out of the narrow aisle of the high bay then passes by an intermediate bin.
Where this is not necessary, the system makes 1 task from source to destination.
EWM system must be able to create separate warehouse tasks for:
- Full pallets: one task per source location respecting the pallet quantity in the master data.
- >= 1 or >= multiple Layers (less than full pallet): one task per source location. One warehouse
order per material.
- Loose cartons only (less than 1 layer): one task per source location. One warehouse order per
delivery.
During picking, the operator can use exception codes on RF to register a pick shortage or to move the
picked handling unit to the damages area. In this case, it will be visible on the delivery and the
transportation unit that this handling unit is in not in the staging area.
Picking for so called “cross dock deliveries” will search for stock in the cross dock area first, before
looking in the regular stock. For the operators there is no difference in the process, only the source bin is
different. (Picking from cross-dock area)
Picks can be cancelled on HU level and above (a line cancellation equals cancellation of multiple HU’s).
Standard transaction code /SCWM/CANCPICK is used for this process.
If a partial pallet of the exact requested quantity is available in the high bay, it must be possible to pick it
from high bay to VAS or SA directly without replenishment via OPA.
Materials that are not picked via the OPA’s will have a separate process.
- Some products can be picked from the bin (e.g. Pentapharm, ADR…).
- Drums will be picked via a pick point instead of with
When full pallets are picked, no packing material needs to be entered on RF, for partial pallets this is
necessary. The process starts by creating an empty HU of the correct packaging material.
Developments:
EWM05 - WO per product
EWM10 - Read packspec based on fields in delivery
EWM11 - Print HU function in RF

Page 70 of 176
June 30, 2019
The storage type search strategy
Finding the correct storage type in the warehouse is determined by several parameters:
- The stock removal indicator

- Warehouse process type
- Quantity Classification
- Stock Type
- Stock Usage
- Hazard Rating
During picking also, physical aspects of the warehouse are considered, for example in the high bay. The
aisles in the high bay are only accessible for the reach trucks, movements outside of the high bay are
performed with forklift trucks. In EWM, Layout Oriented Storage Control is used to define if stock needs to
be moved via intermediate locations.
Apart from selecting the best suitable stock, EWM also takes rules into account to optimize handling on
RF. The system follows the following logic for Warehouse Task creation at wave release for Outbound
Delivery Orders:
1. Task split based on quantity classification

2. Warehouse Order creation based on
a. Source and Destination
b. Max number of warehouse tasks (e.g. full pallet pick is 1 WT in 1 WO. Colli pick on a pick
handling unit will group all tasks in 1 WO)
3. Pick HU creation per Warehouse Order.
Since HU’s are mandatory in EWM, the system proposes pick-HU creation depending on the type of pick:
 Piece picking – The operator needs to create a pick-HU on the Radio Frequency device and performs
piece picking into the pick-HU.
 Pallet picking – No pick HU creation needed; the source HU is re-used as pick-HU.
As soon as a Warehouse Order with picking Warehouse Task(s) is created, it is added to a queue
defined for outbound. The warehouse worker logs on to this queue and executes the first Warehouse
Order assigned to him.
Per Warehouse Order the system guides the Warehouse Worker through the followings steps:
Full pallet pick
1. Scan source handling unit (= the pallet to be picked)

2. Scan destination location
For full pallet picks, the pallet can either be:

Page 71 of 176
June 30, 2019
- Sent to pack center for repacking or VAS activities (See chapter Error: Reference source not
found)
- Sent immediately to the staging area. In this case the operator needs to print the logistics label
and apply it to the pallet.
During picking activity, the high bay operations must to be optimized so that pick and put-away operations
can be combined (interleaving).
It must be possible to move the picked HU to different destinations in the warehouse depending on the
next step in the process (e.g. pick, vas, stage…).
It must be possible to send a picked Full Pallet directly to a staging area,
When moving a full pallet directly to staging area, the printing of the shipping label should be triggered
automatically.
Full pallets that require VAS activities must be sent to a work center automatically.
It must be possible for to send a full pallet pick HU directly to destination merge/repack for doing the
merge / repack activities.
Partial pick with replenishment (COLLI/LAYER)
Partial picks for regular products are guided via the picking area with an order based replenishment
process (See chapter 7.4.4). The picker in the picking area get the following steps on RF:
1. Pick-HU creation (based on pack specs, the correct pallet type can be proposed)
2. Confirmation of picking Warehouse Tasks into the pick-HU
3. Confirmation of the move of the pick-HU to the destination bin by scanning.
For partial picks from the picking areas, the destination will always be one of the 2 OPA Work Centers.
- When no VAS activities are required, the HU is sent via Work Center OPA I where the logistics
label will be applied.
- When additional label activities are required, the HU is sent via Work Center OPA II where the
necessary actions can be executed.
- In case specific manual packing is instructed by DNP (deviating from the pre-generated pack
data), the HU will be sent to the work center PACK where an operator will repack based on the
delivery-specific instruction of DNP.
If a partial pallet of the exact requested quantity is available in the high bay, it must be possible to pick it
from high bay to VAS or SA directly without replenishment via OPA.
It must be possible for a partial pallet pick HU to send directly to destination VAS area where the HU
requires value-added services.
It must be possible to pick less than a full pallet (layer, loose cartons/bags) from the bin in the high bay
area for specific materials.
Page 72 of 176
June 30, 2019
These materials will not go via the OPA (Order Pick Area) but will be picked from the bin.
It must be possible to pick drums (not full pallet) from a bin without replenishment. (pick point).
EWM system must support a process to join partial pallets to full pallets and/or layers including multiple
batches
Partial picks must start with empty handling unit of correct packaging material.
Partial pick via Pick Point (DRUMS)
Partial picks for DRUMS are not guided with a replenishment process. Drums need to be picked with a
specific device, this would cause unsafe situations in the picking area and needs to be done in a separate
area called a Pick Point. This process is also guided with Layout Oriented Storage control in combination
with the usage of a specific HU Type Group.
1. Warehouse task is automatically split into 2 movements. Movement 1 is moving a full pallet pick to a
Pick Point
2. Pick-HU creation in the pick point (based on pack specs, the correct pallet type can be proposed) <to
be detailed more in detail design phase>
3. Confirmation of picking Warehouse Tasks into the pick-HU
4. Confirmation of the move of the pick-HU to the destination bin by scanning.
5. The remaining stock of the pallet can be returned to stock.
For partial picks from via pick bins, the picked goods could go straight to the staging area, or via a work
center.
- When no VAS activities are required, the HU is sent straight to the staging area and the forklift
driver applies a Logistics label.
- When additional label activities are required, the HU is sent via Work Center Label where the
necessary actions can be executed.
- In case specific manual packing is requested by DNP (deviating from the pre-generated pack
data), the HU will be sent to the work center PACK where an operator will repack based on the
delivery-specific instruction of DNP.
Cold storage 2A Picking
<Old text from plan A, to be updated during detailed design>
There are 3 types of picks from this area:
 Full pallet picks

 Partial pallet picks (cold materials)
 Partial pallet picks (overflow materials from other storage types)
Page 73 of 176
June 30, 2019
o Partial picks for cold materials from this area will not go via the OPA (Picking area) but
instead will be picked near the racks after which the remaining stock will go back into the
rack.
o A Pick-point will be used to support this process. The flow will be as following:
High Rack  Front drop-off  Pick-point  Staging Area
o The remaining materials will move back from the pick-point to the rack storage.
Note: The process of using a pick-point does NOT apply for partial pallet picks for materials that are
natively not stored in the cold storage area, but thus are overflown from other storage types. Those
materials should follow the picking process that always flows via the OPA area. (By using a different
removal indicator for those materials, this should be steerable.)
Picking shuttles
<to be completed>
Picking Pentapharm
<Old text from plan A, to be updated during detailed design>
The process of using a pick-point is also applicable for the Pentapharm materials which are stored in Hall
4.
Specify Stock Removal Rule
The stock removal rule can be based on the different characteristics, including SLED (shelf life expiration
date), Quantity, GR Date and Storage bin sorting. In the DNP warehouse however, the batch will be sent
with the deliveries and therefore no pick sorting needs to be done based on batch and stock related
dates. The main influencing factors are:
- Quantity (e.g. Full or partial pallets)

- Bin sorting (e.g. influence pick path)
Whse Rem. Rule Description

A100 AQUH ascending quantity (HU)
A100 AQUP ascending quantity (piece)
A100 DQUH descending quantity (HU)
A100 DQUP descending quantity (piece)
A100 FEFO First expiration date First out
A100 FIFO First In First Out
A100 LIFO Last In First Out
Page 74 of 176
June 30, 2019
F1-OB-08-001 VAS Activities in outbound process
In Q26 the fields KNVV-KVGR3 holds the pallet requirements on customer level.
The field MVKE-MVGR3 holds the pallet requirements on material level. They are copied into the sales
order and delivery fields LIPS-KVGR3, LIPS-MVGR3.
Today the VAS services are stored in Q26 in the delivery/sales order as separate outputs using the SAP
output condition technique. The condition record of the output holds the VAS information/instruction.
Output condition records YSP1 until YSP9 plus YSH1 contain the VAS instructions. The two fields
“Recipient” (e.g. label code) and “Cover page text” (VAS instruction text) hold the details.
In addition, a VAS-code (4 or 5 characters) needs to be send to GEODIS (e.g. LAB01). DNP to update all
VAS condition records in Q26 with the new Geodis VAS code in the “SUFFIX2” field of the condition
record. New codes to be provided by Geodis. Clean-up activity to be done by DNP for not used VAS-
condition records.
The VAS code + the fields “recipient” and “cover page text” to be transmitted to Geodis for each of the
applicable VAS codes (YSP1 until YSP9 plus YSH1) per delivery item. This will be most probably
additional fields at the table LIPS. Those fields will be sent to EWM via qRFC interface. If necessary, this
queue will be extended with these fields.
When the OBD delivery from Q26 is distributed to EWM as so called outbound delivery order (OBO) will
be created in EWM. Upon Outbound Delivery Order creation EWM evaluates the Value-Added Service
(VAS) relevance for the ODO customer/article combination and creates the relevant VAS-order if needed.
In case VAS (special packaging instructions) is required, a VAS-order needs to be created for the ODO
item line. To create the VAS-order in EWM a corresponding VAS packaging specification needs to be
maintained in the EWM master data. The actual VAS-order creation is done automatically when the ODO
Page 75 of 176
June 30, 2019
is created (structured VAS) or needs to be done manually after the ODO is created in EWM (ad-hoc
VAS).
If a VAS-order exists for the underlying ODO line(s), the VAS-step is triggered and a VAS Work Center is
proposed as destination bin for the HU. If a HU is relevant for repack and VAS, it will be routed to the
repack station only. No move to second a VAS work center is needed because VAS can be done in the
same (repack) work center. At the VAS Work Center a warehouse worker physically executes the VAS
steps as described in the VAS-Order. When all VAS is executed, the warehouse worker needs to confirm
the VAS-order and close the VAS process step in the Work Center (desktop). This will trigger the creation
of a Warehouse Task for Staging (towards the staging area). The shipping label can already be applied in
the work center, or the forklift driver can print it. Pallets move from work center to staging area per HU (1
WT per HU)
If a VAS-order does not exist for the underlying ODO line(s), the Staging Area bin is directly proposed as
destination bin.
<All VAS information and flows to be added in detailed design phase>
If a specific pallet type is required in the outbound delivery (repalletizing), goods are repacked to the
required pallet type and height. This activity takes place in the VAS area.
In the specific case of deliveries that need to be packed differently than the agreed rules, the office will
send a specific VAS code so that all stock is sent to a work center, where the operator will see the text
entered by the office on how to pack these goods manually.
If an operator wants to manually (ad hoc) repack a pallet, he can do this in any work center. No delivery is
needed for this, if it is non delivery related repacking.
It must be possible in the OPA work center to confirm picked quantity (after blind count).
It must be possible to use staging areas as temporary VAS area in EWM system.
Picked handling units from OPA which need a VAS activity after picking must be sent to a specific work
Development: EWM10 - Read packspec based on fields in delivery
Based on customer/material rules, DNP will send us the expected packaging material for a delivery line.
This allows Geodis to derive the correct pack spec for warehouse task creation and process handling.
Various special packing instructions can apply. Examples:
 Pack in styrofoam box

 Extra strapping
 Extra foil
Page 76 of 176
June 30, 2019
 Add top covers

 Other instructions (add instruction paper, send labels to DSO etc.)
If goods must be relabelled at outbound, a VAS code and corresponding text instruction are sent in the
outbound delivery. All VAS instruction of the delivery (which can be multiple instructions per item) have to
be send to EWM via the SAP standard qRFC interface. This will require some additional development in
Q26.
GEODIS will process the relabel instruction in the outbound process via the VAS/relabel area.
The Q26 VAS instructions have to be stored in EWM and also displayed to the Warehouse user on the
SAP screen and also on RF. This will require some additional developments.
Development: EWM01 - Outbound VAS Enhancements + Display of VAS text instruction
(ECC+EWM)
Q26 will send VAS Codes on delivery items indicating what VAS activities are requested for that delivery
line. These indicators will be received via qRFC into PEW and need to be mapped towards EWM fields.
<to be completed>
Development: EWM03 - VAS status on header level
VAS Status is only visible on item level in standard SAP. This development will reflect the aggregated
VAS status on header level of the delivery and in the EWM Monitor.
Picking specific packaging numbers for quality check
On average weekly, a specific packaging (box, bag, can, ...) number needs to be picked of a batch that is
not released yet for outbound orders. Packaging numbers are not registered anywhere so possibly all
pallets in stock need to be checked until the packaging number is found. GEODIS will be instructed by
email for this value-added service. GEODIS processes the request manually (manual warehouse tasks
from and to stock). As soon as the specific packaging numbers are collected in a specific area (e.g.
crossdock area), an outbound delivery is sent by DNP to ship the goods. The correct stock will be
assigned. Material – batch combination is blocked for other sales orders anyway.
Four eye check requirements for VAS activities
A four-eye check (second person of GEODIS needs to check the correctness and completeness) if
needed for many value added services. Currently this is manually triggered. System support would be
beneficial.
Four-eye check
Page 77 of 176
June 30, 2019
A four-eye check (second person of GEODIS needs to check the correctness and completeness) if
needed for certain.
Table below gives the main four-eye checks, which will be put in place.
All 4-eye checks are executed, and the proof of the check is done on paper.
The 4-eye check on customer specific label needs to block the warehouse activities.
Only when a formal check is executed by the DNP Dangerous Goods Specialist the block can be
removed.
Printing Label procedure Operator 4-eye check Apply label check I Check II Checked data Reference
Global Product label 6.0.04 VAS operator Yes VAS operator VAS operator Material#, Batch#, Man. Date, Exp. Date, Weight. Label assignment, SAP
Shipping label 6.0.03 Forklift Driver No Forklift Driver Material#, Batch#, None
Shipping label 6.0.03 VAS operator VAS operator operator II Material#, Batch#, Global label
SUID label inbound VAS operator / Scanning operator No VAS operator / Scanning operator
ADDITIONAL LABEL
Re-analysed label 6.0.04 VAS operator Yes VAS operator VAS operator Material#, Batch#, Man. Date, Exp. Date, Weight. Label assignment, SAP
Shelf life extension label 6.0.04 VAS operator Yes VAS operator VAS operator Material#, Batch#, Man. Date, Exp. Date, Weight. Label assignment, SAP
Customer specific label 6.0.12 VAS operator Yes VAS operator VAS operator cust request Picklist
Special label (e.g. Feed premix only) 6.0.06 VAS operator No VAS operator cust request Picklist
Dangerous Goods label 6.0.08 VAS operator Yes VAS operator DNP Dangerous Goods Specialist Correct symbols/picto's Picklist
Additional label (e.g. Do not stack) VAS operator No VAS operator
<content proposed solution document to be added>
F1-OB-09-001 Staging
Requirement of limited staging need to be considered (e.g. containment, material stored in phase 1 of the
building has to be staged in phase 1, and others which is to be detailed out in the Functional Design
phase).
Packing
Page 78 of 176
June 30, 2019
When picking full pallets, the pack step is confirmed automatically in the process, when picking from a
pick bin, the pack step is confirmed either in a work-center (e.g. when VAS activities are needed) or by
confirming goods onto your pick handling unit.
When all packing is done for a delivery, an interface will be triggered towards ECC and further on to DNP.
This interface will contain the exact packing information (SKU, Batch, quantity, packaging material and
SSCC). This information allows DNP to generate all necessary documents for the delivery.
Staging
The operator needs to confirm the Warehouse Task for Staging by scanning. Staging in DC North is
guided from the operators on the floor. This means that the operator gets a warehouse task with only the
destination storage type and he is free to choose a bin on a staging area. As soon as the first HU is put
onto a staging location, the remaining pallets for that delivery are guided to the same bin.
If there is a restriction to where the product can be staged (contained area), the system will automatically
propose this area for the pallet being staged. All other handling units for the same destination will
automatically be sent to the same staging area as the one that was chosen for the first pallet. It is
possible to assign multiple staging area bins (for example, when the first one is full)
Development: EWM20 - Staging Area determination from RF on wave level
Because multiple deliveries have the same destination, the functionality of automatically sending pallets
with the same destination to the same staging area needs to be enhanced. Standard SAP only sends
pallets of the same delivery to the same bin. Here we need this functionality on a higher level, i.e. the
wave that contains the delivery. Pallets for the other deliveries of the same wave also need to be sent to
the same staging area.
If the delivery is already contained in a TU, then all pallets for all deliveries of that TU need to be sent to
F1-OB-10-001 Perform Dangerous Goods air delivery activities
DGR Air shipments require additional checking. DGR Air shipments may not be loaded before they are
checked by DNP.
When the warehouse has packed an outbound delivery, the outbound delivery will have the status C in
both SAP EWM and SAP ERP Q26.
Status C is the trigger for DNP to print a report with Packed Dangerous Goods air deliveries. The report is
used for the physical check on the staging area in the warehouse. After the check DNP, DNP will approve
the delivery and will sign the forms. Warehouse planning will receive the DG approval forms and will
archive the forms.
Development: ECC09 - Report packed air shipments for DG labelling check

Page 79 of 176
June 30, 2019
F1-OB-11-001 Update of packaging information in Outbound Delivery
EWM must update the Q26 outbound delivery with the packing information when in EWM the packing
complete status is set.
Once the packing in EWM is done, this information will be transferred into ERP via a Post Process
Framework action. This will update the ERP delivery with the picked and packed HU’s, quantities and
batches. This will be a copy of the SAP standard goods issue PPF without posting a goods issue. The
status of the ERP delivery will change to packed complete. The goods issue of the ERP and EWM
delivery is still open.
Development: EWM12 - Send packaging data at packing complete
F1-U1-12-001 Loading
The Loading step needs to be executed when the Outbound Delivery Order for the HU is assigned to a
Transportation Unit. The Warehouse monitor provides an overview of where the picked pallets are, this
allows to choose a suitable door.
When the TU is physically at the warehouse the Shipping Office docks the TU at a door and creates the
loading Warehouse Tasks for the assigned ODO’s. The operator does the loading by scanning every HU
to the assigned door. When he scans a handling unit that is not for this transportation unit, the system
displays an error message.
When all loading Warehouse Tasks are confirmed, the status of the TU needs to be set to ‘Finished
Loading’. Therefore, the system will prompt the warehouse worker (RF) to set the TU status to ‘Finished
Loading’ as soon as all loading Warehouse Tasks are confirmed. When loading is done in the desktop,
the end-user is not prompted to change the TU status (but is also mandatory).
Loading can be reserved if this is needed (this should always be an exception)
It is possible to create nested handling units on the staging area to make the loading process more
efficient. In this case it is enough to scan the top HU to the TU in 1 move.
The system must prevent loading for the whole shipment when picking, packing or VAS activities for part
of the shipment are not finished (no direct loading).
F1-OB-12-002 BOSS check
Development: EWM18 - Boss check Delivery block
<to be added>
Today a delivery block is set in Q26 when a certain batch should not be distributed. If the transfer order is
already created a block is send to TLS to prevent the picking/goods issue.
Page 80 of 176
June 30, 2019
All delivery blocks have to be checked and analysed what should happen also with regards to the
distribution of deliveries to Mainfreight. What should happen?
Procedure:
• Delivery block indicator is set

• Transfer posting in Q26 triggers interface to EWM to block certain deliveries.
• Deliveries are only blocked in EWM for loading (not blocked in SAP Q26)
F1-OB-13-001 Post Goods Issue & Truck Departure
When goods are shipped, goods issue will be posted in EWM, automatically triggering GI in Q26.
The shipment will be confirmed automatically when the last delivery is confirmed, and this will trigger the
goods issue interface to the forwarders. This to be confirmed with Mainfreight
After the TU status is set to ‘Finished Loading’, the Shipping Office needs to undock and departure the
TU. The departure will trigger the Goods Issue Posting for the HU assigned to the TU. The goods Issue
Posting takes place in PEW and is automatically communicated to Q26 by qRFC. As a result, the relevant
shipping documents are printed in ECC (output is described in chapter ‘Output‘).
F1-OB-14-001 Outbound documents
The following labels and documents are used for outbound shipments. All documents will be in English
only.
<Table to be completed with all forms, documents, labels>
Document / label System Remark

Logistics label GEODIS SAP Incl. SSCC code. In the new situation GEODIS
will print the logistics label. The requirements
regarding the label must be given by DNP.
Special labels PAGO Printed via standalone system Pago (no
change)
Delivery note DNP Q26
Invoice (non-EU only) DNP Q26
Customs documents (non-EU GEODIS DMS
Page 81 of 176
June 30, 2019
only)
CMR GEODIS SAP Including hazardous goods information
It must be possible to print a form to add to the outbound dossier (export information, delivery no., net
and gross weight, ADR, planned loading date, special instructions).
The system must print a document with delivery details (incl. ADR details) to be attached to the CMR
(Road Transportation document). Always print this document to have one process.
It must be possible that after pack confirmation of delivery in EWM, the following printouts are directly
issued from ERP:
• Packing list
• Delivery note
It must be possible to print only the lower level HUs on the Delivery Note (excluding the top-level HU of a
Nested HU)
The system must be able to print all delivery notes for a TU/Shipment.
It must be possible to print a CMR on shipment or on delivery level depending on the situation.
- On shipment level if the truck goes via a hub (groupage shipments)

- On delivery level for all other shipments (direct shipments).
It must be possible to print the T1 number on the CMR.
It must be possible in EWM to print VAS/packaging instructions in the work center for a specific SSCC.
It must be possible in EWM to print VAS/packaging instructions in the work center for all pallets in a
delivery and for that workstation.
It must be possible to print a loading list from EWM. The loading list should contain the TU number, list of
HU’s on TU, loading sequence.
F1-OB-15-001 Outbound logistic labels
The system must be able to print logistics label during various steps in the process, depending on the
order flow: 1st step, 2nd step, VAS, packing.
The system must be able to print one logistics label per handling unit.
The system must be able to print logistics labels according to DNP specification (GS1 layout) containing
SSCC codes. For full pallets SSCC codes from storage can be reused.
<To be completed>
Page 82 of 176
June 30, 2019
Outbound delivery and/or shipment changes
Outbound delivery and/or shipment data might need a change after releasing the information to the
warehouse. Change examples are:
Outbound delivery:
• Batch
• Quantity
• Delete line / Add Line
• Pack data
• Block delivery
• Unblock delivery
Shipment:
• Unlink delivery
• Link new delivery
• Staging indicator (almost never changes)
• Loading date/time
• Container type
A Cancellation Form Procedure will be put in place to manage the changes between DNP (Q26) and
GEODIS (EWM) level.
Outbound delivery and/or shipment cancellation after release to warehouse and goods already loaded
DNP will send a ‘cancellation form’ to GEODIS.
If goods have been loaded already, the delivery cannot be cancelled anymore.
If not loaded yet, the cancellation request can be performed, and the complete delivery will be rolled back
(incl. physical movements back to stock, undo relabelling etc.).
If the complete order was packed already, the interface to DMS has run already which means a
correction must be done there as well.
After the physical actions, Q26 will be updated with quantities 0 as well. If needed the outbound delivery
and/or shipment can be deleted in Q26 afterwards.
The ‘cancellation form’ should be used as well by DNP when a shipment (transport order) is cancelled,.
After approval, GEODIS must unlink the outbound delivery from the truck load (shipment) to prevent
loading. The outbound delivery can be linked to another shipment (transport order) in a later stage.
Page 83 of 176
June 30, 2019
7. Storage
F1-ST-01-001 GDC Storage facility
GDC - Warehouse structure
The figure below shows the existing warehouse layout.
Storage conditions
The storage requirements are reflected in storage types, storage sections and storage bin types.
The standard EWM Warehouse monitor will be used to follow up on stock levels of dangerous goods.
(transaction codes /SCWM/MON Warehouse monitor and
Page 84 of 176
June 30, 2019
Storage Type
Mixed Handling Unit storage is not allowed (>1 product on 1 handling unit), except for pick handling units
going to customers.
Stor.
Whse Description Remark
Type
A100 0100 Phase 1 WH0 - Ambient Single Pallet Racking
A100 0101 Phase 1 Highbay - Ambient Single Pallet Racking
A100 0102 Phase 1 Highbay - Cold Single Pallet Racking
A100 0103 Phase 1 Highbay - Cooled Single Pallet Racking
A100 0105 Phase 2 Highbay - Consumables Single Pallet Racking
A100 0300 Crossdock Single Pallet Racking
A100 0301 Containers in Yard Open storage
A100 0302 Returns Open storage
A100 0500 Picking Ambient - 040 Single Pallet Racking
A100 0502 Picking w/o REPL - Cold Single Pallet Racking
A100 0503 Pentapharm Single Pallet Racking
A100 0504 Samples Single Pallet Racking
A100 0800 ID Point for High Rack Storage Intermediate
A100 0801 Pick Point for High Rack Storage Intermediate
A100 7000 Losses Open storage
A100 7001 Damages Open storage
A100 8001 Work Center Pack
A100 8002 Work Center Label
A100 8003 Work Center Pack in Goods Issue
A100 8004 Work Center OPA I
A100 8005 Work Center OPA II
A100 8030 Pack in Goods Issue
A100 8050 VAS in GR
A100 8055 VAS Consumptions
A100 9010 Provide in Goods Receipt
A100 9015 Goods Receipt in Production
A100 9020 Provide in Goods Issue
A100 9021 Provide in Goods Issue - Lekbakken
A100 9025 Provide and Repack in Goods Issue
A100 9030 Doors Goods Receipt
A100 9040 Doors Goods Issue
Page 85 of 176
June 30, 2019
Stor.
Whse Description Type of storage
Type
A100 0100 Phase 1 WH0 - Ambient Single Pallet Racking
A100 0102 Phase 1 Highbay - Cold Single Pallet Racking
A100 0103 Phase 1 Highbay - Cooled Single Pallet Racking
A100 0105 Phase 2 Highbay - Consumables Single Pallet Racking
A100 0300 Crossdock Single Pallet Racking
A100 0301 Containers in Yard Open storage
A100 0302 Returns Open storage
A100 0502 Picking w/o REPL - Cold Single Pallet Racking
A100 0503 Pentapharm Single Pallet Racking
A100 0504 Samples Single Pallet Racking
A100 0800 ID Point for High Rack Storage Intermediate
A100 0801 Pick Point for High Rack Storage Intermediate
A100 7000 Losses Open storage
A100 7001 Damages Open storage
A100 8001 Work Center Pack
A100 8002 Work Center Label
A100 8003 Work Center Pack in Goods Issue
A100 8004 Work Center OPA I
A100 8005 Work Center OPA II

Page 86 of 176
June 30, 2019
A100 8030 Pack in Goods Issue
A100 8050 VAS in GR
A100 8055 VAS Consumptions
A100 9010 Provide in Goods Receipt
A100 9015 Goods Receipt in Production
A100 9020 Provide in Goods Issue
A100 9021 Provide in Goods Issue - Lekbakken
A100 9025 Provide and Repack in Goods Issue
A100 9030 Doors Goods Receipt
A100 9040 Doors Goods Issue

Page 87 of 176
June 30, 2019
Storage Section
The storage sections are used guide pallets to the correct parts of the determined hall (storage type).
For example, with sections it is determined if there are sprinklers or not. In the High racks, sprinklers are
physically setup at the following locations:
G
F
E
D^^
C
B^^
A
Each beam can store 3 euro pallets. At level B and D restrictions apply to storage of goods because of
the sprinklers above it. Currently the system rigidly allows only 2 CP pallets on levels B and D. Therefore,
storage of CP-pallets is prioritized on those levels. Euro pallets are first stored on the other levels.
Theoretically it is allowed to store an additional euro pallet between the CP pallets on level B and D.
However due to complexity that is currently not done.
Whse StorageType Section Section Description

A100 0100 1001 WH0 - Sheme B met afvoer
A100 0100 1002 WH0 - Sheme B
A100 0100 1003 WH0 - ADR 4.1
A100 0100 1004 WH0 - Sprinkler Solid
A100 0101 0001 Sprinkler A
A100 0101 0002 Sprinkler C
A100 0101 0003 Sprinkler B+D
A100 0101 0004 Sprinkler E+F
A100 0101 0005 Sprinkler Solid
A100 0101 0006 A Lokaties
A100 0101 0007 < 4 Meter
A100 0101 0008 > 4 Meter
A100 0101 0009 ADR 4.2
A100 0102 0007 < 4 Meter
A100 0102 0008 > 4 Meter
A100 0102 0009 ADR 4.2
Page 88 of 176
June 30, 2019

A100 0103 0007 < 4 Meter
A100 0103 0008 > 4 Meter
A100 0103 0009 ADR 4.2
A100 0104 0007 < 4 Meter
A100 0104 0008 > 4 Meter
A100 0300 3001 Crossdock - total section
A100 0301 3101 Containers in Yard
A100 0302 3201 Ambient - Lekbak voorloods
A100 0302 3202 Cooled
A100 0302 3203 Cold
A100 0500 5001 OPA Phase 1
A100 0500 5002 OPA Phase 1 with Sprinkler
A100 0501 5101 OPA Phase 2 Ambient
A100 0501 5102 OPA Phase 2 Ambient level B
A100 0502 5201 Containment
A100 0502 5202 Level A-E (geen lekbak)
A100 0502 5203 Level F-G
A100 0502 5204 Fixed Bin - Dangerous Goods
A100 0502 5205 ADR 4.2
A100 0502 5206 Extra Section I
A100 0502 5207 Extra Section II
A100 0503 5301 Pentapharm Liquid A lokaties
A100 0503 5302 Pentapharm Liquid
A100 0503 5303 Pentapharm Solid A lokaties
A100 0503 5304 Pentapharm Solid
A100 0504 5401 Shuttle 1&2 - Cooled
A100 0504 5403 Shuttle 3&4 - Ambient
A100 0504 5405 Shelves Phase 2- Ambient
A100 0504 5406 Shelves Cold
A100 0504 5407 Freezer
Page 89 of 176
June 30, 2019
A100 0800 0001 Total Section

A100 0801 INBD Inbound Pickpoint
A100 0801 OUTB Outbound Pickpoint
A100 7000 7001 Losses - Ambient
A100 7000 7002 Losses - Cooled
A100 7000 7003 Losses - Cold
A100 7000 7004 Losses - Shuttle
A100 7001 7101 Damages - Ambient
A100 7001 7102 Damages - Cooled
A100 7001 7103 Damages - Cold
A100 7001 7104 Damages - Shuttle
A100 8001 INBD Inbound Section for Work Center 'Pack'
A100 8001 OUTB Outbound Section for Work Center 'Pack'
A100 8050 VI1I Inbound Area for Work Center WVI1
A100 8050 VI1O Outbound Area for Work Center WVI1
A100 8050 VI2I Inbound Area for Work Center WVI2
A100 8050 VI2O Outbound Area for Work Center WVI2
A100 9021 LEK Total Section
A100 9025 INBD Inbound Section for 'Stag' Work Center
Page 90 of 176
June 30, 2019
A100 9025 OUTB Outbound Section for 'Stag' Work Center

Stor.
Whse Section Description
Type
A100 0100 001G Scheme B with drainage
A100 0100 002G Scheme B
A100 0100 003G ADR 4.1
A100 0101 001F Sprinkler A Fast
A100 0101 001M Sprinkler A Medium
A100 0101 001S Sprinkler A Slow
A100 0101 002F Sprinkler C Fast
A100 0101 002M Sprinkler C Medium
A100 0101 002S Sprinkler C Slow
A100 0101 003F Sprinkler B+D Fast
A100 0101 003M Sprinkler B+D Medium
A100 0101 003S Sprinkler B+D Slow
A100 0101 004F Sprinkler E+F Fast
A100 0101 004M Sprinkler E+F Medium
A100 0101 004S Sprinkler E+F Slow
A100 0101 005G Sprinkler Solid Fast
A100 0101 006F >4 Meter Fast
A100 0101 006M >4 Meter Medium
A100 0101 006S >4 Meter Slow
A100 0101 007F <4 Meter Fast
Storage Bin Types
The storage bin type plays an important role during optimization of the automatic search for a storage bin,
in connection with the pallet type. For example, you can define the put away strategy in such a way that
you put away large industrial pallets into special large bins, and smaller pallets into small bins.
The storage bin types currently used at DNP are:
Warehouse Storage Storage Description

type bin type
A100 B1 Bin type 66 cm
Page 91 of 176
June 30, 2019
A100 B3 Bin Type 114 cm

A100 C1 CP3 type 66 cm
A100 C3 CP3 Type 114 cm
A100 E1 Euro Bin type 66 cm
A100 E3 Euro Bin Type 114 cm
A100 EP Euro Pallets Bin
A100 O1 Bin - 225 cm
A100 ST Standard Bin
Storage Bin Types search
<to be completed in detailed design>
Doors
The following doors are defined:

Page 92 of 176
June 30, 2019
Inbound /
Warehouse Door Description Where
outbound
A100 D001 I/O
A100 D002 I/O
A100 D003 I/O
A100 D004 I/O
A100 D005 I/O
A100 D006 I/O
A100 D007 I/O
A100 D008 I/O
A100 D009 I/O
A100 D010 I/O
A100 D011 I/O
A100 D012 I/O
A100 D013 I/O
A100 D014 I/O
A100 D015 I/O
A100 D016 I/O
A100 D017 I/O
A100 D018 I/O
A100 D019 I/O
A100 D020 I/O
A100 D021 I/O
A100 D022 I/O
A100 D023 I/O
A100 D024 I/O
A100 D025 I/O
A100 D026 I/O
A100 D027 I/O
A100 D028 I/O
A100 D029 I/O
A100 D030 I/O
A100 D031 I/O
A100 D032 I/O
A100 D033 I/O
A100 D034 I/O
A100 D035 I/O
Page 93 of 176
June 30, 2019
A100 D036 I/O

A100 D037 I/O
Staging Areas
Staging areas are used for the interim storage of goods in the warehouse. They are in close proximity to
the doors assigned to them.
All Staging areas are created for both directions but some of them are only used for one direction. The
most common use for the door can be seen by the checkbox in the GR (Goods Receipt) or GI (Goods
Issue) column.
Staging areas can be determined via “staging area determination groups” and a staging area
determination table. This will be used for inbound. When a GR officer assigns a door to an inbound TU,
the related staging area will automatically be added.
In the outbound process, operators choose a staging area on RF manually.
Warehouse Storage type Staging area Description GR GI
A100 9010 0001 X

A100 9015 0001 X
A100 9020 0001 X
A100 9021 LEK X
Work Center
The work-center is a physical unit in the warehouse, in which you can perform warehouse activities such
as packing, distribution, or weighing.
The following work-centers are defined:
Warehous
Workcenter Description
e
A100 PICK Pick Point Workcenter
A100 SCRP Repack for Scrapping
A100 STAG Packing in Staging Area
A100 VERP Pack in Goods Issue
A100 VSO1 VAS Pack
A100 VSO2 VAS Label
Page 94 of 176
June 30, 2019
Resource
A resource is an entity representing a user or equipment, which can execute work in the warehouse.
Only the resource type is configuration described here. Different resources can be assigned to 1 resource
type via manual configuration (master data).
See Excel Overview: <XXX>
The following resources are defined:
Resource
Warehouse Description DefPresDevc DefPres Description
Type
A100 FT01 Forklift (standard) PD20 Truckterm Device 8X40
A100 RT01 Reach Truck PD20 Truckterm Device 8X40
A100 GT01 General Resource Type PD20 Truckterm Device 8X40
A100 HH01 Hand Held Device PD20 Handheld Device 16X20
Queues
Queues are used to influence the warehouse order selection for a certain resource. Queues are an
important figure to manage the workload in the warehouse.
All warehouses will operate within a single building. Therefore, the queues can be setup process based
for the total warehouse.
Every organization will select based on the requirements a number of needed queues.
Then required number of queues is dependent to:
 Physical organization of the warehouse.

 The requirement to have fast lanes.
 Priorities over warehouse tasks.
 Resource types.
Warehouse Queue Description

Page 95 of 176
June 30, 2019
A100 001_INB Putaway front to Highbay

A100 001_OUT Highbay - Picks to front
A100 001_REPL Highbay - Replenishments to front
A100 002_INB Putaway front to Highbay
A100 002_OUT Highbay - Picks to front
A100 002_REPL Highbay - Replenishments to front
…
The table below shows the queue determination
Warehouse Act. Area Act. Area Acc. Type WPT Activity Queue
A100 PTWY INBOUND
A100 201P PRIORITY
A100 3033 INBOUND
A100 3062 INTERNAL
A100 9999 INTERNAL
A100 999D INTERNAL
A100 8002 OUTBOUND
A100 8003 OUTBOUND
A100 9020 OUTBOUND
A100 9021 OUTBOUND
A100 0100 0500 3010 WH0_REPL
…
Supply areas
Supply areas are master data. They are created in SAP ECC and replicated into EWM. (one-time action)
Supply areas are linked to a resource (= work-center were the process order is executed in SAP ECC,
e.g. filling lines or packing lines). Supply areas are needed to provide the lines with the necessary
materials for producing.
In the process order in SAP ECC the PSA is determined based on the resource.
Based on the product/product group and the PSA, EWM determines the right bin to stage the products to.
The consumption after production also takes place on this bin.
Page 96 of 176
June 30, 2019
N/A for DNP - No production staging in scope
GDC Storage strategies
Put away strategies is part of inbound.

Page 97 of 176
June 30, 2019
Handling Unit Types
HU types are used to describe the spatial appearance of a handling unit, and thus to find the optimum
storage bins, or to check whether a handling unit can be stored in a storage bin.
HU types are configuration settings INDEPENDENT from warehouses. This means that HU types are for
every warehouse the same, so new local HU types can only be added via a Change Request. Instead a
generic approach on how to use HU types should be worked out for all warehouses. The proper usage of
HU types is a supply chain driven topic.
The HU types contain 2 characteristics:
1. Pallet type (Euro or Block pallet)

2. Standard height of the pallet (range of heights to be established across supply chain)
The following HU types are available:
HU
Description
type
C1 Carton/box/pail
CP CP3 Pallet 114 x 114 x 15 cm
D1 Dummy HU
CP3 Pallet 114 x 114 x 15 cm -
DR
Drums
EP Europallet 120 x 080 x 15 cm
IP IP Pallet 120 x 100 x 15 cm
Page 98 of 176
June 30, 2019
GDC Storage bin types and capacity
Order pick area (OPA)
There are different picking processes in the warehouse. For products that replenished to a dedicated
area, the so called OPA’s are created.
These are reflected in storage types in section 7.1.2.1.
Replenishment and Reverse replenishment are described in the outbound scenarios (
Stock status
Stock statuses is an integration topic between Q26 and PEW.
The following stock statuses will be used as shown below. In Q26 less differentiation is made in stock
statuses than in DNP SAP EWM.
Q26 is mainly driven by the Inventory Status and the Storage Location.
In PEW customizing the link is made towards the Q26 inventory status and storage location. There is an
extra differentiator Stock Type)
Batch statuses
Batch statuses are maintained in Q26 as a characteristic on the batch. This only becomes relevant for
EWM stock types if batch status change influences the ERP Inventory status
Expired stock
When stock exceeds the pre-defined minimum remaining shelf life, the batch will be blocked
automatically in DNP Q26. As from that moment no outbound delivery can be created in Q26 for the
batch.
Page 99 of 176
June 30, 2019
Bonded / non-bonded stock
Both bonded and non-bonded (customs cleared) stock is stored in the GEODIS warehouse.
Stock is not separated physically, but only administrative in Duty Management System (DMS).
Stock statuses SAP ERP Q26 versus Stock type EWM
Stock status in Q26 (Inventory management)
The 4 standard stock categories in Q26 “Blank - Available Stock”, “Q - Stock in Quality Control”, “R -
Returns Stock” and “S -Blocked Stock” are always reflected in EWM.
The batch classification statuses – batch Quality status is update via the LIMS-interface.
Whenever the batch classification statuses – batch Quality status is triggering a transfer posting on
inventory management status it will be reflected in Q26 in one of the four standard stock categories and
therefore also reflected in EWM.
Stock types in PEW (warehouse management)
EWM stock types reflect warehouse-statuses to manage warehouse stock, warehouse activities and
warehouse reporting.
Q26 PEW
Page 100 of 176
Plant Inventory management ERP Storage Location EWM link to ERP EWM Stock types
June 30, 2019
status
Blank (Unrestricted-Use 0001 - Sellable stock FF - Unrestricted-Use Stock G1 - Unrestricted-Use Stock -
Stock) (F)
Functional Specification 2399
QQ - Stock in Quality
Q (in Quality) Inspection
S (Blocked) BB - Blocked Stock
Blank (Unrestricted-Use
Stock) (F) 0150 - Damaged stock FF - Unrestricted-Use Stock G2 - Damaged - 2399
Blank (Unrestricted-Use G3 - Stock Losses Warehouse
Stock) (F) xxxx - Losses Warehouse FF - Unrestricted-Use Stock - 2399
2399 Stock) (F) xxxx - Scrap stock FF - Unrestricted-Use Stock G4 - Scrap stock - 2399
0100 - Returns from RR - Blocked Stock Returns G5 - Return from Customer -
R (Return Customer 2399
Blank (Unrestricted-Use 0110 - Reserved Stock G6 - Reserved Stock (no ATP)
Stock) (F) (no ATP) FF - Unrestricted-Use Stock - 2399
F/Q/S 0200 - Overflow I N/A N/A
F/Q/S 0210 - Overflow II N/A N/A
F/Q/S 0051 - Eurofrigo N/A N/A
F/Q/S 0052 - BakePlus N/A N/A
F/Q/S 0053 - De Rijke N/A N/A
F/Q/S 0066 - Peti N/A N/A
Page 101 of 176

Q26 June 30, 2019 PEW
Plant Inventory management Storage Location EWM link to ERP EWM Stock types
status
BlankFunctional
(Unrestricted-Use
Specification 0001 - Sellable stock FF - Unrestricted-Use Stock L1 - Unrestricted-Use Stock -
Stock) (F) 2102
Stock) (F) 0150 - Damaged stock FF - Unrestricted-Use Stock L2 - Damaged - 2102
Blank (Unrestricted-Use L3 - Stock Losses Warehouse
Stock) (F) xxxx - Losses Warehouse FF - Unrestricted-Use Stock - 2102
2102 Stock) (F) xxxx - Scrap stock FF - Unrestricted-Use Stock L4 - Scrap stock - 2102
0100 - Returns from RR - Blocked Stock Returns L5 - Return from Customer -
R (Return Customer 2102
Blank (Unrestricted-Use 0110 - Reserved Stock L6 - Reserved Stock (no ATP)
Stock) (F) (no ATP) FF - Unrestricted-Use Stock - 2102
F/Q/S 0200 - Overflow I N/A N/A
F/Q/S 0210 - Overflow II N/A N/A
F/Q/S 0051 - Eurofrigo N/A N/A
F/Q/S 0052 - BakePlus N/A N/A
F/Q/S 0053 - De Rijke N/A N/A
F/Q/S 0066 - Peti N/A N/A
Page 102 of 176
June 30, 2019
F1-ST-02-001 External Warehouse and Overflow Warehouse
Separate storage locations are already existing in Q26 for the external warehouses:
St. loc.
0051 Eurofrigo
0052 BakePlus
0053 De Rijke
0066 Peti (only used for tolling/repacking)
Not used at the moment:
0050 ADR ext loc Broekman Logistics could be needed any moment
0099 Temporary Used for multi step postings, e.g. 2399/0001 -> 2399/0099 -> 2399/blank ->
2399 to 2288
0077 Novo DK not used, will stay

0088 0088 not used, will stay
2230 Veembedrijf De Rijke B.V.
23F1 Eurofrigo
23F2 BakePlus
2195 Peti
23DG ADR external location
Additionally, two overflow storage locations will be created:
0200 Overflow 1
0210 Overflow 2
Shipping points will be assigned to the storage locations.
These storage locations will only be inventory managed and are not connected to EWM.
Sales orders to be shipped from different shipping points will be split into several deliveries. Each
shipping point is one delivery.
Execution process for overflow location will be equal to process for external warehouses.
Page 103 of 176
June 30, 2019
The inbound process from overflow warehouse to GDC will be initiated by DNP in a two-step stock
transport order. This will enable warehouse operations to scan the ‘old’ SUID or the ‘new’ SSCC.
The outbound process from GDC towards overflow warehouse will be initiated by DNP in a one-step
stock transport order that generates an outbound delivery.
In customizing the “Stock Transfer Between Storage Locations” needs to be activated. The actual stock
transfer orders are only foreseen for plant to plant transfers. In case for the overflow and external
transfers the storage locations belong to the same plant. The stock transfer between storage locations is
a two-step flow. A stock transfer order; an outbound delivery, PGI of delivery, stock in transit, goods
receipt of delivery. Or a stock transfer between 2399/2399 has to be setup with the one-step flag (not
sure that this works).
2399 2102 ZTRO – is setup as one-step transfer. There are no other entries for 2399 - 2102.
Goods movement: Overflow / External Warehouse to GDC
For receipts from overflow, the inbound delivery is created automatically at goods issue of the outbound
delivery picking from the overflow location.
As there is no HU information in the delivery, the operator in the Distribution Center cannot scan the HU’s
upon receipt. He needs to build them 1 by 1 by entering the relevant information on RF.
Note: If the pallets in the overflow location have been in the DC before moving them to the overflow
location, the labels on the pallets will be scanned to re-use the original HU numbers applied on the pallets
in the DC before sending them to the overflow location.
Note2: If the pallets come from an External warehouse, the same process applies. Usually these pallets
will come into the DC for the initial and only time (so they will not have an SSCC label yet)
Goods movement: GDC to External Warehouse
Table
Materials only stored in external warehouses
Some materials (like frozen and smelly goods) are only stored in external warehouses in The
Netherlands and never at GEODIS.
GEODIS does currently the following inbound tasks:
 Goods receipt on IM (Inventory Management) level in DNP Q26

Page 104 of 176
June 30, 2019
 Customs activities in GEODIS DMS
F1-ST-03-001 Physical inventory counting
 Ad-hoc Physical Inventory counting
Is a type of continuous physical inventory counting and it can be executed anytime during the fiscal year.
You can perform an ad-hoc physical inventory counting in various scenarios, for example, if a product has
been damaged. This procedure can be performed at the storage bin level or it can be product-specific.
To create an ad-hoc physical inventory document, use the following path:
EWM → Physical Inventory → Create Physical Inventory Document.
Select Storage Bin in the Find field. Enter the storage bin from the previous step. Choose Perform
Search. Select the checkbox for the Block Indicator. Then, select the line and choose Set Flag. Then
Save.
Note
The Pl document number that was created (in the task bar the Pl document number is followed by the
current year).
 Cycle counting
Current procedure. All locations must be counted once a year by RF.

Page 105 of 176
June 30, 2019
The objective of this procedure is to have a clear instruction for the cycle count plan and to ensure all bins
(included blocked bins) are counted at least once per year.
A count is a physical check of the inventory stored in the bin, or a confirmation that the bin is empty.
The inventory has to correspond with the information in SAP WM (material / batch / qty). These counts
will take place during a pick or an inventory cycle count.
VLB will perform an administrative check for intermediary storage types and Lost and Found Storage
Types.
Overall statement:
• To be counted bins per quarter: storage types 7001 (Damaged Material), 500 (Partial Picking w
Repl.), 501 & 502 (Partial picking w/o replenishment), 302 (Return Goods), 7000 (Lost and
Damages)
• At least once per year all the bins of storage types 101, 102, 103, 104,105, Containment areas,
Cross docks and Pick Areas with or without replenishment.
• Weekly administrative check of storage type 9010,9015,9020,9021,9025.
•
Cycle count planning per quarter
The storage types below are assigned per quarter to ensure that all bins, included blocked bins, are
counted at least once per year.
- Q1
Inventory counting with RF terminal:
 Highbay storage types 101, 102, 103, 104,105 all bins with “last clearing date”
and “last inventory date” older than 9 months
Paper-based inventory counting:
 7001; Damaged Material

 500; Partial Picking W RPL
 Samples, zone 50 (sample area “fase 2”)
 Samples, zone 52 (shuttle 2)
 302; Quarantine - Return Goods
 Empty bins in highbay warehouse 1+6
- Q2
Page 106 of 176
June 30, 2019

 Samples, zone 50 (sample area “fase 2”)
 Samples, zone 52 (shuttle 2)
 Empty bins in HighBay Warehouse 2+8
- Q3
 Containment
 Containment (empty bins)

 106; Samples, zone 53 (shuttle 3)
- Q4
 107; Pentapharm HB
 107; Pentapharm HB (empty bins)

 300; Cross dock
 External storage
 501 and 502; Partial Picking W/o RPL
 106; Samples, zone 54 (shuttle 4)
Administrative check: All storage types which are used as intermediaries like 9010,9015,9020,9021,9025
will be checked during the day-to-day operations, with a minimum of once per week.
Page 107 of 176
June 30, 2019
Lost and founds in 7001 will be checked once per month
Cycle count statement
# differences between physical- and system-stock per individual bin / # bins counted (highbay picks +
cycle counts per quarter) * 100% < or = 0.02%.
The process flow for Cycle Count is as follows:
There will be authorizations at every level, who can post differences in EWM and who can post in Diff
Analyzer to create a posting in ECC subsequently and an accounting document in the background.
Based on Cycle counting cycle a Physical Inventory document (abbreviated as PID) will be created. The
PID will be activated when actual cycle counting is required.
Counting will be done via RF or wherever a physical print is required, a printout will be executed.
Note:
PID created and printed will use an SAP standard form. In case a customized PID form will be required,
this will be taken up for development at a later stage.
Page 108 of 176
June 30, 2019
Count results at Bin level in EWM might throw some differences. The differences shall not be posted in
ECC before having the necessary approval from DNP.
After proper recount, the differences in count in EWM is posted in EWM and this will put the loss/ gain in
stock in Difference Analyzer in EWM.
Analysis of Stock Difference:
The stock in Difference analyser can be a Loss or Gain.
If the difference is a Gain, then keep the stock in Difference analyser.
Example:
ECC Stock Material – M1, Batch- B1 Stock, Status: Free, Sloc: 0001, Stock Qty: 100
EWM Stock Material – M1, Batch- B1 Stock, Status: Free, Sloc: 1001, Stock Qty: 110
Diff Analyzer Material – M1, Batch- B1 Stock, Status: Free, Sloc: 0001, Stock Qty: 10 (Gain)
The stock gain will be analysed, and the outcome can be following:
 Actual Gain
 Gain due to postings not done before
If this is an actual gain, then the difference will be posted in diff analyser and the ECC stock will become:
110 and EWM stock: 110.
If Gain is due to missing postings, then postings will be made, and the diff analyser stock will be knocked
down against a new PID for the said bin.
If the difference is a Loss, then the ECC stock which for the Loss quantity needs to be blocked.
Example:
Diff Analyzer Material – M1, Batch- B1 Stock, Status: Free, Sloc: 0001, Stock Qty: 10 (Loss)
From the Diff Analyzer as shown below, the stock status of the Diff analyser stock will be changed to
Blocked and this will trigger a material movement in ECC, where 344 movement takes place and the
stock is blocked. The diff analyser stock will also be in blocked status.
Page 109 of 176
June 30, 2019
Example (continuum above after Stock Type change in Diff Analyzer):
ECC Stock Material – M1, Batch- B1 Stock, Status: Blocked, Sloc: 0001, Stock Qty: 10
Diff Analyzer Material – M1, Batch- B1 Stock, Status: Blocked, Sloc: 0001, Stock Qty: 10 (Loss)
Posting Approval for ECC from DNP
After approval to post the difference in ECC, the stock difference in Difference Analyzer in EWM will be
posted and then a Warehouse Material Document will be created in EWM, which will create a Material
posting and corresponding accounting document in ECC.
Note:
For Loss, the knockout of stock in ECC will happen from Blocked Stock.
The count can be changed in Diff Analyzer if required and posted, which will also create a Material and
accounting document in ECC, additionally it will also create a PID document in background and post also.
 Zero stock check
The Zero stock check is done for every bin which becomes empty. The Zero stock check is done
automatically in the background by using the EWM standard functionality of LSPI, where the threshold
value is maintained as zero, so that when the stock is zero, PI is triggered automatically.
Page 110 of 176
June 30, 2019
The LSPI indicator needs to be checked in as shown above in the configuration for every Physical
Inventory area.
 Wall-to-wall count (W2W)
Not applicable.
F1-IB-01-006 Cross dock inbound
When one or more inbound delivery items is relevant for cross dock, Geodis office will change the
warehouse process type on the relevant delivery items in EWM. This will derive a separate putaway
strategy sending the goods to storage type 0300 (Crossdock). The operator posting GR on RF will then
automatically get 0300 as destination when creating putaway tasks.
The separate Warehouse Process Type provided for putaway to crossdock is 1016, it sends goods to
storage type 0300 which is only a virtual area. The actual bins in storage type 0300 correspond to staging
area bins in the GR zone.
Optionally:
If it is known upfront that that the whole delivery will be crossdock relevant, a separate inbound delivery
type could be created in Q26 and distributed to EWM. Based on this delivery type, a specific put away
strategy can be determined automatically to put these goods into a cross dock zone. This would make
the process automatic in the warehouse, with less risk for error.
All inbound deliveries received via EDI from M&T and external suppliers will be created as non-cross
dock relevant deliveries.
U1-ST-04-001 Deliver to destruction / Rework and Tolling
Trigger today/ how is done?
Internal warehouse processes and cross process settings
F1-IN-01-001 Maximum 1 Truck per Aisle
The system must be able to assign warehouse tasks in one aisle to one Narrow Aisle truck only.
SAP EWM offers Resource Execution Constraints functionality to limit the number of resources (for
example, reach trucks) in an area. This functionality will be setup in the DSM system to address the user
requirement.
Page 111 of 176
June 30, 2019
F1-IN-01-002 Queue setup
The warehouse tasks will be assigned to queues. Depending on the process (inbound, internal,
replenishment, picking, high bay…) different queues need to be derived.
The warehouse workload can be managed by using these queues and assigning resources to the
queues.
This requirement is already describing SAP functionality. It will indeed be implemented to meet the
requirement.
F1-IN-01-003 Overrule movements
It is possible in EWM to overrule movements. On RF, an exception code can be used. On desktop a new
task can be created, or an exception code can be entered.
F1-IN-01-004 Interleaving
The high bay operations must to be optimized so that pick and put-away operations can be combined
(interleaving).
Interleaving is standard available in EWM and will be setup.
F1-IN-01-005 Process based RF messages
The system must be able to show VAS instructions on RF during movements (warehouse tasks of put
away, picking, replenishment, reverse replenishment).
EWM16 - Process based RF messages (EWM)
A build object has been foreseen to provide functionality for process-based RF messages. See detailed
specification EWM16.
F1-IN-01-006 Create and move nested handling units
It must be possible to nest handling units in all work centers to support internal moves and loading with
only one scan afterwards.
Creating nested handling units is possible and it is possible to move them around.
It should be clarified what the expectations of the business are “internal moves and loading” can be
interpreted in different ways and the possibilities are limited in the system.
F1-IN-01-007 Batch and product changes with (re)label actions
It must be possible to do a material change in EWM system (material number X to material number Y or
batch number X to batch number Y) including routing via work center.
Page 112 of 176
June 30, 2019
- Batch changes
o shelf life extension with relabelling
o batch to batch
- Material changes
o Material to material
These changes can be triggered from Q26 to PEW with MIGO. This is only possible for
- Full batch quantity

- Partial batch quantity where the warehouse is free to choose the HU’s to change
- Partial batch quantity where the warehouse is informed by DSM which HU’s to change
Once it is clear what stock (handling units) to book, the posting can be created in EWM(including routing
via a Work Center, every move for this type of booking will then always go via a WC)
F1-IN-01-008 VAS Orders for internal warehouse activities
VAS orders can be manually created to do VAS activities (e.g. shelf life extension, re-label, re-pack,
material to material bookings) on stock materials/SSCC (no linked to inbound or outbound movements)
The system must support ad hoc repack of stock.
DNP has re-label requests for stock of a material – batch – combination.
Relabel requests are entered in DCNWEB by DNP with a detailed instruction.
The complete batch is blocked in Q26 by DNP manually until the relabel action is finished. GEODIS will
process the relabel order, system managed (manual warehouse tasks from and to stock), currently in
SAP Q26 and in the future in SAP EWM.
If the remaining shelf life is extended, the LIMS analysis number must be mentioned in the relabel order
by DNP on DCNWEB because it needs to be printed on the label (PAGO).
Material change& Batch number change
Material changes are triggered in DCNWEB via a relabel instruction. The material is completely blocked
in DNP Q26 if the relabel action is not finished.
When the relabel action is finished the material is changed at GEODIS in SAP and put back in stock with
the new material number. The booking will be sent to DMS as well.
DNP will be informed about the change by completing the relabel action in DCNWEB and they will do the
material change in Q26. Then the new material can be ordered.
F1-IN-01-009 Ad hoc repack of stock
Standard EWM supports ad hoc repack of stock, both on RF and on desktop (work center)
Page 113 of 176
June 30, 2019
F1-IN-01-010 Cross Process RF requirements
Development: EWM04 - RF Screen adjustments
On the confirm destination screen in RF, different information is needed for the picker.
- Information for Forklift driver to choose a small or big VAS work center bin
- Information for Forklift driver to choose a staging area for CONTAINERS
- Information for Reach truck operator for distinction between PICK and REPL
EWM04 will cover these changes in the RF Framework to provide the operators with the needed
information.
EWM16 - Process based RF messages
In legacy system there is a custom-built solution to display messages on RF based on the process. This
EWM16 development will provide a similar functionality.
F1-IN-02-010 Ad hoc movement of stock
Standard EWM supports ad hoc movement of stock, both on RF and on desktop. Warehouse Process
Type 9999 is available for these movements.
Page 114 of 176
June 30, 2019
F1-IN-02-001 GDC & RDC
Stock from two different plants 2399 and 2012 will be reflected in PEW as 2 separate Party Entitled to
Dispose. This is supported in standard SAP.
Transfer between the 2 plants will be triggered by the planners from Q26 and will result in posting
changes on PEW side.
The start of the process is purchase requisitions generated by APO. Planners select purchase
requisitions and create ZTRO stock transport orders from these requisitions.
These STO’s result in an outbound delivery in Q26 because the storage location is EWM managed, the
outbound delivery is to be distributed through qRFC to PEW.
In PEW, with standard configuration, the delivery type is mapped to a posting change type which will then
book the stock from Party Entitled to Party Entitled without moving the stock.
Development: ECC10 ZTRA / Step 6 program - ZTRA obsolete; Step 6
- Existing program will be adjusted to skip the Q26 WM steps.

- Q26 will need an RFC call to see the stocks in EWM – to inform the user about partial quantities
as in such cases the posting change in EWM would fail; consequence if partial quantities?
- PEW will need to confirm the posting changes automatically without a need to move stock
physically
Stock from two different plants are stored in the Venlo warehouse. The stock of these two plants must be
considered for the implementation of all warehouse processes
- Global Distribution Centre (GDC)

- Regional Distribution Centre (RDC)
The impact of the two owners needs to be as limited as possible for the operators on the floor.
Transfer of ownership must be possible without physical movement of the pallets.
It must be possible to transfer stock from plant 2399 to plant 2102 via ZTRO (Transfer Order). Reverse
process must be possible as well. (not necessarily via ZTRO transfer order)
F1-IN-02-010 Ad hoc movement of stock
Standard EWM supports ad hoc movement of stock, both on RF and on desktop. Warehouse Process
Type 9999 is available for these movements.
Page 115 of 176
June 30, 2019
8. Returns
Two new storage locations will be created in Q26:
0100 Returns Customer will be EWM managed
0110 Returns Vendor will be EWM managed
F1-RT-01-001 Returns to Supplier
Returns to Suppliers is a normal Outbound sales process. The Sales order of type ZFD shall be created
for Returns to suppliers. This shall create a Purchase Order in ECC system and then create an Inbound
Delivery in ECC.
The Inbound delivery shall create a normal Outbound delivery in EWM and it will be processed normally
from the Returns to Supplier area.
The issue is that DNP only has one stock status to ship goods, which is ‘available’.
The returned stock is always booked to available before it can be shipped back a supplier or before it can
be shipped to a specific customer.
In ECC the stock will be booked into the special storage location 0110 Returns Vendor.
ZFD sales order can reserve goods in:
- Storage location 0001 (normal storage location)

- Storage location 0110 (vendor return storage location).
Trigger: EWM stock which needs to be returned to vendor will be moved to the storage type for Returns
to Vendor, which will trigger a Sloc change movement in ECC to 0110 SLoc. A separate availability group
will be used for Returns to vendor.
Page 116 of 176
June 30, 2019
F1-RT-02-001 Returns from Customer (Inbound)
The Returns from Customer starts with identifying the Billing document which must be returned and a
creation of return SO with order type ZRE1 (ZRE1) or RE (REN). A corresponding outbound return delivery
ZLR1 (ZRE1) and LR (REN) will be created in ECC.
The return delivery number and delivery note information is communicated to the forwarder.
The forwarder knows exactly what to pick up based on the delivery note information.
The delivery number is used as a reference number for slot booking and unloading.
The forwarder pre-advices the return and will agree on an unloading slot (like normal inbound process).
The Return Outbound delivery will be distributed from Q26 to EWM as an Inbound delivery. The broad
process flow is as attached below.
Page 117 of 176
June 30, 2019
The planning of Returns truck is done in the EWM by creating a Transportation Unit in system and
communicated to forwarder. The returns truck received in the warehouse is checked in and blind check is
done, using a Visual Control Document, and after that any mismatch can be treated as three options.
Following are the three options, which are detailed in section Returns exceptions:
Batch Mismatch
Product Mismatch
Quantity Mismatch
The last option, i.e. Option 4 is for matching Returns delivery and matching quantity received physically.
The flow above is for Option 4, where there is no discrepancy between a returns delivery so created in
Q26 and distributed to EWM and the to be physical receipt after Visual Check document.
Page 118 of 176
June 30, 2019
Returns monitoring
The returns monitoring will be handled in EWM via Warehouse Monitor. The DCNWeb functionality will
not be used going ahead and will be managed in EWM.
Dock assignment of Truck will be done in EWM system.
Returns check-in
Warehouse planning will decide if the returned goods have to be stored in the cooled return area or the
ambient return area. Dangerous goods are currently stored in the ROG area but should be stored in a
special dangerous goods area if outside the PGS15 margins (too high volumes).
For full truckloads the ROG area will not be used due to limited space.
Damaged goods are stored in the correct storage type (dangerous, cooled, ambient). Normally damaged
goods are already contained.
When the “Visual Control Document” is filled in completely it is returned by the warehouse operator to the
office. At the office the form is checked if all data is correct and a decision is made if the truck may be
unloaded. If the return is not correct the goods are not unloaded.
Only when the return shipment is too big to be able to check inside the truck, goods are unloaded first
before checking.
If package is never opened, it will not be opened. If the package is open or different tape is used, the
package is opened to see the inner packages for material, batch, quantity and damage.
If an inner package is opened this is treated as damage.
Damages are noted on the unloading card as well and taken over on the CMR at the office.
Returns after unloading are put in the ROG area (Final Putaway Indicator not set in the storage type of
ROG area in EWM) in restricted stock type. After the stock is put away in system, a trigger in the form of
a PPF is sent from EWM system to the planner group. This will be a text email to a specified group
without any attachment. (PPF trigger via Inbound Delivery).
Returns check by DNP
Triggered by the automatic email DNP will physically check the returned goods. This is done for all the
returned goods. Based on criteriathe physical situation, a decision will be made how to book the goods
(available stock, damaged stock, return to supplier) and will be updated in EWM. Additional comments
will be filled by DNP in EWM in the Inbound Delivery. This will be a development, the details of which will
be specified in the Detailed design. QC and insurance might be involved to further investigate the goods.
Page 119 of 176
June 30, 2019
An email needs to be triggered from EWM Inbound delivery to the Warehouse, requesting the
movements to be carried out, in form of a PPF which will be configured in EWM.
Returns put away
Warehouse tasks are created for the different put away to the correct storage location and storage type
(dangerous, cooled, ambient). The storage type is as registered in the material master. After the
Warehouse Tasks are confirmed in EWM, then a trigger is sent to DNP in form of an email, requesting
that as directed movements has been carried out in EWM and the ‘R’ block needs to be removed. This
will be a development.
After the message from EWM, DNP removes the ‘R’ flag in Q26 (453 booking) on IM level. This will
create an Outbound delivery in the Q26 system because the storage location is EWM relevant. The
Outbound delivery will be needed to distribute to EWM, where it will be processed as a posting change
document (which is like a stock type change in EWM). Successful processing of the posting change in
EWM will update ECC stock.
Credit note to the customer can be created in DNP Q26 manually as soon as the billing block is removed.
Can be done at any moment but is generally done after the goods have been received and judged in
Venlo.
Returns exceptions
Quantities received less than the sellable unit (Option 1)
Only multiples of the selling unit may be booked.
Return of material which was not in the original sales order (Option 2)
If material B is shipped instead of material A, material A will be shipped afterwards with the original
documents and material B is returned. Material B cannot be booked with a return sales order because it
was never shipped systematically.
Different Batch Received which was not there in the Delivery. (Option 3)
Assuming that the delivery contains three-line items Material A, Batch B1, Batch B2, Batch B3 and
physically received Material A, but batch B1, Batch B100, Batch B2, then this is a scenario of batch
mismanagement.
Note:
In all exception scenarios, the line item where the exception has occurred should be zeroed using an
exception code in EWM. This will trigger a zero quantity of the same reference document i.e. Outbound
Delivery in ECC. The reference return Sales order will open, and a new corrected Return Outbound
Delivery can be created in ECC and distributed in EWM. The new EWM Inbound Delivery will then be
processed as in Option 4 in the diagram above.
Page 120 of 176
June 30, 2019
Development: EWM25 – Returns related PPF messages
To have the necessary communication between departments during the returns process, 3 e-mail actions
are built into the system (with Post Processing Framework)
9. Customs
Goods of DNP can either be bonded or non-bonded (free circulation / customs cleared). All goods
managed by the GDC and RDC (including External warehouse and overflow warehouse) in Venlo are
managed under the customs E-license of Vitesse Logistics BV and must be administered in the Duty
management system (DMS). All goods managed under de E-license is owned by the GDC (company
name).
The E-license allows registration of bonded / non-bonded goods stock-levels in DMS only. In EWM no
link to bonded or non-bonded stock levels is kept. This allows for
 Optimized and efficient storage management

 optimization customs duty handling
All stock not managed by GEODIS warehouse operations (overflows and external warehouses) but
administered by DMS must be non-bonded (GEODIS policy).
All current (3) DMS interface will be changed in this project from a direct interface to an interface via DNP
and GEODIS middleware. All the mapping activities will be executed in the GEODIS middleware system
GEOBUS. In the DNP middleware only routing and file transfer is handled.
In the diagram below a high-level overview of the processes including Duty management system and
message is drawn.
Page 121 of 176
June 30, 2019
Following are the list of interfaces relevant to Customs (as shown in the Table )
Name of Description Direction from Q26

Interface
TP-03 Material Receipt posting information Outbound
TP-04 Receipt of GR posting approval Inbound
TP-05 Pack and Pick confirmation for Loading Outbound
TP-06 Approval for Loading Inbound
TP-08 Stock File - one in night Outbound
TP-09 Stock Adjustment Outbound
TP-11 Material to material change and Country of Origin change Outbound
U1-CU-01-002 Receipts (including returns)
At arrival of a truck with bonded goods, the T document is registered in DMS and a request for unloading
is send to customs. Possible responses of the customs system:
Page 122 of 176
June 30, 2019
 unloading permission granted

 outstanding permission means check required.
All incoming goods must be blocked for usage in outbound shipment until customs provides a NCTS
arrival Conform statement. During this time, it must be possible to present all goods linked to the goods
receipt to a customs officer for a physical check.
Details of the message TP-03 and TP-04:
TP-03: After unloading and check-in of the complete shipment a “Goods receipt” message is send from
EWM to Q26, in Q26 a goods receipt is booked. From Q26 to DMS the goods receipt booking is send
(TP03). The Goods receipt message is processed in DMS and an “AGS Placing customs in WH” is send
to Customs. All Goods receipt are supposed to be considered.
This stock posted in EWM and ECC should not be picked or made available for Outbound unless
customs sends a “Yes” approval. Hence the proposal is to post the stock in Customs Blocked stock in
EWM. Custom Stock Type used in EWM, will map to a Blocked stock type in ECC.
The user-exit EXIT_SAPLMBMB_001 which processed during a material document posting, determines
the relevancy for customs message by reading the table ZMWIV with key movement type/shipping
point/plant. If the document is customs relevant the material document will be stored in a customized z
table with LSP interface number and with time stamp and flag whether sent. A periodic running program
scans the table for documents to be transmitted and generates and sends the file. The z table is being
updated with a flag that the file is sent.
In principle all materials shall be posted to Customs blocked stock, (Exception can be consumables and
packaging materials – discuss further- Open Point)
Material master information to be sent also (details in xml message and will be detailed out in the
Detailed Design phase) through TP-03.
TP-04: This is a message for approval whether Goods receipt can be posted to available stock which can
be used for outbound activities. Approval of posting of Goods receipt received from Customs after which,
goods can be posted from Customs Blocked stock to available stock. After processing by customs
system, a message is sent (TP04) to Q26. The Q26 will update the z table with a time stamp and trigger a
message to EWM.
This will be a Development where all handling Units related to the pertinent inbound delivery will be
searched and posting change will be processed by changing the stock type, details of which will be done
in the Detailed design phase. The EWM posting will also make the Q26 stock “available”.
Page 123 of 176
June 30, 2019
TP-03 will necessitate a “Yes” from customs. The TP-04 message back from LSP is important as this is
the trigger for stock change posting. The “YES” message should arrive within minutes. A delayed
message means that a customs check is going to happen, there will be no “NO” message.
External warehouses will not block the stock. The TP-04 message for external warehouses will not be
further processed.
Inbound differences
Missing quantities of incoming bonded goods: must be reported to Customs on the T-document will be
booked as a loss at Customs. The missing qty must be settled by the sending party.
Over quantities of incoming bonded goods: must be reported on the T-document of the shipment. The
additional qty will be booked as bonded goods in DMS. The additional qty needs to settle by the sending
party
Storage Customs activities
Free goods (customs cleared or in free circulation) are stored as non-bonded.
Goods which arrive under T1 are stored as bonded.
Stock changes (Loss & found)
All loss and found goods bookings in Q26 must be interfaced from Q26 to DMS. The message structure
used is TP09.
For loss of bonded goods customs duties must be paid. Found goods are booked into stock as non-
bonded.
U1-CU-01-003 Material changes
In case of material to material change, an interface message must be send from Q26 to DMS.
The message structure is TP11.
In DMS when the material to material change both have the same HS-code in DMS the stock will updated
accordingly. In case the HS changes the old material will be shipped and the new material will be
received (including customs clearance for bonded goods).
Batch changes should not be interfaced to DMS.

Page 124 of 176
June 30, 2019
Details of message TP-11
TP-11: Material to Material posting
Movement type 309 Material to Material posting must be reported. Eventually the issuing and receiving
material number must be compared.
TP-09: Stock changes/ adjustments
U1-CU-01-004 Outbound Customs activities
Message structure to be used TP-05 / TP-06.
TP-05: For outbound deliveries after packing is completed in EWM an interface is triggered to Q26. This
interface updates the packing information of the delivery in Q26. A user-exit in MV45AFZZ “save
document” is processed. In this user-exit all relevant deliveries will be filtered by checking the packing
status = complete.
Trigger when Pick Status is “C for external warehouse and overflow location, and Pack complete for
EWM managed. The relevant deliveries will be written to a Z-table. A periodic running program scans the
table for documents to be transmitted and generates and sends the file. The z table is being updated with
a flag that the file is sent (TP-05). Message is triggered per delivery.
All outbound deliveries must be blocked for loading until a release message TP-06 from DMS is received.
Page 125 of 176
June 30, 2019
When the processing in DMS is finished a message is send to customs for the “AGS import declaration”
and the stock is issued from the DMS. The “AGS import declaration” triggers a message from Customs to
DMS releasing the outbound delivery for loading. The release of the outbound delivery for loading is send
to Q26 (message structure TP06).
TP-06: Approval received from LSP regarding staging (as requested on via TP-05) and hence loading
and GI can take place simultaneously.
The lead time to reply is usually 5-10 minutes but it can be longer depending on whether a customs
physical check is required. If TP-06 message is not received, the Truck cannot start load. TP-05 message
is delivered on Outbound delivery level. The Truck should not be loaded and this to be a manual check at
the Truck level. The EWM TU can be status “Blocked for Customs”. (Possible Pre-requisite: TU shall
have the Outbound Delivery attached).
Q26 receives the TP-06 messages. As the many deliveries are grouped into one TU, the system has to
collect all approvals from DMS. Once all deliveries of a TU are approved then a removal message to
EWM can be send. The message removes the “Block for Customs” indicator from the TU. This will
happen via an IDOC from Q26 to EWM.
Prices
Price is available in the sales order of DNP but that is not always the correct price. The correct price must
be in the interface and on the customs invoice. The price used in the interface and stated on the customs
invoice must be equal. For the price determination, there are three situations:
1. Intercompany shipments
2. End customer shipments from RDC Venlo
3. End customer shipments from GDC
Tariff (HS) codes
In Q26 currently the Swiss HS codes are setup. DMS needs the EU HS codes GEODIS customs
department defines the EU HS code. In case of doubt DNP is involved for advice. The local DNP
organization is end responsible for the correct EU HS code.
For bonded stock, the Swiss HS codes are used from Q26 for reporting to the Swiss authorities. The EU
HS codes are currently not set up in Q26. The HS-codes are setup manually as part of the MOC
procedure. The master data interface part of TP01 or TP03 is prepared to receive the EU HS code in the
future.
Page 126 of 176
June 30, 2019
U1-CU-01-007 Stock reconciliation
Stock in DNP SAP ERP and GEODIS DMS must be compared regularly. A stock file interface message
structure TP08 is required.
In DMS stock in different locations are registered and must be identified in the stock file:
1. Stock in GDC Venlo warehouse

2. Stock in RDC Venlo warehouse
3. Stock per overflow warehouses
4. Stock per external warehouses
To allow correct comparison of stocks between Q26 and DMS the stock file should contain all stock in
storage. The stock file should contain the stock levels without stock in Goods Receipt process (Goods
receipt message to Q26 and DMS not yet send) and stock in outbound processing (packing confirmation
interface send but no goods issue yet).
TP-08: The stock file shall contain the combination of Material and SLoc and must exclude all stock which
pack has been confirmed but not Goods Issue done.
Currently in ECC there is a Custom table where all deliveries for LSP are stored, with some additional
columns like packed/ goods issued the necessary deliveries could be identified and be excluded from the
stock file.
Page 127 of 176
June 30, 2019
10. Monitoring & Reporting & KPIs
10.1. Monitoring
To be defined
10.2. Reporting
10.2.1. Inbound
# Functionality Content Frequency Timing (CET)
1 Inbound planning Inbound planning of all flows Realtime -
Text are added for e.g. cross

dock, files are added, add trucks
on free slots, actual date/times
2 Actual truck load dates/times Truck arrival, loading start, Once per T.b.d.
loading end etc.. week?
For carrier measurement.
10.2.2. Storage
# Functionality Content Frequency Timing (CET)
1 Occupation rate Occupation rate per storage type Once per T.b.d.
(dangerous goods, cooled, day?
ambient etc.)
2 SHE + Q compliance Stock download on bin level Once per T.b.d.

including bin type and some week
dangerous goods data to be
able to check if all goods are
stored on the correct location
Page 128 of 176
June 30, 2019
10.2.3. Outbound
# Functionality Content Frequency Moment
1 Outbound planning Time slots for containers only with Realtime -

transport orders as reference.
DNP plans the containers in
DCNWEB. GEODIS adds
reference numbers, weights, seal
number etc.
2 Data for Bill Of Lading Container number, Seal number, GI confirmation

Container size, Gross weight(s).
Currently in DNWEB but can be
interfaced in GI confirmation
3 Actual truck load dates/times Truck arrival, loading start, Once per T.b.d.
loading end etc.. week?
For carrier measurement.
4 Dangerous goods checking for air Pack confirmation via EDI from Realtime -
shipments GEODIS SAP to DNP Q26.
Deliveries will have pack status C
from which reports can be
created. A fixed staging area will
be used for these deliveries.
10.2.4. General
# Functionality Content Frequency
1 VAS report With hours spent per order
10.3. Print Outputs
During the operation running, it is necessary to have documents which are physically printed. The Venlo
warehouse have two major processes:
Page 129 of 176
June 30, 2019
Inbound Process and the Outbound Process
Following documents for Printouts for inbound process, valid for Internal Geodis warehouse.
1. Unloading Card
2. Unloading List
3. SSCC labels
Following documents for Printouts for Outbound Process, valid for internal Geodis warehouse.
1. Internal SSCC Label

2. VAS Instruction
3. Logistics Labels (4 inch)
4. Loading Card
5. Loading List
6. CMR
7. Dossier
Packing List and Delivery Note from ECC.
Note:
The Unloading Card and the Loading Card will have the same format. The Detailed format for each
output will be updated in the Detailed Specification for each printout.
For Internal process – we have cycle count document as printout, for which standard SAP document will
be printed as of now. If there is a requirement then customized document will be printed.
The trigger point for the Packing List and Delivery note is Pick completion in ECC. Packing is done in the
warehouse at Outbound delivery level and when the Pack Status is set to “Completed” in EWM, a
message will be triggered to ECC, which will update the packing information in the Outbound delivery.
Delivery Note and Packing list will get printed when the Pick Status is set to “C”, i.e. completed.
10.4. KPIs
GEODIS management will report monthly to DNP management on the agreed KPIs.
11. Appendix: SAP ERP and SAP EWM Organizational structure

Page 130 of 176
June 30, 2019
<plant, storage locations, shipping points definition etc.>

Page 131 of 176
June 30, 2019
12. Appendix: Abbreviations

Term Description
AGV Automatic Guided Vehicle
APS Automatic Positioning System
BPO Business Process Owner
DCNWEB Web application of GEODIS e.g. planning and value added service data.
DMS Duty Management System
DNP DSM Nutritional Products Ltd.
ERP Enterprise Resource Planning
EWM Extended Warehouse Management
GAMP5 Risk Based approach to Compliant GxP Computerized Systems
GDP-API Good Distribution Practice for Active Pharmaceutical Ingredients
GDC Global Distribution Centre
HS Harmonized System
LDC Local Distribution Centre
MOC Management of Change
MSDS Material Specification Details Sheet
M&T Manufacturing & Technology Site
PAGO Standalone labelling system
Q26 DNP SAP ERP
RDC Regional Distribution Centre
RF Radio Frequency
RILKE WEB Web application, Web GUI for TLS (GEODIS system)
SAP ERP SAP Enterprise Resource Planning - Central Component (multi-user system)
SAP EWM SAP Extended Warehouse Management System
SLA Service Level Agreement
SOP Standard Operating Procedure
TLS Transport Lager System (current DNP Warehouse Management Execution system)
URS User Requirements Specification
WMS Warehouse Management System
Page 132 of 176
June 30, 2019
13. Appendix: Link to URS

General
U1-GT–01-ZZZ General Topics
Functional Specifications
# URS Requirement Remark
F1-GT–01-001 001 System landscape as shown in the figure must be

incorporated in the EWM design.
002 For the implementation, SAP EWM release 9.5 FP2

will be used on a DB2 Database
003 Customs system will have no direct interface to

EWM.
F1-GT–01-002 004 The system must be able to communicate all high

bay warehouse task data with Automated Positioning
System (APS) of the Narrow Aisle trucks
005 There will be no direct interface with Carriers to EWM

all interfaces will be directed to Q26.
F1-GT–01-003 006 For Kardex ASR systems, no interface is required:
Tray changes in Kardex will be directly initiated in the

Kardex user interface without being connected to
EWM.
Confirming a Kardex bin is done via scanning the

barcode of the destination bin.
Page 133 of 176
June 30, 2019
Master data
U1-MD-01-ZZZ Master Data
F1-MD-01-001 001 It must be possible to store material master data in

EWM system received from Q26.
002 Batches and classifications must be distributed to EWM
003 Customers must be distributed to EWM
004 Vendors must be distributed to EWM (incl. carriers)
F1-MD-01-005 005 It must be possible to store packaging master data in

EWM system of all packaging levels at first receipt.
F1-MD-01-006 006 It must be possible to store all relevant Hazardous SEVESO

substance data in EWM system that are needed to
define the correct put away strategy.
F1-MD-01-007 007 The existing bins (locations where material is stored)

which are in use today must be created in the EWM.
008 All currently existing storage types should be optimized.

The new storage type structure should be reflected in
EWM.
009 Shelf Rack storage must be created in the future EWM

system.
010 It must be possible to register maximum weight per SEVESO

location in the system and perform a weight check at
task creation.
011 It must be possible to export actual stored weight per SEVESO

location from the system.
Page 134 of 176
June 30, 2019
U1-DM-01–ZZZ Data Migration (Master Data and Transactional Data)
F1-DM-01-001 001 It must be possible to upload all relevant material

master data
002 It must be possible to upload all Hazardous F1-MD-01-006

substance data.
003 It must be possible to upload all packing F1-MD-01-005

specifications per material in EWM.
F1-DM-01-003 004 It must be possible to work with Dangerous Goods

data in EWM if required.
F1-DM-01-004 005 It must be possible to upload all stock and handling

unit data in EWM system including batch numbers
as provided by DNP at the migration moment.
F1-DM-01-002 006 The EWM system must allow scanning both SUID
and SSCC in all warehouse processes as long as
‘old’ stock without SSCC label is still in the
warehouse.
007 It must be possible to upload all warehouse bins in F1-MD-01-007

EWM system as provided by DNP.
F1-DM-01-005 008 It must be possible to upload open inbound delivery

data during migration.
009 It must be possible to upload all relevant vendor F1-MD-01-001

information in EWM.
010 It must be possible to upload all relevant customer F1-MD-01-001

information in EWM.
F1-DM-01-006 011 It must be possible to have the plants 2102 and

2399 with related shipping points available in EWM.
Page 135 of 176
June 30, 2019
Slot booking
U1-SB-01-ZZZ Truck Planning and Dock Scheduling
F1-SB-01-001 001 A slot planning tool must be available in EWM system

to plan and block 'time windows' and see dock status
F1-IB-03-004 always. This slot planning tool is direction independent,
i.e. same functionality for inbound and outbound.
The dock door will be assigned by receiving office after

the truck driver arrives.
002 It must be possible to register truck, dock number and

dock status real-time in EWM system as from arrival at
the office till departure.
003 EWM system must register the following truck statuses Status is set to “arrived”,
with time stamp: when a Truck reaches the
- 'arrived' premises.
- 'docked Blocked for customs (loading only)
- released for loading
- '(un)loading started'
- '(un)loaded'
- 'released for dock departure' (dock door released)
- 'departed'
004 Before (un)loading, the system must be able to SEVESO, ADR, PGS15,
determine the most optimal dock door from where the environmental license
(un)loading should take place for a TU considering
regulations and storage conditions (e.g. temp
conditions, odorous) rules and available space.
005 It must be possible to assign a door to a truck manually

in EWM from a list of possible available loading doors.
006 It must be possible to print an (un)loading card for the Must have due to dangerous
warehouse from EWM system. goods indicator (and label
code).
TO DO 007 Dock planning must be accessible for DNP.

Page 136 of 176
June 30, 2019
Inbound
U1-IB-01-ZZZ Create & change Inbound Deliveries
F1-IB-02-001 001 The system must support standard IBD with Handling Units
from production site or external supplier.
The delivery should be received via IDOC in ECC and is to
be distributed to EWM
F1-IB-02-002 002 The system must support standard IBD without Handling
Units from production site or external supplier.
The delivery should be received via IDOC in ECC and is to
be distributed to EWM without handling units.
Packaging (creation of handling units) must be possible in
EWM.
003 The system must support goods receipt of a standard IBD HU’s can be built on RF
without Handling Units from production site or external without packaging master
supplier. data, but the packing
The delivery should be received via IDOC in ECC and is to master data must be setup
be distributed to EWM without handling units. to enable put away in EWM
Packaging (creation of handling units) must be possible in
EWM, even if no packaging master data is uploaded yet.
F1-IB-02-003 004 The EWM system must support inbound delivery from .
external supplier without ASN received from supplier.
For this the IBD needs to be created in the Q26 manually.
TO DO 005 It must be possible to block inbound delivery of unauthorized SEVESO, PGS15,
materials in Q26 and EWM. environmental license.
Unauthorized means that MOC procedure has not been
finalized. Materials are not available before finalization of the
MOC procedure.
F1-IB-02-001 006 It must be possible to mark an inbound delivery (or part) for
F1-IB-06-001 Cross Dock relevancy
F1-IB-01-004 007 Reversal processes on inbound deliveries must be possible
in the system.
F1-IB-01-002 008 It must be possible to add batch numbers to inbound Valid for Inbound Deliveries
deliveries manually in EWM system sent from DNP where batch
is empty.
Page 137 of 176
June 30, 2019
U1–IB-02-ZZZ Distribute Inbound Deliveries to EWM
F1-IB-03-003 001 The IBDs created in ECC must be distributed to

EWM via standard SAP interface.
U1–IB-03-ZZZ Create Transport Units & link Inbound Deliveries
F1-IB-03-005 001 It must be possible to register pre-advice information Related to Slot booking U1-SB
from carriers (received via email or phone or
automated) and create a Transportation Unit (TU) in
EWM system along with assigned deliveries.
002 TU created for containers must contain the following
data:
•ship-from name
•carrier name
•number of pallets
•container number
+ material number / description (as stated in the
linked in- / outbound deliveries.
003 It must be possible to create a Transportation Unit
(TU) for parcel deliveries.
004 It must be possible to create Transportation Unit (TU)
in EWM without delivery assignment.
005 It must be possible to create a TU manually
U1-IB-04- ZZZ Container gas measurement
N/A 001 It must be possible to register gas No system requirement; to be covered by

measurement requirement per container procedures
N/A 002 It must be possible to release a container for No system requirement to be covered by
unloading after gas measurement procedures
Page 138 of 176
June 30, 2019
U1-IB-05- ZZZ Quantity check & systematic packing
F1-IB-03-016 002 It must be possible to print a label with barcodes PAGO label or internal SSCC
(SKU and batch) per handling unit from EWM system label?
in case there is no barcode on a visible location on
the packaging (pallet, carton, bag, drum).
F1-IB-03-015 001 It must be possible to create Handling Units (HUs) in

EWM system automatically based on the packing
specification.
F1-IB-03-015 003 EWM must be able to receive an incoming pallet

F1-IB-04-003 (SKU, batch, quantity) to the inbound delivery and
determine deviations.
F1-IB-03-015 004 EWM system must be able to link the SUID and the
SSCC:
- SUID + related material, batch and qty

received via ASN EDI from DNP in inbound
delivery data.
- pallet (handling unit content (Material, batch
and quantity) should be collected by
scanning the SUID barcode.
005 It must be possible to receive and separate quantities

and materials which do not correspond to the packing
list and/or inbound delivery of DNP.
F1-IB-03-015 006 It must be possible to receive every pallet.
Identifying a pallet can be done either by scanning a

SUID / HU number or by scanning the content of
pallet (material number, batch number, quantity).
F1-IB-03-017 007 EWM must be able to inform the warehouse operator

during the receipt check on RF if ADR materials are
in the delivery to check if labelling is applied
correctly.
Page 139 of 176
June 30, 2019
U1-IB-06- ZZZ Put away
F1-IB-03-018 001 The storage restrictions defined by material and HU must be

considered for the final bin determination.
F1-IB-03-018 002 It must be possible to use both 1 and 2-step put away process
depending on destination storage type.
In non-high-bay, pallets are put away with 1 move by a forklift.
In high-bay, there is an intermediate location in front of the aisles

(one for each aisle). Here, a resource change (standard forklift to
high-bay forklift) is required so a twostep process needs to be
automatically derived:
- Step 1: Forklift
- Step 2: Narrow Aisle truck in high bay
F1-IB-03-018 003 EWM system must be able to assign a destination storage bin
according to the put away strategy within the weight constraint of
the location.
Considering:
- Pallet types (EP, ISO, CP3)

- Pallet height
- Maximum rack level (≤ 4 meter, no limitation)
- Fast/medium/slow
The most optimal location must be determined by EWM system
F1-IB-03-018 004 It must be possible to change the destination of a warehouse task

to VAS/(re-)pack or cross dock area in EWM system.
F1-IB-03-018 005 In case of cross-dock relevancy, it must be possible to put away

the HU to the cross-dock zone so outbound can directly pick from
here. Physically, the HU must remain on the inbound zone (no
further movement inside the warehouse). For outbound, it will be
directly picked from here.
Page 140 of 176
June 30, 2019
U1-IB-07- ZZZ Goods Receipt registration
F1-IB-03-015 001 After goods receipt of the last HU of an inbound

delivery on the staging area, it must be possible to
initiate an automatic goods receipt to (available) stock
in SAP Q26.
U1-IB-08- ZZZ Customs registration
# Requirement Remark
TO DO 001 After Goods receipt is completed, it must be possible to Trigger for Customs will be GR
initiate an automatic data transfer to the customs completion in Q26 and Q26
system from SAP Q26. sends GR confirmation to
Customs LSP System
TO DO 002 The delivery needs to be sent to the customs system No system requirement, to be
within 24 hours (manual and/ or system driven trigger). covered by procedures
Page 141 of 176
June 30, 2019
U1-IB-09- ZZZ Repacking / repalletizing / (re)labelling
F1-IB-04-001 001 It must be possible to mark goods as damaged

systematically in EWM system during check-in scan
and route to damage area.
002 EWM system must be able to assign a damage
location within the damage storage type automatically
after damages are classified in system as damage and
a put away task is created at aquarium.
TO DO 003 The storage type search damaged goods must be
influenced by the stock type of the material in the HU.
TO DO 004 The damaged material must be repacked using RF.
When a new HU should be created, a new HU label
should be printed.
F1-IB-09-001 005 It must be possible to create an inbound VAS order
without routing to the VAS area to register the activities
executed before Goods receipt.
E.g. repack and repalletize.
006 It must be possible to define a material as inbound VAS
relevant to route it always to a VAS area.
e.g. Relabel / additional label ‘feed premix only’
U1-IB-10- ZZZ Inbound Quality Inspection
TO DO 001 If Quality Inspection is required for a material, then the Quality check done visual and
Handling Unit must be routed to the Quality inspection outside the system
area.
TO DO 002 It must be possible to create a Service Incident report Service Incident report will
like the DCN Web report remain in DCN Web
U1-IB-11- ZZZ Inbound deviations
F1-IB-11-001 001 It must be possible in EWM to book quantity

Page 142 of 176
June 30, 2019
discrepancies, which do not correspond to the packing

list and/or inbound delivery of DNP
002 It must be impossible to receive materials for which the SEVESO, PGS15,
MOC procedure is not finished (material data including environmental license.
base unit of measure must be complete) in EWM ‘unauthorized material’ in U1-
system. IB-01-005
U1-IB-12- ZZZ Inbound labels & documents
F1-IB-12-001 001 EWM system must be able to print a handling unit label
with SSCC pallet by pallet during check-in.
002 The HU label with SSCC must be printed on a belt
printer.
003 It must be possible to print the row number on internal
HU label with SSCC.
004 It must be possible to print an unloading list from the
system before unloading starts.
005 It must be possible to print an unloading card from the
system before unloading starts.
Page 143 of 176
June 30, 2019
Outbound
U1-OB-01-ZZZ Create Outbound Deliveries
F1-OB-01-001 001 Outbound delivery needs to be in EWM system

before cut-off time, including all required information:
- Material, Batch, Quantity
- Incoterm, Incoterm place
- Shipping remarks
- Origin country
- ERP Delivery number
- ERP Sales Order number
002 For outbound deliveries, it must be possible to
receive packing instructions from ECC in EWM
different from the packing specification.
003 Q26 must be able to send predefined VAS Codes on
the delivery item.
EWM system must be able to receive predefined
VAS codes per outbound delivery item from Q26.
005 It must be possible to distinct rush orders from
normal orders in the system to be able to give
priority to all warehouse tasks. (delivery priority)
F1-OB-01-002 004 Reversal processes on outbound deliveries must be
possible in the system.
Page 144 of 176
June 30, 2019
U1-OB-02-ZZZ Release outbound deliveries to Mainfreight
# Type Requirement Remark
F1-OB-02-001 001 After creating outbound deliveries, Mainfreight Assumption: current process for
(service agent scheduling the carriers) must be other forwarders remains
informed. -
TO DO 002 Mainfreight transportation planning and TU
scheduling must be executed in EWM
U1-OB-03-ZZZ Receive planning from Forwarder Mainfreight
F1-OB-03-001 001 In EWM it must be possible to create a TU based on Assumption: current process for
the transportation planning information received other forwarders remains
from Mainfreight.
002 Mainfreight transportation planning and TU
scheduling must be executed in EWM.
Page 145 of 176
June 30, 2019
U1-OB-04-ZZZ Create Transport Unit
User Requirements
F1-OB-04-001 001 It must be possible to create shipments in Q26

1. from interface (Mainfreight)
2. manually (i.e. Rhenus, BDP)
Carrier, date, route, max weight
F1-OB-04-002 002 It must be possible in the system to mark Solution to be defined similar to
shipments with ‘EQ inspection required’. airfreight approval process (see U1-
Shipments must be prepared one day before OB-12)
shipping to be checked by DNP.
EQ = External Quality. Agree on manual procedure possible
Only needed twice per year. without the risk of ‘slipping through’
without inspection.
F1-OB-04-003 003 It must be possible to add a hub address on a Groupage shipment = shipment
shipment in the system for groupage shipments. towards a hub of the carrier. Carrier
then distributes further to customer
in multiple separated shipments.
F1-OB-04-001 004 It must be possible for Mainfreight that one TU How is the sequence
contains multiple drop off points (common is 1 – 5). communicated? Interface?
The structure, incl. loading sequence, needs to be Clarification needed
available in EWM.
005 It must be possible to create manual TUs for parcel
delivery.
006 It must be possible to create a TU manually
F1-OB-04-004 007 It must be possible to register the following
outbound shipment data in the system:
- driver name
- ID number
- licence plate
- container number
- seal number
- stowage weight
- tare weight of container
Page 146 of 176
June 30, 2019
U1-OB-05-ZZZ Create Wave
User Requirements
F1-OB-05-001 001 EWM system must be able to create waves Mainfreight depending on Mainfreight
automatically per Transportation Unit. process redesign. If Mainfreight cannot
inform us about shipments/TU's in time,
- Containers always on TU level. we will need an additional way to build
- Mainfreight: goal to have TU prior to picking waves.
002 It must be possible to release waves manually

(multiple waves at the same time possible) as
well as automatically, based on a defined date/
time in the wave templates.
F1-OB-05-002 003 During wave release, it must be visible if all

items of a delivery inside this wave can be
completely picked.
If not, all pick tasks can be created by wave

release, a replenishment run must be executed
manually.
TO DO 004 Some VAS codes are not relevant for activities

in a work center. The system must pick directly
to staging area.
It must be visible that these delivery items need

a VAS activity.
Page 147 of 176
June 30, 2019
U1-OB-06-ZZZ Replenishment to pick bins and reverse replenishment
User Requirements
F1-OB-06-001 001 Replenishment process must be supported towards

the pick areas.
002 It must be possible in the high bay to give a higher

priority to replenishment tasks over picking tasks.
003 It must be possible in EWM system to scan

replenishments as well as reverse replenishment to
a drop zone (to remove seal) before scanning to the
destination location.
004 EWM system must be able to select pallets with To clean up warehouse and avoid
lowest quantity first for replenishment orders. a lot of partial pallets due to
reverse replenishments from Order
Pick Area.
005 The system must be able to create replenishment

warehouse tasks for selected 'open' deliveries
without picks.
006 It must be possible to view which replenishments

cannot be created in EWM system due to lack of
empty bins in order pick area.
007 It must be possible in EWM system to print a

handling unit label (with the original SSCC code) for
each reverse replenishment including row number
of the destination bin.
Page 148 of 176
June 30, 2019
U1-OB-07-ZZZ Pick task creation and removal strategy
User Requirements
F1-OB-07-001 001 EWM system must be able to prioritize picks

automatically in OPA (Order Pick Area) based on
outbound shipment planning (date/time) and expected
lead time including VAS.
002 The EWM system must be able to create pick tasks for
multiple outbound deliveries at once.
003 The system must support picking from block storage
without requesting to pick a specific handling unit
number. (e.g. picking from containers)
004 It must be possible to prioritize picks manually (for
urgent orders) in EWM system.
005 EWM system must support both one step (storage/pick
area to VAS/SA) and two steps picking (storage/pick
area to front area + front area to VAS/SA).
006 EWM system must be able to create separate Time saving to be monitored
warehouse tasks for:
- Full pallets: one task per source location respecting
the pallet quantity in the master data.
- >= 1 or >= multiple Layers (less than full pallet): one
task per source location. One warehouse order per
material.
- Loose cartons only (less than 1 layer): one task per
source location. One warehouse order per delivery.
007 It must be possible for the operator to manually assign
multiple staging areas to a shipment (truck load /
container load).
008 The system must assign a dedicated staging area for
specific materials, which need containment.
009 It must be possible to register a pick shortage.
010 When a task is overruled during picking it must be
visible that not all handling units are in the staging area
(not ready for loading).
011 It must be possible to do Outbound Cross Dock in a
similar process as regular outbound.
(Picking from cross-dock area)
012 It must be possible to cancel picks for (part of) a delivery

without the need of complete roll-back of the materials
Page 149 of 176
June 30, 2019
User Requirements
to (high bay) stock.

 Full line cancellation
 Partial line cancellation
 Partial pallet cancellation (repack and cancel)
013 For a cross dock delivery, the system must look for
stock in the cross-dock area first.
014 It must be possible to move the picked HU to different
destinations in the warehouse depending on the next
step in the process (e.g. pick, vas, stage…).
015 It must be possible to send a picked Full Pallet directly
to a staging area
016 When moving a full pallet directly to staging area, the
printing of the shipping label should be triggered
automatically.
017 If a partial pallet of the exact requested quantity is
available in the high bay, it must be possible to pick it
from high bay to VAS or SA directly without
replenishment via OPA.
018 It must be possible to pick less than a full pallet (layer, e.g. Penta pharm. ADR 4.2
loose cartons/bags) from the bin in the high bay area for
specific materials.
These materials will not go via the OPA (Order Pick
Area) but will be picked from the bin.
019 It must be possible to pick drums (not full pallet) from a
bin without replenishment. (pick point).
020 EWM system must support a process to join partial
pallets to full pallets and/or layers including multiple
batches
021 Partial picks must start with empty handling unit of
correct packaging material.
022 During picking the HU creation should result in:
- Full pallets: HU per pallet
- Full layers: 1 HU for all layers
- One HU for all colli, will be split up in pack center
later
Page 150 of 176
June 30, 2019
U1-OB-08-ZZZ VAS Activities in outbound process
User Requirements
F1-OB-08-001 001 It must be possible to perform a Repack activity in any

packing workstation.
002 If a HU is relevant for repack and VAS, it must be routed

to the repack station only.
No move to second a VAS work centre is needed

because VAS can be done in the same (repack) work
centre.
003 It must be possible to send a HU from a repack station to

a staging area.
004 It must be possible in the OPA work centre to confirm This is part of four eye check
picked quantity (after blind count). requests.
005 It must be possible to indicate that a VAS activity is

completed.
006 In case the VAS code is entered that something is not

packed according to the generally agreed rules, the
system must be able to show the packing instruction text
of the ERP Delivery item to the warehouse employee in
the VAS area
007 It must be possible to use staging areas as temporary

VAS area in EWM system.
008 Picked handling units from OPA which need a VAS

activity after picking must be sent to a specific work
009 The system must be able to create warehouse tasks from

VAS area to staging area per Handling Unit.
010 It must be possible to send a full pallet pick HU directly to Merge will be incorporated in
destination merge/repack for doing the merge / repack replenishment via OPA
activities.
011 The system must be able to route outbound goods via

VAS area automatically for VAS relevant
Page 151 of 176
June 30, 2019
User Requirements
materials/deliveries to (re)label, re-palletize, repack.
012 After VAS activity completion, it must be possible to print

a SSCC shipping label, in the VAS area.
When all VAS activities are completed the user must

confirm the completion of these activities and marks the
HU as completed”. This will trigger the creation of the
next task. Destination could be either truck or staging
area.
U1-OB-09-ZZZ Staging
User Requirements
F1-OB-09-001 001 All Handling Units (HUs) for one shipment will be staged in
002 If a HU needs containment, limited staging needs to be

considered.
(example: containment, HU stored in phase 1 of the

building must be staged in phase 1)
003 After successful complete delivery staging, the HU data Related to U1-OB-13
must be transferred to Q26. An interface to customs
system must be automatically triggered (including the final
HU information).
Page 152 of 176
June 30, 2019
U1-OB-10-ZZZ Perform Dangerous Goods air delivery activities
User Requirements
F1-OB-10-001 001 The system must be able to block a delivery in EWM

for loading until the check of air shipments with
dangerous goods by DNP is finished.
002 It must be possible to monitor if the dangerous goods

/ Air deliveries have been checked.
U1-OB-11-ZZZ Update of packaging information in Outbound Delivery
User Requirements
F1-OB-11-001 001 EWM must update the Q26 outbound delivery with
the packing information when in EWM the packing
complete status is set.
Page 153 of 176
June 30, 2019
U1-OB-12-ZZZ Loading
User Requirements
F1-OB-12-001 001 The system must provide an overview of staging

areas per TU to assign the most suitable door for
loading.
TO DO 002 As soon as the truck is ready for loading the loading

warehouse tasks must be created in EWM.
TO DO 003 Loading is executed by scanning every HU to the

assigned door. Now it is being physically loaded. In
case a wrong HU is scanned an error message is
required.
TO DO 004 Loading status must be completed after loading of

the last pallet (by scanning).
TO DO 005 It must be possible in EWM system to unload

handling units again systematically (e.g. in case of
damage, BOSS check).
TO DO 006 The system must prevent loading in case shipment is

not completely staged.
TO DO 007 It needs to be possible to create a nested HU in a

user-friendly RF transaction prior to start of loading.
The basis for loading must be always the Top-HU
(internal warehouse activity)
TO DO 008 It must be possible in EWM system to scan multiple

handling units at once to the dock during loading.
009 The system must prevent loading of deliveries which

are blocked by DNP in Q26 (BOSS check).
F1-OB-12-002 010 BOSS check must follow Management Directive 03.

Page 154 of 176
June 30, 2019
U1-OB-13-ZZZ Post Goods Issue & Truck Departure
User Requirements
F1-OB-13-001 001 It must be possible to do a manual goods issue on

TU level (truck/container load) in the system for all
related outbound deliveries.
TO DO 002 When goods issue is posted for the TU, the door
must be released automatically, and TU status will
be placed on departed’’.
TO DO 003 It must be possible in EWM system to release a

dock manually.
Page 155 of 176
June 30, 2019
U1-OB-14-ZZZ Outbound documents
User Requirements
F1-OB-14-001 001 It must be possible to print a form to add to the Customs / dossier information to
outbound dossier (export information, delivery no., replace hardcopy of Transport
net and gross weight, ADR, planned loading date, Order. Replacement of 3 print outs.
special instructions).
TO DO 002 The system must print a document with delivery
details (incl. ADR details) to be attached to the CMR
(Road Transportation document).
TO DO 003 It must be possible that after pack confirmation of
delivery in EWM, the following printouts are directly
issued from ERP:
 Packing list
 Delivery note
 Certificates of origin
TO DO 004 It must be possible to print only the lower level HUs
on the Delivery Note (excluding the top-level HU of
a Nested HU)
TO DO 005 The system must be able to print all delivery notes
for a TU/Shipment.
TO DO 006 It must be possible to print a CMR on shipment or Business to clarify, usually it is:
on delivery level depending on the situation. - Delivery level: Delivery note
- On shipment level if the truck goes via a hub - Shipment level: CMR for whole
(groupage shipments) truck
- On delivery level for all other shipments (direct
shipments).
TO DO 007 It must be possible to print the T1 number on the

CMR.
TO DO 008 It must be possible in EWM to print VAS/packaging
instructions in the work center for a specific SSCC.
TO DO 009 It must be possible in EWM to print VAS/packaging
instructions in the work center for all pallets in a
delivery and for that workstation.
TO DO 010 It must be possible to print a loading list from EWM.
The loading list should contain the TU number, list
of HU’s on TU, loading sequence.
TO DO 011 It must be possible to print a loading card for the
warehouse from EWM system.
Must have due to dangerous goods indicator (and
Page 156 of 176
June 30, 2019
User Requirements
label code).
U1-OB-15-ZZZ Outbound logistic labels
User Requirements
F1-OB-15-001 001 The system must be able to print logistics label during
various steps in the process, depending on the order
flow: 1st step, 2nd step, VAS, packing.
002 The system must be able to print one logistics label
per handling unit.
003 The system must be able to print logistics labels
according to DNP specification (GS1 layout)
containing SSCC codes. For full pallets SSCC codes
from storage can be reused.
Page 157 of 176
June 30, 2019
Storage
U1-ST–01-ZZZ Storage
User Requirements
F1-ST-01-001 001 For every plant, EWM must be able to support

appropriate number of storage locations. These
storage locations are linked to the warehouse number
that is managed by EWM.
TO DO 002 For the main warehouse in Venlo, one shipping point is
relevant:2102. For the external locations, a shipping
point must exist.
TO DO 003 EWM system must support storage inside containers No yard management
placed outside the warehouse (smelling materials,
quarantine).
TO DO 004 During the picking process, it is important to optimize
the path to the pick-location. Therefore, special storage
sections for fast, medium or slow-moving materials are
installed. The warehouse optimization needs to assure
the optimized allocation of these storage sections.
TO DO 005 For put away and reverse replenishment movements, The HU type should be checked
the HU type must be automatically adjusted depending any time when the HU quantity is
on the actual quantity of material on the pallet. This changing (not for mixed HUs).
allows to derive a smaller suitable bin (and prevents
empty space in bins in the high bay)
TO DO 006 EWM system must be able to operate with multiple
stock types as required by the business process and if
required EWM system must be able to create additional
stock types.
TO DO 007 Q26 system should be adjusted to cope with the
different storage locations related to the EWM stock
types.
TO DO 008 It must be possible in EWM system to authorize stock SAP system authorization
changes from status ‘returned’ to ‘available’ for limited
users only.
TO DO 009 The EWM system must allow scanning the SUID of
Q26 (current) and /or the SSCC of EWM in all
warehouse processes if ‘old’ stock without SSCC label
is still in the warehouse
TO DO 010 It must be possible to handle all DNP and VLB
Page 158 of 176
June 30, 2019
User Requirements
consumables (which are measured in quantity) in the

system (including personal protection materials).
TO DO 011 The “uitzoekhoek” should have an ambient and Initiated by QA
cool/cold section, in case deviations occur with
materials being cool/cold.
TO DO 012 Log for label printing: For all labels, the print log files Done in DCNWeb
need to be imported and stored in system.
U1-ST-02-ZZZ External Warehouse and Overflow Warehouse
User Requirements
F1-ST-02-001 001 It must be possible to set up the external warehouse

locations as IM managed storage locations in ECC.
TO DO 002 It must be possible in EWM system to ship materials to

external & overflow warehouses with a similar picking
process as customer outbound deliveries including an
outbound delivery and CMR.
TO DO 003 There must not be any mixed deliveries picking stock

from external and internal locations.
TO DO 004 It must be possible in EWM system to receive materials

from external and overflow warehouses equal to the
normal inbound flow including an inbound delivery.
TO DO 005 When a pallet returned from overflow has an SSCC, it SSCC needs reprinting with a
must be possible to reuse this number to maintain different row number
traceability
Page 159 of 176
June 30, 2019
U1-ST-03-ZZZ Physical inventory
User Requirements
F1-ST-03-001 001 EWM system must be able to trigger physical inventory For Zero Stock Check, an
count based on the following events: Exception code may require to
 Ad-hoc requirement: A quantity deviation, etc. be entered.
was noticed and the stock needs to be
adjusted.
 Cycle counting: Based on the cycle counting
indicator in the material master, the material
requires physical inventory count.
 Zero stock check: When a bin is completely
emptied the bin receives the status “counted”.
An additional confirmation during picking is not
required.
 Annual counting (wall to wall): The physical
inventory document is manually created.
TO DO 002 It must be possible to have stock of two different To be confirmed by business:
owners on the same bin in the warehouse. During Two owners are only allowed in
physical inventory processing, it is not needed to OPA area, not in high bay.
distinguish between the two owners. Only the total
quantity should be counted.
TO DO 003 It must be possible to do physical inventory counting on When physical inventory
RF or on paper. counting is done in RF the bin
will not be blocked while the PI
document is being created
TO DO 004 The results will be entered by the person executing the To be covered by a procedure
count. The posting of the results will then be executed
by a second person. The four eyes principle must be
met.
TO DO 005 When an inventory difference is counted, it should not
be posted to ERP automatically. It should remain in
EWM until someone with the correct authority clears it.
TO DO 006 The system must support (cycle) counting while open
orders exist.
TO DO 007 The system must support counting of empty bins.
TO DO 008 The difference clearing process is used to write off SOP as is stays in place
stock differences that were identified in EWM to ERP.
Page 160 of 176
June 30, 2019
U1-ST-04-ZZZ Deliver to destruction / Rework and Tolling
User Requirements
F1-ST-04-001 001 For scrapping, rework and tolling processes, a free of

charge delivery with different delivery type must be
created in ERP and distributed to EWM.
002 In EWM, the quants to be:
 Scrapped
 Reworked
 Tolled
need to be differentiated from other stock to
allow specific stock determination. Stock
search based on material, batch, stock type,
storage type, etc.
Page 161 of 176
June 30, 2019
U1-IN–01-ZZZ Cross process settings & Internal processes
User Requirements
F1-IN-01-001 001 The system must be able to assign warehouse tasks in

one aisle to one Narrow Aisle truck only.
F1-IN-01-002 002 The warehouse tasks will be assigned to queues.

Depending on the process (inbound, internal,
replenishment, picking, high bay…) different queues
need to be derived.
The warehouse workload can be managed by using
these queues and assigning resources to the queues.
F1-IN-01-003 003 It must be possible in the system to overrule movements
(warehouse tasks of put away, picking, replenishment,
reverse replenishment) and reroute to a packing station
(for repacking in case of damage / damaged label).
F1-IN-01-004 004 The high bay operations must to be optimized so that
pick and put-away operations can be combined
(interleaving).
F1-IN-01-005 005 The system must be able to show VAS instructions on
RF during movements (warehouse tasks of put away,
picking, replenishment, reverse replenishment).
F1-IN-01-006 006 It must be possible to nest handling units in all work Clarification needed.
centres to support internal moves and loading with only Duplicate with the URS in
one scan afterwards. loading for creation of nested
HU’s?
F1-IN-01-007 007 For batch changes for shelf life extension a VAS
relabelling order is required. The stock needs to be
blocked for picking during the relabelling activity.
008 It must be possible to do a material change in EWM
system (material number X to material number Y or batch
number X to batch number Y) including routing via work
center.
F1-IN-01-008 009 It must be possible in EWM to create VAS orders to do
VAS activities (e.g. shelf life extension, re-label, re-pack,
material to material bookings etc.) on stock
materials/sscc (no linked to inbound or outbound
movements)
F1-IN-01-009 010 The system must support ad hoc repack of stock.
Page 162 of 176
June 30, 2019
U1-IN-02-ZZZ GDC & RDC
User Requirements
F1-IN-02-001 001 Stock from two different plants are stored in the Venlo
warehouse. The stock of these two plants must be
considered for the implementation of all warehouse
processes
 Global Distribution Centre (GDC)
 Regional Distribution Centre (RDC)
002 The warehouse operators should not be impacted by the
ownership split and changes of ownership. In the
execution of the warehouse processes.
003 Transfer of ownership must be possible without physical
movement of the pallets.
It must be possible to transfer stock from plant 2399 to
plant 2102 via ZTRO (Transfer Order). Reverse process
must be possible as well. (not necessarily via ZTRO
transfer order)
Page 163 of 176
June 30, 2019
Returns
U1-RT-01-ZZZ Returns to Supplier (Outbound)
User Requirements
TO DO 001 EWM system must be able to recognize return Valid for all suppliers both internal as
deliveries (delivery type from ECC) and assign return external.
stock. On outbound side there are 3
transactions in current situation ZRT6,
ZRT7 and ZRT8.
U1-RT-02-ZZZ Returns from Customer (Inbound)
User Requirements
TO DO 001 EWM system must be able to recognize return deliveries

(delivery type from ERP).
TO DO 002 EWM system must be able to send all relevant customs
information to DNP Q26 at goods receipt of returns per
delivery
TO DO 003 For a return receipt, the HU must be routed to the returns Separate storage types and
area after Goods receipt for a visual quality inspection. areas will be defined -one for
normal material and another
for cooled material.
TO DO 004 It must be possible to reject a delivery if a return is not
accepted.
In case of rejected return, a manual clarification process
with the customer returns department
TO DO 005 After visual inspection, it must be possible to create a
task in EWM either to available stock or to blocked stock,
depending on the quality.
TO DO 006 DNP system must be able print a Visual Control Procedure; not system
Document requirement
TO DO 007 The system must be able to send all relevant customs Customs information sent from
information to GEODIS DMS per delivery at goods DNP Q26
receipt of returns.
TO DO 008 EWM system must be able to handle processing of
Returns from the Quarantine area. It must be possible to
register actions for returns in EWM system including
Page 164 of 176
June 30, 2019
User Requirements
workflow (after returns are placed in the correct returns

area, an inspection by DNP needs to be performed. A
system trigger is needed to inform DNP that a check is
needed).
Customs
U1-CU-01-ZZZ Customs
User Requirements
F1-CU-01-001 001 Receipt confirmation interface (Q26 to LSP (TP01),

After a truck is completely received.
F1-CU-01-002 002 Receipt approval, after customs approval of the receipt,

LSP to Q26 (TP04)
F1-CU-01-004 003 Stock adjustment interface from Q26 to LSP (TP09)
004 Stock assignment interface after packing completion

from Q26 to LSP (TP05)
005 Release delivery for loading, release from customs for

loading, LSP to Q26 (TP06)
006 It must be possible to generate a stock snapshot from

Q26 to LSP for stock comparison (TP-08). The
snapshot should not include stock
 Received in EWM but not posted in Q26

Set to pack complete but not Goods issue
F1-CU-01-003 007 Material Change interface. If a material change is done

in Q26 an interface must be sent to the LSP system
(TP-11) (Only material number change no other
changes e.g. Batch/Status/Best Use before Date etc.)
Page 165 of 176
June 30, 2019
Monitoring & Reporting & KPIs
U1-MT-01-ZZZ Slot Booking Monitoring
User Requirements
# Ty Requirement Remark
pe
TO DO 001 It must be possible in EWM system to monitor the Clarify requirement?

current Dock loading activities and status.
 Loading Dock door
 Assigned TU
 Loading date & time
 Total SSCC
 SSCC Loaded
 Person assigned
 Boss Check Block (Yes/No)
 Loading TU
 TU Number
 Mode of transport,
 Loading date & time
 Number of SSCC
 BOSS check
 Complete
U1-MT-02-ZZZ Inbound Monitoring
User Requirements
# Typ Requirement Remark

e
TO DO 001 Inbound ing:

It must be possible to search inbound delivery by:
 PO number
 ERP Delivery number
 material number
TO DO 002 It must be possible to view order and task details to be able
to make a detailed plan to manage the warehouse operation
for inbound (work on hand, work done).
TO DO 003 It must be possible to monitor the following inbound data
 Number of pallets needs GR scan
Page 166 of 176
June 30, 2019
User Requirements

e
 Number of warehouse tasks staging area to Front (end

location in high bay -ROW in detailed data)
 Number of warehouse tasks Front to end location in
high bay
Number of pallets in front and staging areas
TO DO 004 EWM system must be able to show VAS activity status per
inbound delivery.
TO DO 005 It must be possible to monitor the lead time of handling units
in the staging area in EWM system as from unloading.
U1-MT-03-ZZZ Outbound Monitoring
User Requirements

e
TO DO 001 Outbound monitoring:

It must be possible to monitor the following data in
system:
- Outbound delivery - outbound shipment status
- All outbound shipments per time slot and
status
- All outbound deliveries per time slot and status
(picked, VAS, packed/staged, loaded)
- # pallets staged /packed per staging area
Loading status per dock door
TO DO 002 Outbound monitoring:
It must be possible to run reports of the outbound
activities performed during a period (e.g. number of
materials shipped, VAS activities).
TO DO 003 Outbound VAS activity monitoring:
It must be possible to monitor VAS activities at
outbound in the system.
 Per Work Center
 Delivery
 Status (started)
 Loading Date/Time
Page 167 of 176
June 30, 2019
User Requirements

e
 Shipment
 Material Number
 Batch
 number of Total pallets
 Number of Finished pallets
 All VAS Codes and VAS Code
description per material
 SSCC Per material
 DG indicator
It must be possible in EWM system to monitor the
current and planned VAS activities
Overview Deliveries in Waves with VAS with VAS Code
and Explanation.
 Filter on VAS Code
 If VAS is started
 HB picks and OPA picks
 pallet requirements
current activities in OPA WC
 OPA WC per Pick Area (OPA40, OPA60)
 Per SSCC
 Delivery
 Loading Date/Time of delivery
 Shipment
 Material Number
 Batch
 Quantity
 All VAS Codes and VAS Code
description
 DG indicator
Page 168 of 176
June 30, 2019
U1-MT-04-ZZZ Warehouse Activity Monitoring
User Requirements
TO DO 001 Warehouse operations monitoring:

It must be possible in EWM system to have in one
overview detailed information to manage the
warehouse operation for outbound:
# replenishments high bay 1st/2nd step
# reverse repl. High bay 1st/2nd step
# picks high bay 1st/2nd step
# picks order pick area (incl. samples) + drop zones
# picks block storage
# picks external
# picks cross dock
# pallets / cartons / bags with VAS activity (label,
merge, repack)
It must be possible to monitor and assign employees
to warehouse tasks in EWM system. One overview
needed to see all employees with type of work they
are performing.

current workload on hand and status of the
workload.
 Monitoring of Waves (wave level)
 Wave description
 Status (release, Partly Complete).
 How many Full and Partial
 Mode transport (Air/LCL/SEA/Truck)
 Loading Date/Time.
 Temperature condition (highest T1 –
T8)
 DG indicator (yes/no)
 Vas indicator (yes/no)
 picks per que. (only applicable when
task is created inactive)
 RPL's (only applicable when tasks
are created inactive)
 Errors in Task Creation.
Page 169 of 176
June 30, 2019
User Requirements
 Progress of wave.
 Per wave List all deliveries.
 Delivery Number
 Number of lines
 Pallet requirements.
 Total Quantity
 Temperature condition (highest T1 –
T8)
 picks per que. (only applicable when
tasks are created inactive)
 RPLs (only applicable when tasks
 Progress of Delivery.
 Per Wave Delivery All Lines
 Material
 Batch
 QTY
 Pallet requirements.
 Temperature condition (T1 – T8)
 Picks per queue (only applicable
when task are created inactive)
 RPLs (only applicable when tasks
 Monitoring per Queue
 Number of Picks
 Number of assigned resources.
 Queue front as one Queue distinct
 Picks
Page 170 of 176
June 30, 2019
User Requirements
 RPL (with Destination OPA)

 Internal Moves (With
Destination)
 Put away
 For HB Queues
 Per HB Row Pallet pick/Put/RPL in
front
 Per HB Row Pallet Put GR zone
 Resources
 Currently Driving
 SSCC
 Resources
 Start Time
 User
TO DO 004 Replenishment monitoring:
It needs to be assured that in the open pick area,
there are always empty bins.
A report must be available to determine which
pallets to send back to the high-bay racks
(housekeeping/ reverse replenishment).
This report must provide info about:

- Open Picks
- Temperature conditions
- Time in ambient order pick area
- Fast/medium/slow mover (for order pick area)
This report must create warehouse tasks for reverse

replenishment until a defined number of empty
locations per picking area are available.
TO DO 005 Storage monitoring:
The system must register all internal moves for
traceability. Each physical process step including
put-away strategy must be accompanied by
scanning on RF.
TO DO 006 Storage monitoring: Environmental license, firefighting
It must be possible to monitor the time dangerous installation, temperature control
goods (ADR) and CMR goods are stored in
(un)loading areas (max. 48 hours allowed) in EWM
Page 171 of 176
June 30, 2019
User Requirements
system.
 Staging/Unloading Area
 Material
 Batch
 SSCC
 ADR Class/CMR material
 Weight Kg
 Number of Units (Box/Bag/Pail)
 Days in Staging/Unloading Area
TO DO 007 Replenishment monitoring:
It must be possible in EWM system to see which
reverse replenishment orders can be done based
on:
- Temperature conditions
- Time in pick area
- ABC Classification for OPA (if possible)
TO DO 008 Work-center activity monitoring:

current activities in OPA WC.
TO DO 009 It must be possible to see overdue tasks in EWM Overdue is > 24 hours after
system to assign a person to put away of that unloading (agreement with DNP). If
shipment / staging area manually; e.g. IBCs, cooled, > 24 hours for cooled and cold
cold. products, SOP must be followed.
U1-RE-01-ZZZ Inbound Reporting
pe
TO DO 001 It must be possible to run reports of the inbound

activities performed during a period (e.g. number of
received materials, VAS activities). Details to be
specified in Functional Specification.
TO DO 002 It must be possible to run a report with all container

data required to determine if gas measurement is
mandatory
Page 172 of 176
June 30, 2019
U1-RE-02-ZZZ Outbound Reporting
pe
TO DO 001
U1-RE-03-ZZZ Storage Reporting
User Requirements
pe
TO DO 001 It must be possible to generate a detailed stock Fire containment report in EWM
snapshot from EWM system incl. (dangerous goods)
master data for reporting according to SEVESO
TO DO 002 It must be possible to view the location of the
handling unit always in EWM system.
TO DO 003 It must be possible to trace each handling unit in
each step in EWM system, also if multiple pallets are
moved at once for different zones/locations
TO DO 004 It must be possible in EWM system to trace time that
products are in different temperature conditions
within the full process in the warehouse.
GDP for API (Active Pharmaceutical Ingredients).
TO DO 005 EWM report should be in place that, and the end of a Initiated by QA
working day, there are no
delayed/extended/postponed not picked up outgoing
deliveries with cool/cold materials on the staging area
(ambient section).
U1-KPI-01-ZZZ KPIs
pe
TO DO 001 EWM system must be able to handle the KPI

reporting requirements.
Page 173 of 176
June 30, 2019
Page 174 of 176
June 30, 2019
Appendix: List of development objects (RICEF)
RICEF stands for:
- Reports
- Interfaces
- Conversion
- Enhancements
- Forms
This chapter gives an overview of all developments listed in this FS document. These are all the objects
that cannot be realized with standard customizing and master data of the SAP system.
Note that developments related to deactivation of old functionality in Q26 are not mentioned here, as they
are not related to the future system landscape.
Note that developments related to data migration are part of the data migration plan.
If a Req# appears to be missing (for example EWM19) this is because the object was defined as out of
scope.
Req# Description
CUS01 TP-03 Material Receipt approval request

CUS02 TP-04 Receipt of GR posting approval
CUS03 TP-05 Loading approval request
CUS04 TP-06 Approval for Loading
CUS05 TP-08 Stock file - stock synch
CUS06 TP-09 Stock Adjustment
CUS07 TP-11 Material to material change and Country of Origin change
ECC01 ECC01 - New DELVRY05/07 from Q26 delivery to Mainfreight
ECC02 ECC02 - new IDOC (SHPCON)? from Mainfreight
ECC03 ECC03 - SHPMNT IDOC to EWM to create shipments (Container + Mainfreight)
ECC04 ECC04 - Packing in ECC based on ASN with SUID
ECC05 calculation for container shipments / Mainfreight now done by PGPD (to
ECC05
support CSA in future)
ECC06 ECC06 - DG data in Q26 from P43 as EWM
ECC07 - HU confirmation in EWM updates status of shipment in Q26 for the
ECC07
SEDI/FORI
ECC08 - Flag for “stick to pre-generated packing”; manual packing instruction as
ECC08
sales order/delivery text
Page 175 of 176
June 30, 2019
ECC09 ECC09 - Report packed air shipments for DG labelling check

ECC10 ECC10 - Transfer of Ownership (Step 6 program)
ECC11 ECC11 - Adjust required outputs in Q26 from the PGPD to the actual pack data
ECC12 ECC12 - Adjust outputs with the SAP standard DG information + used reports
ECC13 ECC13 - adjust ZD04 in Q26 with overflow and external stock information
ECC14 ECC14 - ZB51 for movement type 647
ECC15 ECC15 - YSPx outputs – prevent manual selection of the conditions records
ECC16 - Outbound process: TP06 idoc releases delivery + RFC to EWM to unblock
ECC16
TU for loading
EWM01 EWM01 - Outbound VAS Enhancements + Display of VAS text instruction
EWM02 EWM02 - RF Screen on inbound for Dangerous goods labels
EWM03 EWM03 - VAS status on header level
EWM04 EWM04 - RF Screen adjustments
EWM05 EWM05 - WO Creation enhancements
EWM07 EWM07 - Door determination inbound
EWM08 EWM08 - SUID SSCC Conversion routines on RF
EWM09 EWM09 - SUID registration inbound
EWM10 EWM10 – Read packspecs with fields from ECC
EWM11 EWM11 - Print HU function in RF
EWM12 EWM12 - Send packaging data at packing complete
EWM13 EWM13 - Calculation of HU Type
EWM14 EWM14 - Wave Building
EWM15 EWM15 - Transaction for TU Details
EWM16 EWM16 - Process based RF messages
EWM17 EWM17 – Batch specific replenishment
EWM18 EWM18 - Boss check Delivery block
EWM20 EWM20 - Staging Area determination from RF on wave level
EWM21 EWM21 - Reverse Repl. monitor with function to create WTs
EWM22 EWM22 - Trigger print of Delivery notes in ERP from EWM
EWM23 EWM23 - CIF Restrict update of fields
EWM24 EWM24 - Goods Movement bin determination
EWM25 EWM25 - Returns related PPF trigger - 3 triggers and Email sending
EWM26 EWM26 - Update External ID in HU at time of GR
EWM27 - Inbound process: Post from Customs Blocked to Available stock after TP-
EWM27
04
EWM28 EWM28 SAP Note 2191953 - Cancellation of tasks in status 'waiting'
EWM29 - Outbound Process: Blocking of outbound TU on staging area (block for
EWM29
loading) + RFC to ERP for status update
PRN01 PRN01 - Logistics Label
Page 176 of 176
June 30, 2019
PRN02 PRN02 - Internal SSCC Label

PRN03 PRN03 - CMR (Standard with DG Data on second page)
PRN04 PRN04 - Loading / Unloading List
PRN05 PRN05 - Unloading Card
PRN06 PRN06 - VAS Instruction
PRN09 PRN09 - Loading card
PRN10 PRN10 - Overview document for export data customs (Dossier)
END OF DOCUMENT

20190630 DNP GDC Venlo EWM Functional Specification - v13

Uploaded by

Copyright:

Available Formats

You might also like

20190630 DNP GDC Venlo EWM Functional Specification - v13

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

20190630 DNP GDC Venlo EWM Functional Specification - v13

Uploaded by

Copyright:

Available Formats

For Internal Use Only

September 14th, 2018

Project Brief DNP Project GDC Venlo WMS

DNP GDC Venlo EWM project

June 30, 2019

DNP GDC Venlo EWM-project

Project name DNP GDC Venlo EWM project

 how the system will support the future business processes as

It also summarizes references to custom build solutions needed to

Name Role Date Signature

Karsten Walther DNP IT Project Member

Version Date: Author(s) Remarks

0.1 19-Oct-2018 Thomas Vancaeneghem Initial draft

June 30, 2019

DNP GDC Venlo EWM-project

11 10-04-2019 Karsten Walther Added Mainfreight outbound flow.

June 30, 2019

DNP GDC Venlo EWM-project

Company Name Function

DNP Roel Horsten Head Global Distribution Centre DNP

June 30, 2019

DNP GDC Venlo EWM-project

1. Objective of this document........................................................................................................................... 11

F1-GT–01-001 System Landscape..........................................................................................................................12

Overview & Data Migration Plan...........................................................................................................................13

F1-MD-01-001 Basic master data (Vendor, material, customer, batch)................................................................14

F1-MD-01-005 Packaging specification.................................................................................................................15

F1-MD-01-006 Hazardous substance.....................................................................................................................16

F1-DM-01-001 Product Master data EWM............................................................................................................19

F1-MD-01-007 Storage bin EWM..........................................................................................................................19

F1-DM-01-002 SUID migration to SSCC.................................................................................................................19

4.1. F1-SB-01-001 Slot booking tool.......................................................................................................................21

4.2. TU statuses (in- and outbound)......................................................................................................................21

4.3. Inbound appointment handling......................................................................................................................21

4.4. Outbound appointment handling...................................................................................................................23

June 30, 2019

DNP GDC Venlo EWM-project

5.1. Inbound information.......................................................................................................................................27

5.2. Inbound process scenarios..............................................................................................................................28

5.3. Inbound process steps....................................................................................................................................29

5.4. Exception Handling Inbound...........................................................................................................................51

5.5. F1-IB-12-001 Inbound: labels & documents....................................................................................................55

June 30, 2019

DNP GDC Venlo EWM-project

F1-OB-01-001 Create outbound deliveries.............................................................................................................56

F1-OB-01-002 Reversal processes on outbound deliveries.....................................................................................59

F1-OB-02-001 Release outbound deliveries to Forwarder.....................................................................................59

F1-OB-03-001 Receive planning from Forwarder...................................................................................................60

F1-OB-04-001 Create Transport Unit.....................................................................................................................63

F1-OB-04-002 EQ Inspection required...................................................................................................................64

F1-OB-04-003 Hub address....................................................................................................................................64

F1-OB-04-004 Outbound Shipment data...............................................................................................................64

F1-OB-05-001 Create Wave...................................................................................................................................65

F1-OB-05-002 Release Wave.................................................................................................................................65

F1-OB-06-001 Replenishment to pick bins and reverse replenishment..................................................................66

F1-OB-07-001 Pick task creation and removal strategy.........................................................................................68

F1-OB-08-001 VAS Activities in outbound process.................................................................................................73

F1-OB-10-001 Perform Dangerous Goods air delivery activities............................................................................78

F1-OB-11-001 Update of packaging information in Outbound Delivery................................................................78