Purpose

The purpose of this

specification is to define the

The purpose of this document is to define the conversion approach to create EWM Storage Bins

Storage Bin in EWM is the smallest addressable unit within a warehouse where goods can be stored. Each storage bin is uniquely identified within the warehouse and can hold a specific quantity of materials.

end-to-end approach for migrating Storage Bin Master Data from the legacy SAP WM environment into S/4HANA Extended Warehouse Management (EWM).

Storage bins are critical to warehouse operations as they represent the smallest managed physical units in a warehouse. They determine where stock is stored, how it is accessed, and which restrictions or capacities apply. Accurate migration ensures operational continuity post-cutover.

This document covers:

• Scope of bins to be converted.

• Extraction, transformation, cleansing, and loading approach.

• Detailed field-level mappings.

• Dependencies, error handling, validations, and governance rules.

Bins will be created via Data Collection Template (DCT) and uploaded using transaction /SCWM/SBUP.

.

Conversion Scope

In Scope

• Active, operational bins from the legacy WM system.

• Migration of all mandatory and optional fields required for EWM bin creation:

• Transformation of 3-character warehouse objects (warehouse number, storage type, storage section) to 4-character objects in S/4HANA.

• Upload through transaction /SCWM/SBUP using a Data Collection Template (DCT).

Out of Scope

• Deleted, obsolete, or test bins.

• Warehouses not part of deployment scope.

• Bin sorting rules, process type assignments, or fixed bin assignments (handled as separate conversion objects).

Conversion Scope

The scope of this document covers the approach for converting active Storage Bin from Legacy Source Systems into S/4HANA following the Master Data Standard - DD-FUN-050 Master Data  Standard - Bins. 

All the records (identified based on the relevancy rules and criteria provided in the Master data standard) need to be converted from legacy to S/4HANA system.

Where possible, Bins which do not exist physically / Logical Bins will be cleansed to conform to Master Data Standards. Cleansing activity is performed by Data cleansers in the legacy system before conversion. 

 The data from legacy system includes:

The data from legacy system excludes:

Source Approx No. of Records

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Data cleansing is essential to avoid loading irrelevant or invalid bins into EWM.

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Extraction

Extract data from a source into . There are 2 possibilities:

1. The data exists. connects to the source and loads the data into . There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Image Added

The process is divided into the following stages: Steps 2&3 are part of the DCT file generation 

1. Extraction – Pull relevant fields from legacy system.

2. Cleansing – Apply rules to remove duplicates, obsolete bins, invalid values.

3. Transformation – Apply mapping (3 → 4 char), defaults, and adjustments.

4. Pre-Load Validation – Confirm counts and mapping accuracy.

5. Load – Upload DCT file via /SCWM/SBUP.

6. Post-Load Validation – Confirm successful bin creation in target.

Data Privacy and Sensitivity

Extraction

Source System/Table:

• LAGP (WM Storage Bin Master) in legacy SAP WM.

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

DCT Rules

The DCT serves as the upload file for /SCWM/SBUP.

• Mandatory columns: LGNUM, LGTYP, LGPLA.

• Optional columns included if available and relevant.

• Populated from transformed extract. Will occur as users are constructing data in DCT

• Used both for load and as record of migration scope.

Extraction Dependencies

• Target warehouse org structure (LGNUM, LGTYP, LGSEC) must exist.

• Mapping of 3 → 4 char codes finalized and signed off.

• Legacy data must be cleansed prior to staging.

• Notes:

  • Mandatory: LGNUM, LGTYP, LGPLA.

  • All other fields are optional depending on warehouse design.

  • Validation will check presence of mandatory fields before load.

Transformation

Transformation covers:

• Org fields: 3 → 4 char conversion for LGNUM, LGTYP, LGSEC.

• Bin numbers: Migrated 1:1 (LGPLA).

• Capacities: Defaults applied if missing.

• Blocks and verification: Carried forward only if maintained.

• Coordinates: Loaded if consistent with warehouse design.

Transformation Rules

Transformation Mapping

Mapping tables will be maintained for:

• Warehouse Number (legacy 3-char → EWM 4-char)

• Storage Type (legacy 3-char → EWM 4-char)

• Storage Section (legacy 3-char → EWM 4-char)

Legacy source table : LAGP - storage bin Masterdata

Transformation Dependencies

• Warehouse customizing must match mapping values.

• Master data creation must be completed before transformation.

Extraction Dependencies

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Sample Load File :

Load Run Sheet

Load Phase and Dependencies

Configuration

Conversion Objects

• Predecessor: Warehouse org structure migration.

• Successor: Bin sorting, warehouse process type assignment.

Configuration

N/A

Error Handling

Error handling is critical because /SCWM/SBUP rejects invalid or incomplete bins.

Error Categories

• Error Type	Example	Resolution
  Missing mandatory field	LGNUM not provided	Correct DCT and reload
  Invalid mapping	Legacy 101 not mapped to WH01	Update mapping table
  Incorrect capacity values	MAX_WEIGHT = negative	Correct or default value
  Org mismatch	LGTYP not configured in target warehouse	Validate customizing
  Bin already exists	Duplicate LGPLA	Remove duplicate before reload

  
  

• Error Handling Process

  1. Run /SCWM/SBUP and review error log.

  2. Categorize errors (mapping, cleansing, config, duplication).

  3. Correct DCT file.

  4. Reload corrected bins.

  5. Track and report error resolution status to Project Governance.

Post-Load Validation

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.

• All target org structures (LGNUM, LGTYP, LGSEC) configured and available before load.

• 3 → 4 character mappings signed off prior to conversion.

• Bin numbers migrate 1:1.

• /SCWM/SBUP is

in scope based on data design and any exception requested by business.

• the only upload method.

• Governance applies:

  • Change of Bin Data: Allowed under strict approval.

  • Deletion of Bins: Only if empty and not in use, requires business approval

See also

Change log

Workflow history