Goods Receipt

Goods ReceiptPDF download from SAP Help Portal:http://help.sap.com/saphelp_scm50/helpdata/en/1c/d1fd406b8af16fe10000000a1550b0/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.

NoteThis 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 purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable 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 expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. 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 25

Table of content1 Goods Receipt1.1 Storage Control1.1.1 Process-Oriented Storage Control1.1.1.1 Direct and Combined Storage Control (Putaway)1.1.1.2 Updating the Inbound Delivery in the GR Process1.1.2 Layout-Oriented Storage Control1.1.2.1 Storage Group1.2 Slotting1.2.1 SAP APO Interface for Transferring Requirement Data1.2.2 Update of Results in Product Master1.2.2.1 Update Attribute Storage Bin Improvable1.2.3 Consideration of Storage Types1.2.4 Use of Storage Bin Type Determination Rules1.2.5 Simulation of Slotting1.2.6 Rearrangement1.2.6.1 Example of Rearrangement1.3 Storage Bin Determination for Putaway1.4 Connection of Delivery Processing to Quality Management1.5 Counting1.6 Deconsolidation1.7 Putaway1.7.1 Creation of Warehouse Tasks for Putaway1.7.2 Specification of the Putaway Path1.7.3 Putaway Using Radio Frequency1.8 Confirmation Correction


Page 2 of 25

!--a11y-->

1 Goods Receipt

PurposePutaway enables you to display your complex putaway process steps and includes the following functions:

Unloading Counting Deconsolidation Final Putaway

It takes into account your warehouse arrangement (for example, putaway using identification points in a high rack storage area) as well as the process-orientedrules and process flows defined by you (for example, counting requests, repacking). Extended Warehouse Management (EWM) contains putaway strategies tosimplify the search for appropriate storage bins.You can put away your products directly or through storage control.You can only execute complex putaway processes by using handling units.

Prerequisites You have defined the following basic settings in Customizing for Extended Warehouse Management (EWM):

Basic settings are, for example:

IMG Activity Path in Implementation Guide (IMG)Storage types, storage area, storage bins Implementation Guide (IMG) for SAP Supply Chain Management ( SAP SCM ) under

Extended Warehouse Management Master Data Define Storage Type Define Storage Section Storage Bins

Activity Areas Implementation Guide (IMG) for SAP SCM under Extended WarehouseManagement Master Data Activity Areas Define Activity Areas

Activity types Implementation Guide (IMG) for SAP SCM under Extended WarehouseManagement Master Data Activity Areas Activity Types Define ActivityTypes .

if required, work centers, for example, for deconsolidation For more information about defining putaway steps, see the Implementation Guide(IMG) for SAP SCM under Extended Warehouse Management Master Data Work Center Define Work Center.

Doors Implementation Guide (IMG) for SAP SCM under Extended WarehouseManagement Master Data Warehouse Door Define Warehouse Door

Staging areas Implementation Guide (IMG) for SAP SCM under Extended WarehouseManagement Goods Issue Process Define Staging Areas

You have displayed your putaway steps in the system.For more information about defining putaway steps, see the Implementation Guide (IMG) for SAP SCM under Extended Warehouse Management Cross-Process Settings Warehouse Task Layout-Oriented Process Control or under Process-Oriented Storage Control.

All required processes are fully integrated. The system updates, for example, the inbound delivery in the warehouse activities.

Process 1. The process begins when SAP R/3 receives an advanced shipping notification from an external system (for example, SAP CRM ) for a planned inbound

delivery. 2. The ERP system uses this advanced shipping notification to create an inbound delivery, and distributes it to EWM. 3. EWM uses the data from this inbound delivery to create a warehouse request.

This warehouse request is the starting point for the putaway process.If you reject the inbound delivery in EWM, EWM sets the planned delivery quantity to zero and notifies the ERP system. EWM ends the inbound deliveryand sets the status of the warehouse request to Completed .

For more information, see Warehouse Request for Returns.

ResultsEWM uses the warehouse request to create one or more warehouse tasks for the putaway (putaway WT). You can use it to put away the products.


Page 3 of 25

!--a11y-->

1.1 Storage Control

UseYou can use the process-oriented as well as layout-oriented methods for storage control. The goal of storage control is to display your complex putaway or stockremoval process steps based on your processes or your layout data. During putaway or stock removal, an individual process step can be executed on singlelevel basis or on multi level basis (that is, through intermediate storage types).You can combine the process-oriented storage control with the layout-oriented storage control. Here, EWM always executes the process-oriented storage controlfirst. The layout-oriented storage control then checks whether the sequence of putaway process steps is possible in layout view, and if required, adjusts the flow ofthe putaway or stock removal.

Based on the process-oriented storage control, EWM determined the following putaway process flow: Unloading at door Counting at counting station Checking the quality Executing value-added services Putaway in high rack storage areaThe layout-oriented storage control determines that a direct putaway in the high rack storage area is not possible and that the putaway must occurwith the use of an identification point. Unloading at door Counting at counting station Identification of goods at the ID point Putaway in high rack storage area

IntegrationExtended Warehouse Managment (EWM) uses the delivery to determine, via delivery type and delivery item among others, the warehouse process type. Thiscontains the procedure, in other words, the putaway or stock removal process with different activities. EWM transfers this operation to the handling unit to be putaway or removed from stock. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal.

PrerequisitesYou have defined the following in Customizing for the putaway:

Paramaters that specify the work station determination for the next function (for example, counting) within the goods receipt processThe following parameters are possible:

Source storage type Destination activity area or destination storage type Warehouse process type Handling unit type

Determination of the warehouse process type, using the delivery type and delivery item type, among others.

FeaturesFor information about the features of storage control, see Process-Oriented Storage Control and Layout-Oriented Storage Control.

!--a11y-->

1.1.1 Process-Oriented Storage Control

UseYou use this type of storage control to map complex putaways or stock removals. In doing so, you combine your storage process steps into one storage process.You can also trace the status of the individual process steps.

Process-oriented storage control only operates with handling units.


Page 4 of 25

IntegrationFor more information about integration, see Storage Control.

PrerequisitesFor more information about the prerequisites, see Storage Control.

FeaturesYou define the process steps for your complex storage process.A process step is, for example, unloading, counting, or deconsolidating. Extended Warehouse Management (EWM) recognizes internal process steps predefinedby SAP and external steps that you can define yourself. Your external process stesps can base themselves on internal ones.In addition, internal or external process steps can be simple, such as unloading, or combined, such as deconsolidating.For more information, see Direct and Combined Storage Control.The process steps for the Counting and Deconsolidating processes predefined by SAP can be dynamic.During goods receipt or goods issue, EWM copies the predefined process steps from the storage process type to the handling unit. EWM assigns these processsteps to a handling unit as soon as it has created or changed them.

ActivitiesTo make Customizing settings for process-oriented storage control, see the Implementation Guide (IMG) for SAP Supply Chain Management (SAP SCM) underExtended Warehouse Management Cross-Process Settings Warehouse Task Define Process-Oriented Storage Control.

!--a11y-->

Direct and Combined Storage Control (Putaway)

UseIf you want to execute a direct putaway, you do not have to define anything in the process-oriented storage control.If you want to define complex putaway processes, you have to use a combined process-oriented storage control. Extended Warehouse Management ( EWM )uses this during creation of a warehouse task to determine the intermediate storage types (for example, deconsolidation station, counting station).For information about integration and the prerequisites, see Storage Control .

FeaturesDirect Storage Control at PutawayIf EWM determines that you are to put away a handling unit (HU) directly, it creates a warehouse task for this HU that determines the way from the source storagetype to the destination storage type. For more information about updating the status, see Updating the Inbound Delivery in the GR Process.The following graphic shows you the relationship between direct putaway and creation of warehouse tasks.


Page 5 of 25

Combined Storage Control at PutawayIf EWM determines that you are to put away a HU from stock using one or more intermediate storage types, it creates one warehouse task per route section forthis HU.

One warehouse task that describes the route from source storage type to intermediate storage typeIrrespective of your settings in Customizing, EWM also creates a warehouse task per product contained in the HU. If, for example, an inbound delivery ispacked and the HU has no profile for process-oriented storage control, EWM creates product warehouse tasks at putaway.

Based on your settings in Customizing, one warehouse task from the intermediate storage type to the next intermediate storage type, or to the finaldestination storage type.

You can carry out different activities at the intermediate storage types. For example, within a putaway process, at an intermediate storage type, you can distributeHUs containing different products to putaway HUs.In combined putaway, you can determine the final destination storage type either right at the beginning of your putaway process, or later.EWM manages the intermediate storage types in the same way as standard storage types. For example, you can break these down into storage sections and

storage bins.For more information about updating the status, see Updating the Inbound Delivery in the GR Process.The following graphic shows you the relationship between combined putaway and creation of warehouse tasks.

ExampleDirect Goods ReceiptThe following is a sample process flow of a direct goods receipt. 1. The truck comes to the loading ramp. 2. You open the truck. 3. In EWM , you confirm the arrival of the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and

Receiving. 4. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. You unload the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving Unload. 6. You count the number of pieces of your products and confirm these in the WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse

Management Execution Confirm Warehouse Task. 7. You execute the putaway. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Confirm Warehouse


Page 6 of 25

Task.Combined Goods ReceiptThe following is a sample process flow of a combined goods receipt. 1. The truck comes to the loading ramp. 2. You open the truck. 3. In EWM , you confirm the arrival and opening of the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management

Shipping and Receiving. 4. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. You unload the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving Unload. 6. You count the number of pieces of your products and confirm these in the WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse

Management Execution Confirm Warehouse Task. 7. EWM indicates that a deconsolidation of the products is necessary. 8. You store your products at the intermediate storage location and confirm this. To do this, on the SAP Easy Access screen, choose Extended Warehouse

Management Execution Confirm Warehouse Task. 9. You execute the deconsolidation at the intermediate location. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management

Execution Deconsolidation in Goods Receipt. 10. You store your products at the destination storage bin. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management

Execution Confirm Warehouse Task.

!--a11y-->

Updating the Inbound Delivery in the GR Process

UseExtended Warehouse Management (EWM) updates the inbound delivery corresponding to the goods receipt activities. For the goods receipt process (GRprocess), EWM maps the warehouse with the goods receipt and interior of the warehouse areas. This allows EWM to determine the point in time from when aputaway is planned, that is, from when a warehouse activity exceeds the limit for the interior of the warehouse. The following information belongs to the goodsreceipt area:

Transportation units (TUs) Storage bins at warehouse doors Staging area groups

All storage types that do not correspond to goods receipt belong to the interior of the warehouse area. For example: Work centers Identification points Final storage types

EWM updates the statuses Unloading , Putaway Planning and Putaway in the inbound delivery, corresponding to this warehouse mapping.

Features

Updating an Inbound Delivery with a Handling Unit Warehouse Task (HU WT) For Packed StockThe following graphic and description shows you the connection between process steps in GR and updating the inbound delivery with an HU WT for packedstock.

You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery. The following applies for the status Unloading :

If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery (see number1 in the graphic).

If you confirm an HU WT that is moving from a staging area group to a door or a TU, EWM resets the status Unloading in the inbound delivery (seenumber 2 in the graphic).

The following applies for the status Putaway Planning : If you or the system generate an HU WT that is moving from goods receipt to the interior of the warehouse, EWM sets the status Putaway Planning in the

inbound delivery (see number 3 in the graphic). If you cancel an HU WT that is moving from goods receipt to the interior of the warehouse, EWM resets the status Putaway Planning in the inbound

delivery (see number 4 in the graphic). If you confirm an HU WT that is moving from the interior of the warehouse to goods receipt, EWM resets the status Putaway Planning in the inbound

delivery (see number 5 in the graphic).


Page 7 of 25

The following applies for the status Putaway :If you confirm an HU WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery (see number 6 in the graphic).

Updating an Inbound Delivery with a Product Warehouse Task (Product WT) For Unpacked StockYou perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery.

The following applies for the status Unloading :If you confirm a product WT for unpacked stock that is located in a TU or storage bin at the door, EWM sets the status Unloading in the inbound delivery. Aprerequisite for this is that the destination location in the product HU is not a TU, or that the destination storage type in the product WT is not a door.

The following applies for the status Putaway Planning : If you or the system generate a product WT that is moving from the goods receipt bin to another storage bin, EWM sets the status Putaway Planning in

the inbound delivery. If you cancel a product WT because EWM originally set the status Putaway Planning in the inbound delivery, EWM resets the status Putaway

Planning in the inbound delivery. If you move a product back to its original goods receipt bin with a product WT, EWM resets the status Putaway Planning in the inbound delivery.

If you move a product from the goods receipt bin to an HU, and this HU is in the interior of the warehouse, EWM always sets the status Putaway Planning inthe inbound delivery. EWM does not update the status Putaway Planning unless the HU is in the interior of the warehouse .

The following applies for the status Putaway :If you confirm a product WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery.

Updating an Inbound Delivery with Storage ControlThe following graphic and description shows you the connection between process steps in GR and updating the inbound delivery with storage control.

You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery. The following applies for the status Unloading :

If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery (see number1 in the graphic).

If you confirm an HU WT that is moving from a staging area group to a door or a TU, EWM resets the status Unloading in the inbound delivery (seenumber 2 in the graphic).

The following applies for the status Putaway Planning : If you or the system generate a product WT for putaway and an HU WT for unloading, EWM always sets the status Putaway Planning in the inbound

delivery corresponding to the warehouse activities for the product WT. EWM uses the HU WT to update the status Unloading in the inbound delivery(see number 3 in the graphic).

If you or the system generate an HU WT into the interior of the warehouse and no product WT for putaway exists, EWM always sets the status PutawayPlanning in the inbound delivery corresponding to the warehouse activities for the HU WT (see number 4 in the graphic).

The following applies for the status Putaway :If you confirm a product WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery corresponding to the product WT. Ifyou confirm an HU WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery corresponding to the HU WT. This meansthat, depending on which WT you confirm first, EWM sets the status Putaway in the inbound delivery with this WT (see number 6 in the graphic).

Updating an Inbound Delivery and Outbound Delivery Order in Cross-DockingEWM performs cross-docking (CD). For the CD-relevant products, EWM generates one or more pick-warehouse tasks (pick-WTs) for CD and updates the inbounddelivery and the outbound delivery order simultaneously. For the other products, EWM generates standard product WTs.

The following applies for the status Unloading : If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery. If you confirm an HU WT that is moving from a staging area group to a door or TU, EWM resets the status Unloading in the inbound delivery.

The following applies for the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order in CD: If EWM generates a pick-WT for CD, the system sets the status Putaway Planning in the inbound delivery and the status Picking Planning in the

outbound delivery order . If you cancel a pick-WT for CD, EWM resets both the status Putaway Planning in the inbound delivery and the status Picking Planning in the

outbound delivery order . The following applies for the status Putaway in the inbound delivery and the status Picking in the outbound delivery order in CD:

If you confirm a pick-WT for CD, EWM sets the status Putaway in the inbound delivery and the status Picking in the outbound delivery order .

!--a11y-->

Layout-Oriented Storage Control


Page 8 of 25

UseYou can use the layout-oriented storage control if stock movements in your warehouse do not occur from a source storage bin to a destination location directly, butrather via intermediate storage bins.

The layout-oriented storage control only operates with handling units.One exception is the process display with picking or identification points.

You use layout-oriented storage control in the material flow system to define conveyor segments.

IntegrationFor more information about integration, see Storage Control.

PrerequisitesFor more information about the prerequisites, see Storage Control.

FeaturesFor layout-oriented storage control, you define external warehouse process steps for your warehouse, including identification points and pick points.

For example, you have a high rack storage area. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B(high rack storage area), the system should execute a contour and weight check to ensure that the product pallet can be put away in the high rackstorage area safely. For this activity, Extended Warehouse Management ( EWM ) splits the warehouse order into two: one from storage bin A toidentification point I, and a second from identification point I to storage bin B.

You can move your goods using a pick point during picking.

ActivitiesTo make settings in Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for SAP Supply Chain Management (SAP SCM) underExtended Warehouse Management Cross-Process Settings Warehouse Task Layout-Oriented Storage Control.

!--a11y-->

1.1.2.1 Storage Group

DefinitionThe storage group is a grouping of storage bins within a storage type that is used to determine intermediate storage bins.

UseExtended Warehouse Management ( EWM ) uses the storage group in layout-oriented storage control to determine the intermediate storage bins.

The material flow system also uses layout-oriented storage control and thereby the storage group to define conveyor segments.

StructureThe storage group consists of a four-character identifier that you assign to a warehouse number and a storage type.

IntegrationEWM uses storage groups in layout-oriented storage control and in the material flow system.

ExampleYou group all the storage bins in an aisle into a storage group since you want to take the goods that you remove from this aisle to an interim storage bin at the endof the aisle.


Page 9 of 25

!--a11y-->

1.2 Slotting

UseDuring slotting, a storage concept is automatically determined for a product. The system determines the underlying storage parameters that are relevant forputaway on the basis of master data, that is, product data, requirement data, and packaging data. These parameters describe the storage section in which theproduct is to be stored, the properties that the storage bin is to have, and the putaway strategy that is to be used. Slotting takes into account master data that is notdependent on the execution process. If the putaway process for a product is dependent on execution parameters, this dependency is taken into account later onduring storage bin determination for putaway. This does not, however, have an effect on the results of slotting.

Prerequisites You work with storage bin types. You have defined the attributes in the product master that you want to use to determine the storage parameters. You have defined a number range interval and assigned it to your warehouse in Customizing under Extended Warehouse Management Goods Receipt

Process Slotting General Settings. You have defined storage type sequences in Customizing under Extended Warehouse Management Goods Receipt Process Slotting Master

Data. You have made the settings for the condition technique in Customizing under Extended Warehouse Management Goods Receipt Process Slotting

Condition Technique. You have defined condition records. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting

Condition Maintenance for Slotting.

FeaturesDuring slotting, the system determines the following storage parameters and stores them in the product master: 1. Putaway control indicator (and, optionally, stock removal control indicator) 2. Maximum quantity in storage type 3. Storage section indicator 4. Storage bin typesThe system always performs step 1. Steps 2 to 4 are optional.Steps 1, 3, and 4 are performed using the condition technique. Step 4 can also be performed using storage bin type determination rules. For more informationabout the condition technique, see the SAP Library under mySAP Customer Relationship Management CRM Enterprise Enterprise Sales SalesManagement for Commercial and Industrial Customers Basic Functions Condition Technique.Slotting is optional. We recommend that you perform it periodically in the background.The results of slotting can be used in storage bin determination. Slotting also forms the basis of rearrangement.

ActivitiesTo perform slotting, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting Slot Products for Warehouse.Then choose the storage parameters that the system is to determine.

!--a11y-->

SAP APO Interface for Transferring Requirement Data To be able to calculate parameters such as the maximum quantity in the storage type, slotting needs requirement data for the relevant product. This requirementdata can come from SAP Advanced Planning and Optimization (SAP APO). Extended Warehouse Management (EWM) stores this information locally in theproduct master (on the Slotting tab page, Requirement/Demand Data area).You can also fill these local attributes in EWM with data from other sources. To do this, you have several processing options in the product master, for example,manual input or mass maintenance.SAP APO and EWM manage requirement data at different organizational levels. SAP APO performs planning processes for locations of the type Plant . EWMstores requirement data at warehouse number level. Slotting assumes that a 1:1 relationship exists between the SAP APO location and the EWM warehousenumber. If the relationship is not 1:1, you can use Business Add-Ins (BAdIs) for the conversion.In most cases, SAP APO and EWM run on different systems. The calling EWM system needs information about the SAP APO instance such as:

Logical system Time interval for which the system is to read requirement data Information as to whether the data is forecast data or historical data

You define this information in Customizing for EWM. For more information, see the Implementation Guide (IMG) under Goods Receipt Process Slotting General Settings Change Information for APO Instances.

If you have set the following indicators on the selection screen for slotting, the system reads the requirement data from SAP APO when performing slotting:


Page 10 of 25

Update Requirement Quantity Update Number of Order Items Update Recommended Storage Qty

You can also read the requirement data as a separate process.

!--a11y-->

Update of Results in Product Master

UseThe system updates the results of the slotting run in the product master.

FeaturesAll the product attributes that form the slotting results exist twice in the product master:

As active values As planned values (can be recognized due to their name)

The exact values that are updated when the results are updated depends on the save mode that you chose when you called slotting: Do Not Save Results

We recommend that you use this option if you have performed slotting interactively and you want to analyze the results. If you have performed slotting in thebackground, you can analyze the log, but you cannot see the results directly.

Save Results (The system only updates the planned values in the product master.)Depending on the storage bin and stock situations, it can be useful to save the results of slotting as planned values only. The system only keeps the plannedvalues for a possible activation, and does not use them in storage processes.

Save and Activate Results (The system updates both the planned values and the active values in the product master.)The system updates the results of slotting in the fields for the planned values and the active values in the product master. These new values are thenavailable immediately for all storage processes.

Product Attribute LevelsThe product master has various views that represent various levels of product attributes:

Global views Warehouse-number-dependent views Storage-type-dependent views

Before a slotting run, only a global view must exist for the product, in other words, the product must be known in the system. The system either creates thewarehouse-number-dependent views and storage-type-dependent views when updating the results in the product master or it updates them if they existedalready.

Fixing ValuesYou can use a relevant indicator to fix all product attributes that can form the results of slotting. In this case, the system does not overwrite these attributes duringslotting.

!--a11y-->

Update Attribute Storage Bin Improvable

UseSlotting determines the optimum storage type, storage section, and storage bin type for a product. The system can determine whether a certain stock (quant) isstored in an optimum way. To do this, it compares these optimum values with the attributes of the storage bin in which the quant is located.Since the attribute Storage Bin Improvable depends on product attributes and on the current storage bin, it exists in both the fixed bin table and in the quant.

Instances of the Attribute Storage Bin ImprovableThe attribute has the following instances:

Not Improvable ( )All three attributes ( storage type , storage area , and storage bin type ) are optimum.

Pick with Priority (A)You can use this instance to support campaigns. You must configure this process manually. If a significantly greater demand is expected for a product duringa campaign, you can create additional new fixed storage bins (picking bins) and can choose the instance Pick with Priority for these bins. You should alsoadjust the maximum storage type quantity of the relevant storage type for the product, or deactivate the check.This instance is independent from the other instances and it is never set automatically by slotting.

Improvable (B)One of the three attributes ( storage type , storage section , or storage bin type ) is not optimum. The criteria for the instance Storage Type Improvable (C)


Page 11 of 25

are not met. Storage Type Improvable (C)

The storage section and storage bin type are optimum. The current storage type belongs to a storage type group. The storage type is optimum for the productwithin the group but it is not optimum on a global level. In other words, the storage type group is not first in the search sequence.

UpdateWhen you save or activate the results of slotting for a product, the system updates the attribute Storage Bin Improvable for the following in the warehousenumber:

For all quants of the product within the warehouse number For all existing and any newly-assigned fixed storage bins for the product within the warehouse number

The system determines the attribute Storage Bin Improvable for the new quant in the destination storage bin for each stock movement within the warehousewhere the destination storage type has the storage type role Standard Storage Type .

!--a11y-->

1.2.3 Consideration of Storage Types In slotting, the system determines attributes for a subset of storage types only. These storage types are assigned to a warehouse number.You define the relevant storage types in Customizing for EWM (Extended Warehouse Management) by using the Warehouse No. and PutawayControlInd keyfields. For more information, see the Implementation Guide (IMG) under Goods Receipt Process Slotting Master Data Define Putaway ControlIndicator.You have assigned a storage type search sequence to the putaway control indicator in Customizing for EWM. The search sequence can contain storage types orstorage type groups.

Storage TypesThe system interprets each storage type as an independent area in the warehouse (for example, reserve or picking area). It assumes that stock for a product is tobe stored in each storage type.

Storage Type GroupsThe storage types in a storage type group have an equal weighting. The system assumes that a product is to be stored in one storage type only within a group.If, therefore, the system considers the storage type group for a certain product, there can be a prioritization of the storage types within this group in relation to thisproduct.The system uses the optimum storage bin type per storage type for the prioritization. It determines an optimum storage bin type from the potential storage bintypes for each storage type. It then prioritizes the optimum storage bin types again. When doing this, the system uses the same criteria as it used to determine theoptimum value within a storage type. The sequence of storage bin types produces the sequence of storage types.The systems updates the position of a storage type in accordance with the prioritization in the product master in the storage type view in the Putaway Sequenceattribute. It then uses this information when creating warehouse tasks (WTs).

Skip Storage TypeIf the system could not determine the optimum storage section indicator or the optimum storage bin type during slotting, it does not consider the storage type whencreating a WT. This system does this by setting the Skip During Putaway indicator in the storage type view of the product master.In this case, the system does not set the following attributes:

Min. Replenish. Qty (Minimum Replenishment Quantity) Plnd Min. Replen. Qty (Planned Minimum Replenishment Quantity)

Maximum QuantityThis also means that replenishment cannot take place in this storage type.

!--a11y-->

Use of Storage Bin Type Determination Rules

UseThere are two options for determining the optimum storage bin type in slotting:

Using the condition technique (in the same way as determining the putaway control indicator and the storage section indicator) Using storage bin type determination rules

The option that the system uses depends on the parameters that you have defined at storage type level for slotting.


Page 12 of 25

PrerequisitesIn Customizing for Extended Warehouse Management (EWM), you have defined whether you want to work with the condition technique or with storage bin typedetermination rules. In the latter case, you have chosen the required storage bin type determination rule. For more information, see the Implementation Guide(IMG) for EWM under Goods Receipt Process Slotting General Settings Define Storage Type Parameters for Slotting .

FeaturesThe following storage bin type determination rules are available:

Maximum Weight Capacity Factor: Material Simple Volume Check Simple Dimension Check

The system compares the dimensions of the relevant packing level (PL) with the dimensions of the storage bin type (BT) in accordance with the followinglogical expression:

Length (PL) < Length (BT) AND Width (PL) < Width (BT) ANDHeight (PL) < Height (BT)

The system calculates the maximum number of packages by dividing the length, width, and height of the storage bin type by the length, width, and height ofthe packing level. The result is a maximum number per dimension. The global maximum number is then the product of the three maximum values perdimension.

Dimension Check with Z-Axis RotationThe system compares the dimensions of the relevant packing level with the dimensions of the storage bin type in accordance with the following logicalexpression:

Length (PL) < Length (BT) AND Width (PL) < Width (BT) ANDHeight (PL) < Height (BT)ORLength (PL) < Width (BT) AND Width (PL) < Length (BT) ANDHeight (PL) < Height (BT)

The system calculates the maximum number of packages as described in the section Simple Dimension Check for each of the two orientations allowed.The global maximum number is then the greater of the two maximum values per orientation.

Dimension Check with Rotation and TiltThe system compares the dimensions of the relevant packing level with the dimensions of the storage bin type in accordance with the following logicalexpression:

Length (PL) < Length (BT) AND Width (PL) < Width (BT) ANDHeight (PL) < Height (BT)ORLength (PL) < Length (BT) AND Width (PL) < Height (BT) ANDHeight (PL) < Width (BT)ORLength (PL) < Width (BT) AND Width (PL) < Length (BT) ANDHeight (PL) < Height (BT)ORLength (PL) < Width (BT) AND Width (PL) < Height (BT) ANDHeight (PL) < Length (BT)ORLength (PL) < Height (BT) AND Width (PL) < Length (BT) ANDHeight (PL) < Width (BT)ORLength (PL) < Height (BT) AND Width (PL) < Width (BT) ANDHeight (PL) < Length (BT)

The system calculates the maximum number of packages as described in the section Simple Dimension Check for each of the six orientations allowed.The global maximum number is then the greatest of the six maximum values per orientation.

Weight Check and Simple Volume Check Weight Check and Simple Dimension Check Weight Check and Dimension Check with Z-Axis Rotation Weight Check and Dimension Check with Rotation and Tilt

Additional Parameter Dimension RatioThe product master attribute Dimension Ratio (on the Slotting tab page) considers the ratio between the length, width, and height of the relevant packing level.The system calculates all the ratios between length, width, and height that make sense on the basis of the orientations allowed. Orientations are not permitted incases where the calculated ratio exceeds the parameter value from the product master.The system uses the dimension ratio in the following storage bin type determination rules:

Simple dimension check (one orientation) Dimension check with z-axis rotation (two orientations) Dimension check with rotation and tilt (six orientations) Weight check and simple dimension check Weight check and dimension check with z-axis rotation Weight check and dimension check with rotation and tilt

!--a11y-->

1.2.5 Simulation of Slotting PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 13 of 25

UseYou can use this function to simulate slotting without updating the product master.

FeaturesYou perform the simulation in the test system. There you can change the configuration in any way that you want to without causing errors. You can analyze theresults of the simulation step-by-step and can optimize the configuration.When you are satisfied with the result, you must adapt the configuration in the production system in accordance with the configuration in the test system. Part of theconfiguration is mapped via master data that you must change manually in the production system. We recommend that you then simulate slotting in the productionsystem to check the configuration. Afterwards, you can perform slotting in the production system, and can save and activate the results there.

Activities To simulate slotting, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting Slot Products for

Warehouse. To activate the plan values or to simulate the activation of plan values, on the SAP Easy Access screen, choose Extended Warehouse Management

Master Data Slotting Activate Plan Values .You cannot perform slotting runs in this transaction. You can only display and activate the results from a slotting run that you have performed interactively or inthe background. You can also simulate the activation of these results.

!--a11y-->

1.2.6 Rearrangement

UseYou can use rearrangement to optimize the arrangement of your products in the warehouse by moving stock such as fast-moving items to the relevant optimalstorage bin.

Prerequisites You have created products and stocks. You have defined a default warehouse process type in Customizing for Extended Warehouse Management (EWM) under Internal Warehouse Processes

Warehouse Optimization Specify Default Warehouse Process Type for Rearrangement. You have made the Customizing settings for putaway. If you want to work with slotting indexes, you must enter a value in the following places in the Evaluate Whse Item field in Customizing for EWM under

Goods Receipt Process Strategies : Storage Type Search Assign Storage Types to Storage Type Search Sequence Storage Section Search Maintain Storage Section Search Sequence Storage Bin Determination Alternative Storage Bin Type Sequence or HU Types Define HU Types for Each Storage Bin Type

FeaturesThe system compares the current storage type, storage section, and storage bin type with the optimal parameters from slotting. When doing this, it analyzes howwell suited the current parameters (storage type, storage section, and storage bin type) are to the product. If they are not optimal, the system proposes anoptimum storage bin.When searching for an optimum destination storage bin (destination storage bin determination), the system uses search sequences for storage types, storagesections, and storage bin types. The entries in the search sequences are sorted by the slotting index and in descending order.You can assign a slotting index for each step in a search sequence in Customizing. The first entry in a search sequence should not have a slotting index so that astorage bin with an optimum storage type, storage section, and storage bin type has a slotting index of zero.In the case of rearrangement, the system first tries to propose an optimum storage bin (with a slotting index of zero). If this is not possible, the system proposes analternative storage bin with the next lowest slotting index. The system only proposes an alternative storage bin if its slotting index is lower than that of the currentstorage bin.You can identify the most urgent stock transfers on the basis of the following data:

Slotting index of the current storage bin Difference between the slotting indexes of the proposed storage bin and the current storage bin

The system also displays the number of empty bins per storage type, storage section, and storage bin type as part of the analysis.For an example of rearrangement, see here.

Activities 1. To start rearrangement, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Rearrangement.


Page 14 of 25

2. Choose the required stocks. The system performs the analysis and displays the number of stock items per optimal storage bin type, storage section, andstorage bin type/storage section for each current storage bin type, storage section, and storage bin type/storage section.

3. Choose one of the analyses, the required cell, column, or row, and then Details . 4. In the detail view, choose the required stock item and create a warehouse task. The system proposes a destination storage bin and reserves it. Save the

warehouse task.

Alternatively, you can create a warehouse request to plan rearrangement as a wave. In this case, the system does not adopt the proposeddestination storage bin and does not reserve it.

You can also execute rearrangement in the background. To do so, on the SAP Easy Access screen, choose Extended WarehouseManagement Work Scheduling Rearrangement (Background).

!--a11y-->

1.2.6.1 Example of Rearrangement The first figure shows the warehouse before rearrangement takes place. The warehouse has an area for fast-moving items (golden zone). It is positioned along thecentral aisle of the warehouse to ensure that the picker can reach it easily. The area for slow-moving items is positioned behind this area.

The second figure shows a typical pick path before rearrangement takes place. Since some of the storage bins containing the products to be picked are situateda long way from the central aisle in the area for slow-moving items, the picker sometimes has to drive a long way down the side aisles to pick the requiredproducts.

The third figure shows how the system tries to shorten this long pick path during rearrangement by proposing that the fast-moving products are moved to the areafor fast-moving items.


Page 15 of 25

The fourth figure shows the pick path after rearrangement has taken place. During picking, fast-moving items are often picked. Since these are now closer to thecentral aisle, the pick path is shorter. Now the picker rarely has to drive down a side aisle to pick products.

!--a11y-->

Storage Bin Determination for Putaway

UseThe aim of storage bin determination is to find the best physical destination storage bin for a putaway process or an internal warehouse goods movement. Inaddition to other data, parameters from the product master that you have defined manually or that were determined in slotting are used to do this.Storage bin determination for putaway occurs automatically when a warehouse task is generated.

Prerequisites You have created storage bins. You have made the settings for putaway in Customizing for Extended Warehouse Management (EWM) , for example:

You have defined storage section search sequences under Goods Receipt Process Strategies Storage Section Search Maintain StorageSection Search Sequence.

You have defined HU types for each storage bin type under Goods Receipt Process Strategies Storage Bin Determination HU Types Define HU Types for Each Storage Bin Type.

FeaturesDuring storage bin determination, a physical storage bin is determined by means of determining and applying the suitable strategies.

In a fixed storage bin scenario, it could be the case that the fixed storage bin has already been determined for a storage type by slotting. In this


Page 16 of 25

case, you do not need to determine and apply additional search sequences.In a putaway process, storage bin determination covers the following steps:Determination of storage typesThe system first determines the storage type by determining and applying a storage type search sequence. The storage type search sequence defines in whichstorage types and in which order the system is to search for a destination storage bin for putaway.You can define multiple accesses for determining the storage type search sequence. The system checks these accesses until it finds a suitable storage typesearch sequence.You assign a putaway rule to each storage type in the storage type search sequence. The putaway rule specifies how a storage bin is to be determined, forexample, empty storage bin.In addition to the putaway rule, the storage behavior also plays a role. It describes the type of storage bins, for example, normal, bulk storage, or pallet storage.

If a product has the stock category Quality Inspection , it could be the case that all other parameters are unimportant. You could, therefore, definethe first access in such a way that the system is to search for a storage type search sequence where only this stock type is used.

Determination of storage sectionsFor each storage type that is found, the system then determines a storage section by determining and applying a storage section search sequence. You can usethe Business Add-Ins in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic.Determination of storage bin typesThen the system determines a storage bin type for each storage type by determining and applying a storage bin type search sequence. You can use theBusiness Add-Ins in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic.Determination of storage binsLast of all, the system uses a certain priority to evaluate the combinations of storage type, storage section, and storage bin type that have been found. Here it triesto find a storage bin for each combination in accordance with the putaway rule.

Slotting and storage bin determinationIf you use slotting, it could be the case that you want to prevent storage bin determination for products that have not yet been slotted. If, however,you do not use slotting, there is no reason to prevent storage bin determination. You can also use the IMG activity Define Warehouse NumberParameters for Putaway (under Goods Receipt Process Strategies ) to control at warehouse level whether storage bin determination is to bepermitted if slotting has not yet been performed for a product.

!--a11y-->

Connection of Delivery Processing to Quality Management

UseExtended Warehouse Management (EWM) groups together all the necessary data for Quality Management to automatically create inspection documents in thebackground in accordance with the Customizing for quality management. Here, EWM copies the inspection document number to the inbound delivery. In addition,EWM updates the document flow, the status for inspection planning, and, if necessary, the stock type in the inbound delivery.

IntegrationSee Creation of Inspection Document

Prerequisites You have carried out the Customizing for creating inspection documents. You have defined inspection rules (see Master Data). In the delivery, you have specified all the data necessary for the creation of an inspection document. If not all of the necessary data exists in the delivery by

the time at which EWM is to create the inspection documents, EWM creates the inspection documents later. For example, EWM is to create an inspectiondocument when the inbound delivery is activated. The batch number is required for creation. EWM only creates the inspection document once you havespecified the batch number.

FeaturesIn the following cases, EWM creates inspection documents in the background, regardless of Customizing:

If you or EWM activate an inbound delivery If EWM sets the status In Yard for an inbound delivery Before EWM creates a warehouse task Before you post the goods receipt

When EWM creates an inspection document, it simultaneously updates the inbound delivery. EWM sets the QM Check Planning status type to the status valueCompleted and the QM Counting Planning status type to the status value Completed . Regardless of whether you carry out a quality inspection or not, EWM

always updates the status data. For example, the result of quality inspection planning could be that EWM is not to carry out a quality inspection. EWM also setsthe status data in this case.Once EWM has created the inspection documents, it updates the document flow for the reference document types Q01 and Q03 . Thus, you can view all of the


Page 17 of 25

inspection documents for an inbound delivery in document flow.If necessary, EWM updates the stock type. For example, EWM changes the stock type in the inbound delivery from unrestricted-use stock to stock in qualityinspection.For more information, see Quality Inspection and Creation of Inspection Document.

ActivitiesIf you want to display the statuses QM Inspection Planning and QM Counting Planning , on the SAP Easy Access screen, choose Extended WarehouseManagement Delivery Processing Maintain Inbound Delivery . Go to the Status tab page.

!--a11y-->

1.5 Counting

UseThe aim of counting is to check the quality of a sample of inbound deliveries. This means that counting is a quality assurance measure in the goods receiptprocess that you can use to ensure consistency between the quantities entered in the system and the actual quantities.

Integration The Quality Inspection Engine (QIE), an integral part of the SCM system, provides essential functions that enable a system-supported check (counting)

in the inbound delivery process. Integration with an ERP system is required to enable inbound delivery notifications to be created automatically in Extended Warehouse Management

(EWM) .

PrerequisitesGeneral settings for counting

You have implemented the QIE and executed the following in Customizing for EWM under Cross-Process Settings Quality Management: You have assigned decision codes to decision groups. You have defined which of the available properties of the inspection object types the system is to use as dynamic criteria when creating the inspection

document. You have defined a percentage that specifies how many delivery items are to be counted. You have checked that the inspection object types and their properties have been activated.

You have defined quantity intervals and value intervals in Customizing for EWM under Goods Receipt Process Counting . You have defined inspection rules. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Quality

Management Maintain Inspection Rule.Additional settings for explicit countingStorage control

You have defined the following in Customizing for EWM under Cross-Process Settings Warehouse Task Define Process-Oriented Storage Control: Storage types and storage bins (basis of the counting station) External storage process steps Definition of the storage process

You have defined warehouse process types and control indicators for determining warehouse process types in Customizing for EWM under Cross-ProcessSettings Warehouse Task.

You have defined warehouse products. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Product Maintain Warehouse Product.

Counting station You have defined a work center for counting (counting station). To do so, on the SAP Easy Access screen, choose Extended Warehouse Management

Master Data Work Center Define Master Data Attributes.

FeaturesWhen you change or activate an inbound delivery notification, the system first determines whether the delivery items are to be counted. To do this, it checks if anactive inspection object type and inspection rule exist. Inspection object types define the inspection process. You use the inspection rule to define when adelivery item is to be counted. To do this, you draw on certain inbound delivery notification properties:

Warehouse number Document type of the delivery Partner (supplier) Product Quantity interval Value interval

If a valid inspection rule exists, the system creates an inspection document, taking into account the dynamic criteria. It marks the relevant delivery item forcounting.


Page 18 of 25

You then perform counting either explicitly or implicitly: Explicit counting

You must enter the count results for the products at the counting station. The system determines the storage bin (storage type) for this counting station on thebasis of the storage control settings. You can perform explicit counting only for handling units.

Implicit countingThe information specifying that a product must be counted is part of the warehouse task data. If a difference is determined, you must confirm the warehousetask with differences (exception code) to end the transaction. You can perform implicit counting only for unpacked products.

ActivitiesExplicit counting 1. You have changed or activated an inbound delivery notification in EWM . The system has found an active inspection object type and an inspection rule, and

has created an inspection document.Create a warehouse task with reference to the inbound delivery and confirm it. To do this, on the SAP Easy Access screen, choose Extended WarehouseManagement Work Scheduling Create Warehouse Task for Warehouse Request Putaway for Inbound Delivery. The system uses the storagecontrol settings to determine the storage bin for counting for all the delivery items with an inspection document.If the system had not created an inspection document because an active inspection object type and inspection rule were not available, the delivery itemswould be put away immediately at the final storage bin.

2. Call the counting station that is assigned to the storage bin for counting and enter the count results. To do this, on the SAP Easy Access screen, chooseExtended Warehouse Management Execution Quality Inspection and Count.

Implicit countingYou have changed or activated an inbound delivery notification in EWM . The system has found an active inspection object type and an inspection rule, and hascreated an inspection document.Create a warehouse task with reference to the inbound delivery, confirm the count results, and confirm the warehouse task. To do this, on the SAP Easy Accessscreen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request Putaway for Inbound Delivery.The delivery items are put away immediately at the final storage bin.

!--a11y-->

1.6 Deconsolidation

UseYou can use this function to divide up a deconsolidation handling unit (deconsolidation HU) across multiple putaway HUs. This is necessary if a deconsolidationHU contains different products that you want to put away in different storage sections.

IntegrationYou define the consolidation groups in Customizing for storage control.For more information, see the Implementation Guide (IMG) for SAP Supply Chain Management ( SAP SCM ) under Extended Warehouse Management Goods Issue Process Define Consolidation Group.

Prerequisites If Extended Warehouse Management (EWM) is to define a deconsolidation, one of the following cases must be present:

The activity areas for the products within an HU are different. The activity areas for the products within an HU are the same, but the consolidation groups are different. The activity areas and consolidation groups for the products within an HU are the same, but the maximum number of warehouse tasks for the HU has

been exceeded. In Customizing, you have defined activity areas. For more information, see the Implementation Guide (IMG) for SAP SCM under Extended Warehouse

Management Master Data Define Activity Area. In Customizing, you have defined deconsolidation rules. For more information, see the Implementation Guide (IMG) for SAP SCM under Extended

Warehouse Management Goods Receipt Process Deconsolidation. If you want to use deconsolidation in process-oriented storage control, you must have defined the deconsolidation attributes for each activity area. For more

information, see the Implementation Guide (IMG) for SAP SCM under Extended Warehouse Management Goods Receipt Process Deconsolidation Define Attributes for Deconsolidation for Each Activity Area.

FeaturesWhen EWM performs deconsolidation, it creates a warehouse task for each HU item, which deconsolidation then takes into account.

For example, you have a deconsolidation HU HU123 with product PROD1 for the reserve storage area RL, product PROD2 for the bulk storagearea BL, and product PROD3 for the high rack storage area HL.EWM creates the following warehouse tasks: A warehouse task for the deconsolidation HU A warehouse task for each product, for deconsolidating the deconsolidation HU into three putaway HUs. Other warehouse tasks, depending on your Customizing settings (direct or combined storage control).


Page 19 of 25

Special Features for Deconsolidation in Cross-DockingWhen you perform deconsolidation in cross-docking, EWM distributes the contents of the deconsolidation HU as follows:

EWM distributes the products in the deconsolidation HU that are not relevant for cross-docking across multiple putaway HUs, as in the standard putawayprocedure.

EWM distributes the products in the deconsolidation HU that are relevant for cross-docking across multiple pick-HUs.EWM does not determine the consolidation group of the pick-HUs for products that are cross-docking-relevant from the data of the destination storage bin, ratherfrom the data of the outbound delivery. For example, a consolidation group can correspond to the delivery in such a way that EWM assigns all products that belongto a delivery to a consolidation group as well. For more information about cross-docking, see Cross-Docking.

ActivitiesOn the SAP Easy Access screen, choose Extended Warehouse Management Execution Deconsolidation in Goods Receipt.

ExampleYou receive a deconsolidation HU with 15 warehouse tasks (WTs), where the destination data is all assigned to the same activity area. You have set theMaximum Number of WTs in the Deconsolidation HU to ten, and the Maximum Number of WTs in the Putaway-HU to five. This means that if you are using

process-oriented storage control, EWM forwards the HU to a deconsolidation station, due to the HU exceeding the permitted maximum number of WTs in thedeconsolidation HU.During deconsolidation at this location, EWM creates putaway-HUs. After you have confirmed the repacking of five product-WTs into the putaway-HU, EWMproposes this HU for closure, due to the parameter Maximum Number of WTs in the Putaway-HU . This means that it also releases the HU for the followingprocess step Putaway .

!--a11y-->

1.7 Putaway

UseThe destination of the final putaway is the putaway of products into storage bins in the warehouse. The starting point for this is the warehouse request. For theputaway, Extended Warehouse Management (EWM) determines a putaway path. EWM uses your settings to define the path that the warehouse employee shouldtake to put the products away.Regardless of how you perform putaways in your company, you can configure EWM in such a way that the putaway activities are performed in one of the followingways:

Automatically during creation of an inbound delivery Regularly at specific times Manually using overviews of the daily loads, after a request from an employee

You specify this using the Post Processing Framework.For scheduling and monitoring of the putaway operations, EWM stores a putaway status in each delivery item. This status tells you, for example, for which itemsputaway has already started.

IntegrationPutaway uses the following:

Putaway Strategies Slotting Storage Control

Features You can perform the final putaway using radio frequency devices (RF devices), or you can print the warehouse orders and enter the information for the final

putaway manually. You can then enter and save the manually entered data in EWM.Both on the RF devices display and on the paper printout, the sequence of the warehouse tasks corresponds to the putaway path.

If there are unplanned stock movements without a preceding document, you can create a warehouse request without a reference. If, for example, the connection between SAP R/ 3 and EWM is interrupted, you can create a warehouse request manually. SAP R/ 3 and EWM

compare their data at a later point when the connection is available again. You can use EWM to allow the system to define a putaway path for the putaway, which optimizes the order of the storage bins. Storage bin sorting takes

place in a logical section of the warehouse, the Putaway activity area, and refers to specific activity categories. When defining this path, EWM takes intoaccount both one-way streets as well as differentiations in the various putaway strategies, for example, first drive to all the right-hand bins, then to all the left-hand bins, or first drive to the standard bins, then to the reserve bins.

Warehouse Tasks for PutawayPutaway creates warehouse tasks for you, for the purpose of putting away your products. The warehouse tasks can be created in the following ways:

Automatically by EWM


Page 20 of 25

You can control the time by assigning a schedule condition in the Post Processing Framework Action (PPF Action). For example, Status Packed is Set orStatus Goods Receipt is Set .

Manually by a userPutaway requires warehouse tasks in order to

Specify the destination storage types, sections, and bins Specify the storage control for the destination storage type

For more information about storage control, see Process- and Layout-Oriented Storage Control.When EWM creates a warehouse task for putaway, it simultaneously checks whether the product to be put away is a hazardous substance. If the product is ahazardous substance, EWM determines (according to your Customizing) the storage type you can use to put away the hazardous substance. For more information, see Hazardous Substance Master.

ActivitiesIf you want to use RF devices, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Log On to RF Environment .If you want to print the warehouse order, make the relevant Customizing settings in the Implementation Guide (IMG) for SAP Supply Chain Management ( SAPSCM ) under Extended Warehouse Management Cross-Process Settings Warehouse Order Print.

!--a11y-->

Creation of Warehouse Tasks for Putaway

UseExtended Warehouse Management ( EWM ) automatically creates warehouse tasks for the putaway based on a warehouse request for an inbound delivery, so

that you can put away products.EWM uses a warehouse task to specify the following for the putaway: The destination storage types, sections, and bins The path to the destination storage type

PrerequisitesIf you want EWM to automatically group warehouse tasks into warehouse orders, you must have made the settings in Customizing for warehouse order creation.In the Implementation Guide (IMG) for SAP Supply Chain Management ( SAP SCM ), choose Extended Warehouse Management Cross-Process Settings Warehouse Order.

Features EWM can create warehouse tasks for an inbound delivery in the following ways:

EWM automatically creates warehouse tasks for an inbound delivery, using an action from the Post Processing Framework ( PPF ). You create the warehouse tasks manually.

When EWM creates a warehouse task for a warehouse request, it uses putaway strategies to determine the storage bin. For more information, see StorageBin Determination for Putaway.

When EWM creates a warehouse task, it uses direct or combined storage control to determine whether you should put away a handling unit directly or byusing interim storage bins. The warehouse task reflects the direct or combined storage control.

EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. For more information, see Warehouse OrderCreation.

EWM uses layout-oriented and process-oriented storage control, according to your Customizing settings. For more information, see Process-Oriented StorageControl and Layout-Oriented Storage Control.

In the warehouse task, EWM specifies various activities for you to perform (for example, deconsolidation), according to your Customizing settings.

Activities If you have made settings in Customizing for PPF for the PPF action to create warehouse tasks for putaway, EWM automatically creates the warehouse

task for putaway.In the Implementation Guide (IMG) for SAP Supply Chain Management , choose Extended Warehouse Management Cross-Process Settings Delivery Processing Actions Use Assistant to Create Actions .

If you want to create a warehouse task manually, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request Putaway for Inbound Delivery.

If you want to post goods receipts for all deliveries for an inbound delivery, and also want to create warehouse tasks for unloading, on the SAP Easy Accessscreen, choose Extended Warehouse Management Goods Receipt and Shipping Unload .

When EWM creates a warehouse request warehouse task for an outbound delivery, it simultaneously updates this warehouse request. EWM carries out thisupdate by updating the quantity in the document flow. If the quantity update leads to a change in status, EWM updates this change in the warehouse requestas well.


Page 21 of 25

You have an inbound delivery of 100 pieces of a product. EWM automatically creates three warehouse tasks (WT1, WT2, and WT3) for theentire quantity, based on the storage bin determination.Following creation of the warehouse tasks, the warehouse request status Putaway Planning changes to Completed .If EWM does not create warehouse tasks for the entire quantity, the Putaway Planning status is set to Partially Completed .The following table gives you an overview of the Putaway Planning status in the warehouse request.

Goods Receipt ProcessProduct Description

Delivery Item Warehouse Task Warehouse Request Status PutawayPlanning

P-01 10 WT1 for 10 pieces Partially Completed , after EWM createsWT1

P-01 20 WT2 for 30 pieces Partially Completed , after EWM createsWT2

P-01 30 WT3 for 60 pieces Completed , after EWM creates WT3

!--a11y-->

1.7.2 Specification of the Putaway Path

UseYou can use this function to specify a putaway path for each activity in the activity area. When Extended Warehouse Management (EWM) creates a warehouserequest (WT), it specifies this putaway path. During definition of putaway paths, you can assign more than one putaway path, or you can allow activity areas tooverlap. However, only one putaway path is active for each WT.

IntegrationSpecification of the putaway path is integrated into WT processing, which means that EWM sorts the WTs according to the putaway path.

Prerequisites You have defined the storage bin types, descriptions, and structure.

In Customizing for SAP Supply Chain Management , choose Master Data Storage Bins . You have defined activity areas and categories, have assigned storage bins to the activity areas, and have specified the sorting sequence of the activity

areas.In Customizing for SAP Supply Chain Management , choose Master Data Activity Areas .

You have assigned an activity to a warehouse process type.In Customizing for SAP Supply Chain Management , choose Cross-Process Settings Warehouse Task Define Warehouse Process Type .

FeaturesIf EWM has grouped several WTs into a warehouse order, then it sorts the WTs based on the warehouse order. This is not dependent on the product that iscontained in the handling unit.If you use radio frequency devices, you can skip a destination storage bin proposed by EWM. EWM places this destination storage bin at the end of the RFdisplay.

You cannot gain access to a destination storage bin because a colleague is currently putting away products in it. You skip the destination storagebin proposed by EWM and process the next one.

ActivitiesFor your putaway, you or EWM create the necessary WTs for the warehouse request of the outbound delivery. In so doing, EWM determines the putaway pathaccording to your settings in Customizing and saves this information in the WT. On the radio frequency device, EWM shows the destination storage bins in thispredefined sequence.

ExampleThe following figure shows you an example of specification of the putaway path, based on a warehouse order.


Page 22 of 25

EWM has created a warehouse order that contains WTs. It has created a WT for each handling unit item.EWM creates the following putaway path:

Document item Handling unit1 12 23 14 25 3

Therefore, if you simultaneously put away several HUs, EWM sorts these across the warehouse.

!--a11y-->

1.7.3 Putaway Using Radio Frequency

UseYou can execute putaways using a radio frequency presentation device (RF presentation device).

PrerequisitesYou have logged on in the RF environment.The destination storage bins of the warehouse orders to be processed are always in the same activity area.

FeaturesPutaway According to Handling Unit (HU)You enter a handling unit number (HU number) and the system searches for the corresponding warehouse order or warehouse orders.Putaway According to HU (Collective)You enter more than one HU number and the system searches for the corresponding warehouse orders.Putaway According to Warehouse OrderYou enter a warehouse order number and the system displays the warehouse tasks assigned to the warehouse order that are to be executed.

ActivitiesPutaway According to Handling Unit (HU)


Page 23 of 25

1. You enter a HU number. EWM thus includes the HU in the resource. 2. The system searches for the corresponding warehouse orders. 3. The system displays the following:

If the system finds a WT for the entire HU, the system displays the source data (HU number, destination storage bin). If the system finds WTs for the products in the HU, then you are dealing with a distributive putaway. The system displays the first WT it has found

according to the sort sequence of the destination storage bins. The system displays the following data: Source HU Product Quantity Batch Destination HU Destination storage bin

If a warehouse order has more than one WT, you can do the following: You can skip a WT. You can reverse the sequence in which the system displays the WTs. You can place the displayed WT at the end of the execution.

4. You confirm the data of the HU WT or of the first product WT. 5. If a warehouse order has more than one product WT, the system displays the data of the next product WT and the action repeats itself.Putaway According to Handling Unit (Collective) 1. You enter all desired HU numbers. 2. You decide whether you want to putaway further in a guided manner or according to product number or warehouse task. 3. The system searches for the corresponding warehouse task. 4. The further steps correspond to steps three to five for putaway according to handling unit.Putaway According to Warehouse Order 1. You enter a warehouse order number. 2. The system searches for the corresponding warehouse tasks. 3. The system displays the source data (product, quantity, batch, and source storage bin) of the first product WT that belongs to the warehouse order, or the

source data (HU and source storage bin) of the first HU WT that belongs to the warehouse order.If a warehouse order has more than one WT, you can do the following:

You can skip a WT. You can reverse the sequence in which the system displays the WTs. You can place the displayed WT at the end of the execution.

4. You confirm the source data of the first product WT or the source data of the first HU WT. 5. The system displays the destination data of the product WT (product, quantity, batch, and destination storage bin), or the destination data of the HU WT (HU

and destination storage bin). 6. You confirm the destination data of the first WT. 7. If a warehouse order has more than one WT, the system displays the source data of the next WT (product WT or HU WT), and the action repeats itself.

Exceptions to Putaway Using RFHU WT ConfirmationYou can specify an exception for this process and then:

Change the destination storage bin In general, skip the HU WT that is currently to be processed

For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system nolonger shows you this HU WT and you do not need to confirm the source data and destination data.

Product WT ConfirmationYou can specify an exception for this process and then:

Change the destination storage bin Record differences

For example, if a piece of the product quantity is damaged, you can enter a smaller product quantity rather than confirm the quantity. Change the batch In general, skip the product WT that is currently to be processed

For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system nolonger shows you this HU WT and you do not need to confirm the source data and destination data.

!--a11y-->

1.8 Confirmation Correction

UseFor example, if you want to change a quantity specification, you can still correct warehouse tasks in the goods receipt process that have already been confirmed.

PrerequisitesYou have defined a completion delay for inbound deliveries.For more information, see the Implementation Guide (IMG) for SAP Supply Chain Management under Extended Warehouse Management Goods ReceiptProcess Inbound Delivery Define Delay in Completing Inbound Deliveries.


Page 24 of 25

You are using a document type and item type with a status profile for which you have activated the status DWM .For more information, see the Implementation Guide (IMG) for SAP Supply Chain Management under Extended Warehouse Management Cross-ProcessSettings Delivery Processing Status Management Define Status Profiles.

FeaturesEWM delays sending a warehouse task that has already been confirmed, corresponding to the completion delay you have specified for inbound deliveries inCustomizing. In accordance with the completion delay, you can still correct the actual quantity for the destination storage bin and the batch. You make yourcorrection and specify an exception code in the warehouse task for each delivery item.When the completion delay has passed, EWM sets the status DWM for sending the completion indicator to Completed . By doing this, EWM also indirectly setsthe completion status DCO for the inbound delivery to Completed . Only when the completion status DCO for an inbound delivery has status valueCompleted does EWM forward the confirmed warehouse task to the ERP system. Only now does the ERP system perform any necessary activities, such as for

a returns process or a stock transfer order. From this point in time, you cannot make any further corrections in the confirmed warehouse task. You can schedulereport /SCWM/R_PRDI_SET_DWM to set the status DWM for sending the completion indicator to Completed . For more information, see the reportdocumentation.

If you do not specify a completion delay for inbound deliveries in Customizing, EWM immediately sets the status DWM for sending thecompletion indicator to Completed , and you can no longer make a confirmation correction.

You can correct a warehouse task that has already been confirmed in both the user interface and in the RF environment. EWM calculates the difference quantityand posts it.

For example, you have specified 11 pieces as the Act.Qty (Dest.) (destination actual quantity) and already confirmed the warehouse task. Younotice that you have made a mistake, and change the Act.Qty (Dest.) to 10 pieces. EWM automatically calculates the Dest.Diff.Qty (destinationdifference quantity) as 1 piece, and posts this. That is, EWM performs a type of stock adjustment regarding the relevant warehouse task.

For displaying the warehouse task in the user interface or in the RF environment, you can use the warehouse order, the stock identification, or the storage bin as aselection criterion.

Activities 1. If you want to make a confirmation correction using the user interface, on the SAP Easy Access screen choose Extended Warehouse Management

Execution Confirm Warehouse Task and then Correct the Confirmation . 2. EWM then does the following:

a. Checks whether serial numbers are mandatory for the products of the warehouse taskYou cannot correct the confirmation for products for which a serial number requirement exists.

b. Checks which authorizations you have c. Checks whether the warehouse task is locked d. Checks which inbound delivery belongs to the warehouse task (reference)

3. EWM reads the inbound delivery and checks that the completion status DCO of the inbound delivery does not yet have status value Completed . a. If the status does not yet have the status value Completed , EWM locks the inbound delivery from further warehouse activities until you have made your

confirmation correction. The fields for the confirmation correction entry are ready for input, and you can make your correction. b. If the status already has the status value Completed , none of the fields are ready for input, and you cannot make a confirmation correction.


Page 25 of 25

Documents

Goods Receipt