Warehouse Task

PDF download from SAP Help Portal:
http://help.sap.com/saphelp_scm50/helpdata/en/82/858f41912aad5fe10000000a1550b0/content.htm
Created on July 15, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
© 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 9
Table of content
1 Warehouse Task
1.1 Product Warehouse Task
1.2 Handling Unit Warehouse Task
1.3 Identification Point
1.4 Pick Point
1.5 Creation of Warehouse Tasks for Warehouse Request
1.6 Determination of Priority for Inbound Deliveries
1.7 Ad Hoc Movement
1.8 Posting Change for Stocks
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 9
!--a11y-->
1 Warehouse Task
Definition
Document that uses Extended Warehouse Management ( EWM ) to execute goods movements. Logical or physical goods movements or even stock changes
can be the basis for a warehouse task. These include:
● Picks
● Putaways
● Internal goods movements
● Posting changes
● Goods receipt postings
● Goods issue postings
Use
You create the warehouse task either with reference to a warehouse request or without a reference document, for example for internal goods movements.
The following figure shows the different warehouse tasks for products and handling units (HUs):
Product Warehouse Tasks
Handling Unit Warehouse Tasks
You or the system use product warehouse tasks, for example, for deconsolidation and handling unit warehouse tasks, for example, for unloading.
You can identify the type of the warehouse task from the warehouse process type in the warehouse task. For more information about the simultaneous use of
product warehouse tasks and handling unit warehouse tasks, see Pick Point.
EWM also submits hazardous substance texts in the warehouse task.
When you confirm a warehouse task, you can also perform a physical inventory at the same time. Here, EWM can work with the low-stock physical inventory.




!--a11y-->
1.1 Product Warehouse Task
Definition
Document that helps Extended Warehouse Management ( EWM ) move products. A product warehouse task (product WT) can be based on physical goods
movements or changes in stock.
Use
The product WT contains all the information required to execute the physical transfer of products into the warehouse, out of the warehouse, or within the warehouse
from one storage bin to another storage bin.
When you confirm a product WT, you inform EWM what you have processed this product WT and that the goods have arrived at their destination. If the planned
quantity (target quantity) differs from the actual quantity of stock that is moved, a difference quantity exists. If you confirm a product WT with a difference, the
system automatically posts the difference quantity to a “difference interface”.
Once confirmed, the product WTs also have a documentation function, since they document movements in the warehouse.
Structure
A product WT contains all necessary information about a goods movement to be executed.
· What should be moved?
· Which quantity should be moved?
· From where (source storage bin) should the product be moved, and to where (destination storage bin)?
When you create a product WT, it consists of an item with the source storage bin and destination storage bin.
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 3 of 9
When you confirm a product WT, it consists of either an item with the source destination bin or destination storage bin, or it consists of more than one item in the
case of partial confirmations.
· For goods receipt postings, the product WT consists of an item that increases the stock.
· For goods issue postings, the product WT consists of an item that decreases the stock.
· For transfer postings, the product WT consists of two items. One item that decreases the stock, and one item that increases the stock.
· In the case of partial confirmations, EWM creates one item for each partial confirmation. You create partial confirmations, for example, when you partially pick
from a nested handling unit, or when you confirm different pick handling units.
A product WT reserves the quantities, so that these are no longer available for other product WTs.


!--a11y-->
1.2 Handling Unit Warehouse Task
Definition
Document that helps Extended Warehouse Management ( EWM ) to move handling units (HUs). A handling unit warehouse task (HU WT) is based on goods
movements.
Use
The HU WT contains all the information required to execute the physical transfer of HUs within the warehouse from one storage bin to another storage bin. As an
exception, you can also use the HU WT for the loading and unloading process.
When you confirm a HU WT, you inform EWM what you have processed this HU WT and that the goods have arrived at their destination. Once confirmed, the HU
WTs also have a documentation function, since they document movements in the warehouse.
Structure
An HU WT contains all necessary information about a goods movement to be executed.
· Which HU should be moved?
· From where (source storage bin) should the HU be moved, and to where (destination storage bin)?
The HU WT always consists of an item with the source destination bin and destination storage bin. It does not reserve any quantities.


!--a11y-->
1.3 Identification Point
Definition
Place in an automated warehouse at which you identify newly-arrived goods.
Use
In many warehouses, certain storage types (such as high rack storage areas) require identification points (ID points). In these warehouse types, you have to use
the ID point to execute the putaway of all handling units (HUs). In Extended Warehouse Management ( EWM ), the ID point is a physical place in a HU-managed
warehouse at which you identify goods receipts for further processing.
The following figure illustrates the transfer of products from the goods receiving zone to a high rack storage area using an ID point.

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 9
For example, if you have assigned the ID point storage type 0081 to the storage type 0080, and want to put away goods in the storage type 0080, then EWM
proposes the ID point storage type 0081.
Structure
The purpose of an Identification Point includes the following:
● Contour control
A contour check often occurs at an ID point to determine whether the HU was built correctly.
● Changing the mode of transport
A conveyor equipment change can occur at an ID point. For example, the HUs are loaded from a forklift onto a conveyor.
● To determine the final destination
EWM determines the destination storage bin in the final storage type at the ID point. Since EWM only assigns the destination storage bin after the HU
arrives at the ID point, EWM determines the location of the storage bin based on the most current information about the storage type's space availability.
Integration
● You define an ID point in EWM as the storage type “identification point“ in Customizing for EWM under Master Data ® Define Storage Types , by setting
the storage role Storage Type Is ID Point .
● You connect the ID point to the HU-managed storage type in which the putaways from the ID point are to occur:
a. In Customizing, choose Master Data ® Define Storage Types.
b. Select the storage type to which you want to assign the ID point.
c. Choose ID Point Active .
d. In Customizing for EWM, assign your IDpoint to a storage type, by choosing Cross-Process Settings ® Warehouse Task ® Define Layout-Oriented
Storage Control .
For more information about layout-oriented storage control, see Layout-Oriented Storage Control.
For more information about Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for Extended Warehouse
Management under Cross-Process Settings ® Warehouse Task ® Define Layout-Oriented Storage Control.


!--a11y-->
1.4 Pick Point
Definition
The pick point is the actual place in the warehouse at which you pick items for a partial stock pick from a handling unit (HU).
In an automated high rack storage area (HRSA), the pick point can be a certain point on the conveyor line along which you move the HUs for
picking. A pick point can also be a marked floor area to which you bring entire pallets for removal of products.
Use
If you cannot execute partial stock picks in a storage type, for example due to physical restrictions in a high rack storage area, you use pick points to pick partial
quantities or to repack.
The following graphic illustrates how a partial stock pick occurs using a pick point.
If you only want to pick a portion of the product quantity from the HU, you bring the HU to the HU-managed pick point to carry out the actual picking.
1. At the pick point, you pick the required product quantity from the HU and remove the required products to the goods issue zone.
2. After picking, you put away the HU with the remaining product quantity from the pick point back into the warehouse and confirm the HU warehouse task.
Return Transfer of HUs
You can putaway partial HUs back into the warehouse after picking at the pick point.
● You have determined a fixed storage type for the return transfer of HUs, because you have a special storage type for partial HUs, for example.
In the Implementation Guide (IMG) for Extended Warehouse Management ( EWM ), choose Master Data ® Work Center ® Define Work Center.
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 9
EWM determines a new storage bin in the storage type and creates a corresponding HU warehouse task with the destination storage bin.
● You putaway the partial HU back into the same storage type in which you previously removed it.
You do not determine a fixed storage type for the return transfer of HUs. EWM determines the storage type as well as the destination storage bin by using
putaway strategies.
Integration
● You define a pick-point in EWM as the “pick point“ storage type in Customizing for EWM, under Master Data ® Define Storage Type , by setting the
storage role Storage Type Is Pick Point .
● You link the pick point to the HU-managed storage type from which the stock removals to the pick point are to occur:
a. In Customizing for EWM , choose Master Data ® Define Storage Type.
b. Select the storage type to which you want to assign the pick point.
c. Specify Pick Point Active .
d. In Customizing for EWM , assign your pick point to a storage type, by choosing Cross-Process Settings ® Warehouse Task ® Define Layout-
Oriented Storage Control .
For more information about layout-oriented storage control, see Layout-Oriented Storage Control.
For more information about Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for Extended Warehouse
Management under Cross-Process Settings ® Warehouse Task ® Define Layout-Oriented Storage Control.
● You set your pick point as work center.
In Customizing for EWM, choose Master Data ® Work Center ® Define Work Center.


!--a11y-->
Creation of Warehouse Tasks for Warehouse Request
Use
Extended Warehouse Management (EWM) uses this function so that when you or EWM release a wave, EWM simultaneously creates warehouse tasks for stock
removal or internal stock movements. EWM creates warehouse orders pursuant to the warehouse tasks, to assemble work packages for the individual warehouse
workers.
Instead of this standard creation of warehouse tasks through wave release, you can also create a warehouse task as follows:
● Manually, with the user interface
● Automatically, by calling a Post Processing Framework action (PPF action)

Features
When EWM creates a warehouse task for a warehouse request, it uses putaway strategies to determine the storage bin, or stock removal strategies to determine
the stock.
For more information, see Storage Bin Determination for Putaway or Stock Determination.
Extract Time Determination
The extract time determination calculates the target time effort to execute a stock movement. EWM determines this time for each warehouse task. Warehouse order
creation adds up the extract time of the individual warehouse tasks for a warehouse order. Optionally, warehouse order creation supplements the extract time
determination with a setup time that is defined in the warehouse order creation rule. In addition, if resource management is used, a route time is determined based
on the resource used. The warehouse order includes the sum of these times. Based on this, EWM determines the latest start time of a warehouse order.
The parameters of extract time determination formulas for a warehouse task are dependent on the product, the quantity, the unit to be transported, and
geographical dependencies.
For more information about Customizing for extract time determination, see the Implementation Guide (IMG) for Supply Chain Management under Extended
Warehouse Management ® Cross-Process Settings ® Warehouse Task ® Define Extract Time Determination.

Activities
When EWM creates a warehouse task for a warehouse request, it simultaneously updates this warehouse request. EWM carries out this update by updating the
document flow. If the document flow update leads to a change in status, EWM updates this change in the warehouse request as well.
● By default, you or EWM create warehouse tasks by releasing a wave.
After a wave is generated, it can be released immediately, either automatically or manually depending on the release methods you have defined for the wave
or wave template.
For more information, see Processing of Waves.
● Instead of this standard creation of warehouse tasks through wave release, you can also create a warehouse task as follows:
○ If you want to create warehouse tasks manually using the user interface, on the SAP Easy Access screen, choose Extended Warehouse
Management ® Work Scheduling ® Create Warehouse Task for Warehouse Request and then the desired action (for example, Putaway for Inbound
Delivery ).
○ If you want to create warehouse tasks automatically by calling a PPF action, on the SAP Easy Access screen, choose Extended Warehouse
Management ® Print ® Display and Process PPF Actions .
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 6 of 9


!--a11y-->
Determination of Priority for Inbound Deliveries
Purpose
You use Extended Warehouse Management (EWM) priority points to achieve an optimal unloading sequence for several trucks at transportation unit level in the
yard. At the same time, EWM updates the inbound delivery until the Warehouse Activities Status is Completed .
Process
1. The ERP system receives an advanced shipping notification (ASN) and creates an inbound delivery.
2. The ERP system notifies SAP APO and EWM about this.
3. Based on the notification, the system executes the following:
a. SAP APO calculates the priority points at item level.
b. EWM creates an inbound delivery request.
EWM or you activate the inbound delivery request.
EWM creates an inbound delivery from the active inbound delivery request.
The priority points in the inbound delivery are initial (initial value is zero) until SAP APO sends the results of the calculation for an update.
4. SAP APO communicates the calculated priority points to the ERP system, which then communicates them to EWM .
5. EWM updates the priority points in the inbound delivery.
EWM saves the priority points for an inbound delivery at item level. EWM calls the Business Add-In (BAdI) /SCWM/EX_DLV_DET_LOAD to display the
inbound delivery. This BAdI calculates an aggregated priority at header level.
6. EWM aggregates the priority points at transportation unit level using the BAdI /SCWM/EX_SR_PRIOP. You can see this on the user interface for unloading.
You can start the report /SCWM/PRIOP_UPDREQ for the recalculation of priority points from the SAP Easy Access display, under Extended Warehouse
Management ® Delivery Processing ® Inbound Delivery ® Update Priority Points . EWM triggers an asynchronous request for the recalculation of
priority points in SAP APO via the ERP system. As with the first calculation (step 4), SAP APO sends the result of this recalculation to EWM via the
ERP system. EWM updates the priority points in the inbound delivery and aggregates the priority points at transportation unit level.
For more information, see the report documentation.
Results
SAP APO has calculated the priority points and has communicated this to EWM via the ERP system . Provided the Warehouse Activities status is not
Completed , EWM has updated priority points in the inbound delivery.


!--a11y-->
1.7 Ad Hoc Movement
Use
Ad hoc movements are unplanned goods movements that you create manually within a warehouse. This means that the decision to make an ad hoc movement is
not controlled by the system. Instead, it is triggered manually. Ad hoc movements do not have a preceding document. An ad hoc movement may be necessary for
the following reasons:
● The wrong product is located in the storage bin.
● You have to take the product to another storage bin due to damage, for example for a quality inspection.
● You want to take a product to the appropriate storage bin for scrapping.
● You have to empty an aisle or storage bin for safety reasons.
● You want to perform unplanned rearrangement movements.
● You have to clear away stock lying around in the warehouse.
Prerequisites
● Stock is available for the product to be moved.
● You have defined a warehouse process type in Customizing for EWM under Cross-Process Settings ® Warehouse Task ® Define Warehouse Process
Type.
● If you do not enter a source or destination storage bin for ad hoc movement and want the system to determine this automatically, you can control this using
stock removal and putaway strategies. For more information about prerequisites, see Putaway and Stock Removal Strategies.
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 7 of 9
Features
In an ad hoc movement, you move the stock of products from one storage bin to another. To be able to reproduce these movements, you manually create a
product warehouse task (product WT) or a handling unit warehouse task (HU WT). If you work with HUs, you can also unpack or repack the products belonging to
an HU by creating a product WT in the HU WT.
The following table shows the significant data for manually creating product WTs and HU WTs:
Product WT HU WT
The system uses the product and source storage data from the stock overview that you
have displayed by entering selection criteria. If you do not want the product to be removed
from a specific storage bin, you can control the determination of the source storage data
using stock removal strategies.
The system takes the HUs and source storage data from the overview.
Warehouse process type Warehouse process type
Destination storage data (optional) Destination storage data (optional)
Reason (optional) Reason (optional)
Source quantity –
You can manually overwrite the values determined by the system. For the values entered manually, the system checks if they match the configuration of the
storage type, storage section, and storage bin in question, for example, if mixed storage or receipts are allowed.
Immediate confirmation of the WTs is optional. Depending on the warehouse process type, you can confirm WTs directly after they have been created. While a WT
is still open, in other words, until you have confirmed it, the assigned product quantity is not available at the source storage bin nor at the destination storage bin,
but belongs to reserved stock. After you have confirmed a WT you can no longer delete it. You can, however, cancel it.
Radio Frequency Environment
In a radio frequency environment, you can also perform ad hoc movements for products and HUs. For more information, see Ad Hoc Movements Using Radio
Frequency.
Actions
To create a product WT, on the SAP Easy Access screen, choose Extended Warehouse Management ® Work Scheduling ® Create Warehouse Task
Without Reference ® Move Product.
To create an HU WT, on the SAP Easy Access screen, choose Extended Warehouse Management ® Work Scheduling ® Create Warehouse Task Without
Reference ® Move Handling Unit.


!--a11y-->
1.8 Posting Change for Stocks
Use
In Extended Warehouse Management (EWM) , you can make a posting change for stock, for example:
· From available stock to blocked stock (for example, in the case of a complaint)
· From available stock to customs blocked stock
Prerequisites
· You have made the settings for posting changes in the warehouse process type in Customizing for EWM under Cross-System Settings ® Warehouse
Task ® Define Warehouse Process Type. Here you define, for example, whether a warehouse task (WT) is created automatically during the posting
change, or whether it is to be created before or after the posting change.
· You have optionally defined destination data for stocks in conjunction with the warehouse process type that the system is to suggest for posting changes. You
make these settings in Customizing for EWM under Internal Warehouse Processes ® Default Values for Posting Changes.
Features
You make a posting change for stock by changing the relevant stock attributes and then creating the posting change. You can change the following stock
attributes, for example:
· Storage bin
· Stock type
· Batch
· Sales order or project
You want to move stock from available stock to quality inspection stock. You have the following options that you can configure in Customizing.
§ The stock is to remain in the storage bin, but is no longer to be available for picking. In this case, the system does not create a WT and the stock is
simply given a different stock type.
§ You want to take the stock to the quality department. In this case, the system creates a WT. There are two options:
PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 8 of 9
· The system creates the WT and then a posting change is made automatically for the stock when the destination storage bin is confirmed.
· The stock is booked out of the source storage bin and then the WT is created automatically.
You can make posting changes for stock for which serial numbers exist on a serial number basis. For more information about serial numbers, see Serial Number.
Activities
To post stocks, on the SAP Easy Access screen, choose Extended Warehouse Management ® Work Scheduling ® Make Posting Change for Product.
In this transaction, you can choose and make a posting change for both available stock and the entire stock.

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 9 of 9