Outbound Process Flow

Creation of Sales Order (ECC)

Outbound Delivery Creation (ECC)

OD Replication in EWM through QRFC

There are certain custom fields which also gets updated in the ODO which are as below.
ZZ_RESERVATION - Reservation of specific inventory on Sales Orders and STOs. Will be used while
allocation.

ZZ_FRESHNESS - Minimum Freshness in days

ZADJ_ARRIVAL_DT - Adjusted arrival date. ECC will calculate and pass adjusted arrival date which
represents date when goods are expected to arrive at customer place.

BONDED_PICK_RULE
ZADJ_PGI_DATE - Suggested Ship Date. Indicate when delivery need to ship from DC.

ZREV_REC_DT - Revenue recognition date.

Used at month end to prioritize deliveries that will give revenue current month.

ZZ_NETWR - Sales value

ZZ_WEARK - Sales value currency

ZZ_VAS_REL- VAS relevance indicator. Helps to identify which deliveries having VAS activity

Z_PKINS – Packaging Instruction number is a 3 Digit code in ODO that indicates the below

 Pallet type
 Packing type
 Pallet length in cm
 Pallet with in cm
 Max height in KG
 Special packing instructions

ZZ_PALLET_STRING Information used to determine which delivery lines (cartons) can be put on same
pallet. The criteria for the palletization string are identical to the cubing criteria (except for VAS)
 Division and grouping of division
 Event materials
 Product family and grouping of the product family (based on product hierarchies)
 Customer PO reference

ZZ_CUBING_STRING This string will be used to define which products can be packed together in one
carton. Cubing family string, delivery lines with same cubing string are allowed to be packed in same
carton

ZZ_DLVRYGRPSTRING Information will be used to group deliveries (header) together, which should
be shipped together in one shipment
ZZ_SHBLK Create dispatch block in SAP EWM to prevent loading. Block is removed manually. This is
relevant for customers which that need further investigation or Legal documentation

ZZ_HAZD Hazmat Documentation. The correct hazmat labelling (OCEAN vs AIR) needs to be triggered
by this field and cannot be derived from Shipping condition as per sample explained in comments

TU Assignment
TU Assignment is Done automatically based on the following conditions.

Delivery grouping string

Ship-to

Shipping condition

Dispatch Date at which the shipment should be ready for dispatch.

In case the relevant data is not available for TU mapping then a TU will be created & assigned to this
Delivery.
PPF Actions

Now the standard PPF action for creating warehouse tasks (WHT) will start. The creation of WHT triggers
the Cartonization Process.

Stock Allocation & Cartonization happens automatically through the Batch Job.

We can also check the Log of this Delivery in SLG1 by entering the OBD number of EWM.
Stock Allocation starts after the assignment of TU to OBD

Stock Allocation checks 2 things.

Storage type will be identified by using the standard SAP EWM function with a stock removal indicator

Secondly the quantity will be split based on different packaging units.

As a result of the stock allocation a WT will be created

System checks stock removal control indicator in the product master data & the quantity from PDS
codes

FRICE ID for Stock Allocation-: 6341

One Warehouse Order(Status Blocked) is created for the OBD with 4 Warehouse Task with Activity Area 0033 which is Loose
Pick.

0030 -: Full Case Pick

0021-: High Bay Pick

Warehouse Task doesn’t have any Carton here as it is updated later.

After the Stock Allocation is done then the Cartonization Process starts.

The goal of this process is to plan how many HUs are needed, which packaging material the HUs should have as well as which
materials will be packed into them in order to optimize the packing. Based on specific criteria the packing of the materials into
specific HUs is planned. The result of the Cartonization are Planned Shipping HUs (PSHU), which do have a reference to the
outbound delivery order they were created for.
Tables Updated

ZTLGT_O_CAR with status 1 is created which is Initial

Tables

ZTLGT_DEFAULT_PM

After the Cartonization is done then the Packmaster Calculation starts.

Packmaster has got an Interface with EWM.

After Cartonization is finished, all cartons from one TU are sent through Interface to the Packmaster.
Packmaster then takes all the cartons & puts it into a Pallet.

So this gets all the cartons we have, what Product it is How Big the cartons are going to be, How heavy
the cartons are going to be, and then send it to the packmaster for calculating how many Target Pallets
you need, on which orders the cartons should go on to the pallet, and what access points robot is going
to use the keep the cartons on the pallet
Incase the PM Planning Date has not reached then below will be the error.

In case if the timing needs to be changed then it can be done by the following Transaction
Now Run the packmaster again .

So this gets all the cartons we have, what Product it is How Big the cartons are going to be, How heavy
the cartons are going to be, and then send it to the packmaster for calculating how many Target Pallets
you need, on which orders the cartons should go on to the pallet, and what access points robot is going
to use the keep the cartons on the pallet

Program to send the Telegram out to the Packmaster

Before Packmaster calculation starts ZTLGT_O_CAR Table

Before PM calculation starts ZTLGT_O_PAL Table status.

PM Planning Status & Order Release Status

After Packmaster Queue is executed

Now check the SLG1 Log for Packmaster Outbound Data creation

Telegram
Telegram Direction 1 is for sending out the Packmaster Data & 2 is for the one that we get from PM.

XML log sent to the Packmaster. These are the information sent to the Packmaster & based on this the
Packmaster calculates the number of Pallets required

XML Log received from the Packmaster.

If Packmaster sends any error then the error is shown in the Error ID in the Telegram. 0 is good. If it is 2
then mostly the error is due to product Master data like carton was bigger than pallet so PM could not
load it into pallet.

In case there is any issue with the Packmaster then the same can executed manually in EWM itself but
this is only applicable for manual palletization.
Now after the Packmaster calculation has been completed the O Car Table is updated with new status

Also the O PAL Table gets populated now with SSCC Pallet number

We can also check the status of O Pal, O Car, Pick status & PM Sequence after Palletization in Monitor as
well by typing the TU Number

Robot can only pack in the sequence shown in this calculation

At this stage neither the Pallet number is known nor the Carton number.

Only after the Order release the carton number that will come from OSR will be known & when empty
pallet request will be done we get to know the Pallet number.

Order Release

Now the Order release will start.

System will check for the warehouse orders that can be released.

0030- OSR Full Pick

0033- OSR Loose Pick

0021- High Bay

2020- Oversized

If a Warehouse order doesn’t have a O Car entry then it will not be released.

Once we receive the data from Packmaster the below 2 fields gets updated
Planned GI date is the Date when we want the product to go out of DC & accordingly start Picking or
start Palletizing

Planned Palletizing Start Date

Now run the custom Program for Order Release. In Production this happens through the Batch Job. This
searches for Warehouse orders that can be release
Now we can check the status of Warehouse Order from Blocked to Open

Also here one Higher level warehouse order is created so this consolidates all the warehouse orders
assigned against this & send them as One Telegram to the OSR. And this happens only for Full case.

Order Release Log

Now check the OSR Telegram.
Pick Order Sent to OSR & OSR will check the condition

Pick Order XML

Pick Order Married(Incoming Telegram from SRC. Here we get the container number which is the Tray
having the HU CHG number married to the WH Order number). Here the owner of the Tray is EWM so
SRC cannot make any plan for this Tray. Also the CHG number is proposed by SRC here

Next Telegram is for Order Update when Picking started

Pick Order Finished

Once the Pick Order is finished we sent a Transport Order for the Tray & then Tray moves out of the OSR

In case of Loose Pick the Picking happens in the Loose Pick Area which is controlled by SRC.

In the above we are sending the Container Base size which is C6

SRC then request the Container Type from EWM as you can see from the above screen

SRC then marries the Container Type with Container number starting with 7 series which is a dummy HU
number

As you can see in the above screenshot, here the carton gets created. (S,M,L) when the request is sent by SRC. In the labelling
area this carton gets labelled with this 7 series number. When the carton gets labelled that’s when it is married. And this
updates the O Car Table with the Routing label number.
Now the process of Carton request is finished.

Then it goes like normal Full case pick request where the Pick order is married. SRC is marrying the
Warehouse order number starting with 3 with the container number starting with 7 as shown in the
above screenshot

Now in order update the CHG number will be the source carton from which the materials will be picked
& put into the Destination HU which is the 7 series number.

To check the Pick Warehouse order in WH, select the Warehouse Order creation rule as PICK & WO
Activity Area should be 0033 for Loose Pick. For Full Pick it should be 0030 & for High Bay 0021.
For completed ones WO Status should be C, For cancelled ones it should be A & for Blocked ones should
be B

One Pick WH order is one carton.

OSR Connection Status is as below

OSR Queue

From below Table system will check if the small carton is available or not, if not then it will go for
medium, if not medium then it will go for Large carton.

In the below Table 0 means Available, 1 is not available

Picking Process

Picking of OSR products without VAS

In case of executing this process in the warehouse in case of loose picks the SRC GUI at the
G2P picking station is executed.

After the picking, Non VAS-relevant full cases will be transported to the labelling area and Non VAS-
relevant loose picks to the carton closing area. After the loose picks are closed, they will also be
transported to the labelling area. And the HU number will change to a Top Label number, which will be
captured in the z-table “ZTLGT_O_CAR”.

Depending on the size of the picked carton, it will either go through the automated labelling street or to
the manual labelling station. In order to execute the manual labelling process, the following steps need
to be executed.

Transaction ZLRGT635800

Scan the carton HU number and click on “Print”. To finish the process, click on “Con-firm &
Finish”.

As soon as the labelling is done, the carton will be packed onto a tray and transported back to the OSR
for restoring.
Picking of OSR products with VAS

After the picking, VAS-relevant cartons will be transported to the VAS area. This is valid for both, full
cases and loose picks

Transaction ZLRGT640900 to execute the VAS Process

Secondly, scan the HU number (carton) and click on “Start. And as soon as VAS activities are completed
click on Stop & push the carton/tray back to the loop.

After all VAS activities were executed, full cases will be transported to the labelling area and loose picks
to the carton closing area.
Picking of Mech To Pallet Products without VAS

Mech-to pallet full cases and loose picks will always be picked onto the conveyor.

Cartons which are relevant for VAS will be picked into a VAS carrier.

All labels for these products / cartons must be directly applied at the pick-station.

Trigger for the print of the label will happen during the picking screen on the GUI-screen.

The carton will be weight by an integrated scale directly on the conveyor and the weight label will be
applied directly on the conveyor.

Transaction ZLRGT635700

Secondly, choose the picking mode

Then scan the source HU (= pallet) and click on enter

A. LOOSE PICK scenario

In case there is a HU with packaging material “LOOSEPICK” stored on the source pallet, the system will
display the HU number in the field “source carton”. In case there is no HU with packaging material
“LOOSEPICK” available, this field will be empty, and the user needs to choose one HU, which will then be
turned into a “LOOSEPICK” by changing the packaging material in background.

Scan the Source Carton

Enter HU number for target carton which is created newly by applying the Top Label

Enter picked quantity

Click on “Confirm Pick” label printing screen is shown

Click on “Print Labels”

Check the printed labels in transaction SP01

Click on Print Packaging List

Check the printed label in transaction SP01

Click on “Finish”

Check the confirmed warehouse tasks in transaction /SCWM/MON

FULL CASE scenario

Scan source carton (destination is defined as “CONVEYOR” because of M2P)

Click on “Confirm Pick” -> label printing screen is shown

Click on “Print Labels”
Check the printed labels in transaction SP01

Picking screen for next Warehouse Task. (Source carton & Target Carton same in this case)

If no open Pick WHT from this source pallet this HU needs to be brought back to HBW for
storing or non mech loop in case further pick needs to be executed from this pallet.

O_CAR Table status with Status Pick as 2

Picking of M2P products with VAS

The picking of M2P products from the highbay warehouse will be done with the help of an SAP GUI transaction.
Access transaction ZLRGT635700 and execute the picking process

a. LOOSE PICK scenario

The following steps need to be executed in this scenario:
Scan source carton (Destination in this case is “VASCARRIER)

Enter HU number for target carton (make sure the HU number is not yet existing in the system)
Enter picked quantity & Confirm

b. Full Case Scenario

Scan source carton & Click on Confirm Pick

Move HU to VAS Area. Once the HU is placed in VAS area execute Transaction ZLRGT640900 to perform all
the VAS activities. Once the VAS activities are completed same set of process for picking as explained in the top

Picking of NM2P products without VAS

As soon as a source pallet got scanned, Based on the product size category of the products on the scanned pallet it
will be identified by the system which type of pick it is. In case of Loose Pick the Full case field will be empty in
warehouse order.

System assigns the target pallet to a workstation in the z-table ZTLGT_ACT_PAL

The system reads out the product size category 7-Non-mech-to-pallet and shows “Pallet” in the destination field
Transaction ZLRGT635700

LOOSE PICK scenario

In case no loose pick carton then Source carton field remains empty. And he can take any full
case carton, scan it & and an automated repacking into a loose pick carton will be execute.
Packaging material will be changed from 0002 to Z005
Same as M2P case except here the destination is Pallet.

Enter weight of HU and click on “Print Weight label

FULL CASE scenario

Same as Mech To Pallet except the print of weight label.
Scan the Source carton & click on Confirm Pick

Enter weight of HU & Click on Print Weigh Label & check the Confirmed WH Task in Monitor

Check the O CAR Table.

STATUS_CAR set to “5 (palletizing completed)

STATUS_PICK set to “2 (picked)

Entries in z-table “ZTLGT_O_PAL” will be status 5 (Palletizing Completed)

Picking of NM2P products with VAS

Access transaction ZLRGT635700 and execute the picking process

Loose Pick
Enter the warehouse number and the work center and click on execute. Choose the picking mode and
scan the source HU & then confirm Pick.

Enter Weight of HU & Click on Print Weight Label.

Click on Finish

FULL CASE scenario

Scan source carton (Note: the system will provide a list of cartons placed on the VAS Carrier;
the destination is defined as “PALLET”)
Click on “Confirm Pick” label printing screen is shown
i Click on “Print Labels”
ii Click on “Finish” Weight label screen is shown
iii Enter weight of HU and click on “Print Weight label
iv Click on Finish
v Release the Source & Target HU

ZTLGT_O_CAR Table

Top label gets updated with HU number of Picked carton

STATUS_CAR set to “5 (palletizing completed)”
STATUS_PICK set to “2 (picked)

ZTLGT_O_PAL

STATUS_PAL needs to be set to “5 (palletizing completed)

Non Mech to Pallet Picking can be seen from the below screen in WH monitor

Picking of oversized products

The picking of oversized products from the oversized area will be done with the help of a RF-workflow
by Queue that is set in the system

TCode /SCWM/RFUI
Verify proposed source bin

Verify proposed source HU (pallet)

Enter HU (carton), which is placed on the pallet (check in transaction /SCWM/MON)

Enter target HU either enter source HU if only one carton is on the source HU and the packaging material is correct or enter new HU
number, which is not yet existing in the system

Verify proposed target bin

Entries in ZTLGT_O_CAR Table is as follows

Entries in ZTLGT_O_PAL is as follows where it shows Status 5 (Palletizing completed)

Restoration in M2P Buffer

After the M2P cartons were picked, they will be buffered in the “M2P buffer”. The cartons will be
automatically transported to the buffer area once they are put on the case conveyor after
picking.
Carton Closing
Carton closing is done after packaging list, wedging then carton closing & finally Top Labelling is done and put into
the carton. The carton needs to be closed for shipping.
Done after labelling but before the Top Label applicator
Packaging list is created at labelling station, once it is printed then it is put into the open carton. After all print outs are
put into the carton then it goes for the carton closing.
After the Top Label applicator the Top Label of carton marries with the Routing Label. So when the scanner scans,
SAP EWM receives a telegram with corresponding HU number. And based on that information system creates a new
HU number of Top Label & same packaging material as HU with number of Routing label repacks the stock into
newly created & captures the number of Top Label in O Car table.

Routing to Labelling Station

In order to determine if the carton needs to be diverted to the manual labelling station or automated labelling street, the
system needs to check the height and length of the carton. So the conveyor scans the HU number after the carton closing area
and once after the full case picking sends the HU number to SAP EWM via a telegram. The system determines the dimensions of
the carton and decides where to transport the carton.

System will provide a function module for MFS to be called. The function module will read the HU
information and determines if the HU flagged for ‘no_labelling’. If label should be applied, the system
determines the HU dimensions and creates an open warehouse task to fitting station, manual station if
within defined measurements or to automated labelling street. In case the HU is flagged for ‘no_label’,
the FM creates a warehouse task for OSR putaway. The additional exporting flags are support
parameters for testing and further handling.
Box size is not matching or beyond dimensions then it goes to Manual labelling station.

Stream_type handling will be part of MFS/OSR implementations

Required storage types:
 3030 (manual labelling station)
  3020 (automated labelling street)
Automated Labelling Logic
 After the system decides that the carton needs to go to the automated labelling street, it creates
a warehouse task for the movement & the conveyor transports the carton there. At the
beginning of the labelling street as well as before every printer / applicator there is another
scanner, which sends the HU number to SAP EWM via a telegram. The system checks if the
corresponding label, additionally to some standard labels, is required based on the z-field for the
HAZMAT-indicator on the header of the corresponding ODO. In case the document needs to be
created before printing, the system triggers that creation via the interface to KNAPP PCS. In case
the document is already on a pre-printed role and will only get applicated, MFS triggers this
application as a next step.
 After all labels are printed and/or applied, the carton will be packed onto a tray and transported
to the OSR for buffering until palletizing starts.
 If an error occurred somewhere while printing and/or applicating, the conveyor transports the
carton to the manual labelling station.

Telegrams for Loose Picking

PICK_ORDER
CONTAINER_REQUEST

CONTAINER_REQUEST_MARRIED

CONTAINER_REQUEST_FINISHED

PICK_ORDER_MARRIED

Order Update
Order Finished

Tray Unloading by Ansorix Robot during Picking.

At this station full cases will be picked from the tray onto the conveyor. In case the carton is the last one
on the tray and is VAS relevant, it will be directly diverted to the corresponding area without going
through the robot. In case the carton is not the last one on the tray but is VAS relevant, it will be
diverted to the corresponding area after it was picked from the tray to the conveyor. The system will
confirm the corresponding PICK-WTs and execute all relevant status updates
The technical interface to the full case picking robot is based on a TCP/IP XML connection.

Robot Interface Log

Pick Order
Pick Order Carton Confirm

PickOrderTrayConfirm

As per the rule if there is only one Tray in the Carton then it can go directly to VAS if it is VAS
activated. No picking is needed.
But if it has got more than one tray then it needs to go to Robert for Tray Unloading.

There are 3 Jobs that are planned.

One for Tray Loading, One for Palletizing & 3rd one for Tray Unloading.
These are running the whole time & sending Telegrams if they find something in the queue.
Queue for Outbound Telegram

Below are the Outbound Orders sent from EWM

SPRO Settings for Tray Unloading Robot. Waits 30 seconds for Answer. Tries 3 times before an
Answer

In case there is any error then we can find it like this.

Tray Unloader Robot Log

After the Tray Unloading is completed then it goes through the various Labelling & finally gets loaded on to a Tray &
goes to the OSR.

Palletizing Process

When Trays are back in OSR, they have been picked, they have been labelled & they have been stored
Then jobs runs to create entry in the palletizing pool

Palletizing Pool is a custom made queue for all the robots for the Palletizing of Cartons.

4 Manual & 6 Automated Station for Palletizing

Prerequisite to start the Palletizing Process.(Status should be Packmaster calculation completed & Picking status
should be 4 which is OSR Restoration done)

The palletizing starting time will be calculated backwards from the PGI date, the time for carton retrieval, palletizing
and pallet finishing will be subtracted.
Second is in case if anything changes the PM does the calculation again & then the next precondition is Planned
Palletizing Start Date & Time & also GI Date.

First the Pallet needs to be assigned a Work center for which the Job runs for determining pallet for palletizing pool.
Entry gets created in Z table ZTLGT_PAL_POOL

Pallet SSCC; sequencing, TU, when gets assigned, what pallet we need, how many palletized, how many carton etc.
Currently nothing is happening
Now the empty pallets need to be requested from the De-stacker or the manual pallet infeed as
well as the restored cartons from the buffer zones (OSR or M2P buffer).
Entries in z-table “ZTLGT_PAL_POOL as below

PAL_REQ_STATUS is set to R
CAR_REQ_STATUS is set to R

New entry is updated in Table for Empty Pallet Request when executed.
Now the System creates the Warehouse order for empty pallets. Job is scheduled for
creating the same through Program ZLGTU6380_CREATE_WT_EMPTY_PAL.

Status of Z Table ZTLGT_O_PAL is as follows.

Subsequently the entries in Empty request Z Table ZTLGT_EMPTY_REQ gets deleted.

Status 5 below means the cartons are on the Pallet. Also the cartons go on sequences
mentioned below.
If sequence goes wrong, pallet goes to manual palletization & cartons to OSR. From there they
go to Manual Palletizing.
Fastbox is mini OSR & it is a buffer used for sequencing.
Warehouse Task for carrying the tray from OSR to FastBox is as below.

The warehouse Task for the Automatic Palletizing is as below.

Telegram for the Automatic Palletizing is as below.

Telegram from the Robot.

Robert sending to EWM the request to bring the pallet 220000207724

Then EWM is sending the information what Trays are coming in what cartons
The information like length height weight sequence comes from Packmaster like which carton
will be on top bottom.

At this point we create the Transport from Fast Box to the Robot
Then we get the confirmation from Robot on the confirmation on the Trays that have got the
carton.
Once all the confirmation is received from the Robot on all the Trays the Order Pallet
confirmation is sent from the Robot.
As soon as all the Cartons are Palletized the Status changes to 5 in O Car status & Pallet gets
removed from the Palletizing Pool.
Manual Palletizing

Transaction ZLRGT640300

Click on “Start Palletizing” and the system will automatically load the HU number of the
pallet based on the z-table ZTLGT_ACT_PAL_WC as well as the place, where the next related
carton needs to be picked from based on the storage bin of the corresponding HUs.
Enter the HU Number & Enter

Repeat this process until there is no carton to be packed in the pallet.

Click on Stop Palletizing now.

You can check the entries in OCar & OPal Table

In the Manual Palletizing Area the Mech to pallet cartons & OSR cartons get palletized
Mech To Pallet & NMP Finishing

Transaction ZLRGT640200

Click on “Print Labels” & then Click on Confirm & Finish after Print is done

Print Lables can be checked below through SP01

Click on Refresh to load the next Pallet number which is assigned to the workstation

Now check the Monitor to check the warehouse task for movement either to HBW or to the
Dispatch lane if the assignment is done.

Oversized pallets
The oversized pallets, which were picked in the oversized area, need to be brought manually to
the overpack station and will be finished with the help of an SAP GUI transaction

Access transaction ZLRGT640200

The cartons placed on the oversized pallets need to be finished. Therefor enter the HU
number of the carton and confirm the entered value with ENTER, click on “Print Labels” and
after the printing was executed (success message is shown) click on “Con-firm & Finish”

Now click on Print Labels.

These Printed lables can be checked in SP01

Now in order to finish the Pallet, enter the Pallet HU number

And then it comes to the Oversize area for finishing & finally kept in the Staging area.

Restore in HBW

After the pallets were finished and no DL is assigned yet, they will be restored in the HBW.

The pallets will be automatically transported to the HBW storage.

Creation of Vehicle

Before the Vehicle is created the Dispatch Date & Time needs to be updated

Vehicle is created in transaction /SCWM/VEH. Enter the details of the vehicle & Carrier & other
details as mentioned below.
Also enter the Door to which this Vehicle will be assigned.
Next assign this Vehicle to the TU.
This is what it will look like after the assignment of TU.

Now the vehicle needs to be set to Arrival at checkpoint to set the vehicle Active & to be Docked
at the Door
Table to check the Docking Status

Assignment of dispatch lanes

In the monitor Outbound –> Documents –> Shipping Overview –> Loading dock door –>
Transport Unit Header Outbound.
Select the required TU and click on “Assign Dispatch lane”

Enter the Dispatch Lane. You can enter a maximum upto 3 Dispatch Lanes

Now check if the assignment have been done properly for the Dispatch lane.
Goods Issue Posting

Once all the above steps are completed, the GI Posting for all pallets will start for the
corresponding TUs.
Goods Issue Posting Job will run in the background with the Program
ZLGT6397_GOODS_ISSUE_TU.

Status of Transportation Unit

Status of Outbound Delivery

Idoc Status after GI Posting in ECC

Pallet retrieval out of HBW

The pallets from the HBW will be retrieved automatically 30 min (customizable parameter) ahead of
loading time/date if, at least, one staging lane is assigned, and the assigned staging lane has capacity.

The start of the automatic retrieval will be based on a scheduled job. The job searches for TUs, which
have reached the dispatch time (- customizable parameter) and are assigned to a vehicle. Depending on
the assigned dispatch lanes, the system creates the warehouse orders for the pallets height group by
height group. The warehouse orders will be created blocked to avoid overruling of pallets from different
vehicles. The system will release the WHOs based on the capacity of the dispatch lanes and the buffer in
front of the lanes.
Loading

The loading of the truck are done using a custom RF transaction. When the user scans the door, the
system looks for the corresponding vehicle and TUs assigned to it. When loading, the user confirms the
loading of each pallet with scanning the door.
After loading all pallets to the vehicle, the user enters the seal number and the standard status of the
TUs is set to “Loading completed”.
The entries in z-table “ZTLGT_O_PAL” changes for Loaded Status to 4
Status of TU changes to Loading Completed
Thank You