www.KNAPP.

com

Development Order
C903A

2012

Order release

Customer: ESTÉE LAUDER Companies

Project: C903A ELC

Consultant: Julia Friedl

Developer: Agoston Gyulai

Time recording: Realisierung – 2012 Order release

BBP Version: 20190719_ELC_Business-Blue-Print_V1.4_Outbound_planning

BBP Chapter.: 6 Order start

FRICE-ID: 6391

KNAPP IT Solutions GmbH • Parkring 1 • 8074 Grambach bei Graz • Austria • +43 50 495 - 9100
Uni Credit Bank Austria AG • BIC: BKAUATWW • IBAN: AT611200052959159109 • FN: 383109 x • UID: ATU67349648 • DVR number: 4017059
 www.KNAPP.com

Change log

Version Date Author Remarks

1.0 22.11.2019 FRJ Initial version

2.0 02.04.2021 WIN Updated version after development and some design changes

23/04/2023 844573593.docx 2/17

 www.KNAPP.com

Content
1 Introduction 4
2 Chapter 1: Order release strategy 4
2.1 Acceptance criteria 4
2.2 Mockups / Use Cases / Processes 5
2.3 Additional information 5
3 Chapter 2: Order Release VAS Carrier 9
3.1 Acceptance criteria 9
3.2 Execution flows 9
3.3 Mockups / Use Cases / Processes 9
3.4 Additional information 9
4 Chapter 3: Order Release AUX Carrier 10
4.1 Acceptance criteria 10
4.2 Execution flows 10
4.3 Mockups / Use Cases / Processes 10
4.4 Additional information 10
5 Chapter 4: Cello Wrapping 10
5.1 Acceptance criteria 10
5.2 Execution flows 11
5.3 Mockups / Use Cases / Processes 13
5.4 Additional information 14
6 Customizing 15
7 Architecture 15
8 Technical implementation 15
8.1 Entry point 15
8.2 Packages 15
8.3 Implemented BAdI’s 16
8.4 Important classes / function modules 16
8.5 Database tables 16
8.6 Checkpoint groups 16
8.7 Others 16

23/04/2023 844573593.docx 3/17

 www.KNAPP.com

1 Introduction
Order release will be used in order to finally release created WHOs while cartonization. These WHOs
will always be created “locked” and the order release therefore controls a timely start of the WHOs,
while monitoring the capacity utilization of the stations. Several checks need to be done before a
WHO can be released in the system, which are described in this DO.
Furthermore, the process for the WHO release for automated cello wrapping is also described in this
DO. Automated cello wrapping is part of the order release of a WHO but will only be executed for full
cases with the VAS-Code for automated cello wrapping. As this VAS activity is quite time consuming
the goal is to sum up similar WHO with same defined criteria in order to limit the change over time for
cello wrapping to a minimum.
The release in the system doesn´t mean a physical order start, as this is controlled by KiSoft SRC
and described in the DO: C903A_2013_A_Logic in carton erection.

2 Chapter 1: Order release strategy

The process of the order release with a push strategy includes the following criteria for the order re-
lease. All three criteria must be fulfilled otherwise WHO is not allowed to be released by the system:
- Check if cut-off time has already been reached, for each area.
- Check if capacity is available on the conveyor and on the station(s) (workstation group).
- Check if labels are already pre-picked for VAS execution for storage type OSR
For the order release groups of workstation will be used. This means if there are multiple of one work-
station executing the same process a workstation group will be considered for the calculation of the
capacity.

2.1 Acceptance criteria

a) The system release all WHO which “planned goods issue time of the WHO – cut off time” is
equal or before the current time (see chapter 2.3, z-table cut-off time).
b) If the current time is earlier than the calculated cut-off time, the system skips the current WHO
for this order release run.
c) The system only releases WHOs of the product size category 06-mech-pallet in case all car-
tons from the OSR with the same target pallet have the pick status “Re-stored in OSR” in the
O*CAR table, see chapter 2.3
d) For full cases (check: packaging material) from the storage type OSR the system needs to
check the utilization at the full case pick robot (workstation group)
1. The WHO is skipped if the maximum number of cartons at the workstation group is
reached (see the z-table for maximal values and factors in chapter 2.3).
e) The system checks if full case picking robot has still capacity left and no ODOs could be
released. If this is the case, the system checks for IMST documents (WMR category, type
SREA or ZSCR) which WHOs have next LSD and releases the WHOs until capacity is
reached.

23/04/2023 844573593.docx 4/17

 www.KNAPP.com

1. The system only releases WHOs, were the carton status in table ZTLGT_O_CAR is
“3 PM calc. completed”. If this is not the case the system writes an info log, that the
WHO could not been released due to missing Packmaster calculation.
2. The system logs in SLG1 / alert monitor, if no capacity for IMST documents was
available.
f) For all cartons coming from the OSR with VAS relevance (check: delivery item for VAS code)
the system needs to check the capacity utilization at the VAS station (workstation group)
1. The WHO is skipped if the maximum number of cartons at the workstation group is
reached (see the z-table for maximal values and factors in chapter 2.3).
g) For pallets coming from the HBW the system needs to check the capacity utilization of the
conveyor.
1. The WHO is skipped if the maximum number of cartons at the workstation group is
reached (see the z-table for maximal values and factors in chapter 2.3).
h) System skips the current WHO for this order release run, if the status for label-picking into
pouch for the cartons from storage type OSR and HBW is not set.
i) Status of the WHO will be set to “ ” for open in case the WHO isn´t relevant for automatic
cello wrapping (see chapter 3 / US 2).
j) The system only releases WHOs for all product size categories (incl. Oversized products with
product size category 8) in case the Packmaster planning status is set to “planned”.
k) The system only releases WHOs for all product size categories (incl. Oversized products with
product size category 8) if the stock of the ODO is fully allocated (see chapter 2.3).
l) The system only considers WHOs (incl. Oversized products with product size category 8) with
the status “blocked” in case of a re-calculation for the Order Release.
m) The system releases VAS relevant WHOs for one VAS carrier (same target pallet SSCC,
same product / batch, same PDO) at once independent of the capacity (e.g. capacity for 5
WHOs, but 6 WHOs for same VAS carrier à release all 6 WHOs as they will be picked onto
the same VAS Carrier).
n) The system must exclude PICK WHOs for a source HU with an open inventory HU WT (MFS
WT, warehouse process type 3094).

2.2 Mockups / Use Cases / Processes

Workstation structure in the VAS area

23/04/2023 844573593.docx 5/17

 www.KNAPP.com

2.3 Additional information

The following formula will be used in order to calculate the capacity:
ACTHUstation X + (PLANNEDHUstation X * FACTOR) <= MAXHUstation X
The following table should explain what each value in the formula stands for depending on the stor-
age type:
Storage ACTHU PLANNEDHU FACTOR MAXHU
type
OSR full currently occupied stor- sum of sent transport Fixed value from Fixed
cases age bins at the full case orders to full case pick z-table value from
robots robot z-table
OSR loose sum of the cartons sum of all cartons Fixed value from Fixed
picks (WHO), which are cur- (WHO) which are on z-table value from
rently located at the VAS- the way to the VAS z-table
station (workstation station
group))
Capacity for the first activ-
ity should be considered.
HBW sum of pallets (WHO) sum of pallets (WHO) Fixed value from Fixed
which are currently lo- which are on the way z-table value from
cated at the pick-station to the pick station z-table
group

This table describes the defined cut-off time per storage type (for example ZTLGT_CUTOFFTIME).
This information will be visible in the standard transaction SPRO and will look like this e.g.

The Cuf-off time will be maintained in hours before planned goods issue and there is no differentiation
between loose picks and case picks. For this calculation no weekends and public holiday will be con-
sidered, therefore the right factory calender in SAP EWM must chosen, this is in the responsibility of
ELC.
The values of PLANNEDHU, ACTHU are counter for each station, these values will change depend-
ing on the quantity of HUs per station. However, MAXHU and FACTORHU are fixed values, which
can differ depending on the station and will be set manually in the system, for testing dummy values
will be used, the final value for this parameter will be set during onsite testing in by KNAPP and ELC
and can be adjusted by ELC after the go-live.
All workstations / robots will be treated as workstation groups. Per workstation group a max. capacity
will be maintained. The work center group is based on the following table: ZTLGT_ WCGROUPS (see
document: C903A_4007_A_Printing transaction_V2.

The following table shows how the information regarding MAXHU and FACTORHU could be stored in
as two new columns in ZTLGT_WCGROUPS. table:
23/04/2023 844573593.docx 6/17
 www.KNAPP.com

The following information will be used in order to identify if Cello Wrapping is required or not for a
dedicated VAS Code.

Check if carton is coming from OSR

Check product master putaway control indicator (PACI) for OSR. Value is also maintained in
warehouse default table:

VAS workstation group

VAS workstation group needs to be added in ZTLGT_WCGROUPS and ZTLGT_WC_GROUPS (New

domain fix value for VAS group).

How to know if pouch picking is ready:

How to check if WHO has pouch and pouch is ready:

Select from ZTLGT_VAS_HU_AUX using WH = HU = SSCC HU for WHO + AUX category = P1or
PRT1 –

If records are not found means WHO has no pouch dependency for release

If records are found it means HU has pouch(s) and further pouch readiness check is needed

From the records selected get unique POUCH numbers in Field POUCH.

If no pouch number is found then WHO is not ready for release as pouch creation has not started.

If pouch numbers are found Then for these pouches check if all have pick status = C and Mailbox
assignment status = A Actual by selecting from ZTLGT_LMS_POUCH where WH = WH, HU = SSCC
HU number + Pouch = Pouch number read. Pick Status will be in KOSTK and mail box assignment
status will be in MBAST

If all pouches are picked and are in mail box then only WHO can be considered for release.

Sequence VAS-Code

23/04/2023 844573593.docx 7/17

 www.KNAPP.com

Assignment VAS-Codes to Workstation-Groups (n:n)

WHOs sorted by LSD

After calculation the release time the WHOs are sorted by the LSD, by this it can be ensured that
WHOs which have a longer throughput time are started earlier.

Only release 06-mech-to-pallet when all OSR cartons restored

WHOs for the non-mech-picking station with product size category 06-mech-to-pallet should only be
released if all the WHOs (cartons) from the OSR, which need to be packed onto the same target pal -
let (at the manual palletizing station) as the cartons at the non-mech-picking station, are re-stored in
the OSR. This requirement is only valid for products with product size category 06 – mech-to-pallet
(product size category group 3-M2P-cartons in the O*CAR table).
- System needs to identify if the current WHO has product size category 06-mech-to-pallet.
- System needs to identify the assigned target pallet to the current WHO based on the SSCC-Code
in the O*PAL and O*CAR table
- System needs to check for cartons which are belonging to the same target pallet, with the product
size category group “4-OSR cartons” in the O*Car table. If the system identifies relevant cartons
the order release at the non-mech-station needs to wait until all of these cartons are re-stored in
the OSR (check for pick-status in O*CAR  “Restored in OSR”).

Parameters for order release:

23/04/2023 844573593.docx 8/17

 www.KNAPP.com

Only release a fully allocated ODO

A check got implemented in order to only release a WHO if the stock of the ODO got fully allocated,
this means as long as there is a partial quantity open all created WHOs for the delivery are not re-
leases

IMST documents
Doc type SREA and ZSCR will be added to the ZTLGT_WH_DFLT

3 Chapter 2: Order Release VAS Carrier

In this chapter it is described how the VAS Carrier (containing finished VAS cartons) will be retrieved
from the HBW with the order release program in order to repack the cartons onto the final target pal-
let, as well as the WT / WHO creation for the release.

3.1 Acceptance criteria

a. The system creates a new WT / WHO for pallets with the set z-field ZZ_VAS_COMPLETED
and pallet type P3 coming from the source bin “HBW-Infeed”, after the pallet was confirmed to
the destination bin in the HBW. WT / WHO gets created with process type 4030 and ware-
house order creation rule VCRR, destination for of the WT is the non-mech-picking station.
b. System deletes the flag ZZ_VAS_COMPLETED after the WHO for the transport to the non-
mech-picking station was created.

23/04/2023 844573593.docx 9/17

 www.KNAPP.com

c. System checks if the next WHO has warehouse process type 4030 (warehouse order cre-
ation rule VCRR), if this is the case the system needs to check the product size category. In
case of product size category 07- non-mech-to pallet, the system needs to check the
ZZ_PSD / ZZ_PST date in order to know when the pallet is allowed to be retrieved (time for
palletizing). Pallet should be retrieved from the HBW in case the current time is equal or
already later than the ZZ_PSD / ZZ_PST.
d. System checks if the next WHO has warehouse process type 4030 (warehouse order cre-
ation rule VCRR), if this is the case the system needs to check the product size category. In
case of product size category 06- mech-to pallet, the system needs to check the ZZ_PSD /
ZZ_PST – defined Cut-Off time for palletizing in order to know when the pallet is allowed to
be retrieved. Pallet can be retrieved from the HBW in case the current time is equal or already
later than the ZZ_PSD / ZZ_PST – Cut-Off time.
e. The system checks if the target bin of the warehouse task is related to an active NMP station
(not in inventory mode), if this is not the case, the system updates the target bin to the one of
the active station (Independent of the PSC).
f. The system checks if the target bin of the warehouse task is related to the NMP station with
the most free capacity, if this is not the case, the system updates the target bin to the one of
the station with more available capacity(Independent of the PSC).
g. The system updates the target bin of the warehouse task to the same station as for the other
VAS Carriers, which need to be removed for the same target pallet SSCC only for product
size category 06- mech-to pallet.

3.2 Execution flows

No execution flow is needed.

3.3 Mockups / Use Cases / Processes

No Mock-ups are needed.

3.4 Additional information

Retrieval of VAS Carrier:
At the non-mech-picking-station the user picks products with VAS relevance onto the VAS Carrier,
this VAS Carrier will then be transported to the VAS area. After all VAS activities are finished (flag
ZZ_VAS_COMPLETED will be set on the HU header) the VAS Carrier will be re-stored in the HBW
until time for palletizing has been reached. After transporting pallet back to HBW a WT / WHO for the
retrieval of the VAS Carrier will be created automatically.
In order to now finally pick / repack the products onto the final target pallet the VAS Carrier needs to
be retrieved in time from the HBW with the order release logic.

4 Chapter 3: Order Release AUX Carrier

In this chapter it is described how the AUX Carrier will be retrieved from the HBW with the order re-
lease program in order to bring the aux materials to the workstation, where it was requested.

23/04/2023 844573593.docx 10/17

 www.KNAPP.com

4.1 Acceptance criteria

a. The system identifies locked WHOs with WOCR AUXP and warehouse process type 3095.
b. The system considers the capacity at the non-mech-pick station as described in the chapter
2.
c. The system release the identified locked WHOs automatically, as soon as capacity is avail-
able.

4.2 Execution flows

No execution flow is needed.

4.3 Mockups / Use Cases / Processes

No Mock-ups are needed.

4.4 Additional information

Retrieval of AUX Carrier:

WHOs are already created with the process auxiliary material replenishment, for further information
see DO: C903A_7008_A_Auxiliary material replenishment

At the non-mech-picking-station the user picks AUX products onto a target pallet or picks whole pal-
lets from the conveyor. The AUX Carrier will then be transported to the workstation where the Aux.
materials was requested.

5 Chapter 4: Cello Wrapping

Automatic cello wrapping is a VAS activity (VAS-Code L22), which will only be relevant for full cases
and products with VAS-Code for automated cello wrapping. As it is a fully automated process step, no
user interaction is required. In order to execute the automatic order release for cello wrapping it will
be scheduled as a background job. The logic for the automated order release for cello wrapping isn`t
relevant for picks at the non-mech-picking station (product size category: 06-mech-to-pallet & 07-non-
mech-to-pallet).

5.1 Acceptance criteria

a. System only considers WHOs for full case picks with cello wrapping relevance (check: VAS-
Code L22) and excludes product size category 06-mech-to-pallet & 07-non-mech-to-pallet.
b. System sets the flag for the manual cello wrapping relevance ZZ_MANUAL_CELLO on the
WHO header (/SCWM/WHO) in case a WHO for LP with VAS Code L22 (automated cello
wrapping) got identified.
c. The system identifies the not released WHO (status of WHO is “B” locked) with the earliest
Planned Palletizing Starting date and time (PST) on TU header.

23/04/2023 844573593.docx 11/17

 www.KNAPP.com

d. The system only considers not released WHOs (status of WHO is “B” locked), with PST equal
or smaller than earliest PST (planned palletizing start date) for WHO + defined time parame-
ter from z-table (see chapter 5.4)Additional information
e. If the latest starting date (LSD) of the WHO has already been reached the carton for this
WHO will be routed to the manual cello wrapping station (storage type 2061) (change of des-
tination location; flag will be set on the WHO for manual order release).
f. If the toolkit-number isn´t set for the PDS-Code (in a defined table or on the product master
data for non-batch managed products in a z-field) of the current WHO, the system writes an
entry in the alert monitor for this WHO (Message: Tool-kit-number is missing for WHO) and
the WHO will be routed to the manual cello wrapping station (change of destination location
flag will be set on the WHO for manual order release), see chapter 5.4.
g. The system checks if the quantity of all pieces per carton (case pack quantity from PDS-
Code) for all WHO with the same tool-kit number in the defined time window is equal or
higher than the defined threshold for the tool-kit (see chapter 5.4). The system transports all
cartons to the manual cello wrapping station in case the quantity is lower than the set thresh-
old (flag will be set on the WHO for manual order release).
h. System sets the status of all considered WHOs to “ “ – open.
i. The system continues the check form the beginning on.

5.2 Execution flows

Option 1:
1. System only considers WHOs for full case picks with cello wrapping relevance (VAS-Code
L22) and excludes product size category 06-mech-to-pallet & 07-non-mech-to-pallet. WHO
´s.
2. The system identifies the not released WHO (status of WHO is “B” locked) with the earliest
Planned Palletizing Starting date and time (PST) on TU header.
3. The system only considers not released WHOs (status of WHO is “B” locked), with PST
equal or smaller than earliest PST (planned palletizing start date) for WHO + defined time
parameter from a table.
4. The system checks if the latest starting time of the WHO has already been reached.
5. System identifies that LSD hasn´t been reached yet.
6. System checks if per PDS-Code a tool-kit number is set in the system
7. The system checks if the quantity of all pieces per carton (case pack quantity from PDS-
Code) for all WHOs in the defined time window for the same toolkit, is equal or higher than
the set threshold for the tool-kit.
8. System sets the status for all WHOs, which are relevant for this order release run to “ ” –
open.

Option 2:
1. System only considers WHOs for full case picks with cello wrapping relevance (check: VAS-
Code).
2. The system identifies the not released WHO (status of WHO is “B” locked) with the earliest
Planned Palletizing Starting date and time (PST) on TU header.

23/04/2023 844573593.docx 12/17

 www.KNAPP.com

3. System identifies that PST for WHO is bigger than the PST of the first WHO + parameter
from table.
4. System won´t release the WHO.

Option 3:
1. The system checks if the latest starting time of the WHO has already been reached
2. System identifies that the latest starting has already been reached
3. System won´t consider the WHO for automated cello wrapping and routes the carton the
manual cello wrapping.
4. A flag will be set on the WHO for manual cello wrapping

Option 4:
1. The system checks if per PDS-Code a tool-kit number is set in the system.
2. The system identifies that no entry is set for the tool-kit
3. System won´t considered the WHO for automatic cello wrapping and routes the carton to the
manual cello wrapping station and writes an error into the alert monitor.
4. A flag will be set on the WHO for manual cello wrapping

Option 5:
1. The system checks the quantity of all pieces per carton (case pack quantity from PDS-Code)
for all WHO in the defined time window for the same toolkit, is equal or higher than the set
threshold for the tool-kit in the system.
2. The system identifies that the quantity is smaller than the threshold
3. System won´t consider the WHO for automated cello wrapping and routes the carton to the
manual cello wrapping station.
4. A flag will be set on the WHO for manual cello wrapping

Option 6:
1. The system checks if further WHOs with the same toolkit number are in the time window of
earliest planned palletizing start date & time + parameter from ZTLGT_CW_TIME, see chap-
ter

23/04/2023 844573593.docx 13/17

 www.KNAPP.com

5.3 Mockups / Use Cases / Processes

23/04/2023 844573593.docx 14/17

 www.KNAPP.com

5.4 Additional information

The following information defines the additional time, until when WHO will be considered for Cello
Wrapping. This information will be accessible from SPRO:

The following information describes the table for the assignment of the toolkit number to the PDS-
Code. As the information of the toolkit-number won´t be transferred from ECC, this information must
be filled in the table while cutover.

The following table describes the threshold per toolkit-number.

In order to also treat non-batch managed products for cello wrapping a further z-field need to be im-
plemented on the product master data (e.g. ZZ_PDS_TK). In case no PDS Code is given the tool-kit
number can be assigned to the product via this field.

23/04/2023 844573593.docx 15/17

 www.KNAPP.com

Capacity management at the Cello Wrapping Area:

 All WHO with the same toolkit number within the next e.g. 3 hours should be released if
o the capacity at the work center group is greater than 0
o and the threshold of the toolkit number got reached
 This means only if there is no capacity at the workstation for cello wrapping, no WHO should
be released
 If the latest starting time (LSD) has been reached the WHO (cartons) should be transported
to the manual station for cello wrapping
 Cello Wrapping should always be the first activity for a carton, that will be executed.
o in case the activity of labelling (service code for labelling on the delivery item) need to
be done for a carton, this carton will be routed to first to the label picking / printing
area (storage type 2061), the labels will only be picked (put onto the tray) and then
the carton moves further to the cello wrapping station.
o The activity of applying the labels at the carton will be done later, after cello wrap-
ping.

6 Customizing
- Job must be customized, which triggers a report for calling the order release every XX min-
utes.
- Customizing of storage types
- Warehouse order creation rule for VAS Carrier  VCRR
- Warehouse process type for VAS Carrier  4030
- Warehouse order creation rule for VAS Carrier  AUXP
- Warehouse default table: VAS-Code for automated cello wrapping: L22

7 Architecture
A job is scheduled to execute the order release. The report ZLGTU6391_ORDER_RELEASE is exe-
cuted.
The class ZLGT6391CL_ORDER_RELEASE is responsible for the order selection and determination
and check of the order parameters.
The WHO handling is implemented in the class ZLGT6391CL_ORDER_RELEASE_WHO.

The determination of the first VAS activity of the WHO is required for most released and not released
orders. As this calculation is complex, it is executed only once at the WHO creation. The method
WHO_FIELD_UPDATE of the class /KNAPP/CL_CART_POHU_UPDATE is executed to determine
the value and save it on the WHO.
In case of cello wrapping it is not possible to influence the WTs after the picking, as those are not
created yet. Because of that the field ZZ_MANUAL_CELLO is added to the WHO to indicate that the
manual cello wrapping is required.

23/04/2023 844573593.docx 16/17

 www.KNAPP.com

8 Technical implementation

8.1 Entry point

A job is scheduled to execute the order release. The report ZLGTU6391_ORDER_RELEASE is
called.

8.2 Packages
ZL6391_ORDER_RELEASE Order Release

8.3 Implemented BAdI’s

8.4 Important classes / function modules

ZLGT6391CL_ORDER_RELEASE Order Release
ZLGT6391CL_ORDER_RELEASE_WHO Order Release WHO handling
ZLGT6391CL_ORDER_RELEASE_ALERT Class for order release alert monitoring

8.5 Database tables

ZTLGT_CUTOFFTIME Cut-off time per activity area

ZTLGT_VAS_SEQ VAS activity sequence
ZTLGT_VAS_WC Assigns the VAS-Codes to the work center groups
ZTLGT_PDS_TK PDS-Code Toolkit-number assignment
ZTLGT_TK_TH Threshold in EA for Toolkit-number
ZTLGT_ORDER_REL Order release customizing

8.6 Checkpoint groups

8.7 Others
Message class:
ZL00_ORDER_RELEASE

Function Group:
ZLGT6391_ORDER_RELEASE

Function module:
Z_LGT6391_SET_OREL_STATUS_DLV Set Order Release Status on Delivery

23/04/2023 844573593.docx 17/17