4/3/25, 8:11 PM

SAP Extended Warehouse Management

(SAP EWM)
Generated on: 2025-04-03 20:11:54 GMT+0000

SAP Supply Chain Management (SAP SCM) | 7.0 EHP4

Public

Original content: https://help.sap.com/docs/SAP_SUPPLY_CHAIN_MANAGEMENT/57574d15fa1d414792d74047b66c3e41?

locale=en-US&state=PRODUCTION&version=7.0.4

Warning

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

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

This is custom documentation. For more information, please visit SAP Help Portal. 1
 4/3/25, 8:11 PM

Storage Bin Migration

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 first part is used to download the storage bin data and/or sortation data and store it in an
intermediate file.

The second part is used to upload the storage bin data and/or sortation data from the CSV file or the server file 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.

To use migration from LE-WM, you must activate the business function EWM, Usability and Implementation 1 (
SCM_EWM_USAB_IMPL_1).

Prerequisites

If you migrate the data by creating a local CSV file, the structure of this file must match the fields 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 file or the logical file name of the server file. You can also
refine 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 file.

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

For the storage bin sortation data, the fields 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 file for one storage bin.

The intermediate file in which data is stored is either a locally-stored CSV file or a logical file stored on the application
server. The CSV file has a header line with short text of the fields and can be edited with Microsoft Excel or a text editor.
Both files are based on the structure /SCWM/S_LAGP_LSMW_MIG. In the CSV file, the fields are separated either by a semi-
colon or a colon. The fields in the server file are not separated and there is no header line. The name of the CSV file always
has the extension '.csv'. The file type of the server file is taken from the setup of the logical file name. During the data
migration, the system ignores the first line of the CSV file, 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.

This is custom documentation. For more information, please visit SAP Help Portal. 2
 4/3/25, 8:11 PM
In LE-WM the sorting fields can contain alphanumeric values, whereas this is not possible in EWM. If the system identifies
alphanumeric values during download, it automatically resorts the affected activities in the activity area. If your sorting
fields 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:

LE-WM Value EWM Value

01 1

1 1

00001 1

00001 1

010203 10203

A1B2 Resort

13 Resort

The following fields are taken from LE-WM and transferred into the fields 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

This is custom documentation. For more information, please visit SAP Help Portal. 3
 4/3/25, 8:11 PM

LE-WM Field Length EWM Field Length Description

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 field for cross-line

stock put away

REIHF 6 Sort field for stock

removal

IDATU 8 IDATU 21, 7 Date of last inventory for

this storage bin

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 Verification field for

mobile data entry

This is custom documentation. For more information, please visit SAP Help Portal. 4
 4/3/25, 8:11 PM

LE-WM Field Length EWM Field Length Description

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 fields are taken from LE-WM and transferred into the fields 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 filled with value

from SORLP or REIHF

This is custom documentation. For more information, please visit SAP Help Portal. 5