Purpose

The purpose of this specification is to define the 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).

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:

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)

<Object> 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

• Mapping tables must be reviewed and approved by Functional and Business owners.

• Warehouse customizing must match mapping values.

• Legacy cleansing must be completed before transformation.

Pre-Load Validation

Project Team

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

• Predecessor: Warehouse org structure migration.

• Successor: Bin sorting, warehouse process type assignment.

Configuration

List the Configurations required before loading can commence

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

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 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

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history