9/2/2022

SAP Extended Warehouse Management

(SAP EWM)
Generated on: 2022-09-02 12:31:08 GMT+0000

SAP Extended Warehouse Management (SAP EWM) | 9.5 FP02

PUBLIC

Original content:
https://help.sap.com/docs/SAP_EXTENDED_WAREHOUSE_MANAGEMENT/3d97bec9bf1649099384bb8167df3cf2?locale=en-
US&state=PRODUCTION&version=9.5.0.2

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 9/2/2022

SAP Extended Warehouse Management (SAP EWM)

Use
Extended Warehouse Management (EWM) offers you exible, automated support for processing various goods movements and
for managing stocks in your warehouse complex. The system supports planned and efficient processing of all logistics processes
in your warehouse.

Introductory Notes

If you manage your warehouse stocks using the application component Inventory Management (MM-IM), you manage the
quantities and values of stocks in several storage locations.

In contrast, EWM gives you the option of mapping your entire warehouse complex in detail in the system, down to storage bin
level. Not only does this give you an overview of the total quantity of a product in the warehouse, but you can also always see
exactly where a speci c product is, at any time, in your warehouse complex. With EWM, you can optimize the use of various
storage bins and stock movements, and can store together stocks from several plants in randomly-managed warehouse. Using
EWM, you can control and optimize various processes in the warehouse.

Integration
EWM is completely integrated into Inventory Management and Delivery Processing. Business processes, which you trigger in
other application components, lead to physical goods movements in your warehouse. You organize, control, and monitor these
goods movements using EWM.

Features
Storage Bin Management and Optimization

You map the entirety of your storage facilities in EWM. You can set up different storage facilities such as automatic warehouses,
high-rack storage areas, bulk storage areas, or xed bin warehouses, in various storage types, according to your requirements.

You manage the stocks at storage bin level. You can de ne these storage bins according to your own requirements. Every
storage bin in your warehouse is mapped in the system. This enables you to constantly track all stock movements in detail. You
can see exactly where a speci c product is located in your warehouse. You can also use EWM to optimize storage bin
management, since EWM takes on a large part of optimizing the products, so that each product is assigned to the correct
storage bin, depending on its size and frequency of access.

Inventory Management and EWM are fully integrated. Using the physical inventory procedures and the entry of stock
differences, the system ensures that the book inventory balance in Inventory Management always matches the warehouse
stock in EWM.

Goods Movements

You process all goods movements that affect your warehouse using EWM, such as goods receipts, goods issues, stock transfers,
and automatic replenishment. These movements can include goods receipts, goods issues, stock transfers, automatic
replenishment, management of dangerous goods, layout-oriented and process-oriented storage control, effective work
preparation using automatic wave pick creation, resource optimization using rule-based bundling of warehouse tasks, or
processing of inventory differences in your warehouse.

EWM optimizes warehouse capacities and material ows using putaway and stock removal strategies that you can adjust to
your needs, or by you using handling units.

This is custom documentation. For more information, please visit the SAP Help Portal 2
 9/2/2022
Work Center

You can use the work center to map a physical unit in the warehouse, which you use to carry out warehouse activities such as
packing, deconsolidation, weighing, quality inspections, and counting. You can personalize each work center, so that each user
sees exactly those elds, data, and tab pages that are necessary for their work.

Physical Inventory

You use physical inventory to regularly perform a physical stock take in your warehouse. You compare the actual, existing,
physical, stock with the data managed in EWM. By entering physical inventory differences, you update the accounting data for
the stock, according to the results of the physical stock take. If you have performed physical inventory at least once in a scal
year for each storage bin/each product, the physical inventory is classed as complete.

If you use EWM, the physical inventory is performed at Warehouse Management level. You can perform a physical inventory
based on products and/or based on storage bins. There is a difference monitor available, with con gurable tolerance groups,
which you can use to de ne maximum values for posting differences for each user. In addition, the system supports automatic
posting according to time intervals, different priorities for each individual inventory procedure, a zero stock check, and a low
stock check. The radio frequency functions are integrated into the physical inventory and support you when you perform the
different physical inventory procedures, such as cycle counting, physical inventory during putaway, and physical inventory using
zero stock check. Handling units are fully integrated into the physical inventory process.

Planning and Monitoring

EWM gives you an overview of all goods movements and warehouse stocks. The system supports you in planning, monitoring,
and optimizing work processes. For example, it gives you a preview of the workloads for the coming days, or enables you to take
preventive action in critical warehouse processes, so that you can perform stock movements on time. The extensive monitoring
functions give you a current view of all activities in the warehouse. You can control the actual work in the warehouse using the
individual monitors.

Radio Frequency Connection

To structure the work in the warehouse efficiently and cost-effectively, you control the warehouse workers' work steps clearly
and simply via mobile radio-frequency terminals.

The radio frequency connection (RF connection) to mobile data entry achieves fast and accurate data transfer. The RF devices
receive data directly from the SAP system and transfer data back to the system. You can enter and verify information using bar
codes. This means that you ensure a high standard of quality in your warehouse.

Warehouse Control

EWM also contains an interface to external systems (warehouse control units). This enables you to integrate automated
putaway and stock removal systems, or forklift control systems for all stock movements using this Application Link Enabling
interface (ALE interface) in the warehouse management system.

What's New in SAP Extended Warehouse Management 9.5

Here are the release notes for SAP Extended Warehouse Management 9.5.

What's New in SAP Extended Warehouse Management 9.5 SP00

Here are the release notes for SAP Extended Warehouse Management 9.5 SP00.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 9/2/2022

Labor Management

Shift Management
This feature enables you to plan employee work schedules by de ning shifts and shift sequences centrally, which helps you to
reduce the effort required to determine employee capacity.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-LM

Availability SAP Extended Warehouse Management 9.5

Additional Details
You use shifts to de ne start and end working times for processors working together in a warehouse. You can assign breaks and
a shift factor to shifts, to reduce the productive working time of a shift. Therefore, you can use shifts to determine the
productive labor capacity at a certain point of time in your warehouse. You use shift sequences to de ne a shift order for as
many consecutive days as you want. Shift sequences repeat in cycles, for example, every 5 days for a 5-day shift sequence.

You can also determine the labor performance of shifts if you activated Labor Management. For example, when a processor
con rms a warehouse task, the system records the processor's shift in the executed workload record for future labor
performance evaluation.

Effects on Customizing
You have con gured shift management in Customizing for Extended Warehouse Management under Labor
Management Shift Management :

De ne Capacity Variants

Maintain Shift Management Defaults

Maintain Tolerance Limits for Shift Determination

If you want to have your own criteria for how the system determines the shift a worker is assigned to when the system
records the executed workload, use BAdI: Shift Determination for Executed Workload in Customizing for Extended
Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Labor
Management Shift Management .

See Also
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Labor Management (LM) Master Data in Labor Management Shift Management .

Time and Attendance

This is custom documentation. For more information, please visit the SAP Help Portal 4
 9/2/2022
This feature enables you to store time events (clock-in and clock-out) in SAP Extended Warehouse Management (SAP EWM).
These time events can be copies from an external time and attendance system.

You can work with the time events in SAP EWM in the following ways:

Use the application programming interface for time and attendance to upload time events from an external system to
SAP EWM

Display and maintain time events manually in SAP EWM

Upload time events from CSV les

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-LM

Availability SAP Extended Warehouse Management 9.5

See Also
For more information about time and attendance, see http://help.sap.com/ewm under Application Help SAP Extended
Warehouse Management (SAP EWM) Labor Management (LM) Execution Time and Attendance .

Enhancements to Processors
With this enhancement, you can perform the following actions:

Classify processors

Assign processors to group hierarchies

Perform mass changes to processors using the warehouse management monitor

Create processors by using CSV les

Using processors is mandatory when using Labor Management in SAP Extended Warehouse Management (SAP EWM). You use
processors to map your employees in the warehouse. You create your employees as processors using the SAP Business Partner,
and de ne master data for the processor.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-LM

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing

This is custom documentation. For more information, please visit the SAP Help Portal 5
 9/2/2022
You de ne processor types in Customizing for Extended Warehouse Management under Labor
Management Processors De ne Processor Types

You de ne reporting groups for processors in Customizing for Extended Warehouse Management under Labor
Management Processors De ne Reporting Groups for Processors

You de ne work categories in Customizing for Extended Warehouse Management under Labor
Management Processors De ne Work Categories

See Also
For more information about processors, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse
Management Labor Management Master Data in Labor Management (LM) Processor .

Mask Processor in Labor Management Reporting

With this feature, you can mask processor details in the following user interfaces and labor management reporting and analysis
tools:

Con rmed warehouse tasks

Value-added services

Indirect labor tasks

Warehouse management monitor

Executed Workload Analysis transaction

Standard Time Simulation transaction

This can be necessary in countries where you are not allowed to evaluate the performance of an individual employee.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-LM

Availability SAP Extended Warehouse Management 9.5

See Also
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Labor Management (LM) Reporting and Analysis Tools Masking of Processor Details .

Performance Evaluation
This feature enables you to report on the efficiency and utilization of individual employees, groups, or shifts in your warehouse.

The executed workload (EWL) re ects the work done in your warehouse, that is, it describes who did what and when. EWLs are
created automatically by the system or you can create an EWL manually. You can use the EWLs to report on the efficiency and

This is custom documentation. For more information, please visit the SAP Help Portal 6
 9/2/2022
utilization of your employees. You can also create employee performance documents and transfer them to your Human Capital
Management system.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SAP-EWM-LM

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing
The following Business Add-Ins (BAdIs) are available for executed workloads in Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Labor Management Workload :

BAdI: Determination of Processor Group for Executed Workload

BAdI: Addition of Custom Fields to Executed Workload

BAdI: Enrichment of Executed Workload for Custom Processes

BAdI: Enrichment of Contexts for Executed Workload Determinations

BAdI: Checking Completion of Executed Workload Record

Calculation of Standard Time

With this feature, you can calculate the standard time it should take to perform a task in the warehouse. The standard time
includes allowances for real-life conditions such as fatigue. You can compare the standard time with the actual duration to
evaluate the performance of processors.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-LM

Availability SAP Extended Warehouse Management 9.5

Additional Details
The standard time is calculated in four steps. Steps 1 and 2 are optional. Step 3 is mandatory. Step 4 is mandatory for
calculating standard time, but you do not need to perform it if you only want to calculate normal time.

1. The labor activity is determined. A labor activity is a new classi cation of work that allows you to de ne highly speci c
tasks, such as case picking and pallet picking.

2. The travel time is calculated, based on the travel network.

3. The system analyzes the de nitions of engineered labor standards to determine the normal time to perform a task.

This is custom documentation. For more information, please visit the SAP Help Portal 7
 9/2/2022
4. The system calculates the personal needs, fatigue, and unavoidable delay (PFD) factor and multiplies this by the normal
time to give the standard time.

Effects on Customizing
To calculate the standard time for labor activities, you need to make settings in all or some of the following activities in
Customizing for Extended Warehouse Management:

Extended Warehouse Management Labor Management Activate Labor Management

Extended Warehouse Management Labor Management Assign Application and Function to Decision Service Context

Extended Warehouse Management Labor Management Labor Activities De ne Labor Activity Groups

Extended Warehouse Management Labor Management Labor Activities De ne Evaluation Types

Extended Warehouse Management Labor Management Labor Activities De ne Labor Activities

Business Add-Ins (BAdIs) are available in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs)
for Extended Warehouse Management and then the following nodes:

Labor Management Labor Activity Determination

Cross-Process Settings Travel Distance Calculation Travel Time Calculation

Labor Management Standardized Standard Time Determination

Labor Management Personal Needs, Fatigue, and Unavoidable Delays

See Also
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Labor Management (LM) Labor Activities and Duration .

Validation and Reconciliation of the Standard Time Calculation

This feature enables you to analyze how the standard time has been calculated. You can compare the standard time with the
actual duration for each executed workload or in an aggregated view. You can display detailed logs that describe how the
standard time has been calculated.

If you nd that the calculation is not correct, you can change the rules you de ned, validate the new rules, and adjust the
standard times of executed workloads that have already been created, so they correspond to your new rules.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-LM

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing

This is custom documentation. For more information, please visit the SAP Help Portal 8
 9/2/2022
In Customizing for Extended Warehouse Management, you need to select that you are using BRFplus for your engineered labor
standards (ELS), under Labor Management Activate Labor Management .

See Also
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Labor Management (LM) Reporting and Analysis Tools .

Change SAP ERP Delivery After Replication to SAP EWM

This feature enables you to change an outbound delivery in SAP ERP after it has already been replicated to SAP Extended
Warehouse Management (SAP EWM). If you open an SAP ERP outbound delivery in edit-mode, the system checks which elds
you can change without harming the process in SAP EWM.

Fields that are not related to SAP EWM are changeable according to the standard rules in SAP ERP.

You can change SAP EWM-related details depending on the processing status in SAP EWM. For example:

You can change details such as the quantity or batch up until a warehouse task is created.

You can change the means of transport up until the transportation unit is created.

You can change texts up until the outbound delivery is created.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-DLP

Availability SAP Extended Warehouse Management 9.5

Additional Details
To be able to use this feature, you must be connected to an SAP S/4HANA system that is running SAP S/4HANA 1709 or higher.

Effects on Customizing
You enable delivery changes in Customizing for Logistics Execution under Logistics Execution Extended Warehouse
Management Integration Basic Setup of Connectivity Con gure SAP EWM-Speci c Parameters .

The following Business Add-Ins (BAdIs) are available in Customizing for Extended Warehouse Management under Business Add-
Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration :

Inbound Messages from ERP System to EWM BAdI: Receipt of Outbound Delivery Change

Delivery Processing BAdI: Modify Change Behavior of Original Delivery

See Also

This is custom documentation. For more information, please visit the SAP Help Portal 9
 9/2/2022
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Delivery Processing Communication from EWM to SAP ERP Processing of Outbound Deliveries .

Order Reduction
With this feature, you can reduce the quantity of a sales order even after SAP Extended Warehouse Management (SAP EWM)
has created warehouse tasks for the corresponding outbound delivery order. When you save your updated sales order, SAP
EWM is informed of the quantity reduction and reacts in the following way:

If the warehouse tasks have not yet been con rmed, SAP EWM cancels the warehouse tasks and changes the quantity of
the outbound delivery order.

If the warehouse task of picking has already been con rmed, the stock is updated. Stock marked for order reduction can
be identi ed by the corresponding checkbox. At the work center, the worker is informed when packing. The stock item
loses the reference to the outbound delivery order and the quantity of the outbound delivery order item is reduced.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-DLP

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing
To activate order reduction on warehouse number level, make the following settings for the item type in Customizing for
Extended Warehouse Management:

Allow order reduction in Customizing for Extended Warehouse Management under Cross-Process Settings Warehouse
Task De ne Warehouse Process Type .

De ne quantity offsetting pro les in Customizing for Extended Warehouse Management under Cross-Process
Settings Delivery - Warehouse Request Quantity Offsetting De ne Quantity Offsetting Pro les .

De ne status pro les in Customizing for Extended Warehouse Management under Cross-Process Settings Delivery -
Warehouse Request Status Management De ne Status Pro les .

Optional: De ne date pro les in Customizing for Extended Warehouse Management under Cross-Process Settings
Delivery - Warehouse Request Dates/Times De ne Date Pro les .

Optional: De ne document types in Customizing for Extended Warehouse Management under Goods Issue
Process Outbound Delivery De ne Document Types for Outbound Delivery Process .

The following Business Add-Ins (BAdIs) are available in Customizing for Extended Warehouse Management under Business Add-
Ins (BAdIs) for Extended Warehouse Management:

Interfaces ERP Integration Delivery Processing BAdI: Prediction Service for Order Reduction

Goods Issue Process Outbound Delivery BAdI: Sorting of Warehouse Tasks for Partial Cancellations

See Also

This is custom documentation. For more information, please visit the SAP Help Portal 10
 9/2/2022
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Delivery Processing Communication from EWM to SAP ERP Processing of Outbound Deliveries Order Reduction .

Pick by Cart
With this app, you can pick multiple orders with a pick cart in a single trip through the warehouse. This app helps to improve
customer satisfaction in the following ways:

Improves picking efficiency

Reduces human errors

Reduces the cost of warehouse operations

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-WOP-PCK

Availability SAP Extended Warehouse Management 9.5

Additional Details
The key features of this app are as follows:

Pick multiple orders in a single trip

Graphically display handling units (HUs) and their logical positions on a pick cart

Employ intuitive Fiori user interface

Provide up-to-date picking relevant information

Support scanning

Pick serial-number managed products

The process of this app contains the following steps:

In the preparation step, you put pick-HUs in the logical positions of a pick cart for the subsequent pick and unloading
tasks.

In the pick step, you pick products for destination HUs. A pick step contains pick tasks grouped together for picking
products with the same attributes, for example, the same source bin.

In the unloading step, you unload HUs at their destinations. An unloading step can contain several HUs grouped together
because of the same destination bin.

Effects on Customizing
You select the Layout Type eld for your resource type in Customizing for Extended Warehouse Management under Cross-
Process Settings Resource Management De ne Resource Types .
You de ne layout types in Customizing for Extended Warehouse Management under Cross-Process Settings Resource
Management De ne Layout Types .

This is custom documentation. For more information, please visit the SAP Help Portal 11
 9/2/2022

See Also
For more information, see https://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Goods Issue Stock Removal Picking Apps for Picking Pick by Cart .

Outbound Delivery Order Query

This feature enables you to perform the warehouse outbound operational analysis to determine the number, volume, and
weight of the outbound delivery order items. You can group outbound delivery order items by day, week, and month to, for
example:

Fine-tune the shift schedule.

Optimize and balance the number of workers.

Request a budget for equipment.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-DLP

Availability SAP Extended Warehouse Management 9.5

Additional Details
You can use this feature for the following outbound operational analysis :

Workload and execution progress

Operation alerts for overdue goods issue

Operation quality

Effects on Data Transfer

You use the Redundant Header and Item Data for Outbound Delivery Order (/SCDL/ODO_CDS_RED_UPD) report to write
redundant header and item data for outbound delivery orders into the databases for the orders that you created before the
system upgrade.

Effects on Customizing
You write redundant header and item data for inbound deliveries and outbound delivery orders in Customizing for Extended
Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process
Settings Delivery - Warehouse Request BAdI: Writing Redundant Header and Item Data for Deliveries .

See Also
For more information, see https://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Analytics Core Data Services Outbound Delivery Order Query

This is custom documentation. For more information, please visit the SAP Help Portal 12
 9/2/2022

Combined Picking Using Radio Frequency

This feature enables you to perform picking more efficiently using radio frequency devices in the following ways:

To perform combined picking from bulk storage areas

To split the combined quantities with exception codes

To verify and enter serial numbers collectively for products of combined warehouse tasks

To see the combination group of warehouse tasks in the warehouse management monitor

To calculate the adjusted planned duration of executed workload based on the combined picking

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-RF

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing
You select the Serial Number checkbox to indicate that the products in the combined warehouse tasks are serial-number
managed in Customizing for Extended Warehouse Management under Mobile Data Entry De ne Combined Picking Pro le .

See Also
For more information, see https://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Radio Frequency Framework Work Processing Using Radio Frequency Picking Combined Picking Using Radio
Frequency .

Process E-Commerce Returns

With this app, you can process the returned products more efficiently in the following ways:

Using process-oriented storage control to perform other tasks, for example, packing, before the follow-up tasks, for
example, putaway, that are triggered for the returned products.

Quickly interacting with the system by scanning or entering access codes, for example, to increase product quantities
and choose conditions and return reasons for returned products

Managing handling units (HUs), for example, printing HU labels and creating or moving HUs

Scanning product barcodes using the GS1-128 format

Using additional International Article Number (EAN) and Global Trade Item Number (GTIN)

Scanning serial-number managed products

Technical Details

This is custom documentation. For more information, please visit the SAP Help Portal 13
 9/2/2022
Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-IF

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing
You de ne application codes in Customizing for Extended Warehouse Management under Cross-Process
Settings Access Codes Basics De ne Application Codes .

You de ne business contexts in Customizing for Extended Warehouse Management under Cross-Process
Settings Access Codes Basics De ne Business Contexts .

You de ne semantic elds in Customizing for Extended Warehouse Management under Cross-Process Settings Access
Codes Basics De ne Semantic Fields .

You de ne business steps in Customizing for Extended Warehouse Management under Cross-Process Settings Access
Codes Basics De ne Business Steps .

You de ne internal access codes in Customizing for Extended Warehouse Management under Cross-Process
Settings Access Codes Basics De ne Internal Access Codes for Applications .

You de ne an external access code in Customizing for Extended Warehouse Management under Cross-Process
Settings Access Codes De ne External Access Codes .

See Also
For more information, see https://help.sap.com/viewer/p/SAP_FIORI under More SAP Fiori Products for SAP Business
Suite SAP Fiori 1.0 for SAP Extended Warehouse Management Process E-Commerce Returns .

Enhancements to the Travel Distance Calculation

This feature enables you to better set up the travel distance calculation:

There is a plausibility check when you de ne the travel network. The system alerts you if, for example, edges are close
together but not connected.

You can upload and download the travel network to and from SAP Extended Warehouse Management (SAP EWM).
Therefore, if you already have the information about the travel network in another system, you can upload this network
to SAP EWM.

You can simulate the travel distance and travel time calculation. You can enter a source bin, a destination bin, and a
resource. The system shows you in detail how the travel distance and travel time have been calculated.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-MD-WL-TDC

Availability SAP Extended Warehouse Management 9.5

This is custom documentation. For more information, please visit the SAP Help Portal 14
 9/2/2022

See Also
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Travel Distance Calculation .

Package Building
This feature enables you to create planned shipping HUs (PSHUs) using the same algorithm that SAP Transportation
Management uses to create freight units. This algorithm does not replace the existing cartonization algorithm, but it provides
more features. The package building algorithm works as follows:

The system rst tries to create full pallets of a single product.

If a quantity remains, the system creates mixed pallets where each layer consists of a single product.

If the system cannot create layers of one product, it creates mixed layers.

The system takes into account the weight, height, and volume of the products.

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM-CAP

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing
Determine the process pro les for cartonization planning in Customizing for Extended Warehouse Management under
Goods Issue Process Cartonization Planning :

De ne Process Pro les for Cartonization Planning

Determine Process Pro les for Cartonization Planning

De ne a package building pro le in Customizing for Extended Warehouse Management under Goods Issue
Process Cartonization Planning Package Building .

Determine the algorithm pro les for cartonization planning in Customizing for Extended Warehouse Management under
Goods Issue Process Cartonization Planning :

De ne Algorithm Pro les for Cartonization Planning

De ne Access Sequence of Algorithm Pro les

See Also
For more information, see http://help.sap.com/ewm under Application Help SAP Extended Warehouse Management (SAP
EWM) Goods Issue Cartonization Planning Con guring Package Building .

General Enhancements
This is custom documentation. For more information, please visit the SAP Help Portal 15
 9/2/2022
These features enable you to do the following:

Create an outbound delivery order directly, skipping the step of creating an outbound delivery request. This is also
possible for the inbound process and posting changes.

Perform stock consolidation on partial quantities of products to create complete quantities, for example, building full
pallets.

Integrate cancel picking into your own UIs, for example, in the case of an order reduction, using the new API
/SCWM/IF_API_CANCEL_PICKING.

Create immediately con rmed warehouse orders even if Labor Management is active in a warehouse.

The system can then determine the actual duration of an immediately con rmed warehouse order, based on the end
time of the previous warehouse order.

Group warehouse tasks of existing warehouse orders into a new warehouse order to be processed next by a resource.

This feature can help you to optimize resource capacity, for example, by moving two handling units with a single
movement.

In Labor Management, the Customizing activity De ne Activities has been renamed to Assign External Process Step to
Warehouse Activity.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM

Availability SAP Extended Warehouse Management 9.5

Effects on Customizing
You allow the system to create immediately con rmed warehouse orders even if Labor Management is active in a
warehouse in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended
Warehouse Management Labor Management Workload BAdI: Immediate Con rmation of WOs with Labor
Management .

You group warehouse tasks of existing warehouse orders into a new warehouse order to be processed next by a resource
in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse
Management Mobile Data Entry Flow Processing of RF Framework BAdI: Resource-Based Warehouse Order
Optimization .

The following Business Add-Ins (BAdIs) are available for stock consolidation in Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Internal Warehouse
Processes Warehouse Optimization Stock Consolidation :

BAdI: In uencing Process Steps in Stock Consolidation

BAdI: Data Selection in Stock Consolidation

BAdI: Calculation of Proposal for Stock Consolidation

See Also

This is custom documentation. For more information, please visit the SAP Help Portal 16
 9/2/2022
For more information about stock consolidation, see http://help.sap.com/ewm, under Application Help SAP Extended
Warehouse Management (SAP EWM) Warehouse Task Ad Hoc Movement Stock Consolidation .

For more information about order reduction, see http://help.sap.com/ewm, under Application Help SAP Extended Warehouse
Management (SAP EWM) Delivery Processing Communication from EWM to SAP ERP Processing of Outbound
Deliveries Order Reduction .

What's New in SAP Extended Warehouse Management 9.5 FP02

Here are the release notes for SAP Extended Warehouse Management 9.5 FP02.

Enhancement to Plant-Speci c Batch Handling

This feature enables SAP Extended Warehouse Management to support plant speci c-batch handling introduced with SAP
S/4HANA Cloud 1802 as described in SAP Note 2564190 .

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-MD

Availability SAP Extended Warehouse Management 9.5 FP02

Effects on Customizing
To enable this feature, see SAP Note 2604990 .

See Also
For more information about batch management, see http://help.sap.com/ewm under Application Help SAP Extended
Warehouse Management (SAP EWM) Batch Management .

Enhancements to Q-Inspection Product/Batch Whse-Internal

(IOT 5)
With this feature, you can create inspection rules for inspection object type (IOT) Q-Inspection Product/Batch Whse-Internal
(IOT 5) that are speci cally for recurring inspections and internal stock inspections so as to distinguish between these
inspection processes.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-QM

This is custom documentation. For more information, please visit the SAP Help Portal 17
 9/2/2022
Availability SAP Extended Warehouse Management 9.5 FP02

Enhancements to the Recording of Partial Inspection Decisions

With this feature, you can do the following while recording partial inspection decisions for the partial quantities of an inspection
lot:

You can repack the partial quantity into a new destination handling unit.

You can record a quantity difference using an exception code.

If recording a partial inspection decision for a serialized material, you can directly assign serial numbers for the partial
quantity.

You can change the layout of the Stock Items to Be Inspected screen into a vertical or horizontal split screen.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-QM

Availability SAP Extended Warehouse Management 9.5 FP02

Enhancements to Process E-Commerce Returns

With this app, you can process an unplanned customer return received without a warehouse request by identifying the sales
order number.

Technical Details

Product Feature is Changed

Country Dependency Valid for all countries

Application Component SCM-EWM-IF

Availability SAP Extended Warehouse Management 9.5 FP02

Effects on Customizing
You determine the document type that the system uses when you create an inbound delivery in Customizing for
Extended Warehouse Management under Goods Receipt Process Inbound Delivery Determine Document Types for
Inbound Delivery Creation .

You de ne return reasons in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound
Delivery De ne Return Reasons .

You de ne a number range for return orders in Customizing for Extended Warehouse Management under
Interfaces ERP Integration Delivery Processing De ne Number Ranges for Return Orders .

You choose a number range interval for creating SAP ERP return orders using the Order Int. eld in Customizing for
Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Control Message Processing
Dependent on Recipient .

This is custom documentation. For more information, please visit the SAP Help Portal 18
 9/2/2022
The following Business Add-Ins (BAdIs) are available in Customizing for Extended Warehouse Management under
Business Add-Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration Unplanned Returns ：

BAdI: Determination of Original System for Sales Orders

BAdI: Data Retrieval and Preparation for Return Delivery

BAdI: Change of Stock Types and Special Stock Indicators

The following Business Add-Ins (BAdIs) are available in Customizing for Extended Warehouse Management under
Business Add-Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration Outbound Messages from
EWM to ERP System ：

BAdI: Creation of Return Orders in ERP System

BAdI: Creation of Return Deliveries in ERP System

The Customizing activity De ne Number Ranges for ERP Documents has been renamed to De ne Number Ranges for
ERP Deliveries.

See Also
For more information, see https://help.sap.com/viewer/p/SAP_FIORI under More SAP Fiori Products for SAP Business
Suite SAP Fiori 1.0 for SAP Extended Warehouse Management Process E-Commerce Returns .

Deletion of Personal Data in SAP-EWM

Use
As of Feature Pack 02 for SAP Extended Warehouse Management 9.5, functions are available that simplify the blocking and
deletion of personal data by using SAP Information Lifecycle Management (ILM).

You can use the data destruction object EWM_DSAPP, which is mapped to the ILM object EWM_DSAPP, to delete loading
appointment data based on de ned retention periods.

You can use the data destruction object EWM_TATT, which is mapped to the ILM object EWM_TATT, to delete time and
attendance data based on de ned retention periods.

Effects on Existing Data

These functions enable you to use the SAP Information Lifecycle Management (ILM) component to support the deletion of
personal data and to control the deletion and blocking of business partner master data. Personal data collected in business
partner master data can be blocked as soon as business activities for which this data is needed are completed and the
residence time for this data has elapsed; after this time, only users who are assigned additional authorizations can access this
data. After the retention period for data expires, personal data can be destroyed completely so that it can no longer be
retrieved. Retention periods must be de ned in the customer system.

Effects on Data Transfer

An end of purpose check determines whether data is still relevant for business activities based on the retention period de ned
for the data. The retention period of data consists of the following phases.

Phase one: The relevant data is actively used.

Phase two: The relevant data is actively available in the system.

Phase three: The relevant data needs to be retained for other reasons.

This is custom documentation. For more information, please visit the SAP Help Portal 19
 9/2/2022
For example, processing of data is no longer required for the primary business purpose but to comply with legal rules for
retention the data must still be available. In phase three, the relevant data is blocked.

Blocking of data prevents the business users of SAP applications from displaying and using data that may include personal data
and is no longer relevant for business activities.

Blocking of data can impact system behavior in the following ways:

Display: The system does not display blocked data.

Change: It is not possible to change a business object that contains blocked data.

Create: It is not possible to create a business object that contains blocked data.

Copy/Follow-Up: It is not possible to copy a business object or follow up a business object that contains blocked data.

Only users with special authorization can display blocked data; they are not authorized, however, to create, change, or copy
business objects with blocked data, or perform follow-on activities with these business objects.

Effects on Customizing
To use SAP Information Lifecycle Management (ILM) to simplify the deletion of application-speci c personal data:

Activate the business function Information Lifecycle Management (ILM).

Make the necessary Customizing settings related to SAP Information Lifecycle Management (ILM) in Customizing for
SAP NetWeaver Application Server Basis Services Information Lifecycle Management .

Run transaction ILMARA and maintain and activate the required audit areas for the ILM objects of the application.

Run transaction IRMPOL and maintain the required retention policies for the ILM objects of the application.

In transaction ILM_DESTRUCTION, apply the ILM rules for the data destruction objects to data.

To use the new functions to simplify the blocking and deletion of business partner master data:

Activate the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF).

Make the necessary Customizing settings related to the blocking and deletion of business partner master data in
Customizing for Cross-Application Components under Data Protection.

To use the new functions to simplify the blocking and deletion of customer and vendor master data:

Activate the following business functions:

ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF)

ILM-Based Deletion of Customer and Vendor Master Data (ERP_CVP_ILM_1)

Make the necessary Customizing settings related to the blocking and deletion of customer and vendor master data in
Customizing for Logistics - General Business Partner Deletion of Customer and Vendor Master Data .

More Information
https://help.sap.com/viewer/p/SAP_INFORMATION_LIFECYCLE_MANAGEMENT

SAP Library for SAP ERP Cross-Application Functions at http://help.sap.com/erpApplication Help SAP ERP Cross-
Application Functions under Cross-Application Components Data Protection Deletion of Business Partner Data ,
Deletion of Customer Master Data or Deletion of Vendor Master Data.

This is custom documentation. For more information, please visit the SAP Help Portal 20
 9/2/2022
SAP Library for SAP Extended Warehouse Management at http://help.sap.com/ewm under SAP Extended Warehouse
Management Data Destruction in Extended Warehouse Management (SCM-EWM) .

SAP Extended Warehouse Management Security Guide at http://help.sap.com/ewm

Change Documents
Change documents are available for the following:

Employee performance documents

Time and attendance records

Labor-management-related processor data

Technical Details

Product Feature is New

Country Dependency Valid for all countries

Application Component SCM-EWM

Availability SAP Extended Warehouse Management 9.5 FP02

Effects on Customizing
You activate change documents for employee performance documents, time and attendance records, and labor-management-
related processor data in Customizing for Extended Warehouse Management under Labor Management Activate Change
Documents .

Business Functions

EWM, Essential Foundation Functions

Use

Technical Data

Technical Name of Business Function SCM_EWM_FND

Type of Business Function Enterprise Business Function

Available From SAP Extended Warehouse Management (SAP EWM) 9.0

Technical Usage EWM

Application Component Extended Warehouse Management (SCM-EWM)

Required Business Function Advanced Returns Management 2 (OPS_ADVRETURNS_2)

This business function should be switched on in your SAP Extended Warehouse Management (EWM) 9.0 system directly after
technical deployment of SAP EWM 9.0. It activates features that are technically situated in lower-level software components in

This is custom documentation. For more information, please visit the SAP Help Portal 21
 9/2/2022
the SAP EWM software component stack. These features of lower software components are necessary for the following
features:

Advanced returns management

Stock-speci c unit of measure

Displaying route master data on a geographical map

Cartonization planning

Dock appointment scheduling

Business partner ID mapping

As of SAP EWM 9.2, the features are also necessary for the following features:

Using the shelf life period indicator in the determination of shelf life expiration date and latest delivery date

Quality management inspection before goods receipt

Prerequisites
You have installed the following components as of the version mentioned:

Type of Component Component Required for the Following Features Only

Software Component SCMEWM 900 -

SCM_BASIS 702

Software Component SAP_APPL 606 Advanced Returns Management

Software Component SCMEWM 920 Using the shelf life period indicator

SCM_BASIS_713 Quality management inspection before goods receipt

EWM, Additional GTINs (EANs/UPCs) for Product

Use

Technical Data

Technical Name of Business Function SCM_EWM_MEAN

Type of Business Function Enterprise Business Function

Available From SAP enhancement package 2 for SAP Extended Warehouse

Management (SAP EWM) 7.0

Technical Usage EWM

Application Component Extended Warehouse Management (SCM-EWM)

Required Business Function Not relevant

You can use this business function to maintain and use additional Global Trade Item Numbers (GTINs) (including International
Article Numbers (EANs) and Universal Product Codes (UPCs)) for a unit of measure of a product in SAP Extended Warehouse

This is custom documentation. For more information, please visit the SAP Help Portal 22
 9/2/2022
Management (EWM). You can use additional GTINs, for example, to identify the same unit of measure of the same product by
different vendors.

Integration
You can download additional GTINs from SAP ERP using Core Interface (CIF) by means of initial transfer or change transfer of
material master data. To do so, you must activate the business function SCM, CIF Transfer of Additional GTINs (EANs/UPCs)
for Material ( LOG_SCM_MEAN_INT). This business function is available as of SAP enhancement package 6 for SAP ERP 6.0.

 Caution
The additional GTINs (EANs/UPCs) transferred from SAP ERP overwrite the additional GTINs that you have maintained in
SAP EWM.

Prerequisites
You have installed the following components as of the version mentioned:

Type of Component Component Required for the Following Features Only

Software Component SCMEWM 702

SCM_BASIS 702

Features
Maintenance of Additional GTINs

You can maintain additional GTINs in the transaction for maintaining product master data ( /SAPAPO/MAT1) and the
transaction for maintaining warehouse product master data ( /SCWM/MAT1) as you can maintain them in the transaction for
maintaining material master data in SAP ERP.

To maintain additional GTINs for a product, on the SAP Easy Access screen, choose Extended Warehouse Management Master
Data Product Maintain Product .

To maintain additional GTINs for a warehouse product, on the SAP Easy Access screen, choose Extended Warehouse
Management Master Data Product Maintain Warehouse Product .

On the tab page Additional GTINs/EANs, you can display, edit, and delete additional GTINs. The Units of Meas. (Units of
Measures) tab page displays in the eld Additional GTINs/EANs exist if additional GTINs exist for a unit of measure of a product
in SAP EWM.

Identi cation of a Product by Additional GTINs

If additional GTINs exists in SAP EWM, you can use them to identify products in the functions where the entry of a GTIN
(EAN/UPC) is possible, for example, in product validation using radio-frequency (RF).

More Information
Additional GTINs (EANs/UPCs) for Product

Migration from LE-WM

This is custom documentation. For more information, please visit the SAP Help Portal 23
 9/2/2022

Use
This section contains information on the functions available to migrate data from an LE-WM system to SAP Extended
Warehouse Management (EWM). The following features are available:

Warehouse Product Migration

Storage Bin Migration

Stock Migration

Physical Inventory Completeness Migration

Map Storage Unit Type to Packaging Material

Map Warehouse Management Unit of Measure to Packaging Material

Warehouse Product Migration

Use
You can use this function to migrate warehouse product data and some warehouse-independent product data from LE-WM into
SAP Extended Warehouse Management (EWM). The following options are available when migrating data:

Migrate product master data

Migrate xed bin assignments

You can create xed bin assignments which are part of the master data in ERP in EWM, where they are stored in a
separate table ( /SCWM/BINMAT).

Migrate palletization data

If the master data of the migrated products in ERP includes palletization data, you can transfer this data into EWM in the
form of new packaging speci cations. A separate packaging speci cation is created for each product. The data is stored
in a sequential text le, which is passed to the transaction /SCWM/IPU for upload.

Migrate warehouse management unit of measure (UoM)

You can migrate the warehouse management UoM from ERP material master data and use it to create a packaging
speci cation in EWM for warehouse task creation. The data is also stored in the sequential text le which is passed to
the transaction /SCWM/IPU for upload.

Integration
Global material master data is generally distributed through the core interface (CIF). However, the data on warehouse or
storage type level is not considered there, because it is the responsibility of the warehouse management.

This function reads the corresponding material data from ERP using an RFC connection. The data sources in ERP are the
following tables:

MLGN - Material Data for Each Warehouse Number

MLGT - Material Data for Each Storage Type

MARA - General Material Data (optional)

MARC - Plant Data for Material (optional)

This is custom documentation. For more information, please visit the SAP Help Portal 24
 9/2/2022
The system converts the extracted ERP data to an EWM-compatible format and downloads it to one sequential le. If the ERP
product has palletization or warehouse UoM information, and the corresponding parameters are set, the system creates a
separate le for the packaging speci cation upload. You can display and change these two intermediate les. During download,
you can also change the eld mapping using BAdIs.

You can also use this function to upload these les into the EWM system. The system updates the data in the warehouse
product master records, which you can display with the transaction /SCWM/MAT1.

If you have speci ed it, the system also creates xed bin assignments, which you can display using the transaction
/SCWM/BINMAT.

If relevant, the system also converts packaging data into a new packaging speci cation during the upload. The packaging
speci cations that have been created are not activated at this point.

Prerequisites
You have set up an RFC connection in the LE-WM and EWM systems.

You have mapped the LE-WM warehouse number to the EWM warehouse number in Customizing for Extended
Warehouse Management under Interfaces ERP Integration General Settings Map Warehouse Numbers from ERP
System to EWM .

You have created storage types in Customizing for Extended Warehouse Management under Master Data De ne
Storage Type .

You have created the relevant xed bins or migrated them from LE-WM on the SAP Easy Access screen for Extended
Warehouse Management under Master Data Storage Bin Create Storage Bin or Interfaces Migration from LE-
WM Storage Bin Migration .

You have created Entitled to Dispose as a business partner for the migrated plants.

You have distributed the global material master data to EWM using CIF.

You have maintained mapping entries for each storage unit type used in the ERP product master palletization data on
the SAP Easy Access screen for Extended Warehouse Management under Interfaces Migration from LE-WM Map
Storage Unit Type to Packaging Material .

To migrate the warehouse management unit of measure, you have de ned mapping on the SAP Easy Access screen for
Extended Warehouse Management under Interfaces Migration from LE-WM Map Warehouse Management UoM to
Packaging Material .

Features
You can use the same tools for download from LE-WM and upload into EWM. The sequential les can be stored either
locally on your PC or as a logical le on the server. You must specify the source system and client in the eld ERP
Business System. You can restrict the entries that are read from the ERP system, selecting by ERP warehouse number,
storage type, and product number. If you want to read plant-speci c data, you must enter an ERP plant.

 Recommendation
You should only enter an ERP plant if you want to migrate the MARC elds MARC-ABCIN ( Cycle counting indicator)
and MARC-EPRIO ( Stock determination group), because the additional selection might slow down the report
runtime. If you only want the warehouse-speci c data, you can leave the ERP plant selection parameter empty.

For xed bin assignment, the same logic can be applied as is available for storage bin migration in general. This means
that you can assign the storage type to the storage bin name in Customizing, either with or without a special separator.

This is custom documentation. For more information, please visit the SAP Help Portal 25
 9/2/2022
To assign a storage type to a storage bin, go to Extended Warehouse Management Interfaces Migration from LE-
WM Assign Storage Type to Storage Bin in Customizing.

When uploading and downloading, you can choose to migrate the data of the product master records, the xed bin
assignments, the packaging speci cation creation data and/or the warehouse management UoM separately. The
product data and xed bins are stored in the same sequential CSV le, whereas for the palletization or warehouse UoM
data the system creates a text le. This is necessary because the packaging speci cation upload is carried out using the
transaction /SCWM/IPU, which requires a text le.

You can manually change the Entitled to Dispose eld. By default it is set by the ERP plant (if given) or the warehouse
number default values in EWM

After downloading, you can display the product data records in an ALV list. When uploading, you can update the product
master data again, create xed bin assignments, or upload the palletization data separately or in the same run.

To check the data for the product master after uploading, you can use the transaction /SCWM/MAT1. You can display a
list of the xed bin assignments with the transaction /SCWM/BINMAT. If packaging speci cations are created, the
numbers of the created speci cations are shown in a protocol at the end of the upload. Using the numbers (or other
selection parameters such as the creator's name or creation time), you can select the packaging speci cations in the
transaction /SCWM/PACKSPEC. To use the created packaging speci cations, you must rst have selected and activated
them.

To delete warehouse number or storage type-speci c product master data, you can use the existing transaction for
changing master data. You can nd this transaction on the SAP Easy Access screen under SCM Basis Master
Data General Master Data Functions Mass Maintenance or by using the transaction MASSD. Here you can initialize the
relevant elds. The warehouse number and storage type views are not completely deleted.

To delete assignments of xed storage bins, you use the existing transaction for mass deletion. You can nd it in the SAP
Easy Access screen under Extended Warehouse Management Master Data Storage Bin Delete Fixed Storage Bin
Assignment or by using the transaction /SCWM/RFIXBINDEL.

To delete the created packaging speci cations, run the transaction /SCWM/PACKSPEC, select the packaging
speci cations, and delete them.

For the warehouse management UoM, the system decides which unit should be used according to the rule given in the
eld Propose UoM From Mat in ERP Warehouse Management General Data. For example, the value ' ' in this rule
indicates that the basis UoM should be the warehouse management UoM. If the chosen eld for the warehouse
management UoM is initial, the system reads table T340D and decides on a UoM according to rule 1 in this eld. If the
UoM is still initial, the system does the same with rule 2. These two rules are exactly the same as those in Propose UoM
From Mat, but are the default values on warehouse level in ERP.

The following elds are transferred from LE-WM:

Product Master Data, Warehouse Level

LE-WM EWM Description

MLGN-MATNR EXT_MATNR Material/product number

MLGN-LGNUM LGNUM Warehouse number

MLGN-LGBKZ LGBKZ Storage section indicator

MLGN- LTKZE PUT_STRA Storage type indicator for stock placement

MLGN-LTKZA REM_STRA Storage type indicator for stock removal

MLGN-BLOCK BLOCK Bulk storage indicator

MLGN-BSSKZ PTDETIND Special movement indicator for warehouse management

MLGN-L2SKR L2SKR Material relevance for two-step picking

This is custom documentation. For more information, please visit the SAP Help Portal 26
 9/2/2022

The following items of palletization data do not have a 1:1 relationship between ERP and EWM. They are transferred into an
EWM packaging speci cation.

LE-WM Description

MLGN-LETY1 Higher level storage unit type used for palletization

MLGN-LHMG1 Packed quantity on higher level storage unit type

MLGN-LHME1 Unit of measure of the packed quantity

MLGN-LETY2 Middle level storage unit type used for palletization

MLGN-LHMG2 Packed quantity on middle level storage unit type

MLGN-LHME2 Unit of measure of the packed quantity

MLGN-LETY3 Lower level storage unit type used for palletization

MLGN-LHMG3 Packed quantity on lower level storage unit type

MLGN-LHME3 Unit of measure of the packed quantity

Product Master Data, Storage Type Level

LE-WM EWM Description

MLGT-LGTYP LGTYP Storage Type

MLGT-NSMN REPQTY Replenishment quantity

Fixed Bin Assignment

LE-WM EWM Description

MLGT-LGPLA LGPLA (Fixed) storage bin

MLGT-LPMAX MAXQTY Maximum storage bin quantity

MLGT-LPMIN MINQTY Minimum storage bin quantity

Product Master Data, General Level

LE-WM EWM Description

MARA-MHDRZ SLRQ_MIN Required minimum shelf life

Product Master Data, Plant Level

LE-WM EWM Description

MARC-ABCIN CCIND Cycle counting indicator

MARC-EPRIO STCKDETGR Stock determination group

All quantities are transferred and stored using the material's base unit of measure.

For the material/product number, the same mapping is used as in the CIF interface. In the intermediate product data le, the
product number is already in an EWM-readable format. Warehouse Number, Entitled and other elds are also represented in
the le with the EWM values.

This is custom documentation. For more information, please visit the SAP Help Portal 27
 9/2/2022
The product number in the le for the packaging speci cation upload is an EWM product number. Additional data in this le is
either taken from the mapping that you have speci ed in the transaction /SCWM/MIG_MAP_SUT, or from the packaging
speci cation Customizing (such as the level type names assigned to the level set used, which in turn is assigned to the
packaging speci cation group).

Example
The following is a valid combination of entries:

Direction

Download from LE-WM X

Product Master Data X

Fixed Bin Assignment X

Pack. Spec. Palletization -

Pack. Spec. for WM UoM -

Data Source

ERP Business System ERP_001

Data Selection

ERP Plant

ERP Warehouse Number 001

ERP Storage Type 005

ERP Product Number EWM*

Conversion Rules

EWM Warehouse Number EW01

Party Entitled to Disp ERP001V

File Destination

Local File X

Product Master File Name C:\ERP\DOWN\TEST

Product Master File Type .csv

Packaging Spec File Name

Packaging Spec File Type .txt

Display Control

Show downloaded data X

When uploading, the selection criteria are ignored, but complete les are read. So it is only essential to input the correct
sequential les and to choose a type of update (product master and/or xed bin assignment and/or packaging speci cation).

Storage Bin Migration

This is custom documentation. For more information, please visit the SAP Help Portal 28
 9/2/2022

Use
You can use this function to migrate storage bin data and storage bin sortation data from LE-WM into SAP Extended Warehouse
Management (EWM).

The report is divided into two parts. The rst part is used to download the storage bin data and/or sortation data and store it in
an intermediate le.

The second part is used to upload the storage bin data and/or sortation data from the CSV le or the server le to the EWM
storage bin table ( /SCWM/LAGP) or the storage bin table for execution areas and activities ( /SCWM/LAGPS). This part uses
the transaction /SCWM/SBUP for the storage bin data and the transaction /SCWM/SRTUP for the sortation data.

Prerequisites
If you migrate the data by creating a local CSV le, the structure of this le must match the elds in the structure
/SCWM/S_LAGP_LSMW_MIG (for the storage bin data) or in the structure /SCWM/S_LAGPS_LSMW (for the sortation data).

Features
Selection Direction: Here you can indicate whether you want to carry out a download step or an upload step and
whether you want to use storage bin data and/or sortation data.

For download you must specify the ERP business system, the warehouse number in ERP, the warehouse number in
EWM and the destination (path and name) of the CSV le or the logical le name of the server le. You can also
re ne the information by entering a storage type range and a storage bin range.The EWM warehouse number you
enter replaces the ERP warehouse number in the intermediate le.

For upload you only need to specify the name of the le that contains the storage bin and/or sortation data. For a
local CSV le, you can enter the path and the le name directly or select the le by using the eld help. For a
server le, you can enter the logical le name directly or select the logical le name by using the eld help.

For the storage bin sortation data, the elds SORLP and REIHF are migrated from ERP. SORLP contains the sorting
sequence of the cross-line stock put away process. REIHF contains the sorting sequence of the picking process. The
storage type of the storage bin master is migrated as the activity area for the sorting table. The activities are taken
from the customized activities in the warehouse which have the warehouse process category 8 (Cross-line stock put
away) and 2 (Stock Removal). This means that you can have multiple lines in the local le for one storage bin.

The intermediate le in which data is stored is either a locally-stored CSV le or a logical le stored on the application
server. The CSV le has a header line with short text of the elds and can be edited with Microsoft Excel or a text editor.
Both les are based on the structure /SCWM/S_LAGP_LSMW_MIG. In the CSV le, the elds are separated either by a
semi-colon or a colon. The elds in the server le are not separated and there is no header line. The name of the CSV le
always has the extension '.csv'. The le type of the server le is taken from the setup of the logical le name. During the
data migration, the system ignores the rst line of the CSV le, as it typically contains the column headers.

In LE-WM the table LAGP is read using the selection criteria you have entered. In EWM the storage bin data is stored in
the table /SCWM/LAGP and the sortation data is stored in /SCWM/LAGPS. No other tables are affected.

In LE-WM the sorting elds can contain alphanumeric values, whereas this is not possible in EWM. If the system identi es
alphanumeric values during download, it automatically resorts the affected activities in the activity area. If your sorting
elds contain alphanumeric values you must migrate all storage bins of a storage type at once. The resorting during a
migration run always starts with the value 1. If you split your storage type the original sorting sequence gets lost, but if
you migrate all bins in a storage type in one run, the system can resort correctly. The LE-WM and EWM systems should
have the same codepage.

The following table shows how LE-WM sorting values are migrated:

This is custom documentation. For more information, please visit the SAP Help Portal 29
 9/2/2022

LE-WM Value EWM Value

01 1

1 1

00001 1

00001 1

010203 10203

A1B2 Resort

13 Resort

The following elds are taken from LE-WM and transferred into the elds of /SCWM/LAGP:

LE-WM Field Length EWM Field Length Description

MANDT 3 MANDT 3 Client. The logon client is taken in EWM

LGNUM 3 LGNUM 4 Warehouse number / warehouse complex

LGTYP 3 LGTYP 4 Storage type. Can be changed in Customizing.

LGPLA 10 LGPLA 18 Storage bin. Can be changed in Customizing.

LGBER 3 LGBER 4 Storage section

LPTYP 2 LPTYP 4 Storage bin type

PLAUF 1 PLAUF 1 Section of a storage bin. Is set by ISU

SKZUA 1 SKZUA 1 Blocking indicator: for stock removals (user)

SKZUE 1 SKZUE 1 Blocking indicator: for putaways (user)

SKZSI 1 SKZSI 1 Blocking indicator: current inventory (system)

SPGRU 1 Blocking reason: is translated into a user status by sharing the same name

ANZLE 9, 3 ANZLE 6 Number of storage units in storage bin. Is set by ISU

MAXLE 5 MAXLE 6 Maximum number of storage units in storage bin. Is set by ISU

LGEWI 11, 3 MAX_WEIGHT 15,3 Load capacity of storage bin

GEWEI 3 UNIT_W 3 Weight unit

MGEWI 11, 3 WEIGHT 15,3 Weight of materials in storage bin. Is set by ISU

BDATU 8 MOVED_AT 15 Date of last movement

BZEIT 6 MOVED_AT 15 Time of last movement

RDATU 8 CLEARED_AT Date of last bin clearing

RZEIT 6 CLEARED_AT Time of last clearing

KZINV 2 KZINV 2 Inventory method

SORLP 6 Sort eld for cross-line stock put away

REIHF 6 Sort eld for stock removal

IDATU 8 IDATU 21, 7 Date of last inventory for this storage bin

This is custom documentation. For more information, please visit the SAP Help Portal 30
 9/2/2022

LE-WM Field Length EWM Field Length Description

KZLER 1 KZLER 1 Indicator whether storage bin is empty. Is always checked

BRAND 2 BRAND 2 Fire-containment section

UNAME 12 UNAME 12 Last changed by. Is set to the processor of the upload

LAEDT 8 LAEDT 15 Date of last change. Is set to the date of upload

LKAPV 11, 3 MAX_CAPA 15, 3 Total capacity of storage bin

RKAPV 11, 3 FCAPA 15, 3 Available capacity in storage bin. Is set by ISU

VERIF 10 VERIF 18 Veri cation eld for mobile data entry

XCORD 10, 3 X_CORD 10, 3 X co-ordinate

YCORD 10, 3 Y_CORD 10, 3 Y co-ordinate

ZCORD 10, 3 Z_CORD 10, 3 Z co-ordinate

The following elds are taken from LE-WM and transferred into the elds of /SCWM/LAGPS:

LE-WM Field Length EWM Field Length Description

MANDT 3 MANDT 3 Client. The logon client is taken in EWM

LGNUM 3 LGNUM 4 Warehouse number / warehouse complex

LGPLA 10 LGPLA 18 Storage bin. Can be changed in Customizing

ACT_TYPE 4 Filled with the activities from Customizing

AAREA 4 Filled with the value from storage type

LGTPY 3 LGTYP 4 Storage type. Can be changed in Customizing

LGBER 3 LGBER 4 Storage section

SRT_NR 10 Either lled with value from SORLP or REIHF

Stock Migration

Use
You can use this function to migrate stock data from LE-WM into SAP Extended Warehouse Management (EWM).

Prerequisites
You have de ned all the storage bins for which you want to transfer the stocks from LE-WM to EWM.

There are no open documents (for example, inbound delivery, outbound delivery, and so on).

You have created the handling unit types in EWM that also exist in ERP.

You have transferred the packaging materials that exist in ERP to EWM.

You have mapped the storage unit types to packaging materials (see Map Storage Unit Type to Packaging Material).

This is custom documentation. For more information, please visit the SAP Help Portal 31
 9/2/2022
You have run the storage bin migration function and created all the necessary bins in EWM. For more information, see
Storage Bin Migration.

You have run the warehouse product migration function for all products that exist in the stock being migrated. For more
information, see Warehouse Product Migration.

Features
Direction

Download from LE-WM : The data is imported from LE-WM and saved in a le, taking into consideration the parameters
speci ed in the following sections.

Upload to EWM: The data is available in a le and ready to be uploaded to EWM.

Data Source

ERP Business System speci es the LE-WM system from which the data is to be imported.

Data Selection

ERP Plant (mandatory)

ERP Storage Location (optional)

ERP Warehouse Number (mandatory)

ERP Storage Type (optional)

ERP Storage Bin (optional)

You can use the optional parameters, for example, to limit the amount of data or to carry out the migration in separate
iterations.

Conversion Rules

EWM Warehouse Number speci es the EWM warehouse number to which the data should be uploaded. This entry is mandatory.

File Destination

Local File: indicates if the le is in the local directory

Logical File: indicates if the le is in the application server

File Name: entry for the le name and its directory

File Type: the le type used by the report (only CSV les are supported)

Display Control

Display Downloaded Data: When you select this checkbox, the data downloaded from LE-WM is displayed after import as
an ALV.

Include Entries with Error: When you select this checkbox, data that contains errors (such as stocks that still have open
documents) are included in the migration.

Activities

This is custom documentation. For more information, please visit the SAP Help Portal 32
 9/2/2022
The function should be executed in two steps:

1. Export the data from LE-WM and save it in a le.

2. Use the report Initial Stock Data Transfer to upload the data to EWM, by selecting the Upload radio button. For more
information, see Initial Stock Data Transfer.

Physical Inventory Completeness Migration

Use
You can use this function to migrate data about when a product was last completely counted. This is necessary because when
stock is migrated from LE-WM to EWM and inventory documents are created for the products, the progress of the inventory in
the legacy system is not migrated with the stock so all of the stocks are proposed for inventory. Inventory documents and
partial count results are not migrated.

Prerequisites
You have distributed the global material master data to EWM using CIF.

You have created physical inventory areas in Customizing for Extended Warehouse Management under Internal
Warehouse Processes Physical Inventory Physical-Inventory-Area-Speci c Settings De ne Physical Inventory Area .

You have created the inventory activity areas for your warehouse number in Customizing for Extended Warehouse
Management under Master Data Activity Areas .

You have mapped the inventory activity areas of your warehouse number to the physical inventory areas in Customizing
for Extended Warehouse Management under Internal Warehouse Processes Physical Inventory Warehouse-Number-
Speci c Settings Assign Physical Inventory Area to Activity Area .

You have set that completeness is always determined for the complete warehouse and not only for single activity areas
in Customizing for Extended Warehouse Management under Internal Warehouse Processes Warehouse-Number-
Speci c Settings Specify Physical-Inventory-Speci c Settings in the Warehouse .

Features
You can download the inventory completeness data from your LE-WM system to either a local or a logical le in the CSV format,
and then review the le before uploading it to EWM. To migrate the date of the last inventory completeness of a product from
the LE-WM to EWM, completeness data sets are created in EWM (table /LIME/PI_ADMI) according to the inventory data of
LE-WM. The following logic is used to determine the inventory completeness during the download:

First all the quants of a product are read from the LE-WM system. The system checks if the quant is in a storage type for
which an inventory method is speci ed in Customizing for Logistics Execution under Warehouse
Management Activities Physical Inventory De ne Types per Storage Type . Only quants in storage types that are
intended for inventory are taken into account.

To determine the last complete inventory date of a product, the system checks whether there is an inventory date
directly on the quant. If this is not the case, either the quant has not yet been counted or the inventory has been done for
the whole bin and not just the quant. This depends on the inventory method used. If the quant has a reference to an
inventory document, the bin containing the quant was counted while the quant was on it. In this case the inventory date
of the bin is used. If there is neither an inventory date on the quant nor on the storage bin the creation date of the quant
is used.

There are generally different inventory dates for the different quants of a product. To create the completeness data sets
in EWM, the earliest count date of all the quants is used. The earliest date is used because it is the date that causes the
This is custom documentation. For more information, please visit the SAP Help Portal 33
 9/2/2022
creation of new inventory documents when the inventory period for a product is over.

The resulting CSV le contains the following elds:

EWM warehouse number

EWM product number

Entitled to dispose

Inventory completeness date

In EWM the completeness data sets indicate the completeness of an inventory for each activity area. In LE-WM the bins are not
assigned to a similar object. Therefore completeness data sets are created for all the inventory activity areas when uploading
the data to set the completeness for the whole warehouse.

Map Storage Unit Type to Packaging Material

Use
You use this function to de ne the mapping between the storage unit type in LE-WM and the following SAP EWM data:

Packaging material

Handling unit type

Pack speci cation group

Condition type

Condition table

This data is used to build the packaging speci cation in EWM. This is part of warehouse product migration.

More Information
Warehouse Product Migration

Map Warehouse Management Unit of Measure to Packaging

Material

Use
You use this function to de ne the mapping between the warehouse management unit of measure (UoM) retrieved from the
LE-WM system and the following SAP EWM data:

Packaging material

Handling unit type

Pack speci cation group

Condition type

Condition table
This is custom documentation. For more information, please visit the SAP Help Portal 34
 9/2/2022
This data is used to build the packaging speci cation in EWM. This is part of warehouse product migration.

You can de ne a default entry in the eld Warehouse Management UoM. You de ne a default entry for all warehouse
management UoMs by leaving this eld blank. If the system does not nd an entry for the warehouse management UoM, it uses
this default entry for further processing.

More Information
Warehouse Product Migration

Warehouse Structure
Before you implement Extended Warehouse Management (EWM), you must de ne the structure, meaning the physical
structure, of your warehouse or warehouse complex and map this in the system.

When you implement EWM, you de ne the individual warehouses (high-rack storage area, bulk storage area, picking storage
area, and so on) as storage types within a warehouse complex, and join them together under one warehouse number.

If other warehouses (storage types) exist that you do not manage using EWM, then you should de ne other storage locations.

In EWM, you de ne storage bins for each storage type. EWM uses these to manage stock information about all products in the
warehouse, at storage bin level.

Mapping the Physical Warehouse in EWM

The warehouse structure in warehouse management is divided hierarchically and consists of the following elements:

Warehouse number

In EWM, you can manage an entire physical warehouse complex using a single warehouse number.

Storage type

This is custom documentation. For more information, please visit the SAP Help Portal 35
 9/2/2022
You can de ne the individual warehouse facilities or warehouses that make up the warehouse complex, using their
technical, spatial, and organizational characteristics as storage types.

Storage section

Each storage type is divided into storage sections. All storage bins with speci c common attributes belong to one
storage section, for example, storage bins for fast-moving items that are close to the goods issue zone.

Storage bin

Each storage type and storage section consists of a selection of storage compartments that are called storage bins in
EWM. The coordinates of the storage bin tell you the exact position in the warehouse, where you can store products.

Quant

The quant is used for inventory management of a product in a storage bin.

Activity area

The activity area is a logical grouping of storage bins. It can refer to a storage bin, or can concatenate bins from several
storage types.

You can either assign storage bins manually to the activity areas, or if there is a 1:1 relationship between storage type
and activity area, you can have the system generate the assignment.

To map the structure of your physical warehouse in the system, you de ne the warehouse structures in EWM in Customizing. We
recommend that you use the following sequence when con guring the warehouse structure in the system.

In the Implementation Guide (IMG) for EWM, choose Extended Warehouse Management Master Data

1. De ne Warehouse Numbers

2. De ne Storage Type

3. De ne Storage Section

4. Storage Bins De ne Storage Bin Types

5. Activity Areas De ne Activity Area

6. Activity Areas Assign Storage Bins to Activity Areas

Warehouse Number

De nition
In Extended Warehouse Management (EWM), you combine an entire physical warehouse under one warehouse number. You can
use the warehouse number to manage several storage facilities, which together form the complete warehouse complex.

Use
The organizational and physical attributes of a warehouse complex are collected together under the warehouse number.

For example, the weight unit, volume unit, and time unit are de ned at warehouse number level. You can also de ne
determination procedures for palletization data and packaging speci cations here. You should not change these settings at a
later time.

This is custom documentation. For more information, please visit the SAP Help Portal 36
 9/2/2022

 Note
We recommend using one warehouse number for each group of storage areas or buildings (warehousing complex) in the
same geographical area. If your warehousing facilities are located in different cities or are physically separated by a longer
distance, it is appropriate to assign a separate warehouse number to each warehouse complex.

For more information about de ning a warehouse number, see the Implementation Guide (IMG) for Extended Warehouse
Management under Master Data De ne Warehouse Number Control .

You must make a one-time assignment between the warehouse number and a supply chain unit with the business character
Warehouse as a continuous setting. For more information, see the IMG for Extended Warehouse Management under Master
Data Assign Warehouse Numbers . Note, however, that you must make this assignment in the production system. For this
reason, you should make this setting from the SAP menu under Extended Warehouse Management Settings Assignments:
Warehouse Numbers/Business Partners .

The supply chain unit contains essential information, such as country, region, and time zone. The system uses the time zone for
the warehouse number when displaying all date and time elds. You can create a supply chain unit in the SAP menu under
Extended Warehouse Management Master Data Maintain Supply Chain Unit .

 Caution
As soon as you actively use a warehouse number, for example because you have already created a warehouse number
product, you should no longer change the assignment of the supply chain unit to the warehouse number. Doing so can result
in follow-on errors.

Example
The warehouse for company XYZ includes the following facilities:

Goods receipt area

Goods issue area

Hall with high rack shelves

Bulk storage area

Activity areas of category Picking with Fixed Bins

Storage space outdoors for special substances

Each of the storage facilities listed above is called a storage type in EWM. EWM groups these facilities together under a
warehouse number.

Storage Type

De nition
A storage type is a storage space, storage facility, or storage zone, which you de ne for a warehouse number in Extended
Warehouse Management (EWM). The storage type is a physical or logical subdivision of a warehouse complex, which is
characterized by its warehouse technologies, space required, organizational form, or function. A storage type consists of one or
more storage bins.

You can de ne the following commonly-used physical storage types in EWM:

This is custom documentation. For more information, please visit the SAP Help Portal 37
 9/2/2022
Bulk storage area

General storage area

High rack storage area

Fixed bin storage area

Rack storage area

Use
The storage types form the warehouse complex and can be located in one or more buildings. You manage all storage types
under a single warehouse number.

The standard system for EWM comes con gured with several complete storage types that you can use straightaway. These
include:

High rack storage area

Bulk storage area

Fixed bin storage area

General storage area

Pallet storage area

These storage types have all been de ned with different control indicators for putaway and picking.

 Note
You can use the standard storage types as the basis for your individual settings, or you can create your own storage types to
meet the special requirements of your company.

De ning Control Indicators in the Storage Type

At storage type level, you must specify the control indicators that control the material ow (putaway and picking) in each
storage type. These include the control indicators for:

Putaway

Stock removal (picking)

 Note
Some control indicators for storage types are mutually exclusive, and certain combinations of indicators cannot be
permitted for legal reasons or due to internal guidelines. In these cases, the system generates an error message. We
recommend that you check and test all new combinations carefully, before you release them in the production
system.

You can only activate or deactivate the level of the available quantities and handling unit management requirement, if
there are no stocks present within a storage type.

We recommend that you only change the capacity check for a storage type if no more stocks are present within the
storage type.

Particular care should be taken if you subsequently change the putaway behavior for putaway.

This is custom documentation. For more information, please visit the SAP Help Portal 38
 9/2/2022
In the storage type, there are indicators that you can override in the warehouse process category. This means that speci c
functions, such as the con rmation requirements for putaway and picking or the option for posting changes to the same
storage bin, are valid for speci c storage types, but are not valid for a speci c posting.

For more information about changing the prede ned storage types or creating new storage types, see the Implementation
Guide (IMG) for EWM under Extended Warehouse Management Master Data De ne Storage Type .

Example
You can de ne several storage types for each warehouse number. The following gure shows ve storage types that are
assigned to a warehouse number:

Activity Area

De nition
Logical section of the warehouse that groups storage bins based on de ned warehouse activities.

Examples of activity areas include:

Putaway

Picking

Inventory

Use

This is custom documentation. For more information, please visit the SAP Help Portal 39
 9/2/2022
You use activity areas to provide logical subdivisions in your warehouse. In these activity areas, different warehouse workers
execute certain warehouse activities, such as putaway or picking.

You create activity-dependent bin sortings within an activity area. Extended Warehouse Management (EWM) uses these bin
sortings to optimize the execution of warehouse tasks.

Structure
An activity area consists of one or more assigned storage bins.

You can de ne the assigned storage bins using the following attributes:

Aisle

Stack

Level

Bin subdivision

Depth

Information about the storage type

Any assigned deconsolidation groups

You can sort these storage bins into any sequence you want, and assign as many activities to them as you require.

For more information, see the Implementation Guide (IMG) for Extended Warehouse ManagementunderMaster Data Activity
Areas Assign Storage Bins to Activity AreasandDe ne Sort Sequence for Activity Area .

 Note
To be able to work with activity areas, you have to generate the bin sorting.

On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Sort Storage Bins.

You can generate activity areas from storage types in Customizing. For more information, see the IMG for EWM under
Master Data Activity Area Generate Activity Area from Storage Type . In this case, the activity area has the same storage
bins as the storage type.

Integration
EWM generates warehouse orders for each activity area.

When EWM generates warehouse tasks, it considers the activity area and copies attributes from this activity area, such as the
deconsolidation group.

Storage Section

De nition
In Extended Warehouse Management (EWM), a storage section is an organizational subdivision of a storage type, which groups
together storage bins with similar attributes for the purpose of putaway. The criteria for grouping bins together are freely

This is custom documentation. For more information, please visit the SAP Help Portal 40
 9/2/2022
de nable: for example, heavy parts, bulky parts, fast-moving items, slow-moving items.

Use
You can use the storage section as an organizational aid for putting away goods in the warehouse. If you use storage types and
storage sections, you must de ne the organizational aims clearly. The physical location is the principal organizational factor. The
use of storage sections in a storage type is only mandatory if you use storage section control or storage section search in the
storage type.

 Note
You can de ne control parameters and control values only in the storage type.

For information on how to de ne a storage section for a storage type, see Customizing for Extended Warehouse Management
under Master Data De ne Storage Sections .

Example
High rack storage areas frequently consist of numerous storage bins of varying size. In many high-rack storage areas, low-level
bins are larger because they are reserved for particularly bulky and heavy parts. The bins located at higher levels are smaller.

The following gure shows a high-rack storage area divided into two storage sections. You use the front storage section for fast-
moving items and the rear one for slow-movers.

This is custom documentation. For more information, please visit the SAP Help Portal 41
 9/2/2022

High-Rack Storage Area Divided into Two Storage Sections

Storage Bin

De nition
A storage type consists of a selection of storage spaces, which are called storage bins in Extended Warehouse Management
(EWM). The storage bin is the smallest spatial unit in a warehouse. Therefore, the storage bin represents the exact position in
the warehouse where products are and/or can be stored.

Since the address of a storage bin is frequently derived from a coordinate system, a storage bin is often referred to as a
coordinate. For example, the coordinate 01-02-03 could be a storage bin in aisle 1, stack 2, and level 3.

Use
To each storage bin, you assign the warehouse number in which the storage bin is located. You just also assign a storage type
and storage section to each storage bin.

You can also de ne the following additional attributes for a storage bin:

Maximum weight

Total capacity

Fire-containment section

Storage bin type (for example, for large or small pallets)

In some putaway strategies, the storage bin type plays an important role during optimization of the automatic search for
a storage bin, in connection with the pallet type. For example, you can de ne the putaway strategy in such a way that you
put away large industrial pallets into special large bins, and smaller pallets into small bins.

For information about de ning storage bins, see the Implementation Guide (IMG) for Extended Warehouse Management under
Master Data Storage Bins .

Structure
You can use any combination of letters and numbers for storage bin coordinates. However, you should ensure that you orient
the parts of the structure to the indicators de ned for the warehouse for aisle, stack, level, and so on.

Quant

De nition
Stock of a speci c product with the same characteristics in one storage bin, resource, transportation unit (TU), or handling unit
(HU). The system manages different batches of a product as different quants.

Use
When you put a product away into an empty storage bin in Extended Warehouse Management (EWM), the system creates a
quant in this storage bin. You can increase the quantity of a quant by adding to the existing stock. When you remove the

This is custom documentation. For more information, please visit the SAP Help Portal 42
 9/2/2022
quantity from storage, the system automatically deletes the quant.

The system manages stock data per quant. Stock data includes the following:

Stock key, such as product number, batch number, and party entitled to dispose

Stock quantities, such as physical quantity and available quantity

Stock attributes, such as weight, volume, goods receipt date, and shelf life expiration date

Serial numbers

Displaying Quants

You can display stock information in the warehouse management monitor under the Stock and Bin node. For more information,
see Warehouse Management Monitor.

The system manages quantity differences posted during physical inventory or warehouse task con rmation at warehouse
number level. To display quantity differences, on the SAP Easy Access screen, choose Extended Warehouse
Management Physical Inventory Difference Analyzer . For more information, see Difference Analysis.

Changing Quants

The following documents can change quants:

A warehouse task changes the location of a quant or a partial quantity of a quant. It does not change the total quantity
of a product in the warehouse. A warehouse task also changes quants in a packaging process when you move an
unpacked quantity to an HU or you change the content of an HU.

A goods receipt or a goods issue changes the quantity of a quant. If the quant does not exist yet, the system creates it
with the goods receipt posting. If a goods issue is posted for the total quantity of a quant, the quant is deleted.

A posting change changes the stock key of a quant. It reduces the quantity of the source quant and increases the
quantity of the destination quant. It does not change the location of a quant.

You can change the attributes of a physical stock in the warehouse management monitor under the Stock and Bin node. You
can also change the quantity and alternative UoM of a quant manually in the monitor under Stock Physical Stock .

Integration with SAP ERP

If the EWM warehouse number is integrated with an SAP ERP system, the total physical stock of the warehouse number equals
the total stock of all plants and storage locations in SAP ERP integrated with the warehouse number. This stock also includes
the quantity differences at warehouse level displayed in the Difference Analyzer.

In integration with SAP ERP, EWM communicates all goods movements (goods issues, goods receipts, posting changes) posted
in EWM to SAP ERP if they are relevant for the ERP stock.

 Example
For example a posting change from a stock type (for example, F1) to another (for example, F2) is communicated to SAP ERP.

 Note
A posting change from a normal stock to a delivery-related stock in the picking process is not communicated to SAP ERP.
Warehouse tasks are EWM-internal processes and are not communicated to SAP ERP.

This is custom documentation. For more information, please visit the SAP Help Portal 43
 9/2/2022
To keep the stock in EWM and SAP ERP consistent, it is not possible to post a goods movement in SAP ERP for stock managed
by EWM. When you post a goods movement in SAP ERP (transaction MIGO), the system creates a delivery, which is transferred
and processed in EWM.

You can compare the total stock of EWM and SAP ERP for each warehouse number and party entitled to dispose on the SAP
Easy Access screen by choosing Extended Warehouse Management Physical Inventory Periodic Processing Stock
Comparison ERP . For more information, see the documentation of the transaction in the system.

The following table shows how the system maps an EWM stock to an ERP stock:

Stock Key in EWM Stock Key in SAP ERP

Product number Material number

Batch number Batch number (or valuation type in case of split-valuated product without
batch)

Party entitled to dispose Plant

Owner Plant for company-owned stock

Vendor for vendor consignment stock or returnable packaging

Stock type Stock type and storage location

Stock usage C and E Special stock indicator K and M

Document type SOS and PJS Special stock indicator E and Q

Document number and item number for sales order stock Sales order number and item (special stock E) or work breakdown structure
(SOS) and project stock (PJS) element (WBS element) (special stock Q)

Document category for stocks related to an EWM Not managed in SAP ERP
document

To change the mapping between the EWM stock key and the SAP ERP stock key, you can use the Business Add-In (BAdI) BAdI:
Enhancement of the ERP Stock ID Mapping . You can for example map the party entitled to dispose to an SAP ERP storage
location or storage location group instead of an SAP ERP plant. For more information, see Customizing under Extended
Warehouse Management Business Add-Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration Goods
Movements ERP Goods Movement Interface BAdI: Enhancement of the ERP Stock ID Mapping .

You can de ne own stock types in EWM and map them to an SAP ERP storage location as follows:

1. Create a new availability group for the SAP ERP storage location. For more information, see Customizing under Extended
Warehouse Management Goods Receipt Process Con gure Availability Group for Putaway .

2. Create a new entry for the SAP ERP storage location and assign it to the new availability group. For more information,
see Customizing under Extended Warehouse Management Interfaces ERP Integration Goods Movement Map Storage
Locations from ERP System to EWM .

3. Create new EWM stock types (for example, for unrestricted-use stock, quality-inspection stock, blocked stock, and
returns stock) and assign them to the new availability group. For more information, see Customizing under Extended
Warehouse Management Master Data Product De ne Stock Types .

Structure
Quant Identi cation

A quant identi cation consists of the following:

This is custom documentation. For more information, please visit the SAP Help Portal 44
 9/2/2022
Location key

A quant exists in a storage bin, a resource, a TU, or a warehouse number. A quant in a storage bin is identi ed by the
warehouse number, storage type, and storage bin. If the storage type is used for production supply, the system
determines the production supply area (PSA) from the storage bin in which the product is stored.

HU identi cation

You can manage quants with or without HUs. If you manage quants with handling units, the system uses the HU number
to identify a quant.

Stock key:

Product number

Batch number if the product is managed by batches or if it is split-valuated without batches

Party entitled to dispose (for example, SAP ERP plant)

Owner (for example, SAP ERP plant or vendor)

Stock type such as unrestricted-use stock or quality-inspection stock. If EWM is integrated with an SAP ERP
system, the stock type represents the SAP ERP stock type combined with the SAP ERP storage location.

Stock usage such as vendor consignment

Document type, document number, and item number for sales order stock (document type SOS) and project
stock (document type PJS)

Document category for stock related to an EWM document such as an outbound delivery, an inspection
document, a warehouse task, or a physical inventory document. Stocks related to a warehouse task or a physical
inventory document are quantity differences managed at warehouse number level.

Stock Quantities

The system manages the following quantities of a quant.

Physical quantity

The system checks and updates the physical quantity of a quant during the con rmation of a warehouse task or during
goods movements. The physical quantity is managed in base unit of measure. In case of catch-weight products it is
managed in parallel in logistics unit of measure and in valuation unit of measure.

In addition to the base unit of measure (or the logistics unit of measure for catch-weight products) you can use an
alternative unit of measure to display or move the stock. To use different packing levels for a product, you must de ne
packaging speci cations.

Available quantity

The available quantity of a quant is checked by the system during the creation of warehouse tasks. When a warehouse
task is created to pick a quantity from a storage bin, the available quantity of the quant is reduced.

The available quantity can be managed together for several quants of a storage bin. Depending on the storage type
settings, the available quantity is managed at the following levels:

at bin level (for all HUs containing a quant with the same stock key) or at top-HU level (for all sub-HUs containing
a quant with the same stock key)

at product level (for all batches of the product in the storage bin or HU) or at batch level

If an available quantity is managed at a different level than the physical quantity (for example, at storage bin level or at
product level) but a warehouse task is created at a more speci c level (for example, for a speci c HU or a batch), the

This is custom documentation. For more information, please visit the SAP Help Portal 45
 9/2/2022
system additionally manages a reserved quantity at the more speci c level. When you create a warehouse task, the
system checks not only the available quantity but also the reserved quantity.

Stock Attributes

The system manages several attributes for a quant:

Shelf life expiration date (which is the date up to which a product can be retained in storage and be acceptable for use)

Goods receipt date and time

Country of origin

Certi cate number

Inspection type and quality inspection document

Stock ID (see Stock Identi cation)

Weight, volume, and capacity usage

Consolidation group (see Consolidation Group)

Document and item number for stock related to an EWM document

Blocking indicator for physical inventory

Indicator for batch in restricted-use stock

 Note
The stock key is the list of all elds used to identify a quant (for example, product number, batch number, party entitled to
dispose).

The stock identi cation is a 20-digit number used to identify and handle easily a quant in the warehouse.

The system automatically creates a new quant if the quantity posted to a storage bin, resource, TU, or HU has a different stock
key, document reference (in case of stock related to an EWM document), stock ID, or quality inspection document reference
than the existing quant in the storage bin, resource, TU, or HU.

In the storage type settings, you can forbid addition to existing stock. This prevents the melding of quants with different stock
attributes. You can de ne special rules for addition to existing stock with regard to the goods receipt date, the shelf life
expiration date, and the certi cate number. For more information, see Customizing under Extended Warehouse
Management Master Data De ne Storage Type .

In addition to the stock attributes, you can manage batch attributes such as the best-before date in the batch data. For more
information, see Batch Management.

Serial Numbers

EWM can manage serial numbers in stock at quant level or at warehouse number level. For serial numbers managed at quant
level, the system keeps as many serial numbers in stock as the physical quantity of a speci c quant. If a quant contains 10
pieces, the system manages 10 serial numbers for the quant. You know in which bin, resource, TU, or HU a serial number is
stored in the warehouse. For serial numbers managed at warehouse level, the system keeps as many serial numbers in stock as
the physical quantity of all quants of a product. You receive no information about the exact location of a serial number in the
warehouse. For more information, see Serial Number.

Example
This is custom documentation. For more information, please visit the SAP Help Portal 46
 9/2/2022
The following gure shows quants of two different products in a storage bin with unpacked quantity (3 pieces (EA)), simple HU
(HU 3000), nested HU (HU 4000), and mixed stock (HU 1000).

Door

De nition
Location in the warehouse where the goods arrive at or leave the warehouse. The door is an organizational unit that you assign
to the warehouse number.

Vehicles and their transportation units (TUs) drive up to the doors of a warehouse to load or unload goods there. The doors are
in close proximity to the relevant staging areas .

Use
To control putaway and stock removal processes in your warehouse, you can de ne doors and staging areas within a warehouse
number.

You can assign various functions to a door:

Inbound

This is custom documentation. For more information, please visit the SAP Help Portal 47
 9/2/2022
Outbound

Inbound and outbound

In delivery processing, the system uses determination rules to determine the following for each delivery item:

Staging area groups

Staging areas

Staging bays

Doors

The determination rules are in uenced by the possible assignments that you have de ned in Customizing between doors and
staging areas as well as between doors and staging area/door determination groups. The system updates the delivery at item
level with the values that it nds.

You de ne doors in Customizing for Extended Warehouse Management (EWM) under Master Data Warehouse Door De ne
Warehouse Door. You assign staging areas and staging area/door determination groups to your doors under Master
Data Warehouse Door.

Structure
You assign each door to a storage bin that you can use to post goods receipts or goods issues. You assign this storage bin to a
storage type with the storage type role F .

You can also assign doors to supply chain units to control authorization checks. You can also assign doors to yard bins (see Yard
Management ).

See also:

Staging Area and Door Determination

Staging Area

De nition
Organizational unit that is assigned hierarchically to the warehouse number and that is used to organize the ow of goods in
the warehouse.

This is custom documentation. For more information, please visit the SAP Help Portal 48
 9/2/2022

Use
Staging areas are used for the interim storage of goods in the warehouse. They are located in close proximity to the doors
assigned to them. You can de ne staging areas for different purposes and even simultaneously for multiple purposes:

Goods receipt

Interim storage of unloaded goods until they are put away

Goods issue

Interim storage of picked goods until they are loaded

In Customizing, you de ne staging areas and assign the staging areas to the relevant doors. For more information, see the
Implementation Guide (IMG) for Extended Warehouse Management (EWM)underMaster Data Staging Areas De ne Staging
AreasandMaster Data Warehouse Door Assign Staging Area to Warehouse Door .

Structure
You can group multiple staging areas into staging area groups. The staging area group corresponds to a storage type (storage
type role "D"), while the staging area corresponds to a storage section. You can divide each staging area into one or more
storage bins. You need multiple storage bins, for example, if you want to de ne a loading sequence.

See also:

Staging Area and Door Determination

Work Center

De nition

This is custom documentation. For more information, please visit the SAP Help Portal 49
 9/2/2022
The work center is a physical unit in the warehouse, in which you can perform warehouse activities such as packing, distribution,
or weighing.

Use
You can use the work center in the following processes:

Packing

Deconsolidation

Counting

Quality Inspection

Extended Warehouse Management (EWM) contains the following transaction types for the work center:

Packing - General

This transaction type is for all general repacking transactions.

Deconsolidation

This transaction type is for distributing mixed handling units (HUs) into HUs for non-mixed deconsolidation groups.

Quality Inspection and Count

This transaction type is for entering count and inspection results, and for con rming inspection results.

Packing in the Staging Area

This transaction type is for packing together HUs according to the criterion Stop on Route .

You must assign each work center to a warehouse number, storage type, and storage bin. Note that you can only use storage
types that have one of the following storage type roles:

Work Center (E)

Pick Point (B)

Work Center in Staging Area Group (I)

Identi cation and Pick Point (C)

You can con gure more than once work center for each storage type in the system.

You can assign an inbound and outbound section to each work section. For more information about setting up work centers, see
Customizing for EWM under Master Data Work Center .

Example
The following example shows you various options, for example, on how a work center for deconsolidation can be structured:

Work center 1 represents the deconsolidation work center, which has no inbound section and no outbound section.

Work center 2 represents the deconsolidation work center, which has an outbound section but no inbound section.

Work center 3 represents the deconsolidation work center, which has both an inbound section and an outbound section.

This is custom documentation. For more information, please visit the SAP Help Portal 50
 9/2/2022

You can also join work centers together into work center groups. This means that you can send individual products or HUs to a
work center group, which corresponds to a storage section. In the above example, this would be a warehouse task to storage
section 0001.

The system only determines the nal storage bin, and thus the work center, when you con rm the warehouse task.

Resource

De nition
A resource is an entity representing a user or equipment, which can execute work in the warehouse.

This is custom documentation. For more information, please visit the SAP Help Portal 51
 9/2/2022

Use
A resource can log on to a radio frequency (RF) or non-RF environment.

Once the resource is logged on to the system, it can receive work for execution, and can be tracked and displayed in the
warehouse management monitor .

 Note
For more information about logging on to an RF environment, see Logon .

For more information about how resources receive work, see Assignment of Warehouse Order to Resource .

Structure
A resource belongs to a resource type and resource group .

 Note
You de ne a resource in the transaction for resource maintenance. To do so on the SAP Easy Access screen, choose
Extended Warehouse Management Master Data Resource Management /SCWM/RSRC - Maintain Resource .
Alternatively you can de ne a resource by using the warehouse management monitor ( method Maint. Resource ).

Resource Type
De nition
A resource type is a grouping of resources with similar technical or physical quali cations.

This is custom documentation. For more information, please visit the SAP Help Portal 52
 9/2/2022

Use
The resource type determines the following for its corresponding resources :

Horizontal velocity

The velocity of a resource can in uence the LSD of a warehouse order (WO).

For more information, see Latest Starting Date (LSD) .

Applicability of position management

For more information, see Position Management .

Quali cations and preferences (re ected by priority values) regarding bin access typesand HU type groups

The quali cations and priority values in uence which WOs are selected for a resource requesting work.

For more information, see Warehouse Order Selection .

 Note
You de ne resource types, and assign to them quali cations, in Customizing for Extended Warehouse
Management Cross-Process Settings Resource Management De ne Resource Types.

You maintain the quali cation priority values using the execution priority maintenance transaction, accessed on the
SAP Easy Access screen ( Extended Warehouse Management Master Data Resource
Management /SCWM/EXECPR - Maintain Execution Priorities ).

Resource Group

De nition
A resource group is a grouping of resources for queue assignment purposes.

Use
The resource group determines the sequence of allowed queues for its corresponding resources, which can in uence which WOs
are selected for a resource. For more information, see Warehouse Order Selection.

 Note
You assign/unassign a resource group to/from a queue using the queue sequence for resource group transaction, accessed
on the SAP Easy Access screen (Extended Warehouse Management Master Data Resource Management /SCWM/QSEQ -
Maintain Queue Sequence for Resource Group ), or from the warehouse management monitor (Assign Queue/Unassign
Queue methods).

Warehouse Product

De nition
Warehouse-number-dependent view of the product master data. The warehouse product comprises all the properties of a
product that relate to its storage in a certain warehouse within the framework of Extended Warehouse Management (EWM),
such as the putaway control indicator.

This is custom documentation. For more information, please visit the SAP Help Portal 53
 9/2/2022

Use
You need the warehouse product if you wish to use a product whose global data you have already maintained in the product
master in EWM.

You can create or change a warehouse product via the SAP menu under Extended Warehouse Management Master Data
Maintain Warehouse Product . Entry of the warehouse number and the 'party entitled to dispose' is mandatory, because the
warehouse-number-dependent data pertaining to the warehouse product applies only to this warehouse number and this party.

Structure
The warehouse-number-dependent data on the warehouse product can be found on the following tab pages in the maintenance
function for warehouse products:

Warehouse data

Here you maintain data on the warehouse in which the product is stored.

Slotting

For more information, see Slotting.

Storage type data

Here you maintain data on the type of facility in which the product is stored. For more information, see Storage Type.

Integration
Global, warehouse-number-independent data pertaining to the storage of the product can be found on the Storage tab page
.This tab page is also displayed in product master maintenance.

The following warehouse-number-independent data on the storage of a product is adopted in EWM from the ERP system.

Handling unit types

Warehouse product group

Warehouse storage condition

Warehouse handling indicator

Serial number pro les

Quality inspection groups

Preferred unit of measure for warehouse operations

For more information about the transfer and maintenance of this data, see the Implementation Guide (IMG) for EWM under
Master Data Product Settings in the ERP System .

For more information about the transfer and maintenance of the preferred unit of measure, see Preferred Unit of Measure.

Hazardous Substance
De nition

This is custom documentation. For more information, please visit the SAP Help Portal 54
 9/2/2022
Substance that can pose a danger to humans, animals, or the environment when being handled or stored. The handling and
storage of hazardous substances is governed by law.

For more information, see the SAP Help Portal under SAP ERP Central Component Logistics Environment, Health and Safety
(EHS) Hazardous Substance Management (EHS-HSM) Hazardous Substance Master Hazardous Substance.

Packaging speci cation

A packaging speci cation is master data. The packaging speci cation de nes all the necessary packing levels for a product in
order, for example, to put away or transport the product. For a product, a packaging speci cation mainly describes in which
quantities you can pack the product into which packaging materials in which sequence.

Use
In printed form, a packaging speci cation is a set of instructions for the employee in the warehouse. More speci cally,
the work steps that you enter in a packaging speci cation are intended as information for the employee. In this way you
can, for example, give the employee exact instructions as to where to place the label on a box, or how a product should
be stacked onto a pallet.

The system can determine packaging speci cations during various processes (see below). Processes that determine
packaging speci cations use only parts or speci c attributes from the packaging speci cation.

Structure

This is custom documentation. For more information, please visit the SAP Help Portal 55
 9/2/2022

Header

Attributes such as the name of the packaging speci cation, user name of the creation user, status, and so on.

Contents

A packaging speci cation contains a product. However, some packaging speci cations contain more than one product, or
refer to other packaging speci cations.

Level

You can map various packing levels in a packaging speci cation. Each level contains a target quantity, which de nes how
many times you can pack the previous level into this level.

Element group

For each level there is exactly one element group. However, you can reuse element groups in several packaging
speci cations.

Elements

Elements consist of a packaging material and/or a work step.

Step

A text with an identi cation, which you can use in one or more packaging speci cations.

Packaging material

This is custom documentation. For more information, please visit the SAP Help Portal 56
 9/2/2022
A product that is de ned with a packaging material type in the product master.

Example for a Packaging Speci cation and Its Structure:

Header: Name: PS1, Status: New

Contents: product A, 1 piece

Level 1: Target quantity one, element group EG1

Element group EG1:

Element E1: packaging material ʻSmall box’, work step ʻPlace 1 piece upright in each box’

Element E2: additional packaging material ʻLabel’, work step ʻPlace label on upper left’

Level 2: Target quantity 50, shift quantity 10, element group EG2

Element group EG2:

Element E3: packaging material ʻPallet’, work step ʻPlace boxes layer by layer onto pallet’

Integration
The following gure shows which processes use the packaging speci cation, and using which components:

This is custom documentation. For more information, please visit the SAP Help Portal 57
 9/2/2022

In both the Inventory Collaboration Hub (ICH) and in Extended Warehouse Management (EWM), you can use the same
packaging speci cation for an inbound delivery or an ASN that you then use for the process Automatic Packing .

Example
Palletization data in EWM

In your warehouse, you put away product A onto pallets for 50 pieces. Create a packaging speci cation with a level that contains
the main packaging material Pallet and the contents Product A. For this level, enter the target quantity 50.

In the process ʻPutaway’ for the inbound delivery, the system splits the quantity in the inbound delivery across multiple
warehouse tasks, due to this packaging speci cation For example, if a quantity of 100 pieces is delivered, then the system
creates two warehouse tasks for 50 pieces.

Functions of the Packaging Speci cation

The following functions are possible for packaging speci cations:

Create, copy, and activate (see also: Creation of Packaging Speci cations)

Search (see also Packaging Speci cation Determination)

Distribute into multiple systems.

Route

De nition
Sequence of legs that are connected by transshipment locations.

Use
The route represents a framework or corridor that comprises a multitude of trips, in other words, possible concrete itineraries.
The system uses routes to determine trips in route determination (see Route Determination).

You can form cross-docking routes from routes (see Cross-Docking Route).

You can de ne routes in transaction /SCTM/ROUTE.

Structure
Leg

A leg is assigned uniquely to a route, in other words, it cannot be part of multiple routes. You de ne legs as a sequence of stops.
Each stop is a supply chain unit (SCU), in other words, a location, or zone (see Zone). The stops that connect two consecutive
legs must be locations.

By specifying whether the stop-offs are optional or mandatory, you de ne which locations the carrier is to serve in which order.

You assign exactly one means of transport to each leg. In most cases, adjacent legs of a route have different means of
transport. However, it might also be necessary to change legs due to various properties of the legs. Nonetheless, in most cases,

This is custom documentation. For more information, please visit the SAP Help Portal 58
 9/2/2022
the legs of a route represent its unimodal parts.

Stop

At stop level, you can assign a mode of transport for foreign trade to each location. The system then takes into account this
mode of transport for outbound shipments in the case of exports. The value that represents this mode of transport is
dependent on the country in which the location lies. The system does not check if the mode of transport semantically matches
the means of transport used for the leg of this location. Since, in most cases, the system cannot de ne a unique country for
zones, it does not permit you to de ne a mode of transport for such stops.

In static route determination, the system determines the mode of transport for foreign trade for outbound shipments (trips) in
the following sequence:

1. Country of rst location

2. Part of the location sequence of the trip that runs from the rst location within this country

3. The rst location in this part of the location sequence when going backward that is a stop along the leg and for which a
mode of transport for foreign trade was de ned, in other words, the location that lies closest to the border.

Carrier Assignment

You can assign as many different carriers as you want to your means of transport or any of its subordinate means of transport
for the leg. You can specify whether dangerous goods can be transported for each such combination of leg, means of transport,
and carrier.

In static route determination, the system de nes the carrier for a trip as the carrier for the rst leg who can transport
dangerous goods, if required, and for which you have de ned the lowest costs for transportation along this leg in the carrier
pro le.

Departure Calendar Assignment

You can de ne a departure calendar for the leg. If the departures for a speci c request type do not correspond with the
departure calendar for the leg, you can also de ne a speci c departure calendar for this request type.

The system takes into account departure calendars when scheduling a trip for both the start location of the request and for
each transshipment location served. For more information, see Scheduling.

Validity and Restrictions

You can restrict the validity of a route by specifying the following:

A validity period that the system compares with the cutoff time of a single request.

Permitted shipping conditions that the system compares with the shipping conditions of a single request.

Permitted request types that the system compares with the request type of a single request.

You can specify permitted request types at the header level of the route and for each stop within the leg (customer, for
example). The request types at stop level must be part of the request types that you specify at header level. Request
types at stop level have a higher priority than those at header level. Accordingly, the request types at header level are
valid for those stops for which you have not de ned separate request types.

Permitted transportation groups that the system compares with the transportation groups of the products in a single
request.

Weight limits for single and collective requests that the system compares with the total weight of the products in the
single request or in multiple combined requests

This is custom documentation. For more information, please visit the SAP Help Portal 59
 9/2/2022
You can also specify weight limits for single and collective requests for each stop within a leg. These limits overwrite the
relevant limits that you specify for the route at header level.

Volume limits for single and collective requests that the system compares with the total volume of the products in the
single request or in multiple combined requests

You can also specify volume limits for single and collective requests for each stop within a leg. These limits overwrite the
relevant limits that you specify for the route at header level.

Dimension limits (length, width, and height)

You can specify the maximum dimensions that a product is permitted to have to be valid for a certain route. The system
compares these dimensions with those that you de ned in the product master.

You can also de ne various lead times for the different request types. These in uence the start time of a trip in scheduling.

Example
The following gure shows a route with three legs that are connected by the transshipment locations P and M. It also shows a
(red) trip for the case where all stop-offs in the middle leg are optional and a (blue) trip for the case where these stop-offs are
mandatory.

Route

Cross-Docking Route

De nition
One or more inbound routes or one or more outbound routes that are connected by exactly one cross-docking location
(warehouse or distribution center relevant to cross-docking).

Use

This is custom documentation. For more information, please visit the SAP Help Portal 60
 9/2/2022
You use cross-docking routes (CD routes) to link routes to route networks. The system takes into account CD routes when you
use route determination as part of cross-docking.

Here you can de ne per route pair (inbound route and outbound route) whether goods at the cross-docking location (CD
location) are to remain on the same vehicle or whether they are be loaded onto a different vehicle.

For more information, see Route Determination as Part of Cross-Docking and SAP Library for SAP Extended Warehouse
Management (SAP EWM) on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Extended Warehouse
Management Cross-Docking (CD) .

Structure
To de ne a CD route, you must make the following settings:

You specify a CD location for the route at header level.

You specify one or more inbound routes on the CD Routes tab page. Here the destination location of all these routes
must be identical with the CD location.

You specify one or more outbound routes on the CD Routes tab page. Here the start location of all these routes must be
identical with the CD location. By specifying a different CD route as the inbound or outbound route, you can create a
route network with multiple CD locations. Here an outbound CD route from CD location 1 must have at least one inbound
route with the start location CD location 1. An inbound CD route to CD location 2 must have at least one outbound route
with the destination location CD location 2.

On the CD Attributes tab page, you de ne the required attributes, for example, whether transshipment is not required
(goods remain on the same vehicle), for the route pairs that consist of inbound and outbound routes.

 Note
You de ne CD routes in the Maintain Route ( /SCTM/ROUTE) transaction.

Example
The following gure shows a route network consisting of two CD routes:

This is custom documentation. For more information, please visit the SAP Help Portal 61
 9/2/2022

Cross-Docking Routes

Vehicle

De nition
A specialization of a particular means of transport. A vehicle can comprise one or more transportation units (TUs). For more
information about transportation units, see Transportation Unit.

Use
You de ne vehicles in the master data for transportation. You use vehicles to group TUs and to communicate with invoicing and
freight order management.

It is not mandatory to use vehicles in shipping and receiving if the features available at TU level are sufficient for your
transportation processes.

If you assign TUs to a vehicle in a xed way, you cannot assign these TUs to another vehicle. In this case, data that you de ne for
the vehicle is also valid for the assigned TUs.

The dimensions of the vehicle come from the means of transport that you assign to the vehicle, and are used as the planned
size.

You can print waybills for vehicles. For more information, see Print Forms in Shipping and Receiving.

Integration
This is custom documentation. For more information, please visit the SAP Help Portal 62
 9/2/2022
If you use the Shipping Cockpit in your outbound processes, a vehicle is just displayed as an attribute of the TU and not
as its own hierarchy level. However, it is still possible to perform process steps on vehicles with assigned TUs, even if they
are executed on TU level.

For processes with transportation planning in SAP ERP, you can create a vehicle from an SAP ERP shipment. You can use
the SAP ERP shipment number as the external vehicle number.

For processes with transportation planning in SAP Extended Warehouse Management and communication to SAP ERP,
you can create an SAP ERP shipment from a vehicle. You can use the external vehicle number as SAP ERP shipment
number.

For processes with transportation planning in SAP Transportation Management (SAP TM), you can create a vehicle from
an SAP TM freight order. You can use the SAP TM freight order as the external vehicle number.

Before goods issue posting, you can create the current invoice via an invoice request to SAP CRM Billing or to SAP ERP.
For more information, see Invoice Creation Before Goods Issue.

Example
The truck with the license plate number HSK-116 has a trailer. This means that it consists of two TUs: The cargo area and the
trailer.

More Information
Shipping and Receiving in Inbound and Outbound Processes.

Transportation Unit

De nition
The smallest loadable unit of a vehicle that is used to transport goods. The transportation unit (TU) can be, but does not need
to be, part of a vehicle. For more information about vehicles, see Vehicle.

The following gure shows different TUs:

Vehicle 1: Semitrailer truck with one TU

Vehicle 2: Truck with cargo area and trailer, in other words, two TUs

Vehicle 3: Train with four wagons, in other words, four TUs

This is custom documentation. For more information, please visit the SAP Help Portal 63
 9/2/2022

Transportation Unit Definition

In addition to the means of transport, you need a packaging material to create a TU. By linking this packaging material to a
means of transport, you de ne construction rules for your vehicles or TUs. In this way, you de ne, for example, how many TUs a
vehicle is supposed to have and the order in which they are to be arranged. You also specify whether a TU is to be optional or
obligatory:

Obligatory TUs are a xed part of a vehicle ( xed assignment). You cannot assign them to another vehicle, for example,
truck cargo area.

You can assign optional TUs to other vehicles, for example, trailer for a truck.

Use
You de ne TUs in the master data for your transportation planning and execution in SAP Extended Warehouse Management
(SAP EWM).

You can print waybills for TUs.

If you use yard management, you use TUs for inventory management in the yard.

Integration
Before you assign deliveries to a TU, you create a shipping and receiving activity for the TU.

In your outbound processes with TUs, you can use the Shipping Cockpit to perform all TU-related steps within your
warehouse.

In processes with transportation planning in SAP ERP, you can create a TU from an SAP ERP shipment. You can use the
SAP ERP shipment number as external TU number.

In processes with transportation planning in SAP EWM and communication to SAP ERP, you can create an SAP ERP
shipment from a TU. You can use the external TU number as SAP ERP shipment number.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 9/2/2022
In processes with transportation planning in SAP Transportation Management (SAP TM), you can create a TU from an
SAP TM freight order. You can use the SAP TM freight order as the external TU number.

Before goods issue posting, you can create the current invoice via an invoice request to SAP CRM Billing or to SAP ERP
(see Invoice Creation Before Goods Issue).

Supply Chain Unit (SCU)

De nition
Physical or organizational unit that is used with one or more business characters within a logistical process. An organizational
unit may be a goods receiving office or a shipping office, for example.

The business characters are prede ned by SAP.

Use
With the SCU, you can replicate certain business characters of locations, such as door or warehouse, which you need in the
processes of Extended Warehouse Management (EWM). You can use an SCU with different business characters. An SCU can
simultaneously be used as a planning location and a shipping office, for example.

You can create hierarchies of SCUs to represent the organization of a supply chain.

You can create, change, and delete SCUs via the SAP menu, under Extended Warehouse Management Master Data Maintain
Supply Chain Unit.

Structure
The SCU contains general data and address data of the corresponding location. In contrast to the latter, however, it does not
contain any further global or application-speci c data. The SCU also has one or more business characters.

You will nd this SCU data on the following tab pages:

General

General header data of the SCU/location, such as the global location number (GLN) and geographical data.

The technical name of an SCU must be unique in the system. That is to say, it must not con ict with the technical name
of a location.

Address Data

Address data of the location/SCU

Business Character

One or more business characters of the SCU.

Integration
When a location is created in SAP SCM either manually or by transfer via the core interface (CIF), the system automatically
creates an SCU with identical general and address data and the business character planning location .

This is custom documentation. For more information, please visit the SAP Help Portal 65
 9/2/2022
Conversely, if you create an SCU with the business character planning location , the system automatically creates a location
with identical general and address data.

 Caution
This relationship is of signi cance when a location is deleted. When you delete a location, the system only deletes the
business character planning location of the corresponding SCU. If the SCU has further business characters, it remains in the
system with the same name. To delete the SCU from the system, you must rst delete all other existing business characters.

If you create an SCU with the business character Warehouse , the system does not create a corresponding location.

Warehouse Task

De nition
Document that uses Extended Warehouse Management ( EWM ) to execute goods movements. Logical or physical goods
movements or even stock changes can be the basis for a warehouse task. These include:

Picks

Putaways

Internal goods movements

Posting changes

Goods receipt postings

Goods issue postings

Use
You create the warehouse task either with reference to a warehouse request or without a reference document, for example for
internal goods movements.

The following gure shows the different warehouse tasks for products and handling units (HUs):

Product warehouse tasks

Handling unit warehouse tasks

This is custom documentation. For more information, please visit the SAP Help Portal 66
 9/2/2022

You or the system use product warehouse tasks, for example, for deconsolidation and handling unit warehouse tasks, for
example, for unloading .

You can identify the type of the warehouse task from the warehouse process type in the warehouse task. For more information
about the simultaneous use of product warehouse tasks and handling unit warehouse tasks, see Pick Point .

EWM also submits hazardous substance texts in the warehouse task.

When you con rm a warehouse task, you can also perform a physical inventory at the same time . Here, EWM can work with the
low-stock physical inventory.

Warehouse Order

De nition
Document that represents an executable work package that a warehouse employee should perform at a speci c time. The
warehouse order consists of warehouse tasks or physical inventory items.

Use
When you move products, in other words you or Extended Warehouse Management (EWM) create warehouse tasks, then EWM
groups these warehouse tasks together into warehouse orders, and makes them available for processing.

When you perform a physical inventory, in other words you create physical inventory items, EWM also groups these physical
inventory items together into warehouse orders.

You can adjust the scope and type of a warehouse order using the warehouse order creation rules that you have de ned in
Customizing.

 Note
For more information about warehouse order creation rules, see the Implementation Guide (IMG) for EWM under Cross-
Process Settings Warehouse Order De ne Creation Rule for Warehouse Orders.

Integration

This is custom documentation. For more information, please visit the SAP Help Portal 67
 9/2/2022
The warehouse groups together warehouse tasks or physical inventory items.

Example
EWM creates warehouse tasks for an outbound delivery with four delivery items. EWM uses warehouse order creation to assign
the resulting four warehouse tasks to a new warehouse order. A warehouse employee receives this warehouse order as a work
package to pick the items listed in the delivery.

Handling Unit (HU)

De nition
A handling unit is a physical unit consisting of packaging materials (load carriers/packing material) and the goods contained
on/in it. A handling unit is always a combination of products and packaging materials. All the information contained in the
product items, for example, about batches, is retained in the handling units and is always available.

For more information, see Packaging Materials.

Handling units can be nested, and you can create a new handling unit from several other handling units.

A handling unit has a unique, scannable identi cation number that you can construct according to industry standards such as
EAN 128 or SSCC.

Fig. 1: Example of a Handling Unit

Structure
The object “Handling Unit” contains the following attributes:

Identi cation number

Dimension

Weight

Volume

Status

Products and quantities

This is custom documentation. For more information, please visit the SAP Help Portal 68
 9/2/2022
Packaging material

Packaging speci cation

A handling unit consists of a handling unit header and handling unit items. It receives a unique number that is used for
identi cation purposes.

Handling Unit Header

The header data of a handling unit is divided up as follows:

Weight/volume/dimension

General data

Storage-speci c data

For more information about the different detailed information, see Packing at the Work Center.

Status

The handling unit is connected to general status management. This enables you to document the various physical statuses
(such as planned or realized) and other attributes (such as, weighed, loaded, blocked, or posted for GI) for a handling unit.

If you want to use your own status, you can store a user schema for the packaging material type.

Handling Unit Item

The items of a handling unit can consist of products, auxiliary packaging materials, or other handling units, which are displayed
in an overview. For more information about this overview, see Packing at the Work Center.

EWM-Speci c Master Data Settings

You can make master data settings speci c to SAP Extended Warehouse Management (EWM).

Additional GTINs (EANs/UPCs) for Product

Use
You can use additional Global Trade Item Numbers (GTINs) (including International Article Numbers (EANs) and Universal
Product Codes (UPCs)) for a unit of measure of a product in SAP Extended Warehouse Management (EWM). You can use
additional GTINs, for example, to identify the same unit of measure of the same product by different vendors.

Features
Maintenance of Additional GTINs in EWM

You can maintain additional GTINs in the transaction for maintaining product master data ( /SAPAPO/MAT1) and the
transaction for maintaining warehouse product master data ( /SCWM/MAT1).

To maintain additional GTINs for a product, on the SAP Easy Access screen, choose Extended Warehouse
Management Master Data Product Maintain Product .

This is custom documentation. For more information, please visit the SAP Help Portal 69
 9/2/2022
To maintain additional GTINs for a warehouse product, on the SAP Easy Access screen, choose Extended Warehouse
Management Master Data Product Maintain Warehouse Product .

On the tab page Additional GTINs/EANs, you can display, edit, and delete additional GTINs. The Units of Meas. (Units of
Measures) tab page displays in the eld Additional GTINs/EANs exist if additional GTINs exist for a unit of measure of a product
in EWM.

CIF Transfer of Additional GTINs (EANs/UPCs) from SAP ERP

You can download additional GTINs from SAP ERP using Core Interface (CIF) by means of initial transfer or change transfer of
material master data.

 Note
To use this feature, you must activate the business function SCM, CIF Transfer of Additional GTINs (EANs/UPCs) for
Material ( LOG_SCM_MEAN_INT) in SAP ERP. This business function is available as of SAP enhancement package 6 for SAP
ERP 6.0.

 Caution
The additional GTINs (EANs/UPCs) transferred from SAP ERP overwrite the additional GTINs that you have maintained in
EWM.

Identi cation of a Product by Additional GTINs in EWM

If additional GTINs exist in EWM, you can use them to identify products in the functions where the entry of a GTIN (EAN/UPC) is
possible, for example, in product validation using radio-frequency (RF).

Business Partner ID Mapping

Use
When SAP EWM is integrated with an ERP system, the ERP customer and vendor data is mapped to a business partner in the
EWM system. If there a customer and a vendor exist in the ERP system with the same number, it is not possible to create a
business partner in EWM for both of them unless the customer and the vendor are actually the same entity and can be
integrated into a single business partner. This issue also arises if multiple ERP systems are integrated with a single EWM
system.

The following graphic shows mutltiple customers and vendors from various systems with the same number being mapped to a
business partner in EWM, and illustrates the problem that arises there.

This is custom documentation. For more information, please visit the SAP Help Portal 70
 9/2/2022

You can use the business partner ID mapping function to enable EWM to work with customers and vendors that share the same
ERP number. These customers and vendors can be from the same ERP system or from different systems.

To use this feature, you must activate the business function EWM, Essential Foundation Functions (SCM_EWM_FND).

Solving Business Partner ID Con icts

Use
To be able to create business partners for ERP customers and vendors with con icting ID numbers, you must implement a Core
Interface (CIF) Business Add-In (BAdI).

Features
An example implementation for the CIF BAdI Inbound Processing of Business Partners is available. You can copy this to create
your own implementation. The BAdI is used when an entity that is represented by a business partner in EWM is transferred from
the ERP system.

The example implementation handles the following cases:

There is no business partner with the corresponding number. The ERP number is used to create a new one.

There is already a business partner with the corresponding number but with a different partner role and/or from a
different ERP system. In this case a new business partner ID is created.

However, if the new ERP entity and the old one have the same city and street, the system assumes that they are
identical. In this case no new business partner is created. Instead the existing one gets a new role.

There is already a business partner corresponding to the ERP entity that is updated with the ERP data.

This is custom documentation. For more information, please visit the SAP Help Portal 71
 9/2/2022
If a con ict occurs, the new business partner IDs are created from the internal number range of the business partner. The
interval the IDs are drawn from should be distinct from the numbers of the ERP objects. Otherwise arti cial con icts occur if a
number is created that also exists as an ERP number.

 Caution
You should take special care if SCM applications other than EWM run on the same SCM server instance. Users of the other
applications have to work with the business partner IDs that are created. EWM currently displays the ERP numbers in this
case.

Example
The following table shows how the system creates new business partner IDs for con icting ERP customer and vendor numbers.
When the rst customer is transferred the business partner number 1400001701 is not yet in use so a business partner with
that number is created. The vendor from the same system also has the number 1400001701. However, as it is a different entity
to the customer, a new business partner with the ID 0000000010 is created. The same applies to the customer and vendor
from a different ERP system. The business partner ID 1400001701 is already in use so a new one is created.

CIF Sequence ERP Number Role* ERP System BP ID

1 1400001701 CRM002 AA1CLNT001 1400001701

2 1400001701 CRM004 AA1CLNT001 0000000010

3 1400001701 CRM002 BB9CLNT500 0000000011

4 1400001701 CRM004 BB9CLNT500 0000000012

*CRM002 = Customer, CRM004: Vendor

To avoid arti cial con icts, in this example customer and vendor numbers are in the interval from 1400000001 to 1499999999
and the created business partner IDs are in the interval from 0000000001 to 0999999999.

Displaying the ERP Number

Use
Business partner IDs that are created by the CIF BAdI differ from the original ERP numbers. To be able to work with the
customer and vendor numbers of the ERP system, you can customize how business partner IDs are displayed in EWM.

To distinguish between business partners with the same ERP number, the ERP number is displayed together with a
differentiator which makes it unique. This is called the external business partner ID as opposed to the real business partner
number, which is now called the internal business partner number.

In Customizing you can choose a unique differentiator for each relevant combination of business partner role and ERP system.

If there is no differentiator speci ed for a combination of partner role and ERP system, the default mapping is displayed. The
external business partner number is concatenated from the ERP number, the business partner role and the logical system of
the ERP system. Thus the number uniquely identi es a business partner.

Example

This is custom documentation. For more information, please visit the SAP Help Portal 72
 9/2/2022
In the following example the chosen differentiator is a mix of the business partner's original system and the partner role. The
character @ is used as a separator between the ERP number and the differentiator. This is de ned in Customizing.

ERP Number Role* ERP System Internal BP Differentiator External BP ID

Number

1400001701 CRM002 AA1CLNT001 1400001701 AA1C 1400001701@AA1C

1400001701 CRM004 AA1CLNT001 0000000010 AA1V 1400001701@AA1V

1400001701 CRM002 BB9CLNT500 0000000011 BB9C 1400001701@BB9C

1400001701 CRM004 BB9CLNT500 0000000012 BB9V 1400001701@BB9V

*CRM002: Customer

CRM004: Vendor

In the following example the default mapping is used; the external business partner number is concatenated from the ERP
number, the business partner role and the logical system of the ERP system.

ERP Number Role* ERP System Internal BP Number External BP ID

1400001701 CRM002 P9QCLNT001 1400001701 1400001701@CRM002@P9QCLNT001

1400001701 CRM004 P9QCLNT001 0000000010 1400001701@CRM004@P9QCLNT001

1400001701 CRM002 Q57CLNT500 0000000011 1400001701@CRM002@Q57CLNT500

1400001701 CRM004 Q57CLNT500 0000000012 1400001701@CRM004@Q57CLNT500

* CRM002: Customer

CRM004: Vendor

Using the External Business Partner ID

Use
You can display business partner IDs in either of the following ways:

The differentiator is always displayed. This option is recommended if there are a lot of number con icts.

The differentiator is only displayed if the business partner's ERP number is not unique. You can use this option if there
are only a few number con icts.

You control which option to use in Customizing. For the input of business partner numbers you can enter an external business
partner ID without a differentiator as long as it is unique. If you enter a non-unique number the system displays an error
message.

To support you in choosing a business partner number, especially when a non-unique business partner number is entered, the
system provides a new search help. This search help takes the external and the internal business partner number as search
parameters. The usual business partner search options are also available, but here only the internal business partner number is
supported. Range selections on the business partner number work with the following limitations:

This is custom documentation. For more information, please visit the SAP Help Portal 73
 9/2/2022
In some cases the system displays an error message stating that the lower limit is higher than the upper limit. If this
happens we recommend that you use a wildcard search.

As the differentiator is used to make the external BP ID unique, you must not use it as part of wildcard selections. For
example, entering 1400*@AA1C causes the system to search for 1400*.

Because of the mapping between internal and external BP numbers, not all the business partners can be selected if you
specify a range that is too wide. In this case, the system displays an information message. You should specify a narrower
range accordingly.

Customizing Settings for Business Partner ID Mapping

Use
You can control various aspects of the business partner ID mapping in Customizing.

Features
The following options are available in Customizing for SCM Basis under Master Data Business Partner Business Partner ID
Mapping :

Activate the business partner ID mapping. This checkbox controls whether business partner ID mapping is performed at
all and is deactivated by default.

Number conversion always or only if necessary. This option controls whether the full external business partner number is
displayed always or only if there are con icting numbers. If there are only few overlapping numbers the differentiator can
be displayed only if necessary. If overlapping numbers are common it could be more convenient to always display the
differentiator.

Character for the separator. This option speci es the character that is used to separate the ERP number from the
differentiator in the external business partner number. The chosen character must not be part of any ERP number that is
mapped to a business partner as this would lead to an incorrect number conversion.

Mapping of partner role and ERP system to a custom differentiator. Each combination of role and logical system can be
mapped to a custom differentiator that is displayed with the ERP number of a business partner. Each combination of
partner role and logical system, as well as each differentiator has to be unique.

Travel Distance Calculation

The travel distance calculation calculates the travel distance that a warehouse worker must travel to execute a warehouse
order.

Use
The result of the travel distance calculation is used for:

Planning the workers, if you have activated Labor Management (LM). For more information, see Operational Planning.

Calculating engineered labor standards (ELS), if you have activated LM. For more information, see Determination of
Normal Time Using Engineered Labor Standards.

Calculating the latest start time for a warehouse order.

This is custom documentation. For more information, please visit the SAP Help Portal 74
 9/2/2022
In addition to calculating the travel distance, the system determines the travel time required by a worker to execute the
warehouse order. The system calculates the time required based on the speed of the resource used, among other factors. For
more information, see Travel Time Calculation.

Prerequisites
You have activated the travel distance calculation for your warehouse number in Customizing for Extended Warehouse
Management under Master Data De ne Warehouse Number Control .

When Is Travel Distance Calculated?

The system calculates the travel distance needed to execute a warehouse order at the following times:

When a warehouse order is created, for planning purposes.

When a warehouse order is con rmed, for evaluation purposes.

When calculating the distance during warehouse order creation, the system uses the following values:

For the speed, the system uses the speed of the slowest resource (pessimistic approach). This is relevant for the travel
time calculation.

For the distance to be covered in order to reach the rst item of a storage type, the system uses the default distance
which you have speci ed in Customizing for Extended Warehouse Management. This is because the system does not
know which resource will execute the warehouse order, and therefore its position is also unknown.

If a travel network is available, the system uses all de ned routes in the network without resource-type restrictions.

The system can only access more detailed information when the warehouse order is con rmed, as only then is the executing
resource known. The following information is then available:

Speed of the resource (relevant for the travel time calculation).

Last position of the resource prior to executing the warehouse order.

The travel network allowed for the resource, if available.

The system saves the result of the travel distance calculation in the planned workload. If you have activated Labor
Management, the system also saves the result of the travel distance calculation in the executed workload. For more
information, see Labor Management (LM).

Types of Distance
Direct distance

The system can calculate the travel distance using the direct distance, based either on the Euclidean or Manhattan
metric.

The gure below shows the direct distance between two storage bins of a storage type. The solid line represents the
Euclidean metric; the dotted line represents the Manhattan metric.

This is custom documentation. For more information, please visit the SAP Help Portal 75
 9/2/2022

Distance based on networks

The system can calculate the travel distance based on an existing valid network. For more information about networks,
see Networks.

The gure below shows the distance between two storage bins of a storage type. The resource moves across the valid
routes.

Networks
Networks de ne the valid routes (streets) in the warehouse, on which the resources move.

Types of Network

This is custom documentation. For more information, please visit the SAP Help Portal 76
 9/2/2022
A network consists of edges and nodes. Edges are connected to each other by way of nodes. Edges represent the valid routes in
the warehouse, and nodes represent crossings.

The gure below shows a warehouse consisting of different storage types. Each storage type is displayed in a different color.
Storage-type-speci c networks are de ned (with green, blue and gold edges), which are connected to each other by a global
network (red edges).

Hover over each area for a description.

Two different networks exist:

Storage-type-speci c networks, which you de ne for each storage type.

These networks consist of edges corresponding to the aisles of a storage type, and edges that connect these aisles to
each other. In the example above, these are the green, blue and gold edges.

You assign storage bins of a storage type to:

An edge, if they are located in an aisle, and an edge exists for the aisle.

A node that matches your X and Y coordinates, or lies close to them in terms of the chosen metric (Euclidean or
Manhattan metric), if you have not assigned an edge.

Global network

The global network connects the de ned, storage-type-speci c networks to each other. If no storage-type-speci c
networks are de ned, it connects the storage bins to each other directly. In the example above, these are the red edges.

The edges have the following properties:

Each edge has a start node and end node.

This is custom documentation. For more information, please visit the SAP Help Portal 77
 9/2/2022
An edge is usually passable in both directions, however it can also be de ned as a one-way street. The direction is
de ned through the start and end nodes.

For each edge, you can de ne which resource types are allowed to pass.

You can assign an edge to an aisle.

An edge has a length that is used by the system to calculate the travel distance, if a resource passes along the edge.

A network is valid if every node can be reached from every other node. The system calculates the validity for each resource type.
The global network is valid if every node of a valid storage-type-speci c network can be reached from every other node of a valid
storage-type-speci c network. The travel distance calculation only uses valid networks. The system ignores edges in invalid
networks.

How to Create Your Networks

There are several methods available for you to create your networks:

You can create both global and storage-type-speci c networks in the settings for the travel distance calculation. For
more information, see Settings for the Travel Distance Calculation.

You can generate storage-type-speci c networks using the Generate Network transaction. For more information, see
Generate Storage-Type-Speci c Networks.

You can upload CSV les containing your network data. For more information, see Upload Travel Distance Network.

How to Verify Your Networks

You can use the Travel Distance Evaluation transaction to check travel paths between two bins in your travel distance network
(for example, to verify your travel distance network). The travel path is displayed as a list of sections. When you click on the
message log icon, you can see more details about the travel distance calculation.

On the SAP Easy Access screen, choose Extended Warehouse Management Settings Travel Distance Calculation Travel Path
Evaluation .

1. Enter your warehouse number.

2. Enter two bins.

3. If you want travel time information to be included in the message log, you can additionally specify the executing resource
and whether or not it is unloaded.

4. Choose either the Euclidean metric or Manhattan metric.

Settings for the Travel Distance Calculation

You use this function to de ne edges for global and storage-type-speci c networks and the average distance between storage
type and resource. The validity of the networks for each resource type is also displayed.

Features
On the SAP Easy Access screen, choose Extended Warehouse Management Settings Travel Distance Calculation Settings for
the Travel Distance Calculation.

You can make the following settings for storage-type-speci c networks:

This is custom documentation. For more information, please visit the SAP Help Portal 78
 9/2/2022
De ne average distance for warehouse number and storage type

De ne edges in storage-type-speci c networks:

X and Y coordinates for the start of the network

X and Y coordinates for the end of the network

De ne edge direction (unidirectional, bidirectional)

De ne aisle (optional)

De ne edge length in the unit of length of the warehouse number

De ne excluded resource types

The validity of the networks for each resource type is displayed.

You can make the following settings for global networks:

For edges in the global network:

X and Y coordinates for the start of the edge

X and Y coordinates for the end of the edge

De ne edge direction (unidirectional, bidirectional)

De ne edge length in the unit of length of the warehouse number

De ne excluded resource types

The validity of the networks for each resource type is displayed.

Generate Storage-Type-Speci c Networks

You can use the program Generate Network to automatically generate storage-type-speci c networks for the travel distance
calculation in Extended Warehouse Management.

Context
You can de ne networks:

For aisles only

For aisles and their connecting edges

The edges for the aisles have the following properties:

Edges are only created for aisles that have more than one storage bin.

Edges can be passed in both directions.

The length of the edges corresponds to the Euclidean distance between the start and end nodes.

If storage bins are located on both sides of the aisle, the edges are located in the center of the aisle.

If there are only storage bins on one side of the aisle, the edges lie half a bin depth away from the aisle.

The edges start and end outside the aisle (half a bin depth).

This is custom documentation. For more information, please visit the SAP Help Portal 79
 9/2/2022
The system generates connecting edges between neighboring aisles by connecting both the start and end nodes of two
neighboring aisles with an edge.

Procedure
1. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Travel Distance
Calculation Generate Network.

2. Select from the following criteria:

Warehouse number

Storage type

Indicate whether you want to generate edges for aisles only, or for an entire network

3. The following information is available from the storage bins:

Aisle attribute for grouping storage bins and allocating edges. The system generates an edge for each aisle.

The X and Y coordinates of the storage bins (these de ne the bottom left corner of a storage bin) are there to
position the start and end nodes of the edges.

The system uses the breadth and depth of the storage bin type to de ne the center of the aisle and the distance
between the edge and the aisle.

4. The system writes a log for edge generation.

Upload Travel Distance Network

You use this function to upload edges and excluded resource types per edge. This information de nes your global and storage-
type-speci c networks.

Procedure
1. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Travel Distance
Calculation Upload Travel Distance Network .

2. Select the warehouse number for which you want to maintain the travel distance network. Specify whether you want to
change the storage type-speci c networks and/or the global network.

3. In the section Upload Object, select whether you want to upload edges or excluded resource types.

4. Choose your upload settings, for example, whether you want to replace the existing data for the networks selected in
step 2 with the uploaded data or only add new edges.

5. Select and upload a CSV le.

Your CSV le for edges should have the following data format per domain:

Storage Edge ID X Cood. Y Coord. X Coord. Y Coord. Direction Length Aisle

Type Start Start End End

CHAR(4) NUMC(10) DEC(10,3) DEC(10,3) DEC(10,3) DEC(10,3) CHAR(1) DEC(10,3) CHAR(18)

For global edges, leave the storage type eld empty.

Specify the edge ID yourself. Edge IDs must be unique on warehouse level.

Your CSV le for excluded resource types per edge should have the following data format per domain:

This is custom documentation. For more information, please visit the SAP Help Portal 80
 9/2/2022

Storage Type Edge ID Resource Type

CHAR(4) NUMC(10) CHAR(4)

6. Optional: Perform network checks by clicking Check Network Before Data Transfer.

How Travel Distance Is Calculated

The travel distance is calculated for the storage bin list. The system generates the list of storage bins from the warehouse
order creation rules. The order is xed, meaning the travel distance calculation does not change the sequence of storage bins.

Horizontal and Vertical Movements

The system differentiates between horizontal (X and Y coordinates) and vertical movements (Z coordinates).

For the movements, we assume that:

The resource visits each storage bin in the sequence de ned by the list.

The resource executes the horizontal movement rst, meaning the resource rst moves to the storage bin in a
horizontal direction.

The resource then executes the vertical movement, namely the movement from the oor to the bin and back.

The resource then moves to the next storage bin in a horizontal direction.

The total travel distance in a vertical direction therefore corresponds to twice the Z distance of the storage bins to the oor
(point of origin Z = 0).

For the horizontal movements, three types of distance in uence the calculation: the direct distance, the distance between a bin
and a node, and movements within a network.

Direct Movement Between Bins

The system uses the direct distance:

For movements between storage bins within a storage type, if no valid storage-type-speci c network exists.

For movements between storage bins from different storage types, if no global valid network exists.

For movements within an aisle. Here, the system uses the direct distance between storage bins to calculate the travel
distance.

This gure shows examples for travel distances between multiple storage bins within an aisle. The green line represents the
Euclidean metric; the dotted blue line represents the Manhattan metric.

This is custom documentation. For more information, please visit the SAP Help Portal 81
 9/2/2022

Distance Between a Bin and a Node in the Network

Storage bins are connected to the network using either of the following:

Using the nearest node, if no edge has been assigned to the storage bin. The node comes from the storage-type-speci c
network, or if this does not exist, the global network.

Calculating the travel distance using the nearest node, if no edge is assigned to the storage bins

Using the nodes of an edge, if the storage bin is in an aisle, and an edge exists for the aisle.

This is custom documentation. For more information, please visit the SAP Help Portal 82
 9/2/2022

Calculating the travel distance using the nodes of an edge, if one storage bin is in an aisle and an edge exists for the aisle, and then
moving to the nearest node, if no edge has been assigned to the second storage bin

Fundamentally, there are four options. However, for a one-way route, only one option is allowed: entering the edge at the
start node and leaving it at the end node.

This gure displays how a bin sequence within an aisle can be connected with the node or nodes of the respective edge.
As stated in the section above, the edge itself is not used for the calculation within an aisle, because the direct distance
is used between storage bins.

This is custom documentation. For more information, please visit the SAP Help Portal 83
 9/2/2022

Movements Within a Network

These take place if the storage bins:

Lie in the same storage type but not in the same aisle, and a valid storage-type-speci c network exists.

Are in different storage types and a valid global network exists.

When calculating movements within the valid global network and any valid storage-type-speci c networks, the system:

1. Connects the storage bins with the nodes of the respective edge or with the nearest node.

2. Adds the travel distance between the assigned nodes. If a bin is assigned to the nodes of an edge, there are several
possible options for calculating the network distance.

Example: Both bins are assigned to different edges, which are not one-way routes. There are four options:

From the start node of the rst edge to the start node of the second edge

From the start node of the rst edge to the end node of the second edge

From the end node of the rst edge to the start node of the second edge

From the end node of the rst edge to the end node of the second edge

This gure shows the different connections between edges (black lines), edge and node (black dots), and possible connections
between the assigned nodes (green lines). The system uses the option with the shortest travel distance.

Examples for the Travel Distance Calculation

Example 1: Travel Distance Calculation Within a Storage Type

The warehouse manager wants to calculate the travel distance from storage bin 1 to storage bin 3 within a storage type with a
valid network (green edges). 1, 2, and 3 are storage bins at which warehouse worker X withdraws goods.

This is custom documentation. For more information, please visit the SAP Help Portal 84
 9/2/2022
The travel distance comprises the following:

Direct distances A (within an aisle), B and D (connection between storage bin and network)

Distance C (connecting edge) within the network.

Of the four possible calculations, the system uses the rst option, as that represents the shortest travel distance.

Option one for calculating travel distance from 1 - 3

Option two for calculating travel distance from 1 - 3

This is custom documentation. For more information, please visit the SAP Help Portal 85
 9/2/2022
Option three for calculating travel distance from 1 - 3

Option four for calculating travel distance from 1 - 3

Example 2: Travel Distance Calculation Between Two Storage Types with Valid
Networks
This example shows a travel distance calculation between two storage types that each have a valid, storage-type-speci c
network (green and blue edges) and a valid, global network (red edges).

This is custom documentation. For more information, please visit the SAP Help Portal 86
 9/2/2022

The travel distance comprises the direct distances A and C (connection between storage bin and network) and distance B within
the entire network (local and global).

Example 3: Travel Distance Calculation Between Two Storage Types with a Global
Valid Network
This example shows the travel distance calculation between two storage types with a valid global network (red edges). Only one
storage type (green) has a valid network (green edges).

The travel distance comprises the direct distances A and C (connection between storage bin and network) and distance within
network B.

This is custom documentation. For more information, please visit the SAP Help Portal 87
 9/2/2022

Heuristics for the Travel Distance Calculation

Use

Two heuristics for the travel distance calculation within a network exist. The system calls both by default. You can control the
heuristics using the Business Add-Ins (BAdIs) for the travel distance calculation.

Depth- rst search

The system attempts to nd a route between the speci ed nodes of a network in the shortest time possible. Here, the
search runs in the direction of start node to end node. The search nishes when the rst complete route is found.

Breadth- rst search

The system looks for all possible routes in the network, and selects the one that has the shortest distance. This heuristic
is more performance intensive at runtime, and is only appropriate for small networks.

Stopping criterion

The stopping criterion quickens the breadth- rst search. This may have a negative impact on the solution quality, and the
system may fail to nd the shortest route. The parameter restricts the number of nodes that can be visited by a route, in
relation to the route found by the depth- rst search.

Travel Time Calculation

The system uses the travel distance and other information to determine the time required by a worker to execute a warehouse
order.

Default Travel Time Calculation

By default, the total travel time is calculated as follows. You can nd the result in the message log in Travel Path Evaluation and
in the planned workload. If you have activated Labor Management, you can also nd it in the executed workload.

Total travel time = Horizontal travel time + Vertical travel time

The horizontal travel time and vertical travel time are calculated as follows:

Horizontal travel time = Total horizontal travel distance / Horizontal resource type speed

Vertical travel time = Total vertical travel distance / Vertical resource type speed

If you want to use a more complex travel time calculation, you can maintain your own set of calculation rules in BRFplus. For
more information, see Con guring the Travel Distance Calculation and Travel Time Using BRFplus.

EWM provides a standard BRFplus application /SCWM/TDC_SYS and function /SCWM/TDC_CALC_TIME to which you can assign
your own rulesets. The interface of the standard function includes the following:

The total horizontal travel distance

The total vertical travel distance

Consolidated section information of horizontal movements

Section information of vertical movements

Resource type information (such as speed)

This is custom documentation. For more information, please visit the SAP Help Portal 88
 9/2/2022
Business information (such as activity area)

When you de ne your own rules, you can use any or all of the above information as input.

Consolidated Section Information

In contrast to the total travel distance, consolidated section information lets you consider each section of the calculated travel
path separately. For example, you might want to consider turns and stops in the travel path, because they limit the maximum
speed of a resource. The shorter a straight segment is, the less likely it is for the resource to travel at its maximum speed.

Technically, a travel path is de ned as a list of points. These points can either be nodes (N) of edges or bins (B). A pair of
consecutive points de nes a section of the travel path. Two consecutive sections de ne a turn angle for the resource.
Sometimes, the turn angle is zero, which indicates that both involved sections can be consolidated into one straight section.
However, if the shared point of both sections is a bin - where the resource needs to stop - the sections cannot be consolidated,
even if the turn angle is zero.

The above gure demonstrates how sections are consolidated. Sections S1 and S2 cannot be consolidated as there is a turn in
between. Sections S2 and S3 cannot be consolidated as there is a bin in between. However, the two sections following S4 can be
consolidated into S5.

Examples for the Travel Time Calculation

The following examples demonstrate ways to de ne rules that are assigned to the EWM standard function
/SCWM/TDC_CALC_TIME.

Example 1
We use the following information from the function interface:

The total horizontal travel distance

The total vertical travel distance

This is custom documentation. For more information, please visit the SAP Help Portal 89
 9/2/2022
The horizontal resource type speed

The vertical resource type speed

In BRFplus we de ne the following formulas:

Total travel distance = Horizontal travel time + Vertical travel time

Horizontal travel time = Total horizontal travel distance / Horizontal resource type speed

Vertical travel time = Total vertical travel distance / Vertical resource type speed

The horizontal travel distance is 5 metres. The horizontal resource type speed is 5m/s. The vertical travel distance is 1 metre.
The vertical resource type speed is 0.5m/s. The total travel time is therefore 3 seconds:

5/5 + 1/0.5 = 3

Example 2
We use the following information from the function interface:

The list of consolidated sections

Section Length Further information

S1 2m ...

S2 4m ...

S3 6m ...

The horizontal resource type speed

The list of vertical movements

Section Length Further information

S1 1m ...

S2 1m ...

S3 0.5m ...

S4 0.5m ...

The vertical resource type speed

We can then de ne a loop expression in BRFplus over the consolidated horizontal sections and de ne the following formula to be
used in every iteration:

Total horizontal travel time = Total horizontal travel time + (Current section in iteration / Horizontal resource type speed) + 2s

In this simpli ed model, we add 2 seconds to the time needed for each section, to account for turns.

For the total vertical travel time, we can de ne a loop expression over the consolidated vertical sections and use a similar
formula in every iteration:

This is custom documentation. For more information, please visit the SAP Help Portal 90
 9/2/2022
Total vertical travel time = Total vertical travel time + (Current section in iteration / Vertical resource type speed) + 1s

Assuming a horizontal resource type speed of 2m/s and a vertical resource type speed of 0.5m/s, we arrive at a total travel
time of 22 seconds.

Horizontal: 2/2+2+4/2+2+6/2+2 = 3+4+5 = 12

Vertical: 1/0.5+1+1/0.5+1+1/1+1+1/1+1 = 3+3+2+2 = 10

BAdIs for the Travel Distance and Travel Time Calculation

Business Add-Ins (BAdIs) are available for you de ne your own logic for the travel distance and travel time calculations.

Available BAdIs
The following BAdIs are available in enhancement spot /SCWM/ES_TDC:

BAdI: Change Storage Bin List for Travel Distance Calculation /SCWM/EX_TDC_BIN_LIST

You can do the following:

Sort the list.

Delete storage bins from the list.

Add new storage bins to the list.

In uence the default distance to the rst storage bin in the storage bin list.

BAdI: Travel Distance Calculation Using Storage Bins /SCWM/EX_TDC_START

The system calls this BAdI to calculate the travel distance of a warehouse order. If you implement this BAdI, you can
de ne your own logic for calculating the travel distance along the sorted storage bin list transmitted to the BAdI.

BAdI: Travel Time Calculation /SCWM/EX_TDC_BRF_CALC_TIME

You can implement this BAdI to de ne your own logic for the travel time calculation or to determine how travel time is
calculated. For more information, see Con guring the Travel Distance Calculation and Travel Time Using BRFplus.

For more information about these BadIs, see Customizing for Extended Warehouse Management, under Business-Add-Ins
(BAdIs) for Extended Warehouse Management Cross-Process Settings Travel Distance Calculation .

Warehouse Management Monitor

Use
The warehouse management monitor is a central tool for keeping warehouse managers constantly up-to-date as to the current
situation in the warehouse, and to enable them to initiate appropriate responses in light of this situation.

The warehouse management monitor also contains alert monitoring capabilities, which highlight to warehouse managers actual
and potential problematic situations in the warehouse, and provide exception handling tools.

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 91
 9/2/2022
You have accessed the warehouse management monitor by:

1. Choosing Extended Warehouse Management Monitoring /SCWM/MON - Warehouse Management Monitor on the SAP
Easy Access screen.

2. Entering the warehouse number and name of the monitor.

3. Choosing Execute.

Features
Node Hierarchy Tree

Node Hierarchy Tree

The node hierarchy tree contains all of the prede ned nodes representing different object classes.

The tree is used solely for navigation purposes. You can use the hierarchy tree to display in the upper view area object
information for a speci c node, based on selection criteria.

The warehouse management monitor contains nodes for object classes relating to the following:

Documents such as warehouse requests, warehouse orders, warehouse tasks, and physical inventory documents

Processes such as stock and bin, and resource management (see Resource Management)

This is custom documentation. For more information, please visit the SAP Help Portal 92
 9/2/2022
Alerts such as overdue waves (see Wave) or overdue deliveries without goods issue or goods receipt

Drilldown Capabilities

After displaying in the upper view area object information for a node, you can drill down and display the object information for its
lower-level nodes, using designated buttons.

You can similarly drill down to the lower-level nodes from the lower view area.

List and Form Views

By default, object information is displayed as a list view. The list view is displayed in an ALV grid, and offers all standard ALV
functionalities, including sorting, ltering and printing.

You also have the option of toggling to form view for a selected object. The form view provides a focused view of the object, and
provides more detailed information than the list view. The form view is displayed in an HTML viewer.

Methods

After object information is displayed in either view area, you can call methods to perform actions on selected objects. For more
information about the available methods, see Monitor Methods.

Automatic Refresh

You can set a default automatic refresh for all displayed nodes in the warehouse management monitor. You can also set an
automatic refresh for speci c displayed nodes. You specify the refresh interval in minutes and it is speci c to your user. For more
information, see Automatic Refresh.

Customizing Options

You can use the standard SAP monitor or you can create your own monitor in Customizing.

For more information about creating your own monitor, see Customizing for Extended Warehouse Management under
Monitoring Warehouse Management Monitor .

If you use the standard SAP monitor, you can tailor it to your needs by either creating variants for the standard nodes or
creating new variant nodes based on the standard nodes, as follows:

Creating variants for the standard nodes enables you to use prede ned selection criteria while running a session
of the monitor. The variant-node assignments are lost when you close the monitor session.

Creating variant nodes enables you to create your own nodes, which are based on the standard nodes, but with
speci c selection criteria, or with a speci c layout. Variant nodes are always available when the user uses the
monitor.

There may be a high memory consumption in the warehouse management monitor per user because of, for example,
queries resulting in large result lists or an extended use of the warehouse management monitor. To counteract this, you
can use BAdI: Monitor Memory Consumption Check to enforce an automatic restart of the warehouse management
monitor.

For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for
Extended Warehouse Management Monitoring Warehouse Management Monitor BAdI: Monitor Memory Consumption
Check .

Monitor Basic Operations

This is custom documentation. For more information, please visit the SAP Help Portal 93
 9/2/2022

Functions

Function What You Should Know

Hide a selected node in the hierarchy tree This operation is invoked by choosing the Hide Node option in the
node's context menu.

Show hidden nodes This operation is invoked by choosing Show Hidden Nodes.

After choosing this option, previously hidden nodes are displayed

in the hierarchy tree.

Unhide a selected node in the hierarchy tree This operation is invoked by choosing the Unhide Node option in
the node's context menu.

Create a variant node in the hierarchy tree There are two options from the node's context menu:

Create Variant Node for Current Level creates a variant

node directly underneath the original node.

Create Variant Node for Category Level creates a variant

node under the original node, on the same level as the
node's category.

When creating the variant node, you have the following execution
options:

Execute creates only the variant node based on the source

node.

Execute with Sub-Tree creates the variant node, as well as

all of the same lower-level nodes as are contained in the
source node

After creating the variant node, you can create a variant for
selection criteria, as well as assign a layout variant to it.

Delete variant node This operation is invoked by choosing the Remove Node option in
the node's context menu.

Change variant node text This operation is invoked by choosing the Rename Node option in
the node's context menu.

Display in list view object information for a node This operation is invoked either by double-clicking the node, or
choosing the Set Selection Criteria option in the node's context
menu.

Expand all nodes in the hierarchy tree This operation is invoked by choosing the Expand All icon in the
top tool bar.

Collapse all nodes in the hierarchy tree This operation is invoked by choosing the Collapse All icon in the
top tool bar.

Display object information of a lower-level node in the higher-level This operation is invoked by selecting a row in the ALV, and
node's list view choosing the button corresponding to the lower-level node.

Information on the lower-level objects appears in the bottom list

view.

Toggle between list and form views You call this operation by selecting one or more rows in the ALV and
choosing the Form View icon from the list view tool bar.

You can toggle back from form view to list view by choosing the List
View icon again.

This is custom documentation. For more information, please visit the SAP Help Portal 94
 9/2/2022

Function What You Should Know

Show display transaction for object For some objects, such as warehouse task, warehouse order, wave,
inbound delivery, outbound delivery, and storage bin, you can go
directly to the relevant display transaction. You call this function by
choosing the required object in the ALV, which in this case is
indicated by a hotspot. For some objects, you can select multiple
rows, and use the ALV tool bar to branch to the display transaction
of multiple objects of the same type. The display transaction is
shown in a new session. If you set the parameter /SCWM/MONNAV
to X in the user pro le, the display is started in the same session.

Schedule jobs to collect SAP Extended Warehouse Management This operation is invoked by choosing the Process in Batch
(SAP EWM) monitor data in batch processing, stored in spool (Spool) option in the node’s context menu.

Schedule jobs to collect SAP EWM monitor data in batch This operation is invoked by choosing the Process in Batch option
processing, stored in SAP EWM data container in the node’s context menu.

Show batch processing data from SAP EWM data container This operation is invoked by choosing the Show Batch Processing
Data option in the node’s context menu.

Administer batch processing data in SAP EWM data container This operation is invoked by choosing the Administer Batch
Processing Data option in the node’s context menu.

Show selection screen of a selection variant of a variant node If you assign a selection variant to a variant node, you now can
decide if the selection screen should be shown and if it can be
changed before the node execution.

This operation is invoked by choosing Assign Selection

Variant With Showing Selection Screen in the variant node’s
context menu.

Store changed splitter sizes This operation is invoked when you leave the monitor by choosing
Exit or Cancel.

Hide monitor tree This operation is invoked by choosing the Fullscreen On/Off
option.

Navigate using custom hotspots To use this function, you must implement the Business Add-In
(BAdI) Custom Implementation of a Monitor Hotspot.

Con rm method execution This operation is invoked by the Dialog eld in the Customizing
activity De ne Object Class Methods.

Automatically refresh nodes This operation is invoked for all nodes by specifying the refresh
interval in minutes in the Warehouse Management Monitor dialog
box when you rst open the warehouse management monitor.
Alternatively, by choosing in the warehouse management
monitor and specifying the refresh interval.

This operation is invoked for a speci c node by choosing Set

Refresh Interval in the node’s context menu and specifying the
refresh interval in minutes.

Monitor Methods

Use
The warehouse management monitor methods enable you to manage and control warehouse objects and processes. The
methods are assigned to object classes, and carried out on speci c objects within the object classes. They are implemented by

This is custom documentation. For more information, please visit the SAP Help Portal 95
 9/2/2022
utilizing function modules from content providers responsible for the object classes.

Prerequisites
You have de ned object class methods and their presentation in Customizing for Extended Warehouse Management under
Monitoring Warehouse Management Monitor De ne Object Class Methods .

 Note
Methods are included in the standard delivery. The methods are displayed as standard with the accumulated methods menu
buttons.

Features

Object Object Class Method Name Method Description Remark

Class Description
Name

ALDITI Alert Inbound Delivery /SCWM/INSP_MON Display Inspection -

Item Document

ALDITO Alert ODO Item /SCWM/WAVEMON_ASSIGN Assign to Wave Enables you to assign one or
more selected outbound
delivery order items to a
speci ed wave.

ALID Inactive Delivery /SCWM/WIP_INAC_DELIV_DOC_ACT Activate + Save -

Document Delivery Doc.

/SCWM/WIP_INAC_DELIV_DOC_REJ Reject + Save Delivery -

Doc.

ALTO Alert Warehouse Task /SCWM/WO_CREATION_SIMULATE_MON Simulate WO Creation Enables you to simulate WO
(WT) creation for one or more
selected WTs, based on a
speci ed WO creation rule.
If no WO creation rule is
speci ed, the system
attempts to determine one
pursuant to the search
sequence for WO creation
rules per activity area.

/SCWM/TO_LOG_DISPLAY_MON Display WT Log -

This is custom documentation. For more information, please visit the SAP Help Portal 96
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WO_SPLIT_MON Split WT from WO Enables you to unassign one

or more WTs from a WO, and
group them into a newly
created WO. Using this
method, you can determine
the WO creation rule. If no
WO creation rule is
speci ed, the system
attempts to determine one
pursuant to the search
sequence for WO creation
rules per activity area. You
can also specify a reason for
the split, which is stored in
the exception log for WOs.

/SCWM/WO_TO_UNASSIGN_MON Unassign WT from WO Enables you to unassign one

or more selected WTs from
a speci ed WO.

 Note
To execute the WTs, you
need to assign them to a
WO.

/SCWM/WO_TO_ASSIGN_MON Assign WT to WO Enables you to assign one or

more selected WTs to a
speci ed WO.

/SCWM/TO_CONF_FG_MON Con rm WT in Enables you to con rm in

Foreground the foreground one or more
selected WTs (transaction
/SCWM/TO_CONF).

/SCWM/TO_CONF_BG_MON Con rm WT in Con rms in the background

Background one or more selected WTs.

/SCWM/TO_CANCEL_BG_MON Cancel WT Enables you to cancel a WT.

/SCWM/TO_REPRINT_MON Re-Print Warehouse Enables you to reprint WT

Task details.

/SCWM/TO_SHOW_ALERT_MON Show Exceptions Shows alerts for WTs with

exceptions if available.

/SCWM/TO_QUAN_VALUE_DISP_MON Show Value Enables you to display the

value of moved goods for
con rmed WTs if available.

ALWAVE Alert Wave /SCWM/WAVEMON_HOLD Lock Wave Release Sets the status of the
selected waves to On Hold.

Waves of this status cannot

be released until their status
is changed back to Initial

This is custom documentation. For more information, please visit the SAP Help Portal 97
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WAVEMON_UNHOLD Unlock Wave Release Sets the status of the

selected waves to Initial.

 Note
You can perform this
method only on waves of
status On Hold.

/SCWM/WAVEMON_DELETE Delete Wave Deletes the selected waves.

All the wave items are

unassigned from the waves.

/SCWM/WAVEMON_MERGE Merge Wave Merges the selected waves

into one wave.

The merged wave inherits

its attributes from the rst
wave.

/SCWM/WAVEMON_SUBSYS Transfer Wave to Sub- Activates the WOs and WTs

System sent to a subsystem.

/SCWM/WAVEMON_SHOW_REL_LOG Display Release Log -

/SCWM/WAVEMON_RELEASE Release Wave Releases one or more

selected waves.

 Note
You can release only
those waves of status
Initial.

/SCWM/WAVEMON_RELEASE_HOLD Release Wave locked Releases one or more

selected waves, but the
warehouse orders stay in
status locked.

 Note
You can release only
those waves of status
Initial.

/SCWM/WAVEMON_RELEASE_SINGLE Release Single Wave Releases one or more

selected waves as
separated waves.

 Note
You can release only
those waves of status
Initial.

This is custom documentation. For more information, please visit the SAP Help Portal 98
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WAVEMON_RELEASE_HOLD_SGL Release Single Wave Releases one or more

locked selected waves as
separated waves, but the
warehouse orders stay in
status locked.

 Note
You can release only
those waves of status
Initial.

ALWO Alert Warehouse /SCWM/WO_LOG_DISPLAY_MON Display WO Log -

Order (WO)
/SCWM/WO_MERGE_MON Merge Warehouse Enables you to merge
Orders selected open WOs, which
unassigns the WTs from the
WOs, and groups them into
a newly created WO. Using
this method, you can
determine the WO creation
rule. If no WO creation rule is
speci ed, the system
attempts to determine one
pursuant to the search
sequence for WO creation
rules per activity area. You
can also specify a reason for
the merge, which is stored in
the exception log for WOs.

/SCWM/WO_PRINT_MON Print Warehouse Enables you to print WO

Order details.

/SCWM/WO_REPRINT_MON Re-Print Warehouse Enables you to reprint WO

Order details.

/SCWM/WO_HOLD_MON Lock Warehouse Sets the status of one or

Order more selected WOs to
Waiting.

The WO cannot be executed

until its status is set to
Open.

/SCWM/WO_UNHOLD_MON Unlock Warehouse Sets the status of one or

Order more selected WOs to
Open.

/SCWM/WO_ADD2SWHO Add WO to Adds an empty WO to a

Load/Unload Super super WO (in a loading or
WO unloading scenario).

/SCWM/WO_CONF_FG_MON Con rm WO in Enables you to con rm in

Foreground the foreground one or more
selected WOs (transaction
/SCWM/TO_CONF).

This is custom documentation. For more information, please visit the SAP Help Portal 99
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WO_CONF_BG_MON Con rm WO in Con rms in the background

Background one or more selected WOs.

/SCWM/WO_CANCEL_MON Cancel WO Cancels one or more

selected WOs and their
WTs.

/SCWM/RSRC_WO_RSRC_ASSIGN_MON Assign to Resource Enables you to assign a

resource to one or more
selected WOs.

/SCWM/RSRC_WO_RSRC_UNASIN_MON Unassign from Enables you to unassign a

Resource resource from one or more
selected WOs.

/SCWM/RSRC_WO_QUEUE_CHANGE_MON Change Queue Enables you to change the

queue to which the selected
WOs are assigned.

/SCWM/RSRC_WO_LSD_CHANGE_MON Change LSD Enables you to change the

latest starting date (LSD) of
the selected WOs.

BIN Storage Bin /SCWM/BIN_DISPLAY_MON Display Storage Bin Displays data for the
selected storage bin
(transaction /SCWM/LS03).

/SCWM/BIN_CHANGE_MON Change Storage Bin Enables you to change data

of the selected storage bin
(transaction /SCWM/LS02).

/SCWM/BIN_PUT_BLOCK_MON Block for Putaway -

/SCWM/BIN_PUT_FREE_MON Unblock Putaway -

/SCWM/BIN_PICK_BLOCK_MON Block Stock Removal -

/SCWM/BIN_PICK_FREE_MON Unblock Stock -

Removal

/SCWM/BIN_BLOCK_MON Block -

/SCWM/BIN_FREE_MON Unblock -

DDATES BBD/SLED Overview /SCWM/STOCK_CAT_CHANGE_MON Change stock type -

/SCWM/CALL_POST_MON Post stock Enables you to create a

posting change (transaction
/SCWM/POST).

EWL Executed Workload /SCWM/EWRKL_MTH_CALL_OBJ Display reference -

document

/SCWM/EWRKL_MTH_MOD Modify Workload -

/SCWM/EWRKL_MTH_CRE Create indirect Labor -

Task

/SCWM/EWRKL_MTH_HIST View history -

EXCCD Exception /SCWM/EXCCODE_MTH_DISPLAY_REF Display Reference -

This is custom documentation. For more information, please visit the SAP Help Portal 100
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

HU Handling Unit /SCWM/HU_PRINT_MON Print Handling Unit Enables you to print HU

details.

/SCWM/HU_REPRINT_MON Re-Print Handling Unit Enables you to reprint HU

details.

/SCWM/STRGCNTRL_CREA_PR_WT_MON Create product WTs Creates product WTs for

HUs with process-oriented
storage control.

/SCWM/HU_DELETE_MON Delete HU Deletes selected HUs. HUs

and sub-HUs are unpacked
if applicable.

/SCWM/HU_CREATE_WT_MON Create Warehouse Enables you to create an

Task Adhoc-WT for the HU
(transaction /SCWM/ADHU).

/SCWM/QUIT_STORAGE_CNTRL_MON Quit Storage Control -

ILT Indirect Labor Task /SCWM/ILT_MTH_DISPLAY Display Indirect Labor -

Task

INSP Inspection /SCWM/QI_INSPDOC_UI_CALL Disp. Inspection Doc -

/SCWM/QI_INSPDOC_RELEASE Release Inspection -

Doc.

INSPST Workstation for q- /SCWM/QI_INSPDOC_UI_CALL2 Disp. Inspection Doc -

inspection

LAMA_P Processor /SCWM/WIP_PRR_MTH_DISPLAY Display Processor -

Master

/SCWM/WIP_PRR_MTH_PROCSA_CH Assign to Ext. Process -

Step

/SCWM/WIP_PRR_MTH_PROCSA_DL Del. Assignment to -

Ext. Step

/SCWM/WIP_PRR_MTH_GRA_CH Assignment to Group -

/SCWM/WIP_PRR_MTH_GRA_DL Del. Assignment to -

Group

/SCWM/WIP_PRR_MTH_BSKEYA_CH Change HR System -

/SCWM/WIP_PRR_MTH_PPROCSA_CH Asgn Standard Ext. -

Proc. Step

/SCWM/WIP_PRR_MTH_PAAREA_CH Assign Standard Area -

/SCWM/WIP_PRR_MTH_LOCA_CH Assign to Warehouse -

/SCWM/WIP_PRR_MTH_LOCA_DL Delete Assignment to -

Warehouse

/SCWM/WIP_PRR_MTH_SCUNITA_CH Assign Supply Chain -

Unit

LUTILD Labor Utilization Detail /SCWM/EWRKL_MTH_CALL_OBJ Display reference -

document

This is custom documentation. For more information, please visit the SAP Help Portal 101
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/EWRKL_MTH_MOD Modify Workload -

/SCWM/EWRKL_MTH_CRE Create indirect Labor -

Task

/SCWM/EWRKL_MTH_HIST View history -

MFSCCH Communication /SCWM/MFS_CCH_START_MON Start Channel -

Channel
/SCWM/MFS_CCH_STOP_MON Stop Channel -

/SCWM/MFS_CCH_RESET_SQSND_MON Reset Send SeqNo Resets sequential number

for outgoing telegrams.

/SCWM/MFS_CCH_RESET_SQRCV_MON Reset Receive SeqNo Resets sequential number

for incoming telegrams.

MFSCP Communication Point /SCWM/MFS_CP_SET_EXCC_MON Set Exception -

/SCWM/MFS_CP_QRY_STAT_MON Send Status Request -

/SCWM/MFS_CP_WT_DET_MON Trigger Telegram -

Processing

MFSCS Conveyor Segment /SCWM/MFS_CS_SET_EXCC_MON Set Exception -

MFSCSG Conveyor Segment /SCWM/MFS_CSGR_SET_EXCC_MON Set Exception -

Group

MFSDY Outgoing Telegram /SCWM/MFS_MFSDELAY_EDIT_MON Edit -

/SCWM/MFS_MFSDELAY_DEL_MON Delete -

/SCWM/MFS_MFSDELAY_PROC_MON Process Telegram -

MFSHU Handling Unit /SCWM/MFS_HU_SET_MFSERR_MON Set MFS error -

/SCWM/MFS_HU_WT_DET_MON Trigger Telegram -

Processing

MFSRS Resource /SCWM/MFS_RSRC_SET_EXCC_MON Set Exception -

/SCWM/MFS_RSRC_SET_COUNTER_MON Recalculate WTs -

/SCWM/MFS_RSRC_QRY_STAT_MON Send Status Request -

/SCWM/MFS_RSRC_WT_DET_MON Trigger Telegram -

Processing

MFSTG Telegram /SCWM/MFS_RESEND_TELEGRAM_MON Resend Telegram -

/SCWM/MFS_TELE_SIMULATE_MON Simulate Telegram -

MFSTQ Incoming Telegram /SCWM/MFS_MFSTELEQ_EDIT_MON Edit -

/SCWM/MFS_MFSTELEQ_DEL_MON Delete -

/SCWM/MFS_MFSTELEQ_PROC_MON Process Telegram -

MQUEUE Message Queue /SCWM/MSG_LOG_DISPLAY Application Log -

/SCWM/MSG_SMQ_NAVIGATE qRFC Monitor -

This is custom documentation. For more information, please visit the SAP Help Portal 102
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/MSG_QUEUE_EXECUTE Execute -

/SCWM/MSG_QUEUE_RESET Reset Status -

PHYSTO Physical Stock /SCWM/QUAN_ATTR_CHANGE Change Attributes -

/SCWM/QUAN_ATTR_REPAIR Repair Batch -

Attributes

PICDOC Count Document /SCWM/PI_DOC_MTH_DISPLAY Display Phys. Inv. Enables you to display and
Document process a physical inventory
document (transaction
/SCWM/PI_PROCESS).

/SCWM/PI_DOC_MTH_DEACTIVATE Deactivate Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_PRINT Print Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_DELETE Delete Phys. Inv. -

Document

PIDIFM Difference Overview /SCWM/PI_DOC_DIFFMON_DOC_0 Difference Today Enables you to analyze the
differences in the Difference
/SCWM/PI_DOC_DIFFMON_DOC_1 Difference 1 Day Old Analyzer (transaction
/SCWM/DIFF_ANALYZER).
/SCWM/PI_DOC_DIFFMON_DOC_2 Difference 2 Days Old

/SCWM/PI_DOC_DIFFMON_DOC_3 Difference 3 Days Old

/SCWM/PI_DOC_DIFFMON_DOC_4 Difference 4 Days Old

/SCWM/PI_DOC_DIFFMON_DOC_5 Difference 5 Days Old

/SCWM/PI_DOC_DIFFMON_DOC_8 Difference > 5 Days

Old

/SCWM/PI_DOC_DIFFMON_DOC_9 Difference Total

PIDOC PI Document /SCWM/PI_DOC_MTH_DISPLAY Display Phys. Inv. Enables you to display and
Document process a physical inventory
document (transaction
/SCWM/PI_PROCESS).

PIHIST Physical Inventory /SCWM/PI_DOC_MTH_DISPLAY Display Phys. Inv. Enables you to display and
Documents Document process a physical inventory
document (transaction
/SCWM/PI_PROCESS).

/SCWM/PI_DOC_MTH_ACTIVATE Activate Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_DEACTIVATE Deactivate Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_BUNDLE Reassign Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_PRINT Print Phys. Inv. -

Document

This is custom documentation. For more information, please visit the SAP Help Portal 103
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/PI_DOC_MTH_RECOUNT Recount Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_POST Post Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_DELETE Delete Phys. Inv. -

Document

/SCWM/PI_DOC_MTH_PRIO_CHANGE Change Reason and -

Priority

PISLOC Storage Bin /SCWM/PI_DOC_MTH_DISPLAY Display Phys. Inv. Enables you to display and
Document process a physical inventory
document (transaction
/SCWM/PI_PROCESS).

/SCWM/PI_DOC_MTH_CREATE Create Phys. Inv. -

Document

RSRC Resource /SCWM/RSRC_CREATE_MON Maintain Resource Enables you to maintain a

selected resource
(transaction /SCWM/RSRC).

/SCWM/RSRC_LOGON_MON Logon to Resource Enables you to log on a

selected resource to the
desktop environment.

/SCWM/RSRC_LOGOFF_MON Logoff from Resource Enables you to log off a

selected resource from the
desktop environment.

/SCWM/RSRC_QUEUE_CHANGE_MON Change Queue -

/SCWM/RSRC_RSGRP_CHANGE_MON Change Resource -

Group

/SCWM/RSRC_MESSAGE_SEND_MON Send Message Enables you to create and

send a message to one or
more selected resources.

 Note
To disable this method,
on the SAP Easy Access
screen, choose Extended
Warehouse
Management Master
Data Resource
Management Deactivate
Messages to
Resources .

RSRCGR Resource Group /SCWM/RSRC_QUEUE_ASSIGN_MON Change Queue -

This is custom documentation. For more information, please visit the SAP Help Portal 104
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

TO Warehouse Task /SCWM/WO_CREATION_SIMULATE_MON Simulate WO Creation Enables you to simulate WO

creation for one or more
selected WTs, based on a
speci ed WO creation rule.
If no WO creation rule is
speci ed, the system
attempts to determine one
pursuant to the search
sequence for WO creation
rules per activity area.

/SCWM/TO_LOG_DISPLAY_MON Display WT Log Displays the application log

for a selected WT.

/SCWM/WO_SPLIT_MON Split WT from WO Enables you to unassign one

or more WTs from a WO, and
group them into a newly-
created WO. Using this
method, you can determine
the WO creation rule. If no
WO creation rule is
speci ed, the system
attempts to determine one
pursuant to the search
sequence for WO creation
rules per activity area. You
can also specify a reason for
the split, which is stored in
the exception log for WOs.

/SCWM/WO_TO_UNASSIGN_MON Unassign WT from WO Enables you to unassign one

or more selected WTs from
a speci ed WO.

 Note
To execute the WTs, you
need to assign them to a
WO.

/SCWM/WO_TO_ASSIGN_MON Assign WT to WO Enables you to assign one or

more selected WTs to a
speci ed WO.

/SCWM/TO_CONF_FG_MON Con rm WT in Enables you to con rm in

Foreground the foreground one or more
selected WTs (transaction
/SCWM/TO_CONF).

/SCWM/TO_CONF_BG_MON Con rm WT in Con rms in the background

Background one or more selected WTs.

/SCWM/TO_CANCEL_BG_MON Cancel WT Enables you to cancel a WT.

/SCWM/TO_REPRINT_MON Re-Print Warehouse Enables you to reprint WT

Task details.

/SCWM/TO_SHOW_ALERT_MON Show Exceptions Shows alerts for WTs with

exceptions if available.

This is custom documentation. For more information, please visit the SAP Help Portal 105
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/TO_QUAN_VALUE_DISP_MON Show Value Enables you to display the

value of moved goods for
con rmed WTs if available.

USER User /SCWM/RSRC_USER_CREATE_MON Maintain User Enables you to maintain a

user (transaction
/SCWM/USER).

WAVE Wave /SCWM/WAVEMON_HOLD Lock Wave Release Sets the status of the
selected waves to On Hold.
Waves of this status cannot
be released until their status
is changed back to Initial.

/SCWM/WAVEMON_UNHOLD Unlock Wave Release Sets the status of the

selected waves to Initial.

 Note
You can perform this
method only on waves of
status On Hold.

/SCWM/WAVEMON_DELETE Delete Wave Deletes the selected waves.

All the wave items are
unassigned from the waves.

/SCWM/WAVEMON_MERGE Merge Wave Merges the selected waves

into one wave. The merged
wave inherits its attributes
from the rst wave.

/SCWM/WAVEMON_SUBSYS Transfer Wave to Sub- Activates the WOs and WTs

System sent to a subsystem.

/SCWM/WAVEMON_SHOW_REL_LOG Display Release Log -

/SCWM/WAVEMON_RELEASE Release Wave Releases one or more

selected waves.

 Note
You can release only
those waves of status
Initial.

/SCWM/WAVEMON_RELEASE_HOLD Release Wave locked Releases one or more

selected waves, but the
warehouse orders stay in
status locked.

 Note
You can release only
those waves of status
Initial.

This is custom documentation. For more information, please visit the SAP Help Portal 106
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WAVEMON_RELEASE_SINGLE Release Single Wave Releases one or more

selected waves as
separated waves.

 Note
You can release only
those waves of status
Initial.

/SCWM/WAVEMON_RELEASE_HOLD_SGL Release Single Wave Releases one or more

locked selected waves as
separated waves, but the
warehouse orders stay in
status locked.

 Note
You can release only
those waves of status
Initial.

WAVITM Wave Item /SCWM/WAVEMON_SPLIT Split Position Splits the selected wave
items from their waves, and
creates a new wave for
them.

/SCWM/WAVEMON_UNASSIGN Delete Wave Unassigns the selected

Assignment wave items from the wave.

/SCWM/WAVEMON_REASSIGN Assign to Wave Enables you to assign one or

more selected wave items
to a speci ed wave.

WHRI Inbound Delivery /SCWM/INSP_MON Display Inspection Displays the inspection

Document documents and inspection
outcomes.

WHRITI Inbound Delivery Item /SCWM/INSP_MON Display Inspection Displays the inspection
Document documents and inspection
outcomes.

WHRITO Outbound Delivery /SCWM/WAVEMON_ASSIGN Assign to Wave Enables you to assign one or
Order Item more selected outbound
delivery order items to a
speci ed wave.

/SCWM/WHR_OUT_TREE Display Item -

Hierarchy

This is custom documentation. For more information, please visit the SAP Help Portal 107
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WHRITEM_OUT_QUANT_ADJ Adjust Quantity Enables you to adjust the

quantity of multiple
outbound delivery order
items to zero, or the picked
quantity in the case of
warehouse activities that
have already been started
for partial quantities, at the
same time. The adjustments
are based on the process
codes assigned to the
items.

/SCWM/WHRITEM_OUT_QUANT_ADJ_OD Adjust Quantity and Enables you to adjust the

Create OD quantity of multiple
outbound delivery order
items to zero, or the picked
quantity in the case of
warehouse activities that
have already been started
for partial quantities, at the
same time. The adjustments
are based on the process
codes assigned to the
items. The system
automatically creates
outbound deliveries for the
items that are reduced to
zero to close the items.

/SCWM/WHRITEM_OUT_BIN_DET Det. Rough Enables you to determine a

Bin/Staging Area rough picking bin, or a
staging area and door for the
outbound delivery items.

/SCWM/WHRITEM_OUT_UPD_LOAD_SEQ Update Loading Enables you to update the

Sequence loading sequence for
outbound delivery items.

WHRO Outbound Delivery /SCWM/WHR_OUT_TREE Display Item -

Order Hierarchy

/SCWM/WHR_OUT_REPRINT Reprint ODO Enables you to reprint

outbound delivery order
details.

/SCWM/WHR_OUT_CREA_WT_BG Create WT in Enables you to trigger WT

Background creation in the background
for outbound deliveries.

/SCWM/WHRHEAD_OUT_UPD_LOAD_SEQ Update Stop Enables you to update the

Sequence stop sequence for outbound
deliveries.

WO Warehouse Order /SCWM/WO_LOG_DISPLAY_MON Display WO Log Displays the application log

for a selected WO.

This is custom documentation. For more information, please visit the SAP Help Portal 108
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/WO_MERGE_MON Merge Warehouse Enables you to merge

Orders selected open WOs, which
unassigns the WTs from the
WOs, and groups them into
a newly created WO. Using
this method, you can
determine the WO creation
rule. If no WO creation rule is
speci ed, the system
attempts to determine one
pursuant to the search
sequence for WO creation
rules per activity area. You
can also specify a reason for
the merge, which is stored in
the exception log for WOs.

/SCWM/WO_PRINT_MON Print Warehouse Enables you to print WO

Order details.

/SCWM/WO_REPRINT_MON Re-Print Warehouse Enables you to reprint WO

Order details.

/SCWM/WO_HOLD_MON Lock Warehouse Sets the status of one or

Order more selected WOs to
Waiting. The WO cannot be
executed until its status is
set to Open.

/SCWM/WO_UNHOLD_MON Unlock Warehouse Sets the status of one or

Order more selected WOs to
Open.

/SCWM/WO_ADD2SWHO Add WO to Adds an empty WO to a

Load/Unload Super super WO (in a loading or
WO unloading scenario).

/SCWM/WO_CONF_FG_MON Con rm WO in Enables you to con rm in

Foreground the foreground one or more
selected WOs (transaction
/SCWM/TO_CONF.)

/SCWM/WO_CONF_BG_MON Con rm WO in Con rms in the background

Background one or more selected WOs.

/SCWM/WO_CANCEL_MON Cancel WO Cancels one or more

selected WOs and their
WTs.

/SCWM/RSRC_WO_RSRC_ASSIGN_MON Assign to Resource Enables you to assign a

resource to one or more
selected WOs.

/SCWM/RSRC_WO_RSRC_UNASIN_MON Unassign from Enables you to unassign a

Resource resource from one or more
selected WOs.

This is custom documentation. For more information, please visit the SAP Help Portal 109
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

/SCWM/RSRC_WO_QUEUE_CHANGE_MON Change Queue Enables you to change the

queue to which the selected
WOs are assigned.

/SCWM/RSRC_WO_LSD_CHANGE_MON Change LSD Enables you to change the

latest starting date (LSD) of
the selected WOs.

FBDET Fixed Bins /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

/SCWM/CREATE_PRODUCT_WT_MON Create Product WT -

/SCWM/CREATE_HU_WT_MON Create HU WT -

FBMUL Fxd Bins with Mltpl. /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

Assgmts
/SCWM/CREATE_PRODUCT_WT_MON Create Product WT -

/SCWM/CREATE_HU_WT_MON Create HU WT -

FBOO Unassgd Fxd Bins /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

Wthout Stk

FBOW Unassgd Fxd Bins with /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

Stk
/SCWM/CREATE_PRODUCT_WT_MON Create Product WT -

/SCWM/CREATE_HU_WT_MON Create HU WT -

FBOWC Assgd Fxd Bins wth /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

Cmp. Stk
/SCWM/CREATE_PRODUCT_WT_MON Create Product WT -

/SCWM/CREATE_HU_WT_MON Create HU WT -

FBOWW Assgd Fxd Bins wth /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

Incmp. Stk
/SCWM/CREATE_PRODUCT_WT_MON Create Product WT -

/SCWM/CREATE_HU_WT_MON Create HU WT -

FBWO Assgd Fxd Bins /SCWM/MAINTAIN_BINMAT_MON Maintain Fixed Bin -

Wthout Stk

WHRI Inbound Delivery /SCWM/INB_REPRINT_MON Reprint inbound Enables you to reprint

delivery order inbound delivery order
details.

WHRO Outbound Delivery /SCWM/WHR_OUT_REPRINT Reprint ODO Enables you to reprint

Order outbound delivery order
details.

TU Transport Unit Header /SCWM/TU_REPRINT_MON Reprint TU Enables you to reprint

Outbound transportation unit details.

VEHICL Vehicle Header /SCWM/VEHICLE_REPRINT_MON Reprint Vehicle Enables you to reprint

Outbound vehicle details.

WHRI Inbound Delivery /SCWM/WHR_IN_CREA_WT_BG Create WT in Enables you to create one or

Background more selected WTs in the
background.

This is custom documentation. For more information, please visit the SAP Help Portal 110
 9/2/2022

Object Object Class Method Name Method Description Remark

Class Description
Name

WHRO Outbound Delivery /SCWM/WHR_OUT_CREA_WT_BG Create WT in Enables you to create one or

Order Background more selected WTs in the
foreground.

Automatic Refresh

Use
In the warehouse management monitor, you can set a default automatic refresh for all displayed nodes and an automatic
refresh for speci c nodes. You specify the refresh interval in minutes and it is speci c to your user.

 Recommendation
Limit your use of automatic refresh and set the refresh interval to a reasonable value. Regular refreshes by multiple users
will add a noticeable workload to the system and can impact system performance and sizing. Therefore we recommend not
setting a default refresh interval. Instead, set a refresh interval for speci c nodes as required.

Features
The automatic refresh interval for speci c nodes overrules the default refresh interval.

The system automatically refreshes a node only if the node is displayed.

You can suspend automatic refresh and you can reactivate it.

If parent and child nodes are displayed, the system uses the lowest refresh interval of both nodes.

If a parent node of a child node is displayed in the form view, the system skips the automatic refresh.

The system reactivates automatic refresh when you go back to the list view.

If a child node is displayed, the system skips the automatic refresh unless all lines of the parent node are selected for
drill-down.

If you perform any action in the warehouse management monitor, for example, drill down or execute a monitor method
(see Monitor Methods), the system postpones automatic refresh.

Then if you, for example, display the warehouse order creation log for a warehouse order, the system restarts the
automatic refresh interval when you close the warehouse order creation log.

Activities
To specify the default refresh interval, specify the refresh interval in the Warehouse Management Monitor dialog box
when you rst open the warehouse management monitor. Alternatively, choose in the warehouse management
monitor.

To specify the refresh interval for a speci c node, in the context menu of the node, choose Set Refresh Interval to open
the Set Refresh Interval dialog box.

Note that if you specify a default refresh interval, you can prevent a refresh of a speci c node by removing the number or
entering 0 in the Node Refresh (Mins) eld in the Set Refresh Interval dialog box for the speci c node.

This is custom documentation. For more information, please visit the SAP Help Portal 111
 9/2/2022
You can suspend automatic refresh by choosing the Suspend Refresh button. You can reactivate automatic refresh by
choosing the Activate Refresh button.

 Recommendation
If there is a dialog box associated with a node, for example, to remind you to enter selection criteria, the system displays the
dialog box during automatic refresh. Therefore do not automatically refresh nodes with dialog boxes. Alternatively, enter the
selection criteria so that the system does not display the dialog box.

More Information
Warehouse Management Monitor

Message Queue Monitoring

Use
You can use the Message Queue node to monitor the status of queued remote function call (qRFC) messages in message
queues in SAP Extended Warehouse Management (SAP EWM). You can also monitor the status of qRFC messages in message
queues between SAP EWM and SAP ERP. This allows you to see messages that have not been processed as expected, so you
can perform any steps necessary resolve the problem. Once you have done this, you can restart message queues from the
Warehouse Management Monitor.

You can con gure the business related selection criteria of the message queue groups, so you can adapt them to the areas of
responsibility of individual users.

Integration
You can use the message queue node to monitor inbound message queues in SAP ERP when SAP EWM is integrated with SAP
ERP.

Features
In the Message Queue node, you can do the following:

Select message queues using the SAP EWM warehouse number

View message queues from different warehouse numbers

View message queues where no warehouse is determined for the message queue, for example, cross-warehouse
messages such as messages related to packaging speci cation

Select message queues by business related selection criteria

View information such as the warehouse number and business key of messages that have not been processed yet and
are still in the message queues

Display the number of entries in one message queue

Display existing SAP EWM application logs

View inbound message queues relevant to SAP EWM on a connected SAP ERP system

Execute message queues

This is custom documentation. For more information, please visit the SAP Help Portal 112
 9/2/2022
Reset the status of message queues

You can give message queues meaningful descriptions. By default, the most common message queues are available in the
Warehouse Management Monitor, but you can adapt these message queue groups or create your own message queue groups
in Customizing for Extended Warehouse Management under Monitoring Message Queue Monitoring De ne Message Queue
De nitions and Monitoring Message Queue Monitoring De ne Message Queue Groups .

Demonstration of SAP Crystal Reports in Warehouse

Management Monitor
You can display data in seven demo SAP Crystal Reports in the warehouse management monitor. The SAP Crystal Reports are
available in a separate monitor, CR_EX, in the warehouse management monitor.

These SAP Crystal Reports can be used to display charts and analytics functions for demonstration purposes.

The reports can be exported and modi ed using SAP Crystal Reports Designer and reimported and saved as an ALV grid layout.
You must purchase a license for SAP Crystal Reports Designer to do this.

The demo SAP Crystal Reports are as follows:

Inbound Delivery Item

Outbound Delivery Item

Loading Workload per Route

Warehouse Task

Physical Inventory Documents

Stock Overview

Labor Utilization Date and Processor

Easy Graphics Framework

Purpose
The Easy Graphics Framework (EGF) is a generic tool that you can use for the simple con guration of cockpits for applications
such as Extended Warehouse Management (EWM). You use these in addition to text-based monitors and to display your data
graphically. Multiple users can work with the EGF cockpit at the same time.

 Note
For more information about an example implementation, see Warehouse Cockpit .

For more information, see the Implementation Guide (IMG) for EWM under Monitoring Easy Graphics Framework .

Implementation Considerations
If you are implementing the standard EGF graphics, you must have SAP GUI 6.40 or later installed. For more information, see
SAP Service Marketplace under service.sap.com/patches .

This is custom documentation. For more information, please visit the SAP Help Portal 113
 9/2/2022

Integration
By default, the EGF uses SAP Internet Graphics Server (SAP IGS) as its graphics provider to generate graphics from
data. You can however use any other graphics provider that generates graphics from data. These graphics must be
transferred to the EGF in the form of Uniform Resource Locators (URLs) (see Make Settings for the Easy Graphics
Framework ).

The service provider de nes which data the EGF displays for an EGF object.

To ensure that the EGF can be displayed without errors, you must have installed Microsoft Internet Explorer version 5 or
higher.

For more information about security settings in Internet Explorer, see SAP Help Portal under help.sap.com SAP
ERP SAP ERP Central Component Logistics Production Planning and Control (PP) Production Planning for Process
Industries (PP-PI) Process Management (PP-PI-PMA) Process Instruction Sheets (PI Sheets) Browser-Based PI
Sheet Setting Up the Browser for PI Sheets and Cockpits .

Features
The following gure provides an overview of the simpli ed process ow in the EGF:

The EGF receives data from a service provider, for example about the utilization of resources. If you are using a chart type to
display this data that is delivered in the standard SAP system, the EGF sends the data to SAP IGS. If you are using your own
chart type to display this data, the EGF uses method GET_URL to send the data to your graphics provider (see Interfaces ). SAP
IGS or your graphics provider generates a relevant graphic, and sends a URL to the EGF. The EGF uses this URL to display the
graphic in your cockpit.

The following functions are available in the EGF:

By default, the EGF uses SAP IGS as a graphics provider. You can use a selection of chart types , which are provided by
SAP IGS. The EGF also provides you with further chart types, such as traffic lights.

This is custom documentation. For more information, please visit the SAP Help Portal 114
 9/2/2022
You can also use your own graphics provider and your own chart types (see Make Settings for the Easy Graphics
Framework ).

The EGF displays all chart types that you have de ned in Customizing for the EGF. The EGF also shows all chart types for
which a graphics provider sends a URL that refers to this chart type. This can be SAP's own graphics, such as from SAP
xApp Manufacturing Integration and Intelligence (xMII) or Business Server Page applications, or graphics from external
providers (see Make Settings for the Easy Graphics Framework ).

You can display graphics either in a cockpit, with or without Customizing, or in your own application (see Make Settings
for the Easy Graphics Framework and Interfaces ).

The EGF displays the current data sent by a service provider, and refreshes this data in speci ed intervals. You can de ne
the input data for a displayed EGF object, including the refresh rate (see Using the Refresh Rate ).

If you have de ned follow-up activities, you can navigate from the graphic in the EGF to another application (see Make
Settings for the Easy Graphics Framework ). For example, you display the number of open warehouse tasks in a graphic,
and have de ned a follow-up activity to navigate to warehouse task con rmation.

If you want to navigate from the EGF to a follow-up activity, you can do this in one of the following ways:

In the context menu of the EGF object, select the corresponding option.

In the graphic, select a data value, from which you can drill-down.

You can de ne EGF object data, such as resource or utilization data, which a user can display as a graphic. You can de ne
these authorizations for each EGF object or for each function using an authorization group. Users can only see EGF
objects in the navigation tree, or functions in the context menu, for which they have authorization (see Make Settings for
the Easy Graphics Framework ).

 Example
You have the EGF objects Door Assignment and Uncon rmed Warehouse Tasks in a cockpit . You want user A to be
able to see only the EGF object for uncon rmed warehouse tasks in the navigation tree of the cockpit, and de ne
authorizations correspondingly.

You want user B to see only uncon rmed warehouse task data for warehouse numbers 0001 and 0002 , and de ne
authorizations correspondingly.

For more information, see the IMG for EWM under Monitoring Easy Graphics Framework De ne Authorization Groups .

You can de ne a cross-user or a user-speci c EGF cockpit layout. For an EGF cockpit menu, for example, you can de ne a
changed structure in the navigation tree with newly created structure nodes (see De nition of EGF Cockpit Layouts ).

In Customizing for the EGF, you can de ne the following for displaying EGF objects (see Make Settings for the Easy
Graphics Framework ):

Cockpit

Available EGF objects for each cockpit

Available chart types for each EGF object

Default chart type

You can specify a default chart type for each EGF object.

Input data for an EGF object

Follow-up activities for each EGF object

De nition of EGF Cockpit Layouts

This is custom documentation. For more information, please visit the SAP Help Portal 115
 9/2/2022

Use
You can de ne different EGF cockpit layouts either user-speci cally or cross-user.

Integration
For more information about EGF integration, see Easy Graphics Framework .

Prerequisites
For more information about EGF prerequisites, see Easy Graphics Framework .

Features
You can de ne the following for a cross-user or user-speci c EGF cockpit layout:

Default layout of an EGF cockpit

 Note
If you do not de ne a default layout, the EGF displays both the standard SAP EGF objects and your own EGF objects.

You can reload a cockpit layout at any time, for example if you have deleted EGF objects from the navigation tree and
want to display them again.

Grouping of EGF objects in the navigation tree, to display your EGF objects in a clearer way

Saving input data, such as the warehouse number

Number of rows and columns of the display grid and the layout of the grid

You can divide a cell of a grid into further rows and columns. You can also insert a grid within a grid, or de ne the size of
the individual viewers.

Size of the displayed graphic

If you change the display size of a displayed EGF object, the EGF automatically adjusts the size of the displayed graphic
as soon as the next refresh interval has occurred. If you choose with the quick info Regenerate Graphics , the EGF
adjusts the display size for EGF objects that are already displayed straight away.

Activities
If you want to de ne a cross-user or user-speci c EGF cockpit layout, choose the EGF cockpit (transaction /SCWM/EGF) and
de ne your EGF cockpit layout. Choose Save Layout . The system displays a modeless dialog box, in which you can de ne the
following:

Layout name

Description

Layout options:

EGF cockpit menu only

EGF cockpit menu and grid layout

EGF cockpit menu, grid layout, and input data

This is custom documentation. For more information, please visit the SAP Help Portal 116
 9/2/2022
Depending on your authorizations, you can also set the Default Layout indicator for a user-speci c EGF cockpit layout and
Cross-User for a cross-user EGF cockpit layout in this modeless dialog box. For more information, see Make Settings for the
Easy Graphics Framework .

If you want to change the settings for the grid and refresh rate at runtime, choose the secondary mouse button.

Make Settings for the Easy Graphics Framework

To be able to use the Easy Graphics Framework (EGF), you must make the following Customizing settings.

Settings for EGF Objects

If you want to display a graphic in a cockpit, de ne your own chart types and assign these or existing chart types to EGF
objects. To do this, in Customizing for EWM, execute the IMG activity De ne Chart Types and De ne Objects . For more
information, see the Implementation Guide (IMG) for EWM under Monitoring Easy Graphics Framework De ne Chart
TypesandDe ne Objects .

If you navigate from a displayed EGF object to follow-up activities, and want to use the Post Processing Framework or a
work ow, de ne follow-up activities. To do this, in Customizing for EWM, execute the IMG activity De ne Functions . For
more information, see the IMG for EWM under Monitoring Easy Graphics Framework De ne Functions .

If you want to de ne authorizations for each EGF object or function, de ne authorization groups and assign these to an
EGF object or function. To do this, in Customizing for EWM, execute the IMG activity De ne Authorization Groups and
De ne Objects . For more information, see the IMG for EWM under Monitoring Easy Graphics Framework De ne
Objects .

 Note
The EGF only performs the authorization check for EGF objects. If you de ne a navigation to follow-up activities and
follow-up objects, you have to perform an authorization check yourself.

You de ne the default chart type for an EGF object. To do this, in Customizing for EWM, you specify the default chart type
for an EGF object in the Chart Type eld of IMG activity De ne Objects . For more information, see the IMG for EWM
under Monitoring Easy Graphics Framework De ne Objects .

If you want to change the prede ned refresh rate, de ne your own refresh rate. To do this, in Customizing for EWM, you
specify your refresh rate in the Interval column of dialog structure Objects in the IMG activity De ne Objects (see Using
the Refresh Rate ). For more information, see the IMG for EWM under Monitoring Easy Graphics Framework De ne
Objects .

Settings for Displaying EGF Objects in the Navigation Tree of the EGF Cockpit
You specify the cockpit for displaying an EGF object by de ning a new EGF implementation. To do this, in Customizing for
EWM, execute the IMG activity De ne Cockpits . For more information, see the IMG for EWM under Monitoring Easy
Graphics Framework De ne Cockpits .

You de ne the number of EGF objects for each cockpit. To do this, in Customizing for EWM, specify the number in dialog
structure Cockpits Objects in IMG activity De ne Cockpits . For more information, see the IMG for EWM under
Monitoring Easy Graphics Framework De ne Cockpits .

You de ne input data for an EGF cockpit. To do this, in Customizing for EWM, specify the number in dialog structure
Cockpits Input Data in IMG activity De ne Cockpits . For more information, see the IMG for EWM under
Monitoring Easy Graphics Framework De ne Cockpits .

This is custom documentation. For more information, please visit the SAP Help Portal 117
 9/2/2022

Settings for Graphics

You de ne the attributes of a graphic for each EGF object, such as per resource or warehouse task, or per user. For
example, you can de ne that the background color in graphics is always blue, or that EGF is to always use blue, yellow,
red, and green to display pie charts.To do so, on the SAP Easy Access screen, choose Extended Warehouse
Management Monitoring Process Chart Template . Make your changes, and save them. When saving, you can choose
between User-Speci c and Cross-User . You have de ned the authorizations per EGF object or user if required. You can
assign the following authorizations:

You can de ne a chart type, and allow it as a default chart type for all users, EGF cockpits, and EGF objects.

You can de ne a chart type, and allow it as a default chart type for user USER1 , all EGF cockpits, and all EGF
objects.

You can de ne a third chart type, and allow it as a default chart type for user USER2 , EGF cockpit COCKPIT2 ,
and EGF object OBJECT2 .

User EGF Cockpit EGF Object Chart Type Default Chart Type

* * * PIE CHART DEFAULT

USER1 * * PIE CHART DEFAULT1

USER2 COCKPIT2 OBJECT2 PIE CHART DEFAULT2

To do this, in Customizing for EWM, you de ne the graphic attributes for each EGF object in dialog structure
Cockpits of IMG activity De ne Settings . For more information, see the IMG for EWM under Monitoring Easy
Graphics Framework De ne Cockpits .

Settings for Your Own Graphics

If you want to use something other than SAP Internet Graphics Server (SAP IGS) as your graphics provider, de ne your
own graphic types and set the URL indicator. This calls the GET_URL method of your service provider, allowing you to
return a Uniform Resource Locator (URL) to the EGF. To do this, in Customizing for EWM, execute the IMG activity De ne
Chart Types . For more information, see the IMG for EWM under Monitoring Easy Graphics Framework De ne Chart
Types .

 Note
The EGF uses an HTML Viewer to display a URL that links to a graphic. You can use the GET_URL method of interface
/SCWM/IF_EGF_SP to implement your own graphics provider instead of the SAP Internet Graphics Server (SAP IGS).
The EGF receives the data from which a graphic is to be generated from the service provider. The EGF then calls your
graphics provider instead of the SAP IGS. In this situation, you are responsible for which data the EGF displays with
the URL. Calling a URL outside of the SAP system and calling a graphics provider within an SAP system may not be
safe, since data can enter the system without undergoing a virus check, for example.

We recommend that you use SAP Web Repository to save and display graphics using a URL with the EGF, for example.
You can activate a virus check with the SAP Web Repository to check documents and graphics before an upload.

We recommend that you make the following settings in your Browser: Make Browser Settings for the Easy Graphics
Framework

For more information, see:

The IMG for EWM under SAP NetWeaver Application Server System Administration Virus Scan Interface.

SAP Service Marketplace under service.sap.com/securityguide SAP Supply Chain Management SAP Supply
Chain Management Security Guide SCM 5.1
This is custom documentation. For more information, please visit the SAP Help Portal 118
 9/2/2022
SAP Help Portal at help.sap.com SAP R/3 Enterprise Release 4.70 SAP NetWeaver Components SAP Internet
Transaction Server ITS Implementation Models WebRFC Programming Web Reporting.

SAP Help Portal under help.sap.com SAP NetWeaver 2004s SAP NetWeaver Library SAP NetWeaver by Key
Capability Application Platform by Key Capability ABAP Technology UI Technology Front-End Services (BC-
FES) SAP HTML Viewer (BC-CI)

You de ne the available EGF objects for each EGF cockpit. To do this, in Customizing for EWM, you executed the IMG
activity De ne Chart Types and De ne Cockpit Settings . For more information, see the IMG for EWM under
Monitoring Easy Graphics Framework De ne Chart TypesandDe ne Cockpits .

Using the Refresh Rate

Use
The Easy Graphics Framework (EGF) uses a refresh rateto refresh the data sent by a service provider for an EGF object.

Features
The default refresh rate is set to one minute.

The refresh rate is located at EGF object level. The EGF checks to see whether a refresh is required for the rst cell in the grid,
for example. If this is the case, the EGF calls the service provider and waits for its response. If the service provider only responds
after 10 minutes, the EFG only checks after 10 minutes whether a refresh is required for the second cell in the grid.

If you are using the EGF for planning purposes or for forecasts, you can deactivate the refresh rate. This enables you to display
trends, such as a trend for the coming year, or forecasts, such as daily resource requirements for a warehouse task.

Activities
You deactivate the refresh rate by setting the refresh rate value to zero either in Customizing for the EGF for the object, or in
the context menu for the object at runtime.

You can de ne the refresh rate for each EGF object.

 Note
You can change the refresh rate at runtime.

You can refresh an EGF object that you are displaying as a graphic immediately by choosing the option Refresh Display in the
context menu for the object. You can also refresh all displayed objects by choosing Refresh Data in the SAP GUI.

See also:

Make Settings for the Easy Graphics Framework

Interfaces, Methods, and Function Modules in the EGF

Use
The Easy Graphics Framework (EGF) allows you to work with various interfaces, methods, and function modules.

This is custom documentation. For more information, please visit the SAP Help Portal 119
 9/2/2022

Features
Interfaces and Methods

The following table gives you an overview of the methods in the EGF.

Interface Method Description

/SCWM/IF_EGF_SP GET_DATA Gets chart data from the application. Most

charts require a group of row values and a
group of data categories as data format. A
simple chart, such as a traffic light, only
sets the color of the traffic light.

/SCWM/IF_EGF_SP GET_URL Gets a URL from the application. This URL

forms the link to the graphic that the EGF is
to display.

/SCWM/IF_EGF_SP HANDLE_FUNCTION If the application receives a function code

for a follow-up activity, this interface
method enters the function code for the
chart.

/SCWM/IF_EGF_SP DRILL_DOWN Speci es what to do if the user chooses

(drills down to) the corresponding EGF
object.

/SCWM/IF_EGF_SP OBJECT_REMOVED If the object is removed from the display, a

noti cation of this event can be
implemented with this interface method.

/SCWM/IF_EGF_SP SET_FUNCTIONS Adds functions dynamically for an object,

which are then displayed in the object's
context menu and can be handled in
method HANDLE_FUNCTION.

You can use these interfaces to do the following:

De ne a source for your chart data

De ne your own graphics provider (see Make Settings for the Easy Graphics Framework)

De ne your own chart types and send them to the EGF using a URL (see Make Settings for the Easy Graphics
Framework)

De ne follow-up activities for an EGF object

For more information, see the interface documentation.

Function Modules

The following table gives you an overview of the function modules in the EGF.

Function Module Description

/SCWM/EGF_COCKPIT Starts an EGF cockpit implementation. You must enter the cockpit
ID as an import parameter.

This is custom documentation. For more information, please visit the SAP Help Portal 120
 9/2/2022

Function Module Description

/SCWM/EGF_CONTAINER You transfer a container instance to the function module, such as to

class CL_GUI_CUSTOM_CONTAINER, in which the required EGF
object is displayed.

/SCWM/EGF_POPUP The system generates a modeless dialog box in which the required
EGF object is displayed.

/SCWM/EGF_COCKPIT_DYNAMIC Starts an EGF cockpit dynamically. All the data required for
generating the cockpit is transferred using the interfaces of the
function module. No Customizing is required here.

/SCWM/EGF_CONTAINER_DYNAMIC You transfer a container instance to the function module, such as to

class CL_GUI_CUSTOM_CONTAINER, in which the required EGF
object is displayed. The EGF object de nition is done dynamically
using the interface of the function module. No Customizing is
required here.

/SCWM/EGF_POPUP_DYNAMIC The system generates a modeless dialog box in which the required
EGF object is displayed. The EGF object de nition is done
dynamically using the interface of the function module. No
Customizing is required here.

You can use these function modules to do the following:

Start an EGF cockpit implementation

Transfer a container instance to a function module

Generate a modeless dialog box

You can display a graphic as a subscreen or as a separate modeless dialog box in your application. To do this, in
Customizing for EWM, choose the following activities under Monitoring Easy Graphics Framework :

De ne Chart Types

De ne Cockpits

For more information, see the function module documentation.

Make Browser Settings for the Easy Graphics Framework

Use
If you work with a Microsoft Internet Explorer in the Easy Graphics Framework (EGF), you must meet the following prerequisites
and make the following security settings.

Prerequisites
To ensure that the EGF can be displayed without errors, you must have installed Microsoft Internet Explorer version 5 or higher.

You must also make the security settings listed below in your Microsoft Internet Explorer.

Procedures
1. In the Internet Explorer menu, choose Tools Internet Options .
This is custom documentation. For more information, please visit the SAP Help Portal 121
 9/2/2022
2. Choose the Security tab page.

3. Choose the Web content zone:

Under Internet Options , you can choose from different options. We cannot recommend Internet . Trusted Sites is safer,
but Local Intranet offers better performance (see also SAP Note 785308).

4. Choose Custom Level....

5. In the Security Settings window, make the following settings:

Function Setting

Download signed ActiveX controls Prompt

Launching programs and les in an IFRAME Prompt

Navigate sub-frames across different domains Prompt

Using the Graphical Warehouse Layout

Use
The graphical warehouse layout displays the interior and exterior of the warehouse as a two-dimensional graphic. You can use
the graphical warehouse layout to check the Customizing of the warehouse. For example, if you are a warehouse supervisor or
expert, you can check master data that you have de ned in Customizing for Extended Warehouse Management (EWM). You can
also get information about the stock situation, for example about empty storage bins and resources. The graphical warehouse
layout displays the warehouse data per warehouse number. For example, if you are using warehouse number 1122 for a
warehouse and warehouse number 1133 for a yard, the GWL shows you the warehouse data for the warehouse in the rst case,
and the warehouse data for the yard in the second case.

Prerequisites
You are using SAP Graphical User Interface (SAP GUI) 7.10 or higher. For more information, see SAP Service Marketplace
under http://service.sap.com/patches .

If you want to use your own graphical warehouse layout objects, you have de ned these in Customizing for EWM under
Monitoring Graphical Warehouse Lagerlayout De ne GWL Objects , and assigned them to a GWL object category under
Monitoring Graphical Warehouse Layout De ne GWL Object Categories .

If you want to restrict the object display to a level of the warehouse, you have de ned the storage type level in
Customizing for EWM under Master Data De ne Storage Type .

Features
Displaying the Warehouse Layout

You can check the Customizing for a warehouse number. For example, the graphical display enables you to quickly identify
whether a shelf is incorrect due to you having entered incorrect data in Customizing. The default values are the warehouse
number and storage type level you speci ed in Customizing. If you do not de ne a storage type level, the graphical warehouse
layout displays all the objects that belong to a warehouse number. You can change the default values. For more information, see
Customizing for EWM under Master Data De ne Warehouse Numbers or Master Data De ne Storage Type .

This is custom documentation. For more information, please visit the SAP Help Portal 122
 9/2/2022
If you only want to check Customizing for a particular part of the warehouse, such as for the goods receipt area, you can also
specify the storage type in the default values.

You can only refresh the display of the graphical warehouse layout for objects that change in the warehouse as part of your daily
work, such as handling units or resources. However, if you display a warehouse, and then create new storage bins and refresh
the display, EWM does not show the new storage bins.

The graphical warehouse layout shows you master data for a warehouse number, such as storage bins or walls, in the form of a
two-dimensional graphic. Here the length details in the graphic correspond to the unit of length that you de ned as a base unit
of measure in Customizing. For more information, see Customizing for EWM under Master Data De ne Warehouse Number
Control . In addition, the display size relates to the largest coordinates that you have de ned for a master record. This enables
you to quickly identify for example whether a rack was de ned incorrectly and is located outside the warehouse.

You can choose the Zoom In and Zoom Out pushbuttons to change the graphical display, to display either the entire warehouse
or individual objects in the warehouse. If the display size does not allow you to display the entire warehouse, you can choose the
corresponding pushbutton to navigate upwards or to the right, for example. Here you use a percentage value to de ne the
percentage of the current display size by which EWM is to change the graphical display in the respective direction.

If you have generated storage bins using a template in Customizing for EWM under Master Data Storage Bins De ne Storage
Bin Structure , EWM groups the storage bins that are located on one side of the aisle into racks by default. Prerequisite for this
is that you have de ned the template in Customizing in such as way that the one side of the aisle contains stacks with even
numbers, and the other side of the aisle contains stacks with odd numbers. The graphical warehouse layout can display these
racks.

 Note
If you choose Extended Warehouse Management Master Data Storage Bin on the SAP Easy Access screen and create
storage bins individually, you must also ful ll the above prerequisite so that EWM combines storage bins into racks and
displays these racks in the graphical warehouse layout.

To switch to the front view of a rack, click the graphical display of the rack. This means that, even for multi-level racks, all storage
bins are visable. If you choose Bin Level, EWM displays the individual storage bins instead of the rack.

If you want to change the display for the graphical warehouse layout, you can use Business Add-In (BAdI) /SCWM/EX_GWLMC
BAdI: Function on Mouse Click. For more information, see the relevant BAdI documentation in Customizing for EWM under
Business Add-Ins (BAdIs) for Extended Warehouse Management Monitoring .

Information and Functions for Existing Objects

You can display detailed information for an object. The graphical warehouse layout displays a popup containing detailed
information or actions for the object. If you want to display your own object-speci c information or actions in the popup, you can
use BAdI /SCWM/EX_GWLDISPLAY BAdI: Change Display of GWL. For more information, see the relevant BAdI documentation
in Customizing for EWMunder Business Add-Ins (BAdIs) for Extended Warehouse Management Monitoring .

You can call a context menu for the object and execute object-speci c functions. If you want to de ne your own object-speci c
functions, you can use the BAdI /SCWM/EX_GWLCM BAdI: Extend Context Menu. For more information, see the relevant BAdI
documentation in Customizing for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management Monitoring .
The following shows examples of objects containing object-speci c functions:

Storage Bin

You can use the context menu to navigate to the transaction for changing storage bins (transaction /SCWM/LS02), and
change the coordinates of a storage bin, for example.

Handling Unit on Conveyor Belt

This is custom documentation. For more information, please visit the SAP Help Portal 123
 9/2/2022
You can use the context menu to display detailed data for a handling unit.

Workers

You can send an e-mail to the worker.

You can display empty or blocked storage bins. If the storage bins are lled, EWM displays the information of the storage bins of
the lowest level. If the storage bins are empty, EWM also displays the empty storage bins of other levels. In the standard
system, No Selection is selected. If you want to display additional selection options, you can use BAdI /SCWM/EX_GWLMARKER
BAdI: De ne Additional Marker. For more information, see the relevant BAdI documentation in Customizing for EWM under
Business Add-Ins (BAdIs) for Extended Warehouse Management Monitoring .

De nition of New Objects

You can de ne your own objects For more information, see Customizing for EWM under Monitoring Graphical Warehouse
Layout De ne GWL Object .

Activities
On the SAP Easy Access screen, choose Extended Warehouse Management Monitoring Graphical Warehouse Layout Display
Graphical Warehouse Layout .

Demo Data in Warehouse Cockpit and Monitor

Use
This function enables you to display demo data instead of real system data quickly and easily in the warehouse management
monitor (WM monitor) or the warehouse cockpit for demo purposes. You can create demo data, import demo data from one
system into another system, and reuse demo data. This allows you to give better demos of the WM monitor and warehouse
cockpit.

 Caution
The demo data function cannot be executed in productive systems. It is for demo purposes only.

The following features are not available in the display demo data set mode in the warehouse cockpit:

Input selection when calling an EGF object

De ne follow-up activities for an EGF object (EGF functions)

Drill down from an EGF object

Save, transport, load, and delete a cockpit layout

Stop refresh, set timer for the object refresh, or change an object’s refresh rate

Regenerate graphics

Insert and change the cockpit grid

Maintain cockpit defaults

The following features are not available in the display demo data set mode in the warehouse management monitor:

Hotspot navigation

This is custom documentation. For more information, please visit the SAP Help Portal 124
 9/2/2022
Method execution

Process
1. You access the WM monitor or warehouse cockpit in maintain demo data set mode in a system where you have some
data. This mode allows you to create, administer, export, and import demo data sets.

 Note
You choose the maintain demo data set mode in the start-up dialog box.

You must specify the demo mode when starting the WM monitor or the warehouse cockpit. If you leave the Demo
Mode eld empty, the WM monitor or the warehouse cockpit runs in standard mode and accesses real data as usual.

2. You display the data in the WM monitor node or the warehouse cockpit in the chart types you want to be shown in the
demo. You prepare each version of the node or cockpit in the sequence of the demo and save the sequence as a demo
data set to the data container. You can specify a description for each cockpit in the demo data set. This description is
only available in the logon language.

3. You can administer demo data for each demo data set in the maintain demo data set mode by choosing the Administer
Demo Data button.

A dialog box appears showing all the demo data of the current demo data set. You can perform the following actions:

Change the description of a demo record

Delete demo records

Change the sequence of demo records

You can store multiple versions of a node or cockpit in a demo data set. The versions are numbered sequentially, and the
number is displayed. If there is only one version in the demo data set, this is always displayed. If there are several
versions, the system displays the next version in the sequence after each refresh of the screen. When you reach the end
of the sequence, the system displays the rst version again.

4. You export the demo data to an XML le by choosing the Export Demo Data button. It stores the whole demo data set in
a single, local XML le, which can be used as basis for demo data in another system.

5. In another system, you open the WM monitor or warehouse cockpit in maintain demo data set mode. You import the
demo data by choosing the Import Demo Data button.

The system asks for a demo data set. If there is already a demo data set with that name in the target system, the
system asks you if the existing demo data should be merged or deleted.

Merge: The existing demo data is overwritten and the new demo data from the XML le is added to the target
demo data set.

Delete: The existing demo data set is deleted prior to the upload of the new data.

6. You open the WM monitor or warehouse cockpit in display demo data set mode. This mode allows you to display the
demo data set in the WM monitor or warehouse cockpit. You choose the demo data to be shown by entering a demo data
set in the dialog box when you start the WM monitor or the warehouse cockpit.

If there are several versions of the node or cockpit in the demo data set, the system displays the next version in the
sequence after each refresh of the screen. When you reach the end of the sequence, the system displays the rst version
again.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 125
 9/2/2022
By uploading demo data using an XML le from a different system, the display demo data set mode shows data that
might not exist in the system. This means that the master data, such as the product, and customizing data, such as
the warehouse process type, displayed in the demo might not exist in the system.

Delivery Processing

Purpose
Extended Warehouse Management (EWM) has its own Delivery Processing area. This is a signi cant part of the logistics chain.
Delivery processing offers functions for executing goods receipt and goods issue activities, as well as for executing posting
changes and internal stock transfers. The following sections describe the available functions, as well as the integration with
EWM.

For an overview of the available user transactions, see User Interfaces in Delivery Processing .

Corresponding to the goods receipt and goods issue, a distinction is made in delivery processing between the inbound delivery
process and the outbound delivery process.

Inbound Delivery Process

In the inbound delivery process, delivery processing supports the following scenarios:

Deliveries from the supplier, from any ship-from party, or from any ship-from location.

Returns from the customer, from any ship-from party, or from any ship-from location.

From the purchase order, the inbound delivery process covers the noti cation, the inbound delivery, the goods receipt posting of
the ordered goods, and the subsequent putaway.

Information about planning is saved in the inbound delivery, the status is monitored, and all the data collected during the
inbound delivery is kept. On creation of the inbound delivery, activities such as the putaway or scheduling are triggered and the
data generated by the inbound delivery process is recorded.

Outbound Delivery Process

In the outbound delivery process, delivery processing supports the following scenarios:

Deliveries to the customer, to the warehouse, to any ship-to party, or to any ship-to location.

Returns to the supplier, to any ship-to party, or to any ship-to location.

The outbound delivery process covers all shipping activities such as picking, packing, transportation and goods issue.

Information about shipping planning is saved in the inbound delivery, the status of the shipping activities is monitored, and all
the data collected during the shipping process is recorded. On creation of the outbound delivery, shipping activities such as
picking or shipment scheduling are triggered and the data generated by the shipping processing is recorded.

Features
In delivery processing, documents are provided which represent the delivery processes in the system. Delivery processing also
provides a series of services and functions to con gure how the documents are to be processed, and to de ne the business
features of the documents in a way that best suits your business process.

This is custom documentation. For more information, please visit the SAP Help Portal 126
 9/2/2022
The following services and functions are provided by delivery processing:

Status management

Quantity offsetting

Text management

Field control

Validation

Connection to the Post Processing Framework (PPF)

Change documents

Archiving

This is custom documentation. For more information, please visit the SAP Help Portal 127