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.
• 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
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).