Carrier integration for SAP® EWM: 300+ carriers. One interface. Zero custom code.
Every new carrier connection to SAP EWM often takes weeks to implement and later becomes a maintenance burden. With the AEB add-on for SAP EWM, you can integrate our Carrier Cloud for SAP directly into your warehouse processes and access all major carriers.
You use SAP EWM and want to manage multiple parcel services or forwarders directly from the system – without having to build a separate interface for each carrier. With the add-on for SAP, you can integrate AEB Carrier Cloud directly into your warehouse processes as a standard extension without modifications. Shipping orders, label printing, and tracking are handled entirely within SAP EWM. No separate system. No custom development. No training for warehouse employees.
More than 300 forwarders and parcel services are available in Carrier Cloud for SAP. Carriers that already exist in AEB Carrier Cloud can be utilized via the central SAP EWM integration without having to develop a completely new point-to-point interface for each service provider. The specific activation process depends on the carrier, service, contract, and shipping process required.
What does Carrier Cloud do in combination with SAP EWM?
Once packing of the handling unit (HU) is complete, the add-on triggers the shipping order. Communication with the carrier, label generation, and the return of tracking numbers and tracking information all take place in the background – warehouse staff remain in their familiar EWM dialogs.
| Process step | What Carrier Cloud for SAP EWM does |
|---|---|
| HU packing completion | Shipping order triggered automatically |
| Carrier communication | Carrier Cloud transmits data in a carrier-specific format |
| Label feedback | Shipping labels can be printed directly from EWM |
| Tracking | Consignment number and status returned to EWM |
| Status overview | EWM cockpit for all shipping orders |
EWM carrier integration with AEB: your benefits
- Maximum process integration: shipment processing directly within SAP EWM as an integral part of the EWM process
- Automatic generation of shipping labels
- Tracking information flows directly back to SAP
- Significantly less effort required for new carriers
- Fewer custom interfaces
- Support for modern Clean Core architectures
- No modification risk; upgradeable via standard BAdIs
- Rapid implementation through standard integration
- No external UI: warehouse employees remain in EWM dialogs
How do SAP EWM, the AEB add-on, and Carrier Cloud interconnect?
SAP EWM provides the shipment, package, and handling unit data required for shipping. The AEB add-on triggers the shipping process at the defined stage and transfers the data to AEB Carrier Cloud, where the carrier-specific formats and services are processed. Shipping labels, tracking numbers, and status information are then returned to SAP EWM.
Who is a carrier platform with SAP EWM suitable for?
Centralized carrier integration is particularly beneficial for industrial companies that want to make their shipping processes in SAP EWM efficient and future-proof. The benefits are particularly significant when multiple parcel services, forwarders, or international transport service providers need to be connected, and the requirements for shipping services, countries, or customers are constantly growing.
Companies that are standardizing their SAP landscape based on a Clean Core strategy or planning a migration to SAP S/4HANA also benefit from a centralized multi-carrier solution. Instead of developing and continuously maintaining numerous individual interfaces, SAP EWM communicates with all connected carriers via a single connection to AEB Carrier Cloud for SAP.
This reduces maintenance effort, simplifies SAP upgrades, and creates a scalable foundation for future shipping requirements.
For which EWM setups is AEB's carrier integration suitable?
The add-on is particularly suitable if:
- SAP EWM is embedded in S/4HANA or operated as a decentralized system
- The shipping process is to be highly automated (triggered upon completion of packing)
- No separate shipping UI is desired – warehouse staff remain within EWM
- Multiple carriers are to be managed centrally, without custom developments
- SAP updates must not be compromised by custom code
- You operate a highly automated warehouse and want shipping orders to be processed without manual intervention
Carrier integration in EWM via the add-on is less suitable if:
- You use SAP LGM (cloud-native, BTP). More information on LGM integration
- You are aiming for a complete side-by-side architecture on BTP. More information on BTP integration
How does carrier integration in SAP EWM work from a technical standpoint?
The add-on requires no modifications and is SAP-update-safe – below are the technical details for your architecture review:
| Target system | SAP EWM (embedded / decentralized) |
|---|---|
| Integration approach | ABAP add-on – deeply integrated into the EWM core; operation within the SAP system |
| Technology | ESI (Express Shipping Interface) + standard BAdIs + PPF; web services |
| Trigger | Automatic upon completion of packing (HU) or configurable status |
| Clean Core suitability | Yes, but as a modification-free add-on within the system (standard BAdIs), it is not equivalent to a fully decoupled side-by-side extension. |
Make your shipping processes future-proof
Andrej Grohar is responsible for Carrier Cloud for SAP at AEB. Having previously worked at DHL Freight and Danzas, he understands the real-world requirements of daily shipping operations, not just the technical aspects. In an initial conversation, we will clarify the following:
- Is the add-on suitable for your EWM architecture?
- Which of your carriers are already connected?
- What does a realistic implementation plan look like for your company?
Andrej Grohar, expert for multi-carrier shipping directly from SAP®
Frequently asked questions about carrier integration in SAP EWM
The integration of parcel services and forwarders into SAP EWM raises similar questions for many companies – ranging from technical connection and maintenance requirements to Clean Core and SAP S/4HANA. Below, we answer the most important questions that SAP managers regularly ask us.