SAP business blueprint for warehouse management with SAP EWM

Our experts prepare an SAP business blueprint for introducing SAP EWM or SAP WM as a warehouse management system, based on the User Requirement Specifications drawn up in the preceding phase. The business blueprint contains a detailed description of the requirements of processes and features and serves as a basis for subsequent implementation.

Our services
    •    Preparation of an SAP business blueprint, with and without automation
    •    Specification and choice of hardware (RF terminals, voice, vision)
    •    Early prototyping of processes and dialogues
    •    Migration concept
    •    Creating a traceability matrix

Process SAP Implementation

1. SAP Strategy Consulting
2. SAP Concept Design
3. SAP Business Blueprint
4. SAP Implementation
5. Go-Live & Ramp-Up Management


Prior to the workshop to generate the SAP business blueprint, we hold an SAP EWM training for the client's project team so that they can actively participate in designing the future processes and features of SAP EWM.

The SAP business blueprint describes in detail the implementation of the master data, processes and interfaces defined in the User Requirement Specifications, including:

  • Customisation of the settings (e.g. warehouse master data, processes, storage and removal strategies, packaging data).
  • Definition of the required SAP EWM extension with BAdls or additional transactions. The intended GUI and RF transactions are determined and any necessary adaptations documented.

Although standard transactions and functions are still executed in the background to maintain the serviceability of the SAP system, the user interface can be adapted in the following areas:

  • Workstations at automated facilities (automatic small parts warehouse, high-bay warehouse, shuttles)
  • Mobile workstations (MDE dialogues, Pick-by-Vision, Pick-by-Voice, Pick-by-Light)
  • Workstations for incoming goods (goods receipt booking, deconsolidation)
  • Packing stations (order consolidation, full pallets, parcel services, freight)
  • Monitoring of capacity utilisation for the various activity zones
  • Retrieval monitoring for packaging, incl. picking and provision status

We develop intuitive and realistic dialogues for the user interface together with the client and provide prototypes at an early stage for testing and acceptance. This includes defining the requirements for paper receipts and labels, coordinating related ERP processes and identifying the resulting ERP gaps.

The business blueprint also contains a description of the IT hardware requirements, particularly for the data processing centre (equipment, security concept), for client and peripheral devices (PCs, MDE, scanners, printers, scales), and for the infrastructure (network, wifi).


Preparing the business blueprint

We prepare the business blueprint for the interfaces between SAP EWM and the secondary controls (e.g. automatic small parts warehouse, high-bay warehouse, scales, printers, put-to-light displays), together with the logistics equipment suppliers:

  • Technical specifications of the facility
  • General characteristics (partial autonomy, e.g. capacity considerations), autonomy levels of secondary controls
  • Interface types (SAP MFS telegram interface, SAP EWM IDoc interface)
  • Communication patterns and flows
  • Control structure
  • Reporting points in material flow
  • Process flows (placement, removal, return and transfer of goods)
  • Error situations and error handling
  • Development of a testing and implementation concept with the equipment suppliers and the client
  • Requirements of an SAP MFS interface emulator for automated testing of the interfaces to the secondary systems
  • Integration of carriers (shipping software for CEP service providers and shipping companies) in SAP EWM, particularly for printing address labels, remote data transmission connections for sending shipping and tracking data to the service providers
  • Description of the recommended methods for go-live and ramp-up, incl. migration and monitoring tools
  • Traceability matrix for full consideration of all the processes defined in the User Requirement Specifications and precise definition of the schedule up to go-live (e.g. implementation cycles, trainings, offline tests, commissioning of plants, machines and other equipment, migration and ramp-up concepts)

Please contact us 

Ansprechpartner IT: Marco Lederle
Marco Lederle Managing Director Phone: +49 6221 379-700


Christian Kaufmann Phone: +49 7152 928 33-40