Multi-carrier shipping for SAP S/4HANA^®

Q: How are carriers connected to SAP S/4HANA?

The AEB add-on connects SAP S/4HANA to the AEB Carrier Cloud via web services. SAP transmits the required shipping data to the multi-carrier platform. AEB formats this information according to the selected transport service provider's specifications and handles the technical communication with the carrier.

Q: Which S/4HANA operating models is the add-on suitable for?

The native ABAP add-on is designed for SAP S/4HANA Cloud Private Edition and SAP S/4HANA On-Premise. Other, cloud-based integration options are available for SAP S/4HANA Cloud Public Edition and SAP Cloud ERP.

Q: Can shipping labels be printed directly from SAP?

Yes. AEB generates shipping labels in accordance with the selected transport service provider's specifications. Printing can be initiated directly from the SAP process or automated for standardized workflows.

Q: Are tracking numbers reported back to SAP?

Yes. Tracking numbers and other relevant shipping order data can be returned to SAP S/4HANA and assigned to the relevant transaction.

Q: Does a separate SAP interface have to be developed for each carrier?

No. SAP S/4HANA is connected to AEB Carrier Cloud once. The carrier-specific interfaces and communication formats are mapped within the AEB platform. For an additional carrier, therefore, it is not usually necessary to develop a completely new, direct connection between SAP and the transport service provider.

Q: What is the difference between AEB Carrier Cloud and the add-on for SA??

AEB Carrier Cloud is the central multi-carrier platform. It handles technical communication with the connected parcel services and forwarders. The add-on for SAP serves as the integration method for SAP S/4HANA private cloud and on-premise. It connects the SAP documents and shipping processes with the AEB platform.

Connect more than 300 parcel services and forwarders to your SAP S/4HANA system and organize shipping processes based on deliveries, transports, and freight orders: from carrier commissioning to label printing and tracking – directly within SAP S/4HANA private cloud or on-premises.

Request demo

What does AEB Carrier Cloud for SAP S/4HANA offer?

AEB Carrier Cloud for SAP is a multi-carrier solution for companies that want to manage their shipment processing directly from SAP S/4HANA.

The solution connects SAP documents – such as deliveries, transports, and freight orders – with shipment processing for more than 300 parcel services and forwarders. Shipping staff can electronically commission transport service providers, generate carrier-specific shipping labels, and import feedback – such as tracking numbers – back into SAP.

Integration is achieved via a native ABAP add-on for SAP S/4HANA Cloud Private Edition and SAP S/4HANA On-Premise. The add-on is installed without any modifications and integrates the functions of AEB Carrier Cloud into existing SAP dialogs and business processes.

SAP remains the leading system for delivery, transport, and package data. AEB handles carrier-specific communication with the connected transport service providers.

Why do companies need a multi-carrier solution for SAP S/4HANA?

SAP S/4HANA contains much of the data required for shipment processing. However, communication with parcel services, express delivery providers, and forwarders is subject to different technical and operational requirements depending on the individual carrier. Among other things, transport service providers use different:

Interfaces and communication formats
Shipping products and additional services
Mandatory fields and ID numbers
Label and document specifications
Booking and cancellation processes
Tracking and status messages

For direct connections, these requirements must be integrated into the SAP landscape and maintained on an ongoing basis separately for each carrier. By contrast, AEB Carrier Cloud establishes a central connection between SAP S/4HANA and more than 300 parcel services and forwarders. Carrier-specific formats, labeling requirements, and communication processes are automatically mapped within the AEB platform.

This eliminates the need to develop and maintain a completely new direct interface in SAP for every additional transport service provider.

How does shipment processing work in SAP S/4HANA?

1. Use SAP document as a basis

The shipping process begins with an existing SAP document. Depending on the logistics architecture used, this could be a delivery, a transport, or a freight order.

The existing SAP data forms the basis for the shipping order. This may include:

Consignor and consignee
Delivery and pickup addresses
Goods and packages
Weights and dimensions
Shipping conditions
Transport service provider
Planned shipping service

It is not necessary to manually re-enter this data into a carrier portal.

2. Generate shipping order from SAP

AEB Carrier Cloud automatically retrieves all necessary data from the relevant SAP document.

If any information is missing, an integrated wizard guides the user through the process and helps to add the missing shipping information. The exact process can be tailored to the requirements of the relevant company and the specific shipping location.

3. Determine carrier and shipping service

The appropriate parcel service or forwarder is selected for the consignment, along with the necessary service.

Depending on the process, the carrier and shipping service may be:

Already contained in the SAP document
Derived from an upstream planning process
Determined by Carrier Cloud based on rules
Selected manually during shipping data entry

4. Transmit shipping data to AEB Carrier Cloud

The add-on for SAP transfers the required shipment data to AEB Carrier Cloud via web services. The AEB solution verifies and processes the information before preparing it in the stipulated format of the selected transport service provider.

5. Electronically commission the transport service provider

AEB Carrier Cloud transmits the shipping order to the carrier and processes the carrier's response. This means that the various interfaces and communication formats used by parcel services and forwarders do not need to be implemented individually in SAP S/4HANA.

6. Generate shipping labels and documents

AEB generates the required shipping labels and other carrier documents in the prescribed format. Printing can be initiated directly from the SAP process or automated for standardized workflows – for example, upon completion of a packing process.

7. Transfer tracking numbers and shipping data to SAP

Relevant carrier feedback and status messages are sent back to SAP S/4HANA and assigned to the relevant shipping transaction. This includes, in particular, tracking numbers and other data from the carrier commissioning.

What key functionality does the solution support?

Create shipping orders automatically from SAP documents. For all transport routes and types (packages, pallets, LTL/FTL containers)
Automatically generate labels in SAP in the native printer language, with flexible process integration
Integrate high-performance printers (laser, thermal, industrial), connect to tagging and labeling systems
Ship hazardous goods with legal and regulatory compliance
Manage multi-package shipments or package-by-package processing
Shipment tracking and entry certificate
Determine freight costs per shipment with direct transfer to SAP – always up-to-date for all parcel services and forwarders

How is the multi-carrier solution integrated into SAP S/4HANA?

AEB Carrier Cloud connects to SAP S/4HANA Cloud Private Edition or SAP S/4HANA On-Premise via a native ABAP add-on.

Modification-free installation

The add-on is installed without modifying the SAP standard. It uses standard SAP technologies and designated extension points such as Business Add-Ins.

AEB provides its own installation packages and regularly updated service packs for current SAP S/4HANA releases.

Integration into existing SAP processes

The shipping functions are integrated directly into the relevant SAP dialogs and documents. This allows employees to work in their familiar SAP environment.

Direct connection to the AEB Cloud

The add-on communicates with AEB Carrier Cloud via web services. No separate middleware is required for the standard integration.

Company-wide integration guidelines or additional system requirements can be taken into account in the implementation project.

Clear separation of responsibilities

The add-on for SAP handles the integration into SAP processes and data exchange with AEB.

AEB Carrier Cloud handles carrier-specific communication, processes carrier responses, and generates the necessary labels and documents.

What are the benefits of AEB Carrier Cloud for SAP S/4HANA?

Shipping directly from the SAP environment

Employees manage shipping orders, carrier assignments, and label printing within their familiar SAP processes. This eliminates the need for manual duplicate entries and switching between different carrier portals.

One connection to numerous transport service providers

SAP S/4HANA is connected to AEB Carrier Cloud once. This connection provides access to more than 300 parcel services and forwarders. It is not usually necessary to develop a completely new, direct SAP interface for additional carriers.

Support for various SAP documents

The integration can generate shipping orders from deliveries and transports, as well as – with an appropriate SAP TM architecture – from freight orders. This allows the multi-carrier processing to be integrated with various logistics source processes.

Less carrier-specific logic in SAP

Different data formats, labeling requirements, and communication processes are managed centrally in AEB Carrier Cloud. Therefore, these requirements do not have to be developed and maintained individually in SAP S/4HANA for each transport service provider.

Automation of standard processes

Once the carrier, service, and all necessary data have been clearly specified, the shipping order, carrier communication, and label printing can be largely automated.

Transparent exception handling

Incorrect and incomplete shipping orders are displayed in the central shipping status monitor, where they can be processed in a targeted manner.

Extensible shipping architecture

Additional carriers, shipping services, and locations can be integrated via the central multi-carrier platform without having to rebuild the underlying architectural model.

What companies is the solution suitable for?

AEB Carrier Cloud for SAP S/4HANA is designed for industrial and commercial companies that use SAP S/4HANA Cloud Private Edition or SAP S/4HANA On-Premise and want to manage multiple parcel services or forwarders directly from SAP.

The solution is particularly suitable for companies that:

Use deliveries, transports, or freight orders as a starting point
Commission multiple parcel services and forwarders
Require deep integration into existing SAP dialogs
Want to avoid manual entry of shipping data into carrier portals
Want to automate carrier commissioning and label printing
Do not want to use an additional middleware layer for standard integration
Want to handle errors and exceptions centrally
Would like the option of determining freight costs directly within the shipping process
Are looking for a modification-free, maintainable SAP extension

The solution is particularly relevant for companies with multiple shipping locations, high shipment volumes, or a diverse landscape of national and international carriers.
AEB offers dedicated integration options for many other system landscapes.

Compare all integrations for AEB Carrier Cloud for SAP

Architecture profile with technical details

Target system	SAP S/4HANA Cloud Private Edition and SAP S/4HANA On-Premise
Integration type	Native ABAP add-on installed without modifications
SAP source documents	Delivery, transport, and – depending on the architecture used – freight order
SAP-side operation	Integration into existing SAP dialogs, guided entry of shipping data, and central shipping status monitor
Connection to AEB Cloud	Web services
Carrier communication	AEB Carrier Cloud
Label printing	Directly or automatically from the SAP process
Tracking and feedback to SAP	Status messages, tracking numbers, and other relevant shipping order data
Middleware	Not required in the standard scenario
Freight cost determination	Available as an option

Talk with our experts to learn more about multi-carrier shipping directly in SAP S/4HANA

Andrej Grohar, expert for multi-carrier shipping directly from SAP^®

I hereby confirm that I have read the data protection statement and have taken note of the right to withdraw/object.

Yes, I would like to receive information by email from AEB about specialist topics, events, and seminars as well as products. The data I have specified may be used for this purpose. I can cancel the newsletter at any time.

Frequently asked questions about multi-carrier shipping in SAP S/4HANA

What is a multi-carrier solution for SAP S/4HANA?

A multi-carrier solution connects shipping processes in SAP S/4HANA with multiple parcel services and forwarders. Companies can transmit shipping orders electronically, generate carrier-specific labels, and import feedback – such as tracking numbers – back into SAP. To this end, AEB Carrier Cloud is integrated into SAP S/4HANA Cloud Private Edition or SAP S/4HANA On-Premise via a native ABAP add-on.

How are carriers connected to SAP S/4HANA?

Which S/4HANA operating models is the add-on suitable for?

Is middleware required?

Can shipping labels be printed directly from SAP?

Are tracking numbers reported back to SAP?

Does a separate SAP interface have to be developed for each carrier?

What is the difference between a BTP integration and a Clean Core integration?

The native add-on is installed directly in SAP S/4HANA and enables deep integration with SAP documents and dialogs. It is installed without any modifications and uses the standard SAP extension technologies. It does not change the standard SAP code. A BTP-based side-by-side integration runs outside the SAP S/4HANA system and communicates via released APIs and events. In particular, this integration may be better suited for public cloud or strictly decoupled extension architectures.

What is the difference between AEB Carrier Cloud and the add-on for SA??

How is solution implemented?

1. Analyze the SAP and shipping landscape: The relevant SAP systems, releases, documents, shipping locations, and transport service providers are evaluated. This involves determining, for example, which delivery, transport, or freight order processes are used, which carriers and shipping services are required, and how packages and handling units are mapped.

2. Define the target process: The future workflow – from the SAP document to carrier commissioning and generation of the shipping label – is defined. Standard processes, automations, and relevant exceptions are considered together.

3. Install and connect the add-on: The AEB add-on is installed in the SAP S/4HANA landscape. The technical connections to AEB Carrier Cloud are then established.

4. Configure SAP and carrier processes: Documents, data fields, rules, carrier services, printing processes, and feedback are configured according to the company's requirements.

5. Test real-world shipping scenarios: The integration is tested using typical shipping processes. This includes various carrier services, package types, printing processes, as well as error and cancellation scenarios.

6. Go live with locations and carriers: Upon successful acceptance, the solution can be rolled out incrementally by location, country, process, or transport service provider.