SAP WM Storage Bin

You are an SAP Warehouse Management (WM) configuration expert. The user wants to configure the warehouse structure by creating storage types, sections, and bins in SAP WM.

What to check first

• Run transaction SE11 to verify the SAPL* table structures exist (TBIN, TSART, TBINS)
• Run transaction SPRO and navigate to Logistics → Warehouse Management to confirm WM module is active
• Check in transaction LT01 that at least one warehouse exists before creating storage bins

Steps

1. Access transaction OLMS (Maintain Warehouse Structure) or use SPRO → Logistics → Warehouse Management → Master Data → Bins
2. Create a storage type in SPRO → Logistics → Warehouse Management → System → Warehouse → Storage Types by entering storage type code, description, and assigning bin strategy (FIFO, LIFO, random)
3. Define storage sections under the storage type using transaction LT04 (Maintain Storage Sections) — assign section number, storage type, and aisle structure
4. Create bin levels using SPRO path above, specifying row, rack, and level numbering convention for your warehouse layout
5. Configure individual storage bins in transaction LT05 (Maintain Bins) by entering bin code (e.g., A-01-01-01 for Aisle-Section-Level-Position), linking to storage type and section
6. Set storage bin attributes: assign material types allowed, maximum weight capacity, and block status (free/blocked for putaway)
7. Use SPRO → Logistics → Warehouse Management → System → Warehouse → Bin Type Assignment to link bins to control strategies
8. Run transaction LIMR to verify bin master data and consistency check for storage structure completeness

Code

*&---------------------------------------------------------------------*
*& Report: Create Storage Bins in SAP WM
*&---------------------------------------------------------------------*
REPORT z_wm_storage_bin_config.

TABLES: tbin, tsart, tbins.

DATA: lt_bins TYPE TABLE OF tbin,
      ls_bin TYPE tbin,
      lt_sections TYPE TABLE OF tbins,
      ls_section TYPE tbins,
      lv_wh_code TYPE lagnum VALUE '100',
      lv_storage_type TYPE storagetype VALUE 'A01',
      lv_section TYPE lagbereich VALUE '001',
      lv_bin_code TYPE lagerplatz,
      lv_aisle TYPE int4,
      lv_rack TYPE int4,
      lv_level TYPE int4,
      lv_position TYPE int4.

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE 'Warehouse Config'.
PARAMETERS: p_wh_code TYPE lagnum DEFAULT '100',
            p_st_type TYPE storagetype DEFAULT 'A01',
            p_section TYPE lagbereich DEFAULT '001',
            p_aisles TYPE int

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change