DOC2 - Storage Type Customizing - Control Parameters
DOC2 - Storage Type Customizing - Control Parameters
Purpose
The purpose of this page is to explain the fields from the storage tythe understanding of the system logic and requirements
in relation to.....
Overview
Storage type settings information.
Storage type
SPRO → Extended Warehouse Management → Master Data → Define Storage Type
1. General Controls
2. Putaway Control
3. Stock Removal Control
4. Goods Movement Control
5. Replenishment
The level of the available quantity can be at either storage bin level or the highest HU level.
Use
The stock removal strategies deal with the available quantity. If this is at storage bin level, the system creates
the warehouse task without reference to a HU, which means that the created warehouse task does not contain
a specific HU. You must enter the HU during confirmation. The warehouse employee can select any HU from
the given source storage bin.
If you have defined the available quantity at the highest HU level, then the source HU is determined as soon as
you create the warehouse task. The warehouse employee then needs to remove the product from this HU.
In all storage types in which you work with individual HUs, and in all work centers, you should define this level
at the highest HU level.
Example
The available quantity is specified in the storage types at storage bin level, and during warehouse task creation
no HU is specified from which the stock should be picked. This is the case, for example, in the bulk storage
area.
In staging areas, packing stations, deconsolidation stations, and counting stations, this should be set to the
highest HU level.
HU Requirement
General setting for whether handling units are mandatory in this storage type.
''
HUs are permitted in this storage type, but are not mandatory. Stock can be kept both in HUs, and also
directly in a storage bin.
'X'
All stock must be kept in HUs. Stock without HUs is not allowed in a storage bin.
'Y'
HUs are not allowed in this storage type.
Sets the maximum number of storage bins allowed per product in a storage type.
Use
The maximum number of storage bins allowed can also be specified on a product-specific basis in the product
master.
The maximum number of storage bins allowed is checked during warehouse task creation if you have set the
Check Maximum Number of Bins indicator in the destination storage type.
Use
If you set this indicator, an inspection always takes place, even if there is no "maximum number of storage bins
allowed" specified in the product master or destination storage type.
Use
A mixture of fixed storage bins and dynamic bins is not intended. In such a case, you can divide the intended
storage type into a storage type with fixed bins and a storage type with dynamic bins.
Set this indicator if you want to work with fixed bins in this storage type.
Do not set this indicator if you want to work with dynamic bins in this storage type.
Use
If you use fixed storage bins, you can use this checkbox to indicate whether you want to assign a fixed storage
bin to a product manually or have it assigned automatically during the first putaway of the product in the
storage bin. You have the following options:
To enable the automatic assignment of a fixed storage bin, deselect this checkbox.
To assign a fixed storage bin manually, select this checkbox. You can manually assign a fixed storage
bin on the SAP Easy Access screen under Extended Warehouse Management -> Master Data ->
Storage Bin -> Maintain Fixed Storage Bin.
Dependencies
To use this field, you must first select the Use Fixed Bins checkbox.
No Capacity Update
No update of capacity data and empty flag
Storage Behavior
The storage behavior specifies the general structure of the storage type. In particular this has an effect on the
replenishment bins for putaway.
Standard warehouse
The bins in the storage type do not have any special attributes.
Pallet warehouse
For one main bin, and depending on the HU type, several identical sub-bins are created during the first
putaway
Bulk storage
Use
If a handling unit or storage bin contains several batches, then you can manage the available quantity for all
batches individually, or generally without reference to a specific batch.
Depending how warehouse requests for batch materials normally arrive in your warehouse, and how you work
in the warehouse, you should make the appropriate settings.
If the available quantity is non-batch-specific, this means that the warehouse requests should also be non-
batch-specific. If you generally create warehouse requests for specific batches, then you should manage the
available quantity for specific batches.
For non-batch-specific available quantities, the warehouse task is also created as non-batch-specific, and you
need to enter the withdrawn batch when you confirm the warehouse task.
Dependencies
This setting is connected to the setting "Leve of Available Quantity".
NOTE:
If the available quantity is non-batch-specific, and the warehouse request is created for a specific batch, then
warehouse task creation cannot automatically determine the stock.
Use
The storage type determination pick uses quantity classification to determine the storage type in which the
product is stored in the optimal packaging unit. Quantity classification arises from the packing instruction,
according to each quantity required.
The operative unit of measure also arises from the packing instruction, by means of quantity classification.
Here, the system determines the quantity classification based on the customizing settings in the storage type,
or in the product master on storage type level. The operative unit of measure is displayed when executing the
transaction. If the setting round is set in the warehouse storage type, the system rounds the stock removal
quantity based on the operative unit of measure.
Example
The following quantity classifications are defined for a warehouse:
3 = tiers
4 = pallets
Use
External process steps are linked to internal storage process steps. You can assign multiple external
process steps to a storage process.
In the EWM Customizing activity Define process-oriented storage control , you can directly define a destination
location for a storage process step in relation to the source location.
Dependencies
If you have marked the field rule-based for the storage process steps Quality Inspection or Value-Added
Service, this requires an extra storage process step in your process-oriented storage control. This step must
contain the destination location.
For Quality Inspection, you must assign the storage process step to define the quality inspection work center
for an inspection rule. See SAP Easy Access Extended Warehouse Management --> Master Data --> Quality
Management --> Maintain Inspection Rule.
For Value-Added Service, assign the storage process step to determine the VAS work center of the packaging
specification. See SAP Easy Access Extended Warehouse Management --> Master Data --> Packaging
Specification --> Maintain Packaging Specification.
Example
Unload, Count, Deconsolidate, Put Away, Remove from Stock, Pack, Stage, Load.
For storage types in which this field is initial, the system updates the contents of the HU at the time of WT
confirmation in a separate table. This enables you to display all movements for a product - including
movements triggered through HU warehouse tasks - in the warehouse management monitor, by choosing
Documents --> All Movements for Product --> Display All Movements for a Product.
Dependencies
Note that logging the HU contents may mean that the confirmation process takes longer to complete. Logging
may be necessary for storage types in which inventory differences occur. This means that you may be required
to analyze all movements for a product.
Default Distance
Defines the average distance that a worker has to cover to reach a storage bin in a storage type.
Use
The default distance is used to calculate the travel distance for the first storage bin of a warehouse order,
providing you confirm this using the Confirm Warehouse Order (/SCWM/TO_CONF) function.
Since the system cannot determine when confirming on the desktop UI where the processor was at the time
when the warehouse order started, the default distance is added to the travel distances between the storage
bins of the warehouse order.
Dependencies
For warehouse orders that you execute using RF or confirm at a work center, the system does not take the
default distance into consideration.
The confirmation requirement always exists for the entire warehouse task. This means that if a stock removal
confirmation is required in the source storage type, or a putaway confirmation is required in the destination
storage type, the entire warehouse task is subject to confirmation. This means, among other things, that the
available quantity in the destination storage type is only updated once the confirmation has occurred.
Use
Only use this indicator for the storage type that should be the final putaway location for the product.
Dependencies
This indicator is evaluated in connection with process-oriented storage control.
Putaway Rules
Definition
The putaway rule specifies the logic that the system will use to find destination bins during putaway.
Use
Empty Bin
The system only searches for empty bins
Consolidation Group
A storage bin is firmly assigned to a consolidation group.
Use
This can be allowed or forbidden for the entire storage type, or controlled by product.
Goods Receipt Process - Strategies - Define Product Putaway Profile and assign it to the relevant
products.
In the product putaway profile, you should set the field Quant Addition to Stock AUoM in Storage Bin/HU to
Allowed – Manage in BUoM only.
You can use the product putaway profile to influence the mixed storage behavior for specific products during
additions to existing stock. The product is influenced by the putaway control indicator.
Activities
For the combination of warehouse number, putaway control indicator, and storage type, maintain the
following fields if you want to allow mixed storage:
Note
All attributes are also present in the storage type master. There they all have an additional attribute "Product
Decides".
The system only considers the relevant value from the product putaway profile if you have selected this
attribute in the storage type (see also: Define Storage Type).
If the storage section check is activated, the system will search for storage bins in storage areas defined in the
storage area check table. Also, in the case of manual entry of the storage area or the storage bin, the system
checks whether a putaway is allowed for this table.
You can use this attribute to control whether splitting is checked if a quantity to be put away only partly fits into
the destination storage bin.
The system considers the maximum storage type quantity if it is to be checked according to
Customizing for putaway
The system checks the weight, volume and capacity key figure according to the capacity check set in
the storage type
For each active check (maximum storage type quantity, weight, volume, capacity key figure), the system
determines the quantity that you can still put away. The smallest quantity results in the actual quantity added to
stock.
The system only performs a split if the possible quantity added to stock has a greater percentage share of the
maximum quantity in the bin than the addition threshold.
Restrictions:
Checking for splitting is only performed for putaway WTs and internal stock transfer WTs.
Checking for splitting is only performed for product WTs, not for HU WTs.
Product:
Only if the available capacity is greater than the Thrshld Addition does a split occur.
Putaway Storage Control
Defines how to create a warehouse task for a handlng unit. You specify whether the putaway is to be:
Evaluated dynamically based on the settings of the field Create Putaway WTs or HU Pick-WTs.
This is only valid in the case of process-oriented storage control. If you do not use process-oriented storage
control, the setting is made at warehouse process type level based on the field Select HU w/o Storage
Process.
Use
This field is evaluated by the system if you have marked the field Create Putaway WTs or HU Pick-WTs within
the Storage Process Definition - Assign Storage Process in Customizing for Define Process-Oriented
Storage Control.
Evaluated dynamically: The decision whether the putaway is performed with a HU WT or a product WT
depends on the Customizing in the storage type control. For more information, also see the
documentation for Create Putaway WTs or HU.
Putaway with product WT: The system creates a product WT for putaway.
Putaway with HU WT: The system performs the putaway with a HU WT, irrespective of the number of
putaway WTs for this HU. The values of the fields HU Requirement and Do not Put Away HUs are
not taken into account. The mixed storage check and the HU type check are executed.
Use
The destination storage data is determined generically. Here, you can configure what destination data
determination should determine from warehouse task creation:
Destination storage type, destination storage section, and destination storage bin
Example
For putaway in a packing station, the destination storage bin should not be determined during WT creation (WT
creation). Instead, it should be determined when the warehouse employee confirms the WT.
Use
Storing several different quants in a storage bin includes both products with different characteristics (for
example, different batches) and also completely different products.
" 2 " Several HUs with Different Batches of the Same Product
Several handling units can be stored in a storage bin simultaneously. However, the handling units
must contain the same product. If the product requires a batch number, you can store several batches
of the product in the bin.
Dependencies
For unpacked stocks, the bin is treated like a handling unit and as such is subject to the mixed storage settings
for handling units.
Use
Storage of several different quants in a handling unit in a storage bin includes materials with different
characteristics (for example different batches) and also completely different products.
" 2 " Several batches contain the same product per handling unit
Only one product can be contained in a handling unit. However, if this product requires a batch
number, then several batches of this product can be stored in the handling unit.
Dependencies
The settings in this field also apply to unpacked stocks in a bin. In other words, if mixed storage is allowed for a
bin but not for the handling unit in this storage type, then the mixed storage of unpacked stock is also not
allowed. You can only store different products in product-pure HUs.
Use
Use this indicator to find the correct date for a stock, if stocks with different dates should be mixed, or if you
want to avoid that stocks with different goods receipt dates are mixed.
Quant Addn to Stock Shelf Life Expir. Date Storage Bin/HU
Controls how a quant addition to stock is performed, with regards to different shelf life expiration dates.
Use
If you want to mix stocks with different shelf life expiration dates, or if you want to avoid mixing stocks with
different shelf life expiration dates, you use this indicator to determine the correct shelf life expiration date for a
stock.
Dependencies
Use this indicator to control how the system handles certificate numbers, if you store different certificate
numbers in the same bin or in the same handling unit.
The first AUoM is kept within the quant. All of the next movements to that particular quant are kept in
the base UoM and converted to this AUoM.
The AUoM data is lost when creating stock in the quant. The AUoM is set to BUoM.
1 Not Allowed
Use this setting to avoid losing AUoM data by storing a product with different AUoM on the same
quant. An error message informs the user that the mix check has failed.
Only one AUoM for the product is accepted for the quant, and stock in BUoM can be added to that
quant. But if a different AUoM is to be added, an error message is raised. Wiith this setting it is
possible to handle values such as 1.333 C06 in the bin or in the HU.
Use
All goods movements first go to this identification point. There the goods are identified, and the system creates
a HU warehouse task for the actual transfer to the current storage type.
You can configure the storage type or storage bin for the identification point using layout-oriented storage
process control.
Use
During stock removal, the product is placed into a pick-HU on the resource. When the stock removal
warehouse task (stock removal WT) is confirmed, the system automatically creates a subsequent WT from the
resource to the original destination storage bin. If you set this indicator, the system creates a product WT for
each pick-WT. If you do not set this indicator, the system creates a HU WT for the pick-HU. If you do not want
to allow putaway of pick-HUs, meaning that the pick-HU remains on the resource, then you should set this
indicator.
If you do not set this indicator, the product is put away anyway, even though the maximum storage type
quantity is exceeded.
Use
If you have set the Stor.Ctrl/Put.Compl. indicator, that is, you are working with final storage types, you also
have to set this indicator for these final storage types.
You can also set this indicator for other storage types. This makes the system delete the stock identification
before putaway from the respective stock has been completed.
For the cross-line stock putaway activity, you can define a bin sorting. The activity area must correspond to the
storage type
The empty bins are prioritized according to their closeness to a fixed bin.
Product decides
The setting for the search rule in the product decides the course of action.
Dependencies
This setting is relevant if addition to stock is permitted in the storage type, and the putaway rule supports
addition to existing stock.
The system automatically performs a capacity check for weight and volume as soon as a maximum weight or
volume is entered for the bin.
In some storage types, there is no danger of overloading (for example, in the goods receipt zone). You can
switch off the capacity check for all values here. In particular you should switch of the capacity check for
storage types that contain your work centers.
Use
Select this checkbox if you want to activate the early capacity check based on the storage bin type for putaway
warehouse tasks in the storage type.
If the capacity of a storage bin type is insufficient, the early capacity check is used to take bins of the storage
bin type from the destination bin search. This enables you to improve performance when working with a large
number of storage bins, since the system does not have to check each bin individually.
Use
Storage type search stock removal uses quantity classification to determine the storage type in which the
product is stored in the optimum packaging unit. The quantity classification here comes from the packaging
specification, depending on the requested quantity.
The operative unit of measure also comes from the packaging specification by way of the quantity
classification. Here, the system determines the quantity classification using the Customizing settings in the
storage type or in the product master at storage type level. The operative unit of measure is displayed when the
transaction is executed. If Rounding has been set in the warehouse process type, the system uses the
operative unit of measure to round the stock removal quantity.
Example
The following quantity classifications are defined for a warehouse:
2 = Cartons
3 = Locations
4 = Pallets
In WPT,
Mixed Stock Types for the Same Product
Controls whether a product in a bin or HU is allowed to be of more than one stock type. If the field is blank,
different stock types are allowed. If it is selected, the product or batch can only exist in one stock type.
Dependencies
If the available quantity level for the storage type is set to Storage Bin, then this field is completely independent
from other storage type settings. However, if the available quantity level is set to Highest-Level HU, the
following dependencies exist:
Mixed Storage must be set either to 1 - Several Non-Mixed HUs with the Same Product/Batch or to 2 -
Several HUs with Different Batches of the Same Product.
Mixed Storage in HU must also be set either to 1 - Several Non-Mixed HUs with the Same
Product/Batch or to 2 - Several HUs with Different Batches of the Same Product.
Dependencies
If the available quantity level for the storage type is set to Storage Bin, then this field is completely independent
from other storage type settings. However, if the available quantity level is set to Highest-Level HU, the
following dependencies exist:
Mixed Storage must be set either to 1 - Several Non-Mixed HUs with the Same Product/Batch or to 2 -
Several HUs with Different Batches of the Same Product.
Mixed Storage in HU must also be set either to 1 - Several Non-Mixed HUs with the Same
Product/Batch or to 2 - Several HUs with Different Batches of the Same Product.
Indicator: Confirmation of Stock Removal Required
Means that if there is a stock removal from this storage type, the warehouse task must be confirmed.
The confirmation requirement always exists for the entire warehouse task. This means that if a stock removal
confirmation is required in the source storage type, or a putaway confirmation is required in the destination
storage type, the entire warehouse task is subject to confirmation. This means, among other things, that the
available quantity in the destination storage type is only updated once the confirmation has occurred.
Use
Set this indicator if, for the stock removal strategy, you also want to consider stock in resources that you
included in this storage type as the last stock.
Dependencies
The storage type in which the resource last included stock is marked in the resource data object.
Example
In a high rack storage area with a connected pick point, stock that is currently in a resource in a HU and on its
way to the pick point, must also be considered.
The available quantity can be negative. Here, you can only create WTs without an actual stock. You
cannot confirm a warehouse task where the stock would become negative.
'space':
On the confirmation screen, the first pick-HU assigned to the warehouse task is proposed as the
destination handling unit and the HU copy indicator is set. In this way, the source handling unit is
copied as the lower-level handling unit into the pick-HU.
'1':
On the confirmation screen, the issuing handling unit is proposed as the destination handling unit
during confirmation of the WT and the HU copy indicator is set.
'2':
The storage process decides whether the handling unit is proposed as the destination handling unit.
'3':
On the confirmation screen, the first pick-HU assigned to the WT is proposed as the destination
handling unit. The HU copy indicator is not set. You should use this option only if the product or the
lower-level handling units are to be picked from the issuing handling unit. If the issuing handling unit is
nested, you must enter the lower-level handling units during confirmation.
Irrespective of the current value of the indicator, the proposals for the destination handling unit and the HU
copy indicator can be overwritten by the user on the confirmation screen
Use
All goods movements from this storage run are processed using a pick point. The requested product can be
removed from the handling unit (HU) and repacked into another HU. The removed HU can then be transferred
back into the return transfer storage type/bin entered for the work center. If the work center does not have a
return transfer storage type/ bin, the system determines the destination storage data for the removed HU using
the putaway strategies.
You can configure the pick point using layout-oriented storage control.
Use
If no stock exists in pick storage types, and no fixed bins exist either, the approximate source data
determination does not usually consider this storage type, and continues looking in the next storage type of the
search sequence that has been set.
You use this indicator to specify that the storage type (without storage bin) is written to the source data of a
delivery item, even if there is no stock for the product in the storage type.
This enables you to use the order-related replenishment to perform replenishment for the pick storage type,
since a requirement for picking occurs in this storage type as a result of this.
Use
You can configure how the WT quantity should be rounded. You can do this at storage type level and in the
warehouse process type.
For each level of a packaging specification, you can assign a quantity classifier for the warehouse.
Different packaging specifications can have the same quantity classifier.
A storage type can have an assigned quantity classifier for the warehouse, which would then be valid
for all products in this storage type.
For each product, you can assign a quantity classifier for the warehouse in the product master, which
then overrides the setting described above.
Process: If a WT was created and you have switched on rounding, the system checks the quantity classifier for
the warehouse at storage type level, and/or in the product master. The system searches for a match in the
packaging specification and rounds the WT quantity according to the unit of measure at the found packaging
specification level.
Example
What do you have to do to always get WTs with a quantity of 1 for a product? Here, we assume that the
product is stored in special storage types.
1. In level 1 of the packaging specification for the product, the quantity classifier for the warehouse 'ST'
is entered. The packaging specification at level 1 has a quantity of 1.
2. The storage type also has the quantity classifier 'ST' assigned for the warehouse.
3. In the storage type where the product is stored, rounding is switched on with the value 'Round Down
to Single Units'.
If a request now exists with a quantity of 10, the rounding logic would round the WT quantity down to 1. The
system would create 10 WTs, each with a quantity of 1, instead of one WT with a quantity 10.
Other example:
In bulk storage, you do not normally want to manage partial pallets. Partial pallets should be picked from a
special partial pallet storage area. The following example should clarify the effects this switch can have on
system behavior.
The requested quantity is 2.5 pallets. The quantity in the bin is 5 pallets:
Rounding up:
Causes a removal of 3 pallets
Round down to a multiple:
Causes a removal of 2 pallets. For the remaining half pallet, the system determines suitable stock
using the storage type search.
Availability Group
In Extended Warehouse Management (EWM), it enables the grouping of stock types according to APO
availability.
Use
The availability group is only used in Customizing for EWM. It is assigned the following objects:
When the system defines the stock type of a delivery, it uses the availability group of the warehouse process
type and not the availability group of the storage type. As a prerequisite for this, you have assigned the
warehouse process type of the delivery to an availability group.
The availability group is also used for communication with the Enterprise Resource Planning (ERP) system.
The availability group is assigned to an ERP storage location. In this way, the system can find an ERP stock
type for every EWM stock type and a specific storage location for each stock type.
Example
You assign a storage type for the goods receipt zone (GR zone) for the availability group 001. The stock type
F1 and ERP storage location 0001 are designated for the availability group 001 in EWM.
Upon receipt of a product of stock type F1 in the GR zone, a goods receipt is posted in the ERP system in the
unrestricted-use stock of storage location 0001.
You assign the storage type for the final putaway to availability group 002. The stock type F2 and storage
location 0002 are designated for the availability group 002.
When confirming the putaway transfer order to the final storage bin, EWM automatically transfers the quantity
from F1 to F2. In this way, the ERP system transfers the quantity from storage location 0001 to storage location
0002.
Use
If you put away a stock quantity with a stock type from a different availability group into the storage type, the
system automatically performs a posting change for the quantity into the relevant stock type of the mandatory
availability group, during warehouse task confirmation.
Example
See also Availability Group.
Use
If you put away a stock quantity with a stock type from a different availability group into the storage type, the
system automatically performs a posting change for the quantity into the relevant stock type of the mandatory
availability group, during warehouse task confirmation.
Example
See also Availability Group.
Use
The location-independent stock type is assigned in Customizing for Extended Warehouse Management (EWM)
to an EWM stock type, and is used for the following functions:
Determining the subsequent stock type for a transfer between two storage types that belong to
different availability groups.
(See also: Availability Group for Putaway)
Mapping between EWM stock type and ERP stock type
Dependencies
The location-independent stock type points uniquely to one stock type in the SAP ERP system:
The SAP ERP system only recognizes the above stock types. You can define other location-independent stock
types in EWM, if you do not need to communicate them to the ERP system.
Use
This indicator controls the relevane for creating a warehouse task during a posting change. The following
settings are possible:
For the setting 'Posting Change Always in Storage Bin', no warehouse task is created. For the setting 'No
Posting Change in Storage Bin' a transfer order is created. If warehouse task creation is dependent on mixed
storage, then a warehouse task is created if the posting change will cause mixed storage in the storage bin or
the HU, which is not permitted in this storage type.
Dependencies
Mixed storage in the storage type.
Replenishment Level
Specifies whether the replenishment in this storage type is requested at storage bin level (fixed bin storage
only) or at storage type level.
Use
In fixed bin storage areas in which you want to request replenishment for each fixed bin, use the replenishment
level "Foxed Bin". In fixed bin storage areas in which you want to view the entire stock across all fixed bins, or
in storage types without fixed bins, use the replenishment level "Storage Type".
Use
During replenishment from this storage type, you can use this field to specify whether creating a warehouse
task with a minimum quantity causes the warehouse order to be completed.
Use
If you select this checkbox, the system ends warehouse task creation when the warehouse task (WT) quantity
reaches the tolerance level, so no more WTs are created for a partial quantity of a handling unit. You can use
this to prevent the system from creating further replenishment WTs after a WT has been created over a
sufficient quantity. This is useful if it is more important to you that the system replenishes a whole handling unit
and does not create partial quantities in the reserve area, than that the original planned replenishment quantity
is maintained.
Dependencies
If you select this checkbox, you must also enter a value in the Tolerance field.
Related Content
Related Documents
SAP Help - Storage Type
Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.