Multi-carrier shipping perfectly integrated into your SAP® systems
Whether S/4, EWM, or ECC: AEB offers numerous pre-designed integration options for various scenarios. Choose the integration that best fits your system, operating model, and shipping process.
One carrier platform for various SAP integrations
AEB Carrier Cloud for SAP is a multi-carrier solution for companies that want to integrate their shipment processing directly into their SAP processes.
The central platform provides access to more than 300 parcel services and forwarders. Depending on the process and integration option, this can be used to do the following and more:
- Create shipping orders from SAP data
- Electronically commission transport service providers
- Create shipping labels and carrier documents
- Transfer tracking numbers and status data to SAP
- Automate shipping processes
- Optionally determine shipping costs per consignment
The suitable integration depends on your SAP environment. SAP ECC and SAP S/4HANA Private Cloud offer different integration options than SAP Cloud ERP, SAP EWM, or SAP Logistics Management.
Whatever your scenario, AEB offers not only a technical interface but also several pre-designed integration options for various SAP systems, operating models, and shipping processes.
Which multi-carrier integration is right for your SAP system?
Which integration is right for your SAP system and your business model? Here you'll find the answer – whether for SAP S/4HANA Public Cloud, Private Cloud, or on-premises, whether for SAP ECC or SAP EWM.
S/4HANA Public Cloud – HPC Integration
Quick setup, preconfigured, event-driven. Ideal for processes that closely follow standards.
S/4HANA Public Cloud – consolut BTP labeling app
Maximum flexibility on your own BTP infrastructure. Ideal for customized shipping processes.
SAP S/4HANA Private Cloud – FIS/PackingCenter
Digital packing station on SAP BTP. Side-by-side extension; no changes to the SAP backend. Ideal for packing station modernization.
SAP S/4HANA Private Cloud – AEB add-on
Native ABAP integration. All standard documents: delivery, transport, freight order.
SAP S/4HANA On-Premise
With the AEB add-on for SAP S/4HANA, you can integrate carrier functionality directly into your SAP dialogs and create shipping orders from outbound shipments, transports, and freight orders.
SAP ECC
The AEB add-on for SAP ECC offers proven native integration. Shipping orders are created from delivery and transport records.
SAP EWM – FIS/PackingCenter
Digital packing station on SAP BTP. Side-by-side extension; no changes to the SAP backend. Ideal for packing station modernization.
SAP EWM – AEB add-on
For deep integration into the EWM warehouse process. Fully automated shipping, triggered upon completion of packing.
SAP LGM integration by consolut
From within the native LGM packing work center, you can create shipping orders for your choice of over 300 forwarders and parcel services – fully native to BTP, without switching systems.
Here's how you find the right integration option
The choice of integration option depends in part, but not solely, on your SAP environment. Four questions are particularly important.
1. Which SAP system and operating model do you use?
SAP ECC and SAP S/4HANA Private Cloud or On-Premise support native add-on integration.
SAP Cloud ERP, on the other hand, requires a Public-Cloud-compatible approach using released interfaces, business events, and the SAP Business Technology Platform.
2. Where does your operational shipping process take place, and on what objects is it based?
If shipping is initiated from a delivery, a transport, or a freight order, integration with the ERP or TM system is recommended.
If the process takes place directly at the packing station, SAP EWM, SAP LGM, or a standalone packing station solution are the more relevant starting points.
3. Should the process run automatically or interactively?
Standardized shipping processes with complete data can be processed event-based in the background.
If employees need to add data, select carriers, or handle exceptions, an integration with its own user interface is usually the better option.
4. What is your extension strategy?
Depending on the SAP environment and architectural specifications, various options are possible:
- Native ABAP add-on
- Side-by-side integration on SAP BTP
- Event-based background integration
- Seamless integration with EWM or LGM
- Packing station solution with integrated multi-carrier shipping
Not every option is equally suitable for every system and every process. During the expert consultation, we'll work together to determine which approach best meets your needs.
Add-on, BTP integration, or integrated packing table solution: What's the difference?
Native SAP add-on
A native add-on is installed directly in SAP ECC or SAP S/4HANA Private Cloud or On-Premise.
It is suitable for companies that require deep integration with existing SAP documents, dialogs, and processes.
Side-by-side integration on SAP BTP
A side-by-side integration runs outside the SAP ERP core and communicates via released APIs and events.
This approach is particularly well-suited for SAP Cloud ERP, as well as for companies that follow a Clean Core extension strategy.
Event-based background integration
In this scenario, an SAP business event triggers the shipping process. Processing is largely automated and does not require an additional user interface.
This is particularly well-suited for standardized processes with complete data.
Custom BTP app
A BTP app provides its own user interface and custom process logic.
It is suitable when shipping staff need to add data, handle special cases, or integrate multiple systems into a single application.
Integration into existing warehouse processes
In SAP EWM and SAP Logistics Management, carrier communication is directly integrated with the respective packing and warehousing processes.
Employees handle packaging and shipping within their familiar SAP process environment, while communication with carriers and label generation are automated in the background.
Packing station solution with integrated shipping
A packing station solution integrates the packing process with carrier commissioning and label printing.
It is particularly relevant when, in addition to multi-carrier shipping, a new, process-driven user interface is needed at the packing station.
What all integration options have in common
Regardless of the technical integration method, the solutions access the same multi-carrier platform from AEB.
More than 300 transport service providers
AEB Carrier Cloud for SAP provides connections to more than 300 parcel services and forwarders.
Which carriers and services are specifically enabled depends on your company's transport contracts, shipping countries, and process requirements.
Less interface complexity, less carrier logic in SAP
AEB integrates the various data formats, interfaces, and labeling requirements of transport service providers into a single, centralized platform.
This eliminates the need to develop a completely new, direct SAP interface for every carrier.
Uniform carrier base across multiple systems
Even if a company uses multiple SAP systems, locations, or operating models, carrier communication can take place via the same AEB platform.
Carrier-specific labels and documents
The solution generates shipping labels, loading lists, waybills, and other documents in accordance with the requirements of the respective transport service provider.
Feedback for SAP processes
Tracking numbers and other relevant shipping data can be returned to the integrated SAP system.
The exact scope depends on the integration option and the agreed-upon set of features.
Easily determine freight costs
Optionally, freight costs can be determined for each consignment and transferred to SAP. Depending on the carrier, you can use current rates via API or your individually negotiated freight rates. Optionally, we can also handle the recording and maintenance of your freight agreements relying on an experienced team and specialized tools.
One carrier platform for your SAP migration
Many companies have been running multiple SAP systems for years or are migrating to SAP S/4HANA in phases.
AEB Carrier Cloud separates carrier communication from the actual SAP integration. Connections to parcel services and forwarders are made available centrally via the AEB platform.
If your SAP environment changes, the SAP-side integration will be adapted to the new target system. Carrier integrations do not need to be developed from scratch for every transport service provider.
This allows you to:
- modernize existing shipping processes in SAP ECC
- implement SAP S/4HANA in phases
- use different integration options for different locations
- deploy a common carrier platform across heterogeneous SAP environments
Andrej Grohar, expert for multi-carrier shipping directly from SAP®
Discover your best SAP integration option
Do you want to connect several parcel services and forwarders to SAP, but are unsure which integration option is the right one?